I'm using the latest 5.9.7 release (3.1?) from gribble.
Xconfigurator fails to start the X server after the video
card, monitor, and default resolution/color depth are
selected. I have this problem with both an ATI Rage Pro
(AGP) board and Matrox Millenium board. In addition, the
default color depth and resolution are no longer auto-probed
for the Matrox (this used to work fine in 5.2 and before).
Did 6.0 final clear this up?
------- Email Received From "Chris Runge" <firstname.lastname@example.org> 06/05/99 06:37 -------
It works for me, but maybe preston has a clue.
There are problems probing for the amount of memory on many
milleniums, so the card has been "blacklisted" for probing until a
better solution can be found. This is why it doesn't determine which
resolutions are available-- it doesn't know how much ram is on the
Xconfigurator will be receiving a complete overhaul for the next
release, and this will be addressed.
*** Bug 3211 has been marked as a duplicate of this bug. ***
The latest version of Xconfigurator is unable to correctly
probe my Matrox Millenium II PCI (8MB) video card. The card
is identified properly, but probing for possible resolutions
and color depths fails. I'm forced to enter information
manually. Xconfigurator worked properly with this card with
RH5.2. Video performance seems to be diminished with this
version of Xconfigurator.