Re: burncd 'blank' not terminating ?

On Fri, 29 Dec 2006, Jeremy Chadwick wrote: On Fri, Dec 29, 2006 at 12:15:37AM -0700, Scott Long wrote: Did you know that ATAPI is actually just the SCSI command set that is merely encapsulated into the IDE wire protocol? This is something Linux has done (you can still use the direct ATA and I

Re: burncd 'blank' not terminating ?

On Fri, Dec 29, 2006 at 12:15:37AM -0700, Scott Long wrote: > Did you know that ATAPI is actually just the SCSI command set that is > merely encapsulated into the IDE wire protocol? This is something Linux has done (you can still use the direct ATA and IDE subsystems if you want, but in most major

Re: burncd 'blank' not terminating ?

Peter Jeremy wrote: On Mon, 2006-Dec-25 16:55:54 +0100, O. Hartmann wrote: burncd had some nice advantages over cdrecord: it came from the BSD tree, it had capabilities for burning DVD+RW images. Disadvantage was the limitation to ATA interface. I see the latter as a disadvantage of cdrecor

Re: burncd 'blank' not terminating ?

On Fri, Dec 29, 2006 at 09:23:06AM +1100, Peter Jeremy wrote.. > On Mon, 2006-Dec-25 16:55:54 +0100, O. Hartmann wrote: > >burncd had some nice advantages over cdrecord: it came from the BSD > >tree, it had capabilities for burning DVD+RW images. Disadvantage was > >the limitation to ATA interface.

Re: burncd 'blank' not terminating ?

On Mon, 2006-Dec-25 16:55:54 +0100, O. Hartmann wrote: >burncd had some nice advantages over cdrecord: it came from the BSD >tree, it had capabilities for burning DVD+RW images. Disadvantage was >the limitation to ATA interface. I see the latter as a disadvantage of cdrecord: It only works on SCSI

Re: [summary] Re: burncd 'blank' not terminating ?

Hello! On Tue, 26 Dec 2006, Luigi Rizzo wrote: I suggest the following two fixes: 1. change burncd.c as below, so that if CDRIOCGETPROGRESS does not return anything good, it calls CDIOCRESET to determine when the command is complete. This can be improved by calling CDIOCRESET unconditiona

Re: [summary] Re: burncd 'blank' not terminating ?

On Wed, Dec 27, 2006 at 02:33:15AM +0100, Søren Schmidt wrote: > Luigi Rizzo wrote: > > summary: there was some discussion on how to > > fix the problem, in 6.x, with "burncd -f /dev/acd0 -v blank" getting > > stuck with this message > > > > blanking CD, please wait.. > > > > This used to work

Re: [summary] Re: burncd 'blank' not terminating ?

Luigi Rizzo wrote: summary: there was some discussion on how to fix the problem, in 6.x, with "burncd -f /dev/acd0 -v blank" getting stuck with this message blanking CD, please wait.. This used to work on 4.x. 6.x changes in two places: * the ioctl handler, acd_get_progress() in /sy

Re: [summary] Re: burncd 'blank' not terminating ?

Luigi Rizzo <[EMAIL PROTECTED]> writes: > summary: there was some discussion on how to > fix the problem, in 6.x, with "burncd -f /dev/acd0 -v blank" getting > stuck with this message > > blanking CD, please wait.. > > This used to work on 4.x. > [ .. stuff deleted .. ] > > Patches below

[summary] Re: burncd 'blank' not terminating ?

summary: there was some discussion on how to fix the problem, in 6.x, with "burncd -f /dev/acd0 -v blank" getting stuck with this message blanking CD, please wait.. This used to work on 4.x. 6.x changes in two places: * the ioctl handler, acd_get_progress() in /sys/dev/ata/atapi-cd.c

Re: burncd 'blank' not terminating ?

Dmitry Pryanishnikov wrote: 1) it seems that problem is in /sys/dev/ata/atapi-cd.c code rather then in burncd utility (but I'm not 100%-sure here); 2) burncd still does _all_ things which it's useful for: it really burns CDs erases and fixates them. It just incorrectly waits for completio

Re: burncd 'blank' not terminating ?

Hello! On Mon, 25 Dec 2006, Scott Long wrote: P.S.: Don't use burncd. Use cdrecord! IMHO it isn't correct approach to avoid use of the tool _instead_ of fixing it. This way, all your tools will be broken one day ;) Sincerely, Dmitry Since this is a very old and well known issue, and it see

Re: burncd 'blank' not terminating ?

On Mon, Dec 25, 2006 at 12:00:41PM -0500, Scott Long wrote.. > O. Hartmann wrote: > >Dmitry Pryanishnikov wrote: > >>Hello! > >> > >>On Fri, 22 Dec 2006, Sergey N. Voronkov wrote: > just noticed, after upgrading to 6.2RC1, that > > luigi# burncd -f /dev/acd0 -v blank > blan

Re: burncd 'blank' not terminating ?

O. Hartmann wrote: Dmitry Pryanishnikov wrote: Hello! On Fri, 22 Dec 2006, Sergey N. Voronkov wrote: just noticed, after upgrading to 6.2RC1, that luigi# burncd -f /dev/acd0 -v blank blanking CD, please wait.. stays there forever. Eventually i gave up and ctrl-C and the application t

Re: burncd 'blank' not terminating ?

Luigi Rizzo wrote: On Mon, Dec 25, 2006 at 05:12:04PM +0200, Dmitry Pryanishnikov wrote: Hello! On Fri, 22 Dec 2006, Sergey N. Voronkov wrote: just noticed, after upgrading to 6.2RC1, that luigi# burncd -f /dev/acd0 -v blank blanking CD, please wait.. stays there forever. Eve

Re: burncd 'blank' not terminating ?

On Mon, Dec 25, 2006 at 04:55:54PM +0100, O. Hartmann wrote: > Since this is a very old and well known issue, and it seems there is no > one left solcing/developing this tool, it should be removed from the > source tree for the time it is to said broken. > burncd had some nice advantages over cdre

Re: burncd 'blank' not terminating ?

On Mon, Dec 25, 2006 at 05:12:04PM +0200, Dmitry Pryanishnikov wrote: > > Hello! > > On Fri, 22 Dec 2006, Sergey N. Voronkov wrote: > >> just noticed, after upgrading to 6.2RC1, that > >> > >>luigi# burncd -f /dev/acd0 -v blank > >>blanking CD, please wait.. > >> > >> stays there forever.

Re: burncd 'blank' not terminating ?

Dmitry Pryanishnikov wrote: > > Hello! > > On Fri, 22 Dec 2006, Sergey N. Voronkov wrote: >>> just noticed, after upgrading to 6.2RC1, that >>> >>> luigi# burncd -f /dev/acd0 -v blank >>> blanking CD, please wait.. >>> >>> stays there forever. Eventually i gave up and ctrl-C and >>> the app

Re: burncd 'blank' not terminating ?

Hello! On Fri, 22 Dec 2006, Sergey N. Voronkov wrote: just noticed, after upgrading to 6.2RC1, that luigi# burncd -f /dev/acd0 -v blank blanking CD, please wait.. stays there forever. Eventually i gave up and ctrl-C and the application terminates, and i was able to write to th

Re: burncd 'blank' not terminating ?

On Thu, Dec 21, 2006 at 09:27:17AM -0800, Luigi Rizzo wrote: > just noticed, after upgrading to 6.2RC1, that > > luigi# burncd -f /dev/acd0 -v blank > blanking CD, please wait.. > > stays there forever. Eventually i gave up and ctrl-C and > the application terminates, and i was able t

Re: burncd blank and format problems

On Sat, 15 Jul 2006, B Briggs wrote: Sorry to have to bring this up again, seems like it was an issue 4 years ago, but I don't know if it's really resolved. If I do: #burncd -f /dev/acd0 blank then burncd will sleep forever. (I have to Ctrl-C for it to exit) It doesn't really hang, but please

Re: burncd audio produces white noise

[LoN]Kamikaze wrote: > Par Leijonhufvud wrote: > > Michael A. Koerber <[EMAIL PROTECTED]> [2006.05.16] wrote: > >> 1. Starting with a known good audio CD > >> 2. Rip via dd if=/dev/acd0t01 ... etc > >> 3. burncd -f /dev/acd0 track01.cdr ... etc > > > This might be because you don't use th

Re: burncd audio produces white noise

Par Leijonhufvud wrote: > Michael A. Koerber <[EMAIL PROTECTED]> [2006.05.16] wrote: >> 1. Starting with a known good audio CD >> 2. Rip via dd if=/dev/acd0t01 ... etc >> 3. burncd -f /dev/acd0 track01.cdr ... etc > This might be because you don't use the appropriate blocksize. A more

Re: burncd audio produces white noise

Michael A. Koerber <[EMAIL PROTECTED]> [2006.05.16] wrote: > 1. Starting with a known good audio CD > 2. Rip via dd if=/dev/acd0t01 ... etc > 3. burncd -f /dev/acd0 track01.cdr ... etc I've also used this, but have some problems: there is sometimes a "blank" section in before the tracks,

Re: burncd audio produces white noise

All, Thanks for the responses. Based on your input I did find that, following the handbook, 1. Starting with a known good audio CD 2. Rip via dd if=/dev/acd0t01 ... etc 3. burncd -f /dev/acd0 track01.cdr ... etc worked just fine. Thus the MP3 to CDR conversion had to be the cause.

Re: burncd audio produces white noise

Max Laier wrote: Yeah, I've noticed that too now that you mention it. When it happened to me, I switched to using atapicam and cdrecord with the -swab parameter. Also, you may want to look at audio/mp3burn (still need to pass -swab though) I would recommend that you file a PR on this one.

Re: burncd audio produces white noise

On Tue, May 16, 2006 4:55 am, Stephen Hurd wrote: > Michael A. Koerber wrote: >> All, >> >> Once upon a time, I think with 5.x or perhaps earlier, the command >> (ATAPI drive) >> >> burncd -ef /dev/acd0 audio *.cdr fixate >> >> would produce an audio CD for me. However, under 6.0 and recentl

Re: burncd audio produces white noise

Michael A. Koerber wrote: All, Once upon a time, I think with 5.x or perhaps earlier, the command (ATAPI drive) burncd -ef /dev/acd0 audio *.cdr fixate would produce an audio CD for me. However, under 6.0 and recently 6.1 this same command produces an CD filled with white noise only. T

Re: burncd audio produces white noise

On Mon, May 15, 2006 at 08:00:48AM -0400, Michael A. Koerber wrote: > Any ideas on what I should look at to fix this problem? What kind of CPU are you using? Perhaps this is an endianness issue, and swapping bytes around using the -x option to sox might do the trick. -Albert

Re: burncd failures on RC-1?

On Fri, Apr 14, 2006 at 01:32:38PM +1200, Jonathan Chen wrote: > Hi, > > Anyone else experiencing burncd failures on RC-1? I've only just recently > cvsup'd and rebuilt, and now burncd(8) just does nothing: > > osiris-~,1:29pm# echo $CDROM > /dev/acd0 > osiris-~,1:26pm# burncd -v blan

Re: burncd and dvd-drives

On Fri, 4 Nov 2005 18:48, Dick Hoogendijk wrote: > But as almost any new computer is supplied with a dvd drive this nice > program has become quit useless. It does not support those drives. > > My question is: will it ever do? It does support DVD's, but in my experience it is a bit buggy so I norm

Re: burncd and dvd-drives

On Friday, 4. November 2005 09:18, Dick Hoogendijk wrote: > I was and am a great fan of the burncd utility. > Very fast, simple and cli.. > > But as almost any new computer is supplied with a dvd drive this nice > program has become quit useless. It does not support those drives. > > My question is

Re: burncd and dvd-drives

Dick Hoogendijk wrote: I was and am a great fan of the burncd utility. Very fast, simple and cli.. But as almost any new computer is supplied with a dvd drive this nice program has become quit useless. It does not support those drives. My question is: will it ever do? I mean, cd-rom drives are

Re: burncd and dvd-drives

On Friday 04 November 2005 00:18, you wrote: > I was and am a great fan of the burncd utility. > Very fast, simple and cli.. > > But as almost any new computer is supplied with a dvd drive this nice > program has become quit useless. It does not support those drives. > > My question is: will it eve

Re: burncd and dvd-drives

On Fri, Nov 04, 2005 at 09:18:31AM +0100, Dick Hoogendijk wrote: > I was and am a great fan of the burncd utility. > Very fast, simple and cli.. Cdrecord is also a cli program. And you probably have it installed, because mkisofs is in the same port. :-) It does need atapicam, though. > But as alm

