Bug 84775 - Phoebe 3: graphic installer refreshrate to high for TFT with GeForce4
Summary: Phoebe 3: graphic installer refreshrate to high for TFT with GeForce4
Status: CLOSED DUPLICATE of bug 88360
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: XFree86
Version: phoebe
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Mike A. Harris
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2003-02-21 08:36 UTC by Gino Rossen
Modified: 2007-04-18 16:51 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2006-02-21 18:51:55 UTC

Attachments (Terms of Use)

Description Gino Rossen 2003-02-21 08:36:29 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210

Description of problem:
During installation my graphic card and monitor are detected (Nvidia Geforce4 -
HP L1720 TFT), but when the installer enters the graphic mode my TFT goes blank
with the warning "Refreshrate to high".
The TFT screen is connected on the DVI output of my GeForce4.
I've also started the setup with linux noddc and linux lowres.  Same result: my
TFT goes blank with the warning "Refreshrate to high".

Workaround: I started the installer in text mode.  After the installation I
edited the /etc/X11/XF86Config file and replaced the nv driver with the vesa driver.

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

How reproducible:

Steps to Reproduce:
1. Start installation
2. choose normal installation, linux noddc or linux lowres
3. monitor and graphic card get correctly detected

Actual Results:  installer enters graphical mode -> monitor goes blank 

Expected Results:  The nv driver should have detected the TFT and set the
refreshrate between 60 and 75 Hz

Additional info:

Creative Geforce 4 Ti 4400
HP L1720 TFT panel DVI

Comment 1 Mike A. Harris 2003-02-21 20:21:15 UTC
We do not have access to Nvidia's proprietary hardware specifications,
and are unable to work on this driver directly.  Please report your problem
to xfree86@xfree86.org and the "nv" driver maintainer should see the bug
report, and propose a solution.

Closing bug as defered to the upstream driver maintainer. (UPSTREAM)

Comment 2 Mike A. Harris 2003-07-17 10:21:44 UTC
I'm processing UPSTREAM flagged bug reports for upstream fixes currently, and
noticed that this bug was flagged upstream but has no upstream bug URL, and I
was unable to find an upstream bug report of this issue in XFree86 bugzilla
located at:


Closing bug report as WONTFIX as I'm unable to track upstream until a bug
report has been filed upstream, and the URL provided for tracking.  If this
issue is still relevant in the latest XFree86 packages in rawhide, after
reporting upstream at http://bugs.xfree86.org, feel free to add the bug
report URL to this report and reopen if you'd like the issue to be tracked
and any fixes from upstream investigated for inclusion in future Red Hat
XFree86 updates.

Comment 3 Mike A. Harris 2003-09-27 01:00:13 UTC

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

Comment 4 Red Hat Bugzilla 2006-02-21 18:51:55 UTC
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.