Red Hat Bugzilla – Bug 426319
after RHEL5 install on QS22, no console on SOL
Last modified: 2007-12-19 20:49:03 EST
Description of problem:
I installed RHEL5u2 nightly build on a QS22 system (ibm-qs22-01 in
redhat westford lab). The install was problem free, but on reboot, I
thought the sytem had hung. This was because the system was configured
to boot with 'console=hvc0'. The system was booting fine (and was
network-reachable afterwards). I just couldn't see the console
How reproducible: 100%
Steps to Reproduce:
1. Install RHEL5u2 (likely RHEL5u1 GA works also) on QS22
No console messages on the SOL provided by the bladecenter.
console messages should go to the SOL provided by the bladecenter.
This problem is fixed simply by removing 'console=hvc0' from the
append line of yaboot.conf after successfully booting.
I assumed that it was anaconda that decided to add these kernel
parameters (I could be wrong).
I can provide access to the system for debugging if needed.
I just realized that the kickstart file that I had used contained:
bootloader --location=partition --append="console=hvc0 rhgb quiet"
This would quite obviously cause there to be 'console=hvc0' on the kernel
command line. Sorry for this bad bug report.
I wonder, if I do not specify any --append argument in a kickstart file, will
anaconda select the correct values ? (I just copied that line from somewhere).