Certain keyboard keys not working.

rhysperry111 · 2019-04-28 23:18:49

I have a HP Pavillion 15 and I am experiencing problems getting the OS to register key presses on the keys:
- Brightness Down (f2)
- Brightness Up (f3)
- Aeroplane mode toggle (f12)

All i have currently done is run xev which did not detect any key events in respect to those keys.

PS: This has also been posted on official HP forum (but i think it is unlikely that the people over there will know how to fix this issue.) -- HP Forum Post

jasonwryan · 2019-04-28 23:30:07

https://wiki.archlinux.org/index.php/Keyboard_input

Moving to NC...

seth · 2019-04-29 07:28:23

Also https://wiki.archlinux.org/index.php/Acpid

rhysperry111 · 2019-04-29 11:15:31

The dmesg method worked. From that i know that:

-- Brightness down = e02b
-- Brightness up = e02b ???

-- WIreless toggle = Non existent

Can anyone give a resonable explanation for this behavior?

Last edited by rhysperry111 (2019-04-29 11:24:51)

seth · 2019-04-29 15:33:16

Did you try acpi_listen?
You can also try whether "showkey" produces anything (for the brightness keys)
Please post the actual dmesg, but the behavior seems common, eg.:
https://wiki.gentoo.org/wiki/HP_Spectre_x360_(2015)
https://bbs.archlinux.org/viewtopic.php?id=122904
https://github.com/linuxmint/Cinnamon/issues/6516

rhysperry111 · 2019-04-29 16:30:55

Already tried acpi listen and showkey which returned nothing. I currently do not have my device but will post dmesg results and try the linked methods ASAP

rhysperry111 · 2019-04-29 17:06:13

Tried methods U listen which did not seem to work. I have a feeling my acpi parameters are not correct. The reason I think this is their are a lot of similar issues which have been fixed by sorting out acpi.

Does anyone know which acpi parameters are likely to fix this.

As for the dmesg output I will post a text file with the output in a few mins

rhysperry111 · 2019-04-29 17:15:57

Dmesg output:

https://pastebin.com/Wx8KHA7y

seth · 2019-04-29 17:28:55

Skip the "acpi=force acpi_osi=linux acpi_backlight=vendor" stuff, you already get some sort of events from the kernel.

How can acpi_listen not record those keys? Did you it as root?
There also seems no backlight device registered in the dmesg, can you control the backlight using xbacklight or by writing into the device (do you have one?), https://wiki.archlinux.org/index.php/Backlight#ACPI

rhysperry111 · 2019-04-29 17:46:42

Removed kernel parameters. I have run acpi listen as root but still no output.

I can manually control the brightness through /sys/class/backlight/intel_backlight/brightness or through a utility called ‘light’ but xbacklight doesn’t work.

rhysperry111 · 2019-04-29 20:48:53

Update: I don’t know if this helps but I have found out some extra info. The device that handles brightness is called ‘HP WMI hotkeys’ and is on /dev/input/event11 and the device that handles the wireless toggle is ‘HP Wireless hotkeys’ on /dev/input/event4. The problem is both of these don’t seem to send/receive anything on key presses.

The strange thing is the standard keyboard on /dev/input/event3 is the one handling the brightness keys and is giving the scan code of ‘ab’ when I press the brightness keys.

seth · 2019-04-30 13:19:32

How do you know this? Do they respond to "libinput debug-events" or "evtest"?

Sidenote: unless somebody responded please just edit your post instead of bumping the thread, see the forum rules.

rhysperry111 · 2019-04-30 16:20:49

I got those results from evtest.

I think my acpi is messed up. I was using acpi_listen and found out that for some reason closing the laptop’s lid reports ‘button/wlan WLAN 00000080 00000000 K’

Last edited by rhysperry111 (2019-04-30 18:35:58)

seth · 2019-04-30 19:25:44

So the keyboard generates regular keyboard events. Nice. (Also for the radio toggle?)
It falls apart at the event driver, do you use evdev at all (default is libintput) - please post your xorg log (also for the actually used symbol table) and also the actual evtest outputs (there're a bunch of HP specific rules, geometries and symbols in xkb - maybe one fits)

rhysperry111 · 2019-05-21 15:49:15

Sorry so being long (been doing exams).

So, the radio toggle does NOT generate anything in evtest. Also, the /dev/input device that does things whenever pressing brightness keys is:

/event3 "AT Translated Set 2 Keyboard"

which I'm guessing is standard keyboard. When pressing the brightness keys it gives the following output (this is me pressing brightness down, releasing, pressing brightness up, releasing):

Event: time 1558452934.616388, type 4 (EV_MSC), code 4 (MSC_SCAN), value ab
Event: time 1558452934.616388, -------------- SYN_REPORT ------------
Event: time 1558452934.626992, type 4 (EV_MSC), code 4 (MSC_SCAN), value ab
Event: time 1558452934.626992, -------------- SYN_REPORT ------------
Event: time 1558452936.236362, type 4 (EV_MSC), code 4 (MSC_SCAN), value ab
Event: time 1558452936.236362, -------------- SYN_REPORT ------------
Event: time 1558452936.246850, type 4 (EV_MSC), code 4 (MSC_SCAN), value ab
Event: time 1558452936.246850, -------------- SYN_REPORT ------------

I also found this which is presented when i select the input device in evtest:

Supported events:
...
Event code 224 (KEY_BRIGHTNESSDOWN)
Event code 225 (KEY_BRIGHTNESSUP)
...

Xorg log

Evtest output (full)

seth · 2019-05-21 20:34:35

Nope, that's the output matching the

[   27.218942] atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[   27.218944] atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[   27.230727] atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[   27.230730] atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[   27.814096] atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
[   27.814103] atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[   27.824651] atkbd serio0: Unknown key released (translated set 2, code 0xab on isa0060/serio0).
[   27.824659] atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.

condition.

Relevant link is https://wiki.archlinux.org/index.php/Ma … o_keycodes
Did you try

setkeycodes e02b 224

? Does it spit out that value for every HW key you press?

Arch Linux

#1 2019-04-28 23:18:49

Certain keyboard keys not working.

#2 2019-04-28 23:30:07

Re: Certain keyboard keys not working.

#3 2019-04-29 07:28:23

Re: Certain keyboard keys not working.

#4 2019-04-29 11:15:31

Re: Certain keyboard keys not working.

#5 2019-04-29 15:33:16

Re: Certain keyboard keys not working.

#6 2019-04-29 16:30:55

Re: Certain keyboard keys not working.

#7 2019-04-29 17:06:13

Re: Certain keyboard keys not working.

#8 2019-04-29 17:15:57

Re: Certain keyboard keys not working.

#9 2019-04-29 17:28:55

Re: Certain keyboard keys not working.

#10 2019-04-29 17:46:42

Re: Certain keyboard keys not working.

#11 2019-04-29 20:48:53

Re: Certain keyboard keys not working.

#12 2019-04-30 13:19:32

Re: Certain keyboard keys not working.

#13 2019-04-30 16:20:49

Re: Certain keyboard keys not working.

#14 2019-04-30 19:25:44

Re: Certain keyboard keys not working.

#15 2019-05-21 15:49:15

Re: Certain keyboard keys not working.

#16 2019-05-21 20:34:35

Re: Certain keyboard keys not working.

Board footer