link in handbook appears to be broken

Tue Jun 7 01:23:28 GMT 2005

On Monday 06 June 2005 02:58 pm, Ted Mittelstaedt wrote:
> Yes, use DAO.  But the software should know that since it's an ISO to
> do that automatically.  An ISO image on a multisession CD would be
> senseless, of course.  An ISO image needs to be written and the CD
> closed in a single session.
>
> Ted
>
> >-----Original Message-----
> >From: owner-freebsd-questions at freebsd.org
> >[mailto:owner-freebsd-questions at freebsd.org]On Behalf Of Steven
> >Friedrich
> >Sent: Monday, June 06, 2005 10:03 AM
> >To: Ted Mittelstaedt
> >Cc: freebsd-questions at freebsd.org
> >Subject: Re: link in handbook appears to be broken
> >
> >On Monday 06 June 2005 01:16 am, Ted Mittelstaedt wrote:
> >> >-----Original Message-----
> >> >From: owner-freebsd-questions at freebsd.org
> >> >[mailto:owner-freebsd-questions at freebsd.org]On Behalf Of Steven
> >> >Friedrich
> >> >Sent: Sunday, June 05, 2005 7:24 PM
> >> >To: Ted Mittelstaedt
> >> >Cc: freebsd-questions at freebsd.org
> >> >Subject: Re: link in handbook appears to be broken
> >> >
> >> >On Sunday 05 June 2005 06:48 pm, Ted Mittelstaedt wrote:
> >> >> >-----Original Message-----
> >> >> >From: owner-freebsd-questions at freebsd.org
> >> >> >[mailto:owner-freebsd-questions at freebsd.org]On Behalf Of Steven
> >> >> >Friedrich
> >> >> >Sent: Sunday, June 05, 2005 8:20 AM
> >> >> >To: Ted Mittelstaedt
> >> >> >Cc: freebsd-questions at freebsd.org
> >> >> >Subject: Re: link in handbook appears to be broken
> >> >> >
> >> >> >On Saturday 04 June 2005 01:04 am, Ted Mittelstaedt wrote:
> >> >> >> Hi Steven
> >> >> >>
> >> >> >>   Please don't waste time with this.  development of
> >> >
> >> >burncd is pretty
> >> >
> >> >> >> much
> >> >> >> dead.  Even the CD's on the list that it supported (of which
> >> >> >
> >> >> >I have one)
> >> >> >
> >> >> >> often didn't work right.  And all of them are old, no longer in
> >> >> >> production.
> >> >> >> burncd is there so if you have a burner sitting around
> >
> >you can plug
> >
> >> >> >> it in and see if it works.
> >> >> >>
> >> >> >>   These days most people use the ATAPI/CAM driver with IDE
> >> >> >
> >> >> >burners, see:
> >> >> >
> >> >> >
> >> >> >http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creati
> >> >> >ng-cds.ht
> >> >> >
> >> >> >> ml#ATAPICAM
> >> >> >>
> >> >> >> Ted
> >> >> >
> >> >> >Ok, but I'm getting nearly the same error with cdrecord.
> >> >> >
> >> >> >cdrecord -blank=all -eject dev=toshiba seemed to work ok.
> >> >> >cdrecord dev=toshiba cd1.iso didn't complain
> >> >> >but then mount /cdrom produced
> >> >> >acd0: READ_BIG - MEDIUM ERROR asc=0x15 ascq=0x00 error=0x00
> >> >> >
> >> >> >
> >> >> >Can someone tell me where to find the meanings of these codes?
> >> >>
> >> >> What you see is what you get - the error "MEDIUM ERROR"
> >
> >seems pretty
> >
> >> >> clear to me - it means that the CD you burned isn't readable.  What
> >> >> are you after - a masters thesis spewed out for every little error?
> >> >> That would bloat the code.
> >> >>
> >> >> FreeBSD tells you there's an error it's your job to find out why
> >> >> there is one.
> >> >>
> >> >> Since as you said in your other posting you are making good CD's at
> >> >> low-speed burn, and frizbees at high speed burn, there is a
> >> >
> >> >good chance
> >> >
> >> >> you
> >> >> are underrunning the buffer in the burner.  Get a faster CPU
> >> >
> >> >or live with
> >> >
> >> >> lower speed burns.
> >> >>
> >> >> UNIX is a preemptive operating system.  That means that
> >
> >during your CD
> >
> >> >> burn, if something else goes on in the system by some
> >
> >other process,
> >
> >> >> then your burning process gets paused.  If the burner you are
> >> >
> >> >using has
> >> >
> >> >> a very small internal buffer than it will run out of data
> >
> >and you will
> >
> >> >> produce a frisbee.
> >> >>
> >> >> WinXP by contrast lets apps like Roxio basically halt the OS while
> >> >> your doing some time-critical operation.  That's fine for a
> >> >
> >> >single-user
> >> >
> >> >> OS but pretty stupid for a server what has lots of people using it
> >> >> all the time.  That is why people don't use WinXP for servers.
> >> >>
> >> >> You cna try playing with the nice command and your cd
> >
> >burns and see if
> >
> >> >> you can make any difference.
> >> >>
> >> >> Ted
> >> >
> >> >My machines (2) are 2.4 GHz pentium 4s.
> >>
> >> OK, in that case chances it's a buffer underrun are much lower.
> >>
> >> >I use the same drive
> >> >and media under
> >> >winXP and using Roxio, I've burned freeBSD 4.11 ISOs and booted
> >> >from them.
> >> >The Memorex 1x-4x media worked with cdrecord but the Memorex
> >> >4x-12x media
> >> >doesn't, even when I tell it to burn at 4x like the 1x-4x media did.
> >> >
> >> >I'm not expecting the software to decode the asc, ascq, and
> >> >error codes, but I
> >> >do expect to find them documented in a header or a book, man
> >> >page, somewhere.
> >>
> >> They are documented, these guys have the docs:
> >>
> >> http://www.t13.org/
> >>
> >> You will have to pay them for them.   Or, go to the technical
> >
> >library of
> >
> >> your nearest university and make copies of the appropriate
> >
> >pages of the
> >
> >> standards.
> >>
> >> ASC = Associated Sense Code
> >> ASCQ = Associated Sense Code Qualifier
> >>
> >> These are codes returned to the driver by the CD reader,
> >
> >unexpectedly of
> >
> >> course,
> >> which is why it errored.  The software driver decoded enough
> >
> >to know that
> >
> >> the
> >> cd reader is reporting a medium error, so it tells you that,
> >
> >then passes
> >
> >> the
> >> sense code that the reader is returning.  You could look up the sense
> >> code
> >> in the documentation provided by the manufacturer of the cdrom reader
> >> drive
> >> if you really want to know, and I can almost guarentee you will get
> >> something
> >> nonsensical.
> >>
> >> Even if the FreeBSD driver decoded the ASC code, since the ASC code
> >> the drive is returning is garbage, it is useless for you.  Your
> >> getting caught up in minutae during the troubleshooting process rather
> >> than
> >> focusing on the basics.
> >>
> >> The basics are that your burner is producing frisbees.  Now, you know
> >> that the
> >> burner hardware is good under Windows, so that rules out mechanical
> >> trouble.
> >> You are running a multi-gigahertz CPU so that greatly reduces the
> >> possibility
> >> it is buffer underrun issues.  (but not rules them out)
> >> So instead it is likely a software problem.  What you don't know is if
> >> the software
> >> bug that is causing this is in the firmware of the CD reader, the
> >> firmware of
> >> the CD burner, or the FreeBSD device drivers.  The fact it works under
> >> Windows
> >> doesen't help because the Windows driver might have been written by
> >> someone
> >> who was aware of whatever firmware bug was present in your burner, and
> >> wrote
> >> around that.
> >>
> >> So the next step is trying to substitute a different vendor's
> >
> >burner in
> >
> >> the FreeBSD
> >> system.  If it gives you the same errors, the problem is most
> >
> >likely not
> >
> >> in the
> >> burner, and most likely in the software drivers.  With that done, you
> >> would
> >> have enough data to write a GOOD pr and submit it.  If the substitute
> >> works
> >> OK then you know it's firmware bugs in the burner you have, and a PR
> >> would not
> >> be warranted.
> >>
> >> Ted
> >
> >I've gotten newer firmware from Toshiba but it didn't help from
> >http://sdd.toshiba.com
> >
> >The asc, ascq codes are available at
>
> http://www.t10.org/lists/asc-num.htm
> In an attempt to determine if buffer underruns are the problem, I've used
> nice
> -18 (even -35) cdrecord...
>
> If I'm burning an iso image, do I need to use SAO (DAO) instead of TAO?
>
> --
> i386 FreeBSD 4.11-STABLE
> There are 10 types of people in this world. Ones that understand binary
> and
> then, the others.
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "freebsd-questions-unsubscribe at freebsd.org"
I have two physical systems and I have mobile racks in them.  I can pull out
freeBSD 4.11 and insert freeBSD 5.4.  I have discovered that I can write to 
the 4x-12x media when using freeBSD 5.4.  I don't even have to use DAO (SAO) 
mode, I can use TAO.

I have freeBSD 4.11 set up the same as 5.4 as far as I can.  I have atapicam, 
and the scsi bus and devices mentioned in the handbook.  cd0 is reported when 
I boot, but 4.11 doesn't have devfs, so it's not a usable device. But 
cdrecord is using dev=1,0,0 anyway.  After I write it with cdrecord, I try to 
mount it and I get an i/o error reported. When I use cdrecord blank=all, 
cdrecord reports errors indicating the media format is corrupt.  Perhaps the 
write operation didn't complete under 4.11 but it does under 5.4?

Anyway to determine what happened?
I don't believe that devfs is available under 4.11, but I really don't believe 
that's the culprit. Any ideas?

-- 
i386 FreeBSD 4.11-STABLE
There are 10 types of people in this world. Ones that understand binary and 
then, the others.