linux-kernel - Re: input/i8042: Malfunctioning brightness keys on HP Elite Dragonfly G2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <df7313597d2ac3212f10c05aa3d369728f030c86.camel@gmx.co.uk>
Date:   Mon, 11 Jul 2022 08:49:27 +0100
From:   Alex Dewar <alex.dewar@....co.uk>
To:     Hans de Goede <hdegoede@...hat.com>, dmitry.torokhov@...il.com,
        tiwai@...e.de, markgross@...nel.org
Cc:     linux-input@...r.kernel.org, linux-kernel@...r.kernel.org,
        platform-driver-x86@...r.kernel.org
Subject: Re: input/i8042: Malfunctioning brightness keys on HP Elite
 Dragonfly G2

Hi Hans,

On Sat, 2022-07-09 at 16:56 +0200, Hans de Goede wrote:
> Hi,
> 
> On 7/5/22 19:25, Alex Dewar wrote:
> > Friendly ping? 🙂
> > 
> > I'm also CC'ing the x86 platform people into this, as I'm not sure
> > whether this problem is something more within their remit.
> 
> Please test the atbkd device with "sudo evemu-record" or "sudo
> evtest"
> and if the brightness keys generate events there, write down the
> raw event codes (MSC events).

I tried this but unfortunately this doesn't seem to be the whole story.
If I press "decrease brightness" I get:
Event: time 1657525393.922727, -------------- SYN_REPORT ------------
Event: time 1657525397.043348, type 4 (EV_MSC), code 4 (MSC_SCAN),
value 81
Event: time 1657525397.043348, type 1 (EV_KEY), code 190 (KEY_F20),
value 1
Event: time 1657525397.043348, -------------- SYN_REPORT ------------
Event: time 1657525397.050384, type 4 (EV_MSC), code 4 (MSC_SCAN),
value 81
Event: time 1657525397.050384, type 1 (EV_KEY), code 190 (KEY_F20),
value 0

And if I press "increase brightness" I get:
Event: time 1657525397.050384, -------------- SYN_REPORT ------------
Event: time 1657525398.607184, type 4 (EV_MSC), code 4 (MSC_SCAN),
value 81
Event: time 1657525398.607184, type 1 (EV_KEY), code 190 (KEY_F20),
value 1
Event: time 1657525398.607184, -------------- SYN_REPORT ------------
Event: time 1657525398.614190, type 4 (EV_MSC), code 4 (MSC_SCAN),
value 81
Event: time 1657525398.614190, type 1 (EV_KEY), code 190 (KEY_F20),
value 0

There's no difference! And I also get the same thing if I press the
*actual* mute mic button 😞.

Any ideas?

Best,
Alex