Dear Lazyweb,
How the hell can you configure how xorg's evdev will interpret keycodes?
I have evdev managing my mice now, and it works like a charm. Yet when I enable evdev for /dev/input/event0, which is the keyboard's dev location, I end up with a semi operational keyboard. I deduced, using a combination of .xinitrc, $($TERM), xev, and evtest, that certain keys are mapped to what they are not. For example Alt_L and Alt_R are mapped right, but Ctl_R is mapped with Next, and Pg_up is mapped to Menu.
I've currently got the setup so evdev runs the mice and kbd runs the keyboard, which keeps everything going, but still leaves me with something 'legacy'.
So lazy web, how the heck?
I have evdev managing my mice now, and it works like a charm. Yet when I enable evdev for /dev/input/event0, which is the keyboard's dev location, I end up with a semi operational keyboard. I deduced, using a combination of .xinitrc, $($TERM), xev, and evtest, that certain keys are mapped to what they are not. For example Alt_L and Alt_R are mapped right, but Ctl_R is mapped with Next, and Pg_up is mapped to Menu.
I've currently got the setup so evdev runs the mice and kbd runs the keyboard, which keeps everything going, but still leaves me with something 'legacy'.
So lazy web, how the heck?