Bug 109487 - Blank screen when using DVI output on GeForce FX 5200 card
Blank screen when using DVI output on GeForce FX 5200 card
Status: CLOSED DUPLICATE of bug 88360
Product: Fedora
Classification: Fedora
Component: XFree86 (Show other bugs)
1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Mike A. Harris
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-11-08 08:29 EST by Steven Moix
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 13:59:51 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Steven Moix 2003-11-08 08:29:41 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET 
CLR 1.0.3705; .NET CLR 1.1.4322)

Description of problem:
Noticed a strange bug on my computer with an ASUS V9520/TD (GeforceFX 
5200 chip) graphic card when starting the Fedora Core 1 installation. 
When I use the VGA output, there is no problem, but when I use the 
DVI output, I get a blank screen when the graphical installation is 
started. I have an Eizo L565 17" TFT screen.

There is no "out of scan range" on the screen when switching to the 
bank screen so it isn't the screen. When I switch to console with 
Alt+F3 I see thet the system is still active (you can go further in 
the installation process by typing "F12" on the blank screen.

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


How reproducible:
Always

Steps to Reproduce:
1. Connect your graphic card on DVI output
2. Boot Fedora Core 1 installation in graphical mode 
3. Wait and you will get a blank screen after hardware probe
    

Additional info:
Comment 1 Jeremy Katz 2003-11-10 16:20:51 EST

*** This bug has been marked as a duplicate of 88360 ***
Comment 2 Red Hat Bugzilla 2006-02-21 13:59:51 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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