From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.4.1)
Description of problem:
On installing rh80 using a serial line terminal as console anaconda installs
grub with a sytax error in the grub configuration screen.
In order to define the serial line to grub there is a line:
serial --unit=0 --speed=96
This should be
serial --unit=0 --speed=9600
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Indstall rh80 useing serial console
2. after reboot you don't see grub on the serial console.
3. you see the kernel messages on the console
4. vi /etc/grub.cfg and change the "serial"-line
5. reboot and you see grub on the serial console.
Expected Results: grub should be seen and on the serial console and you should
be able to use grub on the serial console.
Did you boot the installer with any command line arguments? We read the
arguments directly from what is passed for use during installation
In order to boot a headless system I use the following modified syslinux.cfg on
a bootnet.img floppy:
append initrd=initrd.img lang= text devfs=nomount ramdisk_size=9216
append ks=floppy initrd=initrd.img lang= devfs=nomount ramdisk_size=9216
You say that you read the arguments directly from what is passed for use during
installation. You can do that if you install the lilo bootloader, because it
uses the same syntax for serial line definition as the linux kernel does.
Grub on the other hand uses a different syntax. The baudrate is the example:
The linux boot argument uses "96" for baudrate 9600, whereas GRUB uses "9600" to
set the baudrate to 9600 baud.
No, the correct kernel syntax is
which then gets transformed properly into grub syntax.
OK ttyS0,9600n8 might be the good syntax, but ttyS0,96n8 is also a good syntax
for the kernel but this syntax is NOT good for grub. Practice has proven this
point to be true.
And that was the essence of my bug report.
Further it is up to you as what you do with this info.