From owner-freebsd-current Sun Aug 3 15:04:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA21145 for current-outgoing; Sun, 3 Aug 1997 15:04:34 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA21136 for ; Sun, 3 Aug 1997 15:04:27 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA02444; Sun, 3 Aug 1997 15:03:09 -0700 From: Terry Lambert Message-Id: <199708032203.PAA02444@phaeton.artisoft.com> Subject: Re: XFree86-3.3, FBSD-2.2.2 & ViRGE/VX To: bde@zeta.org.au (Bruce Evans) Date: Sun, 3 Aug 1997 15:03:09 -0700 (MST) Cc: jbarrm@panix.com, sherwink@ix.netcom.com, current@FreeBSD.ORG In-Reply-To: <199708030751.RAA07506@godzilla.zeta.org.au> from "Bruce Evans" at Aug 3, 97 05:51:30 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Some S3 boards uses the same i/o ports as sio3. You shouldn't use both > sio3 and X these boards. Some S3 boards crash at boot time when sio3 > is probed. You shouldn't configure sio3 if you have one of these boards > (even if you don't use X). S3 boards? Is this true? I know there was a problem with Mach32 and Mach64 boards incorrectly listening to I/O's on some ports before being put into a mode where listening was mandatory (it's a bug in the chipset). I didn't think S3 had the same problem... I run nothing but S3 cards, and I haven't seen the problem on any of my machines... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.