MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot

[Till]

Touchpad 'Buttonless Mylar surface multi-touch touchpad' doesn't work at all (No response from the Touchpad) for notebook 'Lenovo Ideapad 5 14IIL05 81YH' from first system start on.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-29-generic 5.4.0-29.33
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: tilman 1607 F.... pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue May 12 21:22:22 2020
InstallationDate: Installed on 2020-05-12 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 81YH
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=bb961a96-8855-4e50-814d-7994235377c3 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-29-generic N/A
 linux-backports-modules-5.4.0-29-generic N/A
 linux-firmware 1.187
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/25/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: DSCN23WW(V1.09)
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: No DPK
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad 5 14IIL05
dmi.modalias: dmi:bvnLENOVO:bvrDSCN23WW(V1.09):bd03/25/2020:svnLENOVO:pn81YH:pvrIdeaPad514IIL05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514IIL05:
dmi.product.family: IdeaPad 5 14IIL05
dmi.product.name: 81YH
dmi.product.sku: LENOVO_MT_81YH_BU_idea_FM_IdeaPad 5 14IIL05
dmi.product.version: IdeaPad 5 14IIL05
dmi.sys.vendor: LENOVO

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[You-Sheng Yang (vicamo)]

Please attach your acpi dump info:

  $ sudo apt install acpica-tools
  $ sudo acpidump -o acpi.dump

And attach that `acpi.dump` file.

[AdrienM (adi90x)]

Hello,

Thanks a lot for having a look, please find enclosed acpi.dump
Do not hesitate if I can provide anything else.

Regards,

[You-Sheng Yang (vicamo)]

@AdrienM, so you can decompile your ACPI blob shipped by the device vendor:

  $ acpixtract acpi.dump
  $ iasl -d *.dat

And from the decompiled `dsdt.dsl` file, it has:

  Name (_HID, "XXXX0000") // _HID: Hardware ID
  Name (_CID, "PNP0C50" /* HID Protocol Device (I2C bus) */) // _CID: Compatible ID
  ...

