I am using a Dell P3 that I installed Knoppix 3.2 on. I did the hard disk install and have a dandy running Debian unstable system. It works beautifully.

Then I yanked a cd burner out of another computer here and tried to get it working. I have xcdroast installed. When I try and run it, it won't even come up.

I have k3b installed. When I try and run it, it says it can't find cdrecord even though I have installed cdrecord. The text of the error message is: "Unable to find cdrecord executable
K3b uses cdrecord to actually write cds. Without cdrecord K3b won't be able to properly initialize the writing devices.
Solution: Install the cdrtools package which contains cdrecord."

Apt-get install does not know of any package called cdrtools.

I have Arson installed. It will come up with no error messages, but when I go into its setup menu, the drop down where you select the cd writer is blank.

My guess is that I just don't have the cd set up correctly at a basic level.

I believe I have scsi emulation set up.

Here are some bits of various files that tell the story I think:

=====fstab=====
# /etc/fstab: filesystem table.
#
# filesystem mountpoint type options dump pass
/dev/hda2 / reiserfs defaults 0 1
/dev/hda1 none swap sw 0 0
proc /proc proc defaults 0 0
/dev/fd0 /floppy vfat defaults,user,noauto,showexec,umask=022 0 0
/dev/cdrom /cdrom iso9660 defaults,ro,user,noexec,noauto 0 0
/dev/cdrw /cdrw iso9660 defaults,ro,user,noexec,noauto 0 0
/dev/dvd /dvd iso9660 defaults,ro,user,noexec,noauto 0 0
/dev/cdaudio /cdaudio iso9660 defaults,ro,user,noexec,noauto 0 0
# harvest.moon:/ /home/ken/harvest nfs rw,hard,intr 0 0
/dev/sda1 /home/ken/camera auto auto,users 0 0
/dev/scd0 /cdrom auto ro,noauto,user,exec 0 0
/dev/scd1 /cdrw auto ro,noauto,user,exec 0 0

====dmesg (part)===========
[snip]
Kernel command line: auto BOOT_IMAGE=Linux ro root=302 hda=scsi hdb=scsi hdc=scsi hdd=scsi hde=scsi hdf=scsi hdg=scsi hdh=scsi apm=power-off nomce
ide_setup: hda=scsi
ide_setup: hdb=scsi
ide_setup: hdc=scsi
ide_setup: hdd=scsi
ide_setup: hde=scsi
ide_setup: hdf=scsi
ide_setup: hdg=scsi
ide_setup: hdh=scsi

[snip]

Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX4: IDE controller at PCI slot 00:07.1
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hdaMA, hdbio
ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdcMA, hddio
hda: WDC WD136AA, ATA DISK drive
hdc: SAMSUNG CD-ROM SC-140F, ATAPI CD/DVD-ROM drive
hdd: CD-W54E, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: attached ide-disk driver.
hda: host protected area => 1
hda: 26564832 sectors (13601 MB) w/2048KiB Cache, CHS=1653/255/63
ide-cd: passing drive hdc to ide-scsi emulation.
ide-cd: passing drive hdd to ide-scsi emulation.
hdc: attached ide-scsi driver.
hdd: attached ide-scsi driver.
Partition check:
hda: hda1 hda2
Promise Fasttrak(tm) Softwareraid driver 0.03beta: No raid array found
Highpoint HPT370 Softwareraid driver for linux version 0.01-ww1
No raid array found
No raid array found
No raid array found
Guestimating sector 26563807 for superblock
driver for Silicon Image(tm) Medley(tm) hardware version 0.0.1: No raid array found
SCSI subsystem driver Revision: 1.00
scsi0 : SCSI host adapter emulation for IDE ATAPI devices
Vendor: SAMSUNG Model: CD-ROM SC-140F Rev: fn10
Type: CD-ROM ANSI SCSI revision: 02
Vendor: TEAC Model: CD-W54E Rev: 7.1F
Type: CD-ROM ANSI SCSI revision: 02
Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0
Attached scsi CD-ROM sr1 at scsi0, channel 0, id 1, lun 0
sr0: scsi3-mmc drive: 40x/40x cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.12
sr1: scsi3-mmc drive: 32x/32x writer cd/rw xa/form2 cdda tray

