Hallo all of you!

Well I've got a weird problem with my external DVD-burner.
I just finished installing Gentoo 2.6.14 with Gnome on my laptop.

My laptop has got an internal DVD-Burner (Pioneer somewhat) and i wanted to use my external (BenQ DW 1640 in an usb case).

Both drives are recognized and can be used to read cds/dvds in the filemanager nautilus. The internal dvd-burner is completely functionall, meaning it burns media. But the external doesn't get recognized in any burning-application. Neither in Graveman nor in k3b.

But cdrecord -scanbus says:

scsibus4:
4,0,0 400) 'BENQ ' 'DVD DD DW1640 ' 'BSMB' Removable CD-ROM
4,1,0 401) *
4,2,0 402) *
4,3,0 403) *
4,4,0 404) *
4,5,0 405) *
4,6,0 406) *
4,7,0 407) *

Meaning it is recognized as a burner.
Adding it manually to k3b failed, by the way.

I'd really appreciate some help, since I'm still quite new to linux (about 8 months now)

Thank you in advance,

Bjoern

Hi!
I realized that when logged in as root, I have access to both burners. Now can you tell me in which group I must put my regular user that I have access to it too? Or which permissions do I have to give?

Sorry for this noob-question but as already said, I'm new to linux!

Greets,
Bjoern

I had similar issues with my external DVD-RW, but since udev has been updated (I run all ~x86) it has been working correctly. Just make sure and run the K3B config utility and change the permissions.

Also, I found while I was having problems, that Nero for Linux worked fine. It just looks ugly, haha.

Hi!
Thanks a lot, that was the solution!!
I updated my previous 0.38 or somewhat version to 0.70-r1 and now it works fine!

Thanks again, finally I can make on-the-fly copies.

Greetings,
Bjoern

PS: I wonder why the current Gentoo Distribution delivers the old version of udev although there is this new one available. I installed 2.6.14-r2 just a week ago. Hmmm..

I run ~x86 to help test and I don't mind a few bugs here and there, but they don't move things into stable until it is tested VERY well usually. That is the reason behind the stable udev. udev has been going through a lot of changes as of late, and quite a few bugs have risen from that. I think it is best to keep the current stable one as stable until the bugs are worked out.

Either way, it is nice to be able to run mixed stable and testing like that.