https://bugzilla.suse.com/show_bug.cgi?id=1229056 https://bugzilla.suse.com/show_bug.cgi?id=1229056#c10 --- Comment #10 from Bernd Speiser <bernd.speiser@uni-tuebingen.de> --- (In reply to Takashi Iwai from comment #9)

OK, thanks.

There are quirk entries for a few Fujitsu models, and we can try them out. e.g. pass the boot options "i8042.nomux=1 i8042.notimeout=1 i8042.noaux=1" Either all or try one by one.

I tried all of the three and all of the combinations. Here are the results ( abbreviate the options in an obvious way): nomux+notimeout+noaux: touchpad unresponsive already after start-up nomux+notimeout: touchpad OK after start-up and after suspend/resume nomux+noaux: touchpad unresponsive already after start-up notimeout+noaux: touchpad unresponsive already after start-up nomux: touchpad OK after start-up and after suspend/resume notimeout: touchpad OK after start-up, but unresponsive after suspend/resume noaux: touchpad unresponsive already after start-up My conclusion is that nomux=1 is solving my problem, notimeout=1 is "neutral", but noaux=1 is breaking the touchpad altogether. -- You are receiving this mail because: You are on the CC list for the bug.