So I compiled and installed cdrtools-1.10a-17 with GNU make and it worked
fine. However, this version still doesn't work when trying to burn a cd.
So you know, this is a Redhat 6.2 system, kernel 2.2.14-5.0. The drive is
a Matsushita (Panasonic) CW-7503. I'm using the sg driver. Please tell
me any other things to try that might help in diagnosing this error. It
looks to me like some scsi error, I wouldn't know where to go past that.
Here are the error messages:
[root@isr6009 bin]# ./cdrecord -v -dao -pad speed=4 dev=0,6,0
~awbailey/stuff/right.wav > foo 2>&1
scsidev: '0,6,0'
scsibus: 0 target: 6 lun: 0
Linux sg driver version: 2.1.36
Cdrecord 1.10a17 (i686-pc-linux-gnu) Copyright (C) 1995-2001 J�rg Schilling
TOC Type: 0 = CD-DA
Using libscg version 'schily-0.5'
atapi: 0
Device type : Removable CD-ROM
Version : 2
Response Format: 2
Capabilities : SYNC LINKED
Vendor_info : 'MATSHITA'
Identifikation : 'CD-R CW-7503 '
Revision : '1.06'
Device seems to be: Generic mmc CD-R.
Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
Driver flags : SWABAUDIO
Drive buf size : 2090928 = 2041 KB
FIFO size : 4194304 = 4096 KB
Track 01: audio 36 MB (03:36.42) no preemp pad
Total size: 36 MB (03:36.42) = 16232 sectors
Lout start: 36 MB (03:38/32) = 16232 sectors
Current Secsize: 2048
ATIP info from disk:
Indicated writing power: 5
Is not unrestricted
Is not erasable
Disk sub type: Medium Type A, low Beta category (A-) (2)
ATIP start of lead in: -11839 (97:24/11)
ATIP start of lead out: 336075 (74:43/00)
Disk type: Long strategy type (Cyanine, AZO or similar)
Manuf. index: 24
Manufacturer: SONY Corporation
Blocks total: 336075 Blocks current: 336075 Blocks remaining: 319843
Starting to write CD/DVD at speed 4 in write mode for single session.
Last chance to quit, starting real write in 9 seconds.8 seconds.7
seconds.6 seconds.5 seconds.4 seconds.3
seconds.2 seconds.1 seconds.
Waiting for reader process to fill input buffer ... input buffer ready.
Performing OPC...
Sending CUE sheet...
./cdrecord: WARNING: Drive returns wrong startsec (0) using -150
./cdrecord: Input/output error. write_g1: scsi sendcmd: no error
CDB: 2A 00 FF FF FF 6A 00 00 1B 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 04 01 00 00
Sense Key: 0x2 Not Ready, Segment 0
Sense Code: 0x04 Qual 0x01 (logical unit is in process of becoming ready) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 13.186s timeout 200s
./cdrecord: Input/output error. read buffer cap: scsi sendcmd: no error
CDB: 5C 00 00 00 00 00 00 00 0C 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 04 01 00 00
Sense Key: 0x2 Not Ready, Segment 0
Sense Code: 0x04 Qual 0x01 (logical unit is in process of becoming ready) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.004s timeout 200s
Writing pregap for track 1 at -150
write track pad data: error after 0 bytes
Starting new track at sector: 0
Track 01: 0 of 36 MB written../cdrecord: Input/output error. write_g1: scsi
sendcmd: no error
CDB: 2A 00 00 00 00 00 00 00 1B 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 04 01 00 00
Sense Key: 0x2 Not Ready, Segment 0
Sense Code: 0x04 Qual 0x01 (logical unit is in process of becoming ready) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.004s timeout 200s
Sense Bytes: 70 00 00 00 00 00 00 0A 00 00 00 00 00 00 00 00 00 00
write track data: error after 0 bytes
Writing time: 19.458s
Fixating...
./cdrecord: Input/output error. flush cache: scsi sendcmd: no error
CDB: 35 00 00 00 00 00 00 00 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 04 01 00 00
Sense Key: 0x2 Not Ready, Segment 0
Sense Code: 0x04 Qual 0x01 (logical unit is in process of becoming ready) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.020s timeout 200s
Trouble flushing the cache
Fixating time: 14.014s
./cdrecord: fifo had 64 puts and 1 gets.
./cdrecord: fifo was 0 times empty and 0 times full, min fill was 100%.
Alan
On Wed, 21 Mar 2001, Joerg Schilling wrote:
> HI,
>
> I again thougt on your problem and it is definitely the Redhat
> won't run SuSE syndrom.
>
> There is absolutely no binary compatibility on Linux. Don't ever
> expect a binary not compiled on your machine to run correctly.
>
> The obvious indicator for the problem in your case is that
> 'smake' believes that XARCH=3Di686-linux-cc is a _target_ name
> and not an option to set a make macro.
>
> This is caused by the fact that the libc on your system tells smake
> that '=' is a (upper/lowercase) character :-( and not a a punctuation
> character (which would be right).
>
> This is either caused by innocent people who don't know what a binary
> interface is and who think that they may put some personal flavor
> in the local libc binary ... or by some kind of war between different
> Linux distributions.
>
> Decide by your own what you like to believe.....
>
> I did not get the answer for this question.
>
> 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
>
--
Alan Bailey
awbailey @ uiuc.edu
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
