Bug 1788537 - Lenovo T490s -> no touchpad input with F30 (updated) nor F31, works with F30 liveboot when TPM security chip is enabled
Summary: Lenovo T490s -> no touchpad input with F30 (updated) nor F31, works with F30 ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 31
Hardware: x86_64
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-07 13:10 UTC by Mickael Istria
Modified: 2020-01-27 08:56 UTC (History)
22 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-27 08:56:07 UTC
Type: Bug
Embargoed:
mistria: needinfo+


Attachments (Terms of Use)

Description Mickael Istria 2020-01-07 13:10:33 UTC
Description of problem:
libinput doesn't send events for T490s touchpad with F31 or up-to-date F30 (works with F30 liveboot)

I recently got a Lenovo T490s.
I tried installing Fedora 31 but faced (from liveboot and also after installaton) that touchpad wasn't working.
I tried installing Fedora 30 and touchpad was working on liveboot and after installation.
Then I `sudo dnf update` my F30 installation, and touchpad doesn't work anymore.
Running `libinput debug-events` doesn't send events anymore for the touchpad (nor for trackpoint)

Version-Release number of selected component (if applicable):
libinput-1.14.2-1.fc30.x86_64, then I downgraded to
libinput-1.13.1-2.fc30.x86_64 and still didn't get touchpad to work
(so I think libinput isn't necessarily the culprit, it could be some other package -like kernel- causing the regression).

How reproducible: At least on my machine, always reproducible

Steps to Reproduce:
1. Get a F31 liveboot installer on USB stick
2. Launch a Lenovo T490s against this USB stick
or
1. Get F30 liveboot, proceed to installation
2. `dnf update`, reboot

Actual results:
* touchpad doesn't work, mouse cursor doesn't move
* `libinput debug-events` doesn't log anything when playing with touchpad

Expected results:
* touchpad works

Additional info:
* plugged mouse works, keyboard works in all cases

Comment 1 Peter Hutterer 2020-01-07 21:35:19 UTC
do you see any events with the libinput record tool? If not, this is a kernel issue.

Comment 2 Mickael Istria 2020-01-08 08:04:54 UTC
(In reply to Peter Hutterer from comment #1)
> do you see any events with the libinput record tool?

`libinput record /dev/input/event17` shows no event when manipulating keyboard.

>If not, this is a kernel issue.

Ok. Should I just change the component for that bug or is it better that I open a separate one?

Comment 3 Mickael Istria 2020-01-09 14:59:07 UTC
> `libinput record /dev/input/event17` shows no event when manipulating keyboard.

s/keyboard/touchpad/

Comment 4 Peter Hutterer 2020-01-09 22:21:54 UTC
thank, moved to the kernel. might be worth trying a few older kernels to narrow down when exactly it broke.

Comment 5 Mickael Istria 2020-01-10 10:03:58 UTC
I confirm it's a kernel issue
* Using 5.0.9-301.fc30.x86_64 => touchpad works
* Using 5.4.7-100.fc30.x86_64 => touchpad doesn't work, no touchpad events found by libinput

Comment 6 Daniel Alley 2020-01-13 14:53:51 UTC
Same issue and same laptop.

I found that disabling the TPM chip in the BIOS temporarily "fixes" this issue, based on a recent forum post that I can't seem to find at this moment. If you look in "Logs" application -> "Hardware" you should see some relevant error messages (I don't have a copy of them at just this moment).

Comment 7 Mickael Istria 2020-01-16 08:15:45 UTC
I confirm Daniel comment #6: disabling the TPM security chip in BIOS makes everything work,

Comment 8 Scott Dodson 2020-01-17 14:42:15 UTC
Issue is still present in kernel-5.5.0-0.rc2.git1.1.fc32

Comment 9 Scott Dodson 2020-01-20 18:42:32 UTC
kernel-5.4.12-200.fc31 fixes this

Comment 10 Daniel Alley 2020-01-25 16:27:05 UTC
Can confirm, everything is working for me now with the TPM chip re-enabled and kernel 5.4.13

Comment 11 Mickael Istria 2020-01-25 21:29:14 UTC
I ran a `dnf update`, got kernel 5.4.13, re-enabled the TPM chip and everything works. Thanks!

Comment 12 Benjamin Tissoires 2020-01-27 08:56:07 UTC
Thanks everyone for testing. Closing as current release


Note You need to log in before you can comment on or make changes to this bug.