Re: burncd issue

[Polytropon]

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

[Dánielisz László]

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

[Dánielisz László]

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

[Dánielisz László]

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"

Re: burncd

[Mel Flynn]

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

[David M. Patronis]

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

[RW]

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"

Re: Burncd & 700MB rw/cd

[Al Plant]

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

[Polytropon]

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]"

Re: burncd error?

[Polytropon]

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]"

Re: burncd on FreeBSD-6.2

[Dieter]

> >> > 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

[sac]

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

[Paul Schmehl]

--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

[sac]

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

[Paul Schmehl]

--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/

Re: burncd makes disk that is unmountable

[Dieter]

> > > > > > 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

[Dieter]

> > > > 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

[youshi10]

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

[Dieter]

> > 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

[Jerry McAllister]

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

[Garrett Cooper]

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

[Jerry McAllister]

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]"

Re: burncd error

[Pablo Mora]

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

[Pablo Mora]

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

[Chuck Swiger]

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

[Mikhail Goriachev]

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

[Napoleon Dynamite]

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

[Josh Paetzel]

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

[Kevin Kinsey]

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

[John Nielsen]

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]"

Re: burncd fails: Input output error

[Lars Stokholm]

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

[Lars Stokholm]

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

[Warren Block]

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]"

Re: burncd multiple files

[Fabian Keil]

dick hoogendijk <[EMAIL PROTECTED]> wrote:

> One question still: you mention cdrtools-devel. What are the pro's/cons
> of a devel port above the normal sysutils/cdrtools.

If you take cdrtools-devel, you get the latest version
(ATM cdrtools-2.01.01a03). The normal cdrtools port contains
the latest stable version (ATM cdrtools-2.01).

cdrtools-2.01 have fewer features, for example its cdrecord can't use
gigarec, and contain a cdda2wav version which doesn't work suid
under BSD.

In general cdrtools alpha versions are quite stable.

See  and

for more information.

Fabian
-- 
http://www.fabiankeil.de/


pgp0yKJDBc740.pgp
Description: PGP signature

Re: burncd multiple files

[dick hoogendijk]

On Sun, 21 Aug 2005 18:33:32 +0200
Fabian Keil <[EMAIL PROTECTED]> wrote:

> dick hoogendijk <[EMAIL PROTECTED]> wrote:
> 
> > I have a directory full with mp3 files and want to burn them to CD with
> > burncd. Is there an easy way to do this in stead of writing down all
> > filenames to do a "burncd  data file1 file2 file3 fixate" ??

> If you want to be able to read back the data later,
> you should consider creating an image with mkisofs first.
> 
> It's in /usr/ports/sysutils/cdrtools-devel.

Thanks for the reply. Though I feel I need to admit I was absendminded
when I asked the question. I really don't know why I forgot the fact I
need to make an ISO file before I can burn my mp3 files to cd. Sorry.

One question still: you mention cdrtools-devel. What are the pro's/cons
of a devel port above the normal sysutils/cdrtools.

-- 
dick -- http://nagual.st/ -- PGP/GnuPG key: F86289CE
++ Running FreeBSD 4.11-stable ++ FreeBSD 5.4
+ Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilja
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd multiple files

[Fabian Keil]

dick hoogendijk <[EMAIL PROTECTED]> wrote:

> I have a directory full with mp3 files and want to burn them to CD with
> burncd. Is there an easy way to do this in stead of writing down all
> filenames to do a "burncd  data file1 file2 file3 fixate" ??
> 
> If it can be done with burncd I'll be happy. If not I have to use one of
> those X programs. (hope not; I like burncd)

If you want to be able to read back the data later,
you should consider creating an image with mkisofs first.

It's in /usr/ports/sysutils/cdrtools-devel.

Read the handbook for more information:


Fabian
-- 
http://www.fabiankeil.de/


pgp5lcQrpuOWw.pgp
Description: PGP signature

Re: burncd - verify burn

[Fabian Keil]

[EMAIL PROTECTED] (Gary W. Swearingen) wrote:

> Brian Henning <[EMAIL PROTECTED]> writes:
> 
> > I would like to know a process to verify that I my cd burner has
> > burned an ISO file correctly with burncd. I know I can take some
> > precautions like checking the md5sum of the iso during a transfer from
> > the Internet. I also read on the Internet that burncd does puts some
> > extra padding at the end of the cd. I am not sure if that is true or
> > not. Could someone tell me how to verify a cd burn?
> 
> Here's a crummy script I just used to burn and verify a CD, but I've
> only tested it with the "cdrecord" setup.  Older versions of it worked
> with "burncd" on older OS versions, but I can tell you that the reason
> I'm using "cdrecord" is that my manual efforts to do this with
> "burncd" on 5.4-RELEASE (and maybe 5.4-STABLE a couple weeks ago)
> failed, because I couldn't "dd" a CD burned with "burncd". (IE, I
> couldn't sucessfully "dd" /dev/acd0, while I could "dd" /dev/cd0).
> 
> (Search this for "diff" to find the "verify".  ISO images generally
> get an extra two blocks of something on the CD "for run-out". See
> "-isosize" description of "cdrecord" manpage.)

Not generally, only if you burn in TAO mode.

BTW you can use readcd -c2scan to check the burning quality at
a deeper level and there even is a patch out there to make reading
c1 error pointers possible. Haven't tested it though. 

Fabian
-- 
http://www.fabiankeil.de/


pgphNPDzWKRES.pgp
Description: PGP signature

Re: burncd - verify burn

[Gary W. Swearingen]

Glenn Dawson <[EMAIL PROTECTED]> writes:

> did you use bs=2048 when dd'ing from /dev/acd0?

Sure did.  And didn't read too many blocks.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd - verify burn

[Glenn Dawson]

At 10:38 AM 7/25/2005, Gary W. Swearingen wrote:

Brian Henning <[EMAIL PROTECTED]> writes:

> I would like to know a process to verify that I my cd burner has
> burned an ISO file correctly with burncd. I know I can take some
> precautions like checking the md5sum of the iso during a transfer from
> the Internet. I also read on the Internet that burncd does puts some
> extra padding at the end of the cd. I am not sure if that is true or
> not. Could someone tell me how to verify a cd burn?

Here's a crummy script I just used to burn and verify a CD, but I've
only tested it with the "cdrecord" setup.  Older versions of it worked
with "burncd" on older OS versions, but I can tell you that the reason
I'm using "cdrecord" is that my manual efforts to do this with
"burncd" on 5.4-RELEASE (and maybe 5.4-STABLE a couple weeks ago)
failed, because I couldn't "dd" a CD burned with "burncd". (IE, I
couldn't sucessfully "dd" /dev/acd0, while I could "dd" /dev/cd0).


did you use bs=2048 when dd'ing from /dev/acd0?

-Glenn

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd - verify burn

[Gary W. Swearingen]

Brian Henning <[EMAIL PROTECTED]> writes:

> I would like to know a process to verify that I my cd burner has
> burned an ISO file correctly with burncd. I know I can take some
> precautions like checking the md5sum of the iso during a transfer from
> the Internet. I also read on the Internet that burncd does puts some
> extra padding at the end of the cd. I am not sure if that is true or
> not. Could someone tell me how to verify a cd burn?

Here's a crummy script I just used to burn and verify a CD, but I've
only tested it with the "cdrecord" setup.  Older versions of it worked
with "burncd" on older OS versions, but I can tell you that the reason
I'm using "cdrecord" is that my manual efforts to do this with
"burncd" on 5.4-RELEASE (and maybe 5.4-STABLE a couple weeks ago)
failed, because I couldn't "dd" a CD burned with "burncd". (IE, I
couldn't sucessfully "dd" /dev/acd0, while I could "dd" /dev/cd0).

(Search this for "diff" to find the "verify".  ISO images generally
get an extra two blocks of something on the CD "for run-out". See
"-isosize" description of "cdrecord" manpage.)

#!/bin/ksh -o posix

## mkisocd [-blank] - file_name
#
## This burns and compares a file to the beginning of the write-only CD (CD-R).
## This must be run by superuser.
#
#  Note that the CD burning software (burncd) often writes an ISO CD at least a 
block bigger than the file.
#  I'm not sure why. (It's not a hard disk file system block size thing.)

#BURNER=/usr/local/bin/readcd
BURNCD=/usr/sbin/burncd
CDRECORD=/usr/local/bin/cdrecord
BURNER=$BURNCD
BURNER=$CDRECORD

if [ "${1}" == -blank ]; then
if [ ${BURNER} == ${BURNCD} ]; then
BLANK="blank"
else
BLANK="blank=fast"
fi
shift
else
BLANK=
fi
TEMP="${1#-}"
if [ "${TEMP}" != "$1" ]; then
SPEED="${TEMP}"
shift
else
echo 'WARNING: nothing done; speed must be given as "-factor" (eg -16)'
exit 1
fi

FILENAME="$1"

#DEBUG; echo "SPEED = '$SPEED', FILENAME = '$FILENAME'"
#exit

if [ ! -r "${FILENAME}" -o ! -f "${FILENAME}" ]; then
echo "ERROR: The argument, \"${FILENAME}\", is not a readable regular file. 
Nothing done."
exit 2
fi

## TBD REMOVE
##blocks=$(( $(ls -l "${FILENAME}" | awk '{print $5;}') / ${blockbytes} ))

blockbytes=2048  ## Block size of ISO CDs. Nothing else will work (esp, in dd 
command).
filebytes=$(stat -f "%z" "${FILENAME}")
fileblocks=$(( ${filebytes} / ${blockbytes} ))
if [ $(( ${fileblocks} * ${blockbytes} )) != ${filebytes} ]; then
echo "ERROR: '${FILENAME}' is not a multiple of the CD blocksize, 
${blockbytes}. Nothing done."
exit 3
fi

echo "WARNING: About to burn this file (${filebytes} bytes, ${fileblocks} 
blocks) to CD."
ls -l "${FILENAME}"
echo -n "Ensure CD in burner and enter \"y\" to continue, else to abort: "

read
if [ "$REPLY" != "y" ]; then
echo "You entered \"$REPLY\", so the command is aborting with nothing done."
exit 4
fi

if [ ${BURNER} == ${BURNCD} ]; then
DEV=/dev/acd0
time burncd -f ${DEV} -s ${SPEED} ${BLANK} data "${FILENAME}" fixate
else
DEV=/dev/cd0  ## cdrecord's default SCSI "dev" is in 
/usr/local/etc/
time cdrecord -v speed=${SPEED} ${BLANK} "${FILENAME}"
fi

