Bug 426319 - after RHEL5 install on QS22, no console on SOL
Summary: after RHEL5 install on QS22, no console on SOL
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: anaconda
Version: 5.1
Hardware: other
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-12-20 00:36 UTC by Scott Moser
Modified: 2007-12-20 01:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-12-20 01:49:03 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Scott Moser 2007-12-20 00:36:58 UTC
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
messages.

How reproducible: 100%
Steps to Reproduce:
1. Install RHEL5u2 (likely RHEL5u1 GA works also) on QS22
2. Reboot
  
Actual results:
  No console messages on the SOL provided by the bladecenter.


Expected results:
  console messages should go to the SOL provided by the bladecenter.

Additional info:
  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.

Comment 1 Scott Moser 2007-12-20 01:49:03 UTC
Doh!
  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).



Note You need to log in before you can comment on or make changes to this bug.