> > (please use reply-all so that the mailing list gets the emails as well) > Oh, my mistake. I didn't actually know the difference between the two. Sorry for any confusion this might cause in the future. > > > > [...] > > > > > Can you see any messages generated by the hp-wmi driver when these key presses occur? > > > > > > > > Not that I know of, unless there is some sort of debug mode that can be enabled > > > > > > > > > > > Now, this is not that interesting at first, I obviously just need to > > > > > > > map a keycode. The confusing part is that for both the brightness up > > > > > > > AND the brightness down key I get the same code (e02b). I am not to > > > > > > > sure how to debug this behavior but I would appreciate if someone > > > > > > > helped investigate this issue. > > > > > > > I am not sure if this is relevant, but my RFKILL key does not work > > > > > > > either (but does not show anything in journal). > > > > > > > > > > Could you please run `evtest` and see if you have a "HP WMI hotkeys" input device? > > > > > If so, please select it, and then press the function keys and see if any events appear. > > > > > > > > After running`evtest` there is a device called "HP WMI hotkeys" (on > > > > /dev/input/event16). However, after selecting it and pressing the > > > > brightness keys no events appear. > > > > > > > > > Furthermore, you could install `acpid`, start it (something along the lines of > > > > > `sudo systemctl start acpid`), then run `acpi_listen` and see if you get anything > > > > > when you press the keys. > > > > > > > > After starting the service and running`acpi_listen`, no events appear > > > > when pressing the brightness keys > > > > > > > > > > > Here is a link to acpidump: > > > > > > > https://www.dropbox.com/s/ulyltq0gz35s79l/acpidump?dl=0 > > > > > > > ::: Rhys Perry ::: > > > > [...] > > > > > > Could you test other function keys like volume up/down, etc.? > > > > > After running some tests with evtest I have found out: > > - Brightness keys: "AT Translated Set 2 keyboard" (although same keycode) > > - Volume keys: "AT Translated Set 2 keyboard" > > - Media keys: "AT Translated Set 2 keyboard" > > - RFKILL key: (none, although there is a device called "HP Wireless hotkeys") > > Please install the `evemu` program suite, and run `evemu-record /dev/input/event...` > for the AT keyboard, HP WMI hotkeys, and HP Wireless hotkeys; in each run press the > brightness up/down, volume up/down keys in any fixed order you like, and then send > the output of each run (including the part that is initially printed before > receiving any events). Could you also run `acpi_listen` at the same time and > see if any key presses are registered there? If yes, what was the output? > Ok, here you go: "AT Translated Set 2 Keyboard": https://0x0.st/idpK.txt "HP Wireless hotkeys": https://0x0.st/idpP.txt "HP WMI hotkeys": https://0x0.st/idpN.txt `acpi_listen`: https://0x0.st/idpb.txt > Just to summarize (please correct me if I'm wrong): > - brightness up/down keys > * send the same scan code via the keyboard; and > * do not trigger any ACPI events Yep, that is what I get > - volume up/down, and media keys send unique key codes via the keyboard and they work (?) Yes, they work as intended > - the rfkill hotkey does not appear to generate any events whatsoever (?) > - the "HP WMI hotkeys" and "HP Wireless hotkeys" input devices don't register > any events Yes, that is the case > > By the way, I suppose that screen brightness control with hotkeys does not work, > correct? > Yes > > > I wonder what the point of the HP WMI or Wireless devices are if they > > are not receiving any events. > > I can only assume that they do work in some circumstances/with older models/etc. > > > [...] Thanks for all the help, Rhys Perry
