From owner-freebsd-scsi Mon Oct 14 12:45:32 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 29D6637B401 for ; Mon, 14 Oct 2002 12:45:29 -0700 (PDT) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C07543E97 for ; Mon, 14 Oct 2002 12:45:23 -0700 (PDT) (envelope-from wkb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.12.6/8.12.6) with ESMTP id g9EJjKFu028841; Mon, 14 Oct 2002 21:45:20 +0200 (CEST) (envelope-from wkb@freebie.xs4all.nl) Received: (from wkb@localhost) by freebie.xs4all.nl (8.12.6/8.12.6/Submit) id g9EJjJtM028840; Mon, 14 Oct 2002 21:45:19 +0200 (CEST) Date: Mon, 14 Oct 2002 21:45:19 +0200 From: Wilko Bulte To: "Kenneth D. Merry" Cc: Kurt Seel , freebsd-scsi Subject: Re: pioneer DRM-600 problem Message-ID: <20021014214519.F28379@freebie.xs4all.nl> References: <3D5B17A4.D2862CA6@utcorp.com> <3DA5CF94.6260EC18@utcorp.com> <20021010133409.A50349@panzer.kdm.org> <3DA60E3F.BA8A597A@utcorp.com> <20021010223418.A53347@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20021010223418.A53347@panzer.kdm.org>; from ken@kdm.org on Thu, Oct 10, 2002 at 10:34:18PM -0600 X-OS: FreeBSD 4.7-RC X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, Oct 10, 2002 at 10:34:18PM -0600, Kenneth D. Merry wrote: > On Thu, Oct 10, 2002 at 19:33:19 -0400, Kurt Seel wrote: > > "Kenneth D. Merry" wrote: > > > On Thu, Oct 10, 2002 at 15:05:56 -0400, Kurt Seel wrote: > > > > Kurt Seel wrote: > > > > > > > > > > I am using FBSD 4.5-stable. > > > > > I have a Pioneer DRM-600. I passes the self diagnostic, > > > > > where to de-cable the unit, power off, flip switches 6 & > > > > > 8, then power on. It goes through loading each disc, then > > > > > ejects. Just like it should. > > > > > When the machine boots, scans the unis and finds 6 cd devs, > > > > > dmesg output at the end of this message. > > > > > But when I type : > > > > > chio status > > > > > I get this : > > > > > chio: /dev/ch0: open: Device not configured > > > > > So I made sure the devices were make, e.g. > > > > > cd /dev; ./MAKEDEV cd5; ./MAKEDEV ch0 > > > > > And : > > > > > mount -t cd9660 /dev/cd0c /conf/tmpmnt > > > > > Gives me : > > > > > cd9660: /dev/cd0c: Device busy > > > > > > > > > > I have tried it with evey permutation of option switches, > > > > > e.g. parity on, parity off ... no dice. > > > > > Is there any hope for this unit? I'de really like to put > > > > > 6 CD's of mp3'ed music on a (atapi) cdrom booted (if you > > > > > look at the dmesg you'll see root is cd9660:acd0c - could > > > > > this be causing the problem?) network music server. > > > > > > > > > > > > > I could not get this machine rebuilt, so I moved the device > > > > to another machine. Which 'sees' the device : > > > > > > > > New /dev > camcontrol devlist > > > > at scbus0 target 0 lun 0 (cd2,pass2) > > > > at scbus0 target 1 lun 0 (pass0,cd0) > > > > at scbus0 target 6 lun 0 (cd1,pass1) > > > > at scbus0 target 6 lun 1 (cd3,pass3) > > > > at scbus0 target 6 lun 2 (cd4,pass4) > > > > at scbus0 target 6 lun 3 (cd5,pass5) > > > > at scbus0 target 6 lun 4 (cd6,pass6) > > > > at scbus0 target 6 lun 5 (cd7,pass7) > > > > at scbus0 target 6 lun 6 (pass8) > > > > at scbus0 target 6 lun 7 (pass9) > > > > > > > > I have gotten musid CD's to play via xmcd (from ports) but I get > > > > the same 'device busy' when I try to mount (a data cd, storebought > > > > or home brew): > > > > > > > > New /root > mount -t cd9660 /dev/cd1c /cdrom1 > > > > cd9660: /dev/cd1c: Device busy > > > > > > Does anything show up in the dmesg? If nothing shows up in the dmesg, try > > > booting with -v. > > > > A hell of alot, actually. I am not really sure what caused > > what so I'll include the whole mess: > > > > cd1 at ahc0 bus 0 target 6 lun 0 > > cd1: Removable CD-ROM SCSI-CCS device > > cd1: 3.300MB/s transfers > > cd1: cd present [321646 x 2048 byte records] > > cd2 at ahc0 bus 0 target 0 lun 0 > > cd2: Removable CD-ROM SCSI-2 device > > cd2: 10.000MB/s transfers (10.000MHz, offset 15) > > cd2: cd present [261209 x 2048 byte records] > > cd3 at ahc0 bus 0 target 6 lun 1 > > cd3: Removable CD-ROM SCSI-CCS device > > cd3: 3.300MB/s transfers > > cd3: cd present [91407 x 2048 byte records] > > cd4 at ahc0 bus 0 target 6 lun 2 > > cd4: Removable CD-ROM SCSI-CCS device > > cd4: 3.300MB/s transfers > > cd4: cd present [332253 x 2048 byte records] > > cd5 at ahc0 bus 0 target 6 lun 3 > > cd5: Removable CD-ROM SCSI-CCS device > > cd5: 3.300MB/s transfers > > cd5: cd present [214998 x 2048 byte records] > > cd6 at ahc0 bus 0 target 6 lun 4 > > cd6: Removable CD-ROM SCSI-CCS device > > cd6: 3.300MB/s transfers > > cd6: cd present [331220 x 2048 byte records] > > cd7 at ahc0 bus 0 target 6 lun 5 > > cd7: Removable CD-ROM SCSI-CCS device > > cd7: 3.300MB/s transfers > > cd7: cd present [326103 x 2048 byte records] > > (cd8:ahc0:0:6:6): READ CD RECORDED CAPACITY. CDB: 25 c0 0 0 0 0 0 0 0 0 > > (cd8:ahc0:0:6:6): ILLEGAL REQUEST asc:25,0 > > (cd8:ahc0:0:6:6): Logical unit not supported > > (cd8:ahc0:0:6:6): fatal error, failed to attach to device > > (cd8:ahc0:0:6:6): lost device > > (cd8:ahc0:0:6:6): removing device entry > > (cd9:ahc0:0:6:7): READ CD RECORDED CAPACITY. CDB: 25 e0 0 0 0 0 0 0 0 0 > > (cd9:ahc0:0:6:7): ILLEGAL REQUEST asc:25,0 > > (cd9:ahc0:0:6:7): Logical unit not supported > > (cd9:ahc0:0:6:7): fatal error, failed to attach to device > > (cd9:ahc0:0:6:7): lost device > > (cd9:ahc0:0:6:7): removing device entry > > Even though the device only has 6 LUNs, it looks like it is responding on > two more for some reason, and then rightly complaining when we try to > issue a read capacity to those LUNs. IIRC I had such a drive some EONs ago. You might want to check the mailing list archives, as I've been having some fun using it. At some point I got a newer firmware ROM, flipped a dipswitch and things worked a lot better afterwards. As I said, IIRC, and I no longer own this beast. -- | / o / /_ _ FreeBSD core team secretary |/|/ / / /( (_) Bulte wilko@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message