From owner-freebsd-current Tue Mar 5 15:40:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA07333 for current-outgoing; Tue, 5 Mar 1996 15:40:03 -0800 (PST) Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA07251 Tue, 5 Mar 1996 15:39:58 -0800 (PST) Message-Id: <199603052339.PAA07251@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: Host localhost.cdrom.com [127.0.0.1] didn't use HELO protocol To: Terry Lambert cc: imb@scgt.oz.au, stable@FreeBSD.org, current@FreeBSD.org Subject: Re: 2842 and the disappearing file-system :-( In-reply-to: Your message of "Tue, 05 Mar 1996 15:57:28 MST." <199603052257.PAA09308@phaeton.artisoft.com> Date: Tue, 05 Mar 1996 15:39:57 -0800 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.org Precedence: bulk >> >> Actually this appears to be a bug in eisaconf as it affects all >> >> eisa scsi controllers at the moment. I'm looking into it, but the >> >> problem is not obvious and doesn't occur in -current. >> > >> >He has a VESA controller... brain farts are contagious! >> >> He has a VESA controller that uses an EISA probe and so is >> also affected. > >Ah. That's broken. 8-(. This must be a VESA/EISA box for it to >see the EISA signature and hit the EISA code? The eisaconf code always probes for eisa ids if it is configured in your system. It hasn't caused any conflicts on any system that I've seen, and since we have at least one device driver that would have to copy the same probe code in order to work, I decied to make eisaconf work this way. > Terry Lambert > terry@lambert.org >--- >Any opinions in this posting are my own and not those of my present >or previous employers. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations ===========================================