Re: burncd and dvd-drives

/usr/ports/sysutils/cdrtools for mkisofs and /usr/ports/sysutils/dvd+rw-tools for growisofs and DVD media creation. It requires cdrtools for creating FS for DVD. Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] On Fri, 4 Nov 2005, Dick Hoogendijk wrote: I was and am a great f

Re: burncd input output error

On Sun, Sep 18, 2005 at 10:09:54AM +0200, Andreas Klemm wrote: > I see this needs more investigation. Maybe it has to deal with > the exit status I had (!=0). > > I will do a test burn now with burncd reading from a file > instead from a pipe. Let's see if it behaves different then. > > Hmm even

Re: burncd input output error

On Sat, Sep 17, 2005 at 08:30:33PM -0700, Andrew Sparrow wrote: > On Sat, Sep 17, 2005 at 12:42:39PM -0400, Chuck Swiger wrote: > > Andreas Klemm wrote: > > [ ... ] > > > - burncd leaves cdrom in a way that CD cannot be mounted > > > after burning, one has to open and re-close CD tray manually >

Re: burncd input output error

On Sat, Sep 17, 2005 at 12:42:39PM -0400, Chuck Swiger wrote: > Andreas Klemm wrote: > [ ... ] > > - burncd leaves cdrom in a way that CD cannot be mounted > > after burning, one has to open and re-close CD tray manually > > before one is able to mount the frshly burned CD. > > This is an issu