I'm not sure what will it be like in the runtime, so we need your to run:

  $ cd /sys/bus/acpi/devices
  $ for d in $(ls -1 */hid); do d=${d%/*}; grep -q PNP0C50 $d/modalias && echo $d; done

And, please re-attach your dmesg log with following kernel boot parameters. For detailed steps, please see https://askubuntu.com/questions/19486/how-do-i-add-a-kernel-boot-parameter:

  dyndbg="file drivers/hid/* +pt" i2c-hid.debug=1 log_buf_len=16M

[AdrienM (adi90x)]

Hello,

Result from

...
for d in $(ls -1 */hid); do d=${d%/*}; grep -q PNP0C50 $d/modalias && echo $d; done
...

=> MSFT0004:01

And attached dmesg output using the boot parameter you mention.

Regards,
Adrien

[You-Sheng Yang (vicamo)]

Sorry, I missed one parameter "hid.debug=1". Could you attach dmesg one more time with that appended? It makes:

  dyndbg="file drivers/hid/* +pt" hid.debug=1 i2c-hid.debug=1 log_buf_len=16M

Thank you.

[AdrienM (adi90x)]

Here it is !

[AdrienM (adi90x)]

Hello,

Anything else I can provide ?

Regards,

[TheTakylo (thetakylo)]

I also have the same problem, under Linux this touchpad doesn't work.

[AdrienM (adi90x)]

This bug report has more information than bug #1880172.
This one should be main thread no ?

[TheTakylo (thetakylo)]

i dont know why but sometimes the touchpad work and sometimes the touchpad doesnt work ..

[AdrienM (adi90x)]

@TheTakylo: What is your OS and what is your kernel version ? Do you have the exact same ideaPad 5 - 14IIL05 ?

[TheTakylo (thetakylo)]

Actually the touchpad doesnt work.
This is my computer details

       _,met$$$$$gg.
    ,g$$$$$$$$$$$$$$$P. --------------------------
  ,g$$P" """Y$$.". OS: Debian GNU/Linux bullseye/sid x86_64
 ,$$P' `$$$. Host: 81YH IdeaPad 5 14IIL05
',$$P ,ggs. `$$b: Kernel: 5.6.0-1-amd64
`d$$' ,$P"' . $$$ Uptime: 49 mins
 $$P d$' , $$P Packages: 1830 (dpkg)
 $$: $$. - ,d$$' Shell: bash 5.0.16
 $$; Y$b._ _,d$P' Resolution: 1920x1080
 Y$$. `.`"Y$$$$P"' DE: GNOME
 `$$b "-.__ WM: Mutter
  `Y$$ WM Theme: Adwaita
   `Y$$. Theme: Adwaita [GTK2/3]
     `$$b. Icons: Adwaita [GTK2/3]
       `Y$$b. Terminal: gnome-terminal
          `"Y$b._ CPU: Intel i5-1035G1 (8) @ 3.600GHz
              `""" GPU: Intel Iris Plus Graphics G1
                              GPU: NVIDIA GeForce MX330
                              Memory: 2906MiB / 15758MiB

[AdrienM (adi90x)]

Hello,

I have it working after installation of Ubuntu 19.10. However it stop as soon as I do an apt upgrade . Will try to understand which package break it.

[AdrienM (adi90x)]

Ok so for the moment , I have a working install of Ubuntu 19.10.
Seems that the issue is happening when you update/change xorg-server, which I was doing almost at first to load nvidia driver.
Therefore, for the moment :
Make sure to be in UEFI
Install from Ubuntu 19.10 ISO
Install from apt nvidia-driver-440 nvidia-prime mesa-utils
(Do not use the Additional Driver GUI interface of Ubuntu)
Then do apt update && apt upgrade && apt autoremove

Not sure it will work for every one as it seems really random , will keep on trying to understand exactly what is happening.

[AdrienM (adi90x)]

Ok in fact the issue is still randomly happening.
Found some bug report on Arch forum too , seems to be an issue of how i2c_hid controler is working and especially how it is shutdown.

[Michael Amplatz (xekuta747)]

I have a 14IIL05 here, and the same issue with Ubuntu 20.04 and Kernel 5.7. The Touchpad does not respond in any way (though it works in Windows, but only after installation of drivers).

[AdrienM (adi90x)]

Normally you can have it working from time to time ( just being lucky on startup I guess ).
Try to shutdown & start ( and not reboot )

[AdrienM (adi90x)]

Did you try enabling SecureBoot ?

[Michael Amplatz (xekuta747)]

Am 01.06.20 um 18:45 schrieb AdrienM:
> Normally you can have it working from time to time ( just being lucky on startup I guess ).
> Try to shutdown & start ( and not reboot )
>
No, Touchpad never worked in Ubuntu.

Am 01.06.20 um 19:11 schrieb AdrienM:
> Did you try enabling SecureBoot ?
>

Yes, I did two times now, but it doesn't change anything.

[TheTakylo (thetakylo)]

For a few days the touchpad worked every other day, for a week it hadn't worked at all for me :/

[Ludovic LEMARINEL (ludovic50750)]

Hi
Just to add some informations.
Just got today a Lenovo Ideapad 14ILI05, Core i5 based, and no touchpad working.
I've tried with kubuntu 19.10 since AdrienM said it was working with this release, but no more luck with it (only tried Live).

I saw a BIOS update on Lenovo support page from 5 days ago, not yet installed it, but I doubt it will make it work !

If I can provide some logs or dumps, or even try patches, I'm willing to help !

[Ludovic LEMARINEL (ludovic50750)]

Just some follow-up :
It seems that my touchpad is not the same as AdrienM, since my acpi dump is about ELAN0001 and AdrienM's is ELAN2097.

Following some recommendations found on askubuntu.com, I'm currently trying to compile a 5.7.2 kernel with added ELAN0001 id to include/linux/input/elan-i2c-ids.h, and also made the elan touchscreen driver as a module, since this driver recognizes the ELAN0001 as a touch screen, and not a mouse.

I'll post an update when I'll have tested.

[Ludovic LEMARINEL (ludovic50750)]

So, tried with kernel 5.7.2, disabled elants-i2c module, and added device ID in elan-i2c-ids.h, same problem.

Don't know where to look now :(

[Michael Amplatz (xekuta747)]

Did you all confirm the issue? I think this is very important to estimate the priority for the developers.

[bast1 (bast1)]

thx for ur feedback..

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

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

this old fix wont work

https://forums.gentoo.org/viewtopic-t-1086512-start-0.html

greetz

[bast1 (bast1)]

perhaps the same issue?!

The main culprit was CONFIG_PINCTRL_SUNRISEPOINT that provides an interface that allows configuring of PCH pins and using them as GPIOs. Apparently the touchpad port needs to be unlocked by the signal raised by PCH's GPIO pins, so this module is required for it to work. It is called pinctrl_sunrisepoint, and it is a feature of my motherboard's chipset, Sunrise Point.

greetz

[TheTakylo (thetakylo)]

I also confirm the error, here is the error of my computer: IdeaPad 5 14IIL05

and the touchpad is not detected.

sudo acpidump | grep -C3 ELAN
   30C80: 30 93 54 50 4C 54 0A 02 70 0D 41 54 4D 4C 32 39 0.TPLT..p.ATML29
   30C90: 35 32 00 5F 48 49 44 70 00 48 49 44 32 70 0A 4A 52._HIDp.HID2p.J
   30CA0: 42 41 44 52 70 0C 80 1A 06 00 53 50 45 44 A4 00 BADRp.....SPED..
   30CB0: A0 30 93 54 50 4C 54 0A 03 70 0D 45 4C 41 4E 32 .0.TPLT..p.ELAN2
   30CC0: 30 39 37 00 5F 48 49 44 70 01 48 49 44 32 70 0A 097._HIDp.HID2p.
   30CD0: 10 42 41 44 52 70 0C 80 1A 06 00 53 50 45 44 A4 .BADRp.....SPED.
   30CE0: 00 A0 30 93 54 50 4C 54 0A 04 70 0D 4E 54 52 47 ..0.TPLT..p.NTRG

[Michael Amplatz (xekuta747)]

Please all click on "This bug affecty you and 7 other people" and then "Does this bug affect you?" "Yes". Thank you!

[Ludovic LEMARINEL (ludovic50750)]

Perhaps it has something to do with CONFIG_PINCTRL_SUNRISEPOINT, but how can we be sure that our motherboard is including SUNRISE POINT ?

[Shivanand (patilshivanand)]

Same issue, got a latest Ideapad 5 and found trackpad and brightness adjustment not working. Tried couple of things like changing distro, changing Kernel version etc, nothing worked.

[TheTakylo (thetakylo)]

Hello,

I don't know why, my touchpad is working today and it's detected!

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

[peteole2707 (peteole2707-linux-kernel-bugs)]

On my lenovo ideapad 5 14ARE05 random decides whether the touchpad works or not, but it stays the same until a second boot. Unlike the 15 inch version it has the following touchpad:
Device 'MSFT0004:00 06CB:CD98 Touchpad':
When it does not work, I get the following kernel error every few seconds:
i2c_designware AMDI0010:00: controller timed out
It is recognized by xinput in inoperational condition as well.
However, the behavior is not totally random. Chances are much better if I shut the computer down and then power it on after a few seconds compared to hitting the reboot button.
I am using manjaro linux, but also tried ubuntu and fedora, it's the same on all distros as well as on the 5.6 kernel.
I have been wondering if it is possible to completely restart the touchpad until it works, but I could not find out which component need to be restarted for that and how to do it. This would be a great functionality to fix all kinds of hardware bugs.
Another idea would be to find out what makes the touchpad go into the working or not working state. I would be pleased for any ideas.

[TheTakylo (thetakylo)]

Doesnt work toaday ... too strange !

[Shivanand (patilshivanand)]

This bug is still unassigned for a month now, Not sure when we can have an update. Has anyone from the affected users found an alternative to this ?.

[bast1 (bast1)]

nope..some old workarounds that don't work for us, this is all.

[Michael Amplatz (xekuta747)]

What I learned by using Linux is patience. In the meantime I use a bluetooth mouse. Works fine, but you have to activate bluetooth with another device ;-) Lucky, that everything else is doing well.

[drdjekyl (mrhyde)]

Hi there,

My problem is same as yours.

I have an Ideapad 81YH with intel i7 chipset. I installed ubuntu 20.04 with kernel 5.4 and touchpad doesn't seem to work as well.

2-3 days ago I modified the grub in /etc/default, it made my touchpad working for a few boots. Unfortunately, it's gone..

IDK what to do to fix this. If someone has some ideas or tests to improve touchpad behaviour, it could be great !

[Gustav Krogh-jeyasingham (gustavekkj)]

Got at Lenovo ideapad 5 14IIL05 intel i7. Fresh install of ubuntu 20.04 touchpad never worked a single time so seems to be the same issue. Any information i can share to help with the issue?

[Gustav Krogh-jeyasingham (gustavekkj)]

I found a weird work around updated the kernel to 5.7.1.
Then i disabled legacy support uefi only.
Then secure boot then booted up. Ubuntu told me it couldn't.
Then disabled secure boot and then it worked.

When it stops working redo these last steps in BIOS makes it work.

[Gustav Krogh-jeyasingham (gustavekkj)]

Confirmation bias: I installed ubuntu again with secure boot. Didn't update kernel. Didn't do anything in bios apart from only uefi. Now i only need to open and close the bios then the touchpad works. If I don't do it it stops working. This bug is weird.

[Adrian Gotca (adriangotca)]

this bug also affects me, just installed Ubuntu 20.04, and touchpad isn't responding at all. waiting for a fix. In the meantime, I'll use a mouse for this job

[TheTakylo (thetakylo)]

No news about a possible fix ?

[louismichel (louismichel-linux-kernel-bugs)]

I have the same touchpad issues with the same laptop IdeaPad 5 14ARE05

I added the kernel boot parameters:
"dynbg=file drivers/input/* +pt" i8042.debug=1 i8042.nopnp=1 log_buf_len=32M

Then I could get the following logs:
On kernel 5.7.6:
(no touchpad at all)
i2c_hid i2c-MSFT0004:00: HID over i2c has not been provided an Int IRQ
i2c_hid: probe of i2c-MSFT0004:00 failed with error -22

On kernel 5.8.2-rc2 mainline:
(touchpad acting limited)
i2c_hid i2c-MSFT0004:00: supply vdd not found, using dummy regulator
i2c_hid i2c-MSFT0004:00: supply vddl not found, using dummy regulator
i2c_hid i2c-MSFT0004:00: failed to retrieve report from device.
input: MSFT0004:00 06CB:CD98 Mouse as /devices/platform/AMDI0010:00/i2c-0/i2c-MSFT0004:00/0018:06CB:CD98.0001/input/input13
input: MSFT0004:00 06CB:CD98 Touchpad as /devices/platform/AMDI0010:00/i2c-0/i2c-MSFT0004:00/0018:06CB:CD98.0001/input/input14
hid-generic 0018:06CB:CD98.0001: input,hidraw0: I2C HID v1.00 Mouse [MSFT0004:00 06CB:CD98] on i2c-MSFT0004:00
i2c_hid i2c-MSFT0004:00: failed to retrieve report from device.
input: MSFT0004:00 06CB:CD98 Mouse as /devices/platform/AMDI0010:00/i2c-0/i2c-MSFT0004:00/0018:06CB:CD98.0001/input/input16
input: MSFT0004:00 06CB:CD98 Touchpad as /devices/platform/AMDI0010:00/i2c-0/i2c-MSFT0004:00/0018:06CB:CD98.0001/input/input17
hid-multitouch 0018:06CB:CD98.0001: input,hidraw0: I2C HID v1.00 Mouse [MSFT0004:00 06CB:CD98] on i2c-MSFT0004:00

Hope that can helps us all find a fix for that issue.

[peteole2707 (peteole2707-linux-kernel-bugs)]

Thanks! I also realized that chances are better for the touchpad to work if it worked on the last boot. I believe the kernel does strange things with it when it spams me with "controller timed out" messages on shutdown. I wrote a script which prevents the system from having these shutdown issues. It unloads some modules and then reloads them. Unfortunately it only helps for the next boot, the touchpad is never even recognized after running it.

sudo modprobe -r i2c_hid
sudo modprobe -r i2c_piix4
sudo modprobe -r hid_multitouch
sudo modprobe i2c_hid
sudo modprobe i2c_piix4
sudo modprobe hid_multitouch

It helps to break "bad boot streaks"

[louismichel (louismichel-linux-kernel-bugs)]

Interesting find indeed when doing
sudo modprobe -r i2c_hid
sudo modprobe i2c_hid
The "controller timed out" messages stops. Although that does not fix the touchpad it does suggest that this module is at cause.

After further digging, I got another set of log after booting on mainline (appended below). Basically, I see that the following shows up first before the "time out spamming" starts:

i2c_designware AMDI0010:00: i2c_dw_handle_tx_abort: lost arbitration
i2c_designware AMDI0010:00: controller timed out
i2c_hid i2c-MSFT0004:00: failed to retrieve report from device.

Now, I found these 3 exact log messages in this commit to fix another DELL Win8 touchpad in 2015:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.8-rc2&id=6d4f5440a3a2bb2e9d0d582bbf98234e9e9bb095

Maybe some learning from this commit can lead us to fix this for the MSFT touchpad.

Here my latest log on mainline:
---------------
i2c_hid i2c-MSFT0004:00: supply vdd not found, using dummy regulator
i2c_hid i2c-MSFT0004:00: supply vddl not found, using dummy regulator
i2c_designware AMDI0010:00: i2c_dw_handle_tx_abort: lost arbitration
i2c_designware AMDI0010:00: controller timed out
i2c_hid i2c-MSFT0004:00: failed to retrieve report from device.
input: MSFT0004:00 06CB:CD98 Mouse as /devices/platform/AMDI0010:00/i2c-0/i2c-MSFT0004:00/0018:06CB:CD98.0001/input/input13
input: MSFT0004:00 06CB:CD98 Touchpad as /devices/platform/AMDI0010:00/i2c-0/i2c-MSFT0004:00/0018:06CB:CD98.0001/input/input14
hid-generic 0018:06CB:CD98.0001: input,hidraw0: I2C HID v1.00 Mouse [MSFT0004:00 06CB:CD98] on i2c-MSFT0004:00
i2c_designware AMDI0010:00: controller timed out
i2c_hid i2c-MSFT0004:00: failed to retrieve report from device.
i2c_designware AMDI0010:00: controller timed out
i2c_hid i2c-MSFT0004:00: failed to retrieve report from device.
i2c_designware AMDI0010:00: controller timed out
i2c_hid i2c-MSFT0004:00: failed to retrieve report from device.
i2c_designware AMDI0010:00: controller timed out
i2c_designware AMDI0010:00: controller timed out
i2c_hid i2c-MSFT0004:00: failed to retrieve report from device.
input: MSFT0004:00 06CB:CD98 Mouse as /devices/platform/AMDI0010:00/i2c-0/i2c-MSFT0004:00/0018:06CB:CD98.0001/input/input17
input: MSFT0004:00 06CB:CD98 Touchpad as /devices/platform/AMDI0010:00/i2c-0/i2c-MSFT0004:00/0018:06CB:CD98.0001/input/input18
hid-multitouch 0018:06CB:CD98.0001: input,hidraw0: I2C HID v1.00 Mouse [MSFT0004:00 06CB:CD98] on i2c-MSFT0004:00
i2c_designware AMDI0010:00: controller timed out
i2c_designware AMDI0010:00: controller timed out
i2c_hid i2c-MSFT0004:00: failed to set a report to device.

[mccricardo (mcc-ricardo)]

I bought this precise laptop last week and found the same issue. I've tried several approaches that I found in blogs/forums and tried several distros (Ubuntu 18.04, 19.10, 20.04), Debian 10, CentOS, and Arch. Also tried several Kernel versions (5.4.49, 5.6.19 and 5.7.6) and got nowhere.

[mccricardo (mcc-ricardo)]

Updated my ubuntu to kernel 5.8-rc4 and still nothing.

[TheTakylo (thetakylo)]

For me the touchpad has been working properly for weeks when it didn't work before.
The only problem is ... I didn't make it work, so I have no idea why it started working. But sometimes (rarely), it doesn't work and you have to turn the computer back on.

[peteole2707 (peteole2707-linux-kernel-bugs)]

Interestingly there are phases which last a few days where it works perfectly. I am wondering which events trigger these phases. Maybe some windows update which makes it go into another shutdown state? Or some updates deep in the kernel? It once changed after trying to install a dkms module to get virtualbox running...

[tim (tim-linux-kernel-bugs)]

Created attachment 290225
attachment-6042-0.html

In my case, the laptop is my son's. Tonight, I gave up on manjaro, and
installed ubuntu. Touchpad didn't work. Booted into windows ... and it also
didn't work (which was new, my son who has been using it for a week and
half has not seen this before). Was not visible in Device Manager, and
scanning for new hardware did not reveal anything. I could not find any
Lenovo drivers to download.. I rebooted a few times. No touchpad in
windows. But there was a BIOS update, (1.06 I think, from July 8, change
note says something about SI03 fixes). I applied that. Secure Boot was
reenabled, and the trackpad worked again in windows. But still no good in
Ubuntu. This is with mainline 5.7.8 and 5.8 RC4. The BIOS update readme
said nothing about touchpad, but it looks like flashing the BIOS fixed the
problem (in Windows).

On Sat, 11 Jul 2020 at 21:19, <email address hidden> wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=208171
>
> --- Comment #4 from Ole Petersen (<email address hidden>) ---
> Interestingly there are phases which last a few days where it works
> perfectly.
> I am wondering which events trigger these phases. Maybe some windows update
> which makes it go into another shutdown state? Or some updates deep in the
> kernel? It once changed after trying to install a dkms module to get
> virtualbox
> running...
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.

[Stanley Fernandes (stanleyfernandes)]

I've faced the same issue on Fedora 32, Ubuntu 20.04 and Pop OS 20.04. Don't know if it help just thought of sharing.
Let me know if I can help by uploading any logs. More than happy to help.

[Michael Amplatz (xekuta747)]

I have ordered another Lenovo Notebook with 15 ", but same type, for my wife. Hope the bug will be resolved soon, so she will allow me to install a Linux system.

[tim (tim-linux-kernel-bugs)]

I think that the touchpad can be reliably reset to a working state in either Windows or Linux by shutdown without AC power attached. In other circumstances, a restart can still leave the laptop with a non-working touchpad, including in Windows.

[Michael Amplatz (xekuta747)]

Ok, I have bought the 15 " Version (PF2891QY) for my wife. Same issue. https://forums.lenovo.com/t5/Other-Linux-Discussions/Touchpad-not-working-on-ideapad-5-14iil05/m-p/5019457

[Tommaso Guaita (tguaita)]

I had the same problem, the touchpad was not even recognised.
I changed the BIOS setting to "only UEFI" (no Legacy support) as suggested by gustavekkj.
Now it works! Or at least most of the time: sometimes when booting it stops working again, but (up until now) a reboot fixes the problem.

[TheTakylo (thetakylo)]

Same for me, it work but sometimes it doesnt work and i just need to reboot my computer to fix the problem

[Jan (jamowei)]

I use Ubuntu 20.04 with the latest Kernel 5.8-rc6 and still having this issue. I figured out that my touchpad only doesn't work when I boot up my laptop with power connector attached. When I'm working in battery mode it works great...

[Jan (jamowei)]

In battery mode my touchpad works with Kernel 5.8-rc6 and UEFI enabled.

[Jan (jamowei)]

In power connector mode my touchpad doesn't work on Kernel 5.8-rc6 and UEFI enabled.

[Jan (jamowei)]

Did anyone tried the latest BIOS Update from here: https://pcsupport.lenovo.com/de/de/products/laptops-and-netbooks/5-series/5-14iil05/downloads/DS543846

I don't know how to flash this from Ubuntu!? Maybe this fixes the issue...?

[Jan (jamowei)]

Ok, I updated my bios to the latest version DSCN27WW (from yesterday) but it didn't help... :/
But I can see less errors in dmesg log.

[Pedro Rodrigues (pedro-pfxr)]

Same problem here. Touchpad works on Windows after driver installation. Never worked on any linux distribution (tried Ubuntu 20.04, Fedora 32, Elementary OS Hera).
Some fix to this would be very welcome.

Additional info: Touch pad does not show up on "cat /proc/bus/input/devices"

[Fredrik Larsson (frla01)]

Have exactly the same problem in my ideapad5 14AER05.
The touchpad works under Windows but not at all when using ubuntu
The touch pad does not show up when using xinput

[alexmaras (alexmaras-linux-kernel-bugs)]

I have the same issue - am happy to help with logs or debug if needed. With either 5.7 or 5.8rc7, and with no dual-boot at all (linux only), the trackpad will sometimes fail to come up on boot.

The state will sometimes change when coming out of hibernation as well, without a full shutdown/reboot. Today, the trackpad wasn't working. After hibernating, waiting a while, then starting up again, it returned from hibernation successfully with a working trackpad.

[Jose H Isaza M (jhisaza)]

I installed Ubuntu Studio 20.04 in my laptop lenovo ideapad S145 and touchpad does not work at all

[Patrick Then (patrickthen)]

I'm also affected by this it seems (although currently using Manjaro).
Both Kernel 5.7.9 and 5.8rc5 result in the Touchpad randomly deciding not to work on boot.
If it works, everything seems fine, though.

On 5.7 Kernel, dmesg is spamming

i2c_designware AMDI0010:00: controller timed out

when the issue appears.

On top of it, sometimes it stops working after suspend, but I suspect this to be a different issue, as for that loggin out and back in again (no reboot or shutdown) seemed to fix it.

Frustrating, as the laptop is pretty nice otherwise and I would really love to use it without Windows.

[Patrick Then (patrickthen)]

My device is an IdeaPad 5 14 (14ARE05) with a Ryzen 5 4600U, btw.

[kxra (kxra-linux-kernel-bugs)]

Looping in some other discussion:
* https://bugs.launchpad.net/linux/+bug/1884981

[Tim Richardson (tim-richardson)]

device is an IdeaPad 5 14 (14ARE05) with a Ryzen 5 4600
Now on kernel 5.8

observation is that the touchpad sometimes doesn't work. So far, shutdown and remove AC then restart fixes it every time. This was true on 5.7 too.

Something goes wrong with hardware initialisation?

[Shekhar Nambi (shekhnam)]

I too have the same issue with my touchpad on Lenovo P72. Below are my details.

Linux P72 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

[Shekhar Nambi (shekhnam)]

For the time being I have solved it by connecting an external mouse and an extrenal mouse makes my mouse pointer work giving temporary relief.

[TheTakylo (thetakylo)]

someone have news about a fix ?

[TheTakylo (thetakylo)]

this solve the issue: https://askubuntu.com/questions/1220264/lenovo-ideapad-s145-touchpad-not-working/1266740#1266740

[Jazz (blaze2236)]

Hi, I'm having the same issue on my Ideapad 5 as well, but I have the AMD version. It does seem to work periodically.

          /:-------------:\ <email address hidden>
       :-------------------:: ----------------
     :-----------/shhOHbmp---:\ OS: Fedora 32 (Workstation Edition) x86_64
   /-----------omMMMNNNMMD ---: Host: 81YM IdeaPad 5 14ARE05
  :-----------sMMMMNMNMP. ---: Kernel: 5.7.15-200.fc32.x86_64
 :-----------:MMMdP------- ---\ Uptime: 59 mins
,------------:MMMd-------- ---: Packages: 1793 (rpm), 12 (flatpak)
:------------:MMMd------- .---: Shell: bash 5.0.17
:---- oNMMMMMMMMMNho .----: Resolution: 1920x1080
:-- .+shhhMMMmhhy++ .------/ DE: GNOME 3.36.5
:- -------:MMMd--------------: WM: Mutter
:- --------/MMMd-------------; WM Theme: Adwaita
:- ------/hMMMy------------: Theme: Adwaita [GTK2/3]
:-- :dMNdhhdNMMNo------------; Icons: Adwaita [GTK2/3]
:---:sdNMMMMNds:------------: Terminal: gnome-terminal
:------:://:-------------:: CPU: AMD Ryzen 7 4700U with Radeon Graphics (8) @ 2.000GHz
:---------------------:// GPU: AMD ATI 05:00.0 Renoir
                                     Memory: 2445MiB / 15433MiB

xinput list: (when 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)]

dmesg | grep touch when working otherwise nothing
[ 2.055799] hid-multitouch 0018:06CB:CD98.0002: input,hidraw1: I2C HID v1.00 Mouse [MSFT0004:00 06CB:CD98] on i2c-MSFT0004:00

[Kẏra (thekyriarchy)]

This is an isuse with the MSFT trackpad/touchpad mouse, not the laptop model or other hardware. The same issue affects the AMD version https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884981

> this solve the issue: https://askubuntu.com/questions/1220264/lenovo-ideapad-s145-touchpad-not-working/1266740#1266740

Really? That looks like elantech not microsoft. Is anyone else able to confirm?

[franlim (franlim)]

Thanks for changing the title. Finally it makes sense.

> this solve the issue: https://askubuntu.com/questions/1220264/lenovo-ideapad-s145-touchpad-not-working/1266740#1266740

Doesn't solve it for me. I have the AMD Ideapad 5-14. In fact it doesn't even boot with "pci=nocrs". No elan module is used.

[Michael Amplatz (xekuta747)]

The title makes no sense for me now.

On the two different Lenovo Notebooks I own the Touchpad didn't work any
time.

But, however, there is no usable solution anyway.

Am 23.08.20 um 21:55 schrieb franlim:
> Thanks for changing the title. Finally it makes sense.
>
>> this solve the issue: https://askubuntu.com/questions/1220264/lenovo-
> ideapad-s145-touchpad-not-working/1266740#1266740
>
> Doesn't solve it for me. I have the AMD Ideapad 5-14. In fact it doesn't
> even boot with "pci=nocrs". No elan module is used.
>

[melchiorre (melchiorre)]

I have a Ideapad 5 are15 and my touchpad didn't work. I followed instruction in this page https://bugzilla.kernel.org/show_bug.cgi?id=207759 and now it works (it fails only rarly)

[Michael Reutman (mreutman)]

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 someone.

[franlim (franlim)]

Hello Michael,

I don't know what these options do but if I use "pci=nocrs" my partitions aren't recognized (UUID not found) during boot. You have a 15 inch model, but you too have the "MSFT0004:00 06CB:CD98" touchpad?

[Jazz (blaze2236)]

@Michael,

Does your solution work consistently?

Someone shared a hack, if you power up the laptop while on Battery then the trackpad is recognized (about 90% of the time). Looking forward to a consistent solution.

[Michael Reutman (mreutman)]

@fanlim, my xinput looks like this when I use the kernel boot arguments.

$ xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ MSFT0001:01 04F3:3140 Touchpad id=10 [slave pointer (2)]
⎜ ↳ MSFT0001:01 04F3:3140 Mouse id=11 [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=9 [slave keyboard (3)]
    ↳ Ideapad extra buttons id=12 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=13 [slave keyboard (3)]

The MSFT0001:01 04F3:3140 entry was not appearing at all without the kernel arguments added.

@blaze2236, the solution I posted works consistently on my laptop regardless of whether or not it is running off battery or AC. My trackpad refused to work regardless of power source, only the kernel boot args made things work.

[franlim (franlim)]

Linux 5.9-rc4 "seems" to work on my machine (ideapad 5-14are w MSFT0004:00 06CB:CD98).Impossible to to know for sure due to the random nature of the bug. I'm on arch right now and used linux-mainline-5.9rc4-1. Maybe others can report back here after trying the new kernel. Then someone could look into changes made e.g. in hid-multitouch and i2c(hid).

[peteole2707 (peteole2707-linux-kernel-bugs)]

I just updated to 5.9rc1 and it seems that it fixed the issue. I have not hat a single failure since the update. However I am not sure due to the random behavior

[tim (tim-linux-kernel-bugs)]

We've been using 5.9rc since release, now on rc4. The problem is fixed.

[Ton Gur (kvantorrr)]

@Michael,

Thanks a lot for the tip, "i8042.nopnp=1 pci=nocrs" solves the problem with touchpad on two Lenovo Ideapad 3 15IIL05.

[bnewell (bnewell-u)]

82A4 IdeaPad Slim 7 14IIL05 Just arrived today.
Clean install of Windows 10 2004, everything works fine.
Installed Ubuntu 20.04.1, no trackpad, graphical artifacts like crazy. VERY sluggish.

Installed 5.9 after another forum member mentioned adding the grub arguement 'GRUB_CMDLINE_LINUX_DEFAULT="pci=nocrs quiet splash" but only after upgrading to 5.8+
This didn't help

BIOS: No secure boot

OS: Ubuntu 20.04.1 LTS x86_64
Host: 82A4 IdeaPad Slim 7 14IIL05
Kernel: 5.8.11-050811-generic
Shell: bash 5.0.17
Resolution: 1920x1080
DE: GNOME
CPU: Intel i7-1065G7 (8) @ 3.900GHz
GPU: Intel Iris Plus Graphics G7
GPU: NVIDIA GeForce MX350
Memory: 3065MiB / 15750MiB

sudo acpidump | grep -C3 ELAN
   29560: 00 03 06 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 ...INT1p. IDAD..
   29570: 53 42 46 53 53 42 46 49 00 5B 82 42 0E 54 50 44 SBFSSBFI.[.B.TPD
   29580: 31 08 5F 41 44 52 00 08 49 44 41 44 00 08 48 49 1._ADR..IDAD..HI
   29590: 44 32 00 08 5F 48 49 44 0D 45 4C 41 4E 30 30 30 D2.._HID.ELAN000
   295A0: 30 00 08 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 0.._CID.PNP0C50.
   295B0: 08 5F 55 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C ._UID..K._DSM..<
   295C0: 93 68 11 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 .h.......<gBUE..

I'm about to try "i8042.nopnp=1 pci=nocrs" and will report back.

[bnewell (bnewell-u)]

82A4 IdeaPad Slim 7 14IIL05 Just arrived today.
Clean install of Windows 10 2004, everything works fine.
Installed Ubuntu 20.04.1, no trackpad, graphical artifacts like crazy. VERY sluggish.

Installed 5.9 after another forum member mentioned adding the grub arguement 'GRUB_CMDLINE_LINUX_DEFAULT="pci=nocrs quiet splash" but only after upgrading to 5.8+
This didn't help

BIOS: No secure boot

OS: Ubuntu 20.04.1 LTS x86_64
Host: 82A4 IdeaPad Slim 7 14IIL05
Kernel: 5.8.11-050811-generic
Shell: bash 5.0.17
Resolution: 1920x1080
DE: GNOME
CPU: Intel i7-1065G7 (8) @ 3.900GHz
GPU: Intel Iris Plus Graphics G7
GPU: NVIDIA GeForce MX350
Memory: 3065MiB / 15750MiB

sudo acpidump | grep -C3 ELAN
   29560: 00 03 06 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 ...INT1p. IDAD..
   29570: 53 42 46 53 53 42 46 49 00 5B 82 42 0E 54 50 44 SBFSSBFI.[.B.TPD
   29580: 31 08 5F 41 44 52 00 08 49 44 41 44 00 08 48 49 1._ADR..IDAD..HI
   29590: 44 32 00 08 5F 48 49 44 0D 45 4C 41 4E 30 30 30 D2.._HID.ELAN000
   295A0: 30 00 08 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 0.._CID.PNP0C50.
   295B0: 08 5F 55 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C ._UID..K._DSM..<
   295C0: 93 68 11 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 .h.......<gBUE..

 "i8042.nopnp=1 pci=nocrs" did not help me. Attaching 'acpi.dump'

[bnewell (bnewell-u)]

Just installed 5.9rc6 booted up on battery only and touchpad is working but cannot reverse 2-finger scrolling direction. I'll just keep upgrading the kernel with every release to see what progress we make. It's still a heck of a Win10 laptop until this get worked out.

https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.9-rc6/amd64/

Whole system responsiveness is still laggy but I think that is may be due to Iris + Nvidia MX350 problems (open and proprietary drivers yield same results).

sudo acpidump | grep -C3 ELAN
   29560: 00 03 06 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 ...INT1p. IDAD..
   29570: 53 42 46 53 53 42 46 49 00 5B 82 42 0E 54 50 44 SBFSSBFI.[.B.TPD
   29580: 31 08 5F 41 44 52 00 08 49 44 41 44 00 08 48 49 1._ADR..IDAD..HI
   29590: 44 32 00 08 5F 48 49 44 0D 45 4C 41 4E 30 30 30 D2.._HID.ELAN000
   295A0: 30 00 08 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 0.._CID.PNP0C50.
   295B0: 08 5F 55 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C ._UID..K._DSM..<
   295C0: 93 68 11 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 .h.......<gBUE..

xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ SYNA2B5A:00 06CB:CDB0 Mouse id=13 [slave pointer (2)]
⎜ ↳ SYNA2B5A:00 06CB:CDB0 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)]
    ↳ Video Bus id=8 [slave keyboard (3)]
    ↳ Power Button id=9 [slave keyboard (3)]
    ↳ Sleep Button id=10 [slave keyboard (3)]
    ↳ Integrated Camera: Integrated C id=11 [slave keyboard (3)]
    ↳ Integrated Camera: Integrated I id=12 [slave keyboard (3)]
    ↳ Ideapad extra buttons id=15 [slave keyboard (3)]
    ↳ Intel HID events id=16 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=17 [slave keyboard (3)]

lspci
00:00.0 Host bridge: Intel Corporation Device 8a12 (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Iris Plus Graphics G7 (rev 07)
00:04.0 Signal processing controller: Intel Corporation Device 8a03 (rev 03)
00:07.0 PCI bridge: Intel Corporation Ice Lake Thunderbolt 3 PCI Express Root Port #0 (rev 03)
00:0d.0 USB controller: Intel Corporation Ice Lake Thunderbolt 3 USB Controller (rev 03)
00:0d.2 System peripheral: Intel Corporation Ice Lake Thunderbolt 3 NHI #0 (rev 03)
00:12.0 Serial controller: Intel Corporation Device 34fc (rev 30)
00:14.0 USB controller: Intel Corporation Ice Lake-LP USB 3.1 xHCI Host Controller (rev 30)
00:14.2 RAM memory: Intel Corporation Device 34ef (rev 30)
00:14.3 Network controller: Intel Corporation Killer Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW) (rev 30)
00:15.0 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP Serial IO I2C Controller #0 (rev 30)
00:15.1 Serial ...

[Knobik (knobiks)]

Lenovo Ideapad 5 14are05.
CPU: Ryzen 7 4700u.
BIOS: 1.06 (latest, on date of posting)
System: Ubuntu 20.04 (kernel 5.4.0-48-generic)
Touchpad reported by dmesg: MSFT0004:00 06CB:CD98

Im attacking a tarball with full dmesg and acpi dumps for both working and broken states.

In the broken state, some funky stuff is happening with the i2c_hid, but in the end it somehow it still recognized the touchpad as a mouse (but it did not work in the system). Everything is in the logs.

[gaoqi7 (gaoqi7)]

There are some good news happened on Lenovo Legion-5 15ARH05 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887190, Hope we will fix this soon :) Thanks all.

[Michael Amplatz (xekuta747)]

Come on, we just wait for half a year now. No reason to urge :-D

Am 29.09.20 um 18:51 schrieb gaoqi7:
> There are some good news happened on Lenovo Legion-5 15ARH05
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887190, Hope we
> will fix this soon :) Thanks all.
>

[matteo.mazzarelli (matteo.mazzarelli-linux-kernel-bugs)]

Note that the problem hasn't been fully fixed. It still persists when going out of S3 deep sleep (suspend) mode - i.e. it's random whether it will work or not when resuming. I can however confirm that running 5.9-rc6 the touchpad always works as expected on a new start or on a reboot.

[Romano (roxibar73)]

Hi everyone, I found the solution, it seems to work, I have tried to restart, shut down, more than 15 times and it always works.
follow the guide:

https://forum.ubuntuusers.de/topic/touchpad-lenovo-ideapad-5-funktioniert-nicht/

[Volker Meyer (vlhm)]

Hi,

"i8042.nopnp=1 pci=nocrs" also works with Lenovo V17-IIL.

Thanks

[Felix T (crvn)]

Touchpad stopped working for me after updating BIOS to latest version DTCN24WW (V1.10). I tried changing several BIOS settings with no success and the device is not listed in xinput.

I stumbled across these messages in dmesg, but I can't tell if this has something to do with the issue.

...
[ 0.432538] platform USBC000:00: failed to claim resource 0: [mem 0xffffffff-0x100000ffe]
[ 0.432546] fbcon: Taking over console
[ 0.432548] acpi USBC000:00: platform device creation failed: -16
...

[Hans de Goede (j-w-r-degoede)]

I've been debugging a similar issue together with a Fedora user:
https://bugzilla.redhat.com/show_bug.cgi?id=1871793
(note this bug is set to private atm, so you can likely not view this, I've asked the reporter if it is ok to open it up)

I see some comments here about things no longer working after a BIOS upgrade, here is what I wrote about this in the Fedora bug:

"Sometimes BIOS upgrades don't clear the BIOS settings even though they should, causing the new BIOS to interpret the binary settings blob from the old BIOS in the wrong way. This may also cause hidden settings to be wrong.

Have you tried loading the BIOS default or optimal settings?"

And it turns out that on the reporters "Lenovo IdeaPad 5 14IIL05" the fix for this issue is the combination of:

1. Install the latest BIOS
2. Enter setup, load default or optimal settings.
3. Save settings, reboot

Please give this a try and if this works, please let us know that this helped.

If you are adding a comment about this helping or not, it would also be useful to know:

1. If you tried "pci=nocrs" with older BIOS versions and if that helped with the older BIOS
2. If you are still using "pci=nocrs" with the newer BIOS
3. If you are still using "pci=nocrs" with the newer BIOS, please try removing "pci=nocrs" from the kernel commandline, do things still work?

Note for the Fedora reporter things worked with:

1. The old BIOS + "pci=nocrs"
2. The new BIOS + default-settings-load without needing "pci=nocrs"

[Felix T (crvn)]

Thank you for your response. I did in fact load and reboot with BIOS defaults multiple times while trying out different settings without success.

After many trials and errors I am currently running BIOS 1.06 with mainline kernel 5.10 and everything is working fine (without GRUB parameters).

Even though my understanding of this issue is superficial at best, my suspicion is that Windows dual boot might be interfering even with disabled fast boot. So one of the things I tried was a forced Windows shutdown with "shutdown /s /f /t 0". This seemed to resolve my issue but it's entirely speculative.

Since I do need this laptop for work from time to time, I am hestitant to try updating the BIOS again and see if I can get the latest version running.

I hope this is helpful in any way.

[Michael Amplatz (xekuta747)]

The first problem is that a BIOS-Update is only delivered as an EXE-file
for Windows 10.

Does this work with WINE?

Am 19.02.21 um 12:05 schrieb Hans de Goede:
> I've been debugging a similar issue together with a Fedora user:
> https://bugzilla.redhat.com/show_bug.cgi?id=1871793
> (note this bug is set to private atm, so you can likely not view this, I've asked the reporter if it is ok to open it up)
>
> I see some comments here about things no longer working after a BIOS
> upgrade, here is what I wrote about this in the Fedora bug:
>
> "Sometimes BIOS upgrades don't clear the BIOS settings even though they
> should, causing the new BIOS to interpret the binary settings blob from
> the old BIOS in the wrong way. This may also cause hidden settings to be
> wrong.
>
> Have you tried loading the BIOS default or optimal settings?"
>
> And it turns out that on the reporters "Lenovo IdeaPad 5 14IIL05" the
> fix for this issue is the combination of:
>
> 1. Install the latest BIOS
> 2. Enter setup, load default or optimal settings.
> 3. Save settings, reboot
>
> Please give this a try and if this works, please let us know that this
> helped.
>
> If you are adding a comment about this helping or not, it would also be
> useful to know:
>
> 1. If you tried "pci=nocrs" with older BIOS versions and if that helped with the older BIOS
> 2. If you are still using "pci=nocrs" with the newer BIOS
> 3. If you are still using "pci=nocrs" with the newer BIOS, please try removing "pci=nocrs" from the kernel commandline, do things still work?
>
> Note for the Fedora reporter things worked with:
>
> 1. The old BIOS + "pci=nocrs"
> 2. The new BIOS + default-settings-load without needing "pci=nocrs"
>
>
> ** Bug watch added: Red Hat Bugzilla #1871793
> https://bugzilla.redhat.com/show_bug.cgi?id=1871793
>

[marius.andreiana (marius.andreiana-linux-kernel-bugs)]

Same issue on lenovo ideapad 5 14ARE05
Linux fedora 5.11.3-300.fc34.x86_64 #1 SMP

# dmesg | grep i2c
[ 1.569895] i2c_hid i2c-MSFT0004:00: HID over i2c has not been provided an Int IRQ
[ 1.569930] i2c_hid: probe of i2c-MSFT0004:00 failed with error -22

[Petteri P (petterip)]

Hi, I have just run into the same random touchpad problem as others with my Lenovo Ideapad 5 14are05 running on Ubuntu 20.04 with kernel 5.8.0-50-generic.

I would like to ask what is the status with this issue?

[Michael Amplatz (xekuta747)]

Tried Ubuntu 21.04 today. Still does not work, neither with 14IIL05, nor
with V15-IIL. Waiting for about one year now.

Am 25.04.21 um 10:16 schrieb Petteri P:
> Hi, I have just run into the same random touchpad problem as others with
> my Lenovo Ideapad 5 14are05 running on Ubuntu 20.04 with kernel
> 5.8.0-50-generic.
>
> I would like to ask what is the status with this issue?
>

[Hans de Goede (j-w-r-degoede)]

Hi All,

So this is a bit of a mess which I'm trying to sort out ATM, there are at least 4 different issues with Ideapad touchpads that I'm aware of:

1. There was a Linux ACPI issue where the resource-list (_CRS) for the touchpad given to Linux was not correct, this has been fixed for a while now by these 2 commits from me:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=21653a4181ff292480599dad996a2b759ccf050f
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8058d69905058ec8f467a120b5ec5bb831ea67f3
These commits should be in recent Ubuntu kernels so if you are still seeing issues then this issue was not the root cause for your laptop model.

2. On some Ideapad models the elants_i2c driver takes control of handling the touchpad, but the touchpad does not talk the elants protocol at all, it uses the standard I2C-HID protocol so this does not work. If adding "initcall_blacklist=elants_i2c_driver_init" to your kernel commandline fixes things, then your Ideapad model is hit by this. This is fixed now by this commit from me:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=65299e8bfb24774e6340e93ae49f6626598917c8
This commit was added to the 5.10.y and 5.12.y stable kernel series a couple of days ago, so hopefully it will get added to the Ubuntu kernels soon too.

3. On some Ideapads the BIOS seems to corrupt its own settings (often after a BIOS update) and as a result of this the BIOS is returning bogus addresses (NULL or 0xffffffff) as base-address from the ACPI _CRS call for some PCI devices, including the I2C controller connected to the touchpad. If adding "pci=nocrs" as a workaround helps then your model Ideapad is affected by this issue.

4. On some Ideapads something goes wrong with the OSYS code in the ACPI tables, this code is responsible for detecting which Windows version the ACPI tables think they are dealing with (or which Windows version Linux mimicks in case you are running Linux). To see if your Ideapad is affected by this issue try running:
"cat /sys/bus/acpi/devices/XXXX0000\:00/status"
from a terminal, if the output of this command is "15" then your model is affected by this issue. At least the "Lenovo Thinkbook 14-ILL" is known to be affected by this. The exact root cause of this is unknown atm. If your laptop is affected by this please run "acpidump -o acpidump" and attach the acpidump here, in combination with specifying the exact model of your laptop.

[Hans de Goede (j-w-r-degoede)]

Since root-cause 1/4 and 2/4 (of the 4 known root causes, see previous comment) are fixed now I would like to focus on further researching root-cause 3/4.

If adding "pci=nocrs" as a workaround helps to get your touchpad working then please do the following:

1. Boot *without* "pci=nocrs" on the kernel commandline (you can e.g. use the edit option in the grub-menu and remove it from the commandline for 1 boot that way. Then run: "dmesg > dmesg.without-nocrs" in a terminal.

2. Boot with "pci=nocrs" on the kernel commandline and then run: "dmesg > dmesg.with-nocrs" in a terminal.

3. Try entering your BIOS setup screen, then select "load optimized defaults" and then "save-and-exit" and check if you still need the "pci=nocrs" workaround after this. Note do this after collecting the 2 dmesg files please.

4. Attach both dmesg files here, in combination with specifying the exact model of your laptop; and also specify if loading + saving the BIOS defaults helped or not.

The goal here is to gather enough info about this problem to hopefully be able to come up with a workaround, e.g. automatically behave as if pci=nocrs is passed for devices where _CRS returns NULL or 0xffffffff as base-address.

[Ratul Saha (thatanonyg)]

@j-w-r-degoede I will get on that and attach the logs. I am on a Lenovo ideapad 3 15iil05. This is a weird issue and I will also provide the journalctl without pci=nocrs as I found something weird there. More info in the next comment. Thanks for researching this.

PS: Another thing I experienced is that every time I ran Ubuntu or PopOS with `i8042.nopnp=1 pci=nocrs` 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.

[Ratul Saha (thatanonyg)]

I ran the tests and got the following results.

1. I have attached the dmesg file without enabling nocrs. (did not work)
2. I have attached the dmesg file with `i8042.nopnp=1 pci=nocrs`. (worked fine)
3. I have attached the dmesg file with `pci=nocrs` (no i8042.nopnp) (stability issues)

Loading and saving default BIOS settings did not work for me.

In the 3rd case, I experienced some stability issues with my system. Things crashed randomly and even had re-login because the whole session crashed once.

Laptop model: Lenovo ideapad 3 15iil05
Touchpad ID according to acpidump: 28D10

[Petteri P (petterip)]

So glad someone is on to this. I would like to help in testing, but I have very little knowledge in this area. I am running Lenovo Ideapad 5 14are05 on Ubuntu 20.04 with kernel 5.8.0-50-generic.

As an example regarding 3/4 where exactly should I add the "pci=nocrs" or regarding 4/4 what should I replace "XXXX0000" in order to run the cat command?

[Oscar Parada (oparada1988)]

I have the same laptop Ideapad 5 14are05, I can confirm that under a new installation of Ubuntu 20.04.2 with Kernel 5.8.55 the laptop still not work.

[Hans de Goede (j-w-r-degoede)]

@petterip:

> regarding 3/4 where exactly should I add the "pci=nocrs"

You should add this to the kernel commandline, see:
https://wiki.ubuntu.com/Kernel/KernelBootParameters

> regarding 4/4 what should I replace "XXXX0000" in order to run the cat command?

You should not replace it; on laptop models which are actually affected by this bug there is actually a directory path containing "XXXX0000", if you get a no such file or directory error then your laptop model is not affected by this issue.

[Hans de Goede (j-w-r-degoede)]

@thatanonyg, thank you for the logs

@thatanonyg, and everyone else for who adding "pci=nocrs" to the kernel commandline helps. I think I've figured out what is going on here and the patch which I'm attach should help, but it needs to be tested.

If you can build a kernel with this patch added and test that without "pci=nocrs" on the kernel commandline that would be great. Please also try dropping the "i8042=nopnp" kernel commandline option (that you need this is weird, but hopefully the patch + removing "pci=nocrs" from the cmdline helps).

[Hans de Goede (j-w-r-degoede)]

Ubuntu devs, if one of you could build a test-kernel with the patch added for reporters to test, then that would be great.

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "[PATCH] PCI/ACPI: Make acpi_pci_root_validate_resources() reject IOMEM resources which start at address 0" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

[Oscar Parada (oparada1988)]

Ditto, if an Ubuntu Dev can build a test kernel with the patch I would be happy to throw it into my installation.

[Petteri P (petterip)]

Thanks for the instructions. So I added the line GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=nocrs" and updated grub. I rebooted the machine at least five times and the touchpad never worked - I had to use an external mouse. This is a bit different in a sense that this seems to be consistent whereas usually the touchpad completely randomly works every now and then.

I think I will keep the settings as they are just to see if the touchpad randomly starts to work again. I mean the position of the moon might have an effect on this ;-)

Let me know if I can be of any help in further testing.

Btw, my kernel was just updated to 5.8.0-55-generic.

[Petteri P (petterip)]

Regarding my previous post what happened is that the touchpad started to work again out of the blue. Before this the system had difficulties to shutdown. The shutdwown process lasted for minutes and during that the system displayed a message "i2c_designware AMDI0010:00: controller times out". This lasted for a long time. So long that I had time to take a photo of it which is attached.

Eventually the system managed to shutdown and now I that I turned on the system the touchpad works again. Bizarre.

[Petteri P (petterip)]

Here is the dmesg output as well.

[Bernhard Übelacker (bernhardu)]

I can report that this device seems also affected:
Lenovo V15-IIL Iron Grey, Core i5-1035G1, 8GB RAM, 512GB SSD, DE (82C500JUGE)

This is with running a Debian testing kernel 5.10.0-7-amd64/5.10.40-1.

Adding the pci=nocrs makes the touchpad work, but unfortunately this does
not survive a standby or hibernate cycle.

@j-w-r-degoede: Do you still need your patch to be tested?

[Hans de Goede (j-w-r-degoede)]

Bernhard, no in the mean time I've learned that my patch is no good. I'm currently debugging this with a Fedora user who also needs pci=nocrs to get the touchpad to work:
https://bugzilla.redhat.com/show_bug.cgi?id=1868899

But this is going quite slow because the cycle between me providing the user with a kernel with some extra debugging logging added; and me getting a dmesg output for that test kernel back is quite slow.

[Ratul Saha (thatanonyg)]

@Hans de Goede (j-w-r-degoede) is the patch working for Ideapad 3 15iil05? Then I would compile a kernel myself and test it on my laptop.

[Hans de Goede (j-w-r-degoede)]

Ratul, the patch which I attached won 't help you. The patch is basically no good, because the problem is not what I thought it was.

[Hans de Goede (j-w-r-degoede)]

I've been working with a Fedora reporter to try and solve the case where pci=nocrs helps to get a working touchpad, see:
https://bugzilla.redhat.com/show_bug.cgi?id=1868899

Thanks to the latest set of logs attached there, I now am finally starting to understand what is going on here.

Your BIOS claims that any memory between 0x000000004bc50000-0x00000000cfffffff is reserved:

[ 0.000000] BIOS-e820: [mem 0x000000004bc50000-0x00000000cfffffff] reserved

But then continuous with placing the iomem window for PCI devices inside that reserved range:

[ 0.609988] pci_bus 0000:00: root bus resource [mem 0x65400000-0xbfffffff window]

This confuses the kernel and makes it unable to assign PCI iomem to devices which have not already been assigned iomem by the BIOS, like the I2C-controller used for the touchpad.

If you are interested in / curious about the low level details, I'm discussing this with the kernel PCI developers (including figuring out how to deal with this) here:
https://<email address hidden>/

[Jayden (jayden99)]

@Hans de Goede Hi, I am using lenovo Ideapad 5 14IIL05 also. After I installed ubuntu 20.04,I can't even boot the ubuntu, I stuck at the black screen with blinking underscore. Is there anything I can do to solve this? I try to use ctrl alt f1 to f10 but no respond from ubuntu. Thanks in advance for your help.

[Michael Amplatz (xekuta747)]

@Jayden: Did you verify the image? Ubuntu 20.04 worked on my 14IIL05, of
course without touchpad. I know that all that is something off topic,
but we should clarify that very fast, so we know, if Jaydens Problem has
something to do with the Touchpad problem.

Am 08.07.21 um 04:27 schrieb Jayden:
> @Hans de Goede Hi, I am using lenovo Ideapad 5 14IIL05 also. After I
> installed ubuntu 20.04,I can't even boot the ubuntu, I stuck at the
> black screen with blinking underscore. Is there anything I can do to
> solve this? I try to use ctrl alt f1 to f10 but no respond from ubuntu.
> Thanks in advance for your help.
>

[Michael Amplatz (xekuta747)]

As this bug exists for more than a year now, it would be great if we
could re-activate Bluetooth-Mice with Keybord only after they say
goodbye occasionally.

[Jayden (jayden99)]

Hi. I did verify the image. Now, I manage to get through the black screen by using win+fn+f2 to go to tty2 then win+fn+f1 to go to login screen. Sometimes if it stuck at black screen, I would use the method mentioned above. Sometimes it manage to get to the login screen directly. But I do think this issue has sth to do with the touchpad. Cuz I will see the error messages controller timeout when I shut the system down (if the touchpad is nit working). For my laptop, the touchpad works sometimes while sometimes it doesn't.

[Ratul Saha (thatanonyg)]

Can we get a fix after over a year now? I think we have enough people suffering to deserve a fix for this bug.

[Abhijit (abhi-ghsh)]

I had similar issue.

Lenovo Ideapad 5 14ARE05 dual boot Windows 10 and Ubuntu 20.04 (Kernel 5.11 after update)

Solution steps:

(1) Update your Ubuntu 20.04 installation with all the latest update. This should update your Kernel too (mine updated to 5.11).

(2) Reboot

(3) Go to Windows 10 and Download and install Latest BIOS update and install it. In my case BIOS updated from V1.09 to 1.10.
***Be careful and pay close attention to the instructions shown by the BIOS update installer. Ideally you should fully charge your laptop before performing BIOS update and keep your charger connected.***

Running BIOS update will reboot your system and change BIOS settings to default. If you had disabled secure boot to install and dual boot Ubuntu then this will enable secure boot option. You will need to disable it again. Once BIOS update is completed reboot and go to BIOS (F2)

(4) Disable secure boot in BIOS again

(5) Boot to Ubuntu. (Tip: Use F12 key to boot to Ubuntu if you do not get Ubuntu Grub Bootloader Menu. You can change the boot order from BIOS settings (F2) permanently)

Your touchpad should start working.

[Petteri P (petterip)]

I am not sure what has happened with my Ideapad 5-14ARE05 laptop, but it just seems that this problem has disappeared. I assume some update fixed it finally.

I am unning 5.11.0-34-generic #36~20.04.1-Ubuntu

I have many other problems with the machine such as it does not suspend when the lid is closed and behaves strangely with my bluetooth headset. This laptop with Linux has really worn me out...

[Hans de Goede (j-w-r-degoede)]

This is a follow-up to comment #123

Sorry for the long silence on this bug. I was hoping one of the upstream pci-subsys devs would help out with this...

Since that did not happen I've been looking into fixing this myself now. I've come up with a solution which still involves a kernel cmdline option for now, but this one is a much smaller hammer (almost a scalpel) and once it is confirmed that this works I can enable this by default through a DMI quirk.

I also hope that this option will not cause the stability issues seen when using pci=nocrs and that it will remove the need to specify i8042.nopnp=1 .

I'll attach my patch here and then hopefully one of the Ubuntu devs can build a test-kernel for people who need pci=nocrs to test.

Alternatively you can build your own kernel with this patch added, see the Ubuntu docs for how to do this.

Once you have a kernel with this patch, remove pci=nocrs and i8042.nopnp=1 from the kernel-commandline and instead add only "pci=no_e820".

If this helps please provide DMI strings for your laptop, so that I can add a quirk to the kernel to automatically enable "pci=no_e820" on your laptop model. Run the following command *as normal user* to collect the DMI strings for your laptop:

grep . /sys/class/dmi/id/* 2> /dev/null

And copy and paste the output here.

[Hans de Goede (j-w-r-degoede)]

Please test a kernel build with this patch, combined with adding "pci=no_e820" added to the kernel commandline. See comment 133 for more details.

[Kai-Heng Feng (kaihengfeng)]

A test kernel with the patch can be found here:
https://people.canonical.com/~khfeng/lp1878279/

[Hans de Goede (j-w-r-degoede)]

Kai-Heng, thank you for providing the test kernel.

Folks, if you need to add pci=nocrs to your kernel-commandline to get your touchpad to work, please test this kernel:

https://people.canonical.com/~khfeng/lp1878279/

With pci=no_e820 on the kernel commandline (replacing pci=nocrs). If the touchpad works this way, please provide DMI strings for your laptop, so that I can add a quirk to the kernel to automatically enable "pci=no_e820" on your laptop model. Run the following command *as normal user* to collect the DMI strings for your laptop:

grep . /sys/class/dmi/id/* 2> /dev/null

And copy and paste the output here.

[Noctis Bennington (noctis13)]

Hello there.

the pci=nocrs on Ubuntu 22.04 doesn't allow boot. So this is again a problem in the last LTS (22.04).

[Michael Amplatz (xekuta747)]

It has never been no problem. A bug that can be solved by a workaround
that works most times with many people is not solved.

In my opinion the case can be closed when the new Touchpad used by
Lenovo works after booting into the official image. I am waiting for
that for two years now on different Notebooks.

Am 26.04.22 um 22:11 schrieb Noctis Bennington:
> Hello there.
>
> the pci=nocrs on Ubuntu 22.04 doesn't allow boot. So this is again a
> problem in the last LTS (22.04).
>

[Noctis Bennington (noctis13)]

Yeah...I'm agree Michael. At least in 20.04 that workaround was working with me and a lot of users (but as I said, I'm agree with you). Now in 22.04 it's impossible to make it works. Let's see if we can do something about it...

[Noctis Bennington (noctis13)]

PS: In case you need see what's going on with pci=nocrs on 22.04

https://i.stack.imgur.com/KZtIy.jpg

[Noctis Bennington (noctis13)]

Hi! @Hans de Goede @j-w-r-degoede

I tested that patch in that kernel (5.14) and it definitely works!

This is the info I received with "grep . /sys/class/dmi/id/* 2> /dev/null"

/sys/class/dmi/id/bios_date:01/28/2022
/sys/class/dmi/id/bios_release:1.52
/sys/class/dmi/id/bios_vendor:LENOVO
/sys/class/dmi/id/bios_version:EMCN52WW
/sys/class/dmi/id/board_asset_tag:NO Asset Tag
/sys/class/dmi/id/board_name:LNVNB161216
/sys/class/dmi/id/board_vendor:LENOVO
/sys/class/dmi/id/board_version: NO DPK
/sys/class/dmi/id/chassis_asset_tag:NO Asset Tag
/sys/class/dmi/id/chassis_type:10
/sys/class/dmi/id/chassis_vendor:LENOVO
/sys/class/dmi/id/chassis_version:IdeaPad 3 15IIL05
/sys/class/dmi/id/ec_firmware_release:1.52
/sys/class/dmi/id/modalias:dmi:bvnLENOVO:bvrEMCN52WW:bd01/28/2022:br1.52:efr1.52:svnLENOVO:pn81WE:pvrIdeaPad315IIL05:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPad315IIL05:skuLENOVO_MT_81WE_BU_idea_FM_IdeaPad315IIL05:
/sys/class/dmi/id/product_family:IdeaPad 3 15IIL05
/sys/class/dmi/id/product_name:81WE
/sys/class/dmi/id/product_sku:LENOVO_MT_81WE_BU_idea_FM_IdeaPad 3 15IIL05
/sys/class/dmi/id/product_version:IdeaPad 3 15IIL05
/sys/class/dmi/id/sys_vendor:LENOVO
/sys/class/dmi/id/uevent:MODALIAS=dmi:bvnLENOVO:bvrEMCN52WW:bd01/28/2022:br1.52:efr1.52:svnLENOVO:pn81WE:pvrIdeaPad315IIL05:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPad315IIL05:skuLENOVO_MT_81WE_BU_idea_FM_IdeaPad315IIL05:

[Hans de Goede (j-w-r-degoede)]

Sorry that it is taking so long to fix this. There have been several attempts at fixing this upstream already, but all of them had to be reverted/dropped because they were causing issues on other laptop models.

The latest attempt at fixing this is here:
https://<email address hidden>/

And this patch, or something close to it will hopefully go upstream soon.

Perhaps one of the Ubuntu kernel devs can provide a test kernel with this patch for Ubuntu users with this problem to test?

[Noctis Bennington (noctis13)]

It could be awesome if some of the Ubuntu Kernel devs help us to test the 5.15 kernel with the patch.

I wanna try to build a custom kernel with the patch but I don't have time and I'm not an expert with it.

Someone can help us with this?

[Hans de Goede (j-w-r-degoede)]

Note if someone wants to build a kernel with:
https://<email address hidden>/

This patch applies on top of the 3 patches from:
https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git/log/?h=pci/resource

[tinozzo123 (tinozzo123-linux-kernel-bugs)]

I have the same laptop, and while on Linux 5.17 I never witnessed the touchpad fail "randomly", I found a consistent way to make it fail: suspend the computer, close the lid, and wake it up while the lid is closed (a way to do so is by plugging/unplugging the charger).
Et voilà, the touchpad won't work, but it will work again by suspending the computer another time and waking it up with the lid open.

[Noctis Bennington (noctis13)]

I tried with pci=nocrs on Linux 5.18 and now it works, just to let you know.

[Michael Amplatz (xekuta747)]

I had an update yesterday on Ubuntu 20.04.5. Today I recognized that the
Touchpad works. SOLVED!!!

After 2,5 years I am lucky.

Michael Amplatz

Am 05.06.22 um 19:18 schrieb Noctis Bennington:
> I tried with pci=nocrs on Linux 5.18 and now it works, just to let you
> know.
>

[Bjorn Helgaas (bjorn-helgaas)]

The current upstream resolution to this problem is https://git.kernel.org/linus/d341838d776a ("x86/PCI: Disable E820 reserved region clipping via quirks"), which relies on quirks that match DMI Vendor, Product Version, Product Name, and Board Name. This isn't an ideal solution because there are likely other systems we don't know about that need a similar fix.

The patch I'm attaching here is an experimental idea to work around this issue without the maintenance burden of the quirks.

If anybody would be willing to test this patch, I would be very grateful. To test it, apply this patch to your kernel, boot with "pci=use_e820 efi=debug", and collect the dmesg log.

[bjorn (bjorn-linux-kernel-bugs)]

I think this is caused by the PCI core not assigning space for a device leading to the touchpad, the same as bug 216565.

You probably see a line like this in the dmesg log:

  pci 0000:00:15.0: BAR 0: no space for [mem size 0x00001000 64bit]

On Ideapads, it should be fixed by https://git.kernel.org/linus/d341838d776a ("x86/PCI: Disable E820 reserved region clipping via quirks"), which appeared in v5.19.

The patch at https://bugzilla.kernel.org/attachment.cgi?id=303237 should fix other machines. If you test this patch, I'd appreciate a note about whether it works and what machine it was.

[Bjorn Helgaas (bjorn-helgaas)]

N.B. Comment #149 came from bugzilla.kernel.org, NOT from launchpad, and the bug 216565 mentioned is a kernel.org bug number: https://bugzilla.kernel.org/show_bug.cgi?id=216565.

Launchpad mistakenly linkified "bug 216565" it to an unrelated launchpad bug with the same number.

[tinozzo123 (tinozzo123-linux-kernel-bugs)]

I wrote before that on my Lenovo IdeaPad 5 14ARE05 I never got my touchpad failing randomly.
I did write however that by plugging/unplugging the charger the laptop would wake up from suspend, and if done while the lid was closed, then the touchpad would stop working until you suspend and wake up the laptop again.
On kernel 6.2, though, plugging/unplugging the charger doesn't wake up the laptop anymore (or, to be more precise, it does wake it up, but then it puts it back to sleep immediately after), meaning I don't experience this bug in any form anymore.

[bjorn (bjorn-linux-kernel-bugs)]

(In reply to tinozzo123 from comment #15)
> ... meaning I don't experience this bug in
> any form anymore.

Thanks very much for testing this out and reporting the results! Please don't hesitate to report any other issues you trip over!

I'm going to close this issue as "resolved" by these commits:

  https://git.kernel.org/linus/d341838d776a ("x86/PCI: Disable E820 reserved region clipping via quirks") (appeared in v5.19)
  https://git.kernel.org/linus/07eab0901ede ("efi/x86: Remove EfiMemoryMappedIO from E820 map") (appeared in v6.2)

If anybody still sees this issue with v6.2 or later, please re-open this and attach the complete dmesg log when booted with "efi=debug".

[radupantiru (radupantiru-linux-kernel-bugs)]

I am having the same issue. Will enable "efi=boot" hopefully to capture more logs.

root@r-laptop ~]# uname -a
Linux r-laptop 6.5.9-arch2-1 #1 SMP PREEMPT_DYNAMIC Thu, 26 Oct 2023 00:52:20 +0000 x86_64 GNU/Linux

Nov 17 18:11:24 r-laptop kernel: i2c_designware AMDI0010:00: controller timed out
Nov 17 18:11:24 r-laptop systemd[1]: Using hardware watchdog 'SP5100 TCO timer', version 0, device /dev/watchdog0
Nov 17 18:11:24 r-laptop systemd[1]: Watchdog running with a timeout of 10min.
Nov 17 18:11:24 r-laptop kernel: watchdog: watchdog0: watchdog did not stop!

[bjorn (bjorn-linux-kernel-bugs)]

radupantiru@: could you also capture the "acpidump" output, please?

We have a couple other reports like https://bugzilla.kernel.org/show_bug.cgi?id=218050 that seem related to 07eab0901ede ("efi/x86: Remove EfiMemoryMappedIO from E820 map").

[radupantiru (radupantiru-linux-kernel-bugs)]

Created attachment 305416
acpidump.txt

There you are and thanks for looking into this!

On Fri, Nov 17, 2023 at 7:02 PM <email address hidden> wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=208171
>
> Bjorn Helgaas (<email address hidden>) changed:
>
> What |Removed |Added
>
> ----------------------------------------------------------------------------
> Status|RESOLVED |REOPENED
> Resolution|CODE_FIX |---
>
> --- Comment #18 from Bjorn Helgaas (<email address hidden>) ---
> radupantiru@: could you also capture the "acpidump" output, please?
>
> We have a couple other reports like
> https://bugzilla.kernel.org/show_bug.cgi?id=218050 that seem related to
> 07eab0901ede ("efi/x86: Remove EfiMemoryMappedIO from E820 map").
>
> --
> You may reply to this email to add a comment.
>
> You are receiving this mail because:
> You are on the CC list for the bug.

[bjorn (bjorn-linux-kernel-bugs)]

radupantiru@: Your MCFG says there's ECAM space at [mem 0xf8000000-0xfbffffff] for [bus 00-3f]. That space *should* be reserved via a PNP0C01 or PNP0C02 device in the ACPI namespace, but it isn't, so this is likely a BIOS defect.

Can you try the patch I attached here? https://bugzilla.kernel.org/show_bug.cgi?id=218050#c6 . If you can, please attach the dmesg log here.

[radupantiru (radupantiru-linux-kernel-bugs)]

Created attachment 305462
dmesg-patched

Hello,

This is the dmesg for the patched kernel.
6.5.9-arch2-1-custom #1 SMP PREEMPT_DYNAMIC Tue, 21 Nov 2023 17:01:41 +0000
x86_64 GNU/Linux

Thank you!

On Mon, Nov 20, 2023 at 11:21 PM <email address hidden> wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=208171
>
> --- Comment #20 from Bjorn Helgaas (<email address hidden>) ---
> radupantiru@: Your MCFG says there's ECAM space at [mem
> 0xf8000000-0xfbffffff]
> for [bus 00-3f]. That space *should* be reserved via a PNP0C01 or PNP0C02
> device in the ACPI namespace, but it isn't, so this is likely a BIOS
> defect.
>
> Can you try the patch I attached here?
> https://bugzilla.kernel.org/show_bug.cgi?id=218050#c6 . If you can,
> please
> attach the dmesg log here.
>
> --
> You may reply to this email to add a comment.
>
> You are receiving this mail because:
> You are on the CC list for the bug.

[bjorn (bjorn-linux-kernel-bugs)]

(In reply to radupantiru from comment #21)
Thanks very much for testing this! The dmesg shows what I expected:

  PCI: [Firmware Info]: ECAM at [mem 0xf8000000-0xfbffffff] not reserved in ACPI motherboard resources
  PCI: ECAM at [mem 0xf8000000-0xfbffffff] reserved as EfiMemoryMappedIO
  PCI: ECAM [mem 0xf8000000-0xfbffffff] reserved to work around lack of ACPI motherboard _CRS

Just to double-check, I think you were seeing a touchpad issue, right? And I assume that problem is fixed by this patch?

[radupantiru (radupantiru-linux-kernel-bugs)]

Created attachment 305467
attachment-26413-0.html

It was indeed the touchpad which failed to work at random intervals. It
will be quite obvious if it fails again and my question is if the patch
will make its way into the future kernels as I will have not to upgrade my
OS in order to monitor the fix.

Thanks,
Radu

[Frank H (fhireman)]

I'm on 6.2.0-39-generic (Ubuntu 22.04) and have started to get touchpad problems(I believe around September 2023).
Touchpad often stops responding after having the laptop(Lenovo Yoga slim 14ARE05) on for a while.

A full shutdown + waiting for a while and starting the laptop again makes the touchpad work again but just a reboot doesn't fix it.

Don't think it will help but here are my journalctl logs from yesterday:

jan 09 23:18:33 codingthing kernel: i2c_designware AMDI0010:00: controller timed out
jan 09 23:18:32 codingthing kernel: i2c_designware AMDI0010:00: i2c_dw_handle_tx_abort: lost arbitration

I didn't have this in the first 2 years of usage though.

I'm unsure how to safely try other kernel versions myself so I'm really hoping this fix finds its way to Ubuntu 22.04 or 24.04 releases.

[Frank H (fhireman)]

Few hours after posting I got the 6.5.0-14-generic update.
So I'll test it out for a while and see if the issue persists or if it's fixed.

Edit 12-01-2024:
No touchpad issues yet after using laptop for 2 days. Seems fixed but will report if issue happens again.

[francesco (airordl)]

Same problem here, (Lenovo ideapad Flex 5 -14ARE05, Ubuntu 22.04.3 LTS), although it did work JUST ONCE, randomly, in ~two years of ownership, about a couple of months ago. The "i8042.nopnp=1 pci=nocrs" solution broke my wifi (?) and didn't fix the problem.

I also just realized that this bug report is four years old...