Thanks to all who have helped me.
Sorry for answering to late but my service provider
for my private machine had problems this weekend.
The good news is that now I can burn my own CDs.
I have switched from cdrtools-1.10a11 to cdrtools-1.10a13
but I believe that the decisive hint came from Thomas
who suggested to try TAO mode instead of DAO mode.
On 26 Jan, [EMAIL PROTECTED] wrote:
>>From: [EMAIL PROTECTED]
>
>>recordable CDs are the only affordable backup medium for a Linux system
>>(at least for private use) - therefore it's a key technology for Linux.
>
> For Linux ????
Yes, since I see the (only) the two big competitors who are Linux and
Windows. Without such a key application as recording a CD and providing
a cheap backup medium Linux will have no chance.
>
> If I got you correctly, then it should read "a key technology for any OS"
>
>>I've been using Unix for over 10 years now and Linux for several years
>>at work where I have expensive DAT recorders for backup.
>
> Is this fact related to your problem?
Yes, it is. With more than 30 years experience with computers of
several kinds, teaching C++ and having no problems with assembler,
having written device drivers myself,
I wouldn't call myself a newbee. Nevertheless I haven't been able
to get cdrecord running. (Yes, I could have studied the sources)
>
>>Now for private use I am on my own since all seems to depend on a single
>>person (Joerg Schilling) who seems to dislike Linux very much.
>
> Why do you make this assumption?
I totally agree with Bill's reply.
> How is it related to your problem?
Yes, you're right, it's not my problem.
But it's a problem for all who like Linux to succeed.
>
>
>>On Linux I've read several HowTo and similar things, I've
>>reconfigured my 2.4.0 kernel until
>>cdrecord -scanbus recognizes my 2 CD drives.
>
> Sorry, you should blame e.g. Alan Cox for this problem.
> Linux still uses a default configuration that does not
> reflect current technology.
I don't blame anybody who a contributed to free software
and I'm grateful especially to Joerg for his software.
>
> ATAPI is SCSI over IDE transport. You only need to
> have one SCSI CD-ROm driver and a SCSI hostadaptor driver
> for the IDE interface. The argument that I mostly hear:
> "why do nwe need a full blown SCSI subsystem for a IDE only
> machine" goes away if you use loadable kernel modules.
I don't know the details, but I wonder why one couldn't use
the standard IDE driver and do all the other stuff by
suitable ioctl calls. If necessary one could try to
have the IDE driver support additional ioctl functions.
>
>>cdrecord is able to read the manufactor information on the
>>blank CD and it's able to eject the CD, so in principle
>>it could access the drive.
>
> So cdrecord works correctly.
Oh please! No blame, but if it were Windows we all
would call it working correctly if it produces a
usable CD in the end.
>
>>But then I get only a scsi error message.
>
>>Perhaps someone (other) can give me a hint where to
>>start to investigate the problem.
>
>>For those who can get some information out of cdrecord's
>>error log, I've appended it.
>
>>My drive seems to be (it has a sticker 'HP CD-Writer Plus')
>
>>Hewlett Packard LT9340 ???
>>Device type : Removable CD-ROM
>>Version : 0
>>Response Format: 1
>>Vendor_info : 'IDE-CD '
>>Identifikation : 'R/RW 4x4x32 '
>>Revision : '1.4B'
>
> It would be intesting to know who build this drive ;-)
>
>
>
>>Calling: /usr/local/bin/cdrecord dev=0,1,0 fs=4096k -v -useinfo speed=4 -dao -eject
>-pad -data "/BackUp/CD_Images/track-01.img" ...
>
>>scsidev: '0,1,0'
>>scsibus: 0 target: 1 lun: 0
>>Linux sg driver version: 3.1.17
>>pregap1: -1
>>Cdrecord 1.10a11 (i686-pc-linux-gnu) Copyright (C) 1995-2000 Jörg Schilling
>>TOC Type: 1 = CD-ROM
>>Using libscg version 'schily-0.4'
>>atapi: 1
>>Device type : Removable CD-ROM
>>Version : 0
>>Response Format: 1
>>Vendor_info : 'IDE-CD '
>>Identifikation : 'R/RW 4x4x32 '
>>Revision : '1.4B'
>>Device seems to be: Generic mmc CD-RW.
>>Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
>>Driver flags : SWABAUDIO
>>Drive buf size : 1572864 = 1536 KB
>>FIFO size : 4194304 = 4096 KB
>>Track 01: data 395 MB padsize: 30 KB
>>Total size: 453 MB (44:56.98) = 202274 sectors
>>Lout start: 454 MB (44:58/74) = 202274 sectors
>>Current Secsize: 2048
>>ATIP info from disk:
>>Indicated writing power: 5
>>Is not unrestricted
>>Is not erasable
>>ATIP start of lead in: -11080 (97:34/20)
>>ATIP start of lead out: 335100 (74:30/00)
>>Disk type: Long strategy type (Cyanine, AZO or similar)
>>Manuf. index: 11
>>Manufacturer: Mitsubishi Chemical Corporation
>>Blocks total: 335100 Blocks current: 335100 Blocks remaining: 132826
>>RBlocks total: 342460 RBlocks current: 342460 RBlocks remaining: 140186
>>Starting to write CD/DVD at speed 4 in write mode for single session.
>>Waiting for reader process to fill input buffer ...
>>cdrecord: Input/output error. mode select g1: scsi sendcmd: retryable error
>>CDB: 55 10 00 00 00 00 00 00 3C 00
>>status: 0x0 (GOOD STATUS)
>
> Well for this error there are several possible reasons.
>
> - Let me use this first so you can"t tell me again that I am against
> Linux (in fact I run Linux on my notebook).
>
> There may be HW or cabling problems.
This was unlikely since the drives works just fine with Windows
>
> - a bug in the SCSI subsystem of the kernel
>
> - binary incompatibility of cdrecord with the kernel.
Most unlikely since I compiled from the source without any
significant warnings
> Please always make sure that you compiled cdrecord on the
> machine you are using. A cdrecord binary compiled on a
> 3 month old Linux-2.4-xxx.yyyy.zzz would not run on a
> 4 month old linux-2.4-xxx.yyyy.zzz.
Done so from the beginning. (Latest cdrtools on latest stable kernel
on latest stable glibc (2.2.1) )
>
> One important note: with ATAPI there is in theory only one possible
> error condition which definitely sets the CHECK_CONDITION bit
> in the SCSI status. This is missing - find out, why cdrecord does not
> get it from the kernel.
>
>
>>cmd finished after 0.007s timeout 200s
>>cdrecord: Warning: using default CD write parameter data.
>>Mode Select Data 00 11 00 00 05 32 02 00 00 00 00 00 00 00 00 00 00 00 00 96 00 00
>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>00 00 00 00 00 00
>
> It looks that the mode page 05 that is send back by the drive is not correct.
> So it may even be rotten firmware.
>
> As the write type is "packet" it may also be a defective media.
Certainly it wasn't
>
> If you have problems with cdrecord you always should do some
> testst that make sure that your environment is not the reason for
> the observed problems....
I would appreciate having such a test tool.
Thanks again to all,
Helmut.
--
Helmut Jarausch
Lehrstuhl fuer Numerische Mathematik
Institute of Technology, RWTH Aachen
D 52056 Aachen, Germany
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
