From: "Randy.Dunlap" <rddunlap@osdlab.org>
To: Erik Mouw <J.A.K.Mouw@ITS.TUDelft.NL>,
Alan <alan@lxorguk.ukuu.org.uk>,
crutcher+kernel@datastacks.com,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Magic SysRq +# in 2.4.9-ac/2.4.10-pre12
Date: Wed, 19 Sep 2001 10:50:25 -0700 [thread overview]
Message-ID: <3BA8DAE1.4F1E2195@osdlab.org> (raw)
In-Reply-To: <3BA8C01D.79FBD7C3@osdlab.org> <20010919193105.E7179@arthur.ubicom.tudelft.nl> <3BA8D723.51F17211@osdlab.org>
"Randy.Dunlap" wrote:
>
> Erik Mouw wrote:
> >
> > On Wed, Sep 19, 2001 at 08:56:13AM -0700, Randy.Dunlap wrote:
> > > I have an IBM model KB-9910 keyboard. When I use
> > > Alt+SysRQ+number (number: 0...9) on it to change the
> > > console loglevel, only keys 5 and 6 have the desired
> > > effect. I used showkey -s to view the scancodes from
> > > the other <number> keys, but showkey didn't display
> > > anything for them. Any other suggestions?
> >
> > Same over here with an IBM PS/2 keyboard that originally came with an
> > IBM PS2 model 55SX. The IBM keyboard is connected to an Asus M8300
> > laptop. The keyboard of that laptop has the interesting "feature" that
> > Alt-SysRQ-m sets the loglevel to 0, and Alt-SysRQ-[suob] also set the
> > loglevel to a different value instead of doing their job.
>
> I'm having this (my same) problem on a different test system/keyboard,
> and I'm beginning to think that it's not a keyboard problem,
> but I don't have any evidence of that one way or the other.
>
> I've tested 2.4.2, 2.4.5, 2.4.6, 2.4.7, 2.4.9, and 2.4.10-pre,
> and all exhibit the same problem.
My Logitech Y-SG13 keyboard works nicely with Alt+SysRq+#,
so I won't go after other ghosts.
~Randy
next prev parent reply other threads:[~2001-09-19 17:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-19 15:56 Magic SysRq +# in 2.4.9-ac/2.4.10-pre12 Randy.Dunlap
2001-09-19 16:30 ` Randy.Dunlap
2001-09-19 16:42 ` Alan Cox
2001-09-19 18:02 ` Randy.Dunlap
2001-09-19 17:31 ` Erik Mouw
2001-09-19 17:34 ` Randy.Dunlap
2001-09-19 17:50 ` Randy.Dunlap [this message]
2001-09-19 17:52 ` Erik Mouw
2001-09-19 20:22 ` Vojtech Pavlik
2001-09-21 20:29 ` Crutcher Dunnavant
2001-09-26 20:38 ` Pavel Machek
2001-10-03 15:08 ` Crutcher Dunnavant
2001-09-21 21:08 ` Crutcher Dunnavant
2001-09-21 21:41 ` [PATCH] Magic SysRq loglevel fix Crutcher Dunnavant
2001-09-22 1:25 ` Randy.Dunlap
2001-09-22 5:16 ` Crutcher Dunnavant
2001-09-21 21:42 ` Magic SysRq +# in 2.4.9-ac/2.4.10-pre12 Randy.Dunlap
2001-09-21 22:07 ` Crutcher Dunnavant
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=3BA8DAE1.4F1E2195@osdlab.org \
--to=rddunlap@osdlab.org \
--cc=J.A.K.Mouw@ITS.TUDelft.NL \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=crutcher+kernel@datastacks.com \
--cc=linux-kernel@vger.kernel.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