Hello,
I am piggybacking on this subject line that I found in the archives because it
describes my problem, even though I think I have a different problem from that
of the the original poster.
I have an LG 8080B attached to a Celeron 400 machine running under Redhat
Linux 6.0, kernel 2.5.5-15. I have set it up using ide-scsi as per the Howto
and some helpful Redhat-specific tips at http://www.leewardfpga.com/cdrw.html.
I compiled cdrecord 1.9 without incident and I can record cdroms at speed=4
without any problems.
However, when I try speed=8 (with -dummy), the write always fails part way
through. I'm doing this with the machine not networked and top showing <1%
cpu and memory use before I start. If I run top while recording (which I
usually don't) the numbers never get up to 3%. If I use the -v switch, the
number of Mb written starts running as it does at speed=4 (except twice as
fast), but stops before the end (always at a different number) and just sits
until I get a timeout message or hit ctrl-c. I don't think it is a buffer
underrun problem, because the percent full indicator is always in the high 90s
and when I get a report at the end the minimum reported is never as low as 70%
and usually a lot higher. Here is an example:
prompt> cdrecord -v -dummy -speed=8 dev=0,0,0 rom
Cdrecord 1.9 (i686-pc-linux-gnu) Copyright (C) 1995-2000 Jörg Schilling
TOC Type: 1 = CD-ROM
scsidev: '0,0,0'
scsibus: 0 target: 0 lun: 0
Using libscg version 'schily-0.1'
atapi: 1
Device type : Removable CD-ROM
Version : 0
Response Format: 1
Vendor_info : 'LG '
Identifikation : 'CD-RW CED-8080B '
Revision : '1.06'
Device seems to be: Generic mmc CD-RW.
Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
Driver flags : SWABAUDIO
Drive buf size : 1024000 = 1000 KB
FIFO size : 4194304 = 4096 KB
Track 01: data 500 MB
Total size: 574 MB (56:56.72) = 256254 sectors
Lout start: 575 MB (56:58/54) = 256254 sectors
Current Secsize: 2048
ATIP info from disk:
Indicated writing power: 4
Is not unrestricted
Is not erasable
Disk sub type: Medium Type A, high Beta category (A+) (3)
ATIP start of lead in: -11250 (97:32/00)
ATIP start of lead out: 337275 (74:59/00)
Disk type: Long strategy type (Cyanine, AZO or similar)
Manuf. index: 26
Manufacturer: TDK Corporation
Blocks total: 337275 Blocks current: 337275 Blocks remaining: 81021
Starting to write CD/DVD at speed 8 in dummy mode for single session.
Last chance to quit, starting dummy write in 1 seconds.
Waiting for reader process to fill input buffer ... input buffer ready.
Starting new track at sector: 0
Track 01: 56 of 500 MB written (fifo 99%).cdrecord: faio_wait_on_buffer for writer
timed out.
fifo had 1930 puts and 1803 gets.
On this particular occasion, after about a 10 min wait, I hit ctrl-c and got
cdrecord: fifo was 0 times empty and 760 times full, min fill was 96%.
Sometimes, though, after a wait of 4 minutes, I see
240000000 microseconds passed waiting for 2 current: 3 idx: 0
On another occasion, the output ended with
cdrecord: Input/output error. write_g1: scsi sendcmd: retryable error
CDB: 2A 00 00 01 98 88 00 00 10 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 24 00 00 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x24 Qual 0x00 (invalid field in cdb) Fru 0x0
Sense flags: Blk 0 (not valid)
write track data: error after 154796032 bytes
DMA addr: 0xBFFFDCAC size: 18 - using copy buffer
Sense Bytes: 70 00 00 00 00 00 00 0A 00 00 00 00 00 00 00 00 00 00
DMA addr: 0x00000000 size: 0 - using copy buffer
DMA addr: 0x00000000 size: 0 - using copy buffer
If I use the -debug flag, there is a continuous flow of lines of the form
DMA addr: <N> size: 32768 - using copy buffer
where N increases by 8000 each time
with occasional lines like
gets: 4509 puts: 4632 cont: 123 low: 124
The numbers change, but the "cont" one is always the difference between the
puts and the gets, and "low" is always one greater than "cont".
Should I just be happy that I can write at speed=4 and get on with my life,
or is there something I can do to achieve speed=8, which the 8080B is supposed
to be capable of?
Thanks in advance.
Stephen Isard
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
