All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: Fredrik Roubert <roubert@df.lth.se>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	linux-input@atrey.karlin.mff.cuni.cz,
	linux-kernel@vger.kernel.org
Subject: Re: Magic Alt-SysRq change in 2.6.18-rc1
Date: Mon, 10 Jul 2006 11:59:41 +0200	[thread overview]
Message-ID: <200607101159.41738.mb@bu3sch.de> (raw)
In-Reply-To: <20060710094414.GD1640@igloo.df.lth.se>

On Monday 10 July 2006 11:44, Fredrik Roubert wrote:
> On Sun 09 Jul 23:06 CEST 2006, Alan Stern wrote:
> 
> > Before 2.6.18-rc1, I used to be able to use it as follows:
> >
> > 	Press and hold an Alt key,
> > 	Press and hold the SysRq key,
> > 	Release the Alt key,
> > 	Press and release some hot key like S or T or 7,
> > 	Repeat the previous step as many times as desired,
> > 	Release the SysRq key.
> >
> > This scheme doesn't work any more,
> 
> The SysRq code has been updated to make it useable with keyboards that
> are broken in other ways than your. With the new behaviour, you should
> be able to use Magic SysRq with your keyboard in this way:
> 
> 	Press and hold an Alt key,
> 	Press and release the SysRq key,
> 	Press and release some hot key like S or T or 7,
> 	Repeat the previous step as many times as desired,
> 	Release the Alt key.

While we are at it, does someone know how to trigger
the sysrq on a PowerBook? Kernel Documentation says to press F13,
but the PowerBook keyboard does not have F13.

-- 
Greetings Michael.

  reply	other threads:[~2006-07-10  9:58 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-09 21:06 Magic Alt-SysRq change in 2.6.18-rc1 Alan Stern
2006-07-10  0:22 ` Andrew Morton
2006-07-10  1:12 ` H. Peter Anvin
2006-07-10  3:08   ` Joshua Hudson
2006-07-10  9:44 ` Fredrik Roubert
2006-07-10  9:59   ` Michael Buesch [this message]
2006-07-10 21:59   ` Roman Zippel
2006-07-11 12:41     ` Pavel Machek
2006-07-11 22:21       ` Roman Zippel
2006-07-11 22:42         ` [patch] " Pavel Machek
2006-07-11 23:33           ` Roman Zippel
2006-07-11 23:50             ` Andrew Morton
2006-07-12  0:16               ` Roman Zippel
2006-07-12  0:37                 ` Andrew Morton
2006-07-12  0:52                   ` Roman Zippel
2006-07-12  1:36                     ` Andrew Morton
2006-07-12  8:08                       ` Pavel Machek
2006-07-12  9:07                       ` Roman Zippel
2006-07-12 13:26                         ` Paulo Marques
2006-07-12 19:42                           ` Paulo Marques
2006-07-12 20:05                             ` Dmitry Torokhov
2006-07-12 22:21                               ` Paulo Marques
2006-07-12 22:44                                 ` Pavel Machek
2006-07-13 18:48                                 ` Dmitry Torokhov
2006-07-12  7:26                 ` Fredrik Roubert
2006-07-12  9:09                   ` Roman Zippel
2006-07-12 15:12                   ` Randy.Dunlap
2006-07-11 12:42     ` Pavel Machek
2006-07-11 13:54     ` Alan Stern
  -- strict thread matches above, loose matches on Subject: below --
2006-07-10  0:01 Chuck Ebbert

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=200607101159.41738.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@atrey.karlin.mff.cuni.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roubert@df.lth.se \
    --cc=stern@rowland.harvard.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.