From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Dell.Client.Kernel@dell.com,
"Matthew Garrett" <mjg59@srcf.ucam.org>,
"Pali Rohár" <pali@kernel.org>
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Dell laptop function keys stopped working between 5.10.46 and 5.13.9
Date: Mon, 16 Aug 2021 11:48:17 +0200 [thread overview]
Message-ID: <b8ff8f68-4d5a-7ec6-4c4f-9f5be6e70ab5@molgen.mpg.de> (raw)
Dear Linux folks,
On a Dell Latitude E7250, updating Linux from 5.10.46 to 5.13.9 (Debian
sid/unstable) the two function keys to (un-)mute the microphone, and
enable/disable Wifi stopped working. The other function keys continue to
work. The `evtest` output did not change.
Linux version 5.10.0-8-amd64 (debian-kernel@lists.debian.org)
(gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for
Debian) 2.35.2) #1 SMP Debian 5.10.46-4 (2021-08-03)
Event: time 1629104514.184947, type 4 (EV_MSC), code 4 (MSC_SCAN),
value 88
Event: time 1629104514.184947, type 1 (EV_KEY), code 240
(KEY_UNKNOWN), value 2
Linux version 5.13.0-trunk-amd64 (debian-kernel@lists.debian.org)
(gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for
Debian) 2.35.2) #1 SMP Debian 5.13.9-1~exp2 (2021-08-10)
Event: time 1629103829.341409, type 4 (EV_MSC), code 4 (MSC_SCAN),
value 88
Event: time 1629103829.341409, type 1 (EV_KEY), code 240
(KEY_UNKNOWN), value 2
The output of `acpi_listen` also did not change.
$ acpi_listen
9DBB5994-A997- 000000d0 00000000
Are you aware of such reports?
Kind regards,
Paul
next reply other threads:[~2021-08-16 9:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 9:48 Paul Menzel [this message]
2021-08-16 10:22 ` Dell laptop function keys stopped working between 5.10.46 and 5.13.9 Paul Menzel
2021-08-16 10:34 ` Hans de Goede
2021-08-16 11:48 ` Paul Menzel
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=b8ff8f68-4d5a-7ec6-4c4f-9f5be6e70ab5@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=Dell.Client.Kernel@dell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=pali@kernel.org \
--cc=platform-driver-x86@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;
as well as URLs for NNTP newsgroup(s).