i tried and made an .fdi file in /etc/hal/policy to map the keys using the codes yielded by input-events (as https://wiki.ubuntu.com/X/Config/Input suggests i should do), but it doesn't work at all..
lshal seems to indicate that the file did register and match properly, but there's still no response in xev.
i'm pretty sure that least some of the keycodes are valid, since i previously downloaded a keytouch file for the keyboard that maps only a few of the keys, and the keycodes match
i attach the (not working) fdi file. it contains the key codes. i'm not sure if the "input.originating_device" will match for other devices, i use it to make sure it matches only to the "second" keyboard (the "first" contains the regular keys).
i tried and made an .fdi file in /etc/hal/policy to map the keys using the codes yielded by input-events (as https:/ /wiki.ubuntu. com/X/Config/ Input suggests i should do), but it doesn't work at all.. originating_ device" will match for other devices, i use it to make sure it matches only to the "second" keyboard (the "first" contains the regular keys).
lshal seems to indicate that the file did register and match properly, but there's still no response in xev.
i'm pretty sure that least some of the keycodes are valid, since i previously downloaded a keytouch file for the keyboard that maps only a few of the keys, and the keycodes match
i attach the (not working) fdi file. it contains the key codes. i'm not sure if the "input.