From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830
Description of problem:
after moving a hard drive from one dell inspiron system to another,
redhat-config-xfree86 failed to correctly determine my hardware, and therefore
couldn't configure my system to start x.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Change system monitor or video card
2. Run redhat-config-xfree86
Actual Results: redhat-config-xfree86 exited without provisionally starting x,
and therefore without allowing me to change settings to get a working x
Expected Results: i should've been able to configure x
video card: ati rage 128 mobility; driver: r128
display: dell inspiron 1400x1050, 24 bit color
What did redhat-config-xfree86 print out on the command line, and please attach
the log (/var/log/XFree86.setup.log) to this bug.
Created attachment 85024 [details]
/var/log/XFree86.setup.log from the failed run
turns out it's 100% reproducible. all i had to do was move /etc/X11/XF86Config
to a different filename, quit x, and run the config program.
command line output:
[root@georgia root]# redhat-config-xfree86
*ddcprobe returned bogus values:
Couldn't start X server, trying with a fresh configuration
Error, cannot start X server.
Strange. It doesn't find any modes. Since the DCC probe failed is should have
falled back to a SVGA monitor spec.
mharris: Exactly what does:
(EE) R128(0): No valid modes found
(EE) Screen(s) found, but none have a usable configuration.
I observe the same repeatable ddcprobe failure from ..config-xfree86 on my NEC
Multisync FP950 resulting in a fallback to 800x600, however:
A run of 'XFree86 -configure' correctly probes the monitor and produces a
correct /root/XF86config file up to the maximum supported resolution of the
Can you try with RHL 9 and see if the problem still exists?
Hmm, well, please reopen this bug is you can reproduce with RHL 9 or with the
Severn beta. The r128 driver works fine for me with those two releses.
I'll upgrade at some point, and report back then. Thanks for following up.