Great, but how do I make this workaround permanent? If it did not work, your system might use a different module. rmi4_f01 rmi4-02.fn01: found RMI device, manufacturer: Synaptics, product: s3203, fw id: 1522295 rmi4_f01 rmi4-01.fn01: found RMI device, manufacturer: Synaptics, product: s3203, fw id: 1522295 If this worked, your touchpad should have sprung back to life, and your dmesg output should look similar to this: To confirm this workaround fix will work on your system, wake your system up from a sleep and confirm the touchpad is non-responsive. If your system is similar to mine and has a touch screen, the i2c_hid module needs to be reloaded in order to properly enable both the touchpad and touch screen. There have been several forum posts and bug reports regarding others experiencing these exact same symptoms, so I figured I’d share a hacky workaround until the bug is fixed upstream.
It was reproduced 100% of the time, and required a complete restart in order to get the touchpad working again. Linux administration - tips, notes and projectsĪfter recently upgrading my Dell XPS 13 w/Touchscreen to Fedora 26, the touchpad suddenly stopped working upon resuming from sleep mode.
0 kommentar(er)
