I installed K3b last night and successfully created a CD from .mp3 files. (cdrw /dev/scd0). I wanted to be able to burn 'on the fly' so I enabled scsi emulation in grub for my DVD rom as well. (hda=ide-scsi hdc=ide-scsi). reboot the puter and all is well, so I thought.

I recreated symlinks for cd and dvd and then ran 'cdrecord -scanbus'. Both devices were listed for scsi emulation. I then opened k3b and checked my devices. k3b reported I had no writing device and it lists both devices under reader.

Is there another step to make sure k3b recognizes my burner as a burner and not a reader? Maybe it's something obvious, but I'm very confused about this. TIA

DVDrom - /dev/scd0
CDRW - /dev/scd1

I can't really offer you any real assistance, but with my mandrake installation and the dvd drive and cdrw, I often have to do some guess work to get things going properly.

By that, on my desktop, the drives are identified as cdrom (the dvd) and cdrom2 (the cdrw). But when it comes to using the bloody things, the system has to have them refered to as hdb for the dvd drive and scd0 for the cdrw.

You should have a look at you initial boot screen, before lilo/grub/whatever kick in (as in where you F1 or delete to access your BIOS) you normally get a list of which ide's things are plugged into - which will give you some idea.

The scsi emulation is something to do with 2 way transfer of data - hence the scd0 (probably) identifier of the cdrw - the dvd will only send the info out - it's (presumably) not a burner (although I don't know if dvd burners also have scd?? identification.

Hope this gives you some ideas.

regards

John

I know that my DVD is master-IDE 1 (hda) and that my CDRW is master-IDE2 (hdc). I can play DVD's with mplayer by pressing the 'DVD' button. I can play audio CD's with DVDrom. Last night, I could burn an audio CD from .mp3's with k3b. (before changing grub)

According to k3b, I need to emulate scsi device in order to burn 'on the fly'. So, I added 'hda=ide-scsi" to grub. Now, both devices have scsi emulation, but k3b no longer recognizes my CDRW (scd1) as a write device.

I'm just wondering if there is a command or setting that lets RH9 know that /dev/scd1 is a write device.

Anybody? Surely someone knows how to make it right. I've searched these forums, google and the k3b website and I don't have a clue. If you can't give me a suggestion of how to fix it, could you at least tell me how to uninstall compiled stuff. Maybe if I reinstall it will work itself out. Kinda like windows, eh?

well first, that didnt' make much sense to me, since hda you say is your dvdrom, which has nothing to do with burning on the fly...but anways i thought i would point that out...

but anyways as of your problem, did you try going to tools, and re-configuring k3b, and even if it does pick it up as a reader, did you try hitting the add button and adding it manually in the cdwriter section?

k3b, being a bizarrely abstracted GUI monster does some weird things sometimes... First, open an xterm and then fire up k3b after su-ing to root and see if its made a mess of permissions. If that refuses to work, check good old xcdroast and see if its recognizing the device correctly.

Cheers,

Finegan

Well...that's a start. I su - 'd and had to type the full path to k3b (is that normal) instead of just 'k3b' and everything seems o.k. (my dvd is a reader, and cdrw is a burner) Whenever I try to use it as a regular user, it detects both the dvd and cdrw as a reader. So it has to be a permission thing.

One more thing...I'm using k3b with gnome. I wasn't able to run the k3bsetup. It causes my desktop to crash. I had to use 'ctrl-alt-F2' to get out of there. I think this lets me set up my permissions. I have created a 'cdwriter' group and put some users in there. I tried a 'chmod ug+rw root:cdwriter /dev/hdc' (and scd1) and it said "failed to get attributes" and "no such file or directory". So I'm kinda at a loss. I'm OK with running k3b as root, but I feel that I shouldn't have to. There seems to be quite afew posts in here to sort this out. But if anyone wants to lend a helping hand...

Listen K3B - Now it's personal !!

*edit*
@DrOzz - Apparently k3b will not recognize an ATAPI device. There is a warning message that told me the way to correct this error is to use scsi emulation.