On other distros (older kernels) and on Windows, pressing my f4 key would switch my display configuration. However, on Arch, that key seems to be assigned a different keycode. Examining xev, pressing the f4 key (without fn held down) generates this message
KeyPress event, serial 32, synthetic NO, window 0x1600001, root 0x91, subw 0x0, time 9265044, (96,452), root:(782,475), state 0x0, keycode 133 (keysym 0xffeb, Super_L), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False
pressing my windows key generates the same message, which is to be expected.
Xmodmap shows that XF86Display is actually mapped to keycode 235, while Super_L is mapped to keycode 133.
keycode 235 = XF86Display NoSymbol XF86Display
So my problem is that keycode 133 corresponds to two different keys on my keyboard, and I would like one of those keys (f4) to correspond to keycode 235. Is there anyway to accomplish this? I've read the xmodmap wiki, but from what I understand, I can only change a keycodes keysym. I don't want to change keycode 133's keysym, because that would also change the "real" Super_L key. I only want f4 to generate a different keycode.
EDIT: I should also mention that none of my keys generate keycode 235, at least when using xev.
Last edited by cris9288 (2013-05-07 04:12:32)
There's something very broken here, F4 should be 70.
What kind of keyboard is it? If it's PS/2, you can use showkey to find out what's the scancode sent by this key and then use setkeycodes to tell the kernel to map it to a different keycode. BTW, F4's scancode should be 0x3E, your keyboard probably is broken and generates something else.
Its a laptop keyboard. All other keys work fine except for this one. I hadn't come across the setkeycodes wiki, but I'll check it out when I get home today.
Use setxkbmap and xmodmap?