K3B Setup in gentoo

[fatshady]

I'm having issues with the setup in K3b. I have tried setting it up, but when I run the program as me it tells me that it cannot find cdrdao:

cdrdao
-----------------------
Cdrdao version 1.1.7 - (C) Andreas Mueller <andreas@daneb.de>
SCSI interface library - (C) Joerg Schilling
Paranoia DAE library - (C) Monty
Check http://cdrdao.sourceforge.net/drives.html#dt for current driver tables.
Using libscg version 'andreas-0.5-UNIXWARE_Patch'
0,0,0: SONY CD-RW CRX220E1 Rev: 6YS1
ERROR: No driver found for 'SONY CD-RW CRX220E1', available drivers:
cdd2600
generic-mmc
generic-mmc-raw
plextor
plextor-scan
ricoh-mp6200
sony-cdu920
sony-cdu948
taiyo-yuden
teac-cdr55
toshiba
yamaha-cdr10x
For all recent recorder models either the 'generic-mmc' or
the 'generic-mmc-raw' driver should work.
Use option '--driver' to force usage of a driver, e.g.: --driver generic-mmc
ERROR: Cannot setup device 0,0,0.

I think this is becuase of permissions as it does run fine when i am logged in as root. Also it does not recognise my DVD drive as am input drive.

Do I need to put myself in the cdrecording group? If so how do i do that?

I have tried to look for this on these forums, and Gentoo's forums and K3B website - but I've turned up nothing.

I have tried to re-emerge it to solve a prob with the setup, which means it asks whether i want to save the data when it finishes, as though I told it to close before it was done, but it does remember the settings i put in...

Any help greatfully recieved.

Cheers

D

[hard candy]

You probably have to put "hdc (or "d", "e" whatever the drive name is)=ide-scsi on the same line as "kernel (hd0,0)/bzImage ro root=/dev***" line in the bootloader cong file (i.e, /boot/grub/grub.config).
Good luck.

[fatshady]

Thanks for the help hard candy,

I have that for the CDRW drive in my lilo.conf already. This is the relevant part of my lilo.conf i think.


image = /boot/bzImage
root = /dev/hda3
#root = /devices/discs/disc0/part3
label = Gentoo
append="hdd=ide-scsi"
read-only # read-only for checking


If i run cdrecord --scanbus then I get the following output.


root@excaliber dan # cdrecord --scanbus
Cdrecord 2.01a14 (i686-pc-linux-gnu) Copyright (C) 1995-2003 Jörg Schilling
Linux sg driver version: 3.1.24
Using libscg version 'schily-0.7'
scsibus0:
0,0,0 0) 'SONY ' 'CD-RW CRX220E1 ' '6YS1' Removable CD-ROM
0,1,0 1) *
0,2,0 2) *
0,3,0 3) *
0,4,0 4) *
0,5,0 5) *
0,6,0 6) *
0,7,0 7) *

Which i think means that my CDRW is recognised by the systems and should work?

Any help anyone - i can burn CD's its just really annoying have to log in as root - mainly cos i can't do anything else for fear of screwing it up!!

[nothingbutlinux]

This sounds very similar to a problem I had with K3B ... I could burn fine when logged in as root, but not as a normal user. If you run "K3B setup", the 5th page of the dialog is where you add users that will use K3B. Near the bottom is a space for the CD Writing group. K3B sets the default to "cdrecording" but I couldn't get it to work no matter what I tried. I checked permissions, verified my normal user was a member of that group, and everything looked fine.

Finally I changed the CD Writing group to "cdrom", verified my users were members, and it worked great! I'm sure there's permissions that aren't getting set right with "cdrecording", but I couldn't find it. K3B is suppose to set all the permissions and group settings for you, but like I said, it didn't work until I changed the group to "cdrom".

I"m curious if that will fix your problem.

[fatshady]

Cheers - I'll try that when i get home - how can I make sure my user is in the group cdrom, and add then to it if nessacery?

[hard candy]

I assume you're using KDE, there may be Kuser in your menu. Or emerge addusr or superadduser and "man adduser" from command line.

[fatshady]

Well I tried, but no I cannot su in as root, or put in the correct password when it asks for the root password, but i can log into KDE as root...

Is there a group I am missing - got users and thast about it except for all the ones i have tried for K3B..

What going on.. Also adding myself to all the rgoups i think it can be doesn't work...

Argghhh.. Anyone help?

[mdwatts]

Does K3B have anything in the preferences/options to setup normal user usage as XCDRoast does?

With XCDRoast, you run it the first time as root, configure to allow normal users, save the config and then run as a regular user.

[fatshady]

You have to set it up as root, and then you sould be able to run it as user, but i couldn't... and now i have no su capabilities now as my main user.. and i cannot configure K3B without logging in and out...

What poss reasons can I not su into root.. I don't have permission apparently... Whats the likely cause for this?

[fatshady]

Problem solved - uninstall user, but don't delete the /home/user dir, and then useradd and thats all sorted - it's all done from the X11 RC4 intruction manual

[fatshady]

to Nothingbutlinux,

It did't work - I still can't use it - I still have the same error about cdrdao, and I know it all works cos I have just burned about 8 CD's for a friend, but logged in as root - which I'm still really twitchy about... :(

And it should work.. My user is in th relevent group - i have chmod'd cdrdao do it is open to all to write/read/execute...

Why doesn't it work?::confused: :confused:

This is really beginning to annoy....

[nothingbutlinux]

Rats, I was hoping that would work, your problem sounds so similar to mine. Just a couple questions ... what group is associated with cdrdao? When I ran K3B setup and changed the group to "cdrom", K3B changed the group association to cdrom.

[fatshady]

I have tried various groups - at the moment it is called burning, and my username is a member of that grouop (also tried groups cdrw, cdrom, cdrecording)...

It's enough to drive you insane... thought it might be something in the way it compiled - tried "emerge -C K3B" - but when merge it again all the same problems.

So far as i can make out - i do not have permission to access cdrdao, but i'm in the group - and everyone should be able to w/r/x...

The file belongs to root - is that right? From the stuff I have read it is, but I am now beginning to wonder....

[nothingbutlinux]

Originally posted by fatshady
The file belongs to root - is that right? From the stuff I have read it is, but I am now beginning to wonder.... Yeah, that's right, mine is the same. I honestly don't think K3B setup is doing what it is suppose to. Maybe I got lucky when I changed the group to "cdrom", but that's what fixed it for me.

[hard candy]

In my gentoo set-up the user is a member of the wheel, cdrw,cdrom, cdrecording, and audio groups.

[fatshady]

OK - cool - which group owns cdrdao, and the other two files i need?

Mine are owned by the group burning of which i am a member..

I guess i'll try joining all of them and see what happens. I re-icreated the user last night as a member of audio, wheel, and users - also no burning as well - which is the group that owns the cdrdao file...

I'll go through it all tonight - and if i work it out I'm gonna write a how-to cos this is enough to make anyone (who isn't me) give up on it... all i wanna do is write cd's <starts crying>

[hard candy]

(Hands over a tissue as fatshady sniffs)
For cdrdao the owner is root and the group owner is cdrecording of which the user is a member. And the group can execute cdrdao.
Which other files were you referring to?

[fatshady]

I have cdtools or cdrecord (I think I have both but only one is used by K3B) which is owned by rot, in the burning group of which user is a member.

When I run K3B setup on the second screen (i think) it asks for programs it can use and their paths and stuff - cdrdao is in that, along with two others (unfortunately I'm not infront of my box nowand my memory is a bit sketchy) one of them is cdrecord and i can't remember the other one...

They are also owned by root, in the burning group.

[hard candy]

( unfurls umbrella to avoid getting soaked)

I'm at work now too, but I seem to remember that cdrecord should be owned by the same group, cdrecording.

And what are the permissions on the device itself (dev/cd**)?

[fatshady]

This is the output from ls -al /dev/cd*

lr-xr-xr-x 1 root root 33 Jan 1 1970 cdrom0 -> ../ide/host0/bus1/target0/lun0/cd
lr-xr-xr-x 1 root root 34 Jan 1 1970 cdrom1 -> ../scsi/host0/bus0/target0/lun0/cd

That might explain my problem - should these be owned by burning too? I would have thought so, cos then as long as user and root are members of burning that should be OK.. yes?

[hard candy]

have you considered the possibility of slightly salty water (i.e, tears) getting into the drive and messing up the permissions? :)

I would try the change, you can always change it back.

[fatshady]

Well - that didn't work either...

I don't think it likes me... I can feel the tears coming on again!! :(

[hard candy]

I found this on a Suse message board:
Anyway, to
make sure you can burn with the recorder device change the group
permission to disk (make sure that device sr0 is changed, the symlink
may or may not change by it's self as well. If not then change the
symlink group permissions to disk). Of course you need to do this as
"root" (forgive me if I'm oversimplifying, I don't know your level of
experience).
It should read something like: /dev/cdrecorder points to /dev/sr0, and
furthermore should look like this:
~ la /dev/sr0
rwxrwxr-x root disk /dev/sr0
or
user root
group disks
and like wise for /dev/cdrecorder symlink.
Then you need to make sure that the users, such as your own user account
are added to the group "disks"
You can also change the group of the device and it's symlink to "users"
if you want. But changing it to disks and giving the group "disks"
read, write, and execute permissions should do it. If you need further
help please post to the list agian. "
We might be changing permissions on a sym-link. Also I read that you need to reboot or start some service but I can't figure which one.

[fatshady]

Well - i changed the driver in the options instead of the setup program on a complete guess and it has worked - i don't understand why - but it appears the K3B setup program does not work, but the options in the program do work...

Ho humm...

Sorry if it wasted too much time - but i didn't expect it to be that wierd...

Cheers

D

[hard candy]

So it's safe to put away the umbrella, take off the raincoat and galoshes, etc?

[fatshady]

I think so...

Cheers for your help...