Alberto Hernando wrote:
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?

The answer depends upon the kernel and udev/hotplug version.

Old-style setup, works with any kernel and udev version (in fact, it works even without udev/hotplug):

Please be sure that there is a /proc/bus/usb line in /etc/fstab, and it mentions the "14" gid and "660" permissions. This creates pseudofiles like /proc/bus/usb/001/002 owned by the "usb" group. Add yourself to this group in order to use your camera. There were racy and non-working attempts to change permissions from hotplug scripts, they are not in the book.

New-style setup (linux >=2.6.14, udev >=081 and libusb >=0.1.12 are needed):

Please be sure that you have the long rule mentioned in http://wiki.linuxfromscratch.org/blfs/ticket/1680. This will create symlinks like /dev/bus/usb/1/2 -> /dev/usbdev1.2 to files owned by the "usb" group. Add yourself to this group in order to be able to use the devices. There is also a (currently debian-specific) script that generates udev rules for all known cameras and specifies a different group. You can do it yourself for your camera, matching on vendor and product IDs, like this:

# UMAX AstraPix 320s
BUS=="usb", SYSFS{idVendor}=="0d64", SYSFS{idProduct}=="1001", MODE="0660", GROUP="camera"

This rule catches all PTP cameras:

# USB PTP Class Camera
BUS=="usb", SYSFS{bDeviceClass}=="06", MODE="0660", GROUP="camera"

--
Alexander E. Patrakov

--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to