Revive a dead Synaptics touchpad after a kernel upgrade
The problem and the core fix are confirmed straight from cited omarchy issue 5991, which contains the same kernel hint string, the same /etc/modprobe.d/psmouse.conf content, the same modprobe -r/modprobe reload, and the same before/after device naming (SynPS/2 Synaptics TouchPad -> Synaptics TM3114-001 on rmi4). The defect is the trailing step: sudo mkinitcpio -P is presented as what makes the setting survive kernel upgrades, and that rationale is simply false. A modprobe.d file is read at module load from the root filesystem and persists on its own, and psmouse is not in the initramfs. Users who see no change after the reload will now also sit through an initramfs rebuild for nothing, and the record never tells them what to check.
Unloading psmouse also disconnects a PS/2 keyboard on some laptops. Have a USB keyboard/mouse to hand, or just reboot instead of using modprobe -r.
Symptom
Touchpad is detected but completely non-functional after a kernel upgrade. The cursor never moves. libinput list-devices shows it as SynPS/2 Synaptics TouchPad. The kernel log contains: Your touchpad says it can support a different bus. If i2c-hid and hid-rmi are not used, you might want to try setting psmouse.synaptics_intertouch to 1.
Cause
The touchpad supports the RMI4/SMBus ("InterTouch") interface but the kernel bound it to the legacy PS/2 protocol instead, which on these panels yields a non-functional device. Reported on Omarchy with a Synaptics TM3114-001 (SYN3228/SYN1e00) after a kernel bump.
Fix
# /etc/modprobe.d/psmouse.conf
options psmouse synaptics_intertouch=1
Apply it without rebooting:
sudo modprobe -r psmouse && sudo modprobe psmouse
This already persists across kernel upgrades. Do NOT run mkinitcpio -P for it. psmouse is not in the initramfs, so regenerating it changes nothing here.
Verify it took:
cat /sys/module/psmouse/parameters/synaptics_intertouch # should print Y
sudo dmesg | grep -i -E 'psmouse|synaptics|rmi4'
sudo libinput list-devices | grep -A3 -i touchpad
The device should now be reported as the real model name (e.g. Synaptics TM3114-001) driven by rmi4 rather than SynPS/2 Synaptics TouchPad. If it does not come up, confirm the SMBus driver loaded (lsmod | grep rmi) and reboot once, because some controllers only re-bind to RMI4 on a cold probe.
Verify
sudo libinput list-devices shows the touchpad under its real model name, and sudo libinput debug-events emits motion events as you move a finger.