N5110 Keyboard extra buttons

ExNeroAngelo · 2019-01-21 21:07:32

Hey everyone. i can't use 2 of my extra buttons on keyboard. [3 buttons on upper right of my keyboard]. I have Dell Inspiron N5110. also I'm using Openbox.
my xinput list :

 ⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ AlpsPS/2 ALPS GlidePoint                	id=14	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Video Bus                               	id=7	[slave  keyboard (3)]
    ↳ Video Bus                               	id=8	[slave  keyboard (3)]
    ↳ Power Button                            	id=9	[slave  keyboard (3)]
    ↳ Sleep Button                            	id=10	[slave  keyboard (3)]
    ↳ Laptop_Integrated_Webcam_HD: In         	id=11	[slave  keyboard (3)]
    ↳ Dell WMI hotkeys                        	id=12	[slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard            	id=13	[slave  keyboard (3)]

when using "xev -event keyboard" there is no output for 2 of them but for last one :

KeyRelease event, serial 28, synthetic NO, window 0x2e00001,
    root 0x14e, subw 0x2e00002, time 3520835, (38,38), root:(39,545),
    state 0x50, keycode 133 (keysym 0xffeb, Super_L), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

Last edited by ExNeroAngelo (2019-01-21 21:10:35)

seth · 2019-01-21 22:10:44

See whether they generate anything on "sudo libinput debug-events".
The third one is just the windows key (meta, super_l, start, the thing w/ the windows logo on most keyboards)

ExNeroAngelo · 2019-01-21 23:24:53

seth wrote:

See whether they generate anything on "sudo libinput debug-events".
The third one is just the windows key (meta, super_l, start, the thing w/ the windows logo on most keyboards)

that's not the super key it's a settings button. btw the code for "sudo libinput debug-events" :

-event3   DEVICE_ADDED     Power Button                      seat0 default group1  cap:k
-event5   DEVICE_ADDED     Video Bus                         seat0 default group2  cap:k
-event4   DEVICE_ADDED     Video Bus                         seat0 default group2  cap:k
-event1   DEVICE_ADDED     Power Button                      seat0 default group3  cap:k
-event0   DEVICE_ADDED     Lid Switch                        seat0 default group4  cap:S
-event2   DEVICE_ADDED     Sleep Button                      seat0 default group5  cap:k
-event14  DEVICE_ADDED     HDA NVidia HDMI/DP,pcm=3          seat0 default group6  cap:
-event15  DEVICE_ADDED     HDA NVidia HDMI/DP,pcm=7          seat0 default group6  cap:
-event16  DEVICE_ADDED     HDA NVidia HDMI/DP,pcm=8          seat0 default group6  cap:
-event17  DEVICE_ADDED     HDA NVidia HDMI/DP,pcm=9          seat0 default group6  cap:
-event12  DEVICE_ADDED     Laptop_Integrated_Webcam_HD: In   seat0 default group7  cap:k
-event10  DEVICE_ADDED     HDA Intel PCH Mic                 seat0 default group6  cap:
-event11  DEVICE_ADDED     HDA Intel PCH Headphone           seat0 default group6  cap:
-event8   DEVICE_ADDED     Dell WMI hotkeys                  seat0 default group8  cap:k
-event6   DEVICE_ADDED     AT Translated Set 2 keyboard      seat0 default group9  cap:k
-event13  DEVICE_ADDED     AlpsPS/2 ALPS GlidePoint          seat0 default group10 cap:p  size 71x50mm tap(dl off) left scroll-nat scroll-2fg-edge dwt-on

this is for working button :

-event6   KEYBOARD_KEY      +2.21s	KEY_LEFTMETA (125) pressed
 event6   KEYBOARD_KEY      +2.21s	*** (-1) pressed
x event6   KEYBOARD_KEY      +2.22s	*** (-1) released
 event6   KEYBOARD_KEY      +2.22s	KEY_LEFTMETA (125) released

those two buttons didn't send any respond.

seth · 2019-01-22 08:25:46

It is the super_l key, no matter what the imprint says.
Though from the debug it looks like it tries to generate a key combo, likely Super_L+i (because this seems to be the windows settings shortcut) but fails on the second one (why you only see the super key pressed on higher levels)
You may be able to fix that in /usr/lib/udev/hwdb.d if there's an unhandled key message from udev in your journal.

The other two keys don't generate events on the kernel level. If you're lucky, they still create acpi events that show up in acpi_listen.

ExNeroAngelo · 2019-01-22 20:06:44

seth wrote:

It is the super_l key, no matter what the imprint says.
Though from the debug it looks like it tries to generate a key combo, likely Super_L+i (because this seems to be the windows settings shortcut) but fails on the second one (why you only see the super key pressed on higher levels)
You may be able to fix that in /usr/lib/udev/hwdb.d if there's an unhandled key message from udev in your journal.
The other two keys don't generate events on the kernel level. If you're lucky, they still create acpi events that show up in acpi_listen.

so this is the log for buttons in acpi_listen :

Jan 22 23:31:14 arch kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xee on isa0060/serio0).
Jan 22 23:31:14 arch kernel: atkbd serio0: Use 'setkeycodes e06e <keycode>' to make it known.

