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.
I have the exact same problem with my Lenovo T14s Gen 1 Hopefully this is an easy fix.
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.
yes, i get this problems with the BIOS/UEFI Release 1.34 and upgrade to 1.39 and after that to version 1.40.
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?
Ok, sorry, then we are talking about different issues.
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. 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 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.