I have the SYNA 3602 touchpad (Vaio FE14, notebook), that is known for have some issues with linux kernel. However, It’s getting better after every new update of kernel (I’m using the kernel 5.16.5-200.fc35).
Anyway, the touchpad don’t work after suspension of the computer, even if I restart the module with sudo modprobe -r i2c_hid_acpi && sudo modprobe i2c_hid_acpi, and doesn’t matter how many times I do, it doesn’t works. By the way, even though it don’t work after suspension the system recognizes it by sudo libinput list-devices but not with cat /proc/bus/input/devices.
I already saw some shell scripts and workarounds for manjaro-linux that does the same as the commands
The touchpad works after every shuting down completely the system, but not with reboot. And, if the touchpad don’t work in the initialization - sometimes happen -, I restart the modules one time and it works properly. If I suspend or reboot it won’t work.
Any help, I will be grateful
I’m not sure, but maybe you also want to check with xinput. On terminal type xinput and enter, then find the id=x of your touchpad, let say it’s id=15 [slave piointer (x)] then try with xinput --disable 15 then enable again with xinput --enable 15.
Sorry, I guess I’m quite late for the party. Did you already solve that problem? If not, does the touchpad get recognized after your pc got suspended? (Yes, I read that it got “partly” recognized, but since you asked that question quite a while ago, I think it could be different by now)
It’s a problem with the linux kernel, and, more precisely, the acpi module. I have problems with the suspension either, besides this touchpad issue. But yes, the system recognizes it in the /proc/bus/input/devices and in libinput list-devices. but only this, it’s just recognizable. In rare events, like 1 in 100, in kernel 5.16 and 5.17, it work after a suspension.
And If I understand your problem correctly, after a suspension your system goes for a reboot. Is that so?
I do not know a solution for the touchpad issue, but you can try restarting the module sudo modprobe -r i2c-hid-acpi && sudo modprobe i2c-hid-acpi. If this make the touchpad work, you can try a workaround, look for some tutorials.
I faced a similar problem (with suspension itself) in my notebook and I had to make some changes. First, uncomment (deleting the # before the content) the lines AllowSuspend=yes and SuspendState… (Did you faced any problems with suspension by closing the lid? See this page: SystemdSuspendSedation - Debian Wiki)
Second, try add the resume module by using dracut: sudo dracut -vf -a resume and see if it works. If positive, echo 'add_dracutmodules+="resume"' > /etc/dracut.conf.d/99-fix-resume.conf && sudo dracut -vf to make the resume module permanent.
I have same exact problem of egassem. I am able to suspend once. After resuming suspension, touchpad stops working and I’m unable to suspend again. When I try to suspend one more time, screen goes black for half a second, then it returns to unlock screen (it does not log me off). Same problem with hybernation.
Quick update on this suspen issue that we are facing. I updated to fedora 36, using at this time kernel 5.17.5-300 and it is working flawless. I hadn’t one single problem with suspension since I rebooted the notebook after the installation.
I’ve noted some changes in the grub file, were added this parameters: GRUB_CMDLINE_LINUX=“resume=UUID=71a3f20c-3eca-4d69-b172-ae3b2700fa60 rhgb quiet”
that weren’t in my fedora 35.
The touchpad still not working even if i restart the modules