Launchpad has imported 9 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=208171.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2020-06-14T22:21:02+00:00 peteole2707 wrote: On my lenovo ideapad 5 14ARE05 random decides whether the touchpad works or not, but it stays the same until a second boot. Unlike the 15 inch version it has the following touchpad: Device 'MSFT0004:00 06CB:CD98 Touchpad': When it does not work, I get the following kernel error every few seconds: i2c_designware AMDI0010:00: controller timed out It is recognized by xinput in inoperational condition as well. However, the behavior is not totally random. Chances are much better if I shut the computer down and then power it on after a few seconds compared to hitting the reboot button. I am using manjaro linux, but also tried ubuntu and fedora, it's the same on all distros as well as on the 5.6 kernel. I have been wondering if it is possible to completely restart the touchpad until it works, but I could not find out which component need to be restarted for that and how to do it. This would be a great functionality to fix all kinds of hardware bugs. Another idea would be to find out what makes the touchpad go into the working or not working state. I would be pleased for any ideas. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-signed- hwe/+bug/1878279/comments/34 ------------------------------------------------------------------------ On 2020-06-27T07:47:57+00:00 louismichel wrote: I have the same touchpad issues with the same laptop IdeaPad 5 14ARE05 I added the kernel boot parameters: "dynbg=file drivers/input/* +pt" i8042.debug=1 i8042.nopnp=1 log_buf_len=32M Then I could get the following logs: On kernel 5.7.6: (no touchpad at all) i2c_hid i2c-MSFT0004:00: HID over i2c has not been provided an Int IRQ i2c_hid: probe of i2c-MSFT0004:00 failed with error -22 On kernel 5.8.2-rc2 mainline: (touchpad acting limited) i2c_hid i2c-MSFT0004:00: supply vdd not found, using dummy regulator i2c_hid i2c-MSFT0004:00: supply vddl not found, using dummy regulator i2c_hid i2c-MSFT0004:00: failed to retrieve report from device. input: MSFT0004:00 06CB:CD98 Mouse as /devices/platform/AMDI0010:00/i2c-0/i2c-MSFT0004:00/0018:06CB:CD98.0001/input/input13 input: MSFT0004:00 06CB:CD98 Touchpad as /devices/platform/AMDI0010:00/i2c-0/i2c-MSFT0004:00/0018:06CB:CD98.0001/input/input14 hid-generic 0018:06CB:CD98.0001: input,hidraw0: I2C HID v1.00 Mouse [MSFT0004:00 06CB:CD98] on i2c-MSFT0004:00 i2c_hid i2c-MSFT0004:00: failed to retrieve report from device. input: MSFT0004:00 06CB:CD98 Mouse as /devices/platform/AMDI0010:00/i2c-0/i2c-MSFT0004:00/0018:06CB:CD98.0001/input/input16 input: MSFT0004:00 06CB:CD98 Touchpad as /devices/platform/AMDI0010:00/i2c-0/i2c-MSFT0004:00/0018:06CB:CD98.0001/input/input17 hid-multitouch 0018:06CB:CD98.0001: input,hidraw0: I2C HID v1.00 Mouse [MSFT0004:00 06CB:CD98] on i2c-MSFT0004:00 Hope that can helps us all find a fix for that issue. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-signed- hwe/+bug/1878279/comments/45 ------------------------------------------------------------------------ On 2020-06-27T12:08:57+00:00 peteole2707 wrote: Thanks! I also realized that chances are better for the touchpad to work if it worked on the last boot. I believe the kernel does strange things with it when it spams me with "controller timed out" messages on shutdown. I wrote a script which prevents the system from having these shutdown issues. It unloads some modules and then reloads them. Unfortunately it only helps for the next boot, the touchpad is never even recognized after running it. sudo modprobe -r i2c_hid sudo modprobe -r i2c_piix4 sudo modprobe -r hid_multitouch sudo modprobe i2c_hid sudo modprobe i2c_piix4 sudo modprobe hid_multitouch It helps to break "bad boot streaks" Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-signed- hwe/+bug/1878279/comments/46 ------------------------------------------------------------------------ On 2020-06-28T06:56:38+00:00 louismichel wrote: Interesting find indeed when doing sudo modprobe -r i2c_hid sudo modprobe i2c_hid The "controller timed out" messages stops. Although that does not fix the touchpad it does suggest that this module is at cause. After further digging, I got another set of log after booting on mainline (appended below). Basically, I see that the following shows up first before the "time out spamming" starts: i2c_designware AMDI0010:00: i2c_dw_handle_tx_abort: lost arbitration i2c_designware AMDI0010:00: controller timed out i2c_hid i2c-MSFT0004:00: failed to retrieve report from device. Now, I found these 3 exact log messages in this commit to fix another DELL Win8 touchpad in 2015: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.8-rc2&id=6d4f5440a3a2bb2e9d0d582bbf98234e9e9bb095 Maybe some learning from this commit can lead us to fix this for the MSFT touchpad. Here my latest log on mainline: --------------- i2c_hid i2c-MSFT0004:00: supply vdd not found, using dummy regulator i2c_hid i2c-MSFT0004:00: supply vddl not found, using dummy regulator i2c_designware AMDI0010:00: i2c_dw_handle_tx_abort: lost arbitration i2c_designware AMDI0010:00: controller timed out i2c_hid i2c-MSFT0004:00: failed to retrieve report from device. input: MSFT0004:00 06CB:CD98 Mouse as /devices/platform/AMDI0010:00/i2c-0/i2c-MSFT0004:00/0018:06CB:CD98.0001/input/input13 input: MSFT0004:00 06CB:CD98 Touchpad as /devices/platform/AMDI0010:00/i2c-0/i2c-MSFT0004:00/0018:06CB:CD98.0001/input/input14 hid-generic 0018:06CB:CD98.0001: input,hidraw0: I2C HID v1.00 Mouse [MSFT0004:00 06CB:CD98] on i2c-MSFT0004:00 i2c_designware AMDI0010:00: controller timed out i2c_hid i2c-MSFT0004:00: failed to retrieve report from device. i2c_designware AMDI0010:00: controller timed out i2c_hid i2c-MSFT0004:00: failed to retrieve report from device. i2c_designware AMDI0010:00: controller timed out i2c_hid i2c-MSFT0004:00: failed to retrieve report from device. i2c_designware AMDI0010:00: controller timed out i2c_designware AMDI0010:00: controller timed out i2c_hid i2c-MSFT0004:00: failed to retrieve report from device. input: MSFT0004:00 06CB:CD98 Mouse as /devices/platform/AMDI0010:00/i2c-0/i2c-MSFT0004:00/0018:06CB:CD98.0001/input/input17 input: MSFT0004:00 06CB:CD98 Touchpad as /devices/platform/AMDI0010:00/i2c-0/i2c-MSFT0004:00/0018:06CB:CD98.0001/input/input18 hid-multitouch 0018:06CB:CD98.0001: input,hidraw0: I2C HID v1.00 Mouse [MSFT0004:00 06CB:CD98] on i2c-MSFT0004:00 i2c_designware AMDI0010:00: controller timed out i2c_designware AMDI0010:00: controller timed out i2c_hid i2c-MSFT0004:00: failed to set a report to device. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-signed- hwe/+bug/1878279/comments/47 ------------------------------------------------------------------------ On 2020-07-11T11:19:32+00:00 peteole2707 wrote: Interestingly there are phases which last a few days where it works perfectly. I am wondering which events trigger these phases. Maybe some windows update which makes it go into another shutdown state? Or some updates deep in the kernel? It once changed after trying to install a dkms module to get virtualbox running... Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-signed- hwe/+bug/1878279/comments/51 ------------------------------------------------------------------------ On 2020-07-11T12:02:12+00:00 tim wrote: Created attachment 290225 attachment-6042-0.html In my case, the laptop is my son's. Tonight, I gave up on manjaro, and installed ubuntu. Touchpad didn't work. Booted into windows ... and it also didn't work (which was new, my son who has been using it for a week and half has not seen this before). Was not visible in Device Manager, and scanning for new hardware did not reveal anything. I could not find any Lenovo drivers to download.. I rebooted a few times. No touchpad in windows. But there was a BIOS update, (1.06 I think, from July 8, change note says something about SI03 fixes). I applied that. Secure Boot was reenabled, and the trackpad worked again in windows. But still no good in Ubuntu. This is with mainline 5.7.8 and 5.8 RC4. The BIOS update readme said nothing about touchpad, but it looks like flashing the BIOS fixed the problem (in Windows). On Sat, 11 Jul 2020 at 21:19, <bugzilla-dae...@bugzilla.kernel.org> wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=208171 > > --- Comment #4 from Ole Petersen (peteole2...@gmail.com) --- > Interestingly there are phases which last a few days where it works > perfectly. > I am wondering which events trigger these phases. Maybe some windows update > which makes it go into another shutdown state? Or some updates deep in the > kernel? It once changed after trying to install a dkms module to get > virtualbox > running... > > -- > You are receiving this mail because: > You are on the CC list for the bug. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-signed- hwe/+bug/1878279/comments/52 ------------------------------------------------------------------------ On 2020-07-13T11:25:17+00:00 tim wrote: I think that the touchpad can be reliably reset to a working state in either Windows or Linux by shutdown without AC power attached. In other circumstances, a restart can still leave the laptop with a non-working touchpad, including in Windows. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-signed- hwe/+bug/1878279/comments/55 ------------------------------------------------------------------------ On 2020-08-01T07:44:50+00:00 alexmaras wrote: I have the same issue - am happy to help with logs or debug if needed. With either 5.7 or 5.8rc7, and with no dual-boot at all (linux only), the trackpad will sometimes fail to come up on boot. The state will sometimes change when coming out of hibernation as well, without a full shutdown/reboot. Today, the trackpad wasn't working. After hibernating, waiting a while, then starting up again, it returned from hibernation successfully with a working trackpad. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-signed- hwe/+bug/1878279/comments/66 ------------------------------------------------------------------------ On 2020-08-04T18:50:12+00:00 kxra wrote: Looping in some other discussion: * https://bugs.launchpad.net/linux/+bug/1884981 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-signed- hwe/+bug/1878279/comments/70 ** Changed in: linux Status: Unknown => Confirmed ** Changed in: linux Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878279 Title: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1878279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
