Hello everyone, I can’t get the numeric keypad on my Acer Chromebook 315 to work.
is there a particular configuration to do ?
I use debian 12
I use this script.
GitHub - WeirdTreeThing/chromebook-linux-audio: Script to enable audio support on many Chrome devices and this one.
GitHub - WeirdTreeThing/cros-keyboard-map: Utility to generate keyd configurations for use on Chromebooks
i find a solution.
https://www.reddit.com/r/chrultrabook/comments/whtbjw/acer_chromebook_315_gemini_lake_blorb_numpad_issue/
It seems that scan codes are coming in from the input device, but are not getting mapped to key press events.
I was able to get the numeric keypad working with ubuntu by creating a file /usr/lib/udev/hwdb.d/90-custom-keyboard.hwdb with the following contents:
evdev:atkbd:dmi:bvn*:bvr*:bd*:svn*:pn*:pvr*
KEYBOARD_KEY_c9=pageup
KEYBOARD_KEY_d1=pagedown
KEYBOARD_KEY_c7=home
KEYBOARD_KEY_cf=end
KEYBOARD_KEY_d3=delete
KEYBOARD_KEY_b5=kpslash
KEYBOARD_KEY_37=kpasterisk
KEYBOARD_KEY_4a=kpminus
KEYBOARD_KEY_47=kp7
KEYBOARD_KEY_48=kp8
KEYBOARD_KEY_49=kp9
KEYBOARD_KEY_4b=kp4
KEYBOARD_KEY_4c=kp5
KEYBOARD_KEY_4d=kp6
KEYBOARD_KEY_4e=kpplus
KEYBOARD_KEY_4f=kp1
KEYBOARD_KEY_50=kp2
KEYBOARD_KEY_51=kp3
KEYBOARD_KEY_52=kp0
KEYBOARD_KEY_53=kpdot
KEYBOARD_KEY_9c=kpenter
thensudo systemd-hwdb update
and reboot. More info at Map scancodes to keycodes - ArchWiki
Now I’m looking for a way to force the numlock
You can do all of that from keyd by modifying the config file at /etc/keyd/cros.conf
The syntax is slightly easier to read compared with udev