From owner-freebsd-current  Sat Aug  2 23:38:08 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id XAA08145
          for current-outgoing; Sat, 2 Aug 1997 23:38:08 -0700 (PDT)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA08139
          for <current@FreeBSD.ORG>; Sat, 2 Aug 1997 23:38:05 -0700 (PDT)
Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.6/8.6.9) with ESMTP id XAA00692; Sat, 2 Aug 1997 23:37:42 -0700 (PDT)
To: Barry Masterson <jbarrm@panix.com>
cc: FreeBSD-current <current@FreeBSD.ORG>
Subject: Re: XFree86-3.3, FBSD-2.2.2 & ViRGE/VX 
In-reply-to: Your message of "Sun, 03 Aug 1997 01:50:41 EDT."
             <Pine.SUN.3.94.970803012304.18904A-100000@panix.com> 
Date: Sat, 02 Aug 1997 23:37:42 -0700
Message-ID: <688.870590262@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> I seem to remember reading on the -questions mailing list that
> XFree86-3.3 was not fully supported on the FreeBSD 2.2.2-R
> system. 

It's not the default XFree86 for it, but it's more than usable with
2.2.2.  I don't know who told you it wasn't supported.

> My question is, Is there anything specific to FreeBSD 2.2.2-R
> that needs to be changed to best run XFree86-3.3; such as

Nope.

> The reason I'm asking, is that while 3.3 runs fine on this system,
> the XF86_SVGA server fails to restart after the first 'startx'
> session is closed on a freshly booted system. (running startx
> a second time results on a frozen keyboard and a blank screen).

That's weird - I can't say that I've seen this happen with my own
XF86_SVGA server (running 2.2-stable).

					Jordan