ead...@freebsd.org wrote:
Synopsis: 9.0 burncd error caused by change to cd0 from acd0
State-Changed-From-To: open-analyzed
State-Changed-By: eadler
State-Changed-When: Mon Sep 26 23:24:00 UTC 2011
State-Changed-Why:
requires only a release notes entry; use cdrecord instead of burncd
http
.
burncd has been part of the system utilities included in the basic
release since release 4.0 and cdrecord is a port. The professional
solution is to remove burncd from the 9.0 system release and add the
cdrecord command to the basic release as the replacement for burncd.
Then add release
On 09/26/2011 18:43, Craig Rodrigues wrote:
On Mon, Sep 26, 2011 at 6:28 PM, Doug Barton do...@freebsd.org wrote:
burncd has been part of the system utilities included in the basic
release since release 4.0 and cdrecord is a port. The professional
solution is to remove burncd from the 9.0
On Mon, Sep 26, 2011 at 6:58 PM, Doug Barton do...@freebsd.org wrote:
I have used burncd on many releases of FreeBSD, on many machines
without problem. I can see the fact that burncd suddenly failing to
work on ATAPI hardware could annoy and confused end-users.
It doesn't fail to work
On Mon, Sep 26, 2011 at 6:28 PM, Doug Barton do...@freebsd.org wrote:
burncd has been part of the system utilities included in the basic
release since release 4.0 and cdrecord is a port. The professional
solution is to remove burncd from the 9.0 system release and add the
cdrecord command
On Mon, 26 Sep 2011, Craig Rodrigues wrote:
On Mon, Sep 26, 2011 at 6:58 PM, Doug Barton do...@freebsd.org wrote:
I have used burncd on many releases of FreeBSD, on many machines
without problem. I can see the fact that burncd suddenly failing to
work on ATAPI hardware could annoy
On Mon, Sep 26, 2011 at 8:30 PM, Garrett Cooper yaneg...@gmail.com wrote:
...
Please fix it and move on.
Thanks,
-Garrett
$ usr.sbin/burncd/burncd -f /dev/cd0 blank
burncd: device provided not an acd(4) device: /dev/cd0.
Please verify that your kernel is built with acd(4
On Mon, 26 Sep 2011, Craig Rodrigues wrote:
On Mon, Sep 26, 2011 at 8:30 PM, Garrett Cooper yaneg...@gmail.com wrote:
...
Please fix it and move on.
Thanks,
-Garrett
$ usr.sbin/burncd/burncd -f /dev/cd0 blank
burncd: device provided not an acd(4) device: /dev/cd0.
Please verify
.. and if someone would like to contribute patches to burncd to update
it, I think there'd be at least one committer here who would be happy
to help you get your changes into the tree.
:-)
Adrian
___
freebsd-questions@freebsd.org mailing list
http
hi,
I found another problem :)
I'm using burncd about a while but today I have the following error while
trying to write a dvd:
burncd -f /dev/acd0 data pats-tt2.iso fixate
next writeable LBA 2352
writing from file pats-tt2.iso size 4579840 KB
written this track 1568 KB (0%) total 1568 KB
It looks like I'm to tired today :-)
I think installing dvd+rw-tools and cdrtools might fix the problem with
growisofs, but I still don't know why burncd is not working.
From: Dánielisz László laszlo_daniel...@yahoo.com
To: freebsd-questions@freebsd.org
Sent
lun -1 (xpt0)
Do you have any idea how can I avoid the recompilation?
From: Dánielisz László laszlo_daniel...@yahoo.com
To: freebsd-questions@freebsd.org
Sent: Tue, February 2, 2010 10:10:32 PM
Subject: Re: burncd issue
It looks like I'm to tired today :-)
I
László
From: Dánielisz László laszlo_daniel...@yahoo.com
To: freebsd-questions@freebsd.org
Sent: Tue, February 2, 2010 10:30:13 PM
Subject: Re: burncd issue
It looks that I should recompile my kernel for using growisofs
# growisofs -dvd-compat -speed=4 -Z /dev
can I avoid the recompilation?
Missing ATAPICAM.
Is it a CD or a DVD you're burning? If it's just a CD, how
about cdrecord (which I prefer to burncd for many years now)?
% cdrecord dev=2,0,0 speed=16 -v -eject -tao -data pats-tts2.iso
By the way, I have an alias for that because I'm
On Fri, Aug 14, 2009 at 08:23:49PM +0200, Fernando Apestegu?a typed:
Hi all,
I'm trying to get my CD drive to work without so much success.
Reading is fine, but when I try to burn a CD I get errors in dmesg.
Using cdrecord -blank=fast dev=3,0,0 I get:
[...]
Using generic SCSI-3/mmc
On Sat, Aug 15, 2009 at 12:20 PM, Ruben de Grootmai...@bzerk.org wrote:
On Fri, Aug 14, 2009 at 08:23:49PM +0200, Fernando Apestegu?a typed:
Hi all,
I'm trying to get my CD drive to work without so much success.
Reading is fine, but when I try to burn a CD I get errors in dmesg.
Using
I'm trying to get my CD drive to work without so much success.
Reading is fine, but when I try to burn a CD I get errors in dmesg.
Using cdrecord -blank=fast dev=3,0,0 I get:
First, I hope that you are using sysutils/cdrtools-devel rather than
sysutils/cdrtools. The latter is several years
On Sat, Aug 15, 2009 at 8:02 PM, b. f.bf1...@googlemail.com wrote:
I'm trying to get my CD drive to work without so much success.
Reading is fine, but when I try to burn a CD I get errors in dmesg.
Using cdrecord -blank=fast dev=3,0,0 I get:
First, I hope that you are using
disk, aborting.
cdrecord: Some drives do not support all blank types.
cdrecord: Try again with cdrecord blank=all.
And dmesg shows:
acd0: FAILURE - READ_BUFFER ILLEGAL REQUEST asc=0x24 ascq=0x00
acd0: FAILURE - MODE_SELECT_BIG ILLEGAL REQUEST asc=0x26 ascq=0x00
Using burncd blank I get:
burncd
=0x26 ascq=0x00
Using burncd blank I get:
burncd: ioctl(CDRIOCBLANK): Input/output error
and in dmesg:
acd0: FAILURE - BLANK_CMD ILLEGAL REQUEST asc=0x30 ascq=0x05
The drive works perfectly with other OS, so I don't think the hardware
is the problem.
The device is identified as:
acd0
On Fri, 14 Aug 2009 18:47:48 -0600, Tim Judd taj...@gmail.com wrote:
First thing I'd suspect is that your drive is a read-only, write-only,
but no rewrite, so that means it's unable to blank RW medium.
The 'DVDR' and CDDVDW both indicate a write once kind of mindset.
does the bezel on
the burncd: ioctl(CDRIOCFIXATE); Input/output error. is being caused by a
bug in ata-queue.c. the fix is in HEAD. here's the PR:
http://www.freebsd.org/cgi/query-pr.cgi?pr=95979 with a patch.
cheers.
___
freebsd-questions@freebsd.org mailing list
http
On Sunday 07 June 2009 20:40:44 David M. Patronis wrote:
I suspect, unlike cdrecord and
growisofs, that burncd is no longer a modern utility, and is in serious
need of an overhaul.
And sos@ retired :/
--
Mel
___
freebsd-questions@freebsd.org mailing
I just installed FreeBSD-7.2. I attempted to burn a CD; however,
when the burn completes, I receive this message:
burncd: ioctl(CDRIOCFIXATE); Input/output error.
This is the command line:
# burncd -ev -s max fixate data notes.txt
Now, if I do not use the 'fixate' command, no error message
burncd: ioctl(CDRIOCFIXATE); Input/output error.
This is the command line:
# burncd -ev -s max fixate data notes.txt
are notes.txt your CD image? at least should be multiple of 2kB, and
probably some minimal size. i don't know what is minimal track size but in
order of 100K
Carmel carmel...@hotmail.com writes:
I just installed FreeBSD-7.2. I attempted to burn a CD; however,
when the burn completes, I receive this message:
burncd: ioctl(CDRIOCFIXATE); Input/output error.
This is the command line:
# burncd -ev -s max fixate data notes.txt
Now, if I do
On 6/9/09, Carmel carmel...@hotmail.com wrote:
I just installed FreeBSD-7.2. I attempted to burn a CD; however,
when the burn completes, I receive this message:
burncd: ioctl(CDRIOCFIXATE); Input/output error.
This is the command line:
# burncd -ev -s max fixate data notes.txt
Now, if I
On Tue, 9 Jun 2009 16:31:10 -0400, Carmel carmel...@hotmail.com wrote:
I just installed FreeBSD-7.2. I attempted to burn a CD; however,
when the burn completes, I receive this message:
burncd: ioctl(CDRIOCFIXATE); Input/output error.
This is the command line:
# burncd -ev -s max fixate
On 6/9/09, Carmel carmel...@hotmail.com wrote:
I just installed FreeBSD-7.2. I attempted to burn a CD; however,
when the burn completes, I receive this message:
burncd: ioctl(CDRIOCFIXATE); Input/output error.
I have been getting that error message on and off for some time
(years) now
I have used burncd to burn both audio and data CDs, the latter almost
always a FreeBSD d{oc,isc{1,2,3}} ; but I was stopped for quite a
while when trying to burn the recent 7.2-RELEASE DVD iso. After losing
three DVD+R blanks to mistakes, I bought a DVD-R pack, and found I
could burn a DVD using
On Sun, 7 Jun 2009 21:11:58 -0400 (EDT)
Chuck Bacon c...@cape.com wrote:
Is there a better tool than burncd?
I've used burncd for CD's, but for DVDs I follow the handbook, and have
never had any problems:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-dvds.html
RW wrote:
On Sun, 7 Jun 2009 21:11:58 -0400 (EDT)
Chuck Bacon c...@cape.com wrote:
Is there a better tool than burncd?
I've used burncd for CD's, but for DVDs I follow the handbook, and have
never had any problems:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating
I'm using an Intel DG33BU board with a SATA HD and SATA optical drives.
Using FreeBSD 7.1 AMD64 I get a kernel panic and subsequent file system
corruption when attempting to burn a cd using the burncd utility. I can
avoid this easily enough by using cdrecord and growisofs which work
On Sun, 25 Jan 2009 17:23:35 +1000, Warren Liddell shin...@maydias.com wrote:
% camcontrol devlist
Typed this but no output what so ever, which presumably isnt a good thing.
If you have ATAPI devices, you need to have the ATAPICAM facility
loaded, either by
# kldload
I havee 2 burrners in my machine and not one off them will bburn a CD or
DVD from command line let alone trying to get k3b to recognise i even
have a scsi burner...
enterprise# burncd -e -v -s 16 -f /dev/acd0 data neroultraV7.iso fixate
adding type 0x08 file neroultraV7.iso size 620990 KB
in a constant state of spin and
the process refuses to die even after issuing the kill -9
I had similar problems, so I dropped burncd in favour of cdrecord
which I'm using for burning ISO data CDs.
What am i doing wrrong or what is wroong with my system to not allow me
to burn a cd//dvd
% camcontrol devlist
Typed this but no output what so ever, which presumably isnt a good thing.
and adjust the dev= parameter accordingly.
For a DVD, try
% growisofs -dvd-compat -Z /dev/dvd=neroultraV7.iso
enterprise# growisofs -dvd-compat -Z /dev/acd0=neroultraV7.iso
:-(
On Sun, 7 Sep 2008 11:16:46 +0800, FBSD1 [EMAIL PROTECTED] wrote:
Does burncd need a programming update to handle these newer larger sized
rw/cd's?
First, just check a few things:
1. Is the CD-RW media okay, not damaged?
2. Does the writer support this media?
3. Do you use the proper speed
FBSD1 wrote:
Been using burncd since Freebsd 4.0 with 650MB rw/cd's just fine. My local
computer store had a sale on 700MB rw/cd's and I picked up a few. Burncd
gives msg (Failure - read_big illegal request) on these 700MB rw/cd's. The
Freebsd 7.0 man burncd has no info on large sized rw/cd's
Been using burncd since Freebsd 4.0 with 650MB rw/cd's just fine. My local
computer store had a sale on 700MB rw/cd's and I picked up a few. Burncd
gives msg (Failure - read_big illegal request) on these 700MB rw/cd's. The
Freebsd 7.0 man burncd has no info on large sized rw/cd's?
Does burncd
Aloha,
Recently when I try to use burncd I get this error when trying to burn
any 8 CURRENT discs . I even got a new Burner and put it on a different
machine but still get this error.
Install fails from these burned discs.
Error message.
acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11
On Thu, 14 Aug 2008 08:21:11 -1000, Al Plant [EMAIL PROTECTED] wrote:
Install fails from these burned discs.
Error message.
acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11
Defective media?
/dev/acd0c used to work. Now you have to use /dev/acd0 (no c) to get
burncd to work.
As far
Hi,
Anybody able to write audio CDs with the current 7.0?
I have Pioneer DVDR-112D/1.21 drive.
Burncd breaks for a long while:
http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/118207
So I used cdrecord from cdrtools-2.01_6 which worked well.
Now command 'cdrecord -v -dao -force dev=1,0,0 speed
I recently installed FreeBSD 6.2 release and see there are two programs for
burning CDs: burncd and cdrtools (cdrecord). My CD-RW drive is ATAPI. I
looked through the online manpage for burncd and saw nothing comparable to
driveropts=burnfree, which I use in Linux with cdrecord. So how would I
El día Tuesday, May 29, 2007 a las 05:17:16PM -0400, Christopher Hilton
escribió:
Matthias Apitz wrote:
[ snip ]
In 6.2-REL I now get the error:
# burncd -f /dev/acd0 -s max data cdimage.raw fixate
next writeable LBA 0
This was discussed here a month or two or three ago. I
On Tue, May 29, 2007 at 05:17:16PM -0400, Christopher Hilton wrote:
Matthias Apitz wrote:
[ snip ]
In 6.2-REL I now get the error:
# burncd -f /dev/acd0 -s max data cdimage.raw fixate
next writeable LBA 0
This was discussed here a month or two or three ago. I believe
Hello,
I've updated over the weekend my laptop from 6.0-REL to 6.2-REL,
nothing has chaged in the hardware and the DVD drive was and is:
May 29 07:34:26 rebelion kernel: acd0: DVDR MATSHITAUJ-841Db/1.00 at
ata0-master UDMA33
In 6.0-REL I was used to use 'burncd' to bring ISO images to
CD
Matthias Apitz wrote:
[ snip ]
In 6.2-REL I now get the error:
# burncd -f /dev/acd0 -s max data cdimage.raw fixate
next writeable LBA 0
This was discussed here a month or two or three ago. I believe that the
problem was not with burncd but with the ide cd driver. I believe that
it's
but when I try to mount the cd later, I'm unable to do it and the
Input/Output error is thrown. Is there anything I'm missing? Is there
any other way to burn the cd other than using cdrecord.
There is something strange going on with burncd/cdrecord and mount.
http://lists.freebsd.org
Hi,
I was trying to burn cds using burncd. When I try to blank using
`burncd -f /dev/acd0 blank', it hangs forever until I interrupt.
And when I burn data in verbose mode it outputs message saying cd
burnt successfully:
addr = 0 size = 372736 blocks = 182
writing from file 7.0-CURRENT
--On Wednesday, May 23, 2007 22:36:06 +0530 sac [EMAIL PROTECTED] wrote:
Hi,
I was trying to burn cds using burncd. When I try to blank using
`burncd -f /dev/acd0 blank', it hangs forever until I interrupt.
And when I burn data in verbose mode it outputs message saying cd
burnt successfully
On 5/23/07, Paul Schmehl [EMAIL PROTECTED] wrote:
--On Wednesday, May 23, 2007 22:36:06 +0530 sac [EMAIL PROTECTED] wrote:
Hi,
I was trying to burn cds using burncd. When I try to blank using
`burncd -f /dev/acd0 blank', it hangs forever until I interrupt.
And when I burn data in verbose
--On Wednesday, May 23, 2007 23:09:57 +0530 sac [EMAIL PROTECTED] wrote:
On 5/23/07, Paul Schmehl [EMAIL PROTECTED] wrote:
--On Wednesday, May 23, 2007 22:36:06 +0530 sac [EMAIL PROTECTED] wrote:
Hi,
I was trying to burn cds using burncd. When I try to blank using
`burncd -f /dev/acd0
burncd. When I try to blank using
`burncd -f /dev/acd0 blank', it hangs forever until I interrupt.
And when I burn data in verbose mode it outputs message saying cd
burnt successfully:
addr = 0 size = 372736 blocks = 182
writing from file 7.0-CURRENT-200704-i386-disc2.iso size 364 KB
Is there anyway to burn a DVD+R with 'burncd' or any other software that
doesn't involve atapicam..?
DVD+RW works fine, except for that burncd wait forever to complete the format.
System:
FreeBSD 6.2-RELEASE #0: Fri Jan 12 10:40:27 UTC 2007
CPU: Intel Pentium III (598.06-MHz 686-class CPU)
real
worked fine,
except for a further odd problem on the DVD+RW laptop drive.
I've never tried -s, so I can't speak to that.
burncd data image.iso
works fine, but
burncd data image.iso fixate
causes an I/O error at the fixate stage - exactly as though the drive (or
utiliy, or OS) has memorised
as a single file to put on a CD to
prove the command works.
I then use
burncd -f /dev/acd0 data junk.tar fixate
and of course trying to
mount -t cd9660 /dev/acd0 /mnt
fails and the CD is also unreadable on windows.
Well duh. That is because THE FILE SYSTEM HAS TO BE CREATED MANUALLY.
Now
The stepwise process for burning CDs or DVDs
I created a junk file called junk.tar as a single file to put on a CD to
prove the command works.
I then use
burncd -f /dev/acd0 data junk.tar fixate
and of course trying to
mount -t cd9660 /dev/acd0 /mnt
fails and the CD is also
for burncd merely
had an example mkisofs command generating the input to be burnt with
burncd, I would have gotten it
right away. Others have pointed out that man burncd discusses ISOs,
but that material is on man page 2,
as it were - and in reading the description and arguments, I was gulled
take it from
there. In fact, I didn't go back and read the
documentation to find out what was wrong; I just took a look at the
cdrecord command doc and the mkisofs
example to create the source was there, and I said, oh, ran it for
burncd, voila. So the missing FAQ would
be sort
is blank.
Is burncd broken?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
of weeks. I
haven't gotten to making my CD backup of my web page yet.
The main thing I did was take out the '-s max' speed parameter and
came up with this which works:
/usr/sbin/burncd -v -f /dev/acd0 data FreeBSD62-disc1.iso fixate
It makes a both bootable and mountable CD.
Although I have used
and on windows says maybe disk is blank.
Care to show us the command you are using and what sort of file you
are writing? In any case, drop the hyphen before fixate.
Is burncd broken?
No, it isn't. I burn CDs with this command:
burncd -f /dev/acd0 data cd.iso fixate
--
Tore
need to do in the kernel if anything to support burning CDs/DVDs
What additional support libraries or software would be needed
The stepwise process for burning CDs or DVDs
I created a junk file called junk.tar as a single file to put on a CD to
prove the command works.
I then use
burncd -f /dev
://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-
cds.html
I created a junk file called junk.tar as a single file to put on
a CD to prove the command works.
I then use
burncd -f /dev/acd0 data junk.tar fixate
and of course trying to
mount -t cd9660 /dev/acd0 /mnt
fails and the CD is also
[Format recovered--see http://www.lemis.com/email/email-format.html]
Line length unified.
On Thursday, 22 March 2007 at 16:16:58 -0700, UCTC Sysadmin wrote:
In looking at the documentation for cdrecord, the examples showed
a two-step process of making an ISO image then burning it.
Here's my
the difference, both to novices and to professionals. Someone who
knows the how and what should
write a contributed thing - whenever they have the time and desire to
educate the unwashed masses.
man (8) burncd
In the examples above, the files burned to data CD-Rs are assumed to be
ISO9660 file systems
On Thu, 22 Mar 2007, UCTC Sysadmin wrote:
[snip]
mount -t cd9660 /dev/acd0 /mnt
fails and the CD is also unreadable on windows.
Well duh. That is because THE FILE SYSTEM HAS TO BE CREATED MANUALLY.
Now, users used to smart unix commands read the man page and it SAYS
of burncd
fixate
On Mar 22, 2007, at 6:16 PM, UCTC Sysadmin wrote:
[snip]
So THE FAQ and/or HOWTO SUCKS, is the problem. If that offends
purists, try fixing your transmission
under deadline with a japanese shop manual translated into english
and no diagrams. Documentation makes
all the difference, both to
On Thursday 22 March 2007 23:42, Jerry McAllister wrote:
On Thu, Mar 22, 2007 at 12:31:32PM -0700, UCTC Sysadmin wrote:
[broken CDs under burncd]
The main thing I did was take out the '-s max' speed parameter
Just as a further point of reference, I also found that -s max caused the
DVD+RW
AMD64 running 6.0
Drive is:
acd0: DVDR HL-DT-ST DVDRAM GSA-4160B/A301 at ata0-master UDMA66
Media is CD-RW
Burned a 6.2 disk using:
burncd data 6.2-RELEASE-amd64-disc1.iso fixate
as suggested in
http://www.freebsd.org/doc
:
burncd data 6.2-RELEASE-amd64-disc1.iso fixate
as suggested in
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html
I don't remember the details, but when I got to 6.1, I found that
my old burncd parameters would not work and I had to change them.
I don't remember
AMD64 running 6.0
Drive is:
acd0: DVDR HL-DT-ST DVDRAM GSA-4160B/A301 at ata0-master UDMA66
Media is CD-RW
Burned a 6.2 disk using:
burncd data 6.2-RELEASE-amd64-disc1.iso fixate
as suggested in
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html
On Fri, 16 Mar 2007, Dieter wrote:
AMD64 running 6.0
Drive is:
acd0: DVDR HL-DT-ST DVDRAM GSA-4160B/A301 at ata0-master UDMA66
Media is CD-RW
Burned a 6.2 disk using:
burncd data 6.2-RELEASE-amd64-disc1.iso fixate
as suggested in
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook
AMD64 running 6.0
Drive is:
acd0: DVDR HL-DT-ST DVDRAM GSA-4160B/A301 at ata0-master UDMA66
Media is CD-RW
Burned a 6.2 disk using:
burncd data 6.2-RELEASE-amd64-disc1.iso fixate
as suggested in
http://www.freebsd.org/doc/en_US.ISO8859-1/books
AMD64 running 6.0
Drive is:
acd0: DVDR HL-DT-ST DVDRAM GSA-4160B/A301 at ata0-master UDMA66
Media is CD-RW
Burned a 6.2 disk using:
burncd data 6.2-RELEASE-amd64-disc1.iso fixate
as suggested in
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html
Seemed to go okay
On Thu, Mar 15, 2007 at 01:06:10PM +0100, Dieter wrote:
AMD64 running 6.0
Drive is:
acd0: DVDR HL-DT-ST DVDRAM GSA-4160B/A301 at ata0-master UDMA66
Media is CD-RW
Burned a 6.2 disk using:
burncd data 6.2-RELEASE-amd64-disc1.iso fixate
as suggested in
http://www.freebsd.org/doc
Jerry McAllister wrote:
On Thu, Mar 15, 2007 at 01:06:10PM +0100, Dieter wrote:
AMD64 running 6.0
Drive is:
acd0: DVDR HL-DT-ST DVDRAM GSA-4160B/A301 at ata0-master UDMA66
Media is CD-RW
Burned a 6.2 disk using:
burncd data 6.2-RELEASE-amd64-disc1.iso fixate
as suggested in
http
Hi All,
I have read through release notes, etc and not seen anything, but I am
wondering if there have been any changes in recent FreeBSD releases -
especially 6.xx, (but possibly 5.xx), that would affect burncd(8) and how
it works - or if it works.
I have a machine that was at about 4.11
[EMAIL PROTECTED] [EMAIL PROTECTED] writes:
I tried to use burncd on my FreeBSD 6.1 system and it failed.
The command I typed is:
burncd -t -v -f /dev/acd0 ISO9660 file-name
and I got the error message no data format selected. I thought the
ISO9660 was the data format
Hello,
I get this error when I try to write (under root) a CD-RW or CD-R as
is found in handbook:
besa# burncd data FC-5-i386-disc1.iso fixate
burncd: ioctl(CDRIOCNEXTWRITEABLEADDR): Input/output error
Here are my (SMP) system details:
besa# uname -a
FreeBSD besa.org 6.1-STABLE FreeBSD 6.1
usable,
though. I switched to k3b for cd burning and have not seen that error since.
k3b uses dvd+rw-tools rather than burncd underneath. It's possible that they
would work better for the original poster too. It also sounds like the issue
with burncd is reproducible, anyone filed a PR
On 6/8/06, Pablo Mora [EMAIL PROTECTED] wrote:
On 6/7/06, Josh Paetzel [EMAIL PROTECTED] wrote:
On Wednesday 07 June 2006 14:46, you wrote:
On Wednesday 07 June 2006 11:04, Josh Paetzel wrote:
I'm running 6.1-RELEASE
Trying to burn iso's using burncd gives me an error.
gimpy
On 6/7/06, Josh Paetzel [EMAIL PROTECTED] wrote:
On Wednesday 07 June 2006 14:46, you wrote:
On Wednesday 07 June 2006 11:04, Josh Paetzel wrote:
I'm running 6.1-RELEASE
Trying to burn iso's using burncd gives me an error.
gimpy# burncd -f /dev/acd0 -s 48 data i386pkg-3.0.iso fixate
I'm running 6.1-RELEASE
Trying to burn iso's using burncd gives me an error.
gimpy# burncd -f /dev/acd0 -s 48 data i386pkg-3.0.iso fixate
next writeable LBA 0
writing from file i386pkg-3.0.iso size 710566 KB
written this track 710566 KB (100%) total 710566 KB
fixating CD, please wait..
burncd
I had the same kind of issue, also with 6.1-RELEASE, and just fixed it
the Windows way - reboot. And it worked fine.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail
On Wednesday 07 June 2006 11:04, Josh Paetzel wrote:
I'm running 6.1-RELEASE
Trying to burn iso's using burncd gives me an error.
gimpy# burncd -f /dev/acd0 -s 48 data i386pkg-3.0.iso fixate
next writeable LBA 0
writing from file i386pkg-3.0.iso size 710566 KB
written this track 710566 KB
Josh Paetzel wrote:
I'm running 6.1-RELEASE
Trying to burn iso's using burncd gives me an error.
gimpy# burncd -f /dev/acd0 -s 48 data i386pkg-3.0.iso fixate
next writeable LBA 0
writing from file i386pkg-3.0.iso size 710566 KB
written this track 710566 KB (100%) total 710566 KB
fixating CD
On Wednesday 07 June 2006 14:46, you wrote:
On Wednesday 07 June 2006 11:04, Josh Paetzel wrote:
I'm running 6.1-RELEASE
Trying to burn iso's using burncd gives me an error.
gimpy# burncd -f /dev/acd0 -s 48 data i386pkg-3.0.iso fixate
next writeable LBA 0
writing from file i386pkg
I got that error pretty routinely for a while. The cd-r was always usable,
though. I switched to k3b for cd burning and have not seen that error since.
On Wednesday 07 June 2006 10:44, Michael S wrote:
I had the same kind of issue, also with 6.1-RELEASE, and just fixed it
the Windows way -
Josh Paetzel wrote:
I'm running 6.1-RELEASE
Trying to burn iso's using burncd gives me an error.
gimpy# burncd -f /dev/acd0 -s 48 data i386pkg-3.0.iso fixate
next writeable LBA 0
writing from file i386pkg-3.0.iso size 710566 KB
written this track 710566 KB (100%) total 710566 KB
On 5/25/06, Lars Stokholm [EMAIL PROTECTED] wrote:
For testing purpose I'm trying to remake and burn the FreeBSD 6.1 CD
#1 iso image. I've put the CD in drive 0 (acd0) and:
[...]
Input/output error
Using the ATAPI/CAM driver and cdrecord (as described in the
handbook), seems to work
flawlessly. At least this proves that my
hardware is OK. Of course I prefer not adding this extra layer, so
don't hold back your suggestions. :)
Oops, I forgot to mention that burncd also doesn't work on my laptop.
It kinda makes it a little harder to accept
:
# burncd -s 16 -tvf /dev/acd1 data freebsd.iso fixate
adding type 0x08 file freebsd.iso size 517364 KB 258682 blocks
next writeable LBA 0
addr = 0 size = 529780736 blocks = 258682
writing from file freebsd.iso size 517364 KB
written this track 832 KB (0%) total 832 KB
Input/output error
I cannot
I've already wasted a CD on an Ubuntu image:
# burncd -s 16 -tvf /dev/acd1 data freebsd.iso fixate
Is that a typo or is your writer a different drive? Multiple drives on
an IDE cable seem to cause problems for some people.
adding type 0x08 file freebsd.iso size
tried to use burncd to record an audio CD but it seems to eat some
of my media space since it wasn't able to record a 62 minutes CD with
a 80 minutes media.
I've been trying to use cdrecord too, but since I can't discover how
to use de correct bus (look at the output of '#cdrecord -scanbus
Hi...
I used to be a debian user and I'm recently migrating to FreeBSD...
One thing that I am still having problems is with the cd recording.
I tried to use burncd to record an audio CD but it seems to eat some
of my media space since it wasn't able to record a 62 minutes CD with
a 80 minutes
El día Sunday, October 16, 2005 a las 03:03:56PM -0200, Frederico Franzosi
escribió:
Hi...
I used to be a debian user and I'm recently migrating to FreeBSD...
One thing that I am still having problems is with the cd recording.
I tried to use burncd to record an audio CD but it seems to eat
On 10/16/05, Frederico Franzosi [EMAIL PROTECTED] wrote:
Hi...
I used to be a debian user and I'm recently migrating to FreeBSD...
One thing that I am still having problems is with the cd recording.
I tried to use burncd to record an audio CD but it seems to eat some
of my media space since
dick hoogendijk [EMAIL PROTECTED] wrote:
One question still: you mention cdrtools-devel. What are the pro's/cons
of a devel port above the normal sysutils/cdrtools.
If you take cdrtools-devel, you get the latest version
(ATM cdrtools-2.01.01a03). The normal cdrtools port contains
the latest
1 - 100 of 275 matches
Mail list logo
