Touchpad not recognized on Lenovo Ideapad Flex 4 running Ubuntu 16.10

Bug #1658345 reported by Keary Parinis
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

I installed Ubuntu 16.10 on my Lenovo Ideapad Flex 4 laptop. Ubuntu does not recognize the touchpad (it does recognize the touch screen nicely though). When I run xinput -list, I do not see the touchpad. I dual boot with Windows 10, which recognizes the touchpad from Elantech. I searched online for days and I found Elantech drivers for Ubuntu 14.04, however, I was unable to load older versions of Ubuntu on my laptop. Do you expect to support the Elantech touchpad in future updates? I attached a screen shot of my xinput -list output. Please let me know if you require any additional information. Thank you.
---
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: keary 2345 F.... pulseaudio
DistroRelease: Ubuntu 16.10
HibernationDevice: RESUME=UUID=dbfec3b4-a8be-406e-9f39-5258c004c656
InstallationDate: Installed on 2017-01-18 (2 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0bda:57fc Realtek Semiconductor Corp.
 Bus 001 Device 002: ID 0cf3:e500 Atheros Communications, Inc.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80U3
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic.efi.signed root=UUID=5be7438e-36fd-4960-a4cd-2371715adfa2 ro quiet splash i8042.kbdreset=1 vt.handoff=7
ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-34-generic N/A
 linux-backports-modules-4.8.0-34-generic N/A
 linux-firmware 1.161.1
Tags: yakkety
Uname: Linux 4.8.0-34-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 11/01/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: 2MCN24WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Sofia-F
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J91204WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad FLEX 4-1130
dmi.modalias: dmi:bvnLENOVO:bvr2MCN24WW:bd11/01/2016:svnLENOVO:pn80U3:pvrLenovoideapadFLEX4-1130:rvnLENOVO:rnSofia-F:rvrSDK0J91204WIN:cvnLENOVO:ct10:cvrLenovoideapadFLEX4-1130:
dmi.product.name: 80U3
dmi.product.version: Lenovo ideapad FLEX 4-1130
dmi.sys.vendor: LENOVO
---
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
DistroRelease: Ubuntu 17.04
InstallationDate: Installed on 2017-01-18 (181 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Tags: zesty
Uname: Linux 4.13.0-041300rc1-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: Upgraded to zesty on 2017-05-07 (73 days ago)
UserGroups:

_MarkForUpload: True
---
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
DistroRelease: Ubuntu 17.04
InstallationDate: Installed on 2017-01-18 (208 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Tags: zesty
Uname: Linux 4.13.0-rc5-elan0602 x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: Upgraded to zesty on 2017-05-07 (100 days ago)
UserGroups:

_MarkForUpload: True

Revision history for this message
Keary Parinis (kparinis) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

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

apport-collect 1658345

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
Revision history for this message
Keary Parinis (kparinis) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected yakkety
description: updated
Revision history for this message
Keary Parinis (kparinis) wrote : CRDA.txt

apport information

Revision history for this message
Keary Parinis (kparinis) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Keary Parinis (kparinis) wrote : IwConfig.txt

apport information

Revision history for this message
Keary Parinis (kparinis) wrote : JournalErrors.txt

apport information

Revision history for this message
Keary Parinis (kparinis) wrote : Lspci.txt

apport information

Revision history for this message
Keary Parinis (kparinis) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Keary Parinis (kparinis) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Keary Parinis (kparinis) wrote : ProcModules.txt

apport information

Revision history for this message
Keary Parinis (kparinis) wrote : RfKill.txt

apport information

Revision history for this message
Keary Parinis (kparinis) wrote : UdevDb.txt

apport information

Revision history for this message
Keary Parinis (kparinis) wrote : WifiSyslog.txt

apport information

Revision history for this message
Keary Parinis (kparinis) wrote : Re: [Bug 1658345] Missing required logs.

Helllo Brad. I ran the command that you provided and posted the log file.
Please let me know if this is sufficient. Thanks.

On Sat, Jan 21, 2017 at 1:00 PM, Brad Figg <email address hidden> wrote:

> This bug is missing log files that will aid in diagnosing the problem.
> >From a terminal window please run:
>
> apport-collect 1658345
>
> 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
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1658345
>
> Title:
> Touchpad not recognized on Lenovo Ideapad Flex 4 running Ubuntu 16.10
>
> Status in linux package in Ubuntu:
> Incomplete
>
> Bug description:
> I installed Ubuntu 16.10 on my Lenovo Ideapad Flex 4 laptop. Ubuntu
> does not recognize the touchpad (it does recognize the touch screen
> nicely though). When I run xinput -list, I do not see the touchpad. I
> dual boot with Windows 10, which recognizes the touchpad from
> Elantech. I searched online for days and I found Elantech drivers for
> Ubuntu 14.04, however, I was unable to load older versions of Ubuntu
> on my laptop. Do you expect to support the Elantech touchpad in future
> updates? I attached a screen shot of my xinput -list output. Please
> let me know if you require any additional information. Thank you.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1658345/+subscriptions
>

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

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

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Keary Parinis (kparinis) wrote : Re: [Bug 1658345] Re: Touchpad not recognized on Lenovo Ideapad Flex 4 running Ubuntu 16.10
Download full text (4.5 KiB)

I was never able to get Ubuntu to recognize the touchpad. This is a new
laptop. Last week, I tried the latest upstream version 17.10 with the same
result. Is there a new version this week?

On Monday, January 23, 2017, Joseph Salisbury <
<email address hidden>> wrote:

> Did this issue start happening after an update/upgrade? Was there a
> prior kernel version where you were not having this particular problem?
>
> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v4.10 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.10-rc5
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1658345
>
> Title:
> Touchpad not recognized on Lenovo Ideapad Flex 4 running Ubuntu 16.10
>
> Status in linux package in Ubuntu:
> Incomplete
>
> Bug description:
> I installed Ubuntu 16.10 on my Lenovo Ideapad Flex 4 laptop. Ubuntu does
> not recognize the touchpad (it does recognize the touch screen nicely
> though). When I run xinput -list, I do not see the touchpad. I dual boot
> with Windows 10, which recognizes the touchpad from Elantech. I searched
> online for days and I found Elantech drivers for Ubuntu 14.04, however, I
> was unable to load older versions of Ubuntu on my laptop. Do you expect to
> support the Elantech touchpad in future updates? I attached a screen shot
> of my xinput -list output. Please let me know if you require any additional
> information. Thank you.
> ---
> ApportVersion: 2.20.3-0ubuntu8.2
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: keary 2345 F.... pulseaudio
> DistroRelease: Ubuntu 16.10
> HibernationDevice: RESUME=UUID=dbfec3b4-a8be-406e-9f39-5258c004c656
> InstallationDate: Installed on 2017-01-18 (2 days ago)
> InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64
> (20161012.2)
> Lsusb:
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 001 Device 003: ID 0bda:57fc Realtek Semiconductor Corp.
> Bus 001 Device 002: ID 0cf3:e500 Atheros Communications, Inc.
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> MachineType: LENOVO 80U3
> Package: linux (not installed)
> ProcEnviron:
> LANGUAGE=en_US
> TERM=xterm-256color
> PATH=(custom, no user)
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic.efi.signed
> root=UUID=5be7438e-36fd-4960-a4cd-2371715adfa2 ro quiet splash
> i8042.kbdreset=1 vt.handoff=7
> ProcVersionSignature: Ubuntu 4.8.0-34....

Read more...

Revision history for this message
Keary Parinis (kparinis) wrote :

I tested my laptop with the upstream kernel 4.10 and it does not recognize my touchpad. Please see attached screen shot I captured during the install. It indicates an error with the Elantech ps mouse / touchpad device.

tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Keary Parinis (kparinis) wrote :

Hi. Just following up to see if there are any new touchpad drivers that may help. Thanks.

Revision history for this message
Just Bob (nitro9net) wrote :

I am having the same problem. The touchscreen and touchpad both work in Windows 10, but the touchpad won't work in Linux.

Revision history for this message
Keary Parinis (kparinis) wrote :

Hey Just Bob. It may help if you indicate that the bug affects you in the section above. May also help if you send Ubuntu bug info via apport. Hopefully, we can raise the profile on this bug and get it fixed. Thx.

Revision history for this message
Morten Grannes (bondeulv) wrote :

I'm also having this problem.
Touchpad mostly works in the Basic setting in BIOS/UEFI, but when I'm on Advanced, the touchpad doesn't even show up in xinput.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Looks like i2c-hid wasn't loaded for Elan.
Can you try latest mainline kernel here: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc1/
And boot with `i2c-hid.dyndbg=+p' to kernel parameter.
Attach `dmesg` afterward.

Revision history for this message
Keary Parinis (kparinis) wrote :

I tried loading the latest mainline kernel and I got this error: "ACPI Error: No handler for Region [ECRM]". Please advise. Thanks.

Revision history for this message
Keary Parinis (kparinis) wrote :

I was able to load release 2 of the mainline kernel released on 5/22/17.
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc2/

Unfortunately, the mousepad is still not recognized after booting with the kernel parameter you recommended 'i2c-hid.dyndbg=+p'. I placed this parameter at the end of the line that begins with 'linux'.

Also, the touchscreen is not recognized in rc2. Touch screen does not work and I do not see the device when I run xinput -list. Touch screen works in earlier versions of Ubuntu.

Please see attached dmseg.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Both touchpad and touchscreen failed to initialize because of i2c-designware:
[ 7.199291] i2c_hid i2c-SYNA7300:00: i2c-SYNA7300:00 supply vdd not found, using dummy regulator
[ 8.228444] i2c_designware i2c_designware.1: controller timed out
[ 8.228462] i2c_hid i2c-SYNA7300:00: hid_descr_cmd failed
[ 8.317098] i2c_hid i2c-ELAN0602:00: i2c-ELAN0602:00 supply vdd not found, using dummy regulator
[ 9.348419] i2c_designware i2c_designware.2: controller timed out
[ 9.348437] i2c_hid i2c-ELAN0602:00: hid_descr_cmd failed

Can you try latest mainline kernel (v4.12) again?
If the issue still happen, you need to file an upstream bug.

Revision history for this message
Keary Parinis (kparinis) wrote :

I tried the latest kernel v4.12-rc7, bit it still does not recognize my touch pad.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Please try kernel in [1] and [2], see which one works.

[1] http://people.canonical.com/~khfeng/lp1658345/
[2] http://people.canonical.com/~khfeng/lp1658345-2/

Revision history for this message
Keary Parinis (kparinis) wrote :

Neither kernel worked unfortunately. Please see attached. Additionally, my touch screen was not recognized.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Hmm, can you attach both dmesg?

Revision history for this message
Keary Parinis (kparinis) wrote :

Please see attached. I got an error indicating "elantech_x551c" is missing when installing the kernels.

Revision history for this message
Keary Parinis (kparinis) wrote :

And here is dmesg for the second kernel.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Why do you need elantech_x551c at first place?

Revision history for this message
Keary Parinis (kparinis) wrote :

elantech is the touchpad that Ubuntu cannot recognize. Without it, I do not have a mouse unless I use an external one or touchscreen. Also, I currently use kernel 4.8.0-45 and the touchscreen works. When I tried the kernels you provided, the touchscreen does not show up in xinput -list. In kernel 4.8.0-45 it shows up as "SYNA7300:00 06CB:177C".

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

What's the touchpad ID under Windows 10?

Revision history for this message
Keary Parinis (kparinis) wrote :

In the Windows 10 device manager, it is listed as "ELAN pointing device". In device details it indicates the manufacturer is "ELAN" and location indicates "on I2C HID Device".

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Okay, so the error in dmesg in #25 should be fixed in -rc3.

Can you use [1], attach dmesg with "i2c-hid.dyndbg=+p" again?

Also, does touchscreen work?

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc1/

Revision history for this message
Keary Parinis (kparinis) wrote :

Please see attached. The touchscreen does not work. It does not even show up in my device list.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

It's a regression for your touchscreen - can you find the first bad mainline kernel that fails to make touchscreen work?

https://wiki.ubuntu.com/Kernel/KernelBisection, "Bisecting upstream kernel versions" part.

Revision history for this message
Keary Parinis (kparinis) wrote :

I couldn't get any of the mainline kernels to recognize my touchscreen or touchpad. I checked between 4.4 and 4.13 with no luck. The touchscreen works on Ubuntu 16.10 (4.8) and 17.04 (4.10.0-20). Since it works on those distributions, I'm not sure why none of the mainline kernels will work. Any recommendations?

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Can you apport-collect under 4.13?

Revision history for this message
Keary Parinis (kparinis) wrote : JournalErrors.txt

apport information

tags: added: zesty
description: updated
Revision history for this message
Keary Parinis (kparinis) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Please try 4.13-rc4 again. Hopefully the touchscreen regression is fixed now.

Revision history for this message
Mark (markjb) wrote :

4.13-rc4 - touchscreen is working. No go on touchpad, does not show up with lsusb, lspci or lshw

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :
Revision history for this message
Mark (markjb) wrote : apport information

ApportVersion: 2.20.3-0ubuntu8.7
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 16.10
InstallationDate: Installed on 2017-07-12 (29 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
Package: linux (not installed)
Tags: yakkety
Uname: Linux 4.13.0-041300rc4-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

Revision history for this message
Mark (markjb) wrote : JournalErrors.txt

apport information

Revision history for this message
Mark (markjb) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Mark (markjb) wrote : ProcEnviron.txt

apport information

Revision history for this message
Keary Parinis (kparinis) wrote :

I was able to get the mousepad working with the last kernel you posted. However, the touchscreen is not working. Mousepad shows up as "Elan Touchpad" in xinput. Now missing "SYNA7300:00 06CB:177C" device that was the touchscreen.

http://people.canonical.com/~khfeng/lp1658345-elan-i2c/

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :
Revision history for this message
Keary Parinis (kparinis) wrote : JournalErrors.txt

apport information

description: updated
Revision history for this message
Keary Parinis (kparinis) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Keary Parinis (kparinis) wrote :

No luck with touch screen. Same as before, the touchpad works but no touchsreen. I posted apport info. Also got an error indicating headers were missing b/c you only posted the single deb image. Not sure if that has something to do with it.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :
Revision history for this message
Keary Parinis (kparinis) wrote :

Neither touch screen nor touchpad works :(

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Okay, so the touchscreen issue is unrelated to touchpad. I'll send a patch to enable the touchpad first.

Also, Mark said the touchscreen works on 4.13-rc4 in comment #45. Can you attach `dmesg` on 4.13-rc4?

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Okay, so the touchscreen issue is unrelated to touchpad. I'll send a patch to enable the touchpad.

Also, Mark said the touchscreen works on 4.13-rc4 in comment #45. Can you attach `dmesg` on 4.13-rc4 and 4.13-rc4?

If this is a regression, you need to find the last working mainline kernel and the first non-working mainline kernel.

Revision history for this message
Keary Parinis (kparinis) wrote :

Here is dmesg for 4.13 rc4

Revision history for this message
Keary Parinis (kparinis) wrote :

Here is dmesg for v4.13 rc5

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

When you rollback to old kernel, does the touchscreen work? Which version is it? Do you use DKMS for the touchscreen?

Revision history for this message
raerek (raerek) wrote :

I *think* I have the same touchpad issue with an IdeaPad 320. How do I find out if I have the same touchpad as in the Flex? I have no Windows to find out running it:(

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

@Varga,

Please file a new bug report.

Revision history for this message
Taylor Lee (taylorlee) wrote :

@kaihengfeng I am having a similar problem with a Lenovo ideapad 330. Could I get access to the custom kernel you posted before? Those links are dead.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Though the symptoms are the same, a lot of time the root cause differs. So please file a new bug.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.