[no subject]

m> <20070615013215.GB28186@nickel.oss.ntelos.net>
From: Matthew Dillon <dillon@apollo.backplane.com>
Subject: Re: burncd error
Date: Thu, 14 Jun 2007 19:28:04 -0700 (PDT)
BestServHost: crater.dragonflybsd.org
List-Post: <mailto:bugs@crater.dragonflybsd.org>
List-Subscribe: <mailto:bugs-request@crater.dragonflybsd.org?body=subscribe>
List-Unsubscribe: <mailto:bugs-request@crater.dragonflybsd.org?body=unsubscribe>
List-Help: <mailto:bugs-request@crater.dragonflybsd.org?body=help>
List-Owner: <mailto:owner-bugs@crater.dragonflybsd.org>
Sender: bugs-errors@crater.dragonflybsd.org
Errors-To: bugs-errors@crater.dragonflybsd.org
Lines: 36
NNTP-Posting-Host: 216.240.41.25
X-Trace: 1181874591 crater_reader.dragonflybsd.org 793 216.240.41.25
Xref: crater_reader.dragonflybsd.org dragonfly.bugs:7126


:I never tried.  So many things on this laptop didn't work that burning
:CDs was pretty low on my list.  I did try playing a DVD with no
:success.
:
:Joe

    Ok.  I don't know if the problem is due to recent changes or if it's
    a long term issue.

    One last thing you could try is cdrecord.  cdrecord takes some getting
    used to because it uses the SCSI API and it is kinda messy.  Even though
    it is still talking to the same ATA device, there's a chance it might
    work where burncd doesn't.

    Get cdrecord from pkgsrc via sysutils/cdrtools-ossdvd

    It has a test mode also.  Basically it works something like this:

    cdrecord -scanbus

	Figure out what scsi device the ATA CD-Drive attached as.  That's
	the device you specify in the below commands.

    cdrecord dev=1,0,0 -checkdrive

	This will print out the drive information.  It may ring a bell with
	someone.

    cdrecord dev=1,0,0 speed=4 -v -dummy -sao ISOFILE

	This does a burn.  I think. (in dummy mode == test mode).

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>