is fine using:
ns1% sudo burncd -f /dev/acd0 data FreeBSD-9.0-CURRENT-201001-ia64-bootonly.iso
Fixating the CD is causing the hard hang:
ns1% sudo burncd -f /dev/acd0 fixate
fixating CD, please wait..
*hard hang*
There's nothing in the console and interrupts are all
masked. A power-cycle is the only
SATA
3Gb/s
ad4: 476940MB MAXTOR STM3500630AS 3.AAE at ata12-master UDMA100 SATA
1.5Gb/s
:
Writing an image is fine using:
ns1% sudo burncd -f /dev/acd0 data
FreeBSD-9.0-CURRENT-201001-ia64-bootonly.iso
Fixating the CD is causing the hard hang:
ns1% sudo burncd -f /dev/acd0 fixate
On Mon, May 26, 2008 at 1:21 AM, Carlos A. M. dos Santos
[EMAIL PROTECTED] wrote:
On Mon, May 19, 2008 at 9:27 AM, Carlos A. M. dos Santos
[EMAIL PROTECTED] wrote:
On Sat, May 17, 2008 at 4:28 PM, Volker [EMAIL PROTECTED] wrote:
Carlos,
IMHO it's better to explicitly check for ioctl
Hello,
I get burncd: ioctl(CDIOCEJECT): Input/output error each time I
attempt to blank a CDRW with
burncd -f /dev/acd0 blank eject
I noticed that this does not happen when I write a data cd with
burncd -f /dev/acd0 data cd-image.iso fixate eject
I have seen the same bahavior on 4
I have cd/dwd writer on my laptop:
acd0: DVDR PIONEER DVDRW DVR-K17/1.05 at ata0-master PIO4
Writer work properly on 7.0-BETA1 #15: Tue Oct 30 13:21:42 EET 2007 ,
but after today upgrade to 7.0-BETA2 #16: Wed Nov 14 15:41:44 EET 2007
kernel panics during run burncd -es 8 data file.iso fixate (i
Peter Jeremy wrote:
On Mon, 2006-Dec-25 16:55:54 +0100, O. Hartmann wrote:
burncd had some nice advantages over cdrecord: it came from the BSD
tree, it had capabilities for burning DVD+RW images. Disadvantage was
the limitation to ATA interface.
I see the latter as a disadvantage
On Fri, Dec 29, 2006 at 12:15:37AM -0700, Scott Long wrote:
Did you know that ATAPI is actually just the SCSI command set that is
merely encapsulated into the IDE wire protocol?
This is something Linux has done (you can still use the direct ATA
and IDE subsystems if you want, but in most major
On Fri, 29 Dec 2006, Jeremy Chadwick wrote:
On Fri, Dec 29, 2006 at 12:15:37AM -0700, Scott Long wrote:
Did you know that ATAPI is actually just the SCSI command set that is
merely encapsulated into the IDE wire protocol?
This is something Linux has done (you can still use the direct ATA
and
On Mon, 2006-Dec-25 16:55:54 +0100, O. Hartmann wrote:
burncd had some nice advantages over cdrecord: it came from the BSD
tree, it had capabilities for burning DVD+RW images. Disadvantage was
the limitation to ATA interface.
I see the latter as a disadvantage of cdrecord: It only works on SCSI
On Fri, Dec 29, 2006 at 09:23:06AM +1100, Peter Jeremy wrote..
On Mon, 2006-Dec-25 16:55:54 +0100, O. Hartmann wrote:
burncd had some nice advantages over cdrecord: it came from the BSD
tree, it had capabilities for burning DVD+RW images. Disadvantage was
the limitation to ATA interface.
I
part of these
changes seems to be effectively NOOP with my TEAC's drive
acd0: CDRW CD-W540E/1.0C at ata1-master UDMA33
But burncd.c patch definitely works! It's output is somehow ugly:
[EMAIL PROTECTED] burncd -f /dev/acd0 -s 10 blank
blanking CD - 17sec 0 % done -1(interim status
summary: there was some discussion on how to
fix the problem, in 6.x, with burncd -f /dev/acd0 -v blank getting
stuck with this message
blanking CD, please wait..
This used to work on 4.x.
6.x changes in two places:
* the ioctl handler, acd_get_progress() in /sys/dev/ata/atapi-cd.c
Luigi Rizzo [EMAIL PROTECTED] writes:
summary: there was some discussion on how to
fix the problem, in 6.x, with burncd -f /dev/acd0 -v blank getting
stuck with this message
blanking CD, please wait..
This used to work on 4.x.
[ .. stuff deleted .. ]
Patches below
Luigi Rizzo wrote:
summary: there was some discussion on how to
fix the problem, in 6.x, with burncd -f /dev/acd0 -v blank getting
stuck with this message
blanking CD, please wait..
This used to work on 4.x.
6.x changes in two places:
* the ioctl handler, acd_get_progress() in /sys
On Wed, Dec 27, 2006 at 02:33:15AM +0100, Søren Schmidt wrote:
Luigi Rizzo wrote:
summary: there was some discussion on how to
fix the problem, in 6.x, with burncd -f /dev/acd0 -v blank getting
stuck with this message
blanking CD, please wait..
This used to work on 4.x.
6.x
Hello!
On Fri, 22 Dec 2006, Sergey N. Voronkov wrote:
just noticed, after upgrading to 6.2RC1, that
luigi# burncd -f /dev/acd0 -v blank
blanking CD, please wait..
stays there forever. Eventually i gave up and ctrl-C and
the application terminates, and i was able to write
Dmitry Pryanishnikov wrote:
Hello!
On Fri, 22 Dec 2006, Sergey N. Voronkov wrote:
just noticed, after upgrading to 6.2RC1, that
luigi# burncd -f /dev/acd0 -v blank
blanking CD, please wait..
stays there forever. Eventually i gave up and ctrl-C and
the application terminates
On Mon, Dec 25, 2006 at 05:12:04PM +0200, Dmitry Pryanishnikov wrote:
Hello!
On Fri, 22 Dec 2006, Sergey N. Voronkov wrote:
just noticed, after upgrading to 6.2RC1, that
luigi# burncd -f /dev/acd0 -v blank
blanking CD, please wait..
stays there forever. Eventually i gave up
On Mon, Dec 25, 2006 at 04:55:54PM +0100, O. Hartmann wrote:
Since this is a very old and well known issue, and it seems there is no
one left solcing/developing this tool, it should be removed from the
source tree for the time it is to said broken.
burncd had some nice advantages over
Luigi Rizzo wrote:
On Mon, Dec 25, 2006 at 05:12:04PM +0200, Dmitry Pryanishnikov wrote:
Hello!
On Fri, 22 Dec 2006, Sergey N. Voronkov wrote:
just noticed, after upgrading to 6.2RC1, that
luigi# burncd -f /dev/acd0 -v blank
blanking CD, please wait..
stays there forever
O. Hartmann wrote:
Dmitry Pryanishnikov wrote:
Hello!
On Fri, 22 Dec 2006, Sergey N. Voronkov wrote:
just noticed, after upgrading to 6.2RC1, that
luigi# burncd -f /dev/acd0 -v blank
blanking CD, please wait..
stays there forever. Eventually i gave up and ctrl-C and
the application
On Mon, Dec 25, 2006 at 12:00:41PM -0500, Scott Long wrote..
O. Hartmann wrote:
Dmitry Pryanishnikov wrote:
Hello!
On Fri, 22 Dec 2006, Sergey N. Voronkov wrote:
just noticed, after upgrading to 6.2RC1, that
luigi# burncd -f /dev/acd0 -v blank
blanking CD, please wait..
stays
Hello!
On Mon, 25 Dec 2006, Scott Long wrote:
P.S.: Don't use burncd. Use cdrecord!
IMHO it isn't correct approach to avoid use of the tool _instead_ of
fixing
it. This way, all your tools will be broken one day ;)
Sincerely, Dmitry
Since this is a very old and well known issue
Dmitry Pryanishnikov wrote:
1) it seems that problem is in /sys/dev/ata/atapi-cd.c code rather then
in burncd utility (but I'm not 100%-sure here);
2) burncd still does _all_ things which it's useful for: it really burns CDs
erases and fixates them. It just incorrectly waits
just noticed, after upgrading to 6.2RC1, that
luigi# burncd -f /dev/acd0 -v blank
blanking CD, please wait..
stays there forever. Eventually i gave up and ctrl-C and
the application terminates, and i was able to write to
the disk a valid image, which probably means that the
disk
On Thu, Dec 21, 2006 at 09:27:17AM -0800, Luigi Rizzo wrote:
just noticed, after upgrading to 6.2RC1, that
luigi# burncd -f /dev/acd0 -v blank
blanking CD, please wait..
stays there forever. Eventually i gave up and ctrl-C and
the application terminates, and i was able
Sorry to have to bring this up again, seems like it was an issue 4 years
ago, but I don't know if it's really resolved.
If I do:
#burncd -f /dev/acd0 blank
then burncd will sleep forever.
(I have to Ctrl-C for it to exit)
It doesn't really hang, but please read this:
http://www.freebsd.org/cgi
On Sat, 15 Jul 2006, B Briggs wrote:
Sorry to have to bring this up again, seems like it was an issue 4
years ago, but I don't know if it's really resolved.
If I do:
#burncd -f /dev/acd0 blank
then burncd will sleep forever.
(I have to Ctrl-C for it to exit)
It doesn't really hang, but please
Michael A. Koerber [EMAIL PROTECTED] [2006.05.16] wrote:
1. Starting with a known good audio CD
2. Rip via dd if=/dev/acd0t01 ... etc
3. burncd -f /dev/acd0 track01.cdr ... etc
I've also used this, but have some problems: there is sometimes a
blank section in before the tracks
Par Leijonhufvud wrote:
Michael A. Koerber [EMAIL PROTECTED] [2006.05.16] wrote:
1. Starting with a known good audio CD
2. Rip via dd if=/dev/acd0t01 ... etc
3. burncd -f /dev/acd0 track01.cdr ... etc
This might be because you don't use the appropriate blocksize. A more
secure
[LoN]Kamikaze wrote:
Par Leijonhufvud wrote:
Michael A. Koerber [EMAIL PROTECTED] [2006.05.16] wrote:
1. Starting with a known good audio CD
2. Rip via dd if=/dev/acd0t01 ... etc
3. burncd -f /dev/acd0 track01.cdr ... etc
This might be because you don't use the appropriate
All,
Thanks for the responses. Based on your input I did find that,
following the handbook,
1. Starting with a known good audio CD
2. Rip via dd if=/dev/acd0t01 ... etc
3. burncd -f /dev/acd0 track01.cdr ... etc
worked just fine.
Thus the MP3 to CDR conversion had to be the cause
My method has always been to use cdrecord with atapicam. cdrecord will
accept .wav files and do the right thing on its own.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any
All,
Once upon a time, I think with 5.x or perhaps earlier, the command
(ATAPI drive)
burncd -ef /dev/acd0 audio *.cdr fixate
would produce an audio CD for me. However, under 6.0 and recently 6.1
this same command produces an CD filled with white noise only. The entire
procedure I've
On Mon, May 15, 2006 at 08:00:48AM -0400, Michael A. Koerber wrote:
Any ideas on what I should look at to fix this problem?
What kind of CPU are you using? Perhaps this is an endianness issue,
and swapping bytes around using the -x option to sox might do the
trick.
-Albert
Michael A. Koerber wrote:
All,
Once upon a time, I think with 5.x or perhaps earlier, the command
(ATAPI drive)
burncd -ef /dev/acd0 audio *.cdr fixate
would produce an audio CD for me. However, under 6.0 and recently 6.1
this same command produces an CD filled with white noise only
On Tue, May 16, 2006 4:55 am, Stephen Hurd wrote:
Michael A. Koerber wrote:
All,
Once upon a time, I think with 5.x or perhaps earlier, the command
(ATAPI drive)
burncd -ef /dev/acd0 audio *.cdr fixate
would produce an audio CD for me. However, under 6.0 and recently 6.1
this same
system that did
the conversion, it should Just Work. iirc, the CDA format uses the
hosts byte order so burncd (or morelikely, the device) would need to use
swab() when burning on BE systems.
Definitely something for Michael to try is following the steps outlined
in the handbook for copying a CD
Hi!
On Wed, Mar 15, 2006 at 04:27:13PM -0500, Scott Robbins wrote:
On Wed, Mar 15, 2006 at 12:51:50PM -0800, David Wolfskill wrote:
I'm running:
I just tried it again, using a different brand of media, and also got:
localhost(6.1-P)[22] sudo burncd -s max -f /dev/acd0 data
6.1
3. Re: help ith burncd (Input/output error, 6.1-RC, plextor
PX-740a) (George Hartzell)
5. Re: help ith burncd (Input/output error, 6.1-RC, plextor
PX-740a) (George Hartzell)
--
Message: 3
Date: Wed, 12 Apr 2006 09:13:03 -0700
From: George
Hi,
Anyone else experiencing burncd failures on RC-1? I've only just recently
cvsup'd and rebuilt, and now burncd(8) just does nothing:
osiris-~,1:29pm# echo $CDROM
/dev/acd0
osiris-~,1:26pm# burncd -v blank
blanking CD, please wait..
No progress messages at all.
atapicam.ko
On Fri, Apr 14, 2006 at 01:32:38PM +1200, Jonathan Chen wrote:
Hi,
Anyone else experiencing burncd failures on RC-1? I've only just recently
cvsup'd and rebuilt, and now burncd(8) just does nothing:
osiris-~,1:29pm# echo $CDROM
/dev/acd0
osiris-~,1:26pm# burncd -v blank
Hartzell wrote:
I have a new system which includes a Plextor PX-740a DVD+-R/RW CD-R/RW
drive attached to an Asus A8V-MX motherboard.
When I try to use burncd to burn a cd, it writes all of the data, says
fixating CD, please wait.. and then reports
burncd: ioctl(CDRIOCFIXATE): Input/output error
On Tue, Apr 11, 2006 at 06:49:02PM -0700, George Hartzell wrote:
When I try to use burncd to burn a cd, it writes all of the data, says
fixating CD, please wait.. and then reports
burncd: ioctl(CDRIOCFIXATE): Input/output error
Oddly enough, the CD seems to be usable.
I can
Igor Robul writes:
On Tue, Apr 11, 2006 at 06:49:02PM -0700, George Hartzell wrote:
When I try to use burncd to burn a cd, it writes all of the data, says
fixating CD, please wait.. and then reports
burncd: ioctl(CDRIOCFIXATE): Input/output error
Oddly enough, the CD seems
to understand if I have a fixable problem, or burncd
has a fixable problem, or if it's just the way that things are.
g.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail
On Wed, Apr 12, 2006 at 09:13:03AM -0700, George Hartzell wrote:
Igor Robul writes:
On same CD-R disc? :-)
No, on a fresh disk... ;)
So, I think you got my point: there maybe problem with disk.
I guess my question is: Is this one of those known things that
everyone just ignores, or do I
I have a new system which includes a Plextor PX-740a DVD+-R/RW CD-R/RW
drive attached to an Asus A8V-MX motherboard.
When I try to use burncd to burn a cd, it writes all of the data, says
fixating CD, please wait.. and then reports
burncd: ioctl(CDRIOCFIXATE): Input/output error
Oddly enough
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Apr 11, 2006 at 06:49:02PM -0700, George Hartzell wrote:
I have a new system which includes a Plextor PX-740a DVD+-R/RW CD-R/RW
drive attached to an Asus A8V-MX motherboard.
When I try to use burncd to burn a cd, it writes all
On Tue, 11 Apr 2006, George Hartzell wrote:
I have a new system which includes a Plextor PX-740a DVD+-R/RW CD-R/RW
drive attached to an Asus A8V-MX motherboard.
When I try to use burncd to burn a cd, it writes all of the data, says
fixating CD, please wait.. and then reports
burncd: ioctl
] sudo burncd -s max -f /dev/acd0 data
6.1-BETA4-i386-disc1.iso fixate
next writeable LBA 0
writing from file 6.1-BETA4-i386-disc1.iso size 454082 KB
written this track 454082 KB (100%) total 454082 KB
fixating CD, please wait..
burncd: ioctl(CDRIOCFIXATE): Input/output error
localhost(6.1-P)[16
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Mar 15, 2006 at 12:51:50PM -0800, David Wolfskill wrote:
I'm running:
I just tried it again, using a different brand of media, and also got:
localhost(6.1-P)[22] sudo burncd -s max -f /dev/acd0 data
6.1-BETA4-i386-disc1.iso fixate
) = aee3a4416eec24b1795346efeb624416
localhost(6.1-P)[15] sudo burncd -s max -f /dev/acd0 data
6.1-BETA4-i386-disc1.iso fixate
next writeable LBA 0
writing from file 6.1-BETA4-i386-disc1.iso size 454082 KB
written this track 454082 KB (100%) total 454082 KB
fixating CD, please wait..
burncd: ioctl(CDRIOCFIXATE): Input/output
On Wed, Mar 15, 2006 at 04:27:13PM -0500, Scott Robbins wrote:
...
In my case, the CD burns without problem however, I get that error.
Googling found me a few other people with a similar issue. Have you
tried the CD afterwords to see if it works anyway?
Well, as I showed in my original
Hello!
On Wed, 15 Mar 2006, Scott Robbins wrote:
fixating CD, please wait..
burncd: ioctl(CDRIOCFIXATE): Input/output error
localhost(6.1-P)[23]
There was a fair amount of time -- around 15 - 20 seconds -- between the
fixating CD, please wait.. message and the whine, during which
I was and am a great fan of the burncd utility.
Very fast, simple and cli..
But as almost any new computer is supplied with a dvd drive this nice
program has become quit useless. It does not support those drives.
My question is: will it ever do?
I mean, cd-rom drives are losing terrain
fan of the burncd utility.
Very fast, simple and cli..
But as almost any new computer is supplied with a dvd drive this nice
program has become quit useless. It does not support those drives.
My question is: will it ever do?
I mean, cd-rom drives are losing terrain with each day passed.
Or will I
On Fri, Nov 04, 2005 at 09:18:31AM +0100, Dick Hoogendijk wrote:
I was and am a great fan of the burncd utility.
Very fast, simple and cli..
Cdrecord is also a cli program. And you probably have it installed,
because mkisofs is in the same port. :-) It does need atapicam, though
On Friday 04 November 2005 00:18, you wrote:
I was and am a great fan of the burncd utility.
Very fast, simple and cli..
But as almost any new computer is supplied with a dvd drive this nice
program has become quit useless. It does not support those drives.
My question is: will it ever do
Dick Hoogendijk wrote:
I was and am a great fan of the burncd utility.
Very fast, simple and cli..
But as almost any new computer is supplied with a dvd drive this nice
program has become quit useless. It does not support those drives.
My question is: will it ever do?
I mean, cd-rom drives
On Friday, 4. November 2005 09:18, Dick Hoogendijk wrote:
I was and am a great fan of the burncd utility.
Very fast, simple and cli..
But as almost any new computer is supplied with a dvd drive this nice
program has become quit useless. It does not support those drives.
My question
On Fri, 4 Nov 2005 18:48, Dick Hoogendijk wrote:
But as almost any new computer is supplied with a dvd drive this nice
program has become quit useless. It does not support those drives.
My question is: will it ever do?
It does support DVD's, but in my experience it is a bit buggy so I
On Sat, Sep 17, 2005 at 08:30:33PM -0700, Andrew Sparrow wrote:
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
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
2 problems with FreeBSD 5.4 stable:
- burncd has strange exit status when reading ISO file from stdin
according to manual page possible:
[...]
gunzip -c file.iso.gz | burncd -f /dev/acd0 data - fixate
[...]
- burncd leaves cdrom in a way that CD cannot be mounted
after burning, one
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Sep 17, 2005 at 03:03:44PM +0200, Andreas Klemm wrote:
2 problems with FreeBSD 5.4 stable:
- burncd has strange exit status when reading ISO file from stdin
according to manual page possible:
[...]
gunzip -c file.iso.gz
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
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
: DVDR PIONEER DVD-RW DVR-107D/1.16 at ata1-master UDMA33
# uname -a
FreeBSD gridlinked.neverness.org 5.4-STABLE FreeBSD 5.4-STABLE #1: Thu
Jul 14 11:39:27 BST 2005
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/MYKERNEL i386
# burncd -f /dev/acd0 audio test.wav fixate
next writeable LBA 4720
writing from
On 7/14/05, Yann Golanski [EMAIL PROTECTED] wrote:
I am trying to burn to my CD drive and I keep getting the same error,
namely only wrote -1 of 37632 bytes: Device busy. I've been able to
write to that dive from FreeBSD in the past but now, nada.
# burncd -f /dev/acd0 audio test.wav fixate
Just in case anyone else has the same problem and wants a solution.
1- Recompile and install your kernel with the following options:
device atapicam
device ata
device scbus
device cd
device pass
2- Go to your MP3 dir.
3- Converts spaces to underscores.
for i in *.mp3; do mv $i `echo
On Thu, 14 Jul 2005 15:50:43 +0200, Yann Golanski [EMAIL PROTECTED] wrote:
Just in case anyone else has the same problem and wants a solution.
1- Recompile and install your kernel with the following options:
device atapicam
device ata
device scbus
device cd
device pass
2- Go to your
All,
1. I've noticed that on two separate systems, both running 5.3-RELEASE
that 'burncd -vef /dev/acd0 erase' hangs at 83%. This is true for a
couple different CD-RW discs (one brand new, never been used).
2. I've been able to burn ISO file systems with no problems. However,
I've not been
Hello,
Last time, the burncd/cdrecord were work when I had FreeBSD
5.4-PRERELEASE #0: Fri Mar 18 14:28:40 CST 2005.. Later when I updated
RELENG_5 to FreeBSD 5.4-PRERELEASE #0: Sun Mar 27 20:11:40 CST 2005 and
the burncd/cdrecord don't work anymore. I tried to update RELENG_5 to
yesterday
Hi,
I'm having trouble burning CD's from FreeBSD 5.3 guest through WinXP host on
VMWare Workstation 4.5.2
My VMWare workstation is complaining about DMA mode when I run:
burncd -s 10 -f /dev/acd0 data test.iso fixate
The error message from VMWare I get is:
Your virtual machine has sent
Hi, freebsd users.
After upgrade from 4.10 to 5.3, I can't write disks
with burncd tool. I see this error:
# burncd -emv -s 10 data akt.iso fixate
adding type 0x08 file akt.iso size 554522 KB 277261 blocks
next writeable LBA 0
addr = 0 size = 567830528 blocks = 277261
writing from file
On Tue, 2005-01-11 at 16:55 +0200, Nikolay Pavlov wrote:
Hi, freebsd users.
After upgrade from 4.10 to 5.3, I can't write disks
with burncd tool. I see this error:
# burncd -emv -s 10 data akt.iso fixate
adding type 0x08 file akt.iso size 554522 KB 277261 blocks
next writeable LBA 0
following a crash. Try running burncd from the console and
see if there are any messages.
Also, you might like to expand on locks up. Can you ping the system
from another host? Switch VTYs? If you have DDB enabled, can you
enter it?
As i can burn it in Win, i am out of ideas.
I
Hallo list,
i have tried to burn an iso of 26MB of size, and my system locks
up so i have to reboot.
The image was created with:
mkisofs -l -J -r -o output.iso burndir/
and the burncommand was:
burncd -f /dev/acd1 -s 4 data output.iso fixate
After reboot i
On Tue, 2005-Jan-04 00:20:59 +0100, Norbert Augenstein wrote:
i have tried to burn an iso of 26MB of size, and my system locks
up so i have to reboot.
/var/log/messages is unlikely to include the last 30 seconds or so of
logging following a crash. Try running burncd from the console
On Sun, 24 Oct 2004 06:28, Jonathan Chen wrote:
Some cd-writers *require* that you eject the newly-burnt cd and
re-insert it, before the drive will read it. This _might_ be the problem
you are seeing, if the cd image is correct (iso 9660).
If only it were so... I forgot to add the
Hi, Jonathan.
On Saturday, 23 October 2004 at 17:49:28 +1300, Jonathan Chen wrote:
Hi,
I'm running 5.3-STABLE, and seem to have a problem where if I run
burncd, I am not able to mount the recently burnt CD. If I
reboot the box, the mount on the CDwill succeed. I am experiencing
this on 2
On Sat, 23 Oct 2004 17:49:28 +1300
Jonathan Chen [EMAIL PROTECTED] wrote:
I'm running 5.3-STABLE, and seem to have a problem where if I run
burncd, I am not able to mount the recently burnt CD. If I
reboot the box, the mount on the CDwill succeed. I am experiencing
this on 2 very different
On Sat, Oct 23, 2004 at 10:56:24AM +0300, Nikolay Pavlov wrote:
Hi, Jonathan.
On Saturday, 23 October 2004 at 17:49:28 +1300, Jonathan Chen wrote:
Hi,
I'm running 5.3-STABLE, and seem to have a problem where if I run
burncd, I am not able to mount the recently burnt CD. If I
reboot
On Sat, Oct 23, 2004 at 11:37:51AM +0200, Torfinn Ingolfsen wrote:
On Sat, 23 Oct 2004 17:49:28 +1300
Jonathan Chen [EMAIL PROTECTED] wrote:
I'm running 5.3-STABLE, and seem to have a problem where if I run
burncd, I am not able to mount the recently burnt CD. If I
reboot the box
Hi,
I'm running 5.3-STABLE, and seem to have a problem where if I run
burncd, I am not able to mount the recently burnt CD. If I
reboot the box, the mount on the CDwill succeed. I am experiencing
this on 2 very different i386 boxes.
Anyone else seeing this?
Cheers.
--
Jonathan Chen [EMAIL
On Wed, 9 Apr 2003 14:43:43 -0500 (EST)
FreeBSD [EMAIL PROTECTED] wrote:
F Are there plans to implement the DVD capabilities of burncd
F in FreeBSD 5.X-CURRENT into 4.X-STABLE? We need to make
F backups to DVD-R using an IDE burner. Is upgrading to
F 5.X-CURRENT our only option
Richard Mahoney wrote:
I am having trouble burning CD-R's with the following:
[ ... ]
Do any readers have any idea what the issue may be. This problem has
been occuring on and off for a while but appears to be becoming worse.
What does atacontrol mode 1 show? Is your burner running in PIO, or in
table size(bytes): 502
Max brk space used c3664
84864 extents written (165 Mb)
next writeable LBA 0
writing from file /usr/home/share/temp/rbm49/scan.iso size 169728 KB
written this track 129184 KB (76%) total 129184 KB
only wrote -1 of 32768 bytes err=5
burncd: ioctl(CDRIOCFLUSH): Input/output error
On Sun, 28 Sep 2003, Jim Bryant wrote:
FreeBSD wahoo.prodigy.net 4.9-PRERELEASE FreeBSD 4.9-PRERELEASE #0: Tue
Sep 23 10:13:51 CDT 2003
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/WAHOO.SMP i386
Dual Pentium II 333 MHz on Tyan Thunder-2 Motherboard.
Anyone else seeing this?
I don't think I
. But as soon as I try to
burn a DVD-R it errors out:
tar burncd -f /dev/cdrom data data_1.iso fixate
burncd: ioctl(CDRIOCNEXTWRITEABLEADDR): Input/output error
And messages throws this up:
acd0: READ_TRACK_INFO - HARDWARE ERROR asc=0x09 ascq=0x02 error=0x00
acd0: TEST_UNIT_READY - HARDWARE ERROR asc
Hi,
Last time I used burncd on this machine was before the ata mfc.
Now when I try burning a .iso image I get:
Jul 28 18:44:38 ei /kernel: acd0: READ_TRACK_INFO command timeout - resetting
Jul 28 18:44:38 ei /kernel: ata1: resetting devices .. ata1-slave: ATAPI identif
y retries exceeded
Jul
-RW
burncd -t -f /dev/acd0c -d audio heart_beat_wisdom.wav
memories_of_xanadu.wav shambhalla.wav symphony_for_shangila.wav
writing from file heart_beat_wisdom.wav size 103621 KB
only wrote -1 of 37632 bytes err=16
writing from file memories_of_xanadu.wav size 75303 KB
only wrote -1
FreeBSD ariel.phys.wesleyan.edu 4.6-RC FreeBSD 4.6-RC #32: Wed May 29
LG CD-RW
burncd -t -f /dev/acd0c -d audio heart_beat_wisdom.wav memories_of_xanadu.wav
shambhalla.wav symphony_for_shangila.wav
writing from file heart_beat_wisdom.wav size 103621 KB
only wrote -1 of 37632 bytes err=16
On Mon, 25 Mar 2002, Andrew Heybey wrote:
AH I'm trying 4.5-RELEASE plus Soren's patches for the new ata driver and
AH burncd. I just got a CD-RW drive, so I don't know if this used to
AH work or not.
AH
AH The following does not work:
AH
AH mkisofs -R some_directory | burncd -s 8 data
On Sun, Feb 17, 2002 at 05:25:17PM -0800, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Paul Mather [EMAIL PROTECTED] writes:
: After a little more research, I found that DAO is supported in burncd
: under 5.0-CURRENT. However, after briefly installing FreeBSD from
://www.freebsd.org/cgi/query-pr.cgi?pr=27893.
My solution? I bought a Plextor.
If only that were an option in this case ;)
Is it a problem with burncd itself or with the ATA drivers?
It is in the ATA kernel code, or rather (IMHO) the LG firmware not
behaving according to spec. I took a quick look
On Wed, Oct 31, 2001 at 07:51:37PM -0800, Mikko Tyolajarvi wrote:
In local.freebsd.stable you write:
I'm trying to write a small audio file to a CD. Burncd refuses to
do it... for instance... if I do something like:
burncd -f /dev/acd0c -s 1 audio audio.raw fixate
[...]
Oct 31 21:45
On Wed, 11 Jul 2001, Søren Schmidt wrote:
It seems Randall Hopper wrote:
Running 4.3-STABLE from 6/25/01, and just tried burning a CD on a new
Sony CRX140E CD-RW (8x4x32) ATAPI drive using burncd:
# burncd -s 8 -t -f /dev/acd0c data firewall.iso fixate
next writeable
-
From: Neil Long [EMAIL PROTECTED]
To: Nuno Teixeira [EMAIL PROTECTED]
Sent: Monday, October 22, 2001 4:51 PM
Subject: Re: burncd, mkisofs, multisession doesn't work for more than 2
sessions
Unless msinfo can give intermediate sessions you may have to rely on
handwritten notes, etc.
Seems
1 - 100 of 114 matches
Mail list logo
