Date: Fri, 29 Dec 1995 14:24:27 +0100 From: se@zpr.uni-koeln.de (Stefan Esser) To: balu@reido.in-berlin.de (Boris Staeblow) Cc: current@freefall.freebsd.org Subject: Re: SCSI II CDROM fails to play Message-ID: <199512291324.AA16829@Sysiphos> In-Reply-To: balu@reido.in-berlin.de (Boris Staeblow) "SCSI II CDROM fails to play" (Dec 29, 13:45)
next in thread | raw e-mail | index | archive | help
On Dec 29, 13:45, Boris Staeblow wrote: } Subject: SCSI II CDROM fails to play } } I've a problem with my new CDROM - It refuse to play audio cd's: } (No problems with W95). } } (ncr0:5:0): "SONY CD-ROM CDU-76S 1.1a" type 5 removable SCSI 2 } cd0(ncr0:5:0): CD-ROM } cd0(ncr0:5:0): 200ns (5 Mb/sec) offset 8. Looks fine so far ... } cd0(ncr0:5:0): UNIT ATTENTION asc:28,0 } cd0(ncr0:5:0): Not ready to ready transition, medium may have changed Well, there was a CD in the drive, and the middle layer SCSI code has been notified of this fact. } When I try to play audio cd's (xcdplayer,cdplay etc.): } } cd0(ncr0:5:0): ILLEGAL REQUEST asc:26,0 Invalid field in parameter list The command has been sent correctly and a status received. Seems there was an illegal (or not understood) parameter in the command last sent. This is not a driver problem, but perhaps the drive does not like some optional field in a request sent by cdplay ... } Is the audio-play support broken? >From some earlier mail exchange with someone who had trouble playing audio CDs: % > Verify that the program does work with the Adaptec. If it does % > you have found a bug. % % I no more have the adaptec. However, I have found the problem :-) % % $ cdplay cd1 % CD>tocentry % track minute second frame % 1 0 2 0 % 2 22 39 3 % 255 43 44 3 % CD>msfplay 0 2 0 43 44 3 % cdplay: Invalid argument #ILLEGAL REQUEST asc:24,0 Invalid field in CDB % CD>msfplay 0 2 0 43 44 2 % CD>stop % % I always used the last minute-second-frame with the msf play % command. Apparently, one must not play the last frame of the disk. But % this does not explain why the adaptec driver does not report the error: % the bug is now in the aha1542 driver :-) Perhaps you can try a few such commands, too, and let us know what you find ... } (BTW: What's the "UNIT ATTENTION" at boot-up?) Just a notification to the upper level code, which might for example make it "umount" some file system it had mounted from that drive before ... Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/~se <se@ZPR.Uni-Koeln.DE>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199512291324.AA16829>