Red Hat Bugzilla – Bug 200331
Neither the 'setkeycodes' nor 'getkeycodes' commands appear to work.
Last modified: 2007-11-30 17:11:38 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:184.108.40.206) Gecko/20060614 Fedora/220.127.116.11-1.2.fc5 Firefox/18.104.22.168 pango-text
Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Give the command
# setkeycodes 1 1
to the shell prompt, or just
KDSETKEYCODE: No such device
failed to set scancode 1 to keycode 1
KDGETKEYCODE: No such device
Build Host: ls20-bc2-14.build.redhat.com
Source RPM: kbd-1.12-13.2.src.rpm
What kind of keyboard to you use? If it is an USB keyboard, do the commands
work after you connect a regular PS/2 keyboard?
For completeness, please attach the log file created by (strace -o log getkeycodes).
Created attachment 133225 [details]
Output of failed (strace getkeycodes) for USB keyboard
Created attachment 133226 [details]
Output of successful (strace getkeycodes) for PS/2 keyboard
Currently using a standard Dell USB corded keyboard.
But everything works fine with an old PS/2 corded keyboard.
The behavior is correct, although not user-friendly: the USB HID standard
defines keyboard scan codes, so there should be no need to modify the
mapping and the USB keyboard driver thus does not support this function.
I'll send a patch upstream to make the error message more informative.