Asus UX31 Elantech Mouse does not register as a touchpad

[jason.sidabras]

This bug is different than the Ubuntu Bug #894515
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/894515

No other elantech bug on a google search, or the fixes work.

In this case, the Elantech driver does not initialise the registers and only registers as a PS/2 mouse. None of the settings for gpointer-device-settings change the mouse characteristics, along with the default mouse settings.

Linux Mint 12

 $ uname -a
Linux tweedledum 3.0.0-12-generic #20-Ubuntu SMP Fri Oct 7 14:56:25 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

$ dmesg | grep lantech
[ 5.469959] elantech: assuming hardware version 3, firmware version 54.31.0
[ 5.500156] elantech: Synaptics capabilities query result 0x20, 0x15, 0x0e.
[ 5.635361] elantech: failed to initialise registers.
[ 5.635365] elantech: failed to put touchpad into absolute mode.
[ 6.110228] input: PS/2 Elantech Touchpad as /devices/platform/i8042/serio4/input/input9

$ cat /proc/bus/input/devices
I: Bus=0011 Vendor=0002 Product=0001 Version=0000
N: Name="PS/2 Elantech Touchpad"
P: Phys=isa0060/serio4/input0
S: Sysfs=/devices/platform/i8042/serio4/input/input9
U: Uniq=
H: Handlers=mouse0 event9
B: PROP=0
B: EV=7
B: KEY=70000 0 0 0 0
B: REL=3

I have modified /usr/share/X11/xorg.conf.d/10-evdev and and 50-synaptics.conf the same (different identifier). Neither of these changes modified my mouse behavior.

Section "InputClass"
        Identifier "evdev touchpad catchall"
        MatchIsTouchpad "on"
        MatchDevicePath "/dev/input/event*"
        Driver "synaptics"
        MatchIsTouchpad "on"
# This option is recommend on all Linux systems using evdev, but cannot be
# enabled by default. See the following link for details:
# http://who-t.blogspot.com/2010/11/how-to-ignore-configuration-errors.html
      MatchDevicePath "/dev/input/event*"
        Option "EmulateTwoFingerMinZ" "40"
        Option "PalmDetect" "true"
        Option "EmulateTwoFingerMinW" "8"
        Option "VertTwoFingerScroll" "on"
        Option "EmulateTwoFingerMinZ" "40"
        Option "EmulateTwoFingerMinW" "8"
        Option "VertTwoFingerScroll" "on"
EndSection

Finally synclient doesn't register that any synaptics driver is loaded
$ synclient
Couldn't find synaptics properties. No synaptics driver loaded?

[Philipp Wolfer (phw)]

Same here with on a Gigabyte U2442 with Elantech touchpad. It only gets registered as a PS/2 mouse without touchpad functionality. Although this could be a duplicate of Ubuntu Bug #894515, don't you think? There the touchpad also only registers as a PS/2, and the synaptics driver does not get loaded.

There seems to be a fix there (updated Kernel http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-rc7-quantal/)

[Philipp Wolfer (phw)]

My log output for the deiver initialization:

[ 11.695029] psmouse serio1: elantech: assuming hardware version 3 (with firmw
are version 0x450f01)
[ 11.738165] psmouse serio1: elantech: Synaptics capabilities query result 0x5
8, 0x17, 0x0c.
[ 11.973341] psmouse serio1: elantech: retrying ps2 command 0x0b (2).
[ 12.114669] HDMI status: Codec=3 Pin=6 Presence_Detect=0 ELD_Valid=0
[ 12.114724] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input8
[ 12.114798] input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
[ 12.114851] input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
[ 12.676396] psmouse serio1: elantech: retrying ps2 command 0x0b (1).
[ 13.379497] psmouse serio1: elantech: retrying ps2 command 0x0b (0).
[ 13.882867] psmouse serio1: elantech: ps2 command 0x0b failed.
[ 13.882874] psmouse serio1: elantech: failed to write register 0x10 with value 0x0b.
[ 13.882878] psmouse serio1: elantech: failed to initialise registers.
[ 13.882881] psmouse serio1: elantech: failed to put touchpad into absolute mode.
[ 14.114783] input: PS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input11

[Narcis Garcia (narcisgarcia)]

Here you may find a solution:
http://ubuntuforums.org/showthread.php?t=2147324

[Matthew Grimes (matthew-koichi-grimes)]

