Weird Keyboard Problem

[Antikx]

I have the same problem without tampering with the keymap. Can someone be
so kind to tell me what to do now? As far as I can see it is a matter of changing
the content of /etc/sysconfig/keyboard/kernel.map and rebooting. What should
be in this file to get a good result?

-- Marcus
[div align=\"right\"][a href=\"index.php?act=findpost&pid=113310\"][{POST_SNAPBACK}][/a][/div]

Maybe I'm missing something, but have you tried what is in the replys of three post above by km2783?
This works for me and stays working untill I go back into the Input Helper.... then I have to go back and edit kernel.map again.

[daniel3000]

Does anyone know the correct entry for kernel.map to swap slash and comma on the console?

Or, how do I get the keycode of a key?
And which strings are allowed as key identifiers on the right side?
Knowing that, I can create my own entries.

daniel

[wyvvie]

Fire up 'xev' from the terminal, press the key you wish to know the code for, and then check the output xev gives you.
 
You'll see something like this:

Code: [Select]

KeyPress event, serial 30, synthetic NO, window 0x1800001,
    root 0x46, subw 0x1800002, time 1544556304, (23,45), root:(342,386),
    state 0x0, keycode 62 (keysym 0xffe2, Shift_R), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: FalseIt's the bit after 'keysym 0xffex2' (Shift_R) that tells you the valid key code, and this is acceptable to put in your keymap/kernel.map file.

It works the same when pressing two keys (e.g, the 'Function' and '?.>' keys), telling you what each combination results in. (In that case 'Mode_switch', and '>').

I know I tend to over-simplify things, so  I apologise in advance

Hope this helps