Re: bin/160979: 9.0 burncd error caused by change to cd0 from acd0
.. 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://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: bin/160979: 9.0 burncd error caused by change to cd0 from acd0
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 built with acd(4) and the beforementioned device is supported by acd(4). Hi, That patch is an improvement over the existing behavior. However, we may want to go a bit farther. Here are some possible scenarios: (1) User has a system with ATAPI CD-ROM only. Covered. (2) User has a system with ATAPI CD-ROM *and* USB CD-ROM. First case covered. Second case requires cdrecord anyhow, so don't care. (3) User has a system with USB CD-ROM only. Second case requires cdrecord anyhow, so don't care. (4) User has a system with ATAPI CD-ROM and SCSI CD-ROM Same as (2). (5) User has a system with SCSI CD-ROM only Same as (3). I would guess that (1) is the most common scenario, and end-users will definitely encounter it and complain. In the case of (1), it would be nice if we could fail if we try to burn to /dev/cd0, as per your patch, but still check to see if ATA_CAM is enabled in the kernel, and print out a message with pointers for using cdrtools. With your patch, a user will see a message about acd(4), and try to get it to compile/kldload/whatever acd(4) on their system, and then not get it to work because ATA_CAM is enabled. Adding notes to the burncd man page that burncd will not work on ATAPI devices if ATA_CAM is enabled would be good to do also. If the long term plan is to get rid of the old ATA subsystem, and completely move to ATA_CAM, then we should put a deprecation warning in the burncd man page as well, to give users a further heads-up. Noting something in the documentation is fine. The point is that there's a lot of wasted electrons being tossed about about a fairly trivial issue: most of the apps that burn/use CDs were converted over to some logic long ago that matches cdrecord. The only apps that haven't really been (atacontrol, burncd) were abandoned because the developer isn't an active maintainer. Thanks, -Garrett___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: bin/160979: 9.0 burncd error caused by change to cd0 from acd0
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 built with acd(4) and the beforementioned > device is supported by acd(4). Hi, That patch is an improvement over the existing behavior. However, we may want to go a bit farther. Here are some possible scenarios: (1) User has a system with ATAPI CD-ROM only. (2) User has a system with ATAPI CD-ROM *and* USB CD-ROM. (3) User has a system with USB CD-ROM only. (4) User has a system with ATAPI CD-ROM and SCSI CD-ROM (5) User has a system with SCSI CD-ROM only I would guess that (1) is the most common scenario, and end-users will definitely encounter it and complain. In the case of (1), it would be nice if we could fail if we try to burn to /dev/cd0, as per your patch, but still check to see if ATA_CAM is enabled in the kernel, and print out a message with pointers for using cdrtools. With your patch, a user will see a message about acd(4), and try to get it to compile/kldload/whatever acd(4) on their system, and then not get it to work because ATA_CAM is enabled. Adding notes to the burncd man page that burncd will not work on ATAPI devices if ATA_CAM is enabled would be good to do also. If the long term plan is to get rid of the old ATA subsystem, and completely move to ATA_CAM, then we should put a deprecation warning in the burncd man page as well, to give users a further heads-up. -- Craig Rodrigues rodr...@crodrigues.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: bin/160979: 9.0 burncd error caused by change to cd0 from acd0
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.
It doesn't fail to work on ATAPI hardware. It fails to work on cd0 which
is a SCSI device. The fact that it's emulated doesn't matter.
True, but the subtlety of that distinction will be lost on a lot of end-users
not familiar with the implementation of the FreeBSD storage implementation.
To them "burncd just doesn't work, when it used to".
Can we modify burncd to somehow detect if ATAPI-CAM is enabled, and print out
a more useful error message?
Sure, as soon as someone volunteers to create that patch. No one is
*trying* to annoy users, but things change around here because people
are interested in changing them.
I am not familiar enough with the ATA_CAM work. Is there a a sysctl or ioctl
that can be queried from userspace to detect if ATA_CAM is configured
in the kernel?
I would suggest something like:
...
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) and the beforementioned
device is supported by acd(4).Index: usr.sbin/burncd/burncd.c
=======
--- usr.sbin/burncd/burncd.c(revision 225704)
+++ usr.sbin/burncd/burncd.c(working copy)
@@ -159,8 +159,16 @@
if ((fd = open(dev, O_RDWR, 0)) < 0)
err(EX_NOINPUT, "open(%s)", dev);
- if (ioctl(fd, CDRIOCGETBLOCKSIZE, &saved_block_size) < 0)
- err(EX_IOERR, "ioctl(CDRIOCGETBLOCKSIZE)");
+ if (ioctl(fd, CDRIOCGETBLOCKSIZE, &saved_block_size) < 0) {
+ if (errno == ENOTTY)
+ errx(EX_IOERR,
+ "device provided not an acd(4) device: %s.\n\n"
+ "Please verify that your kernel is built with "
+ "acd(4) and the beforementioned device is "
+ "supported by acd(4).", dev);
+ else
+ err(EX_IOERR, "ioctl(CDRIOCGETBLOCKSIZE)");
+ }
if (ioctl(fd, CDRIOCWRITESPEED, &speed) < 0)
err(EX_IOERR, "ioctl(CDRIOCWRITESPEED)");
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: bin/160979: 9.0 burncd error caused by change to cd0 from acd0
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 >> cdrecord command to the basic release as the replacement for burncd. >> Then add release notes entry of the change. > > I think you misunderstand the situation. So here are a few hopefully > helpful facts: > > 1. The fact that something is in the base, or in the ports, has > absolutely no bearing on whether one piece of software is fundamentally > more useful or valuable than another. Hi, 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. Fbsd8 has a valid point. Can we modify burncd to somehow detect if ATAPI-CAM is enabled, and print out a more useful error message? "ERROR: burncd does not work when ATAPI-CAM driver enabled. Install the sysutils/cdrtools port and use cdrecord instead. Please refer to http://www.freebsd.org/doc/handbook/creating-cds.html#CDRECORD"; While it is necessary to document all these things in release notes, documentation, etc., I don't always read every single last line of documentation or release notes when using a system, and I suspect many end-users are the same. :) I am a big fan of having the system issue diagnostic errors that give the user a clue how to remedy the problem, or pointers to relevant information. I even put "Please" in the error message to be nice. :) -- Craig Rodrigues rodr...@crodrigues.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: bin/160979: 9.0 burncd error caused by change to cd0 from acd0
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 doesn't fail to work on ATAPI hardware. It fails to work on cd0 which
> is a SCSI device. The fact that it's emulated doesn't matter.
True, but the subtlety of that distinction will be lost on a lot of end-users
not familiar with the implementation of the FreeBSD storage implementation.
To them "burncd just doesn't work, when it used to".
>> Can we modify burncd to somehow detect if ATAPI-CAM is enabled, and print out
>> a more useful error message?
>
> Sure, as soon as someone volunteers to create that patch. No one is
> *trying* to annoy users, but things change around here because people
> are interested in changing them.
I am not familiar enough with the ATA_CAM work. Is there a a sysctl or ioctl
that can be queried from userspace to detect if ATA_CAM is configured
in the kernel?
I would suggest something like:
flag = query for hw.ata.ata_cam_enabled sysctl;
if (flag == 1) {
printf("ERROR: ATA_CAM enabled, etc., etc.)
exit(1);
}
I only see these sysctls on a system with ATA_CAM enabled:
hw.ata.setmax: 0
hw.ata.wc: 1
hw.ata.atapi_dma: 1
hw.ata.ata_dma_check_80pin: 1
hw.ata.ata_dma: 1
dev.atapci.0.%desc: Intel ATA controller
dev.atapci.0.%driver: atapci
dev.atapci.0.%location: slot=3 function=2
dev.atapci.0.%pnpinfo: vendor=0x8086 device=0x29b6 subvendor=0x1028
subdevice=0x0211 class=0x010185
dev.atapci.0.%parent: pci0
dev.ata.2.%desc: ATA channel 0
dev.ata.2.%driver: ata
dev.ata.2.%location: channel=0
dev.ata.2.%parent: atapci0
dev.ata.3.%desc: ATA channel 1
dev.ata.3.%driver: ata
dev.ata.3.%location: channel=1
dev.ata.3.%parent: atapci0
dev.ata.0.%driver: ata
dev.ata.0.%parent: isa0
dev.ata.1.%driver: ata
dev.ata.1.%parent: isa0
--
Craig Rodrigues
rodr...@crodrigues.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: bin/160979: 9.0 burncd error caused by change to cd0 from acd0
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 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 notes entry of the change. >> >> I think you misunderstand the situation. So here are a few hopefully >> helpful facts: >> >> 1. The fact that something is in the base, or in the ports, has >> absolutely no bearing on whether one piece of software is fundamentally >> more useful or valuable than another. > > > Hi, > > 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 ATAPI hardware. It fails to work on cd0 which is a SCSI device. The fact that it's emulated doesn't matter. > Can we modify burncd to somehow detect if ATAPI-CAM is enabled, and print out > a more useful error message? Sure, as soon as someone volunteers to create that patch. No one is *trying* to annoy users, but things change around here because people are interested in changing them. hth, Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: bin/160979: 9.0 burncd error caused by change to cd0 from acd0
On 09/26/2011 17:59, Fbsd8 wrote: > Your solution is very un-professional. Good thing we're all volunteers. :) > What your solution purposes to do > is do nothing. I think your judgment is flawed and a larger group of > your peers need to review your judgment in this case. Ok, 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 replacement for burncd. > Then add release notes entry of the change. I think you misunderstand the situation. So here are a few hopefully helpful facts: 1. The fact that something is in the base, or in the ports, has absolutely no bearing on whether one piece of software is fundamentally more useful or valuable than another. 2. burncd has only ever worked with a subset of the legacy ATA hardware. 3. ATA-CAM is on by default in FreeBSD 9 (which means that rather than acd0 as an ATA device you'll have cd0 as a SCSI device). 4. However, ATA-CAM is not mandatory, which means that leaving burncd in the base for those that want to continue using the legacy ATA interface is a perfectly reasonable course of action. 5. For those that wish to use the default ATA-CAM interface the cdrecord port provides a mature, full-featured solution. Even if it were possible to import it into the base, doing so would be a step in the wrong direction. > You do not knowingly leave a non-working utility in the system, period, That makes sense, however see above. > or not provide a included replacement for a popular utility as this one. The alternative already exists. The fact that it's not in the base has no relevance. I hope this clears up your confusion. If you have any further questions please direct them to freebsd-questions@FreeBSD.org only. Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: bin/160979: 9.0 burncd error caused by change to cd0 from acd0
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://www.freebsd.org/cgi/query-pr.cgi?pr=160979 Your solution is very un-professional. What your solution purposes to do is do nothing. I think your judgment is flawed and a larger group of your peers need to review your judgment in this case. 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 notes entry of the change. You do not knowingly leave a non-working utility in the system, period, or not provide a included replacement for a popular utility as this one. The alternative is to fix burncd or backout the acd0 to cd0 change from 9.0 which may be the most desired solution because its obvious that no one researched the impact this change may have. This change may impact many ports that access cd/dvd drives for read and write access. burncd may be a very small worm in a large can of big worms. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 9.0 and burncd error
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 archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
9.0 and burncd error
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 be fixed to work in 9.0. Has anyone else had problem with the burncd command in 9.0? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: burncd issue
On Tue, 2 Feb 2010 13:30:13 -0800 (PST), Dánielisz László
wrote:
> It looks that I should recompile my kernel for using growisofs
No, you should read "man growisofs". :-)
Honestly: You're trying to run growisofs on an acd device:
> # growisofs -dvd-compat -speed=4 -Z /dev/acd0=pats-tts2.iso
> :-( unable to open64("pats-tts2.iso",O_RDONLY): No such file or directory
Not mentioning the open64() error, this won't work. The
growisofs program uses cd instead of acd - this is the
ATAPICAM "SCSI over ATA" mechanism. You can easily load
the atapicam.ko module to make it available.
Then, you should get something like this:
% camcontrol devlist
at scbus2 target 0 lun 0 (cd1,pass3)
The SCSI ID 2:0:0 corresponds to the /dev/cd1 device. If
you have sufficient permissions (needed for cd, xpt, pass,
check /etc/devfs.rules for permanent settings), you can
run e. g.
% growisofs -dvd-compat -Z /dev/dvd=pats-tts2.iso
You don't need to specify -speed, because growisofs sets
the right speed correctly.
As you see, I'm accessing /dev/dvd; this is a symlink to
the correct cd device, in this case
% growisofs -dvd-compat -Z /dev/cd1=pats-tts2.iso
would be the "good" command.
Your output
> # camcontrol devlist -v
> scbus-1 on xpt0 bus 0:
> <> at scbus-1 target -1 lun -1 (xpt0)
still looks a bit strange - empty identification, 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-tts2.iso
By the way, I have an alias for that because I'm lazy. :-)
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: burncd issue
Well, I fixed that too by adding the following lines to /boot/loader.conf:
atapicam_load="YES"
hw.ata.atapi_dma="1"
DVD writing is in progress:
517341184/4689756160 (11.0%) @3.9x, remaining 14:14 RBU 100.0% UBU 53.1%
535756800/4689756160 (11.4%) @4.0x, remaining 14:05 RBU 100.0% UBU 65.3%
554205184/4689756160 (11.8%) @4.0x, remaining 14:03 RBU 100.0% UBU 81.6%
572227584/4689756160 (12.2%) @3.9x, remaining 13:54 RBU 100.0% UBU 81.6%
591822848/4689756160 (12.6%) @4.2x, remaining 13:43 RBU 100.0% UBU 36.7%
If you don't want to reboot your machine you 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 -Z /dev/acd0=pats-tts2.iso
:-( unable to open64("pats-tts2.iso",O_RDONLY): No such file or directory
# camcontrol devlist -v
scbus-1 on xpt0 bus 0:
<> at 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 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, 2010 10:05:45 PM
Subject: burncd issue
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
burncd: write_file: Device busy
Then I tryed growisofs, but it says
#growisofs
growisofs: Command not found.
# whereis growisofs
growisofs:
Do you have any idea how to fix this?
Thank you!
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: burncd issue
It looks that I should recompile my kernel for using growisofs
# growisofs -dvd-compat -speed=4 -Z /dev/acd0=pats-tts2.iso
:-( unable to open64("pats-tts2.iso",O_RDONLY): No such file or directory
# camcontrol devlist -v
scbus-1 on xpt0 bus 0:
<> at 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 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, 2010 10:05:45 PM
Subject: burncd issue
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
burncd: write_file: Device busy
Then I tryed growisofs, but it says
#growisofs
growisofs: Command not found.
# whereis growisofs
growisofs:
Do you have any idea how to fix this?
Thank you!
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: burncd issue
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, 2010 10:05:45 PM Subject: burncd issue 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 burncd: write_file: Device busy Then I tryed growisofs, but it says #growisofs growisofs: Command not found. # whereis growisofs growisofs: Do you have any idea how to fix this? Thank you! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
burncd issue
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 burncd: write_file: Device busy Then I tryed growisofs, but it says #growisofs growisofs: Command not found. # whereis growisofs growisofs: Do you have any idea how to fix this? Thank you! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 7.2 burncd and cdrecord problem
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 than > sysutils/cdrtools. The latter is several years out of date, and the > upstream maintainer of the software has said that no one should be > using it, but the maintainer of the FreeBSD port has so far been > unwilling to update it. > > ... > >>And dmesg shows: >>acd0: FAILURE - READ_BUFFER ILLEGAL REQUEST asc=0x24 ascq=0x00 >>acd0: FAILURE - MODE_SELECT_BIG ILLEGAL REQUEST asc=0x26 ascq=0x00 > > It is not unusual for some errors to appear, even during normal > operation, so these don't necessarily indicate a problem, although it > was good that you posted them. You should run the cdrecord command > with -vv (yes, two v's) to get verbose error messages from cdrecord. > This should give you a better idea of why cdrecord is failing. If the > error messages from -vv are not enough, you can also add -VV, although > this affects the timing of the operations, and should be used with > care when recording. > > I have had problems like this in the past, when a disk was corrupted, > and cdrecord balked at blanking it. I used blank=all with either the > -immed flag, or the -force flag, or both, to solve the problems. Honestly I didn't think this was the problem, but it seems I've had a bad virgin CD set. Two of them (of a set of 5) seem to work fine. I can write, rewrite and blank them. Aaarrghh! sorry for the noise. Nevertheless, I will try to update to cdrtools-devel since I have cdrtools installed Thanks to all of you. > > If you are using cdrtools, you should probably use the cd(4) driver > together with atapicam(4), rather than the acd(4) driver. To prevent > possible problems, it is safer to prevent both drivers from attaching > to the same device. I usually remove: > > device atapicd > > from my kernel, and just use: > > device ata > device atapicam > device scbus > device cd > device pass > > I don't know whether it is possible to disable the acd(4) driver using > just loader.conf(5), device.hints(5), or some other means at boot- or > run-time, but you could look into that if you don't want to go to the > trouble of removing it from your kernel. > > b. > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 7.2 burncd and cdrecord problem
> 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 out of date, and the upstream maintainer of the software has said that no one should be using it, but the maintainer of the FreeBSD port has so far been unwilling to update it. ... >And dmesg shows: >acd0: FAILURE - READ_BUFFER ILLEGAL REQUEST asc=0x24 ascq=0x00 >acd0: FAILURE - MODE_SELECT_BIG ILLEGAL REQUEST asc=0x26 ascq=0x00 It is not unusual for some errors to appear, even during normal operation, so these don't necessarily indicate a problem, although it was good that you posted them. You should run the cdrecord command with -vv (yes, two v's) to get verbose error messages from cdrecord. This should give you a better idea of why cdrecord is failing. If the error messages from -vv are not enough, you can also add -VV, although this affects the timing of the operations, and should be used with care when recording. I have had problems like this in the past, when a disk was corrupted, and cdrecord balked at blanking it. I used blank=all with either the -immed flag, or the -force flag, or both, to solve the problems. If you are using cdrtools, you should probably use the cd(4) driver together with atapicam(4), rather than the acd(4) driver. To prevent possible problems, it is safer to prevent both drivers from attaching to the same device. I usually remove: device atapicd from my kernel, and just use: device ata device atapicam device scbus device cd device pass I don't know whether it is possible to disable the acd(4) driver using just loader.conf(5), device.hints(5), or some other means at boot- or run-time, but you could look into that if you don't want to go to the trouble of removing it from your kernel. b. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 7.2 burncd and cdrecord problem
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 -blank=fast dev=3,0,0 I get: >> >> [...] >> Using generic SCSI-3/mmc CD-ROM driver (mmc_cd). >> Driver flags : MMC-3 SWABAUDIO BURNFREE >> Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R >> Starting to write CD/DVD at speed 18 in real BLANK mode for single session. >> Last chance to quit, starting real write 0 seconds. Operation starts. >> This drive or media does not support the 'BLANK media' command >> cdrecord: Cannot blank disk, aborting. >> cdrecord: Some drives do not support all blank types. >> cdrecord: Try again with cdrecord blank=all. > > So what happened when you tried the blank=all option instead of your > blank=fast? > You did try that, didn't you? I did, sorry I didn't mention that. It shows the same errors. > > Ruben > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 7.2 burncd and cdrecord problem
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 CD-ROM driver (mmc_cd). > Driver flags : MMC-3 SWABAUDIO BURNFREE > Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R > Starting to write CD/DVD at speed 18 in real BLANK mode for single session. > Last chance to quit, starting real write0 seconds. Operation starts. > This drive or media does not support the 'BLANK media' command > cdrecord: Cannot blank disk, aborting. > cdrecord: Some drives do not support all blank types. > cdrecord: Try again with cdrecord blank=all. So what happened when you tried the blank=all option instead of your blank=fast? You did try that, didn't you? Ruben ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 7.2 burncd and cdrecord problem
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 itself say rewrite anywhere? Check the output of % cdrecord -prcap dev=3,0,0 which will list what the drive does support. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 7.2 burncd and cdrecord problem
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 itself say rewrite anywhere? --TJ On 8/14/09, Fernando Apesteguía wrote: > 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 CD-ROM driver (mmc_cd). > Driver flags : MMC-3 SWABAUDIO BURNFREE > Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R > Starting to write CD/DVD at speed 18 in real BLANK mode for single session. > Last chance to quit, starting real write0 seconds. Operation starts. > This drive or media does not support the 'BLANK media' command > cdrecord: 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 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: DVDR at ata3-master SATA150 > > I have scbus, atapicd and atapicam in my kernel configuration. > > Any ideas? > > Thanks in advance. > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
7.2 burncd and cdrecord problem
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 CD-ROM driver (mmc_cd). Driver flags : MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R Starting to write CD/DVD at speed 18 in real BLANK mode for single session. Last chance to quit, starting real write0 seconds. Operation starts. This drive or media does not support the 'BLANK media' command cdrecord: 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 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: DVDR at ata3-master SATA150 I have scbus, atapicd and atapicam in my kernel configuration. Any ideas? Thanks in advance. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problem with burncd
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://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problem with burncd
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 CD comes out ok, though, so I think it is failing after the fixate process is complete. Without a filesystem, you can still get your file back with "dd if=/dev/acd0 of=newfilename.txt bs=2048" where of course newfilename.txt can be whatever you want the new copy to be called. The other issues raised by your post (no filesystem, other software) have been addressed by others, but fwiw I use mkisofs to build the filesystem, and then burncd to burn it to the cd. For storing data on DVDs, growisofs is much more convenient, install it as part of sysutils/dvd+rw-tools. -- Bob Johnson fbsdli...@gmail.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problem with burncd
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: > > # burncd -ev -s max fixate data notes.txt As far as I know, the command should be like # burncd -ev -s max data notes.txt fixate I don't know if the order matters. Furthermore: You know that you are recording notes.txt directly onto the CD and omitting the ISO-9660 filesystem? > Now, if I do not use the 'fixate' command, no error message is > displayed; however, the CD is not readable. Yes, it is not fixated. > I have no idea what the > problem is. I have used brand new CD disks that work fine on my Windows > PCs. I had similar problems with burncd a long while ago, and I dropped it completely in favour of SCSI / CAM based tools. > Is there a better CD-Burner program that I could use instead? There is. Install cdrecord and / or cdrdao for CDs, and growisofs for DVDs. Loat atapicam kernel module. Use it. Be happy. :-) -- Polytropon >From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problem with burncd
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 > > Now, if I do not use the 'fixate' command, no error message is > displayed; however, the CD is not readable. I have no idea what the > problem is. I have used brand new CD disks that work fine on my Windows > PCs. > > Is there a better CD-Burner program that I could use instead? > > -- > Carmel do you get the contents of notes.txt when you cat /dev/acd0 You may get some more header info of the CD before the notes.txt is displayed. All you told it to do is to burn, verbatim the file notes.txt without any filesystem onto the CD. All CD/CDFS drivers, op systems, etc use a filesystem on the CD. So the file may be there, but not in a filesystem. mkisofs creates the ISO/CDFS filesystem, to various "ISO standards" so you can burn it on CD. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problem with burncd
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 > > Now, if I do not use the 'fixate' command, no error message is > displayed; however, the CD is not readable. I have no idea what the > problem is. I have used brand new CD disks that work fine on my Windows > PCs. > > Is there a better CD-Burner program that I could use instead? First of all, you need to make a filesystem to burn onto the CD. I find it very unlikely that you really want to burn a text file directly. I suggest you start by reading the documentation on the subject: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problem with burncd
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. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Problem with burncd
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 is displayed; however, the CD is not readable. I have no idea what the problem is. I have used brand new CD disks that work fine on my Windows PCs. Is there a better CD-Burner program that I could use instead? -- Carmel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: burncd
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 list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: burncd
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-dvds.html ___ I second that, cdrecord and growisofs (part of the dvd+rw-tools package) are essential for modern machines. Although using burncd works well enough on my ancient rigs, a recent attempt to use burncd with a SATA optical drive resulted in a kernel panic. I suspect, unlike cdrecord and growisofs, that burncd is no longer a modern utility, and is in serious need of an overhaul. David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: burncd
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-dvds.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
burncd
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 burncd. HOWEVER, it failed during fixate.
I could boot from it, but the new OS said it couldn't mount root!
Later attempts to mount the DVD from previous 7.1 also failed.
Is there a better tool than burncd? I resorted to using disc1, which
worked as always, and then copying the packages collection from
the mounted DVD ISO (note the ISO could be mounted, but not the DVD)
before sysinstall could drive me crazy with its disc{1,2,3} swapping
insanity.
BTW I have a DSL connection, 768bps, 89.5Bps on a good day. From
ftp10.freebsd.org it took me about 5 hours to get the DVD, plus another
2+ hours for disc1. Beh.
Sorry if I'm dissembling. Just that 7.2 has been more headache than
previous distros like 7.1, 7.0, 6.3 etc. Mebbe I'll mention some of
the problems - like What is HAL, essential to getting X up? Solved,
BTW, but no help during sysinstall.
Thanks for FreeBSD! I've used it as a retired sysadmin since 386BSD.
Chuck Bacon -- c...@cape.com
ABHOR SECRECY -- DEFEND PRIVACY
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
BurnCd--Kernel Panic
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 they should. I wanted to alert others using the same or similar boards. If anyone has any ideas, I'd like to know why this happens. Is there a planned update to the burncd software or how it addresses the system that might remedy this in future releases? --David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: error trying to burncd thhen ecomign unkillable process
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 or by compiling it into your kernel. If you don't have the proper permissions, access to ATAPICAM won't work. Access to cd, pass and xpt is needed (rules to be setup in /etc/devfs.conf), or simply call the command as root or via sudo. > enterprise# growisofs -dvd-compat -Z /dev/acd0=neroultraV7.iso > :-( unable to CAMGETPASSTHRU for /dev/acd0: Inappropriate ioctl for device > > Something aint right obviously. Obviously. You need to specify an ATAPICAM device, /dev/cd0 for example. If you want to use /dev/dvd like in the example on growisofs's manpage, you need to change the symlink in /etc/devfs.conf: linkcd0 dvd The symlink usually points to acd0 which isn't ATAPICAM compatible. -- Polytropon >From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: error trying to burncd thhen ecomign unkillable process
> % 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 :-( unable to CAMGETPASSTHRU for /dev/acd0: Inappropriate ioctl for device Something aint right obviously. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: error trying to burncd thhen ecomign unkillable process
On Sun, 25 Jan 2009 12:11:18 +1000, Warren Liddell wrote: > 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... > > [...] > > After this error the ROM drives 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 me > to burn a cd//dvd? For a CD, try % cdrecord dev=1,0,0 speed=16 -v -eject -tao -data neroultraV7.iso Check the SCSI device numbers using % camcontrol devlist and adjust the dev= parameter accordingly. For a DVD, try % growisofs -dvd-compat -Z /dev/dvd=neroultraV7.iso Excange /dev/dvd for the correct drive (e. g. /dev/cd0). > I am usingg FreeBSD 7.1-STABLE AMD64 KDE 4.1.4 I don't know exactly, but can K3B be adjusted to use a specific command line burning tool to record pre-mastered ISO files onto CD or DVD? Maybe you could put one of the command lines above into this program... (I'm no KDE user, so I can't check this.) -- Polytropon >From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
error trying to burncd thhen ecomign unkillable process
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 310495 blocks burncd: ioctl(CDRIOCINITTRACK): Input/output error After this error the ROM drives stays in a constant state of spin and the process refuses to die even after issuing the kill -9 What am i doing wrrong or what is wroong with my system to not allow me to burn a cd//dvd? I am usingg FreeBSD 7.1-STABLE AMD64 KDE 4.1.4 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Burncd & 700MB rw/cd
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? Does burncd need a programming update to handle these newer larger sized rw/cd's? What other (built in with the release) program can be used to burn 700 MB rw/cd's? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" Aloha, HEre is what we did about a month ago when a similar issue came up wit a couple of us and CDR's. Julien Cigar wrote: > Same problems for me with atapi CD/DVD drives (READ_BIG timeouts, > etc) .. it works a bit better when dma is turned off, but then > performances are very poor. > > On Thu, 2008-08-07 at 14:17 -1000, Al Plant wrote: >> N.J. Thomas wrote: >>> * "Snorre D. ?verb?" <[EMAIL PROTECTED]> [2008-08-07 15:29:11+]: >>>> When I boot up with the installation DVD these error messages appear >>>> on the screen. >>>> >>>> ad1: FAILURE - READ_DMA status=51 error=84 LBA=0055347 >>>> ad0: FAILURE - READ_DMA status=51 error=84 LBA=0 >>>> etc >>> I got the same exact errors trying to install 7.0-RELEASE on two >>> different Dell boxes. One was 4 years old, the other was brand new (3 >>> months ago). >>> >>> Never was able to fix the problem. For the older one, I plugged in an >>> external DVD drive and installed via that. For the other one, I >>> installed via a mini-install disk, and then did a minimal network >>> install. >>> >>> For the record, they both had SATA drives and the disks worked (and >>> still work) fine after the OS was installed. It was just copying the >>> base system off the CD that was causing errors. >>> >>> Thomas >>> ___ >>> freebsd-questions@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >>> To unsubscribe, send any mail to "[EMAIL PROTECTED]" >> 888 >> Aloha, >> >> I am getting the same errors as you guys with an intermittient BIG_read one occasionally. I've tried to install FreeeBSD CURRENT 8 and 7 release. >> >> This is on a no name box with a bio board and 1100 cpu. I've had this on other boxes too and load IDE drives on a box that works with them and then put them in the box with errors and they work just fine. >> >> Every thing gets recognized normally at install time, but the size of the IDE drive a Fujutsu 20 gig. shows twice what it should be every time. >> >> Dont know if this has anything to do with it, except if you change the size in installer it wont load anything. >> >> Maybe one of the top level gurus on the list can help. >> >> >> Aloha, The suggestion to put the folloeing worked to clear my DMA error. In: /boot/loader Put: hw.ata.ata_dma=0 #disable IDE DMA This allowed an uninterrupted boot. -- ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + + http://aloha50.net - Supporting - FreeBSD 6.* - 7.* - 8.* + < email: [EMAIL PROTECTED] > "All that's really worth doing is what we do for others."- Lewis Carrol ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Burncd & 700MB rw/cd
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 to record the media? Most CD-RWs can't be recorded as fast as CD-Rs can. > What other (built in with the release) program can be used to burn 700 MB > rw/cd's? Since introduction of atapicam (needs to be in your kernel) I switched to the cdrecord utility, and sometimes I use cdrdao, both availabe from ports. -- Polytropon >From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Burncd & 700MB rw/cd
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 need a programming update to handle these newer larger sized rw/cd's? What other (built in with the release) program can be used to burn 700 MB rw/cd's? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: burncd error?
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 as I remember, /dev/acd0 instead of /dev/acd0c is to be used as device file for burning and reading since FreeBSD 5.0. > Can somebody enlighten me please. 1. Maybe you can try blank media from another manufacturer? 2. Maybe you can try another burning program (cdrecord)? 3. Maybe you can try to burn at a lower speed? Just some ideas... -- Polytropon >From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
burncd error?
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 GEOM_LABEL: Label for provider acd0 is iso 9660/FreeBSD_Install This did not happen with Current or RELEASE 7.0 FreeBSD /dev/acd0c used to work. Now you have to use /dev/acd0 (no c) to get burncd to work. Can somebody enlighten me please. ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + + http://aloha50.net - Supporting - FreeBSD 6.* - 7.* - 8.* + < email: [EMAIL PROTECTED] > "All that's really worth doing is what we do for others."- Lewis Carrol ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Unable to write any audio CDs with the current 7.0 (both burncd and cdrecord)
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=4 driveropts=burnfree *.cdr' finishes but produces unplayable CD. I tried the older SONY drive and cdrecord produced unreadable CD with it too. Yuri ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
burncd and driveropts=burnfree?
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 achieve this buffer-underrun protection with burncd in FreeBSD? Or would I need to use cdrecord with kldload atapicam (taking from another current thread on this list)? As far as I could see, Linux and NetBSD use cdrecord, and there is no burncd. I have burned CDs, data only so far, from Linux but not from any other OS. Under FreeBSD, am I better off with burncd or with cdrecord? Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 6.2-REL && burncd
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 that the > problem was not with burncd but with the ide cd driver. I believe that > it's return values and timings changed thus breaking burncd. A scan of > the list archives in Google should show the earlier thread. Yes, I remember that thread and even added to its volume with experiences of my own. There were a number of things pointed out about a driver problem and my comment that I could get it to work if I slowed down the speed from max. But, I don't remember that any solution or patch or fix was ever suggested. So, as far as I know, the problem is still extant and needs some work and is likely to continue to spark questions and comments. I hope it can be fixed. I don't know enough about it to fix it. jerry > > -- Chris > > -- > __o "All I was doing was trying to get home from work." > _`\<,_ -Rosa Parks > ___(*)/_(*)___ > Christopher Sean Hilton > pgp key: D0957A2D/f5 30 0a e1 55 76 9b 1f 47 0b 07 e9 75 0e 14 > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 6.2-REL && burncd
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 believe that the > problem was not with burncd but with the ide cd driver. I believe that > it's return values and timings changed thus breaking burncd. A scan of > the list archives in Google should show the earlier thread. > > -- Chris This (asking Don Google) is what I do always before posting; there is a lot of noise about that and a lot of bug reports in the database, for example this one: http://www.freebsd.org/cgi/query-pr.cgi?pr=95344 but I don't see any solution; of course I could use 'cdrecord' but 'burncd' is much nicer/easier to use matthias -- Matthias Apitz Manager Technical Support - OCLC PICA GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e <[EMAIL PROTECTED]> - w http://www.oclcpica.org/ http://guru.UnixArea.de/ b http://gurucubano.blogspot.com/ OCLC PICA GmbH, Geschaeftsfuehrer: Christine Magin-Weeger, Norbert Weinberger Sitz der Gesellschaft: Oberhaching, HRB Muenchen: 113261 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 6.2-REL && burncd
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 return values and timings changed thus breaking burncd. A scan of the list archives in Google should show the earlier thread. -- Chris -- __o "All I was doing was trying to get home from work." _`\<,_ -Rosa Parks ___(*)/_(*)___ Christopher Sean Hilton pgp key: D0957A2D/f5 30 0a e1 55 76 9b 1f 47 0b 07 e9 75 0e 14 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD 6.2-REL && burncd
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 worked fine and fast. In 6.2-REL I now get the error: # burncd -f /dev/acd0 -s max data cdimage.raw fixate next writeable LBA 0 writing from file cdimage.raw size 517992 KB written this track 517992 KB (100%) total 517992 KB fixating CD, please wait.. burncd: ioctl(CDRIOCFIXATE): Input/output error # and also a second 'fixate' fails with: # burncd -f /dev/acd0 fixate fixating CD, please wait.. burncd: ioctl(CDRIOCFIXATE): Input/output error # A re-read of the burned CD fails as well (even if the CD is mountable): # dd if=/dev/acd0 of=cdimage.iso bs=2048 dd: /dev/acd0: Input/output error 258996+0 records in 258996+0 records out 530423808 bytes transferred in 280.964918 secs (1887865 bytes/sec) but the re-read file is binary identical to the ISO image burned: # diff cdimage.raw cdimage.iso # ls -l cdimage.* -rw-r--r-- 1 root wheel 530423808 29 may 11:19 cdimage.iso -rw-r--r-- 1 root wheel 530423808 28 may 08:57 cdimage.raw # I've grabbed the source of 'burncd' from FreeBSD's CVS and there is no change in src/usr.sbin/burncd/burncd.c (the revision in both cases is 1.45); So, what now? Thx matthias -- Matthias Apitz Manager Technical Support - OCLC PICA GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e <[EMAIL PROTECTED]> - w http://www.oclcpica.org/ http://guru.UnixArea.de/ b http://gurucubano.blogspot.com/ OCLC PICA GmbH, Geschaeftsfuehrer: Christine Magin-Weeger, Norbert Weinberger Sitz der Gesellschaft: Oberhaching, HRB Muenchen: 113261 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: burncd on FreeBSD-6.2
> >> > 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/pipermail/freebsd-questions/2007-March/145173.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: burncd on FreeBSD-6.2
On 5/23/07, Paul Schmehl <[EMAIL PROTECTED]> wrote: --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 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 >> > written this track 364 KB (100%) total 364 KB >> > >> > >> > 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. >> > >> You need to use fixate: >> fixateFixate the medium so that the TOC is generated and the >> media can be used in an ordinary CD drive. The driver >>defaults to creating singlesession media (see -m >>option). Ignored in DAO mode (see -d option). >> >> burncd -ef /dev/acd0 data /home/user/cd.iso fixate >> > > Sorry, I forgot to mention that. I used fixate too. Is the iso really 364KB? That's awfully small for an iso. Maybe there's something wrong with the image? I would think that 7.0 Current Disk 2 would be much largerlike 654MB. Yeah the size is correct. I was able to mount the iso without any problem. And the MD5SUM matched too. Regards, sac. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: burncd on FreeBSD-6.2
--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 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 > written this track 364 KB (100%) total 364 KB > > > 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. > You need to use fixate: fixateFixate the medium so that the TOC is generated and the media can be used in an ordinary CD drive. The driver defaults to creating singlesession media (see -m option). Ignored in DAO mode (see -d option). burncd -ef /dev/acd0 data /home/user/cd.iso fixate Sorry, I forgot to mention that. I used fixate too. Is the iso really 364KB? That's awfully small for an iso. Maybe there's something wrong with the image? I would think that 7.0 Current Disk 2 would be much largerlike 654MB. -- Paul Schmehl ([EMAIL PROTECTED]) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/
Re: burncd on FreeBSD-6.2
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 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 > written this track 364 KB (100%) total 364 KB > > > 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. > You need to use fixate: fixateFixate the medium so that the TOC is generated and the media can be used in an ordinary CD drive. The driver defaults to creating singlesession media (see -m option). Ignored in DAO mode (see -d option). burncd -ef /dev/acd0 data /home/user/cd.iso fixate Sorry, I forgot to mention that. I used fixate too. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: burncd on FreeBSD-6.2
--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: addr = 0 size = 372736 blocks = 182 writing from file 7.0-CURRENT-200704-i386-disc2.iso size 364 KB written this track 364 KB (100%) total 364 KB 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. You need to use fixate: fixateFixate the medium so that the TOC is generated and the media can be used in an ordinary CD drive. The driver defaults to creating singlesession media (see -m option). Ignored in DAO mode (see -d option). burncd -ef /dev/acd0 data /home/user/cd.iso fixate -- Paul Schmehl ([EMAIL PROTECTED]) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/
burncd on FreeBSD-6.2
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-200704-i386-disc2.iso size 364 KB written this track 364 KB (100%) total 364 KB 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. Regards, sac. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
burncd(8) with DVD+R how?
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 memory = 334430208 (318 MB) acd0: CDRW at ata0-slave UDMA33 Media: DVD+R Log: [EMAIL PROTECTED] ~ #burncd -f /dev/acd0 data ~x/disc1.iso fixate next writeable LBA 0 writing from file /home/pb/disc1.iso size 4435298 KB written this track 4435298 KB (100%) total 4435298 KB fixating CD, please wait.. burncd: ioctl(CDRIOCFIXATE): Input/output error Exit 74 [EMAIL PROTECTED] ~ #sync [EMAIL PROTECTED] ~ #burncd -f /dev/acd0 fixate fixating CD, please wait.. burncd: ioctl(CDRIOCFIXATE): Input/output error Exit 74 [EMAIL PROTECTED] ~ #burncd -f /dev/acd0 dvdrw fixate [EMAIL PROTECTED] ~ #burncd -f /dev/acd0 fixate fixating CD, please wait.. burncd: ioctl(CDRIOCFIXATE): Input/output error Exit 74 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SOLVED: Re: Problems with "burncd" - cannot mount result on unix or windows
On Fri, Mar 23, 2007 at 02:11:12PM -0700, Transpacific wrote: > I ought to know better than to say "SUCKS" in any case. > > I tried to make the point that, other things being equal > <... lots excised> > trivial thing to be able to do, so I knew it > was only a 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 said, oh, ran it for > burncd, voila. So the "missing FAQ" would > be sort of an intermediate or slight level of detail, perhaps more like > a tear-out reference card summary of the > actions to take (and any underlying kernel/library/package requirements.) One thing I can agree with when it comes to documentation is that an well crafted example or set of examples can be more meaningful than many paragraphs and even pages of explanation or specification. The specification is necessary, but the examples make it much more clear.More of the documentation - handbook and man pages and FAQs should make better use of examples. Some do, but many don't. The more the better. As for the specific topic of mkisofs and CD burning, the handbook has some basic examples, but might benefit from some more covering possible variations. jerry > > My apologies to Father Greg. > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SOLVED: Re: Problems with "burncd" - cannot mount result on unix or windows
I ought to know better than to say "SUCKS" in any case. I tried to make the point that, other things being equal (I know about filesystems in general, I'm just not familiar with their peculiarities in dealing with CDs), all I wanted to "see quickly" was the example 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 "man page 2", as it were - and in reading the description and arguments, I was gulled by the phrase "fixating the CD writes a TOC and makes the CD readable". It said it wrote files to the CD, I didn't see a reminder or warning that only ISOs would make sense. Now that I know better about what can meaningfully be put on a CD, now I know. I had always equated ISOs with "bootable install images", but now I get it. In fact that distinction was reinforced in using windows CD burning software where ISOs had to be handled differently to be written correctly - what I was otherwise seeing was what appeared to be dumping files to the CD, but underneath the program was encapsulating the data as ISO on the fly, evidently. I wouldn't suspect "burncd" didn't function similarly. And, of course, everyone else already knew about ISOs, and so nobody thought to ask that pre-basic question. As to the "why didn't you just read ..." - I was in a hurry; this was a trivial thing to be able to do, so I knew it was only a 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 said, oh, ran it for burncd, voila. So the "missing FAQ" would be sort of an intermediate or slight level of detail, perhaps more like a tear-out reference card summary of the actions to take (and any underlying kernel/library/package requirements.) My apologies to Father Greg. == Jerry McAllister wrote: On Fri, Mar 23, 2007 at 03:00:49PM -0400, Jerry McAllister wrote: On Thu, Mar 22, 2007 at 04:16:58PM -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 deal: NEVER HAVING BURNED a CD or DVD on FreeBSD before - I go to the documentation to FIND OUT HOW and there really is no HOW So I look in vain for "What you 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/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 commands read the man page and it SAYS of burncd fixate writes a TOC and makes the CD readable I am writing an ISO9660 device (a device for which ISO9660 is a reasonable default FS - yes? no?) Any meaningful defaults here? Did the man page tell me I hade to wrap my data inside a filesystem image? I did not see that. So DUH is right. I then said, hey. mkisofs -R -o image.raw junk.tar THEN said burncd -f /dev/acd0 data image.raw fixate and VOILA like magic all is good. It works and reads on unix and windows like a champ. Sorry for replying to my own reply, but. Oh, I just assumed you had done the mkiso. Should be mkisofs of course. If that is not in the handbook and FAQ, it should be, of course. Just took a look and the handbook does have all this and more. You should actually read it before jumping all over everything about lack of documentation. There may be some terminology such as Rock Ridge and Joliet that could use a more clear explanation, but what you needed to know was clearly there. jerry Sorry. jerry === 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 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. -foo- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebs
Re: SOLVED: Re: Problems with "burncd" - cannot mount result on unix or windows
On Fri, Mar 23, 2007 at 03:00:49PM -0400, Jerry McAllister wrote: > On Thu, Mar 22, 2007 at 04:16:58PM -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 deal: > > > > NEVER HAVING BURNED a CD or DVD on FreeBSD before - > > I go to the documentation to FIND OUT HOW > > and there really is no HOW > > > > So I look in vain for > > > > "What you 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/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 commands read the man page and it SAYS of > > burncd > > > > fixate writes a TOC and makes the CD readable > > > > I am writing an ISO9660 device (a device for which ISO9660 is a reasonable > > default FS - yes? no?) > > Any meaningful defaults here? Did the man page tell me I hade to wrap my > > data inside a filesystem image? > > I did not see that. So DUH is right. > > > > I then said, hey. > > > > mkisofs -R -o image.raw junk.tar > > > > THEN said > > > > burncd -f /dev/acd0 data image.raw fixate > > > > and VOILA like magic all is good. It works and reads on unix and windows > > like a champ. Sorry for replying to my own reply, but. > > Oh, I just assumed you had done the mkiso. Should be mkisofs of course. > If that is not in the handbook and FAQ, it should be, of course. Just took a look and the handbook does have all this and more. You should actually read it before jumping all over everything about lack of documentation. There may be some terminology such as Rock Ridge and Joliet that could use a more clear explanation, but what you needed to know was clearly there. jerry > > Sorry. > > jerry > > > > > === > > > > 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 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. > > > > -foo- > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SOLVED: Re: Problems with "burncd" - cannot mount result on unix or windows
On Thu, Mar 22, 2007 at 04:16:58PM -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 deal: > > NEVER HAVING BURNED a CD or DVD on FreeBSD before - > I go to the documentation to FIND OUT HOW > and there really is no HOW > > So I look in vain for > > "What you 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/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 commands read the man page and it SAYS of > burncd > > fixate writes a TOC and makes the CD readable > > I am writing an ISO9660 device (a device for which ISO9660 is a reasonable > default FS - yes? no?) > Any meaningful defaults here? Did the man page tell me I hade to wrap my > data inside a filesystem image? > I did not see that. So DUH is right. > > I then said, hey. > > mkisofs -R -o image.raw junk.tar > > THEN said > > burncd -f /dev/acd0 data image.raw fixate > > and VOILA like magic all is good. It works and reads on unix and windows > like a champ. Oh, I just assumed you had done the mkiso. If that is not in the handbook and FAQ, it should be, of course. Sorry. jerry > > === > > 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 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. > > -foo- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problems with "burncd" - cannot mount result on unix or windows
--On Friday, March 23, 2007 08:50:08 +0200 Jonathan McKeown <[EMAIL PROTECTED]> wrote: Just as a further point of reference, I also found that -s max caused the DVD+RW drive in my laptop (6.1), and the CD writer in my desktop PC at home (5.4), to make shiny coasters. Setting an actual 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) has memorised the fact that the drive contains a blank CD and continues to treat it as empty media even after writing to it. I have *never* had this problem with burncd. I always burn like this: burncd -ef /dev/acd1 data file.iso fixate I have burned a *bunch* of cds, and I've never once had a problem doing this. Paul Schmehl ([EMAIL PROTECTED]) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/
Re: Problems with "burncd" - cannot mount result on unix or windows
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 drive in my laptop (6.1), and the CD writer in my desktop PC at home (5.4), to make shiny coasters. Setting an actual speed worked fine, except for a further odd problem on the DVD+RW laptop drive. 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 the fact that the drive contains a blank CD and continues to treat it as empty media even after writing to it. In the end the only way I found to close off a disc and write a ToC is: burncd data image.iso burncd fixate Jonathan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SOLVED: Re: Problems with "burncd" - cannot mount result on unix or windows
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 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. -foo- Um, you seem to have done a fair job, why not do: [EMAIL PROTECTED]:~-> diff smart ass 1,2d0 < SMART ASS REMARKS < 47,48d44 < < DRY SARCASM & FURTHER SMART ASS REMARKS [EMAIL PROTECTED]:~-> And commit it yourself? - Eric F Crist Secure Computing Networks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SOLVED: Re: Problems with "burncd" - cannot mount result on unix or windows
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 writes a TOC and makes the CD readable I am writing an ISO9660 device (a device for which ISO9660 is a reasonable default FS - yes? no?) Any meaningful defaults here? Did the man page tell me I hade to wrap my data inside a filesystem image? I did not see that. So DUH is right. I then said, hey. mkisofs -R -o image.raw junk.tar THEN said burncd -f /dev/acd0 data image.raw fixate and VOILA like magic all is good. It works and reads on unix and windows like a champ. === So THE FAQ and/or HOWTO SUCKS, is the problem. Not sure which FAQ you are referring to, and I thought HOWTO was a Linux thing. How about the handbook instead. This whole mkisofs business is pretty well documented at http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html Having read that, I've never had a single problem writing data CDs under FreeBSD, and I'm a long way from being a guru. If that offends purists, try fixing your transmission under deadline with a japanese shop manual translated into english and no diagrams. Been there, done that. How about fixing your transmission with no documentation at all, only your (meager) previous experience to go on. And still with a deadline. And the deadline is tomorrow, but it's the weekend so no shops are open. And Tim Berners-Lee is 22 years old, so nothing online even if you could afford a computer. In my experience, documentation (especially API documentation) is usually wrong in some respect or another. That's why anyone trying to write a driver really needs to have the hardware. Documentation makes all the difference, both to novices and to professionals. I agree completely. Good documentation makes the difference between a painless experience and a painful one. Someone who knows the how and what should write a contributed thing - whenever they have the time and desire to educate the unwashed masses. Please feel free to do so. It would be much appreciated by the next person who finds himself in your position. -foo- -bar- -- Chris Hill [EMAIL PROTECTED] ** [ Busy Expunging <|> ] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SOLVED: Re: Problems with "burncd" - cannot mount result on unix or windows
--On March 22, 2007 4:16:58 PM -0700 UCTC Sysadmin <[EMAIL PROTECTED]> wrote: 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 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. mkisofs(8), available in the FreeBSD Ports Collec- tion, as part of the sysutils/cdrtools port, is commonly used to create ISO9660 file system images from a given directory tree." Hm. man (8) mkisofs "mkisofs is effectively a pre-mastering program to generate an ISO9660/JOLIET/HFS hybrid filesystem. mkisofs is capable of generating the System Use Sharing Protocol records (SUSP) specified by the Rock Ridge Interchange Protocol. This is used to further describe the files in the iso9660 filesystem to a unix host, and provides information such as longer filenames, uid/gid, posix permissions, symbolic links, block and character devices." If you don't like man pages, there's always the handbook: <http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html> "CDs have a number of features that differentiate them from conventional disks. Initially, they were not writable by the user. They are designed so that they can be read continuously without delays to move the head between tracks. They are also much easier to transport between systems than similarly sized media were at the time. CDs do have tracks, but this refers to a section of data to be read continuously and not a physical property of the disk. To produce a CD on FreeBSD, you prepare the data files that are going to make up the tracks on the CD, then write the tracks to the CD. The ISO 9660 file system was designed to deal with these differences. It unfortunately codifies file system limits that were common then. Fortunately, it provides an extension mechanism that allows properly written CDs to exceed those limits while still working with systems that do not support those extensions. The sysutils/cdrtools port includes mkisofs(8), a program that you can use to produce a data file containing an ISO 9660 file system. It has options that support various extensions, and is described below. Which tool to use to burn the CD depends on whether your CD burner is ATAPI or something else. ATAPI CD burners use the burncd program that is part of the base system. SCSI and USB CD burners should use cdrecord from the sysutils/cdrtools port. It is also possible to use cdrecord and other tools for SCSI drives on ATAPI hardware with the ATAPI/CAM module. If you want CD burning software with a graphical user interface, you may wish to take a look at either X-CD-Roast or K3b. These tools are available as packages or from the sysutils/xcdroast and sysutils/k3b ports. X-CD-Roast and K3b require the ATAPI/CAM module with ATAPI hardware." Unix systems *assume* you can read. Perhaps that's a bad assumption, but that's the assumption they make. Unfortunately, many people are impatient and get ahead of themselves, thinking that partial knowledge is all that's required. Sometimes that works. Sometimes it doesn't. Paul Schmehl ([EMAIL PROTECTED]) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/
Re: SOLVED: Re: Problems with "burncd" - cannot mount result on unix or windows
[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 deal: > > NEVER HAVING BURNED a CD or DVD on FreeBSD before - I go to the > documentation to FIND OUT HOW and there really is no HOW You mention documentation above, but you don't say what you're referring to. > So I look in vain for > > "What you 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" What's wrong with the information in the handbook? http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html > So THE FAQ and/or HOWTO SUCKS, is the problem. I see two problems, both of them different: - You don't say what you read, and what you didn't understand about it. - You didn't submit an update. > If that offends purists, I think what's more likely to offend is a complaint without substantiation. I'm not saying that there are no errors in the documentation--of course there are--but how can we fix them (if they exist) based on your rant? Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers. pgpyICFizbfKZ.pgp Description: PGP signature
Re: SOLVED: Re: Problems with "burncd" - cannot mount result on unix or windows
On Mar 22, 2007, at 4:16 PM, 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 deal: NEVER HAVING BURNED a CD or DVD on FreeBSD before - I go to the documentation to FIND OUT HOW and there really is no HOW So I look in vain for "What you 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" It helps 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 mount -t cd9660 /dev/acd0 /mnt fails and the CD is also unreadable on windows. "tar tf /dev/acd0" would give you the contents of the junk.tar file you burned. 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 writes a TOC and makes the CD readable I am writing an ISO9660 device (a device for which ISO9660 is a reasonable default FS - yes? no?) Any meaningful defaults here? Did the man page tell me I hade to wrap my data inside a filesystem image? I did not see that. So DUH is right. There are lots of possible filesystems one could put on a CD. ISO-9660 is a common choice, and even a reasonable default, but if you want to write files directly to the CD as a block-access device, you can. I then said, hey. mkisofs -R -o image.raw junk.tar THEN said burncd -f /dev/acd0 data image.raw fixate and VOILA like magic all is good. It works and reads on unix and windows like a champ. === 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 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. Actually, "man burncd" does give a bunch of examples-- it has an entire section of them-- and finishes with the comment: In the examples above, the files burned to data CD-Rs are assumed to be ISO9660 file systems. mkisofs(8), available in the FreeBSD Ports Collec- tion, as part of the sysutils/cdrtools port, is commonly used to create ISO9660 file system images from a given directory tree. -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
SOLVED: Re: Problems with "burncd" - cannot mount result on unix or windows
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 deal: NEVER HAVING BURNED a CD or DVD on FreeBSD before - I go to the documentation to FIND OUT HOW and there really is no HOW So I look in vain for "What you 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/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 commands read the man page and it SAYS of burncd fixate writes a TOC and makes the CD readable I am writing an ISO9660 device (a device for which ISO9660 is a reasonable default FS - yes? no?) Any meaningful defaults here? Did the man page tell me I hade to wrap my data inside a filesystem image? I did not see that. So DUH is right. I then said, hey. mkisofs -R -o image.raw junk.tar THEN said burncd -f /dev/acd0 data image.raw fixate and VOILA like magic all is good. It works and reads on unix and windows like a champ. === 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 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. -foo- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problems with "burncd" - cannot mount result on unix or windows
UCTC Sysadmin wrote: > Using a Sony CRX850E slimline CD burner / DVD reader > FreeBSD 6.1 > > I write a single file to the CD and say "-fixate"; the command shows the > progress of writing > and then finishes with no error message. Trying to then mount that CD on > 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't. I burn CDs with this command: burncd -f /dev/acd0 data cd.iso fixate -- Tore ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problems with "burncd" - cannot mount result on unix or windows
On Thu, Mar 22, 2007 at 12:31:32PM -0700, UCTC Sysadmin wrote: > Using a Sony CRX850E slimline CD burner / DVD reader > FreeBSD 6.1 > > I write a single file to the CD and say "-fixate"; the command shows the > progress of writing > and then finishes with no error message. Trying to then mount that CD on > FreeBSD says "unrecognizable" > and on windows says "maybe disk is blank." This was covered about a week ago in questions. I had similar problems and am not at all sure why or that the changes I made fixed the problem, but it now 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 FreeBSD62-disc1.iso fixate It makes a both bootable and mountable CD. Although I have used -s max successfully in the past, burncd stopped working when I went to FreeBSD 6.xx - could neither boot nor mount the resulting burned CDs. Taking out that parameter seemed to get it working again. > > Is burncd broken? Maybe, at least sort of?? Or is it my CD burner getting old? Except the problem showed up on all of the machines that I brought up to 6.xx. I doubt that all their Cd burners would simultaneously die at the same time. A couple are barely used and I don't really stress my main one all that much. jerry > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Problems with "burncd" - cannot mount result on unix or windows
Using a Sony CRX850E slimline CD burner / DVD reader FreeBSD 6.1 I write a single file to the CD and say "-fixate"; the command shows the progress of writing and then finishes with no error message. Trying to then mount that CD on FreeBSD says "unrecognizable" and on windows 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]"
Re: burncd makes disk that is unmountable
> > > > > > 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'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 the details, but I settled upon: > > > > > /usr/sbin/burncd -v -f /dev/acd0 data FreeBSD62-disc1.iso fixate > > > > > which seems to work find. Both boots and mounts. That doesn't look > > > > > materially different from yours, but... > > > > > > > > It is defaulting to the correct device. > > > > > > > > > > Seemed to go okay. Disk boots, but I cannot mount it: > > > > > > > > > > > > fstab entry: > > > > > > /dev/acd0 /cdrom cd9660 ro,noauto 0 > > > > > > 0 > > > > > > > > > > > > Yields: > > > > > > g_vfs_done():acd0[READ(offset=32768, length=2048)]error = 5 > > > > > > > > > > > > Tried it with and without "fixate", neither will mount. > > > > > > > > > > > > Other iso disks (probably burned using NetBSD) mount fine. > > > > > > UFS DVD+RW disks burned under FreeBSD using growisofs mount fine. > > > > > > > > > > > > Given the error message, I assume that the block/sector at 32768 > > > > > > isn't > > > > > > getting written. > > > > > > > > New data: NetBSD mounts both disks (with and without "fixate") just > > > > fine. > > > > So perhaps the problem is with FreeBSD's mount rather than burncd? > > > > > > Typing in mount yields what options with NetBSD? > > > > Command is: > > > > mount /cdrom > > > > NetBSD's fstab entry: > > > > /dev/cd0a /cdrom cd9660 ro,noauto 0 0 > > > > Identical to FreeBSD's entry, except for the device name and perhaps > > whitespace. > > > > I now have FreeBSD 6.2 up and limping, and it fails the same way as 6.0. > > Also tried another OS, but the stupid penguin can't even find the drive. Garrett writes: > I hate to slam burncd because it does the job, but I've always found > cdrecord / mkisofs to be a better set of software for burning CDs than > burncd.. I installed cdrecord on FreeBSD 6.2. Result: cdrecord dev=/dev/acd0 -data 6.2-RELEASE-amd64-disc1.iso cdrecord: No write mode specified. cdrecord: Asuming -tao mode. cdrecord: Future versions of cdrecord may have different drive dependent defaults. cdrecord: Continuing in 5 seconds... Cdrecord-Clone 2.01 (amd64-unknown-freebsd6.2) Copyright (C) 1995-2004 J on this OS. Cannot open SCSI driver. Then I installed cdrecord on NetBSD 3.0.1. It happily burned 6.2-RELEASE-amd64-disc1.iso and 6.2-RELEASE-amd64-disc2.iso. NetBSD will mount both. FreeBSD 6.2 will mount both. So: There is something different on a CD burned by cdrecord and a CD burned by burncd. There is something different between FreeBSD mounting a CD containing an ISO and NetBSD mounting the same CD. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: burncd makes disk that is unmountable
> > > > 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'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 the details, but I settled upon: > > > /usr/sbin/burncd -v -f /dev/acd0 data FreeBSD62-disc1.iso fixate > > > which seems to work find. Both boots and mounts. That doesn't look > > > materially different from yours, but... > > > > It is defaulting to the correct device. > > > > > > Seemed to go okay. Disk boots, but I cannot mount it: > > > > > > > > fstab entry: > > > > /dev/acd0 /cdrom cd9660 ro,noauto 0 > > > > 0 > > > > > > > > Yields: > > > > g_vfs_done():acd0[READ(offset=32768, length=2048)]error = 5 > > > > > > > > Tried it with and without "fixate", neither will mount. > > > > > > > > Other iso disks (probably burned using NetBSD) mount fine. > > > > UFS DVD+RW disks burned under FreeBSD using growisofs mount fine. > > > > > > > > Given the error message, I assume that the block/sector at 32768 isn't > > > > getting written. > > > > New data: NetBSD mounts both disks (with and without "fixate") just fine. > > So perhaps the problem is with FreeBSD's mount rather than burncd? > > Typing in mount yields what options with NetBSD? Command is: mount /cdrom NetBSD's fstab entry: /dev/cd0a /cdrom cd9660 ro,noauto 0 0 Identical to FreeBSD's entry, except for the device name and perhaps whitespace. I now have FreeBSD 6.2 up and limping, and it fails the same way as 6.0. Also tried another OS, but the stupid penguin can't even find the drive. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: burncd makes disk that is unmountable
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'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 the details, but I settled upon: /usr/sbin/burncd -v -f /dev/acd0 data FreeBSD62-disc1.iso fixate which seems to work find. Both boots and mounts. That doesn't look materially different from yours, but... It is defaulting to the correct device. Seemed to go okay. Disk boots, but I cannot mount it: fstab entry: /dev/acd0 /cdrom cd9660 ro,noauto 0 0 Yields: g_vfs_done():acd0[READ(offset=32768, length=2048)]error = 5 Tried it with and without "fixate", neither will mount. Other iso disks (probably burned using NetBSD) mount fine. UFS DVD+RW disks burned under FreeBSD using growisofs mount fine. Given the error message, I assume that the block/sector at 32768 isn't getting written. New data: NetBSD mounts both disks (with and without "fixate") just fine. So perhaps the problem is with FreeBSD's mount rather than burncd? Typing in mount yields what options with NetBSD? -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: burncd makes disk that is unmountable
> > 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'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 the details, but I settled upon: > /usr/sbin/burncd -v -f /dev/acd0 data FreeBSD62-disc1.iso fixate > which seems to work find. Both boots and mounts. That doesn't look > materially different from yours, but... It is defaulting to the correct device. > > Seemed to go okay. Disk boots, but I cannot mount it: > > > > fstab entry: > > /dev/acd0 /cdrom cd9660 ro,noauto 0 0 > > > > Yields: > > g_vfs_done():acd0[READ(offset=32768, length=2048)]error = 5 > > > > Tried it with and without "fixate", neither will mount. > > > > Other iso disks (probably burned using NetBSD) mount fine. > > UFS DVD+RW disks burned under FreeBSD using growisofs mount fine. > > > > Given the error message, I assume that the block/sector at 32768 isn't > > getting written. New data: NetBSD mounts both disks (with and without "fixate") just fine. So perhaps the problem is with FreeBSD's mount rather than burncd? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: burncd makes disk that is unmountable
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 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'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 the details, but I settled upon: > > /usr/sbin/burncd -v -f /dev/acd0 data FreeBSD62-disc1.iso fixate > >which seems to work find. Both boots and mounts. That doesn't look > >materially different from yours, but... > > > >jerry > > > >>Seemed to go okay. Disk boots, but I cannot mount it: > >> > >>fstab entry: > >> /dev/acd0 /cdrom cd9660 ro,noauto 0 > >> 0 > >> > >>Yields: > >> g_vfs_done():acd0[READ(offset=32768, length=2048)]error = 5 > >> > >>Tried it with and without "fixate", neither will mount. > >> > >>Other iso disks (probably burned using NetBSD) mount fine. > >>UFS DVD+RW disks burned under FreeBSD using growisofs mount fine. > >> > >>Given the error message, I assume that the block/sector at 32768 isn't > >>getting written. > > I hate to slam burncd because it does the job, but I've always found > cdrecord / mkisofs to be a better set of software for burning CDs than > burncd.. Besides, burncd chokes on permission errors on my machine > whereas cdrecord keeps on humming away with issue, and I've been using > it for 2 releases now (6.1, 6.2). When I was having trouble the last time, I thought about using cdrecord, but managed to get burncd working OK. I use it because it is there and normally does what I want. I would have to install cdrecord separately and figure out how to use it. jerry > > -Garrett > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: burncd makes disk that is unmountable
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/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 the details, but I settled upon: /usr/sbin/burncd -v -f /dev/acd0 data FreeBSD62-disc1.iso fixate which seems to work find. Both boots and mounts. That doesn't look materially different from yours, but... jerry Seemed to go okay. Disk boots, but I cannot mount it: fstab entry: /dev/acd0 /cdrom cd9660 ro,noauto 0 0 Yields: g_vfs_done():acd0[READ(offset=32768, length=2048)]error = 5 Tried it with and without "fixate", neither will mount. Other iso disks (probably burned using NetBSD) mount fine. UFS DVD+RW disks burned under FreeBSD using growisofs mount fine. Given the error message, I assume that the block/sector at 32768 isn't getting written. I hate to slam burncd because it does the job, but I've always found cdrecord / mkisofs to be a better set of software for burning CDs than burncd.. Besides, burncd chokes on permission errors on my machine whereas cdrecord keeps on humming away with issue, and I've been using it for 2 releases now (6.1, 6.2). -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: burncd makes disk that is unmountable
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/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 the details, but I settled upon: /usr/sbin/burncd -v -f /dev/acd0 data FreeBSD62-disc1.iso fixate which seems to work find. Both boots and mounts. That doesn't look materially different from yours, but... jerry > > Seemed to go okay. Disk boots, but I cannot mount it: > > fstab entry: > /dev/acd0 /cdrom cd9660 ro,noauto 0 0 > > Yields: > g_vfs_done():acd0[READ(offset=32768, length=2048)]error = 5 > > Tried it with and without "fixate", neither will mount. > > Other iso disks (probably burned using NetBSD) mount fine. > UFS DVD+RW disks burned under FreeBSD using growisofs mount fine. > > Given the error message, I assume that the block/sector at 32768 isn't > getting written. > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
burncd makes disk that is unmountable
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 mount it: fstab entry: /dev/acd0 /cdrom cd9660 ro,noauto 0 0 Yields: g_vfs_done():acd0[READ(offset=32768, length=2048)]error = 5 Tried it with and without "fixate", neither will mount. Other iso disks (probably burned using NetBSD) mount fine. UFS DVD+RW disks burned under FreeBSD using growisofs mount fine. Given the error message, I assume that the block/sector at 32768 isn't getting written. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Any burncd changes
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 and burned CDs on it with no problem using burncd. Nearly all of these were boot/install CDs - including the one to install FreeBSD 6.1. But immediately after installing 6.1, I can no longer successfully burn a CD. It seems to go through the motions but then nothing seems to get on the CD. I would just write this off as a CD burner gone bad except I have another box here that doesn't seem to want to burn a CD using burncd now that it has been upgraded to 6.0 and this machine has rarely been used for making CDs. Anyway, it is still probably a failing burner, but I want to make sure I am not overlooking something that would account for this happening just as I did the upgrades - actually fresh clean installs. Thanks for any information you might have, jerryJerry McAllister[EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
burncd usage
"[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. What is the data format? "data" is easiest choice in this case. > to burn a CDROM ? Probably the man page should give samples, > highlighting the data format. It does, in fact. If your "file-name" were file1, then the first example in the manual would be exactly what you would need to type. > All the man page examples wrote to the default device and still > included it in the command line. You should write to a non-default > CDROM device, and for at least 1 default CDROM device example, don't > have the device designation in the command. Sounds reasonable. Go ahead and submit it. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
burncd: ioctl(CDRIOCNEXTWRITEABLEADDR): Input/output error
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-STABLE #24: Thu Jun 22 21:36:23 EEST 2006 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/besa i386 besa# dmesg | grep acd acd0: DVDR at ata1-master UDMA66 acd0: FAILURE - READ_TRACK_INFO ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - READ_TRACK_INFO ILLEGAL REQUEST asc=0x24 ascq=0x00 Is there any way to make it work? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: burncd error
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 > > > > 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: ioctl(CDRIOCFIXATE): Input/output error > > > > The 'funny' thing about this is that the CDs I burn work fine. > > (I've tried several different ISOs and have checked the md5's on > > all of them.) > > > > Anyone have an idea of what is going on? I never tried to burn > > anything with 6.0-RELEASE and it worked fine on 5.4-RELEASE > > I've seen the same thing for the past several weeks (worked fine at > some point prior to 6.1). I'm running 6-STABLE, updated every > couple weeks. As near as I've been able to determine, the fixate > step doesn't actually do anything, so your CD's will still be > "open" but should work fine under any modern OS. As a workaround > you can repeat the fixate step at a lower speed: burncd -f > /dev/acd0 -s 4 fixate > > I haven't experimented enough to know at what speed the fixate step > breaks, but that does seem to be what's going on. I also haven't > tried turning off ATAPICAM, which would be another interesting data > point. If you or someone else has the time to figure out exactly > which (set of) commits started producing this behavior, that would > be excellent material for a PR. I may get around to it myself but > it's not a high priority. > > > dmesg is attached. > > Looks like you forgot it. In my case (using ATAPICAM): > > acd1: CDRW at ata1-slave UDMA33 > cd1 at ata1 bus 0 target 1 lun 0 > cd1: Removable CD-ROM SCSI-0 device > cd1: 33.000MB/s transfers > cd1: Attempt to query device size failed: NOT READY, Medium not > present > > JN My client says it included a dmesg...wonder what's going on with that. I've tried using different burn speeds all the way down to 32x. I am using ATAPICAM, I wonder if it is somehow related to that? I think I'll unload that and give it a shot. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html Which tool to use to burn the CD depends on whether your CD burner is ATAPI or something else. ATAPI CD burners use the burncd program that is part of the base system. SCSI and USB CD burners should use cdrecord from the sysutils/cdrtools port. It is also possible to use cdrecord and other tools for SCSI drives on ATAPI hardware with the ATAPI/CAM module. -- Linux is for people who hate Micro$oft. BSD is for people who love Unix ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: burncd 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 > > > > > > 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: ioctl(CDRIOCFIXATE): Input/output error > > > > > > The 'funny' thing about this is that the CDs I burn work fine. > > > (I've tried several different ISOs and have checked the md5's on > > > all of them.) > > > > > > Anyone have an idea of what is going on? I never tried to burn > > > anything with 6.0-RELEASE and it worked fine on 5.4-RELEASE > > > > I've seen the same thing for the past several weeks (worked fine at > > some point prior to 6.1). I'm running 6-STABLE, updated every > > couple weeks. As near as I've been able to determine, the fixate > > step doesn't actually do anything, so your CD's will still be > > "open" but should work fine under any modern OS. As a workaround > > you can repeat the fixate step at a lower speed: burncd -f > > /dev/acd0 -s 4 fixate > > > > I haven't experimented enough to know at what speed the fixate step > > breaks, but that does seem to be what's going on. I also haven't > > tried turning off ATAPICAM, which would be another interesting data > > point. If you or someone else has the time to figure out exactly > > which (set of) commits started producing this behavior, that would > > be excellent material for a PR. I may get around to it myself but > > it's not a high priority. > > > > > dmesg is attached. > > > > Looks like you forgot it. In my case (using ATAPICAM): > > > > acd1: CDRW at ata1-slave UDMA33 > > cd1 at ata1 bus 0 target 1 lun 0 > > cd1: Removable CD-ROM SCSI-0 device > > cd1: 33.000MB/s transfers > > cd1: Attempt to query device size failed: NOT READY, Medium not > > present > > > > JN > > My client says it included a dmesg...wonder what's going on with that. > > I've tried using different burn speeds all the way down to 32x. I am > using ATAPICAM, I wonder if it is somehow related to that? I think > I'll unload that and give it a shot. > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html Which tool to use to burn the CD depends on whether your CD burner is ATAPI or something else. ATAPI CD burners use the burncd program that is part of the base system. SCSI and USB CD burners should use cdrecord from the sysutils/cdrtools port. It is also possible to use cdrecord and other tools for SCSI drives on ATAPI hardware with the ATAPI/CAM module. http://www.freebsddiary.org/cdrecord-ide.php -- Linux is for people who hate Micro$oft. BSD is for people who love Unix ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: burncd error
Napoleon Dynamite wrote: [ ...top posting recovered... ] 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 - reboot. And it worked fine. 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. 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...? -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: burncd error
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, please wait.. > burncd: ioctl(CDRIOCFIXATE): Input/output error > > The 'funny' thing about this is that the CDs I burn work fine. (I've > tried several different ISOs and have checked the md5's on all of > them.) > > Anyone have an idea of what is going on? I never tried to burn > anything with 6.0-RELEASE and it worked fine on 5.4-RELEASE > > dmesg is attached. Hi, Give it a go with cdrecord from cdrtools. /usr/ports/sysutils/cdrtools Cheers, Mikhail. -- Mikhail Goriachev Webanoide Telephone: +61 (0)3 62252501 Mobile Phone: +61 (0)4 38255158 E-Mail: [EMAIL PROTECTED] Web: http://www.webanoide.org PGP Key ID: 0x4E148A3B PGP Key Fingerprint: D96B 7C14 79A5 8824 B99D 9562 F50E 2F5D 4E14 8A3B ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: burncd error
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 - reboot. And it worked fine. > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" pgpW4vES9ohrR.pgp Description: PGP signature
Re: burncd error
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-3.0.iso size 710566 KB > > written this track 710566 KB (100%) total 710566 KB > > fixating CD, please wait.. > > burncd: ioctl(CDRIOCFIXATE): Input/output error > > > > The 'funny' thing about this is that the CDs I burn work fine. > > (I've tried several different ISOs and have checked the md5's on > > all of them.) > > > > Anyone have an idea of what is going on? I never tried to burn > > anything with 6.0-RELEASE and it worked fine on 5.4-RELEASE > > I've seen the same thing for the past several weeks (worked fine at > some point prior to 6.1). I'm running 6-STABLE, updated every > couple weeks. As near as I've been able to determine, the fixate > step doesn't actually do anything, so your CD's will still be > "open" but should work fine under any modern OS. As a workaround > you can repeat the fixate step at a lower speed: burncd -f > /dev/acd0 -s 4 fixate > > I haven't experimented enough to know at what speed the fixate step > breaks, but that does seem to be what's going on. I also haven't > tried turning off ATAPICAM, which would be another interesting data > point. If you or someone else has the time to figure out exactly > which (set of) commits started producing this behavior, that would > be excellent material for a PR. I may get around to it myself but > it's not a high priority. > > > dmesg is attached. > > Looks like you forgot it. In my case (using ATAPICAM): > > acd1: CDRW at ata1-slave UDMA33 > cd1 at ata1 bus 0 target 1 lun 0 > cd1: Removable CD-ROM SCSI-0 device > cd1: 33.000MB/s transfers > cd1: Attempt to query device size failed: NOT READY, Medium not > present > > JN My client says it included a dmesg...wonder what's going on with that. I've tried using different burn speeds all the way down to 32x. I am using ATAPICAM, I wonder if it is somehow related to that? I think I'll unload that and give it a shot. -- Thanks, Josh Paetzel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: burncd error
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, please wait.. burncd: ioctl(CDRIOCFIXATE): Input/output error The 'funny' thing about this is that the CDs I burn work fine. (I've tried several different ISOs and have checked the md5's on all of them.) Anyone have an idea of what is going on? I never tried to burn anything with 6.0-RELEASE and it worked fine on 5.4-RELEASE Have you tried with "-v"? And for different values of "-s"? Just curious, Kevin Kinsey -- Better to light one candle than to curse the darkness. -- motto of the Christopher Society ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: burncd error
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 (100%) total 710566 KB > fixating CD, please wait.. > burncd: ioctl(CDRIOCFIXATE): Input/output error > > The 'funny' thing about this is that the CDs I burn work fine. (I've > tried several different ISOs and have checked the md5's on all of > them.) > > Anyone have an idea of what is going on? I never tried to burn > anything with 6.0-RELEASE and it worked fine on 5.4-RELEASE I've seen the same thing for the past several weeks (worked fine at some point prior to 6.1). I'm running 6-STABLE, updated every couple weeks. As near as I've been able to determine, the fixate step doesn't actually do anything, so your CD's will still be "open" but should work fine under any modern OS. As a workaround you can repeat the fixate step at a lower speed: burncd -f /dev/acd0 -s 4 fixate I haven't experimented enough to know at what speed the fixate step breaks, but that does seem to be what's going on. I also haven't tried turning off ATAPICAM, which would be another interesting data point. If you or someone else has the time to figure out exactly which (set of) commits started producing this behavior, that would be excellent material for a PR. I may get around to it myself but it's not a high priority. > dmesg is attached. Looks like you forgot it. In my case (using ATAPICAM): acd1: CDRW at ata1-slave UDMA33 cd1 at ata1 bus 0 target 1 lun 0 cd1: Removable CD-ROM SCSI-0 device cd1: 33.000MB/s transfers cd1: Attempt to query device size failed: NOT READY, Medium not present JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
burncd error
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 to "[EMAIL PROTECTED]"
burncd error
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: ioctl(CDRIOCFIXATE): Input/output error The 'funny' thing about this is that the CDs I burn work fine. (I've tried several different ISOs and have checked the md5's on all of them.) Anyone have an idea of what is going on? I never tried to burn anything with 6.0-RELEASE and it worked fine on 5.4-RELEASE dmesg is attached. -- Thanks, Josh Paetzel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: burncd fails: Input output error
On 5/26/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. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: burncd fails: Input output error
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. :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: burncd fails: Input output error
On Thu, 25 May 2006, Lars Stokholm 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: # dd if=/dev/acd0 of=freebsd.iso bs=2k Next I want to burn the image on a CD-R, but it fails. I'm using the -t option 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 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 Have you tried a new CD? Every now and then I'll get an error, but "fixate" always seems to write something to the CD, so it's a goner. Maybe not with -t, but an earlier attempt? Try a fresh blank. And also try burning at a slower speed, like 8x. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
burncd fails: Input output error
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: # dd if=/dev/acd0 of=freebsd.iso bs=2k Next I want to burn the image on a CD-R, but it fails. I'm using the -t option now, since I've already wasted a CD 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/output error I cannot blank or erase CD-RW media either: # burncd -s 16 -f /dev/acd1 blank (the process never stops) # burncd -s 16 -f /dev/acd1 erase (the process never stops) I'm logged in as root. Any ideas? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cdrecord vs. burncd
Thank you!!! it really worked out!! On 10/16/05, Andrew P. <[EMAIL PROTECTED]> wrote: > 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 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' > > right below), I couldn't test it yet!!! Do I have to include a special > > module to kernel in order to use cdrecord?? > > > > -- > > [EMAIL PROTECTED] cdrecord -scanbus > > Cdrecord-Clone 2.01 (i386-unknown-freebsd5.4) Copyright (C) 1995-2004 > > J\urg Schilling > > cdrecord: No such file or directory. Open of /dev/xpt0 failed. Cannot > > open SCSI driver. > > cdrecord: For possible targets try 'cdrecord -scanbus'. > > cdrecord: For possible transport specifiers try 'cdrecord dev=help'. > > ___ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > > > > > I also use cdrdao, and I like it much. It works via > ATA (acd) as well as atapicam (cd). > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cdrecord vs. burncd
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 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' > right below), I couldn't test it yet!!! Do I have to include a special > module to kernel in order to use cdrecord?? > > -- > [EMAIL PROTECTED] cdrecord -scanbus > Cdrecord-Clone 2.01 (i386-unknown-freebsd5.4) Copyright (C) 1995-2004 > J\urg Schilling > cdrecord: No such file or directory. Open of /dev/xpt0 failed. Cannot > open SCSI driver. > cdrecord: For possible targets try 'cdrecord -scanbus'. > cdrecord: For possible transport specifiers try 'cdrecord dev=help'. > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > I also use cdrdao, and I like it much. It works via ATA (acd) as well as atapicam (cd). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cdrecord vs. burncd
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 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' > right below), I couldn't test it yet!!! Do I have to include a special > module to kernel in order to use cdrecord?? When I went from SuSE Linux to FreeBSD I got this page as a hint (and it worked for me): http://www.xs4all.nl/~rsmith/freebsd/ matthias -- Matthias Apitz / Sisis Informationssysteme GmbH Gruenwalder Weg 28g / D-82041 Oberhaching Fon: ++49 89 / 61308-351, Fax: -399, Mobile ++49 170 4527211 http://www.sisis.de/~guru/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
