From owner-freebsd-scsi Wed Dec 3 07:16:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA15027 for freebsd-scsi-outgoing; Wed, 3 Dec 1997 07:16:57 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from conductor.synapse.net (conductor.synapse.net [199.84.54.18]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id HAA15012 for ; Wed, 3 Dec 1997 07:16:50 -0800 (PST) (envelope-from evanc@synapse.net) Received: (qmail 10441 invoked from network); 3 Dec 1997 15:16:42 -0000 Received: from cello.synapse.net (199.84.54.81) by conductor.synapse.net with SMTP; 3 Dec 1997 15:16:42 -0000 Date: Wed, 3 Dec 1997 10:16:42 -0500 (EST) From: Evan Champion Reply-To: Evan Champion To: "Steve R. Kaczkowski" cc: freebsd-scsi@FreeBSD.ORG Subject: Re: BT-958 ASYNC Lameness fixed? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 3 Dec 1997, Steve R. Kaczkowski wrote: > Ahhhh, it *IS* a problem.. Seems that the driver is a BIT behind and the > card responds with different info and it defaults to SLOW SLOW mode... It doesn't seem to be a problem on 3.0-current... bt0: rev 0x08 int a irq 14 on pci0.10.0 bt0: Bt958 / 0-(32bit) bus bt0: reading board settings, busmastering, int=14 bt0: version 5.07B, fast sync, parity, 32 mbxs, 32 ccbs bt0: targ 0 sync rate=10.00MB/s(100ns), offset=15 bt0: targ 6 sync rate=10.00MB/s(100ns), offset=15 bt0: Using Strict Round robin scheme scbus0 at bt0 bus 0 sd0 at scbus0 target 0 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access 2047MB (4194058 512 byte sectors) cd0 at scbus0 target 6 lun 0 cd0: type 5 removable SCSI 2 cd0: CD-ROM cd present [272451 x 2048 byte records] (of course, it is misreporting my first target; it is a fast and wide device, so it should be reporting it as 20 MB/s). I suspect a) this problem isn't actually a problem, in that it's not the OS that decides if the device will run async, but the card itself, and b) if you want to get rid of the erroneous output, upgrade to 2.2.5 or 3.0-current. Evan