From: Olaf Dabrunz <od@suse.de>
To: John Stoffel <john@stoffel.org>
Cc: Gerd Hoffmann <kraxel@suse.de>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Paul Mundt <lethal@linux-sh.org>,
Ralf Baechle <ralf@linux-mips.org>, Andi Kleen <ak@suse.de>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Richard Henderson <rth@twiddle.net>,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
Paul Mackerras <paulus@samba.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: [patch v2] Fixes and cleanups for earlyprintk aka boot console.
Date: Thu, 29 Mar 2007 18:37:14 +0200 [thread overview]
Message-ID: <20070329163714.GA29059@suse.de> (raw)
In-Reply-To: <17913.45970.178029.519745@smtp.charter.net>
On 15-Mar-07, John Stoffel wrote:
> Would this explain why recent version of GDM don't find the keyboard
> properly when you boot with a kernel command line of:
>
> kernel ... console=tty0 console=ttyS1,96008N1
>
> until you stop and restart GDM? This was filed under Debian bug
> #406457 (see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=406457)
> and I could never figure it out until I removed my serial console line
> at one point.
Try changing the order of the console= parameters:
kernel ... console=ttyS1,96008N1 console=tty0
Some time ago I understood what this does. Nowadays I can only remember
that this makes both the serial console and directly attached
screen/keyboard console work most of the time. FWIW, tty0 becomes the
so-called "preferred console".
--
Olaf Dabrunz (od/odabrunz), SUSE Linux Products GmbH, Nürnberg
next prev parent reply other threads:[~2007-03-29 16:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-15 15:46 [patch v2] Fixes and cleanups for earlyprintk aka boot console Gerd Hoffmann
2007-03-15 20:58 ` John Stoffel
2007-03-16 8:10 ` Gerd Hoffmann
2007-03-29 16:37 ` Olaf Dabrunz [this message]
2007-04-03 15:42 ` John Stoffel
2007-04-11 18:33 ` Olaf Dabrunz
2007-04-24 6:42 ` Andrew Morton
2007-04-24 14:04 ` Gerd Hoffmann
2007-04-24 17:27 ` Andrew Morton
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=20070329163714.GA29059@suse.de \
--to=od@suse.de \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=benh@kernel.crashing.org \
--cc=ink@jurassic.park.msu.ru \
--cc=jeremy@goop.org \
--cc=john@stoffel.org \
--cc=kraxel@suse.de \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=ralf@linux-mips.org \
--cc=rth@twiddle.net \
/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.