Lenovo Legion 5 touchpad



Any luck with Fedora 32 and Kernel 5.6?

I got Fedora 32 with kernel 5.6 installed, everything working nicely, even switchable graphics between Nvidia card and Renoir. Still no touchpad working.

I have also upgraded to kernel 5.7.7-200 and still no luck with the touchpad. Oh and now the screen brightness control has stopped working :D

crossing my fingers for the release of 5.8
 
and the following does not work, either?
Code:
synclient TouchpadOff=0
 
It does work on the Legion 5 in Linux Mint 20. The touchpad is kinda useful.... Would like a better solution.

Add the following to your /etc/modprobe.d/blacklist.conf

#Fix Touchpad
blacklist hid_multitouch
 
blacklist hid_multitouch can't fix MSFT0001:00 04F3:3140 Touchpad.
 
blacklist hid_multitouch can't fix MSFT0001:00 04F3:3140 Touchpad.

It does not FIX the touchpad it just makes it somewhat useful. Like you could use it in a pinch if your wireless mouse died....

Here is the ID of the one in my Legion 5 when blacklisted I do get basic functionality.
MSFT0001:00 06CB:7F28
 
It does not FIX the touchpad it just makes it somewhat useful. Like you could use it in a pinch if your wireless mouse died....

Here is the ID of the one in my Legion 5 when blacklisted I do get basic functionality.
MSFT0001:00 06CB:7F28

Looks like we are two different kind touchpad. Even add hid_multitouch to blacklist, MSFT0001:00 04F3:3140 still can't use at all.
 
still can't use at all.

Had a Lenovo and was totally dissatisfied with the touchpad, as well. Disables it abd used only the USB mouse. I suggest that y'all learn to live with it.
 
I've bought an lenovo legion 5, which has apparently the same touchpad. Tried different kernels, up to 5.8-rc5, without any success. I also had no sufficient success in manipulation of the xorg....70-synaptics.conf file or something similar. If somebody has new positiv progress, please share :)
 
I also bought a Legion 5.
I was able to install Kubuntu 20.04, but I had to install the OEM kernel (which upgraded to 5.6) before it would boot normally.
I haven't done a lot of testing yet, but the only two issues so far are the touchpad (no surprise) and the display went to a lower resolution (or larger font) for some reason.

To install Kubuntu I had to boot into the recovery mode, then use those menus to boot 'normal', and then install the nvidia driver (not sure I had to install that, but it's more performant than nouveau).
Then I installed 5.6 kernel by running 'apt install linux-oem-20.04', with a couple of reboots between.

If that didn't work I was going to install Fedora, then KDE.
 
Throwing my hat in the ring as well -- bought a Legion 5 Ryzen 4800H and have run MXLinux 19.2 with Kernel 5.6 (5.7 hangs), and Manjaro with 5.6 (5.7 hangs as well).

As is the story with others here, My touchpad shows MSFT0001:00 04F3:3140 and no workarounds have any effect on it. It's a great laptop, and most everything else works great, but so far haven't found anything to bring the touchpad to life.
 
So there is nothing in Arch that works for touchpads? Have you checked in the Arch community, forums, or something? It sounds like a problem that has a specific condition.
I am running Arch on a Lenovo Legion and my touchpad works, not sure if it is helpful since I'm not sure if it is a Legion 5:
Code:
Manufacturer: LENOVO
Version: Legion Y540-15IRH

MSFT0001:01 04F3:309E Mouse                 
MSFT0001:01 04F3:309E Touchpad              

local/xf86-input-libinput 0.30.0-1 (xorg-drivers)
 
Last edited:
I am running Arch on a Lenovo Legion and my touchpad works, not sure if it is helpful since I'm not sure if it is a Legion 5:

Nope, that's an older model, the specific one that has the problem is the Legion 5 15ARH05 with the 3140 touchpad (apparently there's a second model touchpad on this same unit that can be activated with a workaround).

There's a bug report at launchpad.net regarding this exact issue -- I would encourage everyone that is experiencing the bug to sign up there and mark the bug as affecting them.

 
Same story here, got the Legion 5 tried, Manjaro, Fedora and KDE Neon, tried different kernels, tried several other methods nothing worked, hopefully in time it will be fixed.
 
a patch for every kernel (tested on 5.x) has been released by the linux Community on this launchpad bug track:

this is the patch:

Hopefully it will be merged with one of the next mainline kernels!

Minimum Lenovo should do is to give credits to these guys, that did the job 'for free', without ANY assistance from the tech giant (thank you very much..)
 
This link to the patch doesn't work. I have the same issue (ideapad gaming 3i, linux mint 20, kernel 5.8.0-23)

Other then the touchpad and screenbrightness everything works as expected. (amd 5, 4600u)
 
On arch, the recommendations from comment 143 on the bug page above work:

Code:
[ra@localhost ~]$ su
Password:
[root@localhost ra]# cd /sys/class/gpio/
[root@localhost gpio]# echo 386 > export
[root@localhost gpio]# cd gpio386
[root@localhost gpio386]# echo out > direction
[root@localhost gpio386]#

I haven't rebooted yet to see if it persists, but seems to be working well enough at present. Running arch linux 5.9.1.arch1-1.
 
On arch, the recommendations from comment 143 on the bug page above work:

Code:
[ra@localhost ~]$ su
Password:
[root@localhost ra]# cd /sys/class/gpio/
[root@localhost gpio]# echo 386 > export
[root@localhost gpio]# cd gpio386
[root@localhost gpio386]# echo out > direction
[root@localhost gpio386]#

I haven't rebooted yet to see if it persists, but seems to be working well enough at present. Running arch linux 5.9.1.arch1-1.

Thanks for sharing the relevant code from the linked web page. I attempted accessing the original post but it seems the page is gone now.

I have a Lenovo Legion 5P-15ARH05H with touchpad MSFT0001:00 06CB:7F28. The fix works for me in Manjaro kernel 5.8.16-2, however, it does not persist after reboot so I have setup a script to execute at each boot to recreate the entries for me.
 
Last edited:
Just to give you an update: I am now on Fedora 33 kernel 5.9.12 and still nothing.

I also discovered issues when trying to plug in an external monitor via HDMI or USB-C when running in hybrid mode. I will try changing to the dedicated graphics card in the BIOS to see if it works then.
 

Members online


Top