Skip to main content.

2002-Apr-18

cdrecord doesn't work well any more. After modprobing ide-scsi and sg:

# cdrecord -v speed=1 dev=0,0,0 output.iso
Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 Jörg Schilling
TOC Type: 1 = CD-ROM
cdrecord: Invalid argument. Cannot get mmap for 4198400 Bytes on /dev/zero.
I read that if I use 2.4 kernel it will work. I also read that setting fs=0 will work, but I don't know if I should have no fifo (ring buffer). Also, supposedly if I build from source it will be fixed. (It is Debian cdrecord 1.10-2.4 package.)

It appeared to work using:

time cdrecord -v fs=0 speed=1 dev=0,0,0 output.iso 2>&1 | tee LOG
The logging:
scsidev: '0,0,0'
scsibus: 0 target: 0 lun: 0
Linux sg driver version: 2.1.34
Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 Jörg Schilling
TOC Type: 1 = CD-ROM
Using libscg version 'schily-0.5'
atapi: 1
Device type    : Removable CD-ROM
Version        : 0
Response Format: 1
Vendor_info    : 'PHILIPS '
Identifikation : 'PCRW804         '
Revision       : ' 2,1'
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      : 0 = 0 KB
Track 01: data  272 MB
Total size:     312 MB (30:57.90) = 139343 sectors
Lout start:     312 MB (30:59/68) = 139343 sectors
Current Secsize: 2048
ATIP info from disk:
Indicated writing power: 6
Is not unrestricted
Is not erasable
Disk sub type: Medium Type C, low Beta category (C-) (6)
ATIP start of lead in:  -11231 (97:32/19)
ATIP start of lead out: 359849 (79:59/74)
Disk type:    Short strategy type (Phthalocyanine or similar)
Manuf. index: 27
Manufacturer: Prodisc Technology Inc.
Blocks total: 359849 Blocks current: 359849 Blocks remaining: 220506
Starting to write CD/DVD at speed 2 in write mode for single session.
Last chance to quit, starting real write in 0 seconds. Operation starts.
Performing OPC...
Starting new track at sector: 0
Track 01: 272 of 272 MB written.
Track 01: Total bytes read/written: 285370368/285370368 (139341 sectors).
Writing  time: 1066.260s
Fixating...
cdrecord: Input/output error. close track/session: scsi sendcmd: no error
CDB:  5B 00 02 00 00 00 00 00 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 05 00 00 00 00 13 00 00 00 00 72 03 00 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x72 Qual 0x03 (session fixation error -
incomplete track in session) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.001s timeout 480s
cmd finished after 0.001s timeout 480s
Fixating time:    0.004s

real    17m55.665s
user    0m0.370s
sys     0m17.970s
Well the CD didn't work. I couldn't read it. I read that the "fixating time" was way to fast in a posting why CDRW worked but CDR didn't that had similar errors. In a Joerg Schilling README:
NOTE: Some operating systems have a read ahead bug that causes I/O errors for the last file(s) on a CD. This seems at least to be true for all Linux versions and for Solaris 7 FCS. For Solaris 7 there is a patch (107465-02) that you should install. This I/O error problem does not occur with DAO disks and with TAO disks that have been written with cdrecord -pad.
I used speed=1, but I think that defaults to 2. I will try speed=0. Also, maybe my problem is due to using Hi-Tech 16X multispeed, Silver, 80 minute, 700MB CDRs. I read that I should try -ignsize option. But the man page says "It is not needed to write disks with more than the nominal capacity."

I replaced the cdrecord package with: 1.10-7. The newer cdrecord worked without fs=0.

I tried a 74 minute, 650MB disk and it worked.

chrooted to my directory for building CD image. Tried to install icewm-gnome from smaug.fh-regensburg.de. This doesn't make sense:

Package `icewm-gnome-1.0.9.2nb1' depends on `tiff>=3.5.4'.
- tiff-3.5.7 already installed.
Later tried again (after installing other software) and it worked. I may have read error message wrong.

I mentioned to tech-pkg that pkg_add should have an option to save the ftp'd package to a non-tmp location. For example if it failed, then the PKG_PATH could point to it next time you try to install it. *I was told to provide patch.