K3B Error: K3b did not find a suitable writer.

JockVSJock · 09-18-2006, 10:21 PM

You will only be able to create an image is what I'm getting when I try to burn a DVD.

I have K3B 0.12.17...and I know I have done an upgrade via swaret for K3B.

Before the upgrade I was able to burn dvds and cdr, no problem...Now when I try to add a device, it won't allow me and also when I go thru the K3B setup, it finds my Sony DVD burner but can't find my HP cdr burner.

What steps should I take to get this sucker working again?

thanks''

dracolich · 09-19-2006, 02:16 PM

Two things come to my mind: first, is the HP getting detected by the kernel and assigned to a device? second, if first is ok, have you checked the ownership and permissions on the HP's device.

JockVSJock · 09-19-2006, 08:04 PM

Update:

For some reason my cdrom burner won't open. I haven't tried the paper-clip opener yet, but something is really wrong. And I haven't done anything to my case since I build the PC, back in June.

So I will mess with it this weekend, and will report back.

thanks

JockVSJock · 10-11-2006, 01:59 PM

***UPDATE***

Ok, so I swapped around the ide flat cable for the following:

-the DVD burner is on the end, because it is newer
-the cd burnder is on the middle, cause it is older

and made sure the power connectors were well connected.

Once I rebooted, the cd player now can open and close the door, and I attempted to burn with both players...I still get the error from K3B

Code:

K3B Could not find a suitable writer.  
You will only be able to burn an image.

So I hit Google and entered in the error message and found this thread...

http://k3b.plainblack.com/message-bo...uitable-writer

Sure enough I am able to burn as root, but not as my regular user

This was the recommended solution

Quote:

Re: Could not find a suitable writer
User: Visitor
Date: 1/ 6/2006 5:56 pm
Views: 168
Rating: 8 Rate [

+
|

-
]

The problem is easy

1- Go to /etc/fstab to know how the name of your writer at /dev, in my case /dev/hdc

/dev/hdc /media/cdrecorder auto pamconsole,fscontext=system_u

bject_r:removable_t,ro,exec,noauto,managed 0 0

2- Open the terminal, login as root (su) then write this command to change the permission of your writer

chmod 666 /dev/hdc

3- Then open K3b again and it will work

I tried this and it didn't work, would I have to change permission under /dev?

thanks

dracolich · 10-11-2006, 02:22 PM

If you can burn as root then you're almost there. It should be just a permissions issue. The chmod command (run as root) is the one that changes permission under /dev. Is that the part that's not working? I always put it in my /etc/rc.d/rc.local file so it gets done during startup. If you change anything in fstab it should only be to add users to the options for /dev/hdc.

JockVSJock · 10-11-2006, 02:37 PM

So I find this out...

Code:

cmmiller@ladytron:~$ dmesg | more
 SONY DVD RW DRU-810A, ATAPI CD/DVD-ROM drive
hdd: Hewlett-Packard CD-Writer Plus 9500, 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: 488397168 sectors (250059 MB) w/16384KiB Cache, CHS=30401/255/63, UDMA(100)
hdc: attached ide-cdrom driver.

Then do this

Code:

cmmiller@ladytron:/dev$ ls -al | grep hdd
lrwxrwxrwx  1 root     root          8 2006-07-09 20:38 cdrom -> /dev/hdd

and then this...

Code:

cmmiller@ladytron:/dev$ ls -al | grep hdc
lrwxrwxrwx  1 root     root          8 2006-06-10 17:49 dvd -> /dev/hdc

As root, could I just change the owner (chown) of these devices because as ugo, they have full rights...?

thanks

dracolich · 10-11-2006, 04:41 PM

Quote:

cmmiller@ladytron:/dev$ ls -al | grep hdc
lrwxrwxrwx 1 root root 8 2006-06-10 17:49 dvd -> /dev/hdc

Notice the dvd -> /dev/hdc. This indicates that this is a link file linking /dev/dvd to /dev/hdc. Most if not all link files have full permissions. Instead of ls -al | grep hdc try ls -al /dev/hdc to get the ownership/permissions of hdc. I expect you'll find it to be root:disk rw-rw----

