Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 111408 - Install fails with Nvidia Gforce 4
Install fails with Nvidia Gforce 4
Status: CLOSED DUPLICATE of bug 88360
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2003-12-03 05:22 EST by Hansjürg Wenger
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:
Last Closed: 2006-02-21 14:00:15 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Hansjürg Wenger 2003-12-03 05:22:08 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5)
Gecko/20031007 Firebird/0.7

Description of problem:
We are trying to install Fedora Core 1 on some PC's with Nvidia Gforce
4 Cards that have two Connectors, a DVI and a VGA.
The Monitor is connected to the DVI Port. When the X-Server is started,
we get a blank screen and are unable to continue the installation.
We think that the generic Nvidia Driver (nv) uses the wrong output
connector (VGA).
When we use the text mode for the installation, the problem reoccures
when we start Linux the first time (firstboot)
Is there a possibility to force the use of the DVI Interface or to use
another driver.

(Same Problem occures witch RH ES 3.0 and RH WS 3.0)

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

How reproducible:

Steps to Reproduce:
See description

Additional info:
Comment 1 Jeremy Katz 2003-12-03 14:31:14 EST

*** This bug has been marked as a duplicate of 88360 ***
Comment 2 Red Hat Bugzilla 2006-02-21 14:00:15 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.