Re: burncd input output error

Andreas Klemm wrote: [ ... ] - burncd leaves cdrom in a way that CD cannot be mounted after burning, one has to open and re-close CD tray manually before one is able to mount the frshly burned CD. This is an issue with the drive firmware more than anything to do with software. Most drives

Re: burncd input output error

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, Sep 17, 2005 at 03:03:44PM +0200, Andreas Klemm wrote: > 2 problems with FreeBSD 5.4 stable: > > - burncd has strange exit status when reading ISO file from stdin > according to manual page possible: >[...] >gunzip -c file.iso.gz |

Re: [SOLVED] Re: burncd: Device busy error.

On Thu, 14 Jul 2005 15:50:43 +0200, Yann Golanski <[EMAIL PROTECTED]> wrote: Just in case anyone else has the same problem and wants a solution. 1- Recompile and install your kernel with the following options: device atapicam device ata device scbus device cd device pass 2- Go to you

[SOLVED] Re: burncd: Device busy error.

Just in case anyone else has the same problem and wants a solution. 1- Recompile and install your kernel with the following options: device atapicam device ata device scbus device cd device pass 2- Go to your MP3 dir. 3- Converts spaces to underscores. for i in *.mp3; do mv "$i" `echo

Re: burncd: Device busy error.

On 7/14/05, Yann Golanski <[EMAIL PROTECTED]> wrote: > I am trying to burn to my CD drive and I keep getting the same error, > namely "only wrote -1 of 37632 bytes: Device busy". I've been able to > write to that dive from FreeBSD in the past but now, nada. > # burncd -f /dev/acd0 audio test.wav

Re: burncd: ioctl(CDRIOCFIXATE): Input/output error

On Tue, 2005-01-11 at 16:55 +0200, Nikolay Pavlov wrote: > Hi, freebsd users. > After upgrade from 4.10 to 5.3, I can't write disks > with burncd tool. I see this error: > > # burncd -emv -s 10 data akt.iso fixate > adding type 0x08 file akt.iso size 554522 KB 277261 blocks > next writeable

Re: burncd freeze system

On Tue, 2005-01-04 at 18:10 +1100, Peter Jeremy wrote: > On Tue, 2005-Jan-04 00:20:59 +0100, Norbert Augenstein wrote: > >i have tried to burn an iso of 26MB of size, and my system locks > >up so i have to reboot. > > /var/log/messages is unlikely to include the last 30 seconds or so of >

Re: burncd freeze system

On Tue, 2005-Jan-04 00:20:59 +0100, Norbert Augenstein wrote: >i have tried to burn an iso of 26MB of size, and my system locks >up so i have to reboot. /var/log/messages is unlikely to include the last 30 seconds or so of logging following a crash. Try running burncd from the console and

Re: burncd and mount_cd9660

On Sun, 24 Oct 2004 06:28, Jonathan Chen wrote: > > Some cd-writers *require* that you eject the newly-burnt cd and > > re-insert it, before the drive will read it. This _might_ be the problem > > you are seeing, if the cd image is correct (iso 9660). > > If only it were so... I forgot to add the o

Re: burncd and mount_cd9660

On Sat, Oct 23, 2004 at 11:37:51AM +0200, Torfinn Ingolfsen wrote: > On Sat, 23 Oct 2004 17:49:28 +1300 > Jonathan Chen <[EMAIL PROTECTED]> wrote: > > > I'm running 5.3-STABLE, and seem to have a problem where if I run > > burncd, I am not able to mount the recently burnt CD. If I > > reboot the b

Re: burncd and mount_cd9660

On Sat, Oct 23, 2004 at 10:56:24AM +0300, Nikolay Pavlov wrote: > Hi, Jonathan. > > On Saturday, 23 October 2004 at 17:49:28 +1300, Jonathan Chen wrote: > > Hi, > > > > I'm running 5.3-STABLE, and seem to have a problem where if I run > > burncd, I am not able to mount the recently burnt CD. If I

Re: burncd and mount_cd9660

On Sat, 23 Oct 2004 17:49:28 +1300 Jonathan Chen <[EMAIL PROTECTED]> wrote: > I'm running 5.3-STABLE, and seem to have a problem where if I run > burncd, I am not able to mount the recently burnt CD. If I > reboot the box, the mount on the CDwill succeed. I am experiencing > this on 2 very differe

Re: burncd and mount_cd9660

Hi, Jonathan. On Saturday, 23 October 2004 at 17:49:28 +1300, Jonathan Chen wrote: > Hi, > > I'm running 5.3-STABLE, and seem to have a problem where if I run > burncd, I am not able to mount the recently burnt CD. If I > reboot the box, the mount on the CDwill succeed. I am experiencing > this o

Re: burncd to makcd DVD-R backups on 4.X-STABLE?

On Wed, 9 Apr 2003 14:43:43 -0500 (EST) FreeBSD <[EMAIL PROTECTED]> wrote: F> Are there plans to implement the DVD capabilities of burncd F> in FreeBSD 5.X-CURRENT into 4.X-STABLE? We need to make F> backups to DVD-R using an IDE burner. Is upgrading to F> 5.X-CURRENT our only option? N

Re: burncd: ioctl(CDRIOCFLUSH): Input/output error

Richard Mahoney wrote: I am having trouble burning CD-R's with the following: [ ... ] Do any readers have any idea what the issue may be. This problem has been occuring on and off for a while but appears to be becoming worse. What does "atacontrol mode 1" show? Is your burner running in PIO, or in

Re: burncd audio problem

thank you, looking forward for this patch. --- Vlad On Sun, Jun 09, 2002 at 12:41:43PM -0500, David Syphers wrote: > On Saturday 08 June 2002 03:42 pm, Mikko Tyolajarvi wrote: > > In local.freebsd.stable you write: > > > > >FreeBSD ariel.phys.wesleyan.edu 4.6-RC FreeBSD 4.6-RC #32: Wed May 29 >

Re: burncd can't/won't write from pipe?

On Mon, 25 Mar 2002, Andrew Heybey wrote: AH> I'm trying 4.5-RELEASE plus Soren's patches for the new ata driver and AH> burncd. I just got a CD-RW drive, so I don't know if this used to AH> work or not. AH> AH> The following does not work: AH> AH> mkisofs -R | burncd -s 8 data - fixate

Re: Burncd errors...

In local.freebsd.stable you write: >On Wed, 31 Oct 2001, Mikko Tyolajarvi wrote: >> >acd0: CD-RW at ata1-master using PIO4 >> >> Not that it is any help to you, but I have the same problem (data >> burns ok, audio does not) with an 8083B. And apparently we're not >> alone:

Re: Burncd errors...

On Wed, Oct 31, 2001 at 07:51:37PM -0800, Mikko Tyolajarvi wrote: > In local.freebsd.stable you write: > > >I'm trying to write a small audio file to a CD. Burncd refuses to > >do it... for instance... if I do something like: > > >burncd -f /dev/acd0c -s 1 audio audio.raw fixate > > [...] > >

Re: burncd: ioctl(CDRIOCCLOSEDISK)

On Wed, 11 Jul 2001, Søren Schmidt wrote: > It seems Randall Hopper wrote: > > Running 4.3-STABLE from 6/25/01, and just tried burning a CD on a new > > Sony CRX140E CD-RW (8x4x32) ATAPI drive using burncd: > > > > # burncd -s 8 -t -f /dev/acd0c data firewall.iso fixate > > next wr

Re: "burncd, mkisofs, multisession" doesn't work for more than 2 sessions

On Mon, Oct 22, 2001 at 10:22:07AM +0300, Victor Ivanov wrote: > On Mon, Oct 22, 2001 at 03:14:11PM +0800, Eugene Grosbein wrote: > > Nuno Teixeira wrote: > > > > > > Hello to all, > > > > > > I'm trying to use burncd with multisession with no success. I will try to > > > explain my proble

Re: "burncd, mkisofs, multisession" : BUG 27593

- From: "Neil Long" <[EMAIL PROTECTED]> To: "Nuno Teixeira" <[EMAIL PROTECTED]> Sent: Monday, October 22, 2001 4:51 PM Subject: Re: "burncd, mkisofs, multisession" doesn't work for more than 2 sessions > Unless msinfo can give intermediate session

Re: burncd makes computer reboot!

Bad Memory ? > i just burned a CD from an ISO image, when it finished burning the CD burncd > gave the following error: > > burncd: ioctl(CDRIOCCLOSEDISK): Inapproprate iotl for device > > i ran it with the followning command: > > burncd -f /dev/acd0c data data.iso fixate > > what am i do

Re: burncd...

This is using tcsh, so it has its own 'nice' command... On Mon, Aug 21, 2000 at 06:44:59PM +0800, Trent Nelson wrote: > > > Michael Matsumura wrote: > > > [root:~]# nice -20 burncd -s 2 -f /dev/acd1c data /usr/backup.iso fixate > ^^^ > > You're running 'burncd' at the

Re: burncd...

Michael Matsumura wrote: > [root:~]# nice -20 burncd -s 2 -f /dev/acd1c data /usr/backup.iso fixate ^^^ You're running 'burncd' at the lowest possible priority (man nice(1)). Try `nice --20 ...'. > Michael Matsumura > [EMAIL PROTECTED] Regards,

