Differences between version 27 and predecessor to the previous major change of CDWritingNotes.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 27 | Last edited on Wednesday, December 1, 2004 10:01:22 am | by JohnMcPherson | Revert |
| Older page: | version 20 | Last edited on Tuesday, May 25, 2004 11:57:06 pm | by DouglasBagnall | Revert |
@@ -1,16 +1,16 @@
!!! Graphical CD writing software
-Note that these are all merely graphical front-ends that call cdrecord to do the actualy
writing, so you will need to make sure that cdrecord works (see the following sections for help with this).
+Note that these are all merely graphical front-ends that call cdrecord to do the actual
writing, so you will need to make sure that cdrecord works (see the following sections for help with this).
* [K3B|http://k3b.sourceforge.net] is the [KDE] project's [GUI] burning tool
* __xcdroast__ has a fairly awful [GTK] based [GUI].
* __eroaster__ looks much better designed for ease-of-use... written in [Python] and [GTK].
-* [GNOME2
] has nautilus-cd-burner, a gnome-vfs thing that means you can drag'n'drop files into the __burn:///__ virtual directory, and then click the Burn
button. Nice and easy.
+* [GNOME
] has nautilus-cd-burner, a gnome-vfs thing that means you can drag'n'drop files into the __burn:///__ virtual directory, and then click the "Write to CD"
button. Nice and easy. In a nautilus window, click on the "Go" menu and then "CD Creator"
.
!!! cdrecord(1)
-At least in [Debian] [Woody], the file __/etc/default/cdrecord__ stores settings about your CD writer(s). The last section which maps the device settings to the drive name __''must'' be Tab separated__. Blanks
won't work.
+At least in [Debian] [Woody], the file __/etc/default/cdrecord__ stores settings about your CD writer(s). The last section which maps the device settings to the drive name __''must'' be Tab separated__. Spaces
won't work.
Make sure that your user has permission to any required device files and executable programs. In [Debian], the files have the appropriate permissions for people in the __cdrom__ group. If you add yourself to the group you will have to log out and back in for that to take effect.
!!! How to get your CDR working - [IDE] [SCSI] emulation
@@ -58,14 +58,14 @@
Get the latest version of whatever graphical frontend you prefer, and make sure they grok the ATAPI interface. If they don't, email the author requesting the feature and explain why you're now using a different program instead of theirs :)
!! Finding the CDR
-Now find your CDR with __cdrecord dev=ATAPI
-scanbus__. Note the dev=ATAPI
bit. I'm led to believe that without that, cdrecord might well lock solid and need a reboot, although it seems ok in practice
.
+Now find your CDR with __cdrecord dev=ATA:
-scanbus__. Note the dev=ATA
bit.
The above command will return something like:
Cdrecord-Clone 2.01a19 (i686-pc-linux-gnu) Copyright (C) 1995-2003 Jörg Schilling
- scsidev: 'ATAPI
:'
- devname: 'ATAPI
'
+ scsidev: 'ATA
:'
+ devname: 'ATA
'
scsibus: -1 target: -1 lun: -1
Warning: Using ATA Packet interface.
Warning: The related libscg interface code is in pre alpha.
Warning: There may be fatal problems.
@@ -81,24 +81,38 @@
1,1,0 101) *
1,2,0 102) *
...
-So, this says that I have an ATAPI cdrom on dev=ATAPI
:,1,0 and an atapi cdwriter on dev=ATAPI
:1,,.
+So, this says that I have an ATAPI cdrom on dev=ATA
:,1,0 and an atapi cdwriter on dev=ATA
:1,,.
-Devices on
/dev/hdd (ie Secondary Slave) show as ,1
,.
+Note! cdrecord seems to have 2 independent ATAPI
/IDE drivers: "ATA:" and "ATAPI:"
, which map device names differently:
-You can now burn CD's just as you could before
, except use the device names as detailed above (ie
, dev=ATAPI:1,
+ $ cdrecord dev=ATAPI: -scanbus
+ Warning: Using ATA Packet interface.
+ Warning: The related Linux kernel interface code seems to be unmaintained.
+ Warning: There is absolutely NO DMA
, operations thus are slow.
+
,1,0 1) '!CyberDrv' 'CB511D Combo ' '120A' Removable CD-ROM
+ ...
+
+ $ cdrecord
dev=ATA: -scanbus
+ scsidev: 'ATA:'
+ devname: 'ATA'
+ scsibus: -1 target: -1 lun: -1
+ Warning: Using badly designed
ATAPI via /dev/hd* interface.
+ Linux sg driver version
: 3.5.27
+
1,1
,0 101
) '!CyberDrv' 'CB511D Combo ' '120A' Removable CD-ROM
+ ...
-!! Any issues with this ?
+"ATA:" appears to be the preferred driver, and ATAPI: seems to be obsolete.
-* Under earlier 2.6.0 test kernels, I couldn
't write audio cds using
the [ATAPI] interface. Not tried it lately
, nor investigated why.
-* DMA only works in some situations. If you dont have DMA enabled
, you can't write faster than 16x.
+You can now burn CD
's just as you could before, except use
the device names as detailed above (ie
, dev=ATA:1
,,0 )
-However, I successfully wrote an audio cd using ATAPI under kernel 2.4.24 and
cdrecord version 2..something under Debian Testing
(although my graphical front-end didn't know about passing the dev=ATAPI option to
cdrecord, so I had to use the command line with
- $
cdrecord -v -dao dev=ATAPI:,1,0 driveropts=burnfree -audio -pad *
.wav
-The average write speed was 25x
:p (JohnMcPherson)
+You can also save this in the
cdrecord config file
(either /etc/default/
cdrecord on Debian
, or maybe /etc/
cdrecord.conf on other distros) by adding something like
:
--- If you read my SoundProcessingNotes page, you'll note I continued
to have problems
, regardless of whether I used a command line approach or an ATAPI-aware GUI
. However, my command differed from yours above, which could well have been the problem. I will investigate :
) -- DanielLawson
+ CDR_DEVICE=mycdwriter
+ ...
+ mycdwriter= ATA:1,,0
-1
-1 ""
+(and remember
to use tabs for separation
, and not spaces
.)
!! Another Way
In Debian Sid, the file /usr/share/doc/cdrecord/README.ATAPI.setup.gz describes another way to get cdrecord working
@@ -143,11 +157,6 @@
mkisofs will generate the boot.catalog file for you. Add '-dummy' to cdrecord if you want a test run first. If cdrecord doesn't know about your cdr then you'll need to add 'dev=x,y,z' and possibly 'speed=n'. If you just want to create the .iso file then you can use '-o boot.iso' with mkisofs instead of piping it to cdrecord. The '.' at the end of mkisofs is still required though.
There's a file 'README.eltorrito' in /usr/share/doc/mkisofs that explains how to do boot CDs.
-
-!!! See also
-
-* [HowToCDWritingHOWTO]
-* [HowToSCSIGenericHOWTO]
----
CategoryDiskNotes
