RE: plextor px-708uf: cannot get disk type
I guess the answer is: use growisofs with this unit, or get Plextor to do
something about this firmware. I'm not at all opposed to growisofs/k3b, I
was just used to xcdroast for burning CDs.
Have you dealt with anyone at Plextor that I might try to explain this to?
Incidentally, Alan Stern at linux-usb-devel is also looking this over from
the usb-storage end, and I'll post something here if he has something to
add.
Thanks for the note about the dvd+rw-tools update.
Thank you,
Tom
> -----Original Message-----
> From: appro@fy.chalmers.se [mailto:appro@fy.chalmers.se]
> Sent: Thursday, February 05, 2004 12:13 PM
> To: Thomas J Magliery PhD
> Cc: cdwrite@other.debian.org
> Subject: Re: plextor px-708uf: cannot get disk type
>
> > Version with dinfo[32+4]
> > ==============
> > [magliery@reganlinux dvd+rw-tools-5.16.4.8.5]$ ./test /dev/scd0
> > :-( unable to READ DISK INFORMATION: Input/output error
> > ==============
>
> The above program uses READ DISK INFORMATION with length parameter used
> by cdrecord.
>
> > Version with dinfo[32]
> > ==============
> > [magliery@reganlinux dvd+rw-tools-5.16.4.8.5]$ ./test2 /dev/scd0
> > 00 22 00 01 01 01 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 23 05 40
> > 00 00 00 00 00 00 00 00
> > ==============
>
> And this one uses READ DISK INFORMATION with length parameter used by
> growisofs.
>
> > What does *this* mean?
>
> This means that there is no further need for me to assure that growisofs
> works not because it ignores errors [as Joerg implies], but because it
> does things differently.
>
> To wrap up. My initial assumption that it was hardly a firmware
> deficiency was wrong. It is a firmware bug: unit apparently sends less
> information than promised (the second number in above printout should be
> 0x20(*) and 0x20 is the number which I observed uncounted number of
> times in different units). Could Linux USB implementation have managed
> it with more grace? I'm not really in position to judge, but maybe.
>
> (*) You should be able to verify it by declaring dinfo[32+2] in
> previously posted snippet.
>
> Oh! From your prompt one can assume that you use 5.16.x. Note that
> 5.17.x is strongly recommended update for those who use 5.14 through
> 5.16. Cheers. A.
Reply to: