Bug 152306

Summary:	Installer hangs with a blank screen when starting X
Product:	[Fedora] Fedora	Reporter:	John Collector <john_collector>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED DUPLICATE	QA Contact:	Mike McLean <mikem>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-03-28 16:36:29 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 John Collector 2005-03-28 03:22:18 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2

Description of problem:
Anaconda fails to install a proper driver for PCI-Express ATI RADEON cards which results in a blank screen when trying to start graphical part of installation. This especially happens with X600, X600Pro, X700, X800 and X850 cards. The FC3 distro got the same problem, however FC2 i386 is able to install at least the VESA driver resulting in a successful start of X. 

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


How reproducible:
Always

Steps to Reproduce:
1. No special steps are needed, just boot-up the installation CD (DVD)
2. Press Enter to choose a standard installation
3. Wait until anaconda starts to detect your video, monitor and mouse
  

Actual Results:  Blank screen as soon as anaconda starts X.

Expected Results:  The X should start so the graphical part of installation can continue

Additional info:

AMD Athlon 64 3200+
ASUS A8V-E Deluxe with 1004 BIOS
Seagate SATA 200 Gb
Gigabyte ATI Radeon X600Pro
LCD Mitsubishi DV172 (Detected correctly as MEA 172 with FC2 i386,
not detected at all with FC3 x86_64 and FC4test1 x86_64)

Comment 1 Chris Lumens 2005-03-28 16:36:29 UTC


*** This bug has been marked as a duplicate of 151768 ***