Bug 26135

Summary: Thinkpad X1 trackpoint and mouse buttons non-functional with 5.4.12-desktop-1 kernel
Product: Mageia Reporter: Tim Williams <tim>
Component: RPM PackagesAssignee: Kernel and Drivers maintainers <kernel>
Status: RESOLVED OLD QA Contact:
Severity: major    
Priority: Normal CC: rihoward1, tim, tmb
Version: 7   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: kernel-5.4.12-1.mga7.src.rpm CVE:
Status comment:
Attachments: Dmesg from kernel 5.4.6, the last one that works
Dmesg from kernel 5.5.4, which fails
lspcidrake -v from 5.4.6 kernel
Dmesg from 5.4.10 kernel, last working release
Dmesg from 5.4.12 kernel, first non working release

Description Tim Williams 2020-01-26 02:28:35 CET
Description of problem:

The Thinkpad X1 tablet trackpoint and built in mouse buttons are non-functional using the 5.4.12-desktop-1 kernel. The touchpad continues to work for mouse movement, but mouse clicks on the touchpad aren't registered. Booting with the earlier 5.4.6-desktop-2 kernel restores full function as does booting to windows, so this seems to be kernel bug rather than a hardware problem. All packages fully up to date.

Version-Release number of selected component (if applicable):

5.4.12-desktop-1 kernel

How reproducible:

Every time

Steps to Reproduce:
1. Boot with 5.4.12-desktop-1 kernel
2. Try to use trackpoint (fails)
Comment 1 Lewis Smith 2020-01-26 10:02:26 CET
> Booting with the earlier 5.4.6-desktop-2 kernel restores full function
This is clear enough. I imagine you are doing that.
There was an intermediate kernel 5.4.10. Can you say what happened with that?

Assigning to kernel/drivers.

Assignee: bugsquad => kernel

Comment 2 Tim Williams 2020-02-23 18:25:06 CET
Created attachment 11516 [details]
Dmesg from kernel 5.4.6, the last one that works
Comment 3 Tim Williams 2020-02-23 18:25:45 CET
Created attachment 11517 [details]
Dmesg from kernel 5.5.4, which fails
Comment 4 Tim Williams 2020-02-23 18:27:30 CET
All the following kernel updates exhibit the same problem including the latest 5.5.4-desktop-1.mga7 release, so I'm still running 5.4.6 to mitigate the problem for now.

Sorry for the slow reply I didn't get a notification of your response.
Tim Williams 2020-02-23 18:28:44 CET

CC: (none) => tim

Comment 5 Thomas Backlund 2020-02-23 18:56:04 CET
please attach output of lspcidrake -v

CC: (none) => tmb

Comment 6 Tim Williams 2020-02-23 22:27:21 CET
Created attachment 11519 [details]
lspcidrake -v from 5.4.6 kernel
Comment 7 Tim Williams 2020-03-20 01:39:11 CET
Same problem with the latest 5.5.9-1 kernel
Comment 8 Tim Williams 2020-04-24 23:19:13 CEST
Still non-functional with the kernel-desktop-5.5.15-3 kernel.
Comment 9 Tim Williams 2020-05-06 01:09:02 CEST
No change with 5.6.8-desktop-1 kernel, trackpoint and mouse buttons still non-functional. Reverting to the 5.4.6 kernel at boot time continues to restore functionality.
Comment 10 Tim Williams 2020-05-06 02:17:42 CEST
A similar problem has been reported for Ubuntu here:

https://askubuntu.com/questions/1225633/19-10-thinkpad-x1-tablet-gen-2-trackpoint-not-working

