From owner-freebsd-current  Sun Aug  3 00:13:54 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id AAA10021
          for current-outgoing; Sun, 3 Aug 1997 00:13:54 -0700 (PDT)
Received: from dfw-ix3.ix.netcom.com (dfw-ix3.ix.netcom.com [206.214.98.3])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA10016
          for <current@FreeBSD.ORG>; Sun, 3 Aug 1997 00:13:52 -0700 (PDT)
Received: (from smap@localhost)
          by dfw-ix3.ix.netcom.com (8.8.4/8.8.4)
	  id CAA21570; Sun, 3 Aug 1997 02:12:49 -0500 (CDT)
Received: from scz-ca17-04.ix.netcom.com(205.184.191.132) by dfw-ix3.ix.netcom.com via smap (V1.3)
	id sma021566; Sun Aug  3 02:12:35 1997
Message-ID: <33E42F5E.41C67EA6@ix.netcom.com>
Date: Sun, 03 Aug 1997 00:12:30 -0700
From: Sherwin <sherwink@ix.netcom.com>
X-Mailer: Mozilla 3.01Gold (X11; U; FreeBSD 2.2.2-RELEASE i386)
MIME-Version: 1.0
To: Barry Masterson <jbarrm@panix.com>
CC: current@FreeBSD.ORG
Subject: Re: XFree86-3.3, FBSD-2.2.2 & ViRGE/VX
References: <Pine.SUN.3.94.970803012304.18904A-100000@panix.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

I am having a similar problem. See Problem Report bin/4189. It appears
to be related to my use of ppp on a modem on cuaa3. I am running 2.2.2
off the CDROM, with the XFree86-3.3 and the SVGA server, with a Matrox
Millenium. If user ppp is not running, I can restart X as many times as
I like. With user ppp running, I get the freeze immediately after the
carriage-return is echoed. I have yet to figure out why or how to fix
it. Anyone have an idea?

Barry Masterson wrote:
> 
> 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.
> 
> I'm running FreeBSD 2.2.2-R on a ASUS P55T2P4, with a Adaptec
> 2940AU. THe graphics card is a #9 9FX Reality 772 (ViRGE/VX).
> 
> I built XFree86-3.3 (from the source code) because it offers
> better support for the ViRGE/VX chipset.
> 
> 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
> something from the FreeBSD-current source?  Or, I should ask,
> is there something about 2.2.2-R that might cause the situation
> described below.
> 
> 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).
> 
> The author of XF86_S3V & XF86_SVGA is aware of this problem. They
> supplied me with the patches to fix it, but after applying them,
> and rebuilding, the 'no second restart' problem is still present.
> (The XF86_SVGA author can't reproduce the lockup on the patched
> 3.3.1 server)
> 
> Luckily, the XF86_S3V server is ok. However, I've been told
> that the SVGA server is better, and that S3V will at some point
> be phased out.
> 
> In an attempt to cover the bases, I thought I should ask this list
> if FreeBSD 2.2.2-R needs anything from the -current source tree to
> make the 3.3 or the 3.3.1 patched XF86_SVGA server happy.
> 
> Please cc, not currently on -current.
> 
> Thank you for listening.
> 
> Barry Masterson
> jbarrm@panix.com
> 
> >--->--->--->--->--->
>   FreeBSD   2.2.2-R
> <---<---<---<---<---<