linux-kernel - Re: PROBLEM: asus_nb_wmi sends KEY_BRIGHTNESSDOWN on pressing CAPS Lock and PrntScrn on Zenbook S 13 UX5304VA

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: <1884918.tdWV9SEqCh@dividebyzero.it>
Date:   Fri, 24 Nov 2023 16:54:36 +0100
From:   Juri Vitali <juri@...idebyzero.it>
To:     James John <me@...jajo.com>,
        Corentin Chary <corentin.chary@...il.com>,
        Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>,
        Mark Gross <markgross@...nel.org>,
        Hans de Goede <hdegoede@...hat.com>
Cc:     platform-driver-x86@...r.kernel.org,
        acpi4asus-user@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: PROBLEM: asus_nb_wmi sends KEY_BRIGHTNESSDOWN on pressing CAPS Lock and
 PrntScrn on Zenbook S 13 UX5304VA

Hi,
Unfortunately those patches have broken the backlight reporting on older 
laptops, which do rely on the old mechanism.

For instance, on my Asus UX32A/VD when pressing the backlight up/down button 
the backlight changes accordingly, but the event is not caught by the system 
(more precisely, dmesg is complaining of unknown key codes):

> [ 3167.842213] asus_wmi: Unknown key code 0x29
> [ 3168.105096] asus_wmi: Unknown key code 0x28
> [ 3168.142526] asus_wmi: Unknown key code 0x27
> [ 3168.178860] asus_wmi: Unknown key code 0x26
> [ 3168.216027] asus_wmi: Unknown key code 0x25
> [ 3168.256511] asus_wmi: Unknown key code 0x24
> [ 3168.292907] asus_wmi: Unknown key code 0x23
> [ 3168.329704] asus_wmi: Unknown key code 0x22
> [ 3168.366554] asus_wmi: Unknown key code 0x21
> [ 3168.406681] asus_wmi: Unknown key code 0x20
> [ 3168.443330] asus_wmi: Unknown key code 0x20
> [ 3168.480900] asus_wmi: Unknown key code 0x20
> [ 3168.516326] asus_wmi: Unknown key code 0x20
> [ 3168.554006] asus_wmi: Unknown key code 0x20
> [ 3168.593320] asus_wmi: Unknown key code 0x20
> [ 3168.630108] asus_wmi: Unknown key code 0x20
> [ 3168.670110] asus_wmi: Unknown key code 0x20
> [ 3168.943217] asus_wmi: Unknown key code 0x11
> [ 3169.203349] asus_wmi: Unknown key code 0x12
> [ 3169.243239] asus_wmi: Unknown key code 0x13
> [ 3169.279881] asus_wmi: Unknown key code 0x14
> [ 3169.316311] asus_wmi: Unknown key code 0x15
> [ 3169.352887] asus_wmi: Unknown key code 0x16
> [ 3169.392806] asus_wmi: Unknown key code 0x17
> [ 3169.429301] asus_wmi: Unknown key code 0x18
> [ 3169.465843] asus_wmi: Unknown key code 0x19
> [ 3169.502404] asus_wmi: Unknown key code 0x1a
> [ 3169.542308] asus_wmi: Unknown key code 0x1a
> [ 3169.578938] asus_wmi: Unknown key code 0x1a
> [ 3169.615506] asus_wmi: Unknown key code 0x1a
> [ 3169.652002] asus_wmi: Unknown key code 0x1a
> [ 3169.692280] asus_wmi: Unknown key code 0x1a

In this case it seems that the backlight-down codes go from 0x20 to 0x29 while 
the -up from 0x11 to 0x1a, so assuming they are not clamped somewhere else 
they should not conflict with the ones used on newer models.

By the way, I only found those codes to be reported by asus-wmi, while other 
inputs remain silent while pressing those keys.

Let me know if I can help with some logs or anything.

Regards,

Juri