You can access files on either CD or CDRW now?
I see there is a "ide-cd" module I am not familar with. Perhaps it can replace the "ide-scsi" module?
Looks like you can test the CDRW also with mkisofs on a small file and cdrecord in test mode.

michaelk, so how do I point the cd-rom and cd burner folder that I make within the media folder to the device's?

2damncommon, I did a mkisofs -help, but am still lost as to what I am trying here.
also how do I do a unmount from console? I mounted the cd-rw with mount /dev/hdc, but can't unmount it fro either the desktop or console. It tell's me only root can perform.

chopp

Sorry, Let me rephrase... You want to create a new device. Right click on create new CDROM device. Type in a name then select the device tab and then select the /dev/cdrom.

2damncommon was suggesting a method for verifing your CDwriter was functioning.

It sounds like you have a few things to straighten out, but you should be able to test the burner.
Create a folder/directory and put a file or two in it. From the command line run:
mkisofs -r -J -v -o isoname /path/to/files
(All those flags are probably not needed for a test but are what I usually use for real.) That will create an ISO image of your files.
Then as root run:
cdrecord -v -dummy dev=0,0,0 speed=2 /path/to/iso/name.iso
(The speed can probably be higher but I will leave that for you to change)
Those are the exact steps to actually creating a CD. If the test goes OK and you have a CD to waste, remove the "-dummy" and try it.

michaelk, both the cdrom and the burner show up on my desktop, so why do I need to make another device? But I can't seem to unmount the burner?

2damncommon, this is the output of the iso creation:

mkisofs -r -J -v -o isoname /home/doug/Desktop/burn
mkisofs 2.0 (i586-mandrake-linux-gnu)
Scanning /home/doug/Desktop/burn
Writing: Initial Padbock Start Block 0
Done with: Initial Padbock Block(s) 16
Writing: Primary Volume Descriptor Start Block 16
Done with: Primary Volume Descriptor Block(s) 1
Writing: Joliet Volume Descriptor Start Block 17
Done with: Joliet Volume Descriptor Block(s) 1
Writing: End Volume Descriptor Start Block 18
Done with: End Volume Descriptor Block(s) 1
Writing: Version block Start Block 19
Done with: Version block Block(s) 1
Writing: Path table Start Block 20
Done with: Path table Block(s) 4
Writing: Joliet path table Start Block 24
Done with: Joliet path table Block(s) 4
Writing: Directory tree Start Block 28
Done with: Directory tree Block(s) 1
Writing: Joliet directory tree Start Block 29
Done with: Joliet directory tree Block(s) 1
Writing: Directory tree cleanup Start Block 30
Done with: Directory tree cleanup Block(s) 0
Writing: Extension record Start Block 30
Done with: Extension record Block(s) 1
Writing: The File(s) Start Block 31
Total translation table size: 0
Total rockridge attributes bytes: 262
Total directory bytes: 0
Path table size(bytes): 10
Done with: The File(s) Block(s) 95
Writing: Ending pad block Start Block 126
Done with: Ending pad block Block(s) 18
Max brk space used 7064
144 extents written (0 Mb)

I tried cdrecord -v -dummy dev=0,0,0 speed=2 /path/to/iso/name.iso, with another iso I have. Here are the result's of it:
cdrecord -v -dummy dev=0,0,0 speed=2 /home/doug/temp/debian-30r1-i386-binary-1.iso
cdrecord: No such file or directory. No read access for '/home/doug/temp/debian-30r1-i386-binary-1.iso'.

I don't quite understand the No read access. Tmp is 777
thank's again guy's
chopp

You don't, I must be getting tired...

Actually with supermount you do not need to explicitly mount or unmount. To access just open up the folder or cd to the mount point in a console window. Before removing a cd close any apps that are accessing the drive and cd out of the directory if using a console window. Then eject the CD.

The question is, is there an image file called isoname in the directory you executed the command line from?
You did the cdrecord as root? ('su') There are probably permission problems if trying to use cdrecord as a regular user.
You can also confirm the path by doing a 'ls' before or using tab completion while typing the command.
The point of the small ISO file was, of course, to make the test shorter.

Well 2damncommon, I got the process to work with my other iso by eliminating the -dummy from the command. Who is the dummy in this picture. Oh well, at least I am learning from my mistake's.
Buuuuut, the burn had error's just like every other time I have tried to burn this iso. Even with the pretty app's. If you don't mind I will post the output of it, and maybe I can get my burn problem's solved as well as you guy's have solved my mount problem's!

