From owner-freebsd-scsi Tue Jan 4 16:34:20 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 6979E15043 for ; Tue, 4 Jan 2000 16:34:15 -0800 (PST) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id TAA11176; Tue, 4 Jan 2000 19:34:17 -0500 (EST) (envelope-from bsdx@looksharp.net) Date: Tue, 4 Jan 2000 19:34:17 -0500 (EST) From: Adam To: Gerard Roudier Cc: scsi@FreeBSD.ORG Subject: Re: sym troubles In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 5 Jan 2000, Gerard Roudier wrote: >I suggest you the following magic command that should avoid the offending >CHECK CONDITION and should allow the driver to negotiate SYNC=3D20MHz on= =20 >the normal INQUIRY command and prove us it did so as expected: > > ******************************** > * camcontrol inquiry cd1 -D -R * > ******************************** > >I expect this one to finally tell us the truth. Answer should resemble the >following as you know: > >pass1: Removable CD-ROM SCSI-2 device=20 >pass1: 40.000MB/s transfers (16bit) + some BLAH BLAH BLAH > > G=E9rard. True! :) Does this mean it is operating properly a) without special prodding b) only with prodding c) never? I'm just curious if any of this would bring down the bus speed when accessing the cdrom if I had any UW hd's on the bus for example, or if it is purely a cosmetic issue. Also wondering why ncr0 works fine with it :P sapphire:~ % camcontrol inquiry cd1 -D -R=20 pass1: Removable CD-ROM SCSI-2 device=20 pass1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit) sapphire:~ % camcontrol inquiry cd1=20 pass1: Removable CD-ROM SCSI-2 device=20 pass1: 6.600MB/s transfers (16bit) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message