The touchpad randomly stops working. Sometimes it works after boot, sometimes it doesn’t respond at all.
When the issue happens, I see the following errors in the system log:
Failed to start lenovo-touchpad-reset.service - Reset I2C Touchpad Lenovo
ACPI Error: Method execution failed \_SB.PC00.I2C0.TPAD._CRS
AE_AML_PACKAGE_LIMIT
ACPI BIOS Error (bug): Could not resolve symbol
[\_SB.PC00.I2C0.TPD0], AE_NOT_FOUND
What I Have Tried
Press and hold the power button for 30 seconds (power drain).
This sometimes fixes the issue, but not consistently.
Rebooting the system.
Switching between Wayland and X11 (no permanent fix).
Additional Notes
The error seems related to ACPI / BIOS / I2C touchpad initialization.
The lenovo-touchpad-reset.service fails to start.
This looks like a firmware or kernel compatibility issue.
Question
Has anyone experienced a similar issue with Lenovo IdeaPad 5 touchpads on Linux?
Is there a known workaround, kernel parameter, BIOS setting, or patch that can fix this permanently?
Any help or guidance would be greatly appreciated.
Thank you
Unfortunately, I have completely removed Windows from my system and replaced it with Zorin OS.
Is there anything I can still do in this situation?
Do I really need to reinstall Windows just to disable Fast Startup, or is there an alternative solution available on Linux/Zorin OS?
When you switch to Xorg (logout and at login click on your username then a cog wheal appears at the bottom right corner, there you can switch between Xorg and Wayland), you can run this command from Terminal when the touchpad isn't working. Press ctrl+Alt+t
and then enter
xinput --enable "MSFT0004:00 06CB:CD98 Touchpad"
I read that it helped to add the kernel parameter pci=nocrs to /etc/default/grub but I'm not sure if it is worth to add it only because of the touchpad. And all threads were older ones, so I'm not sure if this problem exists in the current 6.14 kernel.
Maybe Aravisian can tell you more whether this parameter is harmful. I would be cautious with this kernel parameter because it is not a permanent problem with your touchpad.
Okay, I’ve tried it and it seems to be working after restarting my laptop.
However, I’m still not entirely sure whether this is a permanent fix or just a temporary workaround. I’ll try to update this thread if the touchpad issue comes back in the future.
Thank you very much for your help. I really appreciate it.
Both statements can be considered valid. A Grub parameter is an additional instruction for the kernel's init process, which is no different than the great many already included in the kernel.
So you can consider it a permanent fix.
Someone being pedantic, can argue that an additional parameter set by the end user is a workaround, as it works around an issue with the kernel. They cannot call it temporary, however.
I’m not sure whether this approach will actually resolve the issue or not, because at the moment my touchpad is currently detected. It’s possible that the following applies:
When this command WILL work xinput --enable "SYNA2BA6:00 06CB:CD98 Touchpad"
This command may be will work only if:
The touchpad is already detected by Xorg
The device name appears in
xinput list
The touchpad exists but is simply disabled
(for example by GNOME settings, a startup script, or a suspend/resume bug)
In this situation, xinput --enable should immediately re-enable the touchpad without any error.
When this command will FAIL
The command will fail if:
The touchpad is not detected at all by Xorg
The device does not appear inxinput list
The input driver never creates a device node
(for example due to I2C-HID issues, missing firmware, or a BIOS/UEFI problem)
A typical error message would be: unable to find device "SYNA2BA6:00 06CB:CD98 Touchpad"
This indicates that the touchpad is not just disabled — it does not exist at the X input layer.
Since Zorin OS uses GNOME by default:
xinputonly works on X11
If you are running a Wayland session, this command:
When this command WILL work
When this command will FAIL