if [ $? != 0 ]; then
echo "ERROR: $BURNER failed. See above error message."
exit 5
fi

beep 2&

sleep 2  ## ??

echo "NOTICE: Comparing \"${FILENAME}\" to the just-written CD. Please wait..."
if dd if=${DEV} count=${fileblocks} bs=${blockbytes} | diff - "${FILENAME}"; 
then
echo "NOTICE: Comparison OK.  The CD seems OK."
else
echo "ERROR: The CD and file differred."
fi

echo done

beep 3&

exit 0

# The End.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd syntax for burning dvd ???

[P.U.Kruppa]

On Sun, 12 Jun 2005, David Kelly wrote:



In the future I suggest using readcd from the cdrtools port. It does a bit 
better handling end of device and recognizing multisession.

Thanks!


Now I would like to burn dvd.iso on a fresh dvd+rw medium.
Could someone be so nice and give me the correct command line for
this - seems I am too stupid to understand the man pages :-( .
Months ago I went down this same path and simply couldn't get burncd to write 
my DVD. Then considered how the Handbook demonstrates using growisofs I put 2 
+ 2 together and realized burncd probably isn't fully ready for DVDs.
Yes, but I thought it would be better to ask to ask before 
blaming other people :-)


Regards,

Uli.



*
* Peter Ulrich Kruppa - Wuppertal - Germany * 
*

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd syntax for burning dvd ???

[David Kelly]

On Jun 12, 2005, at 6:36 AM, Peder Blom wrote:


On Sun, 12 Jun 2005 12:08:21 +0200 (CEST)
"P.U.Kruppa" <[EMAIL PROTECTED]> wrote:



Hello!

I created an .iso file from a dvd by
 # dd if=/dev/acd0 of=dvd.iso bs=2048


In the future I suggest using readcd from the cdrtools port. It does  
a bit better handling end of device and recognizing multisession.



