Bug 121064

Summary:	NVS280 text mode install and X will not start
Product:	Red Hat Enterprise Linux 3	Reporter:	Kim Jensen <kim_jensen>
Component:	anaconda	Assignee:	Jeremy Katz <katzj>
Status:	CLOSED RAWHIDE	QA Contact:	Mike McLean <mikem>
Severity:	high	Docs Contact:
Priority:	medium
Version:	3.0
Target Milestone:	---
Target Release:	---
Hardware:	ia32e
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2004-04-19 20:20:54 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Kim Jensen 2004-04-16 17:18:55 UTC

Description of problem:
When installing RHEL3U2B WS x86_64 on a ia32e box, the install is in 
text mode and once the install completes, X will not start because 
there is no XF86Config file.

On the flip side - when installing RHEL3U2B WS IA32 on the same HW, 
the install is graphical and X starts fine.

The graphics is PCI NVIdia NVS280

Version-Release number of selected component (if applicable):
kernel-2.4.21-12
anaconda-9.1.2-0.RHEL.20040330155035
XFree-4.3.0-62

How reproducible:
Everytime


Steps to Reproduce:
1a. Install RHEL3U2 Beta WS x86-64 w/ NVS280 on ia32e - it's always 
in text mode.
1b. X fails with 
Fatal server error:
no screens found

2a. Install RHEL3U2 Beta WS ia32 2/ NVS280 on x86_64 - it's always 
graphical.
2b. X succeeds 
  
Actual results:
NVS280 installs textually and X fails to start

Expected results:
NVS280 installs graphically and X starts

Additional info:

RHEL3U2Beta WS - IA32 and x86_64 behaved differently

Comment 1 Jeremy Katz 2004-04-16 18:00:26 UTC

Is there a comment about no video hardware found, assuming headless?

Comment 2 Kim Jensen 2004-04-19 19:41:23 UTC

Yes!
   No video hardware found, assuming headless?
   DISPLAY varaible not set.  Starting up text mode!

Comment 3 Jeremy Katz 2004-04-19 20:20:54 UTC

Okay, I have this fixed for the final U2 release then.

Comment 4 Kim Jensen 2004-05-12 16:08:36 UTC

Confirmed - it's fixed.  Thanks!