Sadly no resolution.
Comment 11 Tim Williams 2020-05-06 03:05:13 CEST
Further update, I think I missed the release of the 5.4.10 kernel, I have just tested this and the trackpoint and mouse buttons are working with this release, but definitely non-working with 5.4.12. So that narrows the regression down as being between the two.
Comment 12 Thomas Backlund 2020-05-06 16:40:35 CEST
Can you attach dmesg from both working 5.4.10 and non-working 5.4.12 with no extra usb devices connected.
Comment 13 Tim Williams 2020-05-07 14:06:03 CEST
Created attachment 11618 [details]
Dmesg from 5.4.10 kernel, last working release
Comment 14 Tim Williams 2020-05-07 14:07:15 CEST
Created attachment 11619 [details]
Dmesg from 5.4.12 kernel, first non working release
Comment 15 Tim Williams 2020-05-07 14:09:41 CEST
Dmesg attached as request, no extra USB devices were plugged in.
Comment 16 Thomas Backlund 2020-05-09 14:32:45 CEST
ok, not much standing out besides fixes for zero-length endpoint descriptors and that the input devices get enumerated differently... but they all get listed...

I've just pushed newer libinput packages to Core Updates Testing that has various updates including adaptions and quirks for newer kernels and hardwares...

Please test them when they are available:

x11-driver-input-libinput-0.29.0-1.mga7
libinput-udev-1.15.5-1.mga7

If that is not helping...
is x11-driver-input-evdev installed ?

if it is not installed, try to install it, does it help ?

if it is installed, try to remove it, does it help ?
Comment 17 Tim Williams 2020-05-15 01:37:15 CEST
Testing packages installed (but nothing else from testing), output below to confirm the versions.

[timw@flossie ~]$ rpm -qa | grep x11-driver-input-libinput
x11-driver-input-libinput-0.29.0-1.mga7
[timw@flossie ~]$ rpm -qa | grep libinput-udev
libinput-udev-1.15.5-1.mga7

Sadly this had no impact on the problem. x11-driver-input-evdev wasn't installed, so I tried installing but this also made no difference. I tested the above against the 5.4.12 and 5.6.8 Kernels just in case again.

All normal updates were installed prior to this test.
Comment 18 Tim Williams 2020-06-03 21:07:27 CEST
Still no change with the 5.6.14-desktop-2 kernel.

Doing some further digging there is a thread here:

https://www.reddit.com/r/LinuxOnThinkpads/comments/evr42q/x1_tablet_3rd_gen_left_and_right_mouse_buttons/ffzic55/

for the 3rd gen X1 where the left and right mouse buttons aren't working with kernel 5.4.12+, I'm assuming the reporter never tried the trackpoint. The post includes links to these two kernel patches:

https://lkml.org/lkml/2020/1/14/273
https://lkml.org/lkml/2020/1/14/251

and says that reverting them cures the problem.
Comment 19 Tim Williams 2020-06-04 00:26:02 CEST
In a spirit of experimentation, I downloaded the source rpm for the 5.6.14-desktop-2 kernel, reverted the two patches from my post above and rebuilt. I can confirm that the custom kernel works perfectly with the mouse buttons and track point.
Comment 20 r howard 2020-06-04 01:26:00 CEST
Tim has this problem been reported to the kernel developers https://bugzilla.kernel.org/ ?

Are you going to reply to the reddit thread stating that it is still happening in kernel 5.6.14 ?

CC: (none) => rihoward1

Comment 21 Tim Williams 2020-06-04 12:27:04 CEST
I don't have an account on Reddit and am reluctant to start one just to make a single comment. It's not a website I like, I tend to avoid it.

No idea if the problem is on the Kernel bugzilla, when I have time I can look and report if necessary, but time is in very short supply at the moment.
Comment 22 Aurelien Oudelet 2021-07-06 13:17:12 CEST
Mageia 7 is EOL since July 1st 2021.
There will not have any further bugfix for this release.

You are encouraged to upgrade to Mageia 8 as soon as possible.

@reporter, if this bug still apply with Mageia 8, please let us know it.

@packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead.

This bug report will be closed OLD if there is no further notice within 1st September 2021.
Comment 23 Marja Van Waes 2021-09-07 14:09:42 CEST
Hi bug reporter and hi assignee and others involved,

Please reopen this bug report if it is still valid for Mageia 8 or 9(cauldron), and change "Version:" in the upper left of this report accordingly.

This report is being closed as OLD because it was filed against Mageia 7, for which  support ended on June 30th 2021.

Thanks,
Marja

Resolution: (none) => OLD
Status: NEW => RESOLVED