From owner-freebsd-hardware Wed Apr 17 9:16:56 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by hub.freebsd.org (Postfix) with ESMTP id 0037037B400 for ; Wed, 17 Apr 2002 09:16:53 -0700 (PDT) Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by sasami.jurai.net (8.12.2/8.12.2) with ESMTP id g3HGGi2A011863; Wed, 17 Apr 2002 12:16:44 -0400 (EDT) (envelope-from winter@jurai.net) Date: Wed, 17 Apr 2002 12:16:44 -0400 (EDT) From: "Matthew N. Dodd" To: Peter Jeremy Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Buslogic BT-445S problems In-Reply-To: <20020417201714.A56049@gsmx07.alcatel.com.au> Message-ID: <20020417121328.Q42854-100000@sasami.jurai.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, 17 Apr 2002, Peter Jeremy wrote: > bt0 at port 0x330-0x333 irq 11 drq -1 on isa0 ^^^^^^ Is this for real or just a transcription error? > bt0: BT-445S FW Rev. 3.36 Narrow SCSI Host Adapter, SCSI ID 7, 30CCBs > bt0: Using Strict Round Robin Mailbox Mode Hummm... The source mentions that firmware revision 3.37 is good and all others need a workaround; it could be the workaround code isn't doing the right thing. > I noticed that enabling the card BIOS makes it just lock up after > the "card found at 0x330" message, but I'm not sure if this is > just because it can't find any SCSI disks to boot. If the BIOS won't come up that sounds like something outside of FreeBSD drvier issues. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message