I have been searching around for info on getting k3b to run and all of them refer to using scsi emulation to get k3b to see your burner. Thing is I actually have a scsi burner on
/dev/scd0.

I am not at my home computer so I cannot be more specific at this time but does anyone know were some good info regarding this might be.

By the way I am running Mandrake 9.2. Xcdroast worked fine under Mandrake9.0. I did a clean install when I went to 9.2

Thanks in advance-

Thane

k3b should see your scsi burner provided that SCSI CD support is enabled in the kernel.

Guy -

I have scsi support in my kernel - I have watched it load the scsi driver and I can use said burner to read cdroms all day.

Anyway, I tried xcdroast as it worked in Mdk9.0 and it too hung while scaning for burners. It must be a 9.2 bug. I suppose I ought to check the errata.

Thanks!

Thane.

maybe try disabling supermount (?) for your burner.

a) Are you running as a normal user?
b) Does /dev/scd0 have write permissions?

Post the output of
ls -l /dev/scd*
And that may give us a clue as to what's going on.
Guy

/dev/scd0 is merely a link in this system:

dave@Linbox dave]$ ls -l /dev/scd0
lr-xr-xr-x 1 root root 31 Oct 25 23:09 /dev/scd0 -> scsi/host0/bus0/target1/lun0/cd

I then checked the actual file that it is linked to:

[dave@Linbox dave]$ ls -l /dev/scsi/host0/bus0/target1/lun0/cd brw-rw---- 1 dave cdrom 11, 0 Dec 31 1969 /dev/scsi/host0/bus0/target1/lun0/cd

I chmod'd it and changed it but have yet to try to scan it using either xcdroast or k3b:

[root@Linbox dave]# chmod 777 /dev/scd0 [root@Linbox dave]# ls -l /dev/scd0 lr-xr-xr-x 1 root root 31 Oct 25 23:09 /dev/scd0 -> scsi/host0/bus0/target1/lun0/cd [root@Linbox dave]# ls -l /dev/scsi/host0/bus0/target1/lun0/cd brwxrwxrwx 1 dave cdrom 11, 0 Dec 31 1969 /dev/scsi/host0/bus0/target1/lun0/cd

I have no idea if that will help.

And to answer your other question, when I am running the burner software setup program I am running as root.

Thanks!

Thane

Well, your /dev/scd0 isn't writable, so you may not be able to use it with a CD burner. I'm not too sure, but if I were you, I'd try the following:
1) Remove the /dev/scd0 symlink
2) Set the permissions correctly on the actual device (/dev/scsi/host0/bus0/target1/lun0/cd)
3) Set your umask to 0666 (I think this is right, maybe wait until someone else confirms it?)
4) Re-create the link

Hopefully that wlil help. The device at the moment seems to have alright permissions (as long as you want anyone to be able to access it) so you might just be able to tell 3kb that that is the device name.
Guy

Thanks Guy.


That appears to be the problem. I added write perms to the actual device (/dev/scsi/host0/bus0/target1/lun0/cd) then ran cdrecord -scanbus as root and it saw my burner. I then ran k3bsetup as root and all is well!

Thane.