raska · 10-11-2006, 05:10 PM

Quote:

Originally Posted by dracolich

...I expect you'll find it to be root:disk rw-rw----

root:cdrom is likely too

JockVSJock check those permissions, add yourself to the group(s) the writer(s) are owned and keep the 660 mode on your devices. Also you can let k3b setup make those fixes, you need a new group and add yourself to it (k3b suggests burning group) and it also works fine.

rigelan · 10-11-2006, 06:47 PM

Yeah, just add yourself to the group CDROM It also allows you to play music if you add yourself to the group AUDIO. I don't mind this user management way to do things, I only wish I knew that this was OBVIOUSLY the way to fix my problems.

I usually use 'kuser' to do my user management. I find it pretty easy. But I can only do it by going through konqueror/system/kuser, because otherwise I don't have the authority to change users and groups.

JockVSJock · 10-12-2006, 11:51 AM

Quote:

Originally Posted by dracolich

Notice the dvd -> /dev/hdc. This indicates that this is a link file linking /dev/dvd to /dev/hdc. Most if not all link files have full permissions. Instead of ls -al | grep hdc try ls -al /dev/hdc to get the ownership/permissions of hdc. I expect you'll find it to be root:disk rw-rw----

Yes you are right...

Code:

root@ladytron:/dev# ls -al /dev/hdc
brw-rw---- 1 root disk 22, 0 2002-06-09 14:27 /dev/hdc
root@ladytron:/dev# ls -al /dev/hdd
brw-rw---- 1 root disk 22, 64 2002-06-09 14:27 /dev/hdd

Do I want to change the owner from root to my regular user on these devices?

Also I re-ran the K3B setup and there is a burning group and when I run it, it says there is no burning group...which is true, there isn't anything listed under /etc/group...Do I have to add this manually to /etc/group to get this to run?

thanks

dracolich · 10-12-2006, 11:57 AM

You have three choices, none of which includes changing the owner from root to a user:

1) K3B setup offers to create a group called burning and add your user to it.

2) Your hdc and hdd are both owned by the group called disk. Simply add your user to that group.

3) Add a line to your /etc/rc.d/rc.local to run during startup

Code:

chmod 666 /dev/hdc

raska · 10-12-2006, 12:07 PM

That's freedom of choice ladies and gents!

I would prefer the first choice to keep K3b happy. The second one is fine too. The third one is the less secure, I think.
I don't remember that K3b would create the group, it only sets the devices' group ownership on that one.
Whatever your choice, it's a piece o' cake, isn't it?

tfrei · 10-12-2006, 12:37 PM

Quote:

Originally Posted by dracolich

You have three choices, none of which includes changing the owner from root to a user:

1) K3B setup offers to create a group called burning and add your user to it.

2) Your hdc and hdd are both owned by the group called disk. Simply add your user to that group.

3) Add a line to your /etc/rc.d/rc.local to run during startup

Code:

chmod 666 /dev/hdc

Thanks dracolich. But with regard to number 1 above ...

I have another thread going re: k3b. My problem is that k3bsetup doesn't work. Does anybody else have this problem. Look at my output in trying to call it up as root:

Quote:

root@tom:/opt/kde/bin# k3bsetup
kcmshell (kdelibs): WARNING: Could not find module 'k3bsetup2'.
root@tom:/opt/kde/bin#

This is from a fresh install of Slackware 11.0. Was this module left out of the distribution?

JockVSJock · 10-12-2006, 01:28 PM

Hey guys, I was able to get K3B to burn for my regular user...thanks ...

As for tfrei, I don't understand why you can't run K3Bsetup either...

dracolich · 10-12-2006, 01:53 PM

tfrei, are you logged in as a user with a terminal opened and su-ed to be root? Did you try accessing the setup from K3B's Tools menu? The error refers to kdelibs not being able to find something required. Assuming you installed or upgraded all of the kde files from the Slackware CD this is my only idea. The Slackware package of K3B includes all required files. You could try reinstalling it with installpkg /path/to/k3b*.tgz to restore anything that might've gotten lost.