l i n u x - u s e r s - g r o u p - o f - d a v i s
Next Meeting:
July 7: Social gathering
Next Installfest:
Latest News:
Jun. 14: June LUGOD meeting cancelled
Page last updated:
2002 Nov 24 21:11

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
[vox-tech] CDR annoyance
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[vox-tech] CDR annoyance

Well, I'm trying to test CD-R writing under Melissa's Linux box
(it's a Mitsumi CR-2801TE), and with some "audio CD-R's" I had,
I was getting "cannot write - application code mismatch" from cdrecord,
although it looked like it was sucessfully doing _something_.

The discs were unmountable, though.

So, I went out and bought a set of TDK 74min, 650MB discs,
"for computer burning" (vs. just audio CD-Rs - I specifically AVOIDED
getting the 80min discs I saw at the store, in case this drive didn't
like them; I figured lowest common denominator).

When I even try to use "cdrecord" with the "-dummy" option, it immediately
quits out and yells:

  cdrecord: No disk / Wrong disk!

Specifically, the command is:

  # nice --10 cdrecord -v  -dummy speed=4 dev=1,0,0 tuxpaint.raw

and the full output is:

  Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 Jörg Schilling
  TOC Type: 1 = CD-ROM
  scsidev: '1,0,0'
  scsibus: 1 target: 0 lun: 0
  Linux sg driver version: 3.1.22
  Using libscg version 'schily-0.5'
  atapi: 1
  Device type    : Removable CD-ROM
  Version        : 0
  Response Format: 1
  Vendor_info    : 'MITSUMI '
  Identifikation : 'CR-2801TE       '
  Revision       : '1.10'
  Device seems to be: Philips CDD-522.
  Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
  Driver flags   : SWABAUDIO
  FIFO size      : 4194304 = 4096 KB
  Track 01: data    8 MB
  Total size:       9 MB (00:58.69) = 4402 sectors
  Lout start:      10 MB (01:00/52) = 4402 sectors
  cdrecord: Input/output error. test unit ready: scsi sendcmd: no error
  CDB:  00 00 00 00 00 00
  status: 0x2 (CHECK CONDITION)
  Sense Bytes: 70 00 02 00 00 00 00 06 00 00 00 00 3A 01
  Sense Key: 0x2 Not Ready, Segment 0
  Sense Code: 0x3A Qual 0x01 (medium not present - tray closed) Fru 0x0
  Sense flags: Blk 0 (not valid)
  cmd finished after 0.001s timeout 40s
  cdrecord: No disk / Wrong disk!

Any ideas?  Did I just pick up discs that won't work?

Doing some Googling, for the "No disk / Wrong disk" message, I noticed
one person who said their drive burns just fine, unless the machine's
been on for a while.  Then it complains.  If they reboot, it becomes happy
again.  (I didn't notice if they mentioned what particular brand of drive
it was.)

Of course, most often people's suggestions are "try a different brand of disc."

Goddamn.  CD burning is irritating, isn't it!? >:^(

i've got some nice, shiny gold coasters for sale :^)  never used!
vox-tech mailing list

LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
EDGE Tech Corp.
For donating some give-aways for our meetings.