Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758317AbYHAM4d (ORCPT ); Fri, 1 Aug 2008 08:56:33 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755015AbYHAM4Z (ORCPT ); Fri, 1 Aug 2008 08:56:25 -0400 Received: from mk-outboundfilter-3.mail.uk.tiscali.com ([212.74.114.23]:16006 "EHLO mk-outboundfilter-3.mail.uk.tiscali.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754670AbYHAM4Y (ORCPT ); Fri, 1 Aug 2008 08:56:24 -0400 X-Trace: 151696647/mk-outboundfilter-1.mail.uk.tiscali.com/F2S/$F2S-NILDRAM-ACCEPTED/f2s-nildram-customers/195.149.44.6 X-SBRS: None X-RemoteIP: 195.149.44.6 X-IP-MAIL-FROM: alistair@devzero.co.uk X-IP-BHB: Once X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AoQFAL+kkkjDlSwG/2dsb2JhbACBW4lFpgs X-IronPort-AV: E=Sophos;i="4.31,293,1215385200"; d="scan'208";a="151696647" X-IP-Direction: IN From: Alistair John Strachan To: "Zdenek Kabelac" Subject: Re: Sysrq+B doesn't work on my box Date: Fri, 1 Aug 2008 13:56:18 +0100 User-Agent: KMail/1.10.0 (Linux/2.6.27-rc1-damocles; KDE/4.1.0; x86_64; ; ) Cc: "Jeremy Fitzhardinge" , "Henrique de Moraes Holschuh" , "Linux Kernel Mailing List" References: <48921A0C.7020909@goop.org> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200808011356.19027.alistair@devzero.co.uk> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1188 Lines: 33 On Friday 01 August 2008 10:54:19 Zdenek Kabelac wrote: > 2008/7/31 Jeremy Fitzhardinge : > > Zdenek Kabelac wrote: > >> SysRQ+B doesn't work with right AltGr on my keyboard - but it does > >> work with the left Alt which I'm not normally using (It's somewhat > >> easier to use the right one) > >> Any idea why AltGR+SysRQ+b does not work on T61 ? > > > > You can type them separately: AltGr+SysRq, AltGr+b (holding AltGr across > > the sequence). > > Ok this sequence does work - so one mystery solved :) > > now the remaining part is. > > > I'll probably try to bisect rc.sysinit script to check what is the > first command > that breaks the reboot - but if there is any idea what should I test > first.? Are you using modules? Maybe a driver is loaded and this upsets the BIOS somehow? If that was the case, the driver wouldn't be loaded in an init=/bin/sh situation, as you described before. -- Cheers, Alistair. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/