From: Armin Wolf <W_Armin@gmx.de>
To: Ilya K <me@0upti.me>, rafael@kernel.org
Cc: lenb@kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, glpnk@proton.me
Subject: Re: [PATCH] ACPI: EC: Ignore ECDT tables with an invalid ID string
Date: Tue, 29 Jul 2025 00:13:26 +0200 [thread overview]
Message-ID: <4e0de0c3-395d-4e70-816c-72a8e75eff8f@gmx.de> (raw)
In-Reply-To: <9323b4ab-f2c2-41ec-be0e-779d327205ca@0upti.me>
Am 28.07.25 um 11:57 schrieb Ilya K:
> Hello folks!
>
> It looks like this change makes the touchpad stop being detected entirely on my ThinkBook 14 G7 IML[0].
>
> The kernel log says: > ACPI: EC: [Firmware Bug]: Ignoring ECDT due to invalid ID string "_SB.PC00.LPCB.EC0"
> Which looks technically invalid, but also probably important? :)
>
> Reverting the change makes things work again. I'm going to try a firmware update and pray to
> whatever dark gods are responsible for Lenovo firmware that they fixed their ACPI tables, but
> that requires getting Windows on the machine, so it'll take a bit.
>
> [0]: https://psref.lenovo.com/Product/ThinkBook/ThinkBook_14_G7_IML
>
> (resend -glpnk because my mail server is a shit)
Oh no, that sounds horrible :(
Can you share the output of "acpidump" once the system is running the latest firmware? If a BIOS update
does not solve the issue then we could give the ID string check a more leeway so that only empty strings
are considered invalid.
P.S: You could try if the BIOS update tool also works using Windows PE (https://wiki.archlinux.org/title/Windows_PE).
I used this method a couple of times on my notebook and it worked flawlessly.
Thanks,
Armin Wolf
next prev parent reply other threads:[~2025-07-28 22:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-29 23:53 Armin Wolf
2025-06-10 18:56 ` Rafael J. Wysocki
2025-07-28 9:57 ` Ilya K
2025-07-28 22:13 ` Armin Wolf [this message]
2025-07-29 4:29 ` Ilya K
2025-07-29 5:04 ` Armin Wolf
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=4e0de0c3-395d-4e70-816c-72a8e75eff8f@gmx.de \
--to=w_armin@gmx.de \
--cc=glpnk@proton.me \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@0upti.me \
--cc=rafael@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®