Hmmm… can you try running
sudo rmmod i2c_i801 ; sudo modprobe i2c_i801 and see what you get in
dmesg -w (on the system where the touchpad does not work)?
Hmmm… can you try running
[ 474.793614] i801_smbus 0000:00:1f.4: SPD Write Disable is set [ 474.793722] i801_smbus 0000:00:1f.4: SMBus using PCI interrupt [ 474.793956] iTCO_wdt: Found a Intel PCH TCO device (Version=6, TCOBASE=0x0400) [ 474.794417] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [ 474.797718] i2c i2c-2: 2/2 memory slots populated (from DMI) [ 474.999296] i801_smbus 0000:00:1f.4: Timeout waiting for interrupt! [ 474.999303] i801_smbus 0000:00:1f.4: Transaction timeout [ 475.001661] i801_smbus 0000:00:1f.4: Failed terminating the transaction [ 475.001751] i801_smbus 0000:00:1f.4: SMBus is busy, can't use it!
I executed the commands, and these are, I guess, the related lines. in dmesg. So they are indeed connected right?
I’m not sure, possibly not. On the system where the touchpad works, can you run
ls -l /sys/bus/acpi/devices/SYNA8004:00/physical_node/?
I will, first thing tomorrow. Thanks for all the help so far. I think I understand the problem way better for now. Unfortunately, it is already quite late here. Thanks, so far. I will report tomorrow.
Hi, so the output for the acpi device on the running system looks as follows:
ls -l /sys/bus/acpi/devices/SYNA8004\:00/physical_node/ total 0 drwxr-xr-x 5 root root 0 Aug 31 07:30 0018:06CB:CD8B.0001 lrwxrwxrwx 1 root root 0 Aug 31 07:30 driver -> ../../../../../../bus/i2c/drivers/i2c_hid lrwxrwxrwx 1 root root 0 Aug 31 07:31 firmware_node -> ../../../../../LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:7a/SYNA8004:00 -r--r--r-- 1 root root 4096 Aug 31 07:31 modalias -r--r--r-- 1 root root 4096 Aug 31 07:30 name drwxr-xr-x 2 root root 0 Aug 31 07:31 power lrwxrwxrwx 1 root root 0 Aug 31 07:30 subsystem -> ../../../../../../bus/i2c -rw-r--r-- 1 root root 4096 Aug 31 07:30 uevent
That looks all good. Is there a way to determine if this is related to an update in the kernel? Because, if we need hours to figure it out it might be faster to just install a new Manjaro for me. Unless, the same problem persists as soon as I update to a newer kernel.
I tried now also going back to kernel version
5.4.60-2-MANJARO. The errors related to the smbus in dmesg are gone here, but the touchpad does not work either. And the output for the ACPI device looks the same.
I don’t understand what goes wrong here. Is there anything that I could have changed in my config, to make this problem to appear? I went through the kernel logs between 5.7.9 and 5.7.15 and found both in 5.7.10 and 5.7.11 some changes to the i2c touchpad modules. But I am not sure, if any of these are causing the problem.
That looks all good. Is there a way to determine if this is related to an update in the kernel?
Possibly the simplest way to determine if it is related to the kernel is to simply reinstall Manjaro, and if the touchpad works, update the kernel right away and see if it stays functioning.
I went through the kernel logs between 5.7.9 and 5.7.15 and found both in 5.7.10 and 5.7.11 some changes to the i2c touchpad modules. But I am not sure, if any of these are causing the problem.
I did that as well, but I couldn’t see anything that might cause your problem.
Is there anything that I could have changed in my config, to make this problem to appear?
I’m tempted to say it’s a kernel problem, but I’m not sure. If you have a certainly working, and a certainly not working kernel, then you could git-bisect it to find the commit that caused the problem.
Thanks. If I sort out my backups etc. I will try to install a fresh manjaro tomorrow or so. Unfortunately I need the device for work, and a broken touchpad is better than a broken machine… Maybe I create a separate partition and try it there.
I found this long thread here: bugs.launchpad. net/ubuntu/+source/linux/+bug/1861610 . And I have the feeling it is related. But I can’t get the solution there to work.
Thanks for all the help! I will keep you updated.
The solution there involves modifying ACPI tables, but if the touchpad has worked before, and the ACPI tables haven’t been modified (by means of BIOS/firmware update, etc.), then it is a regression in the kernel.
I see. The problem is, that I (will never do that again) did the
pamac update and fwupdmgr updates in one row, without a restart. Never ever again, but everything was working so smoothly the last months, that I got sloppy.
Anyway, since it works in the live system, who knows what went wrong… I will give it a try and install it. Update to the same kernel and see what happens.
I’m thinking kernel regression, but we will see.
so I finally found the time to try the same kernel with a fresh instal with the latest
5.8.6-1-MANJARO kernel on both systems. And it works on the freshly installed system So it must be some configuration problem. No idea… Maybe I will just reinstall then. Any ideas welcome, but I guess, figuring this out will take much more time than a simple reinstall.
I have been having a similar issue
stable, on kernel 5.8.6, worked
but after switching to testing branch the touchpad it is no longer detected upon reboot, mouse works fine
(using HP ENVY x360 13-ay0021nr, kde manjaro)
[it does work on stable when I switch back to it, so it seems it’s just testing]
Please install and run
evtest, and check if it shows your touchpad. If yes, please select it, and check if it shows anything when you move your finger on the touchpad.
I finally took the time to reinstall my Manjaro. I am now running 5.8.6 as before, installed all my packages, and did my adjustments to the configuration. Everything works perfectly, including the touchpad! I have no idea why it was broken, but it works in a fresh installation. Maybe some config that became incompatible over time. For now I am happy Thanks again @pobrn for all your help!
I recently run into the same issue on a Razer Blade. Downgrading to kernel 5.6 worked for me, but weirdly upgrading to 5.9.0 also solved the issue. I have no idea what got broken in the 5.8.
Also @pobrn I tried running
evtest but I did not find the touchpad there.
Thank you guys here for sharing, I have same problem like @the-hampel. No touch pad setting, neither in sudo evtest. Then I calm down, reboot, check again. It still don’t work, but appear in sudo evtest again. In touchpad and mouse setting, It don’t appear, reboot again more, nothing change. Then I press Fn-F7 to turn it on, and tada! It worked. I think you should reboot, and try to do st, you will get lucky like me!