Hello Han,
Thank you very much for this detailed steps. I was able to reproduce
this with "evtest" and everything went okay.
After editing /lib/udev/hwdb.d/60-keyboarrd.hwdb as you specified, the
problem has been fixed, which I believe should revert on reboot?
This is the content of /sys/class/dmi/id/modalias
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX5304VA.304:bd05/16/2023:br5.27:svnASUSTeKCOMPUTERINC.:pnZenbookS13UX5304VA_UX5304VA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX5304VA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
Yes, I built my kernel. I wish I could parse this and write a proper quirk.
Also, I don't know if this is related; the hotkeys should be enabled by
default. Fn key should be for Function keys. But in the current state,
it is reversed.
Thank you
James
On 01/10/2023 09:28, Hans de Goede wrote:
Hi James,
On 10/1/23 10:11, James John wrote:
Hello,
First of all, thank you very much for the work you do with maintaining these drivers and supporting systems. It is not an easy one.
I have debugged this bug down to the asus_nb_wmi module. When I disable this module, the problem goes away, but then other hotkeys are not recognized. Attached is a debug event from libinput, where I pressed the capslock twice
I have tried to dabble around with asus-nb-wmi.c codes to see if I could fix it by luck, by adding UX5304VA to `static const struct dmi_system_id asus_quirks[]` but to no avail. And I have a very little knowledge of what "quirks" are.
I have attached some information regarding my hardware and kernel. I will be available to provide any more information that might be needed to resolve this.
A related open thread: https://bbs.archlinux.org/viewtopic.php?pid=2123716
First of all lets confirm that the KEY_BRIGHTNESSDOWN events are really coming from asus_nb_wmi.
Please install evtest and then run "sudo evtest" and then select the "Asus WMI hotkeys" device
by typing its number followed by enter.
After this reproduce the bug and see if the log shows KEY_BRIGHTNESSDOWN.
Since you said you tried playing around with the quirks, I assume you can build
your own kernel, please let me know if that is wrong.
If this confirms the KEY_BRIGHTNESSDOWN events are coming from the "Asus WMI hotkeys" device,
then please edit /lib/udev/hwdb.d/60-keyboard.hwdb
And search for "Asus WMI hotkeys", this should find this section:
evdev:name:Asus WMI hotkeys:dmi:bvn*:bvr*:bd*:svnASUS*:pn*:*
evdev:name:Eee PC WMI hotkeys:dmi:bvn*:bvr*:bd*:svnASUS*:pn*:*
evdev:name:Asus Laptop extra buttons:dmi:bvn*:bvr*:bd*:svnASUS*:pn*:*
KEYBOARD_KEY_6b=f21 # Touchpad Toggle
KEYBOARD_KEY_7c=f20 # Remap micmute to f20
Change this to:
evdev:name:Asus WMI hotkeys:dmi:bvn*:bvr*:bd*:svnASUS*:pn*:*
evdev:name:Eee PC WMI hotkeys:dmi:bvn*:bvr*:bd*:svnASUS*:pn*:*
evdev:name:Asus Laptop extra buttons:dmi:bvn*:bvr*:bd*:svnASUS*:pn*:*
KEYBOARD_KEY_6b=f21 # Touchpad Toggle
KEYBOARD_KEY_7c=f20 # Remap micmute to f20
KEYBOARD_KEY_20=unknown
And then run "sudo udevadm hwdb --update" followed by "sudo udevadm trigger",
that should filter out the spurious keypresses.
If that helps, please run:
cat /sys/class/dmi/id/modalias
So that a proper DMI based quirk to only to the filtering on your model
can be written.
Regards,
Hans
