From: Juri Vitali <juri@dividebyzero.it>
To: "James John" <me@donjajo.com>,
"Corentin Chary" <corentin.chary@gmail.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Mark Gross" <markgross@kernel.org>,
"Hans de Goede" <hdegoede@redhat.com>
Cc: platform-driver-x86@vger.kernel.org,
acpi4asus-user@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: asus_nb_wmi sends KEY_BRIGHTNESSDOWN on pressing CAPS Lock and PrntScrn on Zenbook S 13 UX5304VA
Date: Fri, 24 Nov 2023 16:54:36 +0100 [thread overview]
Message-ID: <1884918.tdWV9SEqCh@dividebyzero.it> (raw)
In-Reply-To: <024c4ad4-1a73-8c24-5e6f-f8c9f2f7b98f@redhat.com>
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
next prev parent reply other threads:[~2023-11-24 16:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-01 8:11 PROBLEM: asus_nb_wmi sends KEY_BRIGHTNESSDOWN on pressing CAPS Lock and PrntScrn on Zenbook S 13 UX5304VA James John
2023-10-01 9:28 ` Hans de Goede
2023-10-01 8:46 ` James John
2023-10-01 13:45 ` Hans de Goede
2023-10-01 14:16 ` James John
2023-10-01 14:18 ` James John
2023-10-01 15:09 ` James John
2023-10-11 10:44 ` Hans de Goede
2023-10-11 15:43 ` Hans de Goede
2023-11-24 15:54 ` Juri Vitali [this message]
2023-11-25 14:25 ` Hans de Goede
2023-12-03 15:44 ` Hans de Goede
2023-12-04 0:32 ` juri
2023-12-04 0:32 ` juri
2023-12-04 13:06 ` juri
2023-12-04 13:54 ` Hans de Goede
2023-12-04 15:52 ` juri
2023-10-17 8:50 ` Hans de Goede
2023-10-18 0:17 ` me
2023-10-18 19:35 ` Hans de Goede
2023-10-19 23:22 ` James John
2023-10-21 9:46 ` Hans de Goede
2023-10-21 9:53 ` James John
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=1884918.tdWV9SEqCh@dividebyzero.it \
--to=juri@dividebyzero.it \
--cc=acpi4asus-user@lists.sourceforge.net \
--cc=corentin.chary@gmail.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=me@donjajo.com \
--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