===console output=========
root@full:/etc# ls -l /dev | grep cdrom
brw-rw---- 1 root cdrom 29, 0 Apr 14 2001 aztcd0
brw-rw---- 1 root cdrom 41, 0 Apr 14 2001 bpcd
lrwxrwxrwx 1 root root 9 Aug 15 15:57 cdrom -> /dev/scd0
brw-rw---- 1 root cdrom 24, 0 Apr 14 2001 cdu535
brw-rw---- 1 root cdrom 30, 0 Apr 14 2001 cm206cd0
brw-rw---- 1 root cdrom 16, 0 Apr 14 2001 gscd0
brw-rw---- 1 root cdrom 24, 0 Apr 14 2001 lmscd
brw-rw---- 1 root cdrom 23, 0 Apr 14 2001 mcd
brw-rw---- 1 root cdrom 20, 0 Apr 14 2001 mcdx0
brw-rw---- 1 root cdrom 20, 1 Apr 14 2001 mcdx1
brw-rw---- 1 root cdrom 20, 2 Apr 14 2001 mcdx2
brw-rw---- 1 root cdrom 20, 3 Apr 14 2001 mcdx3
brw-rw---- 1 root cdrom 20, 4 Apr 14 2001 mcdx4
brw-rw---- 1 root cdrom 17, 0 Apr 14 2001 optcd
brw-rw---- 1 root cdrom 46, 0 Jun 2 2001 pcd0
brw-rw---- 1 root cdrom 46, 1 Jun 2 2001 pcd1
brw-rw---- 1 root cdrom 46, 2 Jun 2 2001 pcd2
brw-rw---- 1 root cdrom 46, 3 Jun 2 2001 pcd3
brw-rw---- 1 root cdrom 25, 0 Apr 14 2001 sbpcd0
brw-rw---- 1 root cdrom 25, 1 Apr 14 2001 sbpcd1
brw-rw---- 1 root cdrom 25, 2 Apr 14 2001 sbpcd2
brw-rw---- 1 root cdrom 25, 3 Apr 14 2001 sbpcd3
brw-rw---- 1 root cdrom 11, 10 May 30 2001 scd10
brw-rw---- 1 root cdrom 11, 11 May 30 2001 scd11
brw-rw---- 1 root cdrom 11, 12 May 30 2001 scd12
brw-rw---- 1 root cdrom 11, 13 May 30 2001 scd13
brw-rw---- 1 root cdrom 11, 14 May 30 2001 scd14
brw-rw---- 1 root cdrom 11, 15 May 30 2001 scd15
brw-rw---- 1 root cdrom 11, 16 May 30 2001 scd16
brw-rw---- 1 root cdrom 11, 2 May 30 2001 scd2
brw-rw---- 1 root cdrom 11, 3 May 30 2001 scd3
brw-rw---- 1 root cdrom 11, 4 May 30 2001 scd4
brw-rw---- 1 root cdrom 11, 5 May 30 2001 scd5
brw-rw---- 1 root cdrom 11, 6 May 30 2001 scd6
brw-rw---- 1 root cdrom 11, 7 May 30 2001 scd7
brw-rw---- 1 root cdrom 11, 8 May 30 2001 scd8
brw-rw---- 1 root cdrom 11, 9 May 30 2001 scd9
brw-rw---- 1 root cdrom 18, 0 Apr 14 2001 sjcd
brw-rw---- 1 root cdrom 15, 0 Apr 14 2001 sonycd
root@full:/etc# ls -l /dev | grep cdrw
lrwxrwxrwx 1 root root 9 Sep 21 21:45 cdrw -> /dev/scd1
root@full:/etc#

============




So, that is as much as I know to include here for infomation. I have lost my way in this stuff. Can anyone help?

Thanks in advance

have you tried running cdrecord from command line? this will tell you for sure if its installed, if not then thats obviously your problem, if apt-get doesnt have it (dont know why it wouldnt) then there of course is always the option fo a manual install...theyre really not that hard (though i do understand the hesitance from doing that...after all in gentoo i found myself waiting for an ebuild to emerge new beta kernels...now thats just getting sad)

-good luch

mork

Yes, it seems to be installed. At least here is what the console says when I type cdrecord at the root prompt:

root@full:/home/ken# cdrecord
cdrecord.mmap: No tracks specified. Need at least one.
Usage: cdrecord.mmap [options] track1...trackn

Use cdrecord.mmap -help
to get a list of valid options.

Use cdrecord.mmap blank=help
to get a list of valid blanking options.

Use cdrecord.mmap dev=b,t,l driveropts=help -checkdrive
to get a list of drive specific options.

Use cdrecord.mmap dev=help
to get a list of possible SCSI transport specifiers.
root@full:/home/ken#
root@full:/home/ken#

