From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Nikodem Sanecki <nikodemsanecki@gmail.com>
Cc: westeri@kernel.org, linux-gpio@vger.kernel.org,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Hello, I'm reporting a Caps Lock LED issue on my Lenovo ThinkPad L13 Gen 2 AMD running Arch Linux. I found a workaround that completely fixes it, and I hope the findings might help implement a permanent kernel fix. **A quick note:** This is my first time using Linux, and I'm a complete beginner when it comes to kernel development. I used ChatGPT (GPT-6) to guide the troubleshooting process, analyse my laptop's ACPI firmware, and interpret the results. I personally ran the diagnostic commands and verified the observed behaviour, but the technical explanation below is AI-assisted. Please correct me if any of the analysis is inaccurate. ## Problem Under Linux, the physical Caps Lock indicator LED never illuminates, even though the Caps Lock key itself works normally. The LED works correctly under Windows and during certain stages of boot, so the hardware itself is functional. After investigating, GPT-6 identified what appears to be a conflict involving GPIO 11 on the AMD AMDI0...
Date: Thu, 15 Oct 2026 21:32:35 +0300 [thread overview]
Message-ID: <atEcQ-qjIXt5eNJp@ashevche-desk.local> (raw)
In-Reply-To: <atEY_4U7Z-xZ6QpB@ashevche-desk.local>
On Thu, Oct 15, 2026 at 09:18:42PM +0300, Andy Shevchenko wrote:
> On Thu, Oct 15, 2026 at 03:21:11PM +0100, Nikodem Sanecki wrote:
> > Resending this report in plain text because my original email was
> > rejected by the linux-gpio and linux-kernel mailing lists for
> > containing HTML formatting. Apologies if you received the original
> > message twice.
>
> And now the $Subject is well messed up! :(
Note, let's continue thread in your HTML start, I replied with text only there
and cited the whole message, so formally the content is public via my reply.
Let's not continue _this_ thread (with badly formed Subject).
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2026-10-15 18:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 14:21 Nikodem Sanecki
2026-10-15 18:18 ` Andy Shevchenko
2026-10-15 18:32 ` Andy Shevchenko [this message]
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=atEcQ-qjIXt5eNJp@ashevche-desk.local \
--to=andriy.shevchenko@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikodemsanecki@gmail.com \
--cc=westeri@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
all inboxes | Powered by JetHome®