https://bugzilla.kernel.org/show_bug.cgi?id=215882
--- Comment #2 from Hans de Goede (jwrdego...@fedoraproject.org) --- Thank you for your bug report. It seems that this is actually caused by the fix for: https://bugzilla.redhat.com/show_bug.cgi?id=1610545 Based on: https://wiki.archlinux.org/title/Nuvision_Solo_10_Draw which says that this was introduced in July 23, 2019, I suspect that the fix for rhbz#1610545 : https://github.com/torvalds/linux/commit/9bcf15f75cac3c6a00d8f8083a635de9c8537799 actually causes this issue, or at least exposed a pre-existing problem with the device's firmware which was hidden before. I guess this really actually is the same as bug 203829, which is about a similar bug on a Lenovo Ideapd 100S exposed by the kernel now honoring the battery-temperature-sensor-bias-current configured by the BIOS (honoring as in leaving it as is), rather then hardcoding 80 ųA for this. Can you disable the workaround and then read the value of both registers ? : modprobe i2c-dev i2cget -y -f 6 0x34 0x82 i2cget -y -f 6 0x34 0x84 And let me know the value of both registers? Then please try the following instead as workaround: i2cset -y -f 6 0x34 0x84 0xf3 Unlike the workaround which you have been using this does actually leave the temperature sensor input to the charger enabled, but switches the bias current to 80 ųA as Linux used to do in kernels older then kernel 5.0. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug. _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
