I reported earlier that several keys emit different keycodes using PS/2 versus USB. For example, the "My Computer" key emits keycode 235 using PS/2, but keycode 111 using USB. Any inconsistency is annoying, but this one in particular is especially bad: 111 is already supposed to be the keycode that the "PrintScn" key emits.
So not only dooes the standard XKB "microsoftpro" keyboard model fail to work when using USB, but here's a case in which an end user cannot fix it no matter what he does with xmodmap. The "My Computer" and "PrintScn" keys both emit the same keycode. They are indistinguishable even to the X server itself. I said it before, and I say it again: I think it's really important that this keyboard emit the same keycodes using either PS/2 or USB. The existing PS/2 keycodes have become a de facto standard, and are reflected in such things as the XKB keyboard definition files. For any specific given keyboard, the USB side should be producing the same keycodes that the PS/2 drivers already use. _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
