On Tue, Oct 07, 2003 at 03:45:42PM +0700, Robert Elz wrote:
>     Date:        Tue, 7 Oct 2003 02:19:39 -0500
>     From:        Richard Rauch <rkr@olib.org>
>     Message-ID:  <20031007071939.GA21083@olib.org>
> 
>   | > cdrecord is not supposed to work with /dev/ entries;
> 
> That comment was utter nonsense - better would be to say that the author
> of cdrecord believes that relying on /dev/entries is bad for the health
> (he's wrong, but never mind) and prefers to make people go scan busses
> (assuming they somehow know enough about computer busses to know which
> to scan) find a set of meaningless numbers, and use those.
> 
>   | That's what cdrecord's docs say (or used to say?).  It has never been
>   | necessary for NetBSD in the past.
> 
> And isn't necessary now either.    What's more, if that was the problem
> you'd be having totally different symptoms.

That's what I figured, though I wasn't above grasping at straws in the middle
of the night, so I tried it.  It didn't change anything.



>   | I believe that that is only necessary with CD-RW media.
> 
> Yes, you can't use blank with CD-R.
> 
>   | The CD-R media doesn't show any sign of alteration.  Normally, after burning
>   | a CD, you can see the where some tracks have been burned, and the rest is
>   | still blank.
> 
> Does it look as if the drive is writing (write led lights, and all
> that) ?

Insofar as my faulty memory goes of the few disks that I've burned in the past:
Everything looks hunky dory.  The resulting disk when it's done, however, seems
unaltered and cannot be mounted by any drive.


>   | > Well, might be broken.
>   | Media or drive?
> 
> Could be either, but your descriptions are pointing at the drive.
> (where "broken" includes "all kinds of gunk around the laser").
> 
>   | I also tried putting in old CD-R media that has data on it (which
>   | the CD-RW drive won't recognize, but which I can mount in my CD or
>   | DVD drive).
> 
> That is not a good sign.

I didn't think that it was.  (^&


> 
>   | It looks like media can be ruled out.  The drive may be broken, dirty,
>   | or (remotely possibly) unhappy sitting at cd2 rather than cd1 or cd0.
> 
> As long as you have the correct device created for cd2, it will be fine
> (NetBSD only makes cd0 and cd1 because it is very rare for people to
> have more than 1, and sometimes 2, CD type drives - I also have 3 (the
> same as you do, CD, DVD, CDRW, on one system - on another I have 5
> (4 * CD, 1 * CDRW)).
> 
> The wrong device (just like using a bad dev= to cdrecord) would give
> different symptoms however.
> 
> What does cdrecord say when it is recording?   It tends to be quite
> verbose usually...

The header output says:

cdrecord -v speed=6 dev=/dev/cd1d output.iso
Cdrecord 2.00.3 (i386-unknown-netbsd1.6) Copyright (C) 1995-2002 Jörg Schilling
TOC Type: 1 = CD-ROM
scsidev: '/dev/cd1d'
devname: '/dev/cd1d'
scsibus: -2 target: -2 lun: -2
Using libscg version 'schily-0.7'
cdrecord: Warning: using inofficial libscg transport code version (frueauf-scsi-bsd.c-1.41nb1 '@(#)scsi-bsd.c   1.41 02/10/19 Copyright 1997 J. Schilling').
atapi: 0
Device type    : Removable CD-ROM
Version        : 2
Response Format: 2
Capabilities   : SYNC 
Vendor_info    : 'YAMAHA  '
Identifikation : 'CRW6416S        '
Revision       : '1.0c'
Device seems to be: Generic mmc CD-RW.
Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
Driver flags   : MMC SWABAUDIO 
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R96R
Drive buf size : 1566432 = 1529 KB
FIFO size      : 4194304 = 4096 KB
Track 01: data   264 MB        
Total size:      304 MB (30:08.88) = 135666 sectors
Lout start:      304 MB (30:10/66) = 135666 sectors
Current Secsize: 2048
ATIP info from disk:
  Indicated writing power: 5
  Is not unrestricted
  Is not erasable
  Disk sub type: Medium Type A, high Beta category (A+) (3)
  ATIP start of lead in:  -11634 (97:26/66)
  ATIP start of lead out: 359849 (79:59/74)
Disk type:    Short strategy type (Phthalocyanine or similar)
Manuf. index: 3
Manufacturer: CMC Magnetics Corporation
Blocks total: 359849 Blocks current: 359849 Blocks remaining: 224183
Starting to write CD/DVD at speed 6 in real TAO mode for single session.
Last chance to quit, starting real write    0 seconds. Operation starts.
Waiting for reader process to fill input buffer ... input buffer ready.
Performing OPC...
Starting new track at sector: 0
Track 01:  264 of  264 MB written (fifo 100%) [buf  99%]   6.6x.
Track 01: Total bytes read/written: 277839872/277839872 (135664 sectors).
Writing  time:  311.818s
Average write speed   6.3x.
Min drive buffer fill was 97%
Fixating...
Fixating time:   42.243s
cdrecord: fifo had 4523 puts and 4523 gets.
cdrecord: fifo was 0 times empty and 4435 times full, min fill was 92%.




(Hm.  "Identifikation"?  Can we guess the author's native language from
that line, alone?  (^&)

The resulting disk looks like it did before the burn, and is unusable
in my plain CD drive.



>   | I suspect that it may just be a bit of dust in there, but don't have
>   | the means to clean it at the moment.
> 
> That is what I'd suspect too - a drive with an openning (just not air tight,
> it doesn't need to be wide open - any CD counts) is going to accumulate
 [...]

I'll try getting a cleaning kit today before I give up on the drive altogether.


Thanks (and to the others who replied).



-- 
  "I probably don't know what I'm talking about."  http://www.olib.org/~rkr/