On 4/27/06, Alberto Hernando <[EMAIL PROTECTED]> wrote: > Hi. > > I'm trying to connect to my digital camera using digikam&gphoto, and I have a > problem with permissions, because root can access. When I connect the camera, > I get a /dev/usbdevX device, owned by root.root and with 660. I've read all > my udev rules and there is nothing for this, so I don't know what to do. I > tried to install the latest udev (kernel i 2.6.16) but it conflicts with > hotplug and even if I remove the hotplug init script, the system doesn't work > well, or doesn't boot. So I'm bak to udev-056. What do I need to do to access > my camera?
You should be able to use udev newer than that, but that's not the issue. You need a udev rule, and you need one that conforms with newer usb naming conventions. See this bug that hasn't reached reached a conclusion yet. Add that long rule (you could make it a separate file to keep track of it like 20-libusb.rules). http://wiki.linuxfromscratch.org/blfs/ticket/1680 Then you should have nodes in /dev/bus/usb/x/y owned by group usb with 0660 permissions. Beware that if you're using libusb <= 1.12.0, you'd need a patch referenced in the link on that bug to make libusb aware of that device location. Alternatively, you can leave your setup as is and add a rule like this (maybe 15-myrules.rules, should be before 25-lfs.rules): BUS=="usb", SYSFS{product}=="Canon Digital Camera", SYMLINK+="camera/canon", GROUP:=camera You have to mess around with udev to figure out the write key for matching your camera. The SYMLINK is unnecessary, but could be helpful. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
