ETPS/2 Elantech Touchpad inconsistently detected (Lenovo Y700 15ISK)

[DevenPhillips]

This has been happening reliably on my Lenovo Y700 15ISK since 15.10... Sometimes it shows up as ETPS/2, sometimes PS/2, sometimes Logitech Wheelmouse... Most of the time it shows as "PS/2 Logitech Wheel Mouse" but none of the multitouch (2 finger scroll, 3 finger middle-click) can be set up. synclient says no device is present.

This is likely related to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1594214

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-19-generic 4.10.0-19.21 [modified: boot/vmlinuz-4.10.0-19-generic]
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: dphillips 1280 F.... pulseaudio
CurrentDesktop: XFCE
Date: Tue Apr 18 07:40:12 2017
InstallationDate: Installed on 2017-04-18 (0 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: LENOVO 80NV
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=8bba488a-b6df-4c29-8a90-8811c1078048 ro quiet splash i8042.kbdreset=1 vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-19-generic N/A
 linux-backports-modules-4.10.0-19-generic N/A
 linux-firmware 1.164
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/19/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: CDCN53WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Allsparks 5A
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad Y700-15ISK
dmi.modalias: dmi:bvnLENOVO:bvrCDCN53WW:bd09/19/2016:svnLENOVO:pn80NV:pvrLenovoideapadY700-15ISK:rvnLENOVO:rnAllsparks5A:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapadY700-15ISK:
dmi.product.name: 80NV
dmi.product.version: Lenovo ideapad Y700-15ISK
dmi.sys.vendor: LENOVO

[DevenPhillips (deven-phillips)]

FYI, things that I have tried:

Kernel boot params:

i8042.reset i8042.nomux=0
i8042.reset i8042.nomux=1
i8042.nomux=0
i8042.nomux=1
i8042.reset
i8042.reset i8042.nomux=0
i8042.reset i8042.nopnp
i8042.kbdreset=1
psmouse.elantech=1
psmouse.proto=bare
psmouse.proto=raw
psmouse.proto=imps

Updated the BIOS, twice.

Tried switching between legacy boot and UEFI boot.

Tried setting up module load parameters for evdev, elan_i2c, synaptic_i2c, psmouse, etc...

[DevenPhillips (deven-phillips)]

Entry as currently listed from /proc/bus/input/devices:

I: Bus=0011 Vendor=0002 Product=0001 Version=0063
N: Name="PS/2 Logitech Wheel Mouse"
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input7
U: Uniq=
H: Handlers=mouse1 event15
B: PROP=1
B: EV=7
B: KEY=70000 0 0 0 0
B: REL=3

But sometimes it shows up as "ETPS/2" or others.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc7

[DevenPhillips (deven-phillips)]

No joy... Same result

I: Bus=0011 Vendor=0002 Product=0001 Version=0063
N: Name="PS/2 Logitech Wheel Mouse"
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input9
U: Uniq=
H: Handlers=mouse1 event18
B: PROP=1
B: EV=7
B: KEY=70000 0 0 0 0
B: REL=3

[DevenPhillips (deven-phillips)]

BTW, here's the new kernel info:

Linux ideapad 4.11.0-041100rc7-generic #201704161731 SMP Sun Apr 16 21:32:58 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

[penalvch (penalvch)]

DevenPhillips, to clarify, did this issue happen prior to Ubuntu 15.10?

[DevenPhillips (deven-phillips)]

I do not believe I owned this laptop far enough back to have installed 15.10. I believe the first installation I put on it was 16.04.

Additionally, I tried the kernel boot param of "i8042.kbdreset=1". When I booted up the next time I saw the following output from xinput:

$ xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ PS/2 Elantech Touchpad id=14 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
    ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
    ↳ Power Button id=6 [slave keyboard (3)]
    ↳ Video Bus id=7 [slave keyboard (3)]
    ↳ Power Button id=8 [slave keyboard (3)]
    ↳ Sleep Button id=9 [slave keyboard (3)]
    ↳ Yubico Yubikey 4 OTP+U2F+CCID id=10 [slave keyboard (3)]
    ↳ Lenovo EasyCamera id=11 [slave keyboard (3)]
    ↳ Ideapad extra buttons id=12 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=13 [slave keyboard (3)]

But almost as soon as I started to move the pointer around the touchpad locked up (pointer stopped responding) for about 5-10 seconds and then started working again, but now the output of xinput looked like:

$ xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ PS/2 Logitech Wheel Mouse id=14 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
    ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
    ↳ Power Button id=6 [slave keyboard (3)]
    ↳ Video Bus id=7 [slave keyboard (3)]
    ↳ Power Button id=8 [slave keyboard (3)]
    ↳ Sleep Button id=9 [slave keyboard (3)]
    ↳ Yubico Yubikey 4 OTP+U2F+CCID id=10 [slave keyboard (3)]
    ↳ Lenovo EasyCamera id=11 [slave keyboard (3)]
    ↳ Ideapad extra buttons id=12 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=13 [slave keyboard (3)]

Checking out dmesg, I saw:

[ 33.327457] psmouse serio1: Touchpad at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.
[ 33.880155] psmouse serio1: resync failed, issuing reconnect request
[ 37.823561] psmouse serio1: Failed to deactivate mouse on isa0060/serio1
[ 38.259688] input: PS/2 Logitech Wheel Mouse as /devices/platform/i8042/serio1/input/input20
[ 38.381415] systemd[1]: motd-news.timer: Adding 25min 26.475299s random time.

So, as you can see, even when it does get detected as a touchpad it will not remain functional for long.

I hope this helps!

Deven

[Kai-Heng Feng (kaihengfeng)]

Please use latest mainline kernel here: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc1/

And do this:
$ sudo sh -c 'echo -n "elantech" > /sys/bus/serio/devices/serio1/protocol'

Hopefully it'll work.

[DevenPhillips (deven-phillips)]

@kaihengfeng - This has certainly improved the situation. The "resync failed, issuing reconnect request" issue has gone away. Multitouch is still not working though. I will try reconfiguring the X server settings to see if I can get it to detect as a multi-touch capable device.

Thanks!!

[DevenPhillips (deven-phillips)]

Does anyone know which input driver should be used with the elantech? synaptics/evdev/libinput?

[Kai-Heng Feng (kaihengfeng)]

For userspace driver, you probably need to ask it on <email address hidden>.

In the meantime, I'll work on a udev solution to make sure it uses elantech protocol.

[Kai-Heng Feng (kaihengfeng)]

I suppose you use Zesty? Please try udev packages here:
http://people.canonical.com/~khfeng/lp1683760/

[DevenPhillips (deven-phillips)]

This is still an ongoing issue even after upgrading to Artful and latest kernel releases. The kernel still intermittently detects the mouse differently. Even when it DOES detect it as an ETPS/2 Touchpad, using the device caused the cursor to jump around and click without pressing to click.

[Kai-Heng Feng (kaihengfeng)]

Does
$ sudo sh -c 'echo -n "elantech" > /sys/bus/serio/devices/serio1/protocol'
still work for you?

[DevenPhillips (deven-phillips)]

Not reliably. Sometimes it will fix things when they go wrong, but not more than about 60%.

[Kai-Heng Feng (kaihengfeng)]

Sounds like you run the command after the touchpad doesn't work.

What if you run the command right after boot?