[email protected] (Joerg Schilling) wrote: > José Romildo Malaquias <[email protected]> wrote: > > > > BTW: this may be caused by the fact that you did not simply add debug=2 > > > but at the same time removed -V. > > > > I have run the cdrecord command again, this time passing "-V" and "debug=2": > > > > $ script -f -c "cdrecord -vvv -V debug=2 -sao -eject speed=8 fs=256m > > driveropts=burnfree /var/tmp/image.iso" cdrecord.log > > > > and the compressed log is attached. > > > > I hope you can find anything useful to understand what is happening. > > I'll look at this later. Could you meanwhile do a test without -V please?
Sorry - I mean wihtout -v With -v, crecord calls "read buffer cap" and this may cause a firmware bug in your drive. Jörg -- EMail:[email protected] (home) Jörg Schilling D-13353 Berlin [email protected] (uni) [email protected] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
