Bug 1773879 - Touchpad / Trackpoint not working on T490s with latest kernel
Summary: Touchpad / Trackpoint not working on T490s with latest kernel
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 30
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-19 08:40 UTC by Dee'Kej
Modified: 2020-05-26 18:43 UTC (History)
26 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-26 18:43:05 UTC
Type: Bug
Embargoed:
bcotton: fedora_prioritized_bug-
devel: needinfo-


Attachments (Terms of Use)
dmesg.tt (203.50 KB, text/plain)
2019-11-19 08:40 UTC, Dee'Kej
no flags Details

Description Dee'Kej 2019-11-19 08:40:14 UTC
Created attachment 1637551 [details]
dmesg.tt

Hello guys, I've received a new working machine and now I'm facing some severe problem with it.

1. Please describe the problem:
After updating to latest version of kernel (in F30), I'm no longer able to use Touchpad/Trackpoint with Lenove Thinkpad T490s. Rebooting to older kernel version (shipped with F30 live ISO) makes the Touchpad/Trackpoint work again.

Trying updating the configuration in Fedora (Gnome Workstation) has no effect.

Using external mouse (Razer Deathadder) via USB is working.

2. What is the Version-Release number of the kernel:
kernel-5.3.11-200-fc30.x86_64


3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :
kernel-5.0.9-301.fc30.x86_64 is working correctly


4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
> Please, see point 1.


5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:
Yes. The issues still persists. (kernel-5.4.0-0.rc7.git1.2.fc32.x86_64)

6. Are you running any modules that not shipped with directly Fedora's kernel?:
No, this is fresh F30 installation.

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

Comment 1 Matthew Miller 2019-12-04 16:17:37 UTC
Sorry for taking so long to get to this. I see that there's a 5.5.0 rc kernel in testing now. Can you update to that?

Comment 2 Ben Cotton 2019-12-04 17:19:51 UTC
In this week's Prioritized Bugs meeting, we decided to defer a decision. I will send a request to the test mailing list to see if they can reproduce the issue.

Adding needinfo to Dee'Kej to see if
1. The 5.5.0 kernel currently building (https://koji.fedoraproject.org/koji/packageinfo?packageID=8) fixes it
2. The latest live respin (https://dl.fedoraproject.org/pub/alt/live-respins/F31-WORK-x86_64-LIVE-20191105.iso) works. The respin contains kernel 5.3.8, so that may help narrow down the version that introduced this behavior.

Comment 3 Ben Williams 2019-12-04 17:59:09 UTC
grab a updated 20191205 (f31) or 20191206 (F30) updated iso from http://tinyurl/Live-respins 
do either resolve this issue?

Comment 4 Kamil Páral 2019-12-05 13:21:37 UTC
Latest libinput pre-release contains:
"Touchpad fix and trackpoint speed adjustment for Lenovo T490s" [1]

Perhaps related?

[1] https://lists.freedesktop.org/archives/wayland-devel/2019-December/041062.html

Comment 5 Dee'Kej 2019-12-17 16:16:50 UTC
My apologies for late reply, I was stuck in personal stuff.

Unfortunately I cannot test this issue anymore, since I'm no longer working for a company from which I was using the Lenovo T490s. Hopefully someone with the same model can reproduce and confirm/reject the fix.

With kind regards,

Dee'Kej

Comment 6 Ben Cotton 2019-12-18 16:20:44 UTC
Rejected as a Prioritized Bug since the reporter no longer has access to the affected hardware and there are no other reports.
https://meetbot.fedoraproject.org/fedora-meeting/2019-12-18/fedora_prioritized_bugs_and_issues.2019-12-18-16.06.log.html#l-39

Comment 7 Scott Dodson 2020-01-17 13:52:02 UTC
This can be reproduced on the new standard spec laptop provided by Red Hat service desk. There's also a bug for this specific to Fedora 31 https://bugzilla.redhat.com/show_bug.cgi?id=1788537

I'm not sure how Fedora manages bugs, whether or not one of these should be marked as a dupe of each other so I'll just leave this note here. Since I'm using Fedora 31 I'll attempt to use a 5.5 kernel and report back on the other bug.

Comment 8 Tim Bielawa 2020-01-17 15:00:08 UTC
I can confirm that disabling TPM in the BIOS on the T490s works as a workaround for Fedora 30 running Linux 5.4.10-100.

Comment 9 Gary Case 2020-03-05 21:54:26 UTC
I ran into this problem on F31 today with a fresh install, but after updating to the latest packages including kernel 5.5.7-200.fc31.x86_64 the trackpad on my T490s started working properly.

Comment 10 Mike McCune 2020-03-08 18:05:41 UTC
Disabling TPM on a T490s gets past this issue on F31 LiveCD. 

For those not sure how to do this:

* enter your BIOS screen (hit enter on boot)
* Go to "Security" section
* disable "Trusted Platform Module" (typing from memory, it may not be named exactly this)
* save and exit
* boot to USB and install OS

Comment 11 Konrad Kleine 2020-04-24 11:10:22 UTC
I couldn't find the TMP or alike setting in the BIOS. But I found a hint in BZ1634832#c23 where it is suggested to add psmouse.elantech_smbus=0 to the kernel parameter in /etc/default/grub. I'm going to dnf update first and reboot now and if that doesn't work I'm going to add the kernel parameter.

Comment 12 Konrad Kleine 2020-04-24 11:18:47 UTC
After rebooting my system to the new kernel (with no other changes) I no longer have the problems that my trackball and touchpad don't work.

kkleine@work ~$ uname -a
Linux work 5.5.17-200.fc31.x86_64 #1 SMP Mon Apr 13 15:29:42 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

kkleine@work ~$ lsb_release -a
LSB Version:	:core-4.1-amd64:core-4.1-noarch
Distributor ID:	Fedora
Description:	Fedora release 31 (Thirty One)
Release:	31
Codename:	ThirtyOne

Comment 13 Ben Cotton 2020-04-30 20:11:47 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 14 Ben Cotton 2020-05-26 18:43:05 UTC
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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