On the other hand, when I do it non root, I get:

ken@full:~$ cdrecord
/usr/bin/cdrecord: /usr/bin/cdrecord: Permission denied


Hmm . . .

i dont know what else will require this but you could start by trying chmod 666 /bin/cdrecord and the same to /usr/bin/cdrecord, does k3b or whatever else work as root?

Got a no such file error for /usr/cdrecord but it seems to have let me change /usr/bin/cdrecord.

I get the same error when I run k3b as root.

I think maybe cdrecord expect to see a SCSI device, which should be OK since Knoppix seems to be installing SCSI emulation on all disks. Try (as root)

# cdrecord -scanbus

As well as my old (real SCSI) CD recorder I see my (IDE) zip drive:

Cdrecord 2.01a16 (i686-pc-linux-gnu) Copyright (C) 1995-2003 Jörg Schilling
Linux sg driver version: 3.1.25
Using libscg version 'schily-0.7'
scsibus0:
0,0,0 0) 'IOMEGA ' 'ZIP 100 ' '14.A' Removable Disk
etc...

I use cdrecord from the command line, and the three digits at the beginning of the line are the device number cdrecord needs to know, so if I have

1,3,0 103) 'TEAC ' 'CD-R55S ' '1.0R' Removable CD-ROM

then I have to put dev=1,3,0 on the cdrecord command line. I've only ever used cdrecord and the Linux CD-writing HOWTO.

Here is what I got:

ken@full:~$ cdrecord -scanbus
/usr/bin/cdrecord: /usr/bin/cdrecord: Permission denied
ken@full:~$ su
Password:
root@full:/home/ken# cdrecord -scanbus
Cdrecord-Clone 2.01a18 (i686-pc-linux-gnu) Copyright (C) 1995-2003 Jörg Schilling
Linux sg driver version: 3.1.25
Using libscg version 'schily-0.7'
scsibus0:
0,0,0 0) 'SAMSUNG ' 'CD-ROM SC-140F ' 'fn10' Removable CD-ROM
0,1,0 1) 'TEAC ' 'CD-W54E ' '7.1F' Removable CD-ROM
0,2,0 2) *
0,3,0 3) *
0,4,0 4) *
0,5,0 5) *
0,6,0 6) *
0,7,0 7) *
root@full:/home/ken#

Still stuck, but thanks for trying!

Ken

You should be able to record using (as root):

# cdrecord -v speed=<whatever> dev=0,1,0 -data cdimage.iso

If you don't like that you can try making cdrecord 'SUID root' which means it has root powers even if it being run by non-root users. You can probably reconfigure the package using (as root):

# dpkg-reconfigure cdrecord

I will try and use cdrecord as root from the console. In the meantime, I ran across a command in another thread here that I tried and got this output. Not sure if it adds to the picture

root@full:/home/ken# dmesg | grep -i rom
hdc: SAMSUNG CD-ROM SC-140F, ATAPI CD/DVD-ROM drive
hdd: CD-W54E, ATAPI CD/DVD-ROM drive
Promise Fasttrak(tm) Softwareraid driver 0.03beta: No raid array found
Vendor: SAMSUNG Model: CD-ROM SC-140F Rev: fn10
Type: CD-ROM ANSI SCSI revision: 02
Type: CD-ROM ANSI SCSI revision: 02
Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0
Attached scsi CD-ROM sr1 at scsi0, channel 0, id 1, lun 0
Uniform CD-ROM driver Revision: 3.12
root@full:/home/ken#

Does this look right?

Ken

Tried cdrecord from console. After the first attempt I did a mount -a. then I ran the command suggested. Got a file not found.

So I put a knoppix disk in the cd reader and a blank cdrw in the writer and ran the second attempt.

Not sure what to make of it all, but here it is:

