Date: Thu, 5 Mar 1998 10:07:09 -0700 From: Nate Williams <nate@mt.sri.com> To: Stephen McKay <syssgm@dtir.qld.gov.au> Cc: Nate Williams <nate@mt.sri.com>, freebsd-current@FreeBSD.ORG Subject: Re: silo overflows (Was Re: 3.0-RELEASE?) Message-ID: <199803051707.KAA18935@mt.sri.com> In-Reply-To: <199803050927.TAA15964@troll.dtir.qld.gov.au> References: <199803050530.WAA16531@mt.sri.com> <199803050927.TAA15964@troll.dtir.qld.gov.au>
next in thread | previous in thread | raw e-mail | index | archive | help
> >> > I can tell you that uniquivocally XFree86 causes this to happen. > >> > >> I am guessing it is something to do with the S3 chip. > > > >But I didn't change boards when I changed X servers. XFree86 caused > >them, XIG didn't. The hardware was exactly the same, the only > >difference was the Xserver. > > But do you have an S3 or a Matrox? Yes. :) The board at home which gets all the serial/modem traffic is an S3 board. The one at work is a Matrox. :) > And to stick up for S3, I use 801 ISA, 805 VLB and Trio64V+ PCI based > video in various machines and have seen no serial port interference from > any of them. But the borrowed Matrox caused silo overflow problems. The board that causes silo overflows due to Xfree86 is a 928 (old) board. But, it also had problems when it had an 801 board in it. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199803051707.KAA18935>