From owner-freebsd-questions Thu Aug 1 09:23:19 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA23232 for questions-outgoing; Thu, 1 Aug 1996 09:23:19 -0700 (PDT) Received: from filitov.isf.rl.af.mil (FILITOV.ISF.RL.AF.MIL [128.132.64.25]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA23220 for ; Thu, 1 Aug 1996 09:22:46 -0700 (PDT) Received: (from green@localhost) by filitov.isf.rl.af.mil (8.7.3/8.7.3) id MAA24184; Thu, 1 Aug 1996 12:21:50 -0400 (EDT) Message-Id: <199608011621.MAA24184@filitov.isf.rl.af.mil> From: green@filitov.isf.rl.af.mil (Charles Green) Date: Thu, 1 Aug 1996 12:21:50 +1000 In-Reply-To: Tim Vanderhoek "Re: FreeBSD and Mach 64" (Aug 1, 11:53) X-Mailer: Mail User's Shell (7.2.4 2/2/92) To: Tim Vanderhoek Subject: Re: FreeBSD and Mach 64 Cc: questions@freebsd.org Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Tim Vanderhoek stands accused of saying: } Date: Aug 1, 11:53 } Subject: Re: FreeBSD and Mach 64 } On Thu, 1 Aug 1996, Charles Kenneth Green - PRC wrote: } } [cc: list trimmed] } } > Has there been a fix for the sio.c bug that fouls up Mach 64 } > cards. I have a FreeBSD 2.1 system that I had to replace the video card } > in. The card I ended up getting uses a Mach 64 chip and I'd prefer not to } > have to send it back. } } Sort of. The sio driver no longer probes com3 (or whichever one it was) } by default. The only bug that really existed was that the sio driver } probed every comport even if it was only supposed to check one. } } I'm using a Mach64 here, and it works great (although you may need to get } a beta X server from the ftp.xfree86.org if it uses one of those `CT' or } `VT' (I think it's `VT' -- don't quote me) chips). } That would be exceptable, I already have the Beta-E, I needed it for a diamond card I'm using on another system. } } -- } Outnumbered? Maybe. Outspoken? Never! } tIM...HOEk } }-- End of excerpt from Tim Vanderhoek -- Charles Green, PRC, Inc. Rome Laboratory, NY