.. 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
On Mon, 26 Sep 2011, Craig Rodrigues wrote:
On Mon, Sep 26, 2011 at 8:30 PM, Garrett Cooper 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
On Mon, Sep 26, 2011 at 8:30 PM, Garrett Cooper 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 ke
On Mon, 26 Sep 2011, Craig Rodrigues wrote:
On Mon, Sep 26, 2011 at 6:58 PM, Doug Barton 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
On Mon, Sep 26, 2011 at 6:28 PM, Doug Barton 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
>> cdrec
On Mon, Sep 26, 2011 at 6:58 PM, Doug Barton 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
On 09/26/2011 18:43, Craig Rodrigues wrote:
> On Mon, Sep 26, 2011 at 6:28 PM, Doug Barton 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 rem
k, done. Eitan is right.
> 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 repla
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
h
Don't take my word for it, but I suppose burncd wasn't updated
for ahci support, and ahci driver is used by default in 9.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/9-0-and-burncd-error-tp4830395p4838303.html
Sent from the freebsd-questions mailing list
It seems that in 9.0 the cd/dvd/drive is now given a dev name of cd0
where in all previous releases it was acd0. Tried to use the burncd
command in 9.0 and get this error msg
burncd: ioctl(CDRIOCGETBLOCKSIZE): Inappropriate ioctl for device
Looks to me like maybe the burncd command needs to
, negative
ID numbers...
> Do you have any idea how 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
should do a kldload atapi
László
From: Dánielisz László
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 -
t scbus-1 target -1 lun -1 (xpt0)
Do you have any idea how can I avoid the recompilation?
From: Dánielisz László
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 th
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ó
To: freebsd-questions@freebsd.org
Sent: Tue, February 2,
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 15
On Sat, Aug 15, 2009 at 8:02 PM, b. f. 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 sysutils/cdrtools-devel rather
> 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 12:20 PM, Ruben de Groot 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 cdrecord
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
On Fri, 14 Aug 2009 18:47:48 -0600, Tim Judd 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 drive it
EGAL REQUEST asc=0x24 ascq=0x00
> acd0: FAILURE - MODE_SELECT_BIG ILLEGAL REQUEST asc=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
&g
d: Cannot blank 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
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 ma
On 6/9/09, Carmel 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. The
On Tue, 9 Jun 2009 16:31:10 -0400, Carmel 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:
>
> # burnc
On 6/9/09, Carmel 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
Carmel 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
>
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
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
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@fr
RW wrote:
On Sun, 7 Jun 2009 21:11:58 -0400 (EDT)
Chuck Bacon 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
On Sun, 7 Jun 2009 21:11:58 -0400 (EDT)
Chuck Bacon 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/creat
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
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 as
On Sun, 25 Jan 2009 17:23:35 +1000, Warren Liddell 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 /boot/kernel/atapicam.ko
o
> % 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
:-
s stays 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
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
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 larg
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
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&
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) t
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
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
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
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 w
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
>
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&#
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 at
ata0-master UDMA33
In 6.0-REL I was used to use 'burncd' to bring ISO images to
CD and this
> >> > 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
gt;>
>> > 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
>> > burn
--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
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 interru
--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 s
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-CU
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-
matter of seeing commands to do it and I'd 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
e use. Had the handbook's
example 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 &quo
d 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"
;
> "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
>
speed 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) h
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 ca
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 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
ll 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
I
[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'
if people read the FreeBSD handbook:
http://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 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, users used to smart unix c
t; FreeBSD says "unrecognizable"
> 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&
works for me, at
least for the ISOs I have made in the last couple 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
ows says "maybe disk 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]"
> > > > > > AMD64 running 6.0
> > > > > > Drive is:
> > > > > > acd0: DVDR at ata0-master UDMA66
> > > > > > Media is CD-RW
> > > > > >
> > > > > > Burned a 6.2 disk using:
> > &g
> > > > AMD64 running 6.0
> > > > Drive is:
> > > > acd0: DVDR at ata0-master UDMA66
> > > > Media is CD-RW
> > > >
> > > > Burned a 6.2 disk using:
> > > > burncd data 6.2-RELEASE-amd64-disc1.iso fixate
&
On Fri, 16 Mar 2007, Dieter wrote:
AMD64 running 6.0
Drive is:
acd0: DVDR 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
I don&#
> > AMD64 running 6.0
> > Drive is:
> > acd0: DVDR 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
On Thu, Mar 15, 2007 at 08:44:00PM -0700, Garrett Cooper wrote:
> Jerry McAllister wrote:
> >On Thu, Mar 15, 2007 at 01:06:10PM +0100, Dieter wrote:
> >
> >>AMD64 running 6.0
> >>Drive is:
> >> acd0: DVDR at ata0-master UDMA66
> >>Media is C
Jerry McAllister wrote:
On Thu, Mar 15, 2007 at 01:06:10PM +0100, Dieter wrote:
AMD64 running 6.0
Drive is:
acd0: DVDR 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
On Thu, Mar 15, 2007 at 01:06:10PM +0100, Dieter wrote:
> AMD64 running 6.0
> Drive is:
> acd0: DVDR 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.or
AMD64 running 6.0
Drive is:
acd0: DVDR 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. Disk boots, but I cannot
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"
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
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.
> >
> >
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
> > >
> > >
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
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 thi
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 - re
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 fixa
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
f
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 s
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
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 wai
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
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 flawles
tion now, since 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 f
D on an Ubuntu image:
# 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/ou
m 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 media.
> >
> > I've been trying to use cdrecord too, b
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 s
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 C
1 - 100 of 298 matches
Mail list logo
