patch to fix burncd bug
alexbestms at math.uni-muenster.de
Fri Jan 9 22:45:35 PST 2009
hmmm...that's odd because the only changes the patch makes deal with fixating
the cd. maybe you could try updating your sources to either 7-STABLE or
7.1-RELEASE, apply the patch and recompile your kernel. it might be a good
idea to also install a fresh version of burncd.
i just downloaded ata-queue.c and atapi-cd.c that shipped with 7.1-RELEASE and
the patch applies without any problems. so your revision of both files isn't
up to date.
please also keep in mind that this patch was made for 8-CURRENT. i don't think
it's been tested under 7 so far.
George Hartzell schrieb am 2009-01-10:
> Michael Proto writes:
> > On Thu, Jan 8, 2009 at 12:13 PM, Alexander Best <
> > alexbestms at math.uni-muenster.de> wrote:
> > > could somebody please commit the following patch to dev/ata? it
> > > fixes a
> > > nasty
> > > bug during fixation in burncd. the bug exists in RELENG6,
> > > RELENG7 and HEAD
> > > (and maybe RELENG5):
> > > http://www.freebsd.org/cgi/query-pr.cgi?prp=95979-3-txt&n=/patch
> > > the whole PR can be found here:
> > > http://www.freebsd.org/cgi/query-pr.cgi?pr=95979
> > I second this request. A fix would be nice, this bug has bitten me
> > in both
> > 7-STABLE and 8-CURRENT :)
> I have a mac pro running 7.1-PRERELEASE system (not sure when I last
> updated it) on which burncd seems to successfully burn the data but
> then fails while fixating.
> I applied the above patch by hand, with a little bit of fuzz, and now
> it fails to burn the data but fixating no longer bombs out. Here's a
> section of a script session (edited to remove the bulk of the written
> (delicious)[5:37pm]~>>sudo burncd -e data
> iso/7.0-RELEASE-amd64-livefs.iso fixate
> next writeable LBA 0
> writing from file iso/7.0-RELEASE-amd64-livefs.iso size 279174 KB
> written this track 32 KB (0%) total 32 KB
> written this track 64 KB (0%) total 64 KB
> written this track 1152 KB (0%) total 1152 KB
> Input/output error
> fixating CD, please wait..
> I think that I got the patch applied properly, I wonder if
> changed to obsolete it?
More information about the freebsd-current