In addition to these comments, I would add the following possibilities:
There are actually two different servers for S3 (Virge &
otherwise) with my version of X. Watch that .
Another possibility is that there is a XF86Config problem. I
note you hacked the XF86Config. I got that error by giving a line of
fixed clocks. On startup, if the fixed clocks don't work out for the
available modes/refresh rates, X will delete them. I ended up with
no modes that actually worked out! The S3 cards should have a max dac
speed, not a line of dot clocks
Previous message
.................snip....................
>
> > _X11TransSocketUNIXConnect: Can't connect: errno = 111
>
> > This last message is issued repeatedly.
> > I appreciate that this message in itself says little about the
> > problem, but as this is occuring at startup there are no other
> > messages to help explain.
>
> > However, I reasoned that the first client to try to connect to
> > the server would probably be xdm, and, sure enough, in the
> > xdm-errors file I found:
>
> > xdm error (pid xxx): server open failed for :0, giving up
> > xdm error (pid yyy): Display :0 cannot be opened
> > xdm error (pid yyy): Display :0 is being disabled
>
> > I checked the xdm/Xservers file and it's identical to the
> > equivalent file in my previous working X installation, namely:
>
> > :0 local /usr/X11R6/bin/X
>
>Obvious check: what does `ls -ld /usr/X11R6/bin/X` display? It should
>show a SymLink to the relevant server driver, but it sounds as if it's
>missing, based on the above message...
>
>
>
> > Before I try a re-install, or simply revert to my old
> > installation, could anyone suggest why the server may fail to
> > start up in this way, and how this problem may be resolved?
>
>If the above is correct, then do the following:
>
> Q> cd /usr/X11R6/bin
> Q> ln -s XF86_SVGA X
>
>It should start working after you've done that...
>
--
Regards
(now at [EMAIL PROTECTED])
Declan Moriart