Now I would like to burn dvd.iso on a fresh dvd+rw medium.
Could someone be so nice and give me the correct command line for
this - seems I am too stupid to understand the man pages :-( .

Thanks,

Uli.





The FreeBSD Handbook (eg. at www.freebsd.org) has detailed  
instructions
on how to burn different kinds of dvd:s. See chapter "16.7 Creating  
and

Using Optical Media".


Months ago I went down this same path and simply couldn't get burncd  
to write my DVD. Then considered how the Handbook demonstrates using  
growisofs I put 2 + 2 together and realized burncd probably isn't  
fully ready for DVDs.


--
David Kelly N4HHE, [EMAIL PROTECTED]

Whom computers would destroy, they must first drive mad.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd syntax for burning dvd ???

[Tsampros Leonidas]

On Sun, Jun 12, 2005 at 01:29:00PM +0200, P.U.Kruppa wrote:
> On Sun, 12 Jun 2005, Tsampros Leonidas wrote:
> 
> >On Sun, Jun 12, 2005 at 12:08:21PM +0200, P.U.Kruppa wrote:
> >>Hello!
> >>
> >>I created an .iso file from a dvd by
> >># dd if=/dev/acd0 of=dvd.iso bs=2048
> >>Now I would like to burn dvd.iso on a fresh dvd+rw medium.
> >>Could someone be so nice and give me the correct command line for
> >>this - seems I am too stupid to understand the man pages :-( .
> >>
> >>Thanks,
> >
> >I think that this one will work:
> >
> >burncd -e -f /dev/acd0 -s max data fixate dvdrw dvd.iso
> No, that doesn't, but ...
> 
> >Why don't you use growisofs ?
> Because I didn't know it yet :-)
> 
> >You can install it through the ports at
> >sysutils/dvd+rw-tools . To write tha same iso you would use the
> >following command:
> >
> >growisofs -speed=N -dvd-compat -Z /dev/dvd=image.iso

where N is the speed you want to burn the dvd ( 4 or 8 are common
speeds)

> That works, when I use SCSI emulation for my ATAPI burner:
> # growisofs -dvd-compat -Z /dev/cd0=image.iso
> 
> I'll find out about -speed later.
> 
> Thanks!
> 
> Uli.
> 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd syntax for burning dvd ???

[Peder Blom]

On Sun, 12 Jun 2005 12:08:21 +0200 (CEST)
"P.U.Kruppa" <[EMAIL PROTECTED]> wrote:

> Hello!
> 
> I created an .iso file from a dvd by
>   # dd if=/dev/acd0 of=dvd.iso bs=2048
> Now I would like to burn dvd.iso on a fresh dvd+rw medium.
> Could someone be so nice and give me the correct command line for 
> this - seems I am too stupid to understand the man pages :-( .
> 
> Thanks,
> 
> Uli.
> 


The FreeBSD Handbook (eg. at www.freebsd.org) has detailed instructions
on how to burn different kinds of dvd:s. See chapter "16.7 Creating and
Using Optical Media".

Good Luck

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

[gaghiel: Re: burncd syntax for burning dvd ???]

[Tsampros Leonidas]

- Forwarded message from Tsampros Leonidas  -

Date: Sun, 12 Jun 2005 14:02:31 +
From: Tsampros Leonidas 
Subject: Re: burncd syntax for burning dvd ???
To: "P.U.Kruppa" <[EMAIL PROTECTED]>
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.9i

On Sun, Jun 12, 2005 at 12:08:21PM +0200, P.U.Kruppa wrote:
> Hello!
> 
> I created an .iso file from a dvd by
>   # dd if=/dev/acd0 of=dvd.iso bs=2048
> Now I would like to burn dvd.iso on a fresh dvd+rw medium.
> Could someone be so nice and give me the correct command line for 
> this - seems I am too stupid to understand the man pages :-( .
> 
> Thanks,

I think that this one will work:

burncd -e -f /dev/acd0 -s max data fixate dvdrw dvd.iso 

No guarantees though as i haven't tried it. Why don't you use
growisofs ? You can install it through the ports at
sysutils/dvd+rw-tools . To write tha same iso you would use the
following command:

growisofs -speed=N -dvd-compat -Z /dev/dvd=image.iso

Tested and always works. 
.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd, eject before read

[Tom Norris]

Tobias Fendin wrote:

Hi folks.

I've just burned an iso to a cd successfully.
But before I could mount it, I had to eject the cd-tray and then close 
it, before I could mount it.


I got this error message from mount:
cd9660: /dev/acd0: Input/output error

I wonder if it's a bug or feature.

   - Tobias
I believe that's a hardware limitation.  I know a few drives support 
burning/reading without ejecting, but I'm not sure which ones do.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd, eject before read

[Charles Swiger]

On Jun 9, 2005, at 6:04 PM, Tobias Fendin wrote:

I've just burned an iso to a cd successfully.
But before I could mount it, I had to eject the cd-tray and then  
close it, before I could mount it.


I got this error message from mount:
cd9660: /dev/acd0: Input/output error

I wonder if it's a bug or feature.


Most CD-burners won't re-read the CD's table-of-contents after  
burning an image, until you eject the device.  However, you might be  
able to use atacontrol to nudge the drive hard enough to take another  
look.


Arguably this is a bug with the CD-ROM firmware, but it's common  
enough to not be surprising.


--
-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 problems

[Steven Friedrich]

On Thursday 02 June 2005 05:24 pm, Steven Friedrich wrote:
> I've created a directory tree in /usr/freeBSD and it has directories for
> each of my four systems; lightning, daemon, gandalf, and freakinBSD.  Each
> of those has subdirectories like /etc, and so on.
>
> I used mkisofs -R -o ~admin/cd1.iso /usr/freeBSD
>
> then I used vnconfig and mount to look at the image before burning it:
> vnconfig -e vn0c ~admin/cd1.iso
> mount_cd9660 /dev/vn0c /cdrom
>
> and then I burned it:
> burncd data ~admin/cd1.iso fixate
>
> But when I try to mount the CD, using:
> mount_cd9660 /dev/acd0c /cdrom
> I get: 
> mount_cd9660: /dev/acd0c: Input/output error
>
> The files you hand to burncd are "image" files.  Does that mean ISO images
> or did I miscontrue the man page?

here's the error displayed on the console
acd0: READ_BIG - MEDIUM ERROR asc=0x11 ascq=0x06 error=0x00


-- 
i386 FreeBSD 4.11-STABLE
There are 10 types of people in this world. Ones that understand binary and 
then, the others.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd problems

[Steven Friedrich]

On Thursday 02 June 2005 05:24 pm, Steven Friedrich wrote:
> I've created a directory tree in /usr/freeBSD and it has directories for
> each of my four systems; lightning, daemon, gandalf, and freakinBSD.  Each
> of those has subdirectories like /etc, and so on.
>
> I used mkisofs -R -o ~admin/cd1.iso /usr/freeBSD
>
> then I used vnconfig and mount to look at the image before burning it:
> vnconfig -e vn0c ~admin/cd1.iso
> mount_cd9660 /dev/vn0c /cdrom
>
> and then I burned it:
> burncd data ~admin/cd1.iso fixate
>
> But when I try to mount the CD, using:
> mount_cd9660 /dev/acd0c /cdrom
> I get: 
> mount_cd9660: /dev/acd0c: Input/output error
>
> The files you hand to burncd are "image" files.  Does that mean ISO images
> or did I miscontrue the man page?

here's the error displayed on the console
acd0: READ_BIG - MEDIUM ERROR asc=0x11 ascq=0x06 error=0x00


-- 
i386 FreeBSD 4.11-STABLE
There are 10 types of people in this world. Ones that understand binary and 
then, the others.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd: "device busy" error when writing .iso

[Jason Morgan]

On Wed, Jan 12, 2005 at 01:42:43PM -0500, Jason Morgan wrote:
> I am attempting to burn an .iso of the 5.3 mini distribution and keep 
> running into the following error:
> 
> # burncd -f /dev/acd0 data 5.3-RELEASE-i386-miniinst.iso fixate
> next writeable LBA 0
> writing from file 5.3-RELEASE-i386-miniinst.iso size 274400 KB
> written this track 640 KB (0%) total 640 KB
> only wrote -1 of 32768 bytes: Device busy
> 
> fixating CD, please wait..
> 
> I have verified that the drive is working and is accessible.  I have 
> tried different media and keep running into the same result.
> 
> # dmesg | grep acd0
> acd0: DVDR  at ata1-master PIO4
> 
> This is a new drive, that I just recently installed.
> 
> Oh, I'm running FreeBSD 5.2.1-RELEASE-p11 #7.
> 
> Any suggestions?  I've only burned CDs with FreeBSD a few times and 
> never on this system, so I'm kinda a newb.
> 
> Thanks for your time.

I finally solved the problem.  I had to include "device atapicam" in my kernel, 
then used cdrecord instead of burncd, 
using the drive as a scsi device.  Hope this info will help some newb in the 
future.

Cheers. 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd problem err=16 any ideas?

[Subhro]

On Wed, 1 Sep 2004 02:50:36 +0530, Subhro <[EMAIL PROTECTED]> wrote:
> On Tue, 31 Aug 2004 16:05:13 -0500, michael <[EMAIL PROTECTED]> wrote:
> > Im pretty sure Im using a 40 conductor type, as for using the same cable
> > for a Hard drive then cd rom they have there own separate cables,
> > Primary goes to the hard drive, secondary is to the cd rom and i dont
> > use a floppy.  Im not sure if the cd rom is set to slave ( manually )
> > but im going to check that tonight. The Drive does support the buffer
> > under run error protection, ill give you the whole specs of my system,
> >
> > Amd 146 Opteron 2.0 ghz
> > Asus SK8V Motherboard
> > 1024mb of ram
> > Sony DRU-530A Cd/Dvd Burner ( i have that model number memorized now
> > thanks to my recent problems with it )
> > Here are the results from the sysctl command:
> >
> > <118>mtree -deU -f /usr/src/etc/mtree/BSD.sendmail.dist -p /
> > <118> sendmail
> > <118> sendmail-clientmqueue
> > hw.ata.ata_dma: 1
> > hw.ata.atapi_dma: 0
> > <118>mtree -deU -f /usr/src/etc/mtree/BSD.sendmail.dist -p /
> > <118> sendmail
> > <118> sendmail-clientmqueue
> >
> > If you need anything else let me know im gonna pop open the box later to
> > make sure the cdrom is set to slave.
> >
> > Michael
> >
> 
> cat >> /boot/loader.conf 
> 
> hw.ata.atapi_dma=1
> 
> 
> reboot 
> 
> Does it remain?
> 
> And check the drive ordering. Most likely that is the problem.
> 

Also insist on going for a 80 conductor cable instead of the 40
conductor one. They are much better and really worth the bucks.

Regards
S.


-- 
Subhro Sankha Kar
School of Information Technology
Block AQ-13/1 Sector V
ZIP 700091
India
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd problem err=16 any ideas?

[Subhro]

On Tue, 31 Aug 2004 16:05:13 -0500, michael <[EMAIL PROTECTED]> wrote:
> Im pretty sure Im using a 40 conductor type, as for using the same cable
> for a Hard drive then cd rom they have there own separate cables,
> Primary goes to the hard drive, secondary is to the cd rom and i dont
> use a floppy.  Im not sure if the cd rom is set to slave ( manually )
> but im going to check that tonight. The Drive does support the buffer
> under run error protection, ill give you the whole specs of my system,
> 
> Amd 146 Opteron 2.0 ghz
> Asus SK8V Motherboard
> 1024mb of ram
> Sony DRU-530A Cd/Dvd Burner ( i have that model number memorized now
> thanks to my recent problems with it )
> Here are the results from the sysctl command:
> 
> <118>mtree -deU -f /usr/src/etc/mtree/BSD.sendmail.dist -p /
> <118> sendmail
> <118> sendmail-clientmqueue
> hw.ata.ata_dma: 1
> hw.ata.atapi_dma: 0
> <118>mtree -deU -f /usr/src/etc/mtree/BSD.sendmail.dist -p /
> <118> sendmail
> <118> sendmail-clientmqueue
> 
> If you need anything else let me know im gonna pop open the box later to
> make sure the cdrom is set to slave.
> 
> Michael
> 

cat >> /boot/loader.conf 

hw.ata.atapi_dma=1


reboot 

Does it remain?

And check the drive ordering. Most likely that is the problem.

Regards
S.
-- 
Subhro Sankha Kar
School of Information Technology
Block AQ-13/1 Sector V
ZIP 700091
India
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd problem err=16 any ideas?

[Subhro]

What type of ATA cable are you using? The 40 conductor type or the 80
conductor type?

Does your burner support some kind of underburn protection?

Could you paste "sysctl -a | grep dma" without the "s ?
 
FreeBSD requires IDE drives to be fixed on the cable in a particular
order, ie the master drive goes in one end and the slave comes in the
middle. It is recommended not to reply on CS and assign the drives to
be master/slave the hard way, err I meant the manual way. Also if you
intend to burn CDs/DVDs "on the fly" then the source and the
destination drives should not be on the same Bus. Could you tell us
about your setup?

Regards
S.

On Mon, 30 Aug 2004 21:46:33 -0500, michael <[EMAIL PROTECTED]> wrote:
> On another note too, it is burning part of the cd, on my attempts i
> think i completed about 20% maximum, something missing or not enabled in
> the kernel would still cause this ?
> 
> 
> 
> >Are you running the GENERIC kernel? If not have you included support
> >for the CD file system? Also did you put something non standard in
> >/etc/make.conf?
> >
> >Regards
> >S.
> >
> >On Mon, 30 Aug 2004 15:56:54 -0500, michael <[EMAIL PROTECTED]> wrote:
> >
> >
> >>Im running freebsd 4.10 with a sony cd/dvd burner combo (DRU-530A) im
> >>using burncd -f /dev/acd0c -s max -e data imagefile.iso fixate , i have
> >>tried to lower the speed to 1x and 8x and i get the same problem  ill
> >>include the error with -v verabos output maybe it will help ( does
> >>burncd log somewhere there might be more about the error message that
> >>might help this problem out? )
> >>
> >>adding type 0x08 file permfiles.iso size 8992 KB 4496 blocks
> >>next writeable LBA 0
> >>addr = 0 size = 9207808 blocks = 4496
> >>writing from file permfiles.iso size 8992 KB
> >>written this track 1056 KB (11%) total 1056 KB
> >>only wrote -1 of 32768 bytes err=16
> >>
> >>fixating CD, please wait..
> >>
> >>I have also tried to cat imagefile.iso > /dev/acd0c so i could then just
> >>fixate with burncd but i get this error
> >>
> >>cat: stdout: Input/output error
> >>
> >>i looked in my /var/log/messages and found this it might help you guys out
> >>
> >>Aug 30 15:20:49 cripticcorp /kernel: acd0: READ_TRACK_INFO - ILLEGAL
> >>REQUEST asc=0x24 ascq=0x00 error=0x04
> >>
> >>Aug 30 15:21:06 cripticcorp /kernel: acd0: WRITE_BIG - ILLEGAL REQUEST
> >>asc=0x30 ascq=0x05 error=0x04
> >>
> >>Aug 30 15:22:05 cripticcorp /kernel: acd0: WRITE_BIG - ILLEGAL REQUEST
> >>asc=0x21 ascq=0x00 error=0x04
> >>
> >>Aug 30 15:23:07 cripticcorp /kernel: acd0: SEND_OPC_INFO command timeout
> >>- resetting
> >>
> >>Aug 30 15:23:07 cripticcorp /kernel: ata1: resetting devices .. done
> >>
> >>Aug 30 15:23:37 cripticcorp /kernel: acd0: READ_TRACK_INFO command
> >>timeout - resetting
> >>
> >>Aug 30 15:23:37 cripticcorp /kernel: ata1: resetting devices .. done
> >>
> >>Aug 30 15:23:37 cripticcorp /kernel: acd0: READ_TRACK_INFO - ILLEGAL
> >>REQUEST asc=0x20 ascq=0x00 error=0x04
> >>
> >>Aug 30 15:26:52 cripticcorp /kernel: acd0: REZERO command timeout -
> >>resetting
> >>
> >>Aug 30 15:26:52 cripticcorp /kernel: ata1: resetting devices .. done
> >>
> >>Aug 30 15:27:23 cripticcorp /kernel: acd0: SEND_OPC_INFO command timeout
> >>- resetting
> >>
> >>Aug 30 15:27:23 cripticcorp /kernel: ata1: resetting devices .. done
> >>
> >>Aug 30 15:27:53 cripticcorp /kernel: acd0: READ_TRACK_INFO command
> >>timeout - resetting
> >>
> >>Aug 30 15:27:53 cripticcorp /kernel: ata1: resetting devices .. done
> >>
> >>Aug 30 15:27:53 cripticcorp /kernel: acd0: READ_TRACK_INFO - ILLEGAL
> >>REQUEST asc=0x20 ascq=0x00 error=0x04
> >>
> >>Also one last thing in my /dev i have a acd0c and acd0a is this Cd and DVD ?
> >>
> >>Any ideas would be helpful.
> >>
> >>Michael W.
> >>[EMAIL PROTECTED]
> >>
> >>___
> >>[EMAIL PROTECTED] mailing list
> >>http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> >>To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> >>
> >>
> >>
> >
> >
> >
> >
> 
> 


-- 
Subhro Sankha Kar
School of Information Technology
Block AQ-13/1 Sector V
ZIP 700091
India
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd problem err=16 any ideas?

[Subhro]

Are you running the GENERIC kernel? If not have you included support
for the CD file system? Also did you put something non standard in
/etc/make.conf?

Regards
S.

On Mon, 30 Aug 2004 15:56:54 -0500, michael <[EMAIL PROTECTED]> wrote:
> Im running freebsd 4.10 with a sony cd/dvd burner combo (DRU-530A) im
> using burncd -f /dev/acd0c -s max -e data imagefile.iso fixate , i have
> tried to lower the speed to 1x and 8x and i get the same problem  ill
> include the error with -v verabos output maybe it will help ( does
> burncd log somewhere there might be more about the error message that
> might help this problem out? )
> 
> adding type 0x08 file permfiles.iso size 8992 KB 4496 blocks
> next writeable LBA 0
> addr = 0 size = 9207808 blocks = 4496
> writing from file permfiles.iso size 8992 KB
> written this track 1056 KB (11%) total 1056 KB
> only wrote -1 of 32768 bytes err=16
> 
> fixating CD, please wait..
> 
> I have also tried to cat imagefile.iso > /dev/acd0c so i could then just
> fixate with burncd but i get this error
> 
> cat: stdout: Input/output error
> 
> i looked in my /var/log/messages and found this it might help you guys out
> 
> Aug 30 15:20:49 cripticcorp /kernel: acd0: READ_TRACK_INFO - ILLEGAL
> REQUEST asc=0x24 ascq=0x00 error=0x04
> 
> Aug 30 15:21:06 cripticcorp /kernel: acd0: WRITE_BIG - ILLEGAL REQUEST
> asc=0x30 ascq=0x05 error=0x04
> 
> Aug 30 15:22:05 cripticcorp /kernel: acd0: WRITE_BIG - ILLEGAL REQUEST
> asc=0x21 ascq=0x00 error=0x04
> 
> Aug 30 15:23:07 cripticcorp /kernel: acd0: SEND_OPC_INFO command timeout
> - resetting
> 
> Aug 30 15:23:07 cripticcorp /kernel: ata1: resetting devices .. done
> 
> Aug 30 15:23:37 cripticcorp /kernel: acd0: READ_TRACK_INFO command
> timeout - resetting
> 
> Aug 30 15:23:37 cripticcorp /kernel: ata1: resetting devices .. done
> 
> Aug 30 15:23:37 cripticcorp /kernel: acd0: READ_TRACK_INFO - ILLEGAL
> REQUEST asc=0x20 ascq=0x00 error=0x04
> 
> Aug 30 15:26:52 cripticcorp /kernel: acd0: REZERO command timeout -
> resetting
> 
> Aug 30 15:26:52 cripticcorp /kernel: ata1: resetting devices .. done
> 
> Aug 30 15:27:23 cripticcorp /kernel: acd0: SEND_OPC_INFO command timeout
> - resetting
> 
> Aug 30 15:27:23 cripticcorp /kernel: ata1: resetting devices .. done
> 
> Aug 30 15:27:53 cripticcorp /kernel: acd0: READ_TRACK_INFO command
> timeout - resetting
> 
> Aug 30 15:27:53 cripticcorp /kernel: ata1: resetting devices .. done
> 
> Aug 30 15:27:53 cripticcorp /kernel: acd0: READ_TRACK_INFO - ILLEGAL
> REQUEST asc=0x20 ascq=0x00 error=0x04
> 
> Also one last thing in my /dev i have a acd0c and acd0a is this Cd and DVD ?
> 
> Any ideas would be helpful.
> 
> Michael W.
> [EMAIL PROTECTED]
> 
> ___
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> 


-- 
Subhro Sankha Kar
School of Information Technology
Block AQ-13/1 Sector V
ZIP 700091
India
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd: ioctl(CDIOCSTART): Device busy

[Iain Dooley]

More of a question, really.  Why are you using 'fstat -n'?  The -n option 
would appear to print only device numbers, not device names - therefore 
grepping for 'acd' will be fruitless, correct?.
okay, so fstat | grep cd doesn't reveal anything either.
cheers
iain
ORIGINAL MESSAGE

hi there, i'm running freebsd 4.10 with a kodak CR-R drive.
i can mount CD-ROM's in the drive with no problems, but when i insert a
blank CD-R (cdr not cdrw... i checked!!) into the drive and attempt burncd
i get the error
burncd: ioctl(CDIOCSTART): Device busy
i tried "fstat -n | grep acd" but no programs appear to be using the
drive. the light on the CD drive keeps blinking orange too, indicating
that it is trying to read the drive or something similar, but i have not
issued any 'mount /cdrom' command.
i found a similar problem in the lists archive posted by a guy named
willian denton last year, but couldn't find any resolution to the problem.
i emailed him to find out if he ever solved his problem but have not yet
received a reply. [actually, i have now received a reply... he said he never 
solved the problem, he just bought a new drive. my drive works fine in other 
machines, and i can mount CD-ROM's with it, so i don't think it is broken]

http://lists.freebsd.org/pipermail/freebsd-stable/2003-October/004262.html
_
Add photos to your e-mail with MSN 8. Get 2 months FREE*. 
http://join.msn.com/?page=features/featuredemail

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd: ioctl(CDIOCSTART): Device busy

[David Fleck]

On Tue, 10 Aug 2004, Iain Dooley wrote:
i tried "fstat -n | grep acd" but no programs appear to be using the
drive. the light on the CD drive keeps blinking orange too, indicating
that it is trying to read the drive or something similar, but i have not
issued any 'mount /cdrom' command.
[...]
any ideas?
More of a question, really.  Why are you using 'fstat -n'?  The -n option 
would appear to print only device numbers, not device names - therefore 
grepping for 'acd' will be fruitless, correct?.

--
David Fleck
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd question

[arden]

have you tried cdrecord?
On Sun, 2004-07-25 at 16:25, [EMAIL PROTECTED] wrote:
> %uname -a
> FreeBSD SOULFLY.BACK.TO.THE.PRIMITIVE.PH
> 5.2.1-RELEASE-p8 FreeBSD 5.2.1-RELEASE-p8 #0: Mon Jun
> 21 14:53:05 PHT 2004
> [EMAIL PROTECTED]:/usr/src/sys/i386/compile/MMP  i386
> 
> cd-RW dmesg: 
> ata1-slave: FAILURE - SETFEATURES SET TRANSFER MODE no
> interrupt
> acd0: CDRW  at ata1-slave BIOSPIO
> 
> SOULFLY# burncd -f /dev/acd0 -s 12 data downloads.iso
> fixate
> burncd: ioctl(CDIOCSTART): Device busy
> 
> SOULFLY# $ ls -l /usr/sbin/burncd
> -r-xr-xr-x  1 root  wheel  18196 Jun 24 17:51
> /usr/sbin/burncd
> 
> i always get this message, when i attempt to burn an
> .iso, anyone whats this error is all about, my sony 24x
> burner is fine when i burn files from my windows XP
> which is my first partition, i hope anyone can help me
> fixing this problem, thanks ;)
> ___
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> 

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd is unable to fixate on Dell Inpiron 2650

[Malcolm Kay]

On Sunday 27 June 2004 04:28, Dan Finn wrote:
> That did it.  Why is it neccisary to specify the block size?

Because the default block of 512 used by dd is not big enough to hold
a cd block.

Malcolm


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd is unable to fixate on Dell Inpiron 2650

[Dan Finn]

That did it.  Why is it neccisary to specify the block size?

On Fri, 25 Jun 2004 20:22:54 -0500, Vladimir Egorin
<[EMAIL PROTECTED]> wrote:
> 
> On Fri, Jun 25, 2004 at 06:14:45PM -0700, Dan Finn wrote:
>> [ dfinn @ stewie : ~] : dd if=/dev/cd0 of=blah.iso
>> dd: /dev/cd0: Invalid argument
>> 0+0 records in
>> 0+0 records out
>> 0 bytes transferred in 0.000648 secs (0 bytes/sec)
> 
> Hm, how about
> dd if=/dev/cd0 of=blah.iso bs=2048
> dd if=/dev/acd0 of=blah.iso bs=2048
> If this doesn't work, I have no clue.
> --
> Vladimir
>
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd question

[Marc Fonvieille]

On Thu, Apr 22, 2004 at 08:40:50AM +0100, [EMAIL PROTECTED] wrote:
> 
> Greetings all,
> I have used the burncd tool many a time to burn audio cd's from wav's,
> however recently I have been having problems.
> 
> I have recorded some wav files using audio/audacity. A nice lil
> multitrack editor. All I want to do is burn them to cd. So if I do this
> (as I always have):
> 
> burncd -s max audio file.wav fixate
> 
> It does indeed burn a cd. But the audio is much faster than it should be.
> Why is this? I have tryed this on two machines running
> freebsd-5.2-release and they both have the same output. My wav is 32 bit
> at a sample rate of 44100. I have also tryed converting to a 16 bit wav,
> but the outcome is the same. Is there something I have overlooked?
>

burncd supports "raw PCM", the wav header should be a cause of problem.
Try the command given at bottom of 
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/sound-mp3.html
this should "normalize" your audio file.

Marc
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd not able to create multisession disco?

[Sergey 'DoubleF' Zaharchenko]

On Mon, 22 Mar 2004 13:41:30 +0800
"Zhang Weiwu" <[EMAIL PROTECTED]> probably wrote:

> What I wish to do is to burn a multisession data disco, the data
> session should be closed but the disco should not be finalized so I
> can add other files later.
> 
> So it seems burncd(8) cannot do it? I just wanna make it sure rather
> than diging into all the docs only to find it is impossible.

Use -m. man burncd says:

-mclose disk in multisession mode (otherwise disk is closed
  as singlesession).

You have to fixate the disk anyway, but then you can append data to
disk after you fixate it. HTH,

-- 
DoubleF
Keep grandma off the streets -- legalize bingo.


pgp0.pgp
Description: PGP signature

Re: burncd args

[Lowell Gilbert]

Danny Pansters <[EMAIL PROTECTED]> writes:

> On Friday 12 March 2004 02:52, you wrote:
> > lee slaughter <[EMAIL PROTECTED]> writes:
> > > Danny Pansters wrote:
> > > >On Friday 12 March 2004 00:04, lee slaughter wrote:
> > > >>hi.
> > > >>i make a tar.gz backup file.
> > > >>isburncd -f  /dev/acd1 datafixate
> > > >>the right syntax?  is "data" the correct type?  i cannot tell
> > > >>from burncd manpage.
> > > >
> > > > What you called  should be the ISO (top of my head, I
> > > > think the only exception is if you're creating an audio CD with only
> > > > WAV/AIFF files that go into tracks). So use mkisofs first, then
> > > > burncd.
> > >
> > > hmmm.  so you can  only burn an ISO image onto a CD. not anything
> > > else?  like UFS or any other format?
> >
> > No, you can burn any format you want.
> > You have to remember what it is to mount it again, though;
> > most people will assume it's an ISO 9660 if it's on a CD.
> >
> > It can be useful to burn a raw tar or dump file to a CD,
> > for example.
> 
> I didn't know that, thanks for pointing that out. Though in order to have 
> anything bootable (from a CD rom) you'd have no other choice than iso, or 
> not? (I sometimes made these mini install CDs containing only the 2.88 floppy 
> image but I always thought of it as an ISO with the bootable image being 
> specified. I'm now wondering if I misunderstood this).

That's certainly the usual way to do it.  
I can't tell you for *sure* that there's no other way...
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd args

[Danny Pansters]

On Friday 12 March 2004 02:52, you wrote:
> lee slaughter <[EMAIL PROTECTED]> writes:
> > Danny Pansters wrote:
> > >On Friday 12 March 2004 00:04, lee slaughter wrote:
> > >>hi.
> > >>i make a tar.gz backup file.
> > >>isburncd -f  /dev/acd1 datafixate
> > >>the right syntax?  is "data" the correct type?  i cannot tell
> > >>from burncd manpage.
> > >
> > > What you called  should be the ISO (top of my head, I
> > > think the only exception is if you're creating an audio CD with only
> > > WAV/AIFF files that go into tracks). So use mkisofs first, then
> > > burncd.
> >
> > hmmm.  so you can  only burn an ISO image onto a CD. not anything
> > else?  like UFS or any other format?
>
> No, you can burn any format you want.
> You have to remember what it is to mount it again, though;
> most people will assume it's an ISO 9660 if it's on a CD.
>
> It can be useful to burn a raw tar or dump file to a CD,
> for example.

I didn't know that, thanks for pointing that out. Though in order to have 
anything bootable (from a CD rom) you'd have no other choice than iso, or 
not? (I sometimes made these mini install CDs containing only the 2.88 floppy 
image but I always thought of it as an ISO with the bootable image being 
specified. I'm now wondering if I misunderstood this).

Cheers,

Dan
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd args

[Lowell Gilbert]

lee slaughter <[EMAIL PROTECTED]> writes:

> Danny Pansters wrote:
> 
> >On Friday 12 March 2004 00:04, lee slaughter wrote:
> >
> >>hi.
> >>i make a tar.gz backup file.
> >>isburncd -f  /dev/acd1 datafixate
> >>the right syntax?  is "data" the correct type?  i cannot tell
> >>from burncd manpage.
> >>
> >
> > What you called  should be the ISO (top of my head, I
> > think the only exception is if you're creating an audio CD with only
> > WAV/AIFF files that go into tracks). So use mkisofs first, then
> > burncd.
> >
> hmmm.  so you can  only burn an ISO image onto a CD. not anything
> else?  like UFS or any other format?

No, you can burn any format you want.  
You have to remember what it is to mount it again, though;
most people will assume it's an ISO 9660 if it's on a CD.

It can be useful to burn a raw tar or dump file to a CD,
for example.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd args

[lee slaughter]

Danny Pansters wrote:

On Friday 12 March 2004 00:04, lee slaughter wrote:
 

hi.
i make a tar.gz backup file.
isburncd -f  /dev/acd1 datafixate
the right syntax?  is "data" the correct type?  i cannot tell
from burncd manpage.
   

What you called  should be the ISO (top of my head, I think the only 
exception is if you're creating an audio CD with only WAV/AIFF files that go 
into tracks). So use mkisofs first, then burncd.

hmmm.  so you can  only burn an ISO image onto a CD. 
not anything else?  like UFS or any other format?

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd args

[Danny Pansters]

On Friday 12 March 2004 00:04, lee slaughter wrote:
> hi.
> i make a tar.gz backup file.
> isburncd -f  /dev/acd1 datafixate
> the right syntax?  is "data" the correct type?  i cannot tell
> from burncd manpage.

What you called  should be the ISO (top of my head, I think the only 
exception is if you're creating an audio CD with only WAV/AIFF files that go 
into tracks). So use mkisofs first, then burncd.


HTH,

Dan

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd and cdrecord

[Malcolm Kay]

On Mon, 8 Mar 2004 11:50, [EMAIL PROTECTED] wrote:
> I backed some files up using burncd and cdrecord. The files burned fine.
> But the problem that I am having. Is that I am unabel to see the files. The
> command I used for burn cd was: "burncd -f /dev/asc1c -s max -e data *.*
> fixate". And the command I used for cdrecord i baleve was: "cdrecord
> dev=1,1,0 *.*". I am not sure the exact command I did for cdrecord. Because
> I only have 1,1,0 written down. I am using FreeBSD 4.9  and have a Hewlett
> Packard Cd-Writer Plus 9100 series.

The *.* in the above should be a prepared image of an ISO-9660 filesystem --
not just a set of ordinary files as they come.

You need to make the image using mkisofs. Have a look at the man page.

You might find the example script /usr/share/examples/worm/makecdfs.sh
a useful starting point although not exactly what you want as it  actually 
creates a bootable CD.

If you have an ATAPI CD drive then burncd is straightforward and works well
without the complication of atapicam.

Malcolm
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd and cdrecord

[anubis]

On Mon, 8 Mar 2004 11:20 am, [EMAIL PROTECTED] wrote:
> I backed some files up using burncd and cdrecord. The files burned
> fine. But the problem that I am having. Is that I am unabel to see
> the files. The command I used for burn cd was: "burncd -f
> /dev/asc1c -s max -e data *.* fixate". And the command I used for
> cdrecord i baleve was: "cdrecord dev=1,1,0 *.*". I am not sure the
> exact command I did for cdrecord. Because I only have 1,1,0 written
> down. I am using FreeBSD 4.9  and have a Hewlett Packard Cd-Writer
> Plus 9100 series.
>
> ___
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "[EMAIL PROTECTED]"

Dude, you need to create an iso first.  Look at man 8 mkisofs
Also take some time and look here at the handbook Section 12.5
http://www.au.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd + 5.2

[Lowell Gilbert]

Martin Vana <[EMAIL PROTECTED]> writes:

> I've got problems blanking/burning cds on my teac cd writer, burncd will
> fall into nanslp and stop responding:
>  1288K   624K nanslp   0:01  0.00%  0.00% burncd
> I know that this was an issue a while ago but is it fixed yet?
> How to fix it?

I've had problems like that when the drive hardware itself is hanging
up and stops responding to commands.  Most often, it's triggered by
bad media.  I took enough of a look at it to see that there isn't much
the OS can do about it (however, -STABLE has had some recent
improvements -- within the last few months, anyway -- that reduce the
impact on other system functionality).  So for me, anyway, I've
written it off as a price of cheap hardware.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd issues

[Ion-Mihai Tetcu]

On Sat, 27 Dec 2003 07:58:43 -0600
Eric F Crist <[EMAIL PROTECTED]> wrote:

> On Saturday 27 December 2003 01:30 am, Ion-Mihai Tetcu wrote:
> > On Sat, 27 Dec 2003 01:23:04 -0600
> >
> > Eric F Crist <[EMAIL PROTECTED]> wrote:
> > > Hey all,
> > >
> > > This is the first time I've tried burning CDs or DVDs from freebsd.  I
> > > have read through what I thought was the pertinent information on the
> > > archives and typed the following command to burn a simple pdf file (an
> > > old email from the KDE print system, which is readable from the hard
> > > drive) to the CDRW drive on my laptop:
> > >
> > > # burncd -f /dev/acd0c -s max data /home/user/email-test.pdf fixate
> >
> > Perhaps you missed the isofs step ? From that command line it seems you
> > burned directly the file itself, co is no wonder that mount can
> > recognise the file-system format.

>  > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html
> 
> That worked!  Thank you so very much for pointing that out for me.

no problem ;)



-- 
IOnut
Unregistered ;) FreeBSD user
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd issues

[Eric F Crist]

On Saturday 27 December 2003 01:30 am, Ion-Mihai Tetcu wrote:
> On Sat, 27 Dec 2003 01:23:04 -0600
>
> Eric F Crist <[EMAIL PROTECTED]> wrote:
> > Hey all,
> >
> > This is the first time I've tried burning CDs or DVDs from freebsd.  I
> > have read through what I thought was the pertinent information on the
> > archives and typed the following command to burn a simple pdf file (an
> > old email from the KDE print system, which is readable from the hard
> > drive) to the CDRW drive on my laptop:
> >
> > # burncd -f /dev/acd0c -s max data /home/user/email-test.pdf fixate
>
> Perhaps you missed the isofs step ? From that command line it seems you
> burned directly the file itself, co is no wonder that mount can
> recognise the file-system format.
>
>
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html
>
> > The cdrw drive works for a few seconds, I get some output from burncd
> > that indicates everything is OK and I eject the CDR, noting the burned
> > tracks that are visible with the right reflection of light.
> >
> > However, I get the following error when I try to execute the following
> > two commands:
> >
> > # mount -t cd9660 /dev/acd0c /cdrom
> > or
> > # mount /cdrom
> >
> > Output: cd9660: /dev/acd0c: Invalid argument
> >
> > Is there a different option I should give burncd or mount?  Please let me
> > know.  Also, from 4.9, are there any other major issues I should know
> > about burning a DVD?  5.x?

That worked!  Thank you so very much for pointing that out for me.

Eric Crist
AdTech Integrated Systems, Inc

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd issues

[Ion-Mihai Tetcu]

On Sat, 27 Dec 2003 01:23:04 -0600
Eric F Crist <[EMAIL PROTECTED]> wrote:

> Hey all,
> 
> This is the first time I've tried burning CDs or DVDs from freebsd.  I have 
> read through what I thought was the pertinent information on the archives and 
> typed the following command to burn a simple pdf file (an old email from the 
> KDE print system, which is readable from the hard drive) to the CDRW drive on 
> my laptop:
> 
> # burncd -f /dev/acd0c -s max data /home/user/email-test.pdf fixate

Perhaps you missed the isofs step ? From that command line it seems you
burned directly the file itself, co is no wonder that mount can
recognise the file-system format.


http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html

> The cdrw drive works for a few seconds, I get some output from burncd that 
> indicates everything is OK and I eject the CDR, noting the burned tracks that 
> are visible with the right reflection of light.
> 
> However, I get the following error when I try to execute the following two 
> commands:
> 
> # mount -t cd9660 /dev/acd0c /cdrom
> or
> # mount /cdrom
> 
> Output: cd9660: /dev/acd0c: Invalid argument
> 
> Is there a different option I should give burncd or mount?  Please let me 
> know.  Also, from 4.9, are there any other major issues I should know about 
> burning a DVD?  5.x?



-- 
IOnut
Unregistered ;) FreeBSD user
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd ``only wrote -1...'' coasting discs.

[jens thys]

I had the same problem before on a 5.1 version and wiped of the src tree and downloded 
the sources from scratch. Made the kernel compiling according to the instructions 
regarding the "new way" ( see the handbook ) and it worked out perfectly. 

Ps check as well if you are using a rw cdrom and especillay if the burner is a high 
speed one able to burn the high speed cdroms. Elder burner reject the newest standards 
of cdrom in my case. 




 On Thu, 20 Nov 2003 00:04:06 +
Lewis Thompson <[EMAIL PROTECTED]> wrote:

> Hi,
> 
> I've tried to burn ISOs on a number of occassions using the burncd
> utility.  I use the command ``burncd -s max -f /dev/acd0c data foo.iso
> fixate'' (as I always have done), but this fails /very/ quickly with the
> following message:
> 
> next writeable LBA 0
> writing from file disc1.iso size 646272 KB
> written this track 832 KB (0%) total 832 KB
> only wrote -1 of 32768 bytes: Device busy
> 
> fixating CD, please wait..
> 
>   I posted a while back and was told it might be because I was running
> 5.1-RELEASE and a lot of code had changed.  Right now I'm running
> 4.9-RELEASE (with the same problems).
> 
>   This is a new DVD-RW drive (a TEAC DV-W50E) that /does/ support a form
> of buffer underrun (I think it is BurnProof -- Nero burns discs just
> great under XP).  Any idea what this could be?
> 
> -lewiz.
> 
> -- 
> I was so much older then, I'm younger than that now.  --Bob Dylan, 1964.
> 
> -| msn:[EMAIL PROTECTED] | jabber:[EMAIL PROTECTED] | url:www.lewiz.org |-
> 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd ``only wrote -1...'' coasting discs.

[Lewis Thompson]

On Mon, Oct 20, 2003 at 09:26:28AM -0400, Lowell Gilbert wrote:
> Lewis Thompson <[EMAIL PROTECTED]> writes:
> 
> > I'm trying to use burncd to write an ISO to a blank disc.  The discs are
> > all fine, etc. and this is a new DVD drive (writes DVDs and CDs), so I'm
> > guessing that is the problem.
> 
> By itself, it shouldn't be.  If you're running 5.x, that's another
> story.

In true me style I am and as ever I always forget to add some relevant
detail to all posts, so this is it.  I'm using 5.1-RELEASE-p8.

  Could you point me (or just tell me ;) in the direction of where I can
find out about this problem?

  Thanks very much,

-lewiz.

-- 
I was so much older then, I'm younger than that now.  --Bob Dylan, 1964.

-| msn:[EMAIL PROTECTED] | jabber:[EMAIL PROTECTED] | url:www.lewiz.org |-


pgp0.pgp
Description: PGP signature

Re: burncd ``only wrote -1...'' coasting discs.

[Lowell Gilbert]

Lewis Thompson <[EMAIL PROTECTED]> writes:

> I'm trying to use burncd to write an ISO to a blank disc.  The discs are
> all fine, etc. and this is a new DVD drive (writes DVDs and CDs), so I'm
> guessing that is the problem.

By itself, it shouldn't be.  If you're running 5.x, that's another
story (the relevant code has gone through a whole series of
significant changes there), but since you didn't mention what your OS
configuration was like, I'll assume you're running a "production"
release of the OS (4.x).

>   A simple output is as follows:
> 
> [EMAIL PROTECTED] /mnt/packages/unix/isos/hurd > sudo burncd -s max -f
> /dev/acd0 data disc1.iso fixate
> next writeable LBA 0
> writing from file disc1.iso size 646272 KB
> written this track 832 KB (0%) total 832 KB
> only wrote -1 of 32768 bytes: Device busy
> 
> fixating CD, please wait..
> [EMAIL PROTECTED] /mnt/packages/unix/isos/hurd >
> 
>   This leaves me a bit annoyed but with a shiny new mat for my glass.
> Problem is I have quite a collection now and I'll have to start handing
> them out to my friends soon.

I tend to recommend using CD-RW disks for experimenting instead of
CD-Rs.  They tend to require much lower speeds, which can hide some
kinds of problems, but at least you can rule out a number of areas.

>   I'm wondering if it's because the drive doesn't have BurnProof (or
> similar)?  It's a fairly hi-spec machine (XP2800) and the CPU usage at
> the time was around 4%.

BurnProof shouldn't be relevant.  I don't think burncd will use it
anyway, although I'm too lazy to actually check the code.  With a
*really* fast burner, I suppose it's possible that your system can't
the data off the hard disk fast enough (particularly if the image is
mounted over a network, as seems to be the case from your directory
path), then buffer underruns are definitely possible.

The first thing to look at is whether it works at a lower speed.  In
fact, start with a burn speed of 1x or 2x.  If that works, then the
media you're using can't handle the top speed of the drive.  This is
quite common these days.  If underruns are occurring, then burning at
a slower speed should avoid the problem as well. 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd freebsd 5.1

[jon]

> next writeable LBA 450> addr = 450 size = 655589376 
> writing from file slackware-9.1-install-d1.iso size 
> 640224 KB written this track 32 KB (0%) total 32 K
> only wrote -1 of 32768 bytes: Bad address


Are you using atapicam?  If so, try using
cdrecord.this worked for me, same problem. i thought
it was my pioneercd-rw/dvd-+rw drive

__
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd freebsd 5.1

[Warren Block]

On Mon, 29 Sep 2003 [EMAIL PROTECTED] wrote:

> When i tried to burn this iso image i got the following error ( please find
> below).
>
> #used command:
>
> burncd -f /dev/acd0 -t -v -s 4 data slackware-9.1-install-d1.iso

/dev/acd0(c) is the default, at least on 4.8.  -t is for a test... and
it needs a "fixate" at the end to complete the CD:

burncd -s4 data slackware-9.1-install-d1.iso fixate

would really create a CD-R.

> #Output of the error message:
>
> next writeable LBA 450
> addr = 450 size = 655589376 blocks = 320112
> writing from file slackware-9.1-install-d1.iso size 640224 KB
> written this track 32 KB (0%) total 32 K
> only wrote -1 of 32768 bytes: Bad address

Are you using a CD-R disk?  (Not CD-RW.)  Has it been written before?
Some brands of drives are not supported by burncd... there should be a
partial list at

http://freebsd.dk

-Warren Block * Rapid City, South Dakota USA
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd freebsd 5.1

[Micheas Herman]

On Mon, 2003-09-29 at 09:35, [EMAIL PROTECTED] wrote:
> Hello,
> 
> When i tried to burn this iso image i got the following error ( please find
> below).
> 
> #used command:
> 
> burncd -f /dev/acd0 -t -v -s 4 data slackware-9.1-install-d1.iso

I belive the command should be:
burncd -f /dev/acd0 -t -v -s 4 data slackware-9.1-install-d1.iso fixate
 --
man burncd | grep gunzip

gives the command that I use for burning iso images.

Micheas

> 
> iso image is correct (md5 cjhecked).
> 
> #Output of the error message:
> 
> next writeable LBA 450
> addr = 450 size = 655589376 blocks = 320112
> writing from file slackware-9.1-install-d1.iso size 640224 KB
> written this track 32 KB (0%) total 32 K
> only wrote -1 of 32768 bytes: Bad address
> 
> #System information
> 1- uname output:
> FreeBSD  5.1-CURRENT FreeBSD 5.1-CURRENT #0: Sun Sep 14 23:04:43 CEST 2003
> 
> root@:/usr/src/sys/i386/compile/XXX  i386
> 
> 
> 
> Ce service de mailing vous est offert par http://www.freesurf.fr.
> FreeSurf, votre acces ADSL a partir de 29 euros/mois
> http://www.freesurf.fr/adsl/
> 
> 
> ___
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
-- 
Micheas Herman <[EMAIL PROTECTED]>
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd freebsd 5.1

[Andrew L. Gould]

On Monday 29 September 2003 11:35 am, [EMAIL PROTECTED] wrote:
> Hello,
>
> When i tried to burn this iso image i got the following error ( please find
> below).
>
> #used command:
>
> burncd -f /dev/acd0 -t -v -s 4 data slackware-9.1-install-d1.iso
>
> iso image is correct (md5 cjhecked).
>
> #Output of the error message:
>
> next writeable LBA 450
> addr = 450 size = 655589376 blocks = 320112
> writing from file slackware-9.1-install-d1.iso size 640224 KB
> written this track 32 KB (0%) total 32 K
> only wrote -1 of 32768 bytes: Bad address
>
> #System information
> 1- uname output:
> FreeBSD  5.1-CURRENT FreeBSD 5.1-CURRENT #0: Sun Sep 14 23:04:43 CEST 2003
>
> root@:/usr/src/sys/i386/compile/XXX  i386
>

Are you using atapicam?  If so, try using cdrecord.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd and /dev/acd0c ??

[Guillaume]

Lowell Gilbert wrote:
ivan georgiev <[EMAIL PROTECTED]> writes:


On Thursday 25 September 2003 07:01 am, Warren Block wrote:

On Wed, 24 Sep 2003, ivan georgiev wrote:

I am trying for first time to burn a CD under freebsd. I have read the
man page for burncd, but I do not have /dev/acd0c created (only /dev/acd0
is there).Is this a problem or not?
It could be--in /dev with FreeBSD 4.8, I see acd0a, acd0c, acd1a and
acd1c.  This is probably different under 5.x.

Also, cdrecord -scanbus doesn't show anything...
cdrecord is for SCSI, or if you are using atapicam to emulate SCSI with
IDE devices.
Thanks Warren,

But as I said, there is only acd0 in /dev. No /dev/acd0c is created (I use 
5.1-current).

/dev/acd0c does not exist in -CURRENT. Use /dev/acd0 instead.



Guillaume

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd and /dev/acd0c ??

[Lowell Gilbert]

ivan georgiev <[EMAIL PROTECTED]> writes:

> On Thursday 25 September 2003 07:01 am, Warren Block wrote:
> > On Wed, 24 Sep 2003, ivan georgiev wrote:
> > > I am trying for first time to burn a CD under freebsd. I have read the
> > > man page for burncd, but I do not have /dev/acd0c created (only /dev/acd0
> > > is there).Is this a problem or not?
> >
> > It could be--in /dev with FreeBSD 4.8, I see acd0a, acd0c, acd1a and
> > acd1c.  This is probably different under 5.x.
> >
> > > Also, cdrecord -scanbus doesn't show anything...
> >
> > cdrecord is for SCSI, or if you are using atapicam to emulate SCSI with
> > IDE devices.
> 
> Thanks Warren,
> 
> But as I said, there is only acd0 in /dev. No /dev/acd0c is created (I use 
> 5.1-current).

It should be.  Check to see if it's being detected at boot.
If you're having problems with -CURRENT, though, you really need to
use its mailing list to get help.  You really should be reading the
list if you're going to run -CURRENT anyway.  Admittedly, it's a lot
of mail, but that's just part of running the latest development code.

> Do I have to emulate SCSI in order to use the CD writer?

No.  In fact, SCSI emulation almost certainly won't detect the device
either if direct ATAPI support doesn't.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd and /dev/acd0c ??

[ivan georgiev]

On Thursday 25 September 2003 07:01 am, Warren Block wrote:
> On Wed, 24 Sep 2003, ivan georgiev wrote:
> > I am trying for first time to burn a CD under freebsd. I have read the
> > man page for burncd, but I do not have /dev/acd0c created (only /dev/acd0
> > is there).Is this a problem or not?
>
> It could be--in /dev with FreeBSD 4.8, I see acd0a, acd0c, acd1a and
> acd1c.  This is probably different under 5.x.
>
> > Also, cdrecord -scanbus doesn't show anything...
>
> cdrecord is for SCSI, or if you are using atapicam to emulate SCSI with
> IDE devices.

Thanks Warren,

But as I said, there is only acd0 in /dev. No /dev/acd0c is created (I use 
5.1-current).
Do I have to emulate SCSI in order to use the CD writer?

Ivan

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd and /dev/acd0c ??

[Warren Block]

On Wed, 24 Sep 2003, ivan georgiev wrote:

> I am trying for first time to burn a CD under freebsd. I have read the man
> page for burncd, but I do not have /dev/acd0c created (only /dev/acd0 is
> there).Is this a problem or not?

It could be--in /dev with FreeBSD 4.8, I see acd0a, acd0c, acd1a and
acd1c.  This is probably different under 5.x.

> Also, cdrecord -scanbus doesn't show anything...

cdrecord is for SCSI, or if you are using atapicam to emulate SCSI with
IDE devices.

-Warren Block * Rapid City, South Dakota USA
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd and PIONEER DVD-RW DVR-106D

[Marc Wiz]

On Sat, Sep 20, 2003 at 05:57:16PM -0700, jon wrote:
> this post is very similar to my problem, 
> 
> http://freebsd.rambler.ru/bsdmail/freebsd-hardware_2003/msg00521.html
> (i emailed the above but got no response.)
> 
> i replaced the burner, tried different dvd+rw,
> googled, and RTFM. still, no go. any ideas? 
> 5.1 release from cvs 9/18. 

I am running 4.8 and have a a Pioneer 106 in a Firewire enclosure.
I have not tried burncd.  I have it working with dvdrecord.

Marc

-- 
Marc Wiz
[EMAIL PROTECTED]
Yes, that really is my last name.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd

[Aaron Siegel]

Hello
The handbook does a good job cover this topic, please take a look at it
 
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html

On Thursday 31 July 2003 06:25 am, marlon corleone wrote:
> how do i burn a directory using burncd
>
> i did burncd -f /dev/acd1 data mp3z fixate
> is this correct?
>
> __
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free, easy-to-use web site design software
> http://sitebuilder.yahoo.com
> ___
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "[EMAIL PROTECTED]"

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd

[Serge Terryn]

Ada Cheng wrote:

You need audio instead of data.
Ada
On Thu, 31 Jul 2003, marlon corleone wrote:
 

how do i burn a directory using burncd

i did burncd -f /dev/acd1 data mp3z fixate
is this correct?
__
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
   

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
 

Like the manpage tells you, you must make a iso file system first.
Use mkisofs to create a iso filesystem from your mp3 directory.
To simply burn mp3's, you need data en not audio.

Otherwise you need a program that convert mp3's to cd audio files.

Serge

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd

[Ada Cheng]

You need audio instead of data.
Ada
On Thu, 31 Jul 2003, marlon corleone wrote:

> how do i burn a directory using burncd
>
> i did burncd -f /dev/acd1 data mp3z fixate
> is this correct?
>
> __
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free, easy-to-use web site design software
> http://sitebuilder.yahoo.com
> ___
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: burncd data files

[dick hoogendijk]

On 01 Mar Mike Meyer wrote:
> The easiest way to deal with data on the CD is to burn a file system
> and then mount it to read the data back. Since iso 9660 file systems
> were designed for CDs, that's probably the best one to use.

I follow the logic of this. Maybe my confusion arose from the fact that
*normally* you only burn ONE iso file per disk to disk and the burncd
manual speaks about ".. data file1.iso file2.iso file3.iso fixate"
This is confusing 'cause the only way I can imagine this is some kind of
multi-session CD which you cannot read in total (only separate sessions
(iso files). This 'view' is wrong (?)

-- 
dick -- http://www.nagual.st/ -- PGP/GnuPG key: F86289CE
++ Running FreeBSD 4.7 ++ Debian GNU/Linux (Woody)

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: burncd data files

[Mike Meyer]

In <[EMAIL PROTECTED]>, Dick Hoogendijk <[EMAIL PROTECTED]> typed:
> As I understand I can execute a line like:
> ## burncd -f /dev/acd0c -s 12 data win98.iso fixate
> For this to work I create the iso file system w/ mkisofs.
> OK, but what if I just want to backup some files on my fbsd system to
> cd/rw? Is this possible or do all (data) files written by burncd *have*
> to be ISO files to begin with? Maybe a stupid question but reading
> through the manual I get the impression they have..

You can burn arbitrary data to a cd. The question is - how do you then
get it back? If you burn one file per track, you're limited to the 99
track devices for reading them, and you have to dd them off with an
odd blocksize. If you burn a tar file or something similar, you've
still got the dd problem.

The easiest way to deal with data on the CD is to burn a file system
and then mount it to read the data back. Since iso 9660 file systems
were designed for CDs, that's probably the best one to use.

  http://www.mired.org/consulting.html
Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: burncd on 4.7 + YAMAHA CRW2200E (again)

[mark . b]

Just a stab in the dark, When I got my first cd burner, it would not burn but would 
read cd's
fine, the problem was the burner had to use the "master plug" on the IDE cable.


On 15 Nov 2002 at 17:49, Jacques Beigbeder wrote:

Date sent:  Fri, 15 Nov 2002 17:49:30 +0100
From:   Jacques Beigbeder <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject:burncd on 4.7 + YAMAHA CRW2200E (again)

> Hardware: PC Asus / Athlon processor
> OS : FreeBSD 4.7, GENERIC kernel
>
> During the boot, I read in syslog messages:
>  ata1-slave: ATAPI identify retries exceeded
>  ad0: 19546MB  [39714/16/63] at ata0-master
>  UDMA100 acd0: CD-RW  at ata1-master PIO4
> So the hard drive is primary master, the CD is secondary master.
>
> The CD works since I can mount data CD. It works under Linux
> with cdrecord.
>
> I can write CD-RW with:
>  burncd -f /dev/acd0c blank
>  burncd -f /dev/acd0c data MY_ISO_IMAGE fixate
> But with a CD-R the same (second) command fails and /var/log/messages
> says:
>
> Nov 15 14:56:58 tempo2 /kernel: acd0: SEND_OPC_INFO command timeout -
> resetting Nov 15 14:56:58 tempo2 /kernel: ata1: resetting devices ..
> ata1-slave: ATAPI identify retries exceeded Nov 15 14:56:58 tempo2
> /kernel: done
>
> Just once; what's about "ATAPI identify retries exceeded'? There's
> nothing slave! Than, with a loop:
>
> Nov 15 14:57:56 tempo2 /kernel: acd0: SEND_OPC_INFO command timeout -
> resetting Nov 15 14:57:56 tempo2 /kernel: ata1: resetting devices ..
> done Nov 15 14:59:13 tempo2 /kernel: acd0: SEND_OPC_INFO command
> timeout - resetting Nov 15 14:59:13 tempo2 /kernel: ata1: resetting
> devices .. done
>
> Any hint? Thanks in advance,
>
> --
> Jacques Beigbeder|  [EMAIL PROTECTED]
> Service de Prestations Informatiques | http://www.spi.ens.fr
> Ecole normale supérieure |
> 45 rue d'Ulm |Tel : (+33 1)1 44 32 37 96
> F75230 Paris cedex 05|Fax : (+33 1)1 44 32 20 75
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-questions" in the body of the message


* *  *   *   * *   * * *
** *   *   *   *   *   *
 *   *

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: burncd on 4.7 + YAMAHA CRW2200E

[Kliment Andreev]

> I'm very disappointed, no burncd working, no more a hard disk...
> The hardware was Asus + Athlon.

Unplug the cable from CDRW and try to boot. Double check jumpers and pin
"1". Re-detect HDD from BIOS. It should work. If so, put CDRW on the second
controller as master, but make sure the jumper is correctly set. Use master
not C/S.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: burncd on 4.7 + YAMAHA CRW2200E

[Jacques Beigbeder]

>> > ON a fresh CD, running:
>> > burncd -f /dev/acd0c -s 4 -d data MY_ISO_IMAGE fixate
>> > displays:
>> > /kernel: acd0: TEST_UNIT_READY - MEDIUM ERROR asc=0x57 ascq=0x00
>> error=0x00
>> > /kernel: acd0: START_STOP - MEDIUM ERROR asc=0x57 ascq=0x00 error=0x00
 
>> I have the same CDRW and it works fine. Maybe something is wrong with CD
>> media according to the message you get "MEDIUM ERROR".

I installed Linux, and the hardware and the CD were OK: cdrecord
worked perfectly well.
I rebooted FreeBSD, I re-ran 'burncd'. It failed: computer
still has a prompt, but burncd did nothing. And now
the BIOS doesn't find any more my hard disk

I'm very disappointed, no burncd working, no more a hard disk...
The hardware was Asus + Athlon.

Any hint?

--
Jacques Beigbeder|  [EMAIL PROTECTED]
Service de Prestations Informatiques | http://www.spi.ens.fr
Ecole normale supérieure |
45 rue d'Ulm |Tel : (+33 1)1 44 32 37 96
F75230 Paris cedex 05|Fax : (+33 1)1 44 32 20 75


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: burncd creates jittery audio cd's

[Nathan Kinkade]

On Tue, Nov 12, 2002 at 11:13:17PM -0500, Peter Leftwich wrote:
> On Wed, 13 Nov 2002, Jacob Rhoden wrote:
> > Hi, I have tried burning some wav files onto a cd using burncd, and the audio in a
> > cd player comes out broken (random fraction of a second blank sections in the
> > audio). Is there some special option which I need to use which I am un-aware
> > of from looking in help/man pages... or could it be my cd burner?
> >
> > My burner is a diamond cd burner, which the kernel reports as:
> >  acd0: CD-RW  at ata0-slave PIO4
> > Thanks for any advice,
> > Jacob
> > Jacob RhodenPhone: +61 3 8344 6102
> > ITS DivisionEmail: [EMAIL PROTECTED]
> > Melbourne University   Mobile: +61 403 788 386
> 
> There is a flag to "burncd" of "-s" I believe.  Try matching that to your
> hardware's speed or slower.  Also, are you using mkisofs?  (As far as I
> know, you should be.)
> 
> --
> Peter Leftwich

`mkisofs` is for data CDs.

Nathan

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: burncd creates jittery audio cd's

[Peter Leftwich]

On Wed, 13 Nov 2002, Jacob Rhoden wrote:
> On Wed, 13 Nov 2002 15:13, you wrote:
> > There is a flag to "burncd" of "-s" I believe.  Try matching that to your
> > hardware's speed or slower.  Also, are you using mkisofs?  (As far as I
> > know, you should be.)
>
> Thanks for your reply.. I didnt use the -s flag because the man page reports
> that it defaults to 1 (i assume thats the lowest speed).
>
> Im not using mkisofs, because the man page says use mkisofs to make cd tracks
> which have files in them. (And I guess because the burncd command I used was
> successfull except for the low quality of the sound, it must mean that it
> works without mkisofs?).
> Thanks,
> Jacob
> Jacob RhodenPhone: +61 3 8344 6102
> ITS DivisionEmail: [EMAIL PROTECTED]
> Melbourne University   Mobile: +61 403 788 386

