Messages in this thread | | | From | Dominik Karall <> | Subject | Re: setkeycodes (KDSETKEYCODE: Invalid argument) | Date | Tue, 5 Jul 2005 17:27:58 +0200 |
| |
On Monday 04 July 2005 23:43, federico wrote: > hi all, > > i have a problem: i got a white Apple usb keyboard, but this keyboard > doesn't have PrintScr nor SysRq. > i read in Documentation/sysrq.txt how to change the SYSRQ scancode. > i launched showkey and acknowledged that R_Alt+F13 is 100,183 => 64b7. > i ran > > # setkeycodes 64b7 84 > KDSETKEYCODE: No such device > failed to set scancode b7 to keycode 84 > > i'm on a gentoo-vanilla 2.6.13_rc1 with kbd-1.12-r5. (or on > 2.6.11-gentoo-r9 which produces the same result) > > here's some relevant output from strace: > > open("/dev/tty", O_RDWR) = 3 > ioctl(3, KDGKBTYPE, 0xbffdfcb7) = 0 > ioctl(3, KDSETKEYCODE, 0xbffdfd20) = -1 ENODEV (No such device) > dup(2) = 4 > fcntl64(4, F_GETFL) = 0x8001 (flags O_WRONLY|O_LARGEFILE) > close(4) = 0 > ... > write(2, "KDSETKEYCODE: No such device\n", 29KDSETKEYCODE: No such device > ) = 29 > ... > write(2, "failed to set scancode 64b7 to k"..., 42failed to set scancode > 64b7 to > keycode 84 > ) = 42
Does setkeycode work with current kernels? When I try to set a keycode, I always get following error:
dominik@box # LANG="C" setkeycodes e03e 84 KDSETKEYCODE: Invalid argument failed to set scancode be to keycode 84
but my dmesg output tells me, that this should be ok: atkbd.c: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). atkbd.c: Use 'setkeycodes e03e <keycode>' to make it known.
so, is the output from atkbd.c wrong, or does setkeycodes work in the wrong way?
cheers, dominik [unhandled content-type:application/pgp-signature] | |