Bug 2099699 - No touchpad functions since kernel-5.17.2-200.fc35 after every cold boot
Summary: No touchpad functions since kernel-5.17.2-200.fc35 after every cold boot
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 35
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2022-06-21 13:52 UTC by Patrick West
Modified: 2022-07-07 18:27 UTC (History)
21 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Type: Bug

Attachments (Terms of Use)

Description Patrick West 2022-06-21 13:52:45 UTC
Up to (including) kernel-5.16.20-200.fc35 the touchpad of the ThinkPad T14s Gen 1 works fine.

Starting kernel-5.17.2-200.fc35 (or later) using a cold boot, the touchpad is not recognized correctly anymore: While it possible to basically navigate, functions like typing or scrolling are no longer possible.

Interestingly, when using kernel-5.17.2-200.fc35 (or later), the functions are coming back after a reboot (warm boot) or a switch to suspend. In short: Cold boot, non-working touchpad functions, reboot without powering off, working touchpad functions.

To avoid misunderstandings, a cold boot is when the notebook is shut down, powered off and physically turned on using the power button. Reboot, suspend means actually reboot and/or suspend using the GNOME desktop (warm boot).

Whenever the touchpad works as expected, the device is shown in dmesg(1) output, but there is no output in cases where the touchpad does not work.

$ dmesg -t | grep Elantech
input: ETPS/2 Elantech TrackPoint as /devices/platform/i8042/serio1/input/input12
input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input6

Version-Release number of selected component (if applicable):
kernel-5.16.20-200.fc35 (working)
kernel-5.17.2-200.fc35 (non-working)

How reproducible & Steps to Reproduce:
See above.

Actual results:
No touchpad functions with kernel-5.17.2-200.fc35 (or later) after every cold boot.

Expected results:
Properly working touchpad with kernel-<latest>.fc35 after every cold and warm boot.

Additional info:
From my point of understanding, the following changes happened between kernel-5.16.20-200.fc35 and kernel-5.17.2-200.fc35 on downstream and on upstream side:

 - https://src.fedoraproject.org/rpms/kernel/c/007dd6daa364520147a4ddea445fde2bc75a8909?branch=f35
 - https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/diff/?id=v5.16.20&id2=v5.17.2&dt=2

I am happy to try further debugging (but would need some hints and instructions) to get this tracked down.

Comment 1 Fingerless Gloves 2022-06-29 15:02:33 UTC
I have the exact same problem with my Lenovo T14s Gen 1

Hopefully this is an easy fix.

Comment 2 Fingerless Gloves 2022-06-29 15:02:49 UTC
I have the exact same problem with my Lenovo T14s Gen 1

Hopefully this is an easy fix.

Comment 3 tobias.coni 2022-07-07 18:02:12 UTC
Are you sure that this is Kernel Version related and not BIOS Version related? BIOS 1.40 seems to break the Touchpad in S3 Standby mode, even on Windows.

Comment 4 Patrick West 2022-07-07 18:09:18 UTC
yes, i get this problems with the BIOS/UEFI Release 1.34 and upgrade to 1.39 and after that to version 1.40.

Comment 5 Fingerless Gloves 2022-07-07 18:10:47 UTC
I'm sure I had the issue before I upgraded my BIOS.

What do you mean by "seems to break the Touchpad in S3 Standby mode" you saying it breaks when you enter S3 mode and then come out of S3?

Comment 6 tobias.coni 2022-07-07 18:27:07 UTC
Ok, sorry, then we are talking about different issues.

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