Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 03 Nov 2006 13:27:58 -0500
From:      "Brian A. Seklecki" <bseklecki@collaborativefusion.com>
To:        Matt Domsch <Matt_Domsch@dell.com>
Cc:        eclark <eclark@alabanza.com>, linux-poweredge@dell.com
Subject:   Re: Console Redirection After Boot
Message-ID:  <1162578478.26675.273.camel@soundwave.pgh.priv.collaborativefusion.com>
In-Reply-To: <20061101150834.GD22833@lists.us.dell.com>
References:  <1162357012.4169.378.camel@compulsion> <4ffdf1bc0611010239sb23ee60xf012b9d39865ca7b@mail.gmail.com> <EFBEA069-F2AD-4AA6-B50C-5B6A4F67A9B7@uni.edu> <200611010937.02310.eclark@alabanza.com> <20061101150834.GD22833@lists.us.dell.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 2006-11-01 at 09:08 -0600, Matt Domsch wrote:
> On Wed, Nov 01, 2006 at 10:37:01AM -0400, eclark wrote:
> > there any way to force serial console redirection in the kernel, so I can log 
> > boot sequences? It gets a bit old having to continuously reboot to stare at 
> > scrolling messages when you are trying to do kernel testing.
> 

Just for the record, I just tested:

- An Intel Server Motherboard SE7520*
- A Dell PE2950
- An Axiomtek SBC83672

All have Phoenix BIOS.  All exhibit the same behavior.  I/O to the
console does not get redirected to serial _unless_ it was sent there via
a BIOS call.  Ah la, DOS.

The only options are:

- Write a framebuffer driver for the kernel that uses BIOS calls (_not
  likely_, and for which there would most presumably be no terminal
  disciplines capable of running sysint/sysinstall)

- Convince hardware vendors like Dell/Intel to implement a more Real
  Weasel-like console redirection system (not likely)

- Convince Dell not to re-write the ActiveX applet that is the DRAC5
  interface in something slight more portable, such as...oh, Java.

- During emergency scenarios like DRP deployment, have a Windows system
  around.

- Buy an OpenBoot enabled platform. =p J/K

#3 seems most logical.  Well at least now I understand the problem in
its entirely.  Thanks all.

~BAS

> That's easy.
> 
> 1) Disable (or really, don't enable) console redirection in BIOS SETUP.
> 2) Put on the kernel command line:  console=ttyS0,115200 console=tty0
> 
> We do 99% of our kernel debugging this way.
> 
-- 
Brian A. Seklecki <bseklecki@collaborativefusion.com>
Collaborative Fusion, Inc.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1162578478.26675.273.camel>