Those keycodes then correctly produce the acpi events listed in my first post. The final step in the puzzle is then to write a script that runs on start up with the lines: This time the brightness keys are not listed in the information but actually pressing the keys in the listen mode shows that they have EV_MSC hex codes of 92 and 97 but no EV_KEY codes. The brightness keys are correctly listed in the information as having codes 224 (down) and 225 (up) but actually pressing the function keys in the listen mode doesn’t register anything. So, I’m not sure how that module is meant to work for those two keys. So, of course if you try to reassign these using setkeycodes, you end up reassigning the “1” and “2” keys – not very helpful.
HP ELITEBOOK BRIGHTNESS CONTROL CODE
However, the keycodes that are listed in the code are 0x02 and 0x03. Two of these are relevant to the keyboard, event 0 and event 11.Īccording to the source code for the HP WMI kernel module, it should report the brightness down and brightness up keys. dev/input/event10: HDA Intel Front Headphone
dev/input/event6: ST LIS3LV02DL Accelerometer dev/input/event1: SynPS/2 Synaptics TouchPad dev/input/event0:ĚT Translated Set 2 keyboard Running evtest with no arguments gave the following: The secret weapon was an application called evtest which is in the repositories. I almost left it there but I didn’t want to let it beat me.Īfter much research, I eventually solved the problem and I am putting some notes here in case they help anyone with similar problems. I tried playing with the acpi_os_name and acpi_osi= grub entries as suggested in other places in the forum but this didn’t help.Ĭan anyone give me a way of trying to get the system to look for these keys and report an event when they are pressed?Ĭaprea, As the backlight control itself was actually working OK and the problem was with the function key events not being recognised, I didn’t pursue the backlight options any further.Īfghan, I knew about those lines but they didn’t work because the function keys weren’t being recognised as XF86MonBrightnessDown and XF86MonBrightnessUp and therefore couldn’t be used to trigger backlight-brightness.īlur13, This did work, although I tried it with different keys.
HP ELITEBOOK BRIGHTNESS CONTROL DRIVER
showkey -k gives 224 for brightness up and 225 for brightness down.Īcpi_listen gives video/brightnessdown BRTDN 00000087 00000000 and video/brightnessup BRTUP 00000086 00000000 K.Ĭlearly the hardware works but either the appropriate keyboard driver is not installed in antiX 21 or I cannot find a way to invoke it. Using showkey -s gives me 0xe0 0x4c, 0xe0 0xcc, oxe0 0x54 and 0xe0 0xd4 for the press and release of the two keys respectively. I have other partitions on the laptop with other Debian based Linux OSs on them and they work fine. I tried using acpi_listen with the same result. In all of these pressing the fn f9 and fn f10 keys did nothing. I tried using xev, showkey -s, and showkey -k. However, I can’t get the fn f9 and fn f10 keys to work. The brightness control in the Control Centre also works. I have scripts in /etc/acpi that work fine from a terminal. The Brightness Up and Down keys don’t work. It is the same using both the 4.9 and the 5.10 kernels. I have installed antiX 21 64bit on an HP Elitebook 8730w laptop.
0 kommentar(er)
