| 1 |
On Fri, Nov 20, 2009 at 01:36:27PM +0100, Joerg Schilling wrote: |
| 2 |
> José Romildo Malaquias <j.romildo@×××××.com> wrote: |
| 3 |
> |
| 4 |
> > > BTW: this may be caused by the fact that you did not simply add debug=2 |
| 5 |
> > > but at the same time removed -V. |
| 6 |
> > |
| 7 |
> > I have run the cdrecord command again, this time passing "-V" and "debug=2": |
| 8 |
> > |
| 9 |
> > $ script -f -c "cdrecord -vvv -V debug=2 -sao -eject speed=8 fs=256m driveropts=burnfree /var/tmp/image.iso" cdrecord.log |
| 10 |
> > |
| 11 |
> > and the compressed log is attached. |
| 12 |
> > |
| 13 |
> > I hope you can find anything useful to understand what is happening. |
| 14 |
> |
| 15 |
> I'll look at this later. Could you meanwhile do a test without -V please? |
| 16 |
> |
| 17 |
> There was a report for broken Pioneer formware that hits in -v mode and |
| 18 |
> causes the firmware from the drive to through away the data before writing |
| 19 |
> it to the medium. |
| 20 |
|
| 21 |
Do you mean a test without -V or -v ? |
| 22 |
|
| 23 |
Romildo |
Archives