linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "D. Stimits" <stimits@idcomm.com>
To: "Mike A. Harris" <mharris@opensourceadvocate.org>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: missing sysrq
Date: Thu, 07 Jun 2001 22:38:52 -0600	[thread overview]
Message-ID: <3B2056DC.EBC00D80@idcomm.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0106072239570.26171-100000@asdf.capslock.lan>

"Mike A. Harris" wrote:
> 
> On Fri, 1 Jun 2001, Dieter Nützel wrote:
> 
> >> > In article <3B15EF16.89B18D@idcomm.com> you wrote:
> >> > > However, if I go to /proc/sys/kernel/sysrq does not exist.
> >> >
> >> > It is a compile time option, so the person who compiled your kernel
> >> > left it out.
> >>
> >> I compiled it, and the sysrq is definitely in the config. No doubt at
> >> all. I also use make mrproper and config again before dep and actual
> >> compile. Maybe it is just a quirk/oddball.
> >>
> >> D. Stimits, stimits@idcomm.com
> >
> >Have you tried "echo 1 > /proc/sys/kernel/sysrq"?
> >You need both, compiled in and activation.

Since then I've completely removed that kernel source and kernel, only
the config file remains (and it had it activated if the config followed
it). All kernels before worked, and those since then also work, so I
know it isn't the keyboard. I also always run make mrproper and config
it again between compiles (I keep a list of config history), so I don't
know what was wrong, but replacing the kernel fixed it, and is no longer
an issue. I will, however, keep the showkey suggestion handy in case it
ever does it again.

D. Stimits, stimits@idcomm.com

> 
> If you *know* it is compiled into your kernel, and you *know* it
> is enabled via the above, and it still does not work, do the
> following:
> 
> Run:
> 
> showkey -s
> 
> Then press LALT quickly followed by SYSRQ, and keep holding both
> down, and you should see:
> 
> 0x38
> 0x54
> 
> You might see a bunch of extra 0x38's which is ok.
> 
> If however when you press ALT-SYSRQ you see:
> 
> 0x38 0x54 0xd4
> 
> and are still holding both keys down, then your keyboard is
> broken and incompatible with the kernel SYSRQ feature.
> 
> A proper keyboard will only show "0x38 0x54".  I have written a
> patch for SYSRQ to allow it to be used with broken keyboards that
> send the make+break code for the SYSRQ sequence simultaneously.
> 
> If you need it, let me know and I'll send it to you.
> 
> ----------------------------------------------------------------------
>     Mike A. Harris  -  Linux advocate  -  Open Source advocate
>        Opinions and viewpoints expressed are solely my own.
> ----------------------------------------------------------------------

  reply	other threads:[~2001-06-08  4:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-01  3:51 missing sysrq Dieter Nützel
2001-06-08  2:46 ` Mike A. Harris
2001-06-08  4:38   ` D. Stimits [this message]
2001-06-09  1:10   ` David Ford
     [not found] <Pine.LNX.4.10.10106011050380.2614-100000@coffee.psychology.mcmaster.ca>
2001-06-01 20:52 ` Dieter Nützel
2001-06-01 22:31   ` george anzinger
2001-06-01 22:58     ` Dieter Nützel
2001-06-01 23:13   ` H. Peter Anvin
2001-06-02 19:03     ` Alan Cox
2001-06-02 19:10       ` H. Peter Anvin
2001-06-02 22:08     ` Russell King
2001-06-02 22:10       ` H. Peter Anvin
2001-06-02 22:39         ` Russell King
2001-06-02 22:42           ` H. Peter Anvin
     [not found] <200106010338.VAA13405@totalrecall.idcomm.com>
2001-06-01 16:05 ` D. Stimits
  -- strict thread matches above, loose matches on Subject: below --
2001-05-31  7:13 D. Stimits
2001-05-31 21:43 ` Bernd Eckenfels
2001-05-31 23:48   ` D. Stimits
2001-06-08  2:50     ` Mike A. Harris

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=3B2056DC.EBC00D80@idcomm.com \
    --to=stimits@idcomm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mharris@opensourceadvocate.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;
as well as URLs for NNTP newsgroup(s).