From: "Thomas Gillespie" <thomas@sungillespie.com>
To: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org
Subject: Non-functional keyboard on Lenovo 14IPH11 (Panther-lake)
Date: Thu, 16 Apr 2026 16:56:56 +0100 [thread overview]
Message-ID: <ca5de53f-401e-48b4-90f4-84c5065fec4a@app.fastmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 639 bytes --]
The built-in keyboard on my Lenovo 14IPH11 laptop is completely non-functional under Linux. The device does not appear in `/proc/bus/input/devices`, suggesting it is not being enumerated by the kernel at all. The keyboard works correctly in the BIOS and GRUB, and an external USB keyboard functions normally under Linux.
I have tested this under NixOS with kernel versions 6.9.11 and 7.0.0-rc. I've also tested with an Arch Linux live ISO.
I've attached a collection of diagnostic output, which is hopefully helpful. Please let me know if there's anything else I can send, or if there's anything that you'd like me to run as a test.
Tom
[-- Attachment #1.2: Type: text/html, Size: 1691 bytes --]
[-- Attachment #2: diag.tar.gz --]
[-- Type: application/gzip, Size: 32070 bytes --]
reply other threads:[~2026-04-16 15:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ca5de53f-401e-48b4-90f4-84c5065fec4a@app.fastmail.com \
--to=thomas@sungillespie.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox