[Fujitsu CELSIUS H730] Touchpad doesn't work unless middle-click is constantly pressed on an Elantech touchpad

[Thor K. H.]

Issue: Using a fresh install of Ubuntu 14.10, I discovered that the touchpad did not work.

Steps to reproduce: Install Ubuntu 14.10 on a Fujitsu H730 and attempt to use the touchpad.

Further description: Due to the comments in bug #1300427 I've tested the mainline kernel version 3.17-rc5-utopic, and the only impact I recall was how the right-click button now also worked while pressing middle-click on the touchpad.

WORKAROUND: Remove and load psmouse with proto=exps.

After this, a bit further in time, I accidentally managed to click with the touchpad. It appears that the touchpad strangely enough works quite well as long as I hold down the middle click button. While holding it down, the touchpad seems to work rather well - including multitouch features. The joy is short, as it registers no input while depressed.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-35-generic 3.13.0-35.62
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: thor 2091 F.... pulseaudio
 /dev/snd/controlC1: thor 2091 F.... pulseaudio
CurrentDesktop: Unity
Date: Fri Sep 19 22:27:54 2014
HibernationDevice: RESUME=UUID=a9ec5239-5c4f-474d-8d18-3c1e6883ebd7
InstallationDate: Installed on 2014-09-16 (3 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: FUJITSU CELSIUS H730
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=6cc36406-9a9c-43d3-bd8f-5de598bcd141 ro quiet splash i8042.nopnp
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-35-generic N/A
 linux-backports-modules-3.13.0-35-generic N/A
 linux-firmware 1.127.6
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/01/2014
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.07
dmi.board.name: FJNB274
dmi.board.vendor: FUJITSU
dmi.board.version: H3
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.chassis.version: CELSIUS H730
dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.07:bd05/01/2014:svnFUJITSU:pnCELSIUSH730:pvr10601583197:rvnFUJITSU:rnFJNB274:rvrH3:cvnFUJITSU:ct10:cvrCELSIUSH730:
dmi.product.name: CELSIUS H730
dmi.product.version: 10601583197
dmi.sys.vendor: FUJITSU

[Brad Figg (brad-figg)]

This change was made by a bot.

[Thor K. H. (nitrolinken)]

Hi Christopher, and thanks for the instructions for updating the BIOS - although not fruitful, the thought was appreciated.

With a Windows To Go installation I was able to update to v1.09 without any dual-booting or similarly.
Not surprisingly, dmidecode returns the expected data: "Version 1.09" and "07/30/2014".

Per your request, I've marked it as conf

[Thor K. H. (nitrolinken)]

Thanks to the magic of the touchpad in proto=exps mode, I accidentally posted the comment prematurely.

"Per your request, I've marked it as confirmed and I'm looking forward to anything else I can help with to provide further detail."

[penalvch (penalvch)]

Thor K. H., could you please reverse your WORKAROUND and test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-rc6-utopic/ and advise to the results?

[Thor K. H. (nitrolinken)]

Christopher, thanks for your follow-up.

I've installed the linux-image for v3.17-rc6-utopic (Linux thor-lincoln-library 3.17.0-031700rc6-generic #201409211935 SMP Sun Sep 21 23:37:11 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux), and removed my workaround before rebooting the system.

However, the symptoms are unchanged and identical (to the best of my current experience).

If possible, please advise any furthe debugging that can be done whilst on the mainline kernel, otherwise I'll go back to the stable kernel (due to easier use with Virtualbox).

[penalvch (penalvch)]

Thor K. H., the issue you are reporting is an upstream one. Could you please report this problem through the appropriate channel by following the instructions _verbatim_ at https://wiki.ubuntu.com/Bugs/Upstream/kernel ?

Please provide a direct URL to your e-mail to the mailing list once you have made it so that it may be tracked.

Thank you for your understanding.

[Thor K. H. (nitrolinken)]

Thanks for your follow-up, Christopher.

I've sent off a mail to the list that I hope conforms with the requirements, per your link.

Here's a link to an archived version (spinics seems slow): http://thread.gmane.org/gmane.linux.kernel.input/38326