Date: Sat, 8 May 1999 01:39:34 -0600 (MDT) From: "Kenneth D. Merry" <ken@plutotech.com> To: wilko@yedi.iaf.nl (Wilko Bulte) Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Getting Pioneer CD changer to work Message-ID: <199905080739.BAA57620@panzer.plutotech.com> In-Reply-To: <199905072129.XAA32584@yedi.iaf.nl> from Wilko Bulte at "May 7, 1999 11:29:45 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Wilko Bulte wrote...
> 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: <PIONEER CD-ROM DRM-600 2404> Removable CD-ROM SCSI-CCS device
> (when set to non-SCSI2 mode via the dipswitch on the back)
>
> or
>
> /kernel: cd3: <PIONEER CD-ROM DRM-604X 2404> 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.
Cool!
> 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.
That's not terribly surprising. The defaults are okay for Nakamichi
changers. Perhaps they should be changed...
> 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...
Hmm, it looks like the initial read capacity is timing out. You can try
increasing the timeout for the read capacity in the probe case of
cdstart() and see if that fixes the problem.
I'm not sure, though, why the timeouts work okay for the QLogic board and
not for the NCR. That's rather perplexing.
Ken
--
Kenneth Merry
ken@plutotech.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199905080739.BAA57620>