I have repurposed a X86-64 laptop running MS Win 10 to SL 7. I
installed a new "empty" harddrive and went from there; however, any
firmware modifications, etc., made by MS Win and not automatically
redone by SL would remain with the MS settings.
The 5 key on the keyboard (not the keypad in numlock mode) actually
transmits something else, displayed as ~5 and clearly is not a plain 5.
What utility allows one to get this (I have tried showkey to verify the
key with response:
[root@localhost pass]# showkey
kb mode was ?UNKNOWN?
[ if you are trying this under X, it might not work
since the X server is also reading /dev/console ]
press any key (program terminates 10s after last keypress)...
keycode 28 release
^[[15~5keycode 63 press
keycode 6 press
keycode 63 release
keycode 6 release
I have tried xev with output:
KeyPress event, serial 38, synthetic NO, window 0x3e00001,
root 0x2ec, subw 0x3e00002, time 65129543, (45,48), root:(74,168),
state 0x10, keycode 71 (keysym 0xffc2, F5), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 38, synthetic NO, window 0x3e00001,
root 0x2ec, subw 0x3e00002, time 65129546, (45,48), root:(74,168),
state 0x10, keycode 14 (keysym 0x35, 5), same_screen YES,
XLookupString gives 1 bytes: (35) "5"
XmbLookupString gives 1 bytes: (35) "5"
XFilterEvent returns: False
KeyRelease event, serial 38, synthetic NO, window 0x3e00001,
root 0x2ec, subw 0x3e00002, time 65129656, (45,48), root:(74,168),
state 0x10, keycode 71 (keysym 0xffc2, F5), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 38, synthetic NO, window 0x3e00001,
root 0x2ec, subw 0x3e00002, time 65129660, (45,48), root:(74,168),
state 0x10, keycode 14 (keysym 0x35, 5), same_screen YES,
XLookupString gives 1 bytes: (35) "5"
XFilterEvent returns: False
What other utilities and/or human-readable data can be used to diagnose
and possibly repair this issue?
Any help would be appreciated.
Yasha Karant
|
