From: Joachim Breuer <jmbreuer@gmx.net>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: David Woodhouse <dwmw2@infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: SysRq question
Date: Tue, 19 Mar 2002 12:45:56 +0100 [thread overview]
Message-ID: <m3pu20hjbf.fsf@venus.fo.et.local> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0203180922230.2434-100000@dragon.pdx.osdl.net>
"Randy.Dunlap" <rddunlap@osdl.org> writes:
> On Mon, 18 Mar 2002, David Woodhouse wrote:
>
> | rddunlap@osdl.org said:
> | > I've seen a couple of cheapo keyboards where some Alt-SysRq-key
> | > combinations don't generate anything from the keyboard. (I'm typing
> | > on one of them right now.) For example, Alt-SysRq-5|6 works, but
> | > 1,2,3,4,7,8,9 don't.
> |
> | Try using the other Alt key.
>
> Same result with either Alt key.
BTW that's not the problem I'm seeing, Alt-SysRq-*ANYTHING* is not
caught from any of the offending keyboards because (IIRC) they send
Alt-SysRq as a two-code sequence, with the (apparently) Alt-Down code
repeated before the command keycode - thus, all the command keycode
parser sees (it seems it looks only at the first byte after Alt-SysRq)
is the Alt-Down keycode, which is not a command.
--
"I use emacs, which might be thought of as a thermonuclear
word processor."
-- Neal Stephenson, "In the beginning... was the command line"
prev parent reply other threads:[~2002-03-19 11:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-18 13:52 2.4.18 freezes on heavy IO Richard Ems
2002-03-18 14:09 ` Chris Mason
2002-03-18 14:12 ` Clemens Schwaighofer
2002-03-18 14:16 ` Richard Ems
2002-03-18 14:42 ` Alan Cox
2002-03-18 14:20 ` Richard Ems
2002-03-18 15:48 ` 2.4.18 freezes on heavy IO; SysRq question Joachim Breuer
2002-03-18 16:42 ` Randy.Dunlap
2002-03-18 17:17 ` David Woodhouse
2002-03-18 17:22 ` Randy.Dunlap
2002-03-19 11:45 ` Joachim Breuer [this message]
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=m3pu20hjbf.fsf@venus.fo.et.local \
--to=jmbreuer@gmx.net \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
/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