I don't know, and turn this back over to the list...

--
Peter Leftwich
President & Founder
Video2Video Services
Box 13692, La Jolla, CA, 92039 USA
http://Www.Video2Video.Com


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: burncd creates jittery audio cd's

[Peter Leftwich]

On Wed, 13 Nov 2002, Jacob Rhoden wrote:
> Hi, I have tried burning some wav files onto a cd using burncd, and the audio in a
> cd player comes out broken (random fraction of a second blank sections in the
> audio). Is there some special option which I need to use which I am un-aware
> of from looking in help/man pages... or could it be my cd burner?
>
> My burner is a diamond cd burner, which the kernel reports as:
>  acd0: CD-RW  at ata0-slave PIO4
> Thanks for any advice,
> Jacob
> Jacob RhodenPhone: +61 3 8344 6102
> ITS DivisionEmail: [EMAIL PROTECTED]
> Melbourne University   Mobile: +61 403 788 386

There is a flag to "burncd" of "-s" I believe.  Try matching that to your
hardware's speed or slower.  Also, are you using mkisofs?  (As far as I
know, you should be.)

--
Peter Leftwich
President & Founder
Video2Video Services
Box 13692, La Jolla, CA, 92039 USA
http://Www.Video2Video.Com


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: burncd wierdness

