RHEL5 IPMI+Console bootup messages
Lamont Granquist
lamont at scriptkiddie.org
Tue Nov 6 12:53:08 CST 2007
So, i've got it so that nearly everything is going to both IPMI SOL and
console (PXE menu, grub menu, kernel boot and getty), but I can't get the
stupid redhat [ OK ]'s to go to both the serial port and the VGA console.
My /etc/inittab has:
co:2345:respawn:/sbin/agetty -h -t 60 ttyS1 57600,9600 vt100
My grub.conf looks like:
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You do not have a /boot partition. This means that
# all kernel and initrd paths are relative to /, eg.
# root (hd0,0)
# kernel /boot/vmlinuz-version ro root=/dev/sda1
# initrd /boot/initrd-version.img
#boot=/dev/sda
default=0
# serial argument added by cfengine for IPMI support
serial --unit=1 --speed=57600
# terminal argument added by cfengine for IPMI support
terminal --timeout=5 console serial
timeout=5
# splashimage=(hd0,0)/boot/grub/splash.xpm.gz
# hiddenmenu
title Red Hat Enterprise Linux Server (2.6.18-8.1.8.el5)
root (hd0,0)
kernel /boot/vmlinuz-2.6.18-8.1.8.el5 ro root=LABEL=/ console=ttyS1,57600n8 console=tty0
initrd /boot/initrd-2.6.18-8.1.8.el5.img
title Red Hat Enterprise Linux Server (2.6.18-8.el5)
root (hd0,0)
kernel /boot/vmlinuz-2.6.18-8.el5 ro root=LABEL=/ console=ttyS1,57600n8 console=tty0
initrd /boot/initrd-2.6.18-8.el5.img
Whichever console= argument to the kernel comes last is the one that the
redhat initscripts send the [ OK ] messages to, so in this case the
targets are favoring the VGA console and nothing will show up in between
the kernel boot messages and the login prompt over IPMI.
I can work around this just by including different targets so that if
someone is connecting via ipmi and needs to see the bootup messages they
can hit a different grub menu item, but ideally I'd just like to see the
messages sent to both terminals. I've surfed google pretty extensively
and can't seem to find the answer, is there anyone on this list who knows?
(oh it seems to affect PE1950s and PE1435s equally, I've been testing
mostly with RHEL5/x86_64... not sure if its exclusive to those
configs...)
More information about the Linux-PowerEdge
mailing list