Date: Fri, 9 Apr 1999 18:24:23 +0200 (CEST) From: Wilko Bulte <wilko@yedi.iaf.nl> To: ken@plutotech.com (Kenneth D. Merry) Cc: freebsd-scsi@freebsd.org Subject: Re: Getting Pioneer CD changer to work Message-ID: <199904091624.SAA12343@yedi.iaf.nl> In-Reply-To: <199904082311.RAA12752@panzer.plutotech.com> from "Kenneth D. Merry" at "Apr 8, 1999 5:11:54 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
As Kenneth D. Merry wrote ...
> Wilko Bulte wrote...
> > As Kenneth D. Merry wrote ...
> > > Wilko Bulte wrote...
> > > > As Kenneth D. Merry wrote ...
> > > > > Wilko Bulte wrote...
> > > > > > As Kenneth D. Merry wrote ...
> > > > > > > Wilko Bulte wrote...
> > > > > > > > As Kenneth D. Merry wrote ...
> > > > > > > > > Wilko Bulte wrote...
> > That is what I meant. It works with or without the quirk entry. I tried
> > both. Interestingly enough there is a quirk entry for Pioneer already, but
> > my drive has a slightly different inquiry string:
> >
> > {
> > { T_CDROM, SIP_MEDIA_REMOVABLE, "PIONEER", "CD-ROM
> > DRM-604X",
> > "*"}, /* quirks */ CD_Q_CHANGER
> > },
> > {
> > { T_CDROM, SIP_MEDIA_REMOVABLE, "PIONEER", "CD-ROM DRM-600",
> > "*"}, /* quirks */ CD_Q_CHANGER
> > },
> >
> > I'm not sure if it is worthwhile to put a quirk in the driver for this
> > drive. Maybe if I can get info on why READ TOCs etc fail.. Just sent
> > mail to Pioneer in Belgium to ask for a SCSI implementation manual for this
> > drive. Lets be optimistic..
>
> Hmm, well, my guess is that the 604 is just a newer version of the drive
> you have. I haven't heard any complaints from any 604 owners about read
> toc problems, so my guess is that it's a SCSI-2 drive.
My guess too. I found a couple of identical changers on a system at work.
I asked the 'owner' to find out what firmware revs they have. If it is
different/newer or maybe the DMR-604X of the quirk entry above I'll try
to borrow it's firmware rom for a quick trip to the prom programmer.
> > > > 'Most any' appears to be the right term for it ;) I'll experiment a bit
> > > > more. Just go a solid system lockup by running a 'dd if=/dev/rcd0a' and
> > > > a 'mount /dev/cd1a ...' at the same time. Only ping still works. Hmm.
> > > > More testing to do I guess
> > >
> > > Hmm, interesting. What happens if you just try the DD? Can you break into
> > > the debugger when the machine locks up?
> >
> > I made a new kernel with the debugger in. I'll have it run overnight to see
> > if it re-occurs. In the meantime there was also a spontaneous reboot. No
> > panic as far as I can see. I'll try to reproduce.. Just the DD seems
> > to work just fine.
>
> Hmm, sounds strange indeed.
In the meantime I ran the test again. No machine lockup this time. But
already twice a solid lockup of the drive.. It goes completely comatose,
not even a SCSI reset from a FreeBSD reboot awakens it. The only thing
what works is a whack over the head with the powerswitch. This definitely
is a brilliant piece of firmware I have.
Console messages:
(cd0:isp0:0:5:0): cddone: got error 0x6 back
(cd4:isp0:0:5:4): cddone: got error 0x6 back
(cd3:isp0:0:5:3): cddone: got error 0x6 back
(cd1:isp0:0:5:1): cddone: got error 0x6 back
Sidetracking a bit: man xpt mentions /dev/xpt. /dev/MAKEDEV does not
have it though. Is it supposed to be a manual operation with mknod?
Or is my /dev/MAKEDEV out of date?
Groeten / Cheers,
Wilko
_ ______________________________________________________________________
| / o / / _ Arnhem, The Netherlands
|/|/ / / /( (_) Bulte WWW : http://www.tcja.nl
_______________________ Powered by FreeBSD ___ http://www.freebsd.org _____
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?199904091624.SAA12343>