Re: burncd input output error

[Andrew Sparrow]

On Sun, Sep 18, 2005 at 10:09:54AM +0200, Andreas Klemm wrote:
> I see this needs more investigation.  Maybe it has to deal with
> the exit status I had (!=0).
> 
> I will do a test burn now with burncd reading from a file
> instead from a pipe. Let's see if it behaves different then.
> 
> Hmm even if reading from a file I get this exit status 74.
> 
> [EMAIL PROTECTED] /export/isos burncd -v -s max data xxx.iso fixate
> adding type 0x08 file xxx.iso size 238792 KB 119396 blocks
> next writeable LBA 0
> addr = 0 size = 244523008 blocks = 119396
> writing from file xxx.iso size 238792 KB
> written this track 238792 KB (100%) total 238792 KB
> fixating CD, please wait..
> burncd: ioctl(CDRIOCFIXATE): Input/output error
> Exit 74

Have you tried cdrecord? You pretty much only need to add ATAPICAM
to the kernel, although If you don't already have SCSI support on
the machine, you'll need to add that (cd, scbus, pass) too, of
course. 

Even if you get the same error, it'll provide much more detailed
diagnostic information (maybe there's a flag to burncd to switch
that on?).

What brand of blank are you using? There's some really cheesy
generics - and some even worse Chinese pirates - around...

Also, if the drive's firmware mis-identifies the blank, this could
cause it to use a poor (or downright wrong) strategy for it, which
likely would cause you problems as well.

Handy to have some RWs around for testing like this, too.

Good luck!

AS

>   Andreas ///
> 
> -- 
> Andreas Klemm - Powered by FreeBSD 5.4
> Need a magic printfilter today ? -> http://www.apsfilter.org/
> ___
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd input output error

[Andrew Sparrow]

On Sat, Sep 17, 2005 at 12:42:39PM -0400, Chuck Swiger wrote:
> Andreas Klemm wrote:
> [ ... ]
> > - burncd leaves cdrom in a way that CD cannot be mounted
> >   after burning, one has to open and re-close CD tray manually
> >   before one is able to mount the frshly burned CD.
> 
> This is an issue with the drive firmware more than anything to do with 
> software.  Most drives won't re-read the disk's table-of-contents after 
> burning 
> an image to a blank, until you eject and reload the disk.

Ho, sorry, this is simply not true. Although I don't use burncd so
can't comment on it, I've been using cdrecord since FreeBSD 2.x
(1997-8, IIRC), on a wide variety of burners - none of which have
ever required me to eject/reload the disk to mount it, unless an
operation aborted/failed.  In which case the disk burnt was generally
a coaster anyway.

Even now, using cdrecord with ATAPICAM, this is never necesary on
my current burners (NED ND6500A, Plextor PX-712A).  I simply burn
and then mount immediately.

Regards,

AS
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: dvd+rw+r for FreeBSD

[Andrew Sparrow]

On Mon, Jun 16, 2003 at 01:31:50PM -0500, Thomas T. Veldhouse wrote:
> I believe you need this in your kernel at a bare minimum.  I don't know if
> atapicam is supported in FreeBSD 4.x.  It certainly is in 5.x.

Yup, MFC'd a long time ago now (6-8 months at a guess). 

Cheers,

AS

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"