Touchpad is not detected on Lenovo IdeaPad 3 14IIL05 Core i3-1005G1 (81WD004MGE)

Bug #1880172 reported by bast1
52
This bug affects 11 people
Affects Status Importance Assigned to Milestone
linux-signed-hwe (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Touchpad is not detected on Ubuntu Linux pcl001 5.3.0-53-generic #47~18.04.1-Ubuntu SMP Thu May 7 13:10:50 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

1. ( Laptop model directly from the sticker of the computer. )

   Lenovo IdeaPad 3 14IIL05 Core i3-1005G1 (81WD004MGE)

   Model Name: 81WD

2. ( Manufacturer of the Touchpad. )

   no idea

3. ( When the symptom first appeared.)

   Touchpad is not detected on any other distribution or with live system ( debian 10 or ubuntu 18 + 19 or 20 or Manjaro )

  the Touchpad is working under Windows 10 but not on linux :(

xinput list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [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)]
    ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)]
    ↳ Ideapad extra buttons id=11 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=12 [slave keyboard (3)]

i have attached 3 files in a zip file ( xinput list + dmesg + /proc/bus/input/devices
 output )

pls.. i expect your answer or an fix :)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-5.3.0-53-generic 5.3.0-53.47~18.04.1
ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-53-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
Date: Fri May 22 13:53:02 2020
InstallationDate: Installed on 2020-05-20 (1 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-signed-hwe
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
bast1 (bast1) wrote :
affects: ubuntu → linux-signed-hwe (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux-signed-hwe (Ubuntu):
status: New → Confirmed
Revision history for this message
TheTakylo (thetakylo) wrote :

On my computer the touchpad doesn't work, but it detects

$ xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ MSFT0004:01 06CB:CD98 Mouse id=13 [slave pointer (2)]
⎜ ↳ MSFT0004:01 06CB:CD98 Touchpad id=14 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
    ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
    ↳ Video Bus id=6 [slave keyboard (3)]
    ↳ Video Bus id=7 [slave keyboard (3)]
    ↳ Power Button id=8 [slave keyboard (3)] ↳ Integrated Camera: Integrated C id=12 [slave keyboard (3)]
    ↳ Ideapad extra buttons id=15 [slave keyboard (3)]
    ↳ Intel HID events id=16 [slave keyboard (3)]
    ↳ Intel HID 5 button array id=17 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=18 [slave keyboard (3)]

Revision history for this message
bast1 (bast1) wrote :
Revision history for this message
bast1 (bast1) wrote :
Revision history for this message
bast1 (bast1) wrote :
Revision history for this message
bast1 (bast1) wrote :
Revision history for this message
bast1 (bast1) wrote :

sudo acpidump | grep -C3 ELAN
 27EC0: 70 47 4E 55 4D 0C 10 00 01 06 49 4E 54 31 70 49 pGNUM.....INT1pI
 27ED0: 4E 55 4D 0C 10 00 01 06 49 4E 54 32 A0 34 93 54 NUM.....INT2.4.T
 27EE0: 50 54 59 01 70 0D 4D 53 46 54 30 30 30 31 00 5F PTY.p.MSFT0001._
 27EF0: 48 49 44 70 0D 45 4C 41 4E 30 30 30 31 00 5F 53 HIDp.ELAN0001._S
 27F00: 55 42 70 0A 15 42 41 44 52 70 01 48 49 44 32 A4 UBp..BADRp.HID2.
 27F10: 00 A0 36 93 54 50 54 59 0A 02 70 0D 4D 53 46 54 ..6.TPTY..p.MSFT
 27F20: 30 30 30 31 00 5F 48 49 44 70 0D 53 59 4E 41 30 0001._HIDp.SYNA0

Revision history for this message
bast1 (bast1) wrote :
Revision history for this message
bast1 (bast1) wrote :
bast1 (bast1)
description: updated
Revision history for this message
TheTakylo (thetakylo) wrote :

anyone have any news about this bug ?

Revision history for this message
bast1 (bast1) wrote :

yeah, this touchpad sucks :0

Revision history for this message
TheTakylo (thetakylo) wrote :

@bast1 Too strange, it worked 2 days last week (1 time out of 2 at each start up) and now nothing.

Revision history for this message
Ludovic LEMARINEL (ludovic50750) wrote :

Not sure this ticket is a duplicate of #1878279 : I also have an Ideapad 3 14IIL05, and the acpidump grep doesn't show the same ID that other's ticket.
Also, on the other ticket, the touchpad is working from time to time (one boot can be OK, the other can be not...), and the other's bug specifies MSFT0004:01, but my computer specifies MSFT0001:01.

Hope we'll find a solution soon ?

PS : tried with kernel 5.7.2, disabled elants-i2c module, same problem.

Revision history for this message
bast1 (bast1) wrote :

thx for ur feedback

Revision history for this message
bast1 (bast1) wrote :
Revision history for this message
Ludovic LEMARINEL (ludovic50750) wrote :

Some information that seems revelant to me :
On the gentoo forum subject : before the user enabled CONFIG_PINCTRL_SUNRISEPOINT, the device seemed to be already detected, as it was visible in /proc/bus/input/devices as "MSFT0001:00 06CB:7F27 Touchpad"

He then did enabled the CONFIG in the kernel config, and then when pressing FN-F6, the touchpad did get detected and enabled.

In my case, with kernel 5.7.2, I don't have my touchpad listed in /proc/bus/input/devices.

Revision history for this message
bast1 (bast1) wrote :

yepp, same thing here at kernel version 5.7.1 on ubuntu 18, 19, 20 or fedora :(

Revision history for this message
Ludovic LEMARINEL (ludovic50750) wrote :

Another information I found while installing Windows :
Without any driver, the touchpad doesn't work.
It is instantly detected as an "i2c hid input device" when the "Serial IO I2C Host Controller - 34E9" device drivers are installed.

So, this seems to confirm to me that this touchpad IS plugged on the I2C bus.
If it can help developers, I can give informations about the pointing device while in Windows.

Revision history for this message
Ludovic LEMARINEL (ludovic50750) wrote :

I don't know if this is related with this bug, but in my dmesg, I've found some error messages with I2C controler :

[ 0.432347] pci 0000:00:15.0: BAR 0: no space for [mem size 0x00001000 64bit]
[ 0.432348] pci 0000:00:15.0: BAR 0: failed to assign [mem size 0x00001000 64bit]
[ 0.432352] pci 0000:00:15.1: BAR 0: no space for [mem size 0x00001000 64bit]
[ 0.432353] pci 0000:00:15.1: BAR 0: failed to assign [mem size 0x00001000 64bit]
[ 0.432356] pci 0000:00:1f.5: BAR 0: no space for [mem size 0x00001000]
[ 0.432358] pci 0000:00:1f.5: BAR 0: trying firmware assignment [mem 0xfe010000-0xfe010fff]
[ 0.432360] pci 0000:00:1f.5: BAR 0: [mem 0xfe010000-0xfe010fff] conflicts with Reserved [mem 0xfc800000-0xfe7fffff]
[ 0.432361] pci 0000:00:1f.5: BAR 0: failed to assign [mem size 0x00001000]
[ 0.432365] pci 0000:00:1d.0: PCI bridge to [bus 01]
[ 0.432387] pci 0000:00:1d.0: bridge window [mem 0x81100000-0x811fffff]

...

[ 2.375554] intel-lpss: probe of 0000:00:15.0 failed with error -16
[ 2.392134] platform idma64.0: failed to claim resource 0: [mem 0x00000800-0x00000fff]
[ 2.392136] intel-lpss 0000:00:15.1: Failed to add idma64, fallback to PIO

According to lspci, those 2 devices addresses (00:15:0 and 15:1) are i2c controlers :
00:15.0 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP Serial IO I2C Controller #0 (rev 30)
00:15.1 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP Serial IO I2C Controller #1 (rev 30)

Revision history for this message
Ludovic LEMARINEL (ludovic50750) wrote :

Last strange thing I've noticed :
in dmesg, I've got an error about irq not handled:

[ 9.512884] irq 9: nobody cared (try booting with the "irqpoll" option)
[ 9.512888] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.7.1-050701-generic #202006071230
[ 9.512888] Hardware name: LENOVO 81WD/LNVNB161216, BIOS EMCN14WW 05/11/2020
[ 9.512889] Call Trace:
[ 9.512890] <IRQ>
[ 9.512895] dump_stack+0x6d/0x9a
[ 9.512898] __report_bad_irq+0x3a/0xaf
[ 9.512899] note_interrupt.cold+0xb/0x61
[ 9.512900] handle_irq_event_percpu+0x73/0x80
[ 9.512901] handle_irq_event+0x3b/0x5a
[ 9.512902] handle_fasteoi_irq+0x9c/0x150
[ 9.512904] do_IRQ+0x55/0xe0
[ 9.512905] common_interrupt+0xf/0xf
[ 9.512905] </IRQ>
[ 9.512908] RIP: 0010:cpuidle_enter_state+0xca/0x3e0
[ 9.512909] Code: ff e8 da 60 7a ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 ea 02 00 00 31 ff e8 dd ed 80 ff fb 66 0f 1f 44 00 00 <45> 85 e4 0f 88 3f 02 00 00 49 63 d4 4c 8b 7d d0 4c 2b 7d c8 48 8d
[ 9.512910] RSP: 0018:ffffa936800e3e38 EFLAGS: 00000246 ORIG_RAX: ffffffffffffffde
[ 9.512911] RAX: ffff8f6516c6d2c0 RBX: ffff8f6516c78a00 RCX: 000000000000001f
[ 9.512911] RDX: 0000000000000000 RSI: 000000006b86e1b8 RDI: 0000000000000000
[ 9.512912] RBP: ffffa936800e3e78 R08: 000000023701fcd7 R09: ffffffff9cf6c420
[ 9.512912] R10: ffff8f6516c6bf84 R11: ffff8f6516c6bf64 R12: 0000000000000001
[ 9.512912] R13: ffffffff9cf6c420 R14: 0000000000000001 R15: ffff8f6516c78a00
[ 9.512915] ? cpuidle_enter_state+0xa6/0x3e0
[ 9.512916] cpuidle_enter+0x2e/0x40
[ 9.512917] call_cpuidle+0x23/0x40
[ 9.512918] do_idle+0x1e7/0x280
[ 9.512919] cpu_startup_entry+0x20/0x30
[ 9.512921] start_secondary+0x171/0x1d0
[ 9.512923] secondary_startup_64+0xb6/0xc0
[ 9.512923] handlers:
[ 9.512926] [<00000000a606525d>] acpi_irq

If I try to reboot with "irqpoll" I don't have this error anymore, but another about iwlwifi and a "kernel panic" dump (not sure it's called as this), and wifi doesn't work anymore, but I don't get more touchpad.

Revision history for this message
Nickolai Leschev (demysteriismundi) wrote :

Kernel updating to 5.7.1 version has helped me.

Revision history for this message
bast1 (bast1) wrote :

@Nickolai Leschev
on ubuntu at IdeaPad 3 14IIL05?

Revision history for this message
Ludovic LEMARINEL (ludovic50750) wrote :

His hardware is different of our's : his touchpad is identified as "MSFT0004" but our is "MSFT0001".

Revision history for this message
TheTakylo (thetakylo) wrote :

Yesterday my touchpad worked all day long, even after several restarts, and this morning it doesn't work anymore ... it's really not understandable.

Yesterday I could see it appearing as an xinput list.

⎜ ↳ MSFT0004:00 06CB:CD98 Mouse id=13 [slave pointer (2)]
⎜ ↳ MSFT0004:00 06CB:CD98 Touchpad id=14 [slave pointer (2)]

toaday nothing

Revision history for this message
bast1 (bast1) wrote :

yepp, so0 strange ;(

Revision history for this message
TheTakylo (thetakylo) wrote :

Now it work ... maybe i can help ? Do I need to provide logs or anything else with the touchpad working?

Revision history for this message
bast1 (bast1) wrote :

hey, give us ur dmesg output pls :)

Revision history for this message
TheTakylo (thetakylo) wrote :

this is the output of dmseg

Revision history for this message
TheTakylo (thetakylo) wrote :

the touchpad was not working when I previously sent the dmseg.txt, here is now dmseg.txt with the touchpad working (after reboot)

Revision history for this message
bast1 (bast1) wrote :

thx a lot

Revision history for this message
bast1 (bast1) wrote :

@TheTakylo

and the Output of /proc/bus/input/devices pls..

cat /proc/bus/input/devices

greetz

Revision history for this message
TheTakylo (thetakylo) wrote :

this is the output of

cat /proc/bus/input/devices

Revision history for this message
TheTakylo (thetakylo) wrote :
Revision history for this message
Christian homberg (christianhomberg) wrote :

Here's my dmesg *when it's working*, dev_proc to follow (Ubuntu 19.10 Live CD: MSFT0004)

It wasn't working earlier in my Ubuntu 19.10 installation however.

Revision history for this message
Christian homberg (christianhomberg) wrote :

And here's my proc devices when it's working.

Output for when it's not working to follow.

Revision history for this message
bast1 (bast1) wrote :

pls confirm this error by klicking "Does this bug affect you?"

    Yes, it affects me

thx a lot

@Christian & TheTakylo

the interessting part is:

I: Bus=0018 Vendor=06cb Product=cd98 Version=0100
N: Name="MSFT0004:00 06CB:CD98 Mouse"
P: Phys=i2c-MSFT0004:00
S: Sysfs=/devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-1/i2c-MSFT0004:00/0018:06CB:CD98.0001/input/input15
U: Uniq=
H: Handlers=mouse0 event12
B: PROP=0
B: EV=17
B: KEY=30000 0 0 0 0
B: REL=3
B: MSC=10

I: Bus=0018 Vendor=06cb Product=cd98 Version=0100
N: Name="MSFT0004:00 06CB:CD98 Touchpad"
P: Phys=i2c-MSFT0004:00
S: Sysfs=/devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-1/i2c-MSFT0004:00/0018:06CB:CD98.0001/input/input16
U: Uniq=
H: Handlers=mouse1 event13
B: PROP=5
B: EV=1b
B: KEY=e520 10000 0 0 0 0
B: ABS=2e0800000000003
B: MSC=20

but in my case or device list..

https://launchpadlibrarian.net/481416051/devices

cant see touch or mouse device :(

on ubuntu 18, 19, 20 with new or old kernel ( 5.7.1 )

..but on wakeup i can see an touchpad logo this is all and this suck so0 much!

@Ludovic LEMARINEL

on fedora i have the same output ( red lines )

intel-lpss 0000:00:15.1: Failed to add idma64, fallback to PIO

greetz

Revision history for this message
Christian homberg (christianhomberg) wrote :

Here's my dmesg when it's not working

Revision history for this message
Christian homberg (christianhomberg) wrote :

And here's my proc devices when it's not working

Revision history for this message
bast1 (bast1) wrote :

thx

Revision history for this message
Ludovic LEMARINEL (ludovic50750) wrote :

I'm sorry to inform you I won't be able to help you more, I've sold this laptop.
(Bought a Dell inspiron 5485, everything works fine at startup. Just had to upgrade kernel to >=5.6)

Good luck !

Revision history for this message
bast1 (bast1) wrote :

np, hf :)

Revision history for this message
Michael Reutman (mreutman) wrote :

Hello,

I have a similar model as the one used to file the initial bug report and am having similar issues, i.e. trackpad does not work. I have tried upgrading the kernel to the latest mainline release of 5.8 and am still out of luck. Laptop model is Lenovo Ideapad 3 15iil05.

@bast1, I'm more than willing to help assist debugging this issue.

Revision history for this message
Jazz (blaze2236) wrote :

Hi,

I'm having a same issue with Ideapad 5.

The trackpad does work if a wire mouse plugged in, but it stops working after reboot.

xinput list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ xwayland-pointer:17 id=6 [slave pointer (2)]
⎜ ↳ xwayland-relative-pointer:17 id=7 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
    ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
    ↳ xwayland-keyboard:17 id=8 [slave keyboard (3)]

Revision history for this message
Jazz (blaze2236) wrote :

Nevermind about the trackpad working when the mouse is plugin at boot time. That stopped working.

Revision history for this message
Jazz (blaze2236) wrote :

Found a hack that seems to be working:

Add "i8042.reset" in the /etc/default/grub on the GRUB_CMDLINE_LINUX before "quiet splash"

Found it here: https://youtu.be/ZAPSrbZvsjk

Revision history for this message
Jazz (blaze2236) wrote :

The above does not work, got too excited. It was just a random fluke then just as randomly stopped working.

Revision history for this message
Jazz (blaze2236) wrote :

So I turn on the laptop today, and the trackpad is working.

xinput list is the same as when the trackpad isn't working:
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ xwayland-pointer:17 id=6 [slave pointer (2)]
⎜ ↳ xwayland-relative-pointer:17 id=7 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
    ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
    ↳ xwayland-keyboard:17 id=8 [slave keyboard (3)]

However, I'm now finding it in the dmesg | grep touch

[ 2.055799] hid-multitouch 0018:06CB:CD98.0002: input,hidraw1: I2C HID v1.00 Mouse [MSFT0004:00 06CB:CD98] on i2c-MSFT0004:00

but wasn't able to find it when it wasn't working.

@bast1 I'm available to help debug as well... I love the laptop besides this issue.

Revision history for this message
Jazz (blaze2236) wrote :
Revision history for this message
Michael Reutman (mreutman) wrote :

Hello,

I was able to get the touchpad working on my Lenovo Ideapad 3 15iil05 to function by adding the following arguments to GRUB_CMDLINE_LINUX_DEFAULT.

"i8042.nopnp=1 pci=nocrs"

I'm curious as to what this does that makes it work, but I can report that my touchpad works and I have full control of my mouse (one and two finger gestures work just fine).

Hopefully this helps.

Revision history for this message
Matt Warmerdam (mr-m0ry) wrote :

Hi everyone!

Just wanted to confirm that @mreutman's answer fixed my Lenov Ideapad 3 15iil05.

Added the arguments he mentioned to GRUB_CMDLINE_LINUX_DEFAULT, updated grub of course, rebooted and it worked.

Thanks for the help! :D

P.S. Would also like to know where you got the idea from?

Revision history for this message
Alessandro (sandro-it) wrote :

Hello everyone,

I thank you for the fix proposed from @mreutman! work on my ideapad 3

thank you very much!

Revision history for this message
bast1 (bast1) wrote :

hey all, I've sold this laptop.

but many thx for this nice post :0

greetz all thx a lot

Revision history for this message
Stefan Bambuleac (stefan-bambuleac) wrote :

Lenovo IdeaPad 5 15IIL05 - i5-1035G1
worked like a charm. Thank you very much Michael Reutman (mreutman) .

>>> 01
added to
# nano /etc/default/grub
"
GRUB_CMDLINE_LINUX_DEFAULT="i8042.nopnp=1 pci=nocrs quiet splash"
"

>>> 02
updated grub

# update-grub

>>> 03

reboot

Revision history for this message
Ratul Saha (thatanonyg) wrote :

@mreutman yes that command line argument hack works. But every time I ran Ubuntu or PopOS with that my system got corrupted after few days. My disks would be mounted as read-only with seemingly no way to fix it. Even reinstalling Ubuntu won't fix it. It would only go away after reinstalling windows. I will confirm if those params were the reason after a few days as right now I am running a clean install of Ubuntu without those boot params. But just a heads up. Please let me know if you experienced something similar on Lenovo Ideapad 3 15iil05

Revision history for this message
Noctis Bennington (noctis13) wrote :

Hello there. The option @mreutman recommended doesn't work on Ubuntu 22.04. It doesn't allow boot. So this is again a problem in the last LTS (22.04).

Revision history for this message
chuck hilyard (chilyard) wrote :

thought i'd provide an update, here.

lenovo ideapad 3 17iil05

touchpad works flawlessly in windows 10, of course.

did NOT work w/ fresh ubuntu 22.04 lts

updated lenovo bios to EMCN52WW
updated kernel to 5.18.6-051806-generic
updated grub, as such:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.nopnp=1 pci=nocrs"

xinput FINALLY shows the touchpad. the touchpad now works.

xinput output:
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Microsoft Microsoft 5-Button Mouse with IntelliEye(TM) id=9 [slave pointer (2)]
⎜ ↳ MSFT0001:01 2808:0101 Mouse id=11 [slave pointer (2)]
⎜ ↳ MSFT0001:01 2808:0101 Touchpad id=12 [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)]
    ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)]
    ↳ Ideapad extra buttons id=13 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=14 [slave keyboard (3)]

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.