You are not logged in.
I am at my wit's end. I have a custom keyboard (USB HID) that needs to have multiple scancodes remapped to valid keycodes. However, no matter what I try, I see no evidence that the remapping is effective. My primary reference has been: https://wiki.archlinux.org/index.php/Ma … o_keycodes
Here is a portion of my 99-TO117-keycodes.hwdb file:
evdev:input:*
KEYBOARD_KEY_70068=f25 ## 1 F25
KEYBOARD_KEY_70069=f26 ## 2 F26
KEYBOARD_KEY_7006a=f27 ## 3 F27
KEYBOARD_KEY_7006e=f13 ## 10 F13
KEYBOARD_KEY_7006f=f14 ## 11 F14
KEYBOARD_KEY_070070=f15 ## 12 F15
All of my research suggests using the following to update the hwdb:
udevadm hwdb --update
udevadm trigger
I then try using:
udevadm info /dev/input/by-id/<name>
and I see no "KEYBOARD_KEY*" entries in the output.
I use:
udevadm --debug test-builtin keyboard /devices/<path>
and it gives:
calling: test-builtin
=== trie on-disk ===
tool version: 208
file size: 6347147 bytes
header size 80 bytes
strings 1402059 bytes
nodes 4945008 bytes
load module index
device 0x7f1096a0fa40 has devpath '/devices/pci0000:00/0000:00:14.0/usb4/4-7/4-7.2/4-7.2.2/4-7.2.2:1.0/input/input13/event10'
device 0x7f1096a0fa40 filled with db file data
unload module index
Also with no indication of scancode remapping.
I have tried "keyboard:usb:*" but that seems to be deprecated as of system 220 update. In place of that, I have used "evdev:input:<stuff>" following the guidelines available online. Rebooting doesn't help. I'm sure I'm missing something simple.
Offline