[Warren Block]

On Sun, 27 Oct 2002, Joel Mc Graw wrote:

> Every time I burn a cd with the following line:
> 
> "burncd -f /dev/acd0c -e file.to.burn fixate"
  ^
Don't you need the "data" or "audio" keyword in there?
 
> it creates a perfect CD, but upon ejecting (the "-e" switch), the CD
> drive dies.  The tray stays in the out position, even when pushing the
> external eject/load button, and the only way I can regain access to the
> drive is by rebooting.  This is an IDE SONY CD-RW on FreeBSD 4.5-R
> (i386).  Any thoughts on what might be wrong?

What model of drive?  I've used an HP 8X and a Sony 40X (CR195)
successfully.

-Warren Block * Rapid City, South Dakota USA


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: burncd wierdness

[Nathan Kinkade]

On Sun, Oct 27, 2002 at 10:17:33AM -0700, Joel Mc Graw wrote:
> Every time I burn a cd with the following line:
> 
> "burncd -f /dev/acd0c -e file.to.burn fixate"
> 
> it creates a perfect CD, but upon ejecting (the "-e" switch), the CD
> drive dies.  The tray stays in the out position, even when pushing the
> external eject/load button, and the only way I can regain access to the
> drive is by rebooting.  This is an IDE SONY CD-RW on FreeBSD 4.5-R
> (i386).  Any thoughts on what might be wrong?

