>From: Dirk Pritsch <[EMAIL PROTECTED]>

>something strange happened here.
>I wanted to make a CD from some mp3 files, so I decoded them to wav
>using lame 3.92. As all looked ok, I fired up cdrecord and tried to burn
>them on a CD-R. But then I got the following error:

>Cdrecord 1.11a05 (i586-pc-linux-gnu) Copyright (C) 1995-2001 J�rg
>Schilling
>TOC Type: 0 = CD-DA
>scsidev: '0,0,0'
>scsibus: 0 target: 0 lun: 0
>Linux sg driver version: 3.1.23
>Using libscg version 'schily-0.5'
>atapi: 1
>Device type    : Removable CD-ROM
>Version        : 0
>Response Format: 1
>Vendor_info    : 'LG      '
>Identifikation : 'CD-RW CED-8080B '
>Revision       : '1.07'
>Device seems to be: Generic mmc CD-RW.
>Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
>Driver flags   : SWABAUDIO 
>Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P
>RAW/R96R
>Drive buf size : 1024000 = 1000 KB
>FIFO size      : 12582912 = 12288 KB
>Track 01: audio  39 MB (03:51.99) no preemp pad
>Track 02: audio  42 MB (04:12.70) no preemp pad
>Track 03: audio  41 MB (04:06.51) no preemp pad
>Track 04: audio  40 MB (03:59.77) no preemp pad
>Track 05: audio  33 MB (03:18.47) no preemp pad
>Track 06: audio  37 MB (03:40.84) no preemp pad
>Track 07: audio  37 MB (03:44.10) no preemp pad
>Track 08: audio  35 MB (03:28.35) no preemp pad
>Track 09: audio  43 MB (04:17.81) no preemp pad
>Total size:     350 MB (34:40.65) = 156049 sectors
>Lout start:     350 MB (34:42/49) = 156049 sectors
>Current Secsize: 2048
>ATIP info from disk:
>  Indicated writing power: 5
>  Is not unrestricted
>  Is not erasable
>  Disk sub type: Medium Type A, high Beta category (A+) (3)
>  ATIP start of lead in:  -11864 (97:23/61)
>  ATIP start of lead out: 359849 (79:59/74)
>Disk type:    Long strategy type (Cyanine, AZO or similar)
>Manuf. index: 49
>Manufacturer: Customer Pressing Oosterhout
>Blocks total: 359849 Blocks current: 359849 Blocks remaining: 203800
>Starting to write CD/DVD at speed 8 in write mode for single session.
>Last chance to quit, starting real write in 0 seconds. Operation starts.
>Waiting for reader process to fill input buffer ... input buffer ready.
>Performing OPC...
>Sending CUE sheet...
>/usr/bin/cdrecord: WARNING: Drive returns wrong startsec (0) using -150
>Writing pregap for track 1 at -150
>Starting new track at sector: 0
>Track 01:  39 of  39 MB written (fifo 100%).
>WARNING: padding up to secsize.
>Track 01: Total bytes read/written: 40923836/40924800 (17400 sectors).
>Starting new track at sector: 17400
>Track 02:   3 of  42 MB written (fifo 100%)./usr/bin/cdrecord:
>Input/output error. write_g1: scsi sendcmd: no error
>CDB:  2A 00 00 00 49 74 00 00 1B 00
>status: 0x2 (CHECK CONDITION)
>Sense Bytes: 70 00 04 00 00 00 00 0A 00 00 00 00 09 00 00 00
>Sense Key: 0x4 Hardware Error, Segment 0
>Sense Code: 0x09 Qual 0x00 (track following error) Fru 0x0
>Sense flags: Blk 0 (not valid) 
>cmd finished after 1.075s timeout 200s

>Under normal circumstances I would have said, this is a problem with my
>hardware (LG CED-8080B Fw.rev. 1.07), but until now, it worked
>flawlessly. I tried it a second time, and exactly the same happened at
>the same position (3 of 42 MB, track 2). 
>Now I downloaded another mp3 file from the internet, decoded this one,
>and burned the cd without any problem!

>So I wonder how a wav file can cause a cdrecord error? Could it be any
>strange sequence of bytes which can trigger that?

>I'm quite sure it is no hardware error, as I can burn 10 cds in a row,
>without any problems, and already had about 150 successful burns without
>any errors.


If you really believe that this is not caused by a dusty lens or by blank
media that does not work wit the drive it definiltely is a firmware bug.
Contact LG in this case.


J�rg

 EMail:[EMAIL PROTECTED] (home) J�rg Schilling D-13353 Berlin
       [EMAIL PROTECTED]               (uni)  If you don't have iso-8859-1
       [EMAIL PROTECTED]           (work) chars I am J"org Schilling
 URL:  http://www.fokus.gmd.de/usr/schilling   ftp://ftp.fokus.gmd.de/pub/unix


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to