Elantech Touchpad detects as PS/2 BYD TouchPad or as a PS/2 generic mouse

Bug #1634593 reported by Artem Flyunt on 2016-10-18
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Medium
Unassigned

Bug Description

I have an Elantech Touchpad installed on my Lenovo Y700 laptop and I can't make it work properly by any means. I tried to switch between libinput and synaptics but this bug seems to affect any driver.

Usually, after a system upgrade all works properly till the moment I plug in external mouse (Razer DeathAdder 3500DPI). After that touchpad detected as either PS/2 BYD or PS/2 generic mouse or sometimes PS/2 Elantech touchpad.

After some 5-6 reboots without plugging in external mouse the touchpad finally starts to detect it as ETPS/2 Elantech touchpad.

Reloading psmouse module seems to cause no effect (or it does yet after a minute touchpad stops working for a moment and then switches to PS/2 in xinput). Multitouch stops working as well as tapping with two fingers.

I tried almost all the possible workarounds involving adding boot options, installing elantech driver fixes etc.

Help is appreciated.

The output of xinput as for now:

$ xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ PS/2 BYD TouchPad id=14 [slave pointer (2)]

lsinput
/dev/input/event14
   bustype : BUS_I8042
   vendor : 0x2
   product : 0x1
   version : 99
   name : "PS/2 BYD TouchPad"
   phys : "isa0060/serio1/input0"
   bits ev : EV_SYN EV_KEY EV_REL

UPDATE:

Seems that forcing the psmouse to detect the touchpad as elantech helps to fix problem temporarily. But it works only from time to time:

$ sudo rmmod psmouse
$ sudo modprobe psmouse force="elantech"
---
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
InstallationDate: Installed on 2016-08-27 (52 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Package: linux (not installed)
Tags: xenial
Uname: Linux 4.6.0-040600-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
---
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: blobmasta 2054 F.... pulseaudio
CurrentDesktop: Unity:Unity7
DistroRelease: Ubuntu 17.04
InstallationDate: Installed on 2018-01-07 (3 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: LENOVO 80NV
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic.efi.signed root=UUID=e8b26b1d-8539-4186-b5d1-0b54182e3d56 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-42-generic N/A
 linux-backports-modules-4.10.0-42-generic N/A
 linux-firmware 1.164
Tags: zesty
Uname: Linux 4.10.0-42-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
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: SDK0J40688 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:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoideapadY700-15ISK:
dmi.product.name: 80NV
dmi.product.version: Lenovo ideapad Y700-15ISK
dmi.sys.vendor: LENOVO
---
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity:Unity7
DistroRelease: Ubuntu 17.04
InstallationDate: Installed on 2018-01-07 (5 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Package: linux (not installed)
Tags: zesty
Uname: Linux 4.15.0-041500rc7-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

Artem Flyunt (auggydioz) on 2016-10-18
description: updated

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1634593

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete

apport information

tags: added: apport-collected xenial
description: updated

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.9 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.9-rc1/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Artem Flyunt (auggydioz) wrote :

Sure, I'll test it ASAP

Artem Flyunt (auggydioz) wrote :

Ok, so I'm now using 4.9.0-040900rc1-generic kernel. For a hour or so I thought that everything is good but then touchpad stopped working for a moment. And then it's again detected as PS/2 BYD TouchPad according to xinput.

I added a kernel-bug-exists-upstream tag.

Changed in linux (Ubuntu):
status: Incomplete → Opinion
tags: added: kernel-bug-exists-upstream
Artem Flyunt (auggydioz) on 2016-12-06
Changed in linux (Ubuntu):
status: Opinion → Confirmed
Damien Boyd (ashfallen0) wrote :

over 1 year after last comment... behavior still exists.

ash@CASE:~$ uname -a
Linux CASE 4.13.0-21-generic #24-Ubuntu SMP Mon Dec 18 17:29:16 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
ash@CASE:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 17.10
Release: 17.10
Codename: artful

Kai-Heng Feng (kaihengfeng) wrote :

Please run `apport-collect 1634593`

apport information

tags: added: zesty
description: updated

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Artem Flyunt (auggydioz) wrote :

Here is what I was able to collect running Ubuntu from external USB HDD. The touchpad is currently working but it's a rather random issue that can appear after reboot or waking from sleep.

If you need more info please do not hesitate to request it.

Artem Flyunt (auggydioz) wrote :

And here is dmesg after I've reloaded psmouse module. Not touchpad do not work as intended (no multitouch).

Kai-Heng Feng (kaihengfeng) wrote :

Weird. The comment #7 shows it uses v4.13 but the dmesg you collected was under v4.10.

Can you try mainline kernel? Currently it's v4.15-rc7.

apport information

description: updated

apport information

apport information

Artem Flyunt (auggydioz) wrote :

As you can see from the logs above I've just booted on mainline kernel and the issue is still there. Now It's actually what it was a while ago: Elantech touchpad detects as Logitech PS/2 Mouse.

Hope that helps you.

Kai-Heng Feng (kaihengfeng) wrote :

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

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers