Keyboard 2

> On Mon, 12 Jan 2004, Leonardo Lopes Pereira wrote:
>
>> > On Mon, 12 Jan 2004, Leonardo Lopes Pereira wrote:
>> >
>> >> I wan't to know, why the key "NUM LOCK" doesn't work? The light of
>> it stay off but the function stay active all the time.
>> >
>> > Hi Leonardo.  My keyboard acted differently also.  I don't know why
>> your NUM LOCK key isn't working specifically, but I recommend
>> comparing the outputs of "xmodmap -pk" under XFree86 and fdo's
>> Xserver.  Also, try running "xev" in an xterm and pressing NUM LOCK
>> to see what keycode it generates.
>> >
>> > I hope that helps.
>> >
>> >  - Joel
>> >
>>
>> I will show to you what apears with both commands that you say:
>>
>>  " xev "
>>
>> KeyPress event, serial 24, synthetic NO, window 0x1e00001,
>>     root 0x36, subw 0x0, time 177645011, (218,269), root:(231,323),
>> state 0x0, keycode 77 (keysym 0xff7f, Num_Lock), same_screen YES,
>> XLookupString gives 0 characters:  ""
>>
>>  " xmodmap -pk "
>>
>> There are 4 KeySyms per KeyCode; KeyCodes range from 8 to 135.
>>
>>     KeyCode     Keysym (Keysym) ...
>>     Value       Value   (Name)  ...
>>
>>      76         0xffc7 (F10)
>>      77         0xff7f (Num_Lock)
>>      78         0xff14 (Scroll_Lock)
>>      79         0xffb7 (KP_7)
>>      80         0xffb8 (KP_8)
>>      81         0xffb9 (KP_9)
>>
>> ( I have cutted some parts of xmodmap )
>>
>> It wall to be all correct, so, what is wrong that "Num Lock" doesn't
>> work ?
>>
>>
>What does "xmodmap -pm" show?

xmodmap:  up to 2 keys per modifier, (keycodes in parentheses):

shift       Shift_L (0x32),  Shift_R (0x3e)
lock        Caps_Lock (0x42)
control     Control_L (0x25),  Control_R (0x69)
mod1        Alt_L (0x40)
mod2        Num_Lock (0x4d)
mod3
mod4        Mode_switch (0x6c)
mod5