Red Hat Bugzilla – Bug 9851
Bad monitor detection
Last modified: 2008-05-01 11:37:54 EDT
My Mag DJ717 ended up with a X-configuration like this i a fresh install:
During the install(GUI), I had chosen to configure X and chosen 1152x864.
The alternatives (up to 1600x1200, which my monitor is supposedly able to
handle at a not to great frequency) seemed resonable, so I believe it had
OK data then. Also, a test did work.
Send me the a copy of your XF86Config file, please.
Created attachment 136 [details]
The bad XF86Config file
We updated the entire monitor database just after releasing the public beta, so
this issue will be resolved in the final release. The MAG DJ717 monitor will
now come up with a horizontal sync rate of 30-86 and a vertical of 50-160.
This is not fixed in the 6.1 98 snapshot released Saturday. I could choose
between a lot of resolution in the installer, but only 640x480 was available
when booting. I'll attach the produced XF86Config file to this bug
Created attachment 142 [details]
The new bad XF86Config file
I am not able to replicate this in the lab. I choose the Mag monitor, test out
a couple of resolutions, then finish the installation. On reboot, I have the
correct sync rates for the monitor.
When you select the Mag monitor in the monitor selection screen, are the correct
sync rates being displayed at the bottom of the screen (in the boxes)?
I don't see any frequencies (or ranges) at all when selecting the DDC-probed
I can also add that the same thing happens on another computer, a LG Studioworks
55i on a completely different computer (Mach64, the other one has a Riva TNT
I understand now. Will have to try to get a DDC-probed monitor to come up
without frequency settings.
*** This bug has been marked as a duplicate of 8615 ***