You are not logged in.
Hi everyone,
I’m running Arch Linux on a Lenovo ThinkPad T14 Gen 1 (Intel i5-10210U) and facing a strange issue with the Synaptics TM3471-020 touchpad under the psmouse kernel module.
The touchpad is always detected at boot.
Cursor movement and two-finger scrolling always work.
Tap-to-click and two-finger tap for right-click only work sometimes.
Reloading the driver fixes it (may take only one reload sometimes but mostly it takes multiple reloads to works ):
sudo modprobe -r psmouse && sudo modprobe psmouse
After reloading, all features (including taps) start working perfectly.
This happens intermittently on every reboot — it seems like psmouse sometimes loads the device in generic PS/2 mode instead of full Synaptics mode.
Offline
Hello,
I have the same exact laptop model with the same CPU and touchpad.
I can confirm that touchpad behaves very randomly and sometimes doesn't interpret tap-to-clicks, as well as faster finger movements which are essentially lost.
In my case, the suspend and reboot actions are essential for the touchpad to start (or stop) working correctly - it has never broken during the "awake state".
For me, reloading psmouse module also fixes the issue, but often it takes more than one reload in a row to get right.
What I had recently discovered is that in case of linux-lts kernel, reloading the i8042 module also seems to fix the issue (sometimes, like reloading psmouse).
I am yet to find a long-term, sufficient fix.
Any help would be sincerely appreciated!
Last edited by paz_dn (2025-11-16 18:05:13)
Offline
yeah the issue is pretty annoing What I Did was I Created a Shortcut for psmodule reload (keyboard shortcut) to solve this issue.
Offline
Nevertheless, I'm still eager to find out what the real cause is as I really don't have any clue.
As I mentioned earlier, the touchpad would sometimes break even straight after boot. I would then collect logs from journalctl (for current boot) as well as dmesg to compare them with logs gathered when touchpad was working after the boot.
However, I did not find any differences between the logs regarding the psmouse driver as well as anything to do with the Synaptics Touchpad (at least nothing screaming errors).
I suspect this random behaviour might happen because of some race condition while setting the device up, but I don't really know if that's really the case and if it is, then where exactly does this happen and what the remedy is.
If I find out anything relevant about this, I'll share it under this thread. Meanwhile, if somebody would like to help, I shall repeat once more that I'm looking forward to that.
Last edited by paz_dn (2025-11-19 22:34:04)
Offline
it only happens with linux ( all distros including Ubuntu which is officially supported ) but works flawlessly on Windows, may need to downgrade kernel if possible to 4.1 or less and test it out..
Offline
just hopping on to say i am experiencing this too. this post has been helpful for temporary fixes but I would really like to have it fixed permanently also. Did anyone ever make any progress on this?
Offline
I've dealt with this on two separate laptops. I'd love to investigate further and see if there's a way to root-cause this but have no idea where to begin.
Offline
has anyone tried the suggestions in section 4.1 here?
https://wiki.archlinux.org/title/Touchp … leshooting
I added the suggested kernal parameter to my grub default (psmouse.synaptics_intertouch=0) and I have not been able to get the issue to appear by
-suspending and waking
-adding a new mouse (this is what broke my temp fix initially).
I will report back if I experience it again.
Offline
just following up 1 week later: this seems to have fixed the issue permanently.
Offline