This could be considered a bug in either kickstart or grub, I'm not sure.
The hardware is a bit old, Intel P3 1GZ, aic7xxx scsi drives, bios is
PhoenixBIOS 4.0 Release 6 / STL2 1.7. It's set to redirect to the serial port.
After installing with kickstart, the grub/menu.lst contains:
serial --unit=1 --speed=19200
terminal --timeout=5 serial console
These cause grub to hang, with nothing on the serial console and "GRUB loading
stage2" on the vga console.
It would not be so bad if the %post script could overwrite the file with
something that works, however the bootloader is installed after the %post
script, so it's not really a %post script at all.
In the the stage2.img filesystem, I patched /usr/lib/booty/bootloaderInfo.py
--- bootloaderInfo.py.orig 2007-02-09 18:00:49.000000000 +0000
+++ bootloaderInfo.py 2007-02-09 16:25:18.000000000 +0000
@@ -689,8 +689,8 @@
# reasonable default
speed = "9600"
- f.write("serial --unit=%s --speed=%s\n" %(unit, speed))
- f.write("terminal --timeout=10 serial console\n")
+ #f.write("serial --unit=%s --speed=%s\n" %(unit, speed))
+ #f.write("terminal --timeout=10 serial console\n")
# we only want splashimage if they're not using a serial console
if os.access("%s/boot/grub/splash.xpm.gz" %(instRoot,), os.R_OK):
recompiled them to .pyc files, copied them to the other hd and net .img's
rebuilt the images with mkcramfs, then lo and behold grub prints its menu to
the serial console anyway, and proceeds to boot linux.
Always or never, see below.
1. Install using kickstart on a serial console.
2. Probably depends on our exact hardware so you probably wont be able to
This RHEL AS 3, no updates applied. I checked all the updates to grub I could
find, none mention anything about fixing serial console support. If later
versions of kickstart run the %post script at the *END* of the installation
then that would be an acceptable workaround.
I'm sorry I forgot, using LILO instead is an easier workaround...
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.