Same here with Ubuntu 13.04 and a Gigabyte u2442f with an elantech built-in touchpad. The touchpad and keyboard work fine (unlike in some of the forum URLs above), but the touchpad is treated as a mouse. By this I mean that the "mouse and touchpad" control panel doesn't show any touchpad-specific preferences, such as the "disable while typing" checkbox shown here:

http://www.omgubuntu.co.uk/2013/02/ubuntu-13-04-gains-improved-mouse-touchpad-settings

Here are the relevant dmesg lines:

$ dmesg | grep lantech
[ 12.558944] psmouse serio1: elantech: assuming hardware version 3 (with firmware version 0x450f01)
[ 12.585257] psmouse serio1: elantech: Synaptics capabilities query result 0x58, 0x17, 0x0c.
[ 12.830571] psmouse serio1: elantech: retrying ps2 command 0x0b (2).
[ 13.533665] psmouse serio1: elantech: retrying ps2 command 0x0b (1).
[ 14.236750] psmouse serio1: elantech: retrying ps2 command 0x0b (0).
[ 14.740104] psmouse serio1: elantech: ps2 command 0x0b failed.
[ 14.740110] psmouse serio1: elantech: failed to write register 0x10 with value 0x0b.
[ 14.740113] psmouse serio1: elantech: failed to initialise registers.
[ 14.740115] psmouse serio1: elantech: failed to put touchpad into absolute mode.
[ 14.999977] input: PS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input12
[43478.797090] psmouse serio1: elantech: assuming hardware version 3 (with firmware version 0x450f01)
[43478.820272] psmouse serio1: elantech: Synaptics capabilities query result 0x58, 0x17, 0x0c.
[43479.055297] psmouse serio1: elantech: retrying ps2 command 0x0b (2).
[43479.758392] psmouse serio1: elantech: retrying ps2 command 0x0b (1).
[43480.461480] psmouse serio1: elantech: retrying ps2 command 0x0b (0).
[43480.964819] psmouse serio1: elantech: ps2 command 0x0b failed.
[43480.964821] psmouse serio1: elantech: failed to write register 0x10 with value 0x0b.
[43480.964822] psmouse serio1: elantech: failed to initialise registers.
[43480.964823] psmouse serio1: elantech: failed to put touchpad into absolute mode.
[43481.218451] input: PS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input13
[71825.775321] psmouse serio1: elantech: assuming hardware version 3 (with firmware version 0x450f01)
[71825.799008] psmouse serio1: elantech: Synaptics capabilities query result 0x58, 0x17, 0x0c.
[71826.033658] psmouse serio1: elantech: retrying ps2 command 0x0b (2).
[71826.736752] psmouse serio1: elantech: retrying ps2 command 0x0b (1).
[71827.439842] psmouse serio1: elantech: retrying ps2 command 0x0b (0).
[71827.943178] psmouse serio1: elantech: ps2 command 0x0b failed.
[71827.943191] psmouse serio1: elantech: failed to write register 0x10 with value 0x0b.
[71827.943192] psmouse serio1: elantech: failed to initialise registers.
[71827.943193] psmouse serio1: elantech: failed to put touchpad into absolute mode.
[71828.151634] input: PS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input14
[77490.198056] psmouse serio1: elantech: assuming hardware version 3 (with firmware version 0x450f01)
[77490.221746] psmouse serio1: elantech: Synaptics capabilities query result 0x58, 0x17, 0x0c.
[77490.453375] psmouse serio1: elant...

[Dave Lane (lightweight)]

Same problem - thought I'd found the fix here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1166442/comments/62 but I'm still experiencing the problem with the most recent (supposedly fixed) kernels on Linux Mint 15 (64bit) - with kernel 3.8.0-30-generic (as well as 31 and 32, from raring proposed). I've got a Gigabyte U2442V.

[Martin Pitak (mous-imp)]

I have the same problem with Gigabyte U2442V and i tried psmouse elantech v7 patch and updating to new kernel 3.11.6 but with no success.

[Moritz (moritzteuber)]

same problem here with a gigabyte u2442n. thought it was related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1166442 but the fix seems only to work for newer hardware versions of elantech pads. I'm updated to 13.10, but nothing changed.

[Moritz (moritzteuber)]

also i tried all "workarounds" in the bug report mentioned above, none of them worked