Bug 122608 - False display settings during first-boot
Summary: False display settings during first-boot
Status: CLOSED DUPLICATE of bug 120950
Alias: None
Product: Fedora
Classification: Fedora
Component: redhat-config-xfree86
Version: rawhide
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Brent Fox
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2004-05-06 08:42 UTC by Stefan Sonnenberg-Carstens
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2006-02-21 19:03:02 UTC
Type: ---

Attachments (Terms of Use)

Description Stefan Sonnenberg-Carstens 2004-05-06 08:42:20 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET 
CLR 1.1.4322)

Description of problem:
During the installation of Fedora-Core-2 T3 my graphics card
is correctly regocnised as a nVidia Ti4200, with dual-head
I chose a setting of 1280*1024 px as highest resolution.
First-Boot starts with these settings.
During First-Boot, the system attempted to configure the dual-
head display, but now showing only 800*600 px as a maximum resolution.

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

How reproducible:

Steps to Reproduce:
1.Install Fedora Core 2 T3 with nVidia Ti4200 DH Card
2.During First-Boot, problem occurs

Actual Results:  Wrong display settings. Harmless, but not disered 

Expected Results:  Right display capabilities.

Additional info:

Comment 1 Stefan Sonnenberg-Carstens 2004-05-06 09:29:40 UTC
Solution found.
When the system is installed,
the lines for hor. and vert. frequency of the monitor
are commented out, to enable DDC.
The monitor in use here, a ViewSonic PF775, doesn't seem
to like that.
I throw away the pounds before that lines, added
appropriate mode line, and it works.
Re-Enabling DDC causes the same effect as described earlier.

Comment 2 Miloslav Trmac 2004-05-07 15:39:57 UTC

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

Comment 3 Red Hat Bugzilla 2006-02-21 19:03:02 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.