Don't know what might be wrong, but you could try:
`cdcontrol -f /dev/acd0c close'
assuming, of course that your cdrom device is located at acd0c.
When the problem occurs are there any stray processes that might still
be using the device?  Try taking a peek at `top' or `ps aux' when this happens.

Nathan

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: burncd error

[Oliver Fromme]

parv <[EMAIL PROTECTED]> wrote:
 > in message <[EMAIL PROTECTED]>,
 > wrote Oliver Fromme thusly...
 > > You can even go a step further and let mkisofs create Joliet and
 > > Apple (HFS) extensions on the CD.  You will then have four
 > > different kinds of directory descriptions on the CD for the same
 > > content.  The cool thing is that every operating system picks the
 > > one most suitable for itself.
 > 
 > you forgot to mention one thing that having multiple OS
 > compatibility layers will result in much lower available space than
 > expected.

It depends.  The rockridge extensions don't take that much
space.  I often make CD-ROMs (always with rockridge, of
course) that are very close to the 650 or 700 Mbyte limit
of the respective CD-Rs.  The overhead isn't that large,
unless maybe you have _really_ many small files on it, i.e.
several hundreds of thousands.

As for the Joliet and Apple stuff, those _might_ take a bit
more space, particularly the Apple/HFS filesystem data with
its "resource forks".  I don't normalle create CD-ROMs with
HFS extensions on them, though.

