Bug 208618 - anaconda cannot install via serial console
Summary: anaconda cannot install via serial console
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks: fedora-ia64 208801
TreeView+ depends on / blocked
 
Reported: 2006-09-29 18:27 UTC by Doug Chapman
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-10-02 15:09:30 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Doug Chapman 2006-09-29 18:27:04 UTC
Description of problem:
Booting the installer with a serial console anaconda is still starting the X
server and trying to run the X11 gui version.

I have tried this with no boot options and I have also tried passing "serial"
and "console=ttyS1" and it still runs X11.

This is on a system that has a video card however the system is configured to
use the serial console.  I have not yet tried this version of rawhide on a
system that has no video hardware.


Version-Release number of selected component (if applicable):
anaconda-11.1.0.102-1

How reproducible:
100%

Steps to Reproduce:
1. boot on an HP Integrity server that has video hardware but is configured for
serial console (nearly all HP ia64 servers in rhts)
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Doug Chapman 2006-09-29 18:29:11 UTC
More info... appears this is only happening for kickstart installs.


Comment 2 Doug Chapman 2006-10-01 20:00:58 UTC
I just tried this on x86_64 and I see the same issue so it is not ia64 specific.
 Note that this breaks kickstart installs that require some user interaction.



Comment 3 Jeremy Katz 2006-10-02 15:09:30 UTC
Chris fixed this on Friday, we just didn't build a package as we were trying not
to rock the boat with the FC6pre candidate that was being tested.


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