From owner-freebsd-questions Tue Apr 25 10:09:04 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA01464 for questions-outgoing; Tue, 25 Apr 1995 10:09:04 -0700 Received: from haven.uniserve.com (haven.uniserve.com [198.53.215.121]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA01431 for ; Tue, 25 Apr 1995 10:08:44 -0700 Received: by haven.uniserve.com id <151>; Tue, 25 Apr 1995 10:22:31 -0700 Date: Tue, 25 Apr 1995 10:21:45 -0700 (PDT) From: Tom Samplonius To: Sean Kelly cc: questions@FreeBSD.org Subject: Re: BT946C strangeness In-Reply-To: <9504251639.AA28381@yarmouth.fsl.noaa.gov> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: questions-owner@FreeBSD.org Precedence: bulk On Tue, 25 Apr 1995, Sean Kelly wrote: > >>>>> "Tom" == Tom Samplonius writes: > > Tom> I've just got a BT946C, and decided to try it out with the > Tom> latest SNAP. The weird part is that is detects it as a EISA > Tom> device! > > You think that's bad? My own BT946C under 2.0-RELEASE is an ISA > device: That's easy. Just disable the ISA compatibility port in the setup. Then config FreeBSD to use the PCI port (probably e800) instead. However, this really won't make a speed difference as I found out, and there may be something I'm missing. > And after installing it, I got a new mystery message during the pci > probe: > > pci0:11: vendor=0xffff, device=0x140, class=storage [not supported] > map(10): io(334) > > Huh? This confuses me too. Tom