Re: burncd...

Michael Matsumura wrote: > [root:~]# ls -l /usr/share/examples/atapi/ > total 0 > > [root:~]# ls -l /usr/src/share/examples/atapi > gnuls: /usr/src/share/examples/atapi: No such file or directory I guess it was removed for 4.x since burncd was added. The burndata script is basically just: dev

Re: burncd...

I had similar trouble, but can burn under windows (except 2k which is buggy) j. -- Close your eyes. Now forget what you see. What do you feel? -- My heart. -- Come here. -- Your heart. -- See? We're exactly the same. Jon Smith -- Senior Math Major @ Purdue On Sat, 19 Aug 2000, M

wd vs. ata (was Re: BurnCD)

On 2 May, Rod Taylor wrote: = As a side note to this long conversation, I'll mention that I've = downgraded that box back to 3.4 and it now works properly again. >From my experience, you could've just used the old wd driver instead of the new ata stuff and ignore the config's warnings. I

Re: BurnCD

Jens Fallesen writes: > Rod Taylor wrote: > > > However, I did the upgrade to v4 shortly after moving, so perhaps the > > drive got knocked around during that time. > > I wouldn't go for that explanation--the exact same thing happened on > my machine after going to 4.x and I haven't move

RE: BurnCD

I have the same problem, running 4.0 STABLE from last friday! this is the first try to get some CD's burned after my 3->4 upgrade on a "ATAPI only" machine. my home box have upgraded well and still working as before! thanks FreeBSD people. ]:) are this related to the wdc-->ata change? On 16-Ap