From: Vojtech Pavlik <vojtech@suse.cz>
To: federico <xaero@inwind.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: setkeycodes, sysrq, and USB keyboard
Date: Tue, 5 Jul 2005 00:05:32 +0200 [thread overview]
Message-ID: <20050704220532.GA2086@ucw.cz> (raw)
In-Reply-To: <42C9AD67.5050808@inwind.it>
On Mon, Jul 04, 2005 at 11:43:03PM +0200, 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
>
> if anyone has a possible solution i really appreciate.
> ciao!
Sorry, you can't use 'setkeycodes' on USB keyboards. They don't use the
PS/2 protocol, and hence it doesn't make sense.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next prev parent reply other threads:[~2005-07-04 22:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-04 21:43 setkeycodes, sysrq, and USB keyboard federico
2005-07-04 22:05 ` Vojtech Pavlik [this message]
2005-07-05 9:21 ` federico
2005-07-05 15:27 ` setkeycodes (KDSETKEYCODE: Invalid argument) Dominik Karall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050704220532.GA2086@ucw.cz \
--to=vojtech@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=xaero@inwind.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox