public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Vilain <sam.vilain@catalyst.net.nz>
To: linux-kernel@vger.kernel.org
Subject: Serial console and the Sun X4100M2 ILOM
Date: Thu, 08 Nov 2007 10:30:00 +1300	[thread overview]
Message-ID: <47322E58.7000301@catalyst.net.nz> (raw)

Hi all,

We're using a PXE / network install system for the SunFire x4100M2.  We
had a kernel that worked fine for the x4100 and x2100/x2100M2, but this
new platform does something funny: after selecting the kernel at the
PXElinux prompt, I don't see any kernel messages on the serial console,
until the kernel has finished initialising.  They are appearing on the
VGA console, when I use console=tty0 console=ttyS0.  With console=ttyS0
only, they appear nowhere.

There is a BIOS setting called "Redirect" that has one option that looks
like a smoking gun: "Redirection After BIOS POST".  This has three settings:

  Disable: Turns off the redirection after POST
  Boot Loader: Redirection is active during POST and during Boot Loader.
  Always: Redirection is always active
  (Some OSs may not work if set to Always)

It seems that "always" is behaving just like "Boot Loader" says it
should - as soon as it would be saying "Loading kernel..." then I see no
messages at all.  Except perhaps a suprious character like "Á".

The "Boot Loader" option then works like "disable" - as soon as PXElinux
(or GRUB) loads, the console switches off and I see the "Á".

What's got me confounded is that it suddenly wiki comes right after root
gets mounted - be that an initrd image, or anything else.  What is it
that changes then, and how can I make that happen earlier?

I found the console.txt file, and it seems that while boot is in
progress the "system driver" is active vs the "modular driver".
However, I'm not sure why there is a change of driver at that point; I
didn't ask for it.

I'm coming to the conclusion that the serial console redirection in the
BIOS is broken somehow, anyone have any ideas on tracking this down further?
-- 
Sam Vilain, Chief Yak Shaver, Catalyst IT (NZ) Ltd.
phone: +64 4 499 2267        PGP ID: 0x66B25843

                 reply	other threads:[~2007-11-07 22:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=47322E58.7000301@catalyst.net.nz \
    --to=sam.vilain@catalyst.net.nz \
    --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