Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 13 Sep 1997 20:11:55 -0400
From:      Randall Hopper <rhh@ct.picker.com>
To:        stephane@lituus.fr, Doug White <dwhite@gdi.uoregon.edu>
Cc:        freebsd-questions@FreeBSD.ORG
Subject:   Re: Problem with second start of XFree86 3.3
Message-ID:  <19970913201155.31384@ct.picker.com>
In-Reply-To: <199709120200.EAA00200@sequoia.hol.fr>; from stephane@lituus.fr on Fri, Sep 12, 1997 at 03:59:58AM %2B0200
References:  <199709120200.EAA00200@sequoia.hol.fr>

next in thread | previous in thread | raw e-mail | index | archive | help
stephane@lituus.fr:
 |I have compiled and installed XFree86 3.3 (2nd June 1997 release) on a
 |FreeBSD 2.2.1 (cdrom release). I use the SVGA server with a STB
 |Velocity 3D (S3 Virge/VX - 4 Mo Ram).

Great card!  I have one too. :-)

 |The first time i launch "startx", everything is fine. XFree has no
 |problem at all.  But, if i quit and restart "startx", i get a black
 |screen and all i can do is to reboot the computer with the reset button!!
 |
 |Does somebody have any clue to solve this problem ? Could it be a
 |configuration problem during the compilation of XFree ? Or a SVGA
 |server bug ?

Yes, this bug has been widely reported on the c.s.i.pc.h.video and *linux.x
newsgroups, and the FreeBSD lists.  All posts have in common users running
XFree 3.3 or 3.3.1 on a Virge/VX-based cards (Diamond Stealth 3D 3000 or
STB Velocity 3D) with the SVGA server.  This problem doesn't happen with
original-Virge-based cards (e.g. Diamond Stealth 3D 2000).  

For Virge/VX users, this problem doesn't exist in the S3V server, so you
can switch to using that and get rid of the problem.

In probing for details for the bug report I refiled on XFree 3.3.1's SVGA
server regarding this problem, it appears likely that the Virge/VX init
code in the SVGA server isn't fully initializing (or deinitializing) the
Virge/VX like the S3V server does.  Seems likely because the 2nd-time
startup freeze "doesn't" occur if you start up the S3V server "first" and
bring it down before starting the SVGA server.  You can then start/stop the
SVGA server all you want.  'course this isn't practical usage; just an
interesting note on the problem.

I've got a few other bugs filed on the SVGA Virge functionality.  It's
still a bit beta-ish as of 3.3.1, so I stick with the S3V server for now.
I'm looking forward though to the increased performance we'll get from the
SVGA server when it stabilizes.  The S3V server is very fast, but hey, I'll
take "faster" any day :-)

Randall Hopper



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970913201155.31384>