[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: cdrecord-2.01.01a18: MMC-3 speed select did not work.



Giulio Orsero <giulioo@gmail.com> wrote:

> linux-2.4.32
> LG USB GSA-E10L (HL-DT-ST DVDRAM GSA-E10L LE05)
> 4x DVD+RW
> cdrecord -data padsize=512s -v driveropts=burnfree -sao iso=/path/iso.iso
>
> I upgraded to cdrecord-2.01.01a18 (from cdrecord-2.01.01a09) and some new
> error/warning messages started appearing.
> The burning process seems to be ok, but they look ugly.
> Should I worry? Should I ignore them?
>
> See various "input/output error", "CDB", "status:".... 
>
> Linux sg driver version: 3.1.25
> SCSI buffer size: 64512
> cdrecord: Input/output error. get performance: scsi sendcmd: no error    
> CDB:  AC 00 00 00 00 00 00 00 00 64 03 00                
> status: 0x0 (GOOD STATUS)                       
> cmd finished after 0.004s timeout 200s
> Cdrecord-ProDVD-Clone 2.01.01a18 (i686-pc-linux-gnu) Copyright (C) 1995-2006
> Jörg Schilling
> TOC Type: 1 = CD-ROM
> Using libscg version 'schily-0.8'.
> Driveropts: 'burnfree'
> ...
> ...
> Drive buf size : 1114112 = 1088 KB
> Drive pbuf size: 1966080 = 1920 KB
> Drive DMA Speed: 6490 kB/s 36x CD 4x DVD
> FIFO size      : 4194304 = 4096 KB
> cdrecord: Input/output error. get performance: scsi sendcmd: no error
> CDB:  AC 00 00 00 00 00 00 00 00 64 03 00
> status: 0x0 (GOOD STATUS)
> cmd finished after 0.004s timeout 100s
> cdrecord: MMC-3 speed select did not work.
> cdrecord: Input/output error. get performance: scsi sendcmd: no error
> CDB:  AC 00 00 00 00 00 00 00 00 64 03 00
> status: 0x0 (GOOD STATUS)
> cmd finished after 0.004s timeout 100s
> cdrecord: Input/output error. get performance: scsi sendcmd: no error
> CDB:  AC 00 00 00 00 00 00 00 00 64 03 00
> status: 0x0 (GOOD STATUS)
> cmd finished after 0.004s timeout 100s
> cdrecord: MMC-3 speed select did not work.
> Track 01: data     1 MB         padsize:    1 MB
> Total size:        2 MB = 1509 sectors
> Current Secsize: 2048
> Trying to clear drive status.

If this is not caused by bad cabling, then this is caused by a 
Linux kernel bug. You need to send this to the Linux Kernel group.

Jörg

-- 
 EMail:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
       js@cs.tu-berlin.de                (uni)  
       schilling@fokus.fraunhofer.de     (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily



Reply to: