Re: mu [X11bug]

From: Michele Andreoli (
Date: Thu Dec 09 1999 - 20:22:11 CET

On Thu, Dec 09, 1999 at 11:25:18AM -0200, Renato nicely wrote:

> I can guarantee that mulinux was able to configure X11 in my computer
>from 6r4 to 7r3b (without any configuration file change).

>Now it seems it doesn't find a suitable mode anymore.
> (--) VGA16: Maximum allowed dot-clock: 80.000 MHz
> (--) VGA16: There is no defined dot-clock matching mode "640x480"
> (--) VGA16: Removing mode "640x480" from list of valid modes.
> (--) VGA16: There is no mode definition named "800x600"

I checked, with the Linux "diff" command, the two file,
in 6r4 and 7.x. They are *identical*. We know the bug relative to
missing symlink for release < 7r4. I'm not sure if I fix the symlink
bug in 7r4 o 7r5.

Please, try to figure out the origin of your malfunction. Go in
/usr/X11R6/lib/X11 and do a "ls -l". You can see the file:

                XF86Config -> /etc/X11/XF86Config ?

Go in /etc/X11. You can see the *active* file XF86Config. If yes,
the symlink bug is fixed in your muLinux.

In this case, I cannot understand why X do not work for you!

I see, you have a big clock 80K. Localte in the two rows:

     HorizSync 31.5
     VertRefresh 50-70
and try to enlarge this value: e.g.:

                HorizSync 30-50
                VertRefresh 50-100

News modes will becomes active.

Maybe, in the future, I can parametrize this values, but they are
two hardware-depend and, also, a little dangerous.


I'd like to conclude with a positive statement, but I can't 
remember any. Would two negative ones do?       -- Woody Allen
To unsubscribe, e-mail:
For additional commands, e-mail:

This archive was generated by hypermail 2.1.6 : Sat Feb 08 2003 - 15:27:12 CET