From: John Veness <john@pelago.org.uk>
To: "Rafael J. Wysocki" <rafael@kernel.org>, Nick <nick@kousu.ca>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
regressions@lists.linux.dev, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
platform-driver-x86@vger.kernel.org
Subject: Re: [REGRESSION] Toshiba Fn keys + lidswitch
Date: Sun, 31 May 2026 16:25:53 +0100 [thread overview]
Message-ID: <2238f0ea-e479-4946-971d-9fbfc9170ec4@pelago.org.uk> (raw)
In-Reply-To: <12896447.O9o76ZdvQC@rafael.j.wysocki>
On 19/05/2026 18:15, Rafael J. Wysocki wrote:
> So please let me know if the patch below fixes the problem for you.
>
> In either case, please grep the dmesg output for "ACPI GPE" and let me know
> the result.
>
> Thanks!
Hi Rafael, thanks for the quick patch! I'm not Nick, but I have tested
the patch here on my old Toshiba Tecra Z50-A and it seems to have worked
- I now have Fn+keys working fine, after losing them in a recent kernel
update (apart from Fn+3 for volume down, and Fn+4 for volume up, which
for some reason continued to work when the others didn't).
dmesg|grep "ACPI GPE" since applying the patch gives:
[ 0.197248] [ T1] acpi (null): ACPI GPE enabled for PNP0C0C
John
next prev parent reply other threads:[~2026-05-31 15:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 16:49 Nick
2026-05-19 8:55 ` Thorsten Leemhuis
2026-05-19 11:48 ` Rafael J. Wysocki
2026-05-19 14:08 ` Rafael J. Wysocki
2026-05-19 17:15 ` Rafael J. Wysocki
2026-05-19 17:26 ` Nick
2026-05-31 15:25 ` John Veness [this message]
2026-05-30 12:19 ` John Veness
2026-05-30 13:34 ` johannes.goede
2026-05-31 15:17 ` John Veness
2026-05-31 20:29 ` Nick
2026-06-01 12:12 ` Rafael J. Wysocki
2026-06-02 18:21 ` Sasha Levin
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=2238f0ea-e479-4946-971d-9fbfc9170ec4@pelago.org.uk \
--to=john@pelago.org.uk \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nick@kousu.ca \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=regressions@lists.linux.dev \
/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®