test3: CD1 boots and system-config-display bug ? + workaround

[Phil Schaffner]

On Mon, 2004-04-26 at 14:42, Taylor, ForrestX wrote:
> On Mon, 2004-04-26 at 09:49, Hannes Mayer wrote:
> > Hi all!
> > 
> > After installing FC2test3 today (yes, CD1 booted just fine :-) I experienced
> > screen-resolution problems. I had no problems getting 1024x768 on test2, but
> > the usual procedure failed on test3.
> > 
> > After the installation was complete, I rebooted and the X-config came
> > up. I selected 1024x768, but GNOME came up with 800x600.
> > No chance to get it working with 1024x768 (even selected a default monitor
> > and edited xorg.conf)
> > 
> > # system-config-display
> > * ddcprobe returned bogus values:
> > ID: SNIcc0b
> > Name: SNIcc0b
> > HorizSync: None
> > VertSync: None
> > 
> > Trying with card: ATI Mach64VT (264VT)
> > -------
> > 
> > Then I saw that the line for HorizSync and VertRefresh are commented in
> > xorg.conf. I uncommented them and then it came up with 1024x768.
> > 
> > I think this is a bug in system-config-display ? bugzilla ?
> 
> I had the same problem when I updated to the latest rawhide.  It is
> definitely worth a bugzilla, because a lot of people here have their
> machines on a switch box, so it cannot probe the ddc values properly. 
> Let me know the bug # so I can add my comments.

Does not seem to be related to using a KVM switch.  Had similar problems
with directly connected KVM.  The initial problem seems to be that the X
configuration in firstboot  writes /etc/X11/XF86Config whereas xorg
reads the default /etc/X11/xorg.conf.  Copying (or perhaps better moving
- to avoid future confusion) /etc/X11/XF86Config to /etc/X11/xorg.conf
will give the setup you supplied originally.

The system-config-display bug seems to be a different problem.

Phil