root@full:/home/ken# cdrecord -v speed=30 dev=0,1,0 -data cdimage.iso
Cdrecord-Clone 2.01a18 (i686-pc-linux-gnu) Copyright (C) 1995-2003 Jörg Schilling
TOC Type: 1 = CD-ROM
scsidev: '0,1,0'
scsibus: 0 target: 1 lun: 0
Linux sg driver version: 3.1.25
Using libscg version 'schily-0.7'
SCSI buffer size: 64512
atapi: 1
Device type : Removable CD-ROM
Version : 0
Response Format: 1
Vendor_info : 'TEAC '
Identifikation : 'CD-W54E '
Revision : '7.1F'
Device seems to be: Generic mmc CD-RW.
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC SWABAUDIO
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R
Drive buf size : 1300480 = 1270 KB
FIFO size : 4194304 = 4096 KB
cdrecord.mmap: No such file or directory. Cannot open 'cdimage.iso'.
root@full:/home/ken# cdrecord -v speed=30 dev=0,1,0 -data /cdrom/*
Cdrecord-Clone 2.01a18 (i686-pc-linux-gnu) Copyright (C) 1995-2003 Jörg Schilling
TOC Type: 1 = CD-ROM
scsidev: '0,1,0'
scsibus: 0 target: 1 lun: 0
Linux sg driver version: 3.1.25
Using libscg version 'schily-0.7'
SCSI buffer size: 64512
atapi: 1
Device type : Removable CD-ROM
Version : 0
Response Format: 1
Vendor_info : 'TEAC '
Identifikation : 'CD-W54E '
Revision : '7.1F'
Device seems to be: Generic mmc CD-RW.
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC SWABAUDIO
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R
Drive buf size : 1300480 = 1270 KB
FIFO size : 4194304 = 4096 KB
Track 01: data unknown length
Track 02: data unknown length
Track 03: data unknown length
Track 04: data unknown length
Track 05: data 0 MB padsize: 598 KB
Track 06: data 0 MB padsize: 598 KB
Track 07: data 0 MB padsize: 596 KB
Track 08: data 0 MB padsize: 596 KB
Total size: 5 MB (00:30.10) = 2258 sectors
Lout start: 5 MB (00:32/08) = 2258 sectors
Current Secsize: 2048
ATIP info from disk:
Indicated writing power: 3
Reference speed: 6
Is not unrestricted
Is erasable
Disk sub type: High speed Rewritable (CAV) media (1)
ATIP start of lead in: -11745 (97:25/30)
ATIP start of lead out: 359848 (79:59/73)
1T speed low: 4 1T speed high: 10
power mult factor: 1 5
recommended erase/write power: 5
A1 values: 24 1A D0
A2 values: 00 00 00
Disk type: Phase change
Manuf. index: 40
Manufacturer: INFODISC Technology Co., Ltd.
cdrecord.mmap: Input/output error. read disk info: scsi sendcmd: no error
CDB: 51 00 00 00 00 00 00 00 04 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 03 00 00 00 00 0A 00 00 00 00 31 00 00 00
Sense Key: 0x3 Medium Error, Segment 0
Sense Code: 0x31 Qual 0x00 (medium format corrupted) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.000s timeout 240s
cdrecord.mmap: Cannot get disk type.
root@full:/home/ken#

In my fstab I have

/dev/scd0 /cdrom auto ro,noauto,user,exec 0 0
/dev/scd1 /cdrw auto ro,noauto,user,exec 0 0

And I also get

root@full:/home/ken# dmesg | grep -i rom
hdc: SAMSUNG CD-ROM SC-140F, ATAPI CD/DVD-ROM drive
hdd: CD-W54E, ATAPI CD/DVD-ROM drive
Promise Fasttrak(tm) Softwareraid driver 0.03beta: No raid array found
Vendor: SAMSUNG Model: CD-ROM SC-140F Rev: fn10
Type: CD-ROM ANSI SCSI revision: 02
Type: CD-ROM ANSI SCSI revision: 02
Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0
Attached scsi CD-ROM sr1 at scsi0, channel 0, id 1, lun 0
Uniform CD-ROM driver Revision: 3.12
root@full:/home/ken#

So dmesg thinks they are sr0 and sr1 but fstab tries to set them up as scd0 and scd1.

Does this suggest there is a problem with the way I have it set up or just a problem with me . .. .

Ken

I can see what went wrong there. The 'cdrecord' command needs an 'ISO image' of a CD, which is the usual thing you download from the web or construct yourself out of a bunch of files you want burn onto CD.

I just put 'cdimage.iso' as an example of such a thing.

I highly recommend the CD-writing-HOWTO at

http://www.tldp.org/HOWTO/CD-Writing-HOWTO.html#toc5

It is quite short and well-written and describes the low-level process of putting together a CD. The various GUI packages are mainly just front ends for managing the various steps described there.

P.S. I can't see anything wrong with your hardware. CD writing happens at the device level, not the filesystem level, so fstab does not come into the picture. The advice further up to chmod 666 to make a file executable is wrong. To give everyone execute permission on a file you need chmod 755. By contrast chmod 666 make a file readable and writable by everyone, executable by nobody.