Re: xroastcd fails to verify
Brian May <bam@snoopy.apana.org.au> writes:
> >OTOH, I have the same CDR with 4.17, and it doesn't work under
> >Linux. I'm quite desperate at this point -- have been trying for 3
> >months, and no luck -- cdrecord (and cdrdao) both crap out at the very
> >beginning of the burning process, saying threre's some SCSI retryable
> >error. Have to boot into Win every time I want to burn a CD. :(
>
> I use to have the same problem...
Well, maybe there is hope for me after all. ;^)
> Either upgrading to the latest 2.2.3 (I think) or the latest cdrecord
> helped me.
> (I use the cdrecord and xcdroast from slink).
I have fetched and compiled latest cdrecord and cdrdao from respective
sites.
> >So, my advice for you is to first try 4.14, and only if it doesn't
> >work, then try the 4.17. AFAIK 4.17 doesn't have any significant
> >improvements. See http://homepages.tig.com.au/~cdysan/cw-7502/
>
> Thanks. I will probably try 4.17 first - if I have the same problem
> as you, at least I should find out sooner ;-).
Can you please let me know if you drive will work with 4.17? Also,
which kernel are you running on?
> >I'm considering downgrading firmware to 4.14 just to try -- maybe it
> >will work... [sigh]
>
> Do you have the latest cdrecord? I don't know what fixed the
> same problem for me - it just ... vanished ;-)
Yes, as I said... I guess I should hope for magic. :^| I try new
kernes just as soon as they come out, and I do the same with the
cdrdao and cdrecord -- all in hope that my CDR will all of a sudden
start working. I have 2.2.10 now. I even tried patching the scsi
includes with the code from Joerg Shilling's (SP?) site, the author of
cdrecord. And it didn't help.
--
Arcady Genkin
"... without money one gets nothing in this world, not even a certificate
of eternal blessedness in the other world..." (S. Kierkegaard)
Reply to: