Red Hat Bugzilla – Bug 12013
anaconda incorrectly creates XF86Config-4
Last modified: 2008-05-01 11:37:56 EDT
Using a Matrox Mystique. X Configuration, Custom config. Select only 16
bpp 1024x768 as the resolution to support after having the monitor and
video card correctly selected. /etc/X11/XF86Config-4 will then have a
screen section that does not allow X to start as there isn't a
configuration for 8bpp, and a DefaultColorDepth directive is not set inside
the Screen section. Fix should be similar to what is used to set
DefaultColorDepth in Version3Config()
I have seen this on multiple cards and install too, if you don't select any 8bpp
modes you get an invalid XF86Conifg, if DefaultColorDepth is omitted XF 40
doesn't user the first display section (as XF 33 does), but assumes
DefaultColorDepth is 8 if there is no 8 bpp section XF 40 exits with an error.
I'm pretty certain that XFree 3.3.6 mimics the behavior described above from
XFree4, as I've had multiple problems in the past due to not putting in the
default color depth line.
This behavior persists in beta2
although mentioned on testers-list, still bumping this up to beta3 as it
This defect is considered MUST-FIX for Winston Beta-5
Fixed in CVS, will be in beta4
*** Bug 12126 has been marked as a duplicate of this bug. ***
Resolution not a bug?!