From owner-freebsd-scsi Fri May 7 15: 6: 7 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id B882F153FB for ; Fri, 7 May 1999 15:05:50 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: (from uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id XAA13188; Fri, 7 May 1999 23:38:29 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.6.12) id XAA32584; Fri, 7 May 1999 23:29:45 +0200 (CEST) From: Wilko Bulte Message-Id: <199905072129.XAA32584@yedi.iaf.nl> Subject: Re: Getting Pioneer CD changer to work In-Reply-To: <199904130349.VAA09442@panzer.plutotech.com> from "Kenneth D. Merry" at "Apr 12, 1999 9:49:40 pm" To: ken@plutotech.com (Kenneth D. Merry) Date: Fri, 7 May 1999 23:29:45 +0200 (CEST) Cc: freebsd-scsi@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Like I promised here is the status update for the Pioneer DRM-604X changer. Today I finally got hold of the new (well, newer) firmware roms. I'm running it on a -current of a couple of days ago. It is now at: /kernel: cd4: Removable CD-ROM SCSI-CCS device (when set to non-SCSI2 mode via the dipswitch on the back) or /kernel: cd3: Removable CD-ROM SCSI-2 device (when set to SCSI-2 mode). The problem: May 7 20:53:10 p100 /kernel: (cd3:isp0:0:5:2): READ TOC/PMA/ATIP {MMC Proposed} . CDB: 43 40 0 0 0 0 0 0 4 0 May 7 20:53:10 p100 /kernel: (cd3:isp0:0:5:2): ILLEGAL REQUEST asc:20,0 May 7 20:53:10 p100 /kernel: (cd3:isp0:0:5:2): Invalid command operation code can with this firmware rev be fixed by switching to SCSI-2 mode. The driver is now happy because the READ TOC cmd is no longer VU but adheres to the SCSI2 standard. I can still get the system to lock up with the default CHANGER_MIN_BUSY_SECONDS and CHANGER_MAX_BUSY_SECONDS. A kernel built with # Pioneer cdloader options CHANGER_MIN_BUSY_SECONDS=5 options CHANGER_MAX_BUSY_SECONDS=15 works fine, no lockups. Apparantly the defaults are too low for the Pioneer. All of the above was tested on a Qlogic 1040 board (isp driver). The only mystery left is that I can't get it to work using the ncr driver on a ncr810 board: May 7 23:35:07 p100 savecore: no core dump May 7 23:35:28 p100 /kernel: ncr1: timeout nccb=0xc0789200 (skip) May 7 23:35:28 p100 /kernel: (cd1:ncr1:0:5:0): got CAM status 0x4b May 7 23:35:28 p100 /kernel: (cd1:ncr1:0:5:0): fatal error, failed to attach to device May 7 23:35:28 p100 /kernel: (cd1:ncr1:0:5:0): lost device May 7 23:35:28 p100 /kernel: (cd1:ncr1:0:5:0): removing device entry May 7 23:35:50 p100 /kernel: ncr1: timeout nccb=0xc0788e00 (skip) May 7 23:36:12 p100 /kernel: ncr1: timeout nccb=0xc0788e00 (skip) May 7 23:36:12 p100 /kernel: (cd2:ncr1:0:5:1): got CAM status 0x4b May 7 23:36:12 p100 /kernel: (cd2:ncr1:0:5:1): fatal error, failed to attach to device etc. If anybody has a clue why the ncr is so much more obnoxious... Groeten / Cheers, | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message