and for second button (turn off display):

Jan 22 23:34:04 arch acpid[465]: client connected from 1600[1000:1000]
Jan 22 23:34:04 arch acpid[465]: 1 client rule loaded
Jan 22 23:34:08 arch acpid[465]: client 1600[1000:1000] has disconnected

seth · 2019-01-22 20:27:24

The second output doesn't look like acpi_listen (actually both look more like the journal), but the key is registered and something acts up on it - just maybe not the expected way.
"1600" is the PID of the process that should do somthiing.

As for the first output: for which button is this?
You can use the hinted setkeycodes call to make it generate a keycode (and ultimately be accesible, https://wiki.archlinux.org/index.php/ma … o_keycodes - codes to be found in /usr/include/linux/input-event-codes.h )

ExNeroAngelo · 2019-01-24 15:05:02

seth wrote:

The second output doesn't look like acpi_listen (actually both look more like the journal), but the key is registered and something acts up on it - just maybe not the expected way.
"1600" is the PID of the process that should do somthiing.
As for the first output: for which button is this?
You can use the hinted setkeycodes call to make it generate a keycode (and ultimately be accesible, https://wiki.archlinux.org/index.php/ma … o_keycodes - codes to be found in /usr/include/linux/input-event-codes.h )

yes they are from journal . I used "xmodmap -pke | less" and got info for keycodes. than i used "setkeycodes e06e 156" (keycode 156 = XF86Launch1 NoSymbol XF86Launch1).
what should i do next?
for the other button how can i find the name of "1600" PID?

Last edited by ExNeroAngelo (2019-01-24 15:16:16)

seth · 2019-01-24 15:15:47

xev should now register the key (you might have to restart X11 after assigning the keycode) and you would then be able to assign it to some shortcut.
If everything works fine, you can add an entry in the hwdb to automatically assign the keycode (preferably in /etc/udev/hwdb.d, files in /usr/lib/udev/hwdb.d/ will get overridden with updates) and maybe file a bug against udev (the notebook model doesn't seem new, so it's not likely to be auto-fixed unless somebody calls for it)

ExNeroAngelo · 2019-01-24 15:28:11

seth wrote:

xev should now register the key (you might have to restart X11 after assigning the keycode) and you would then be able to assign it to some shortcut.
If everything works fine, you can add an entry in the hwdb to automatically assign the keycode (preferably in /etc/udev/hwdb.d, files in /usr/lib/udev/hwdb.d/ will get overridden with updates) and maybe file a bug against udev (the notebook model doesn't seem new, so it's not likely to be auto-fixed unless somebody calls for it)

this time i got this form journal :

Jan 24 18:55:52 arch acpid[467]: client connected from 14980[1000:1000]
Jan 24 18:55:52 arch acpid[467]: 1 client rule loaded
Jan 24 18:55:57 arch acpid[467]: client 14980[1000:1000] has disconnected

after using alt+ctrl+f2 second button worked too. how can i add entry to hwdb? (the wiki is overwhelming!)
btw PID of "1600" was acpi_listen. so the last one (the one for turning display off) is not working.

Last edited by ExNeroAngelo (2019-01-24 15:51:30)

seth · 2019-01-24 15:54:13

See the link I posted.
According to /usr/lib/udev/hwdb.d/60-keyboard.hwdb the general identifier matching dell is "evdev:atkbd:dmi:bvn*:bvr*:bd*:svnDell*:pn"

ExNeroAngelo · 2019-01-24 16:31:33

seth wrote:

See the link I posted.
According to /usr/lib/udev/hwdb.d/60-keyboard.hwdb the general identifier matching dell is "evdev:atkbd:dmi:bvn*:bvr*:bd*:svnDell*:pn"

my 90-custom-keyboard.hwdb :

evdev:atkbd:dmi:bvn*:bvr*:bd*:svnDell*:pn
 KEYBOARD_KEY_ee=f23

after that i used "systemd-hwdb update" and "udevadm trigger" but still no feedback from button.

Last edited by ExNeroAngelo (2019-01-24 16:31:52)

seth · 2019-01-24 20:35:56

I don't think function keys > F20 will work at all and why "_ee", your former post suggested the scancode was e06e?

ExNeroAngelo · 2019-01-24 23:16:02

seth wrote:

I don't think function keys > F20 will work at all and why "_ee", your former post suggested the scancode was e06e?

i used ee because of "0xee". F15 is not working either.
from wiki : "The value of <scancode> is hexadecimal, but without the leading 0x (i.e. specify a0 instead of 0xa0)"

Last edited by ExNeroAngelo (2019-01-24 23:17:01)

seth · 2019-01-24 23:18:09

The scancode is e06e - it worked when you were using setkeycodes, did it?

ExNeroAngelo · 2019-01-25 01:16:01

seth wrote:

The scancode is e06e - it worked when you were using setkeycodes, did it?

yeah it did. so what should i use?

seth · 2019-01-25 07:46:43

The working scancode??
Saw your edit: e06e is hexadecimal as well - the notion in the wiki tells you to omit the 0x, not that a string occuring somehere but including the 0x is the actual scancode.

ExNeroAngelo · 2019-01-25 15:19:35

seth wrote:

The working scancode??
Saw your edit: e06e is hexadecimal as well - the notion in the wiki tells you to omit the 0x, not that a string occuring somehere but including the 0x is the actual scancode.

evdev:atkbd:dmi:bvn*:bvr*:bd*:svnDell*:pn
 KEYBOARD_KEY_e06e=f14

this didn't work either.
also i tried "showkey -s" and this is the respond for the working button (the one with super+L) :

0xe0 0x5b 0x2d 0xad 0xe0 0xdb

Last edited by ExNeroAngelo (2019-01-25 15:37:53)

seth · 2019-01-25 15:54:52

Let's see whether it's loaded and applied:

udevadm info /dev/input/by-path/* | grep KEYBOARD_KEY

ExNeroAngelo · 2019-01-25 16:06:28

seth wrote:

Let's see whether it's loaded and applied:
udevadm info /dev/input/by-path/* | grep KEYBOARD_KEY

nope :

udevadm info /dev/input/by-path/* | grep KEYBOARD_KEY
E: KEYBOARD_KEY_81=playpause
E: KEYBOARD_KEY_82=stopcd
E: KEYBOARD_KEY_83=previoussong
E: KEYBOARD_KEY_84=nextsong
E: KEYBOARD_KEY_85=brightnessdown
E: KEYBOARD_KEY_86=brightnessup
E: KEYBOARD_KEY_87=battery
E: KEYBOARD_KEY_88=unknown
E: KEYBOARD_KEY_89=ejectclosecd
E: KEYBOARD_KEY_8a=suspend
E: KEYBOARD_KEY_8b=switchvideomode
E: KEYBOARD_KEY_8c=unknown
E: KEYBOARD_KEY_8f=switchvideomode
E: KEYBOARD_KEY_90=previoussong
E: KEYBOARD_KEY_91=prog1
E: KEYBOARD_KEY_92=media
E: KEYBOARD_KEY_93=unknown
E: KEYBOARD_KEY_95=camera
E: KEYBOARD_KEY_97=email
E: KEYBOARD_KEY_98=f21
E: KEYBOARD_KEY_99=nextsong
E: KEYBOARD_KEY_9a=setup
E: KEYBOARD_KEY_9b=switchvideomode
E: KEYBOARD_KEY_9e=f21
E: KEYBOARD_KEY_a2=playpause
E: KEYBOARD_KEY_a4=stopcd
E: KEYBOARD_KEY_d8=screenlock
E: KEYBOARD_KEY_d9=f21
E: KEYBOARD_KEY_ed=media

seth · 2019-01-25 16:43:50

You could try to skip the vendor,

evdev:atkbd:dmi:bvn*:bvr*:bd*:svn*:pn

/etc/udev/hwdb.bin gets updated?

ExNeroAngelo · 2019-01-25 16:55:54

seth wrote:

You could try to skip the vendor,
evdev:atkbd:dmi:bvn*:bvr*:bd*:svn*:pn
/etc/udev/hwdb.bin gets updated?

i tried this

evdev:atkbd:dmi:bvn*:bvr*:bd*:svn*:pn

there is no respond from "acpi_listen" but "showkey -s" shows "0x5d".
still can't use the button for obkey...

Last edited by ExNeroAngelo (2019-01-26 13:29:27)

Arch Linux

#1 2019-01-21 21:07:32

N5110 Keyboard extra buttons

#2 2019-01-21 22:10:44

Re: N5110 Keyboard extra buttons

#3 2019-01-21 23:24:53

Re: N5110 Keyboard extra buttons

#4 2019-01-22 08:25:46

Re: N5110 Keyboard extra buttons

#5 2019-01-22 20:06:44

Re: N5110 Keyboard extra buttons

#6 2019-01-22 20:27:24

Re: N5110 Keyboard extra buttons

#7 2019-01-24 15:05:02

Re: N5110 Keyboard extra buttons

#8 2019-01-24 15:15:47

Re: N5110 Keyboard extra buttons

#9 2019-01-24 15:28:11

Re: N5110 Keyboard extra buttons

#10 2019-01-24 15:54:13

Re: N5110 Keyboard extra buttons

#11 2019-01-24 16:31:33

Re: N5110 Keyboard extra buttons

#12 2019-01-24 20:35:56

Re: N5110 Keyboard extra buttons

#13 2019-01-24 23:16:02

Re: N5110 Keyboard extra buttons

#14 2019-01-24 23:18:09

Re: N5110 Keyboard extra buttons

#15 2019-01-25 01:16:01

Re: N5110 Keyboard extra buttons

#16 2019-01-25 07:46:43

Re: N5110 Keyboard extra buttons

#17 2019-01-25 15:19:35

Re: N5110 Keyboard extra buttons

#18 2019-01-25 15:54:52

Re: N5110 Keyboard extra buttons

#19 2019-01-25 16:06:28

Re: N5110 Keyboard extra buttons

#20 2019-01-25 16:43:50

Re: N5110 Keyboard extra buttons

#21 2019-01-25 16:55:54

Re: N5110 Keyboard extra buttons

Board footer