Dear all,
I am running Suse 7.3 with kernel 2.4.10 and
Cdrecord 1.11a05 (i686-suse-linux).
My Cd writer is a Waitec Storm 24.
I have problems writing audio both in dummy
mode or in real mode.
I use gcombust or the command line:
cdrecord -v -eject fs=4m speed=2 dev=0,0,0 -dao *.wav
cdrecord -scanbus gives:
Cdrecord 1.11a05 (i686-suse-linux) Copyright (C) 1995-2001 J�rg Schilling
Linux sg driver version: 3.1.20
Using libscg version 'schily-0.5'
scsibus0:
0,0,0 0) 'WAITEC ' 'STORM24 ' 'B1.4' Removable CD-ROM
0,1,0 1) *
0,2,0 2) *
0,3,0 3) *
0,4,0 4) *
0,5,0 5) *
0,6,0 6) *
0,7,0 7) *
the device is at:
lrwxrwxrwx 1 root root 8 Apr 5 18:27 /dev/cdrecorder ->
/dev/sr0
When I try to write I get errors like the following after some tracks (may be
3 or 15):
Starting new track at sector: 360128
Track 03: 35 of 46 MB written (fifo 100%).cdrecord: Input/output error.
write_g1: scsi sendcmd: retryable error
CDB: 2A 00 00 05 BC 73 00 00 1B 00
status: 0x0 (GOOD STATUS)
cmd finished after 200.096s timeout 200s
write track data: error after 37149840 bytes
cdrecord: faio_wait_on_buffer for writer timed out.
cdrecord: Input/output error. request_sense: scsi sendcmd: retryable error
CDB: 03 00 00 00 12 00
status: 0x0 (GOOD STATUS)
cmd finished after 205.060s timeout 200s
Writing time: 632.938s
Fixating...
cdrecord: Input/output error. flush cache: scsi sendcmd: retryable error
CDB: 35 00 00 00 00 00 00 00 00 00
status: 0x0 (GOOD STATUS)
cmd finished after 205.060s timeout 200s
Trouble flushing the cache
cdrecord: Input/output error. prevent/allow medium removal: scsi sendcmd:
retryable error
CDB: 1E 00 00 00 00 00
status: 0x0 (GOOD STATUS)
cmd finished after 205.060s timeout 200s
cdrecord: Input/output error. start/stop unit: scsi sendcmd: retryable error
CDB: 1B 00 00 00 02 00
status: 0x0 (GOOD STATUS)
cmd finished after 819.399s timeout 200s
After that I have to reboot. I can't find a way to solve the problem
Is anyone able to help me?
Many thanks
Antonio Pagliaro
-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
