Touchpad isn't recognized after clean Ubuntu 13.10 install on Fujitsu U574 laptop. Running 'cat /proc/bus/input/devices' shows:
Name="ImPS/2 Generic Wheel Mouse"
Added GRUB params as per bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1244634:
To /etc/default/grub, add to GRUB_CMDLINE_LINUX_DEFAULT:
sudo update-grub && sudo reboot
This solves the issue, touchpad now works after reboot and after suspend.
Ubuntu 13.10 x86_64
Kernel: linux-image-3.11.0-15-generic 3.11.0-15.23
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.21
dmi.product.name: LIFEBOOK U574
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-15-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash i8042.notimeout i8042.nomux vt.handoff=7
I do not believe there is 'notimout' option...
(In reply to Dmitry Torokhov from comment #1)
> I do not believe there is 'notimout' option...
Yes there is: http://lxr.free-electrons.com/source/drivers/input/serio/i8042.c#L66
Thanks for the bug report. This means we need to add a quirk for your model laptop to the kernel.
Do you really need both options? Have you tried with just nomux or just notimout ?
We could check here
if the mux specification version is 1.1 or 1.0.
That way we could eliminate many false positives.
The last version of the mux spec was written in 1999 so it is a safe bet that no hardware will report any other version.
Haiku does that (didn't read the code, just saw something suggesting it in Google Search results for "ps2 multiplexing specification").
Could You provide a dmesg?
(In reply to Mateusz Jończyk from comment #6)
> Could You provide a dmesg?
There is a dmesg in the ubuntu bug, but it has nomux=1 on the commandline.
Can you please provide the output of "dmesg" directly after boot when booted without the nomux option. Also can you please answer my question from comment #3 ?
OK, I have searched in Google for
"Detected active multiplexing controller, rev site:bugzilla.kernel.org"
and do not find any reports of reported mux versions other then 1.1 and 1.0.
This modification as I proposed may be useful, though.
I'm extremely sorry for replying slowly.
Anyway, adding dmesg without either nomux or notimeout and then *with* i8042.notimeout.
in the first case (vanilla setup), touchpad doesn't work. In the second case touchpad works. So it seems there is no need for 'nomux'.
Created attachment 149021 [details]
dmesg without either option
Created attachment 149031 [details]
dmesg with notimeout
Created attachment 149041 [details]
[PATCH] i8042: Add Fujitsu U574 to no_timeout dmi table
Thanks for the testing. Any chance you could build a kernel with the attached patch, and then see if things work without specifying anything on the kernel commandline ?
No worries if you cannot do so, then I'll just send the patch upstream as is, as it basically should work fine.
Jason, any dmesg without i8042.debug=1 is basically useless to us.
Could You send us patches with this option?
Created attachment 149121 [details]
dmesg without notimeout with debug
Created attachment 149131 [details]
dmesg with notimeout with debug
(In reply to Mateusz Jończyk from comment #13)
> Jason, any dmesg without i8042.debug=1 is basically useless to us.
> Could You send us patches with this option?
(In reply to Hans de Goede from comment #12)
> Thanks for the testing. Any chance you could build a kernel with the
> attached patch, and then see if things work without specifying anything on
> the kernel commandline ?
I'll try to free some time to do that this week if possible. Thanks for working on the patch!
Would it make sense to ignore the timeout bit all the time, on all devices?
We are usually quite quick to read the data from 8042.
(In reply to Mateusz Jończyk from comment #17)
> Would it make sense to ignore the timeout bit all the time, on all devices?
> We are usually quite quick to read the data from 8042.
I'm not familiar enough with i8042 code to answer that I'm afraid.
Fujitsu Lifebook AH544 also have this problem =(
notimeout is needed
(In reply to Andrey from comment #19)
> Fujitsu Lifebook AH544 also have this problem =(
> notimeout is needed
So we will need a quirk for that model too, can you please do:
sudo dmidecode > dmi.log
And attach the generated dmi.log file here ?
Created attachment 154601 [details]
dmi log for LIFEBOOK AH544
Product Name: LIFEBOOK AH544
Created attachment 154771 [details]
[PATCH] i8042: Add notimeout quirk for Fujitsu Lifebook A544 and Lifebook AH544
(In reply to SPROg from comment #21)
> Created attachment 154601 [details]
> dmi log for LIFEBOOK AH544
> Manufacturer: FUJITSU
> Product Name: LIFEBOOK AH544
Thanks, I've send the patch which I've just attached upstream, this should make future kernels automatically do the right thing.