Date: Thu, 5 Mar 1998 04:31:42 -0500 (EST) From: Charlie ROOT <root@danberlin.resnet.rochester.edu> 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: <Pine.BSF.3.96.980305043036.191A-100000@danberlin.resnet.rochester.edu> In-Reply-To: <199803050927.TAA15964@troll.dtir.qld.gov.au>
next in thread | previous in thread | raw e-mail | index | archive | help
What version of Xfree86 is this, They fixed a TON of S3 bugs in the 3.3.2 release which was out about 2 days ago. for some strange reason the perms are set wrong on the 3.3.2 dir at ftp.xfree86.org, so i got them from ftp.kernel.org/pub/mirrors/xfree86 --Dan On Thu, 5 Mar 1998, Stephen McKay wrote: > On Thursday, 5th March 1998, Nate Williams wrote: > > >> > 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? (I missed the bit where you detailed > your hardware configuration.) If it is a Matrox and there is a special > "go easy on the PCI bus" flag in some deeply buried register, it could > have been missed by the XFree86 people but correctly set by XiG. > > 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. > > Stephen. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > 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?Pine.BSF.3.96.980305043036.191A-100000>