cdrecord -v dev=0,0,0 speed=2 /home/doug/tmp/debian-30r1-i386-binary-1.iso
Cdrecord 2.0 (i586-mandrake-linux-gnu) Copyright (C) 1995-2002 Jörg Schilling
TOC Type: 1 = CD-ROM
scsidev: '0,0,0'
scsibus: 0 target: 0 lun: 0
Linux sg driver version: 3.1.24
Using libscg version 'schily-0.7'
atapi: 1
Device type : Removable CD-ROM
Version : 2
Response Format: 1
Vendor_info : 'HP '
Identifikation : 'CD-Writer+ 8290 '
Revision : '1.3C'
Device seems to be: Generic mmc CD-RW.
Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
Driver flags : MMC SWABAUDIO
Supported modes: TAO PACKET RAW/R16 RAW/R96R
Drive buf size : 1343488 = 1312 KB
FIFO size : 4194304 = 4096 KB
Track 01: data 583 MB
Total size: 670 MB (66:24.88) = 298866 sectors
Lout start: 670 MB (66:26/66) = 298866 sectors
Current Secsize: 2048
ATIP info from disk:
Indicated writing power: 5
Reference speed: 2
Is not unrestricted
Is erasable
ATIP start of lead in: -11745 (97:25/30)
ATIP start of lead out: 359849 (79:59/74)
1T speed low: 0 (reserved val 0) 1T speed high: 4
2T speed low: 8 2T speed high: 0 (reserved val 10)
power mult factor: 4 6
recommended erase/write power: 5
A1 values: 02 4C D0
A2 values: 4A D8 5A
Disk type: Phase change
Manuf. index: 40
Manufacturer: INFODISC Technology Co., Ltd.
Blocks total: 359849 Blocks current: 359849 Blocks remaining: 60983
Starting to write CD/DVD at speed 2 in real TAO mode for single session.
Last chance to quit, starting real write 0 seconds. Operation starts.
Waiting for reader process to fill input buffer ... input buffer ready.
Performing OPC...
Starting new track at sector: 0
Track 01: 67 of 583 MB written (fifo 100%) [buf 98%] 2.1x.cdrecord: Input/output error. write_g1: scsi sendcmd: cmd timeout after 5.162 (40) s
CDB: 2A 00 00 00 87 BF 00 00 1F 00
cmd finished after 5.162s timeout 40s

write track data: error after 71170048 bytes
Sense Bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Writing time: 246.689s
Average write speed 16.6x.
Min drive buffer fill was 98%
Fixating...
Fixating time: 0.083s
cdrecord: fifo had 1185 puts and 1122 gets.
cdrecord: fifo was 0 times empty and 1121 times full, min fill was 98%.

I first thought it was the iso causing this, but I don't now. With k3b, and X-CD-Roast, they both get to 11% just like what I just got with the command line.
Any ideas on this one?

chopp

Well same as before. No cd-rom again. I have tried these:
none /mnt/cdrom supermount dev=/dev/hdc,fs=auto,--,user 0 0
error=could not enter directory /mnt/cdrom

/dev/hdc /mnt/cdrom supermount dev=/dev/hdc,fs=auto,--,user 1 0
error=could not enter directory /mnt/cdrom

/dev/hdc /mnt/cdrom supermount dev=/dev/hdc,fs=auto,--,user,
unmask=0 0 0
error=could not enter directory /mnt/cdrom

In my mnt directory, I have: cdrom(locked) cdrom2(locked)
floppy(locked) and hdc(not locked)

Any idea what the heck keep's going on here.
I'm not having fun anymore.

chopp

Anyone got any ideas on this?

chopp

Possibly the download is bad. Perhaps you can find a small ISO file to test with?
These are exactly the types of errors I got in 8.0 which disappeared when I ditched supermount per the faq.
Here is a better howto for ditching supermount in favor of autofs:
http://www.mandrakeuser.org/docs/admin/amount4.html

If running the "supermount -i disable" comand and mounting manually seems to solve your problem I would seriously consider not using supermount. Try it a couple days.

quote: lol...thought I'd leave this so you could have a good laugh.
how did you accomplish those line's anyway?
<HR SIZE=4>
If running the "supermount -i disable" comand and mounting manually seems to solve your problem I would seriously consider not using supermount. Try it a couple days.
<HR SIZE=4>

Didn't make any difference on the cdrom access. Should I still go ahead with the autofs?

quote:
<HR SIZE=4>
mkisofs -r -J -v -o isoname /home/doug/Desktop/burn
<HR SIZE=4>
all this seemed to do was create a text file in the /burn directory

Is there a command for blanking cd-rw's

thank's again.
chopp

Here's a couple links RE CDRW blanking:
http://www.faqs.org/docs/Linux-HOWTO...TO.html#ss4.17
http://www.troubleshooters.com/linux/coasterless.htm

RE mkisofs
You would have the files you want to burn to CD in the burn directory. Give isoname an extension (though I don't think it would matter to 'cdrecord') isoname.iso

RE Supermount and autofs
I would confirm that disabling supermount allows you to manually mount the drives before going to autofs. One problem with this could be supermount restarting with a reboot? I don't know if it would or not.
1.Discover if supermount restarts on a reboot (you have issued the -disable command before shutting down).
2. If I understood your posts, you had things working well-or on the way to, then a later post (after a reboot?) says things no longer work. Since your errors are problems I had with supermount and it seems you were back to square one with a reboot I still suspect supermount.
3. After running the -disable command, you would also need to reread and redo some or all of what you did that got things working for you before.
4. When or if to go with autofs is your call. My suggestion is above. Going straight into autofs may or may not work at this point.

Have you discovered the formatting buttons above the posting text box now? The quotes were made using the "Quote" option.

ok that worked. I didn't try just to burn the isoname though, I renamed it to isoname.iso.
I re downloaded another debian.iso and had the same problem's again with cdrecord. I don't know what to think about that one.

As of right now, I have cdrom access with this fstab entry:

none /mnt/cdrom supermount dev=/dev/hdc,fs=iso9660,exec,--,user,dev,suid 0 0

I'll see how long that last's I guess.

I did learn how to blank a cd-rw, with....man cdrecord
Can't see myself going back to a GUI burn program any time soon.

chopp

After spending an afternoon reading docs and man pages on mkisofs and cdrecord I see no reason for a GUI either.

Have you run across the fact that you can mount and brouse an ISO file yet?
mount -t iso9660 xxx.iso /mnt/point -o loop
xxx.iso = the actual ISO you want to mount/browse
/mnt/point = the mount point you have created for mounting your ISO
Then you can view the files on the ISO by going to /mnt/point