Regards
   Oliver

-- 
Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München
Any opinions expressed in this message may be personal to the author
and may not necessarily reflect the opinions of secnetix in any way.

"All that we see or seem is just a dream within a dream" (E. A. Poe)

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: burncd error

[parv]

in message <[EMAIL PROTECTED]>,
wrote Oliver Fromme thusly...
>
> Kevin Oberman <[EMAIL PROTECTED]> wrote:
>  > I suspected that both -allow-lowercase and -allow-multidot were
>  > implicit in -r, but I had never actually tried it.
> 
> No, they're not implicit, but they're not necessary either.
> 
> Let me explain ...

thanks for the info.


> You can even go a step further and let mkisofs create Joliet and
> Apple (HFS) extensions on the CD.  You will then have four
> different kinds of directory descriptions on the CD for the same
> content.  The cool thing is that every operating system picks the
> one most suitable for itself.

you forgot to mention one thing that having multiple OS
compatibility layers will result in much lower available space than
expected.

i once tried all those layers & after 500 MB or so, "file system
full" messages were being generated... until somebody clued me in to
use as minimum options to use as possible.  those messages are in
the (-questions, i think) archive somewhere.


  - parv

-- 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: burncd error

[Oliver Fromme]

Kevin Oberman <[EMAIL PROTECTED]> wrote:
 > I suspected that both -allow-lowercase and -allow-multidot were
 > implicit in -r, but I had never actually tried it.

No, they're not implicit, but they're not necessary either.

Let me explain ...

Standard ISO9660 filesystems have several limitations.  For
example, every filename has a maximum length of 31 characters
(even though it's common to use only 8+3 because of old DOS-
compatibility), only upper-case letters, numbers and under-
scores, there must be exactly one dot (which must not be the
first character of the name), a non-empty filename extension
(after that dot), and a non-empty version number.  Also note
that ISO9660 does not support some of the standard UNIX UFS
features, such as permission modes, ownership etc.

There are several options to mkisofs that cause it to ignore
some of those restrictions.  This usually works most of the
time, but might not work with an operating system (or other
software) that enforces strict ISO9660 conformance.  These
options include -allow-lowercase, -allow-multidot, -d, -D,
-L, -N, -relaxed-filenames, -U, -no-iso-translate.

However, when you use the -R or -r option to create a rock-
ridge extension, you actually have a second directory
hierarchy laid over the existing ISO9660 directory hierachy
(this is somewhat simplified, but the net effect is just
that).  Basically that means that, if you mount the CD with
a rockridge-capable operating system (such as FreeBSD), you
don't see the ISO9660 filenames at all, but only the rock-
ridge filenames.  Obviously, there is no restriction on the
filenames in the rockridge extension, as it was specifically
designed to store information for UNIX filesystems, including
permissions and ownerships.  The above-mentioned options
(-allow-lowercase etc.) don't have any effect on the rock-
ridge extension.

Conversely, if you mount the CD with a non-rockridge-capable
system (such as DOS), you only see the ISO9660 filenames with
all of their limitations, possibly relaxed by the above-
mentioned options (provided that it works, as those options
produce non-standard CDs).  If you expect emergency cases
where you must be able to read a rockridge CD with DOS but
still be able to reconstruct the real filenames somehow,
mkisofs offers the -T option.  It creates a simple text file
called TRANS.TBL in every directory which contains a mapping
between the ISO9660 filenames and the rockridge filenames,
one per line.

You can even go a step further and let mkisofs create Joliet
and Apple (HFS) extensions on the CD.  You will then have
four different kinds of directory descriptions on the CD for
the same content.  The cool thing is that every operating
system picks the one most suitable for itself.

 > > The remarkable thing was actually, that when I used the wrong option,
 > > mkisofs says it doesn't recognise the option, quits the program, and
 > > returns to the prompt in my xterm, but now my xterm shows up with
 > > unrecognisable characters (normally for me: root@hostname, now something
 > > like: %^(%^%(%^&()_)_*).
 > > 
 > > Did I hit a bug?

Indeed, it sounds like a bug.  It seems that cdrecord fails
to send the proper reset/init termcap sequences in that
particular case, so the terminal is left in some unusual
state.  Actually I'm surprised that mkisofs would use
termcap control sequences anyway.  It doesn't really need
to, IMO.

BTW, you can manually reset an xterm by pointing your mouse
pointer inside it, then press (and hold) the Ctrl key, then
press the middle mouse button.  This causes an xterm menu
to pop up.  Select "full reset" from that menu.

Also, typing "reset", "tput reset init" and/or "stty sane"
might help in some situations.  If the terminal settings
are seriously broken so that the enter key doesn't work
anymore, use Ctrl-J instead of enter (you might even have
to type the command blindly if the terminal echo was turned
off).

Regards
   Oliver

-- 
Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München
Any opinions expressed in this message may be personal to the author
and may not necessarily reflect the opinions of secnetix in any way.

"All that we see or seem is just a dream within a dream" (E. A. Poe)

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message