Dan Nicholson wrote:
Do you have permissions as an ordinary user? If it's a usb camera, it
should be following the udev rule we install with libusb:
SUBSYSTEM=="usb_device", GROUP="usb". Is that not working? Are the
permissions not coming out correctly in /dev/bus/usb?
I don't think pam has anything directly to do with gphoto. When you
say gphoto can't detect your camera, what do you mean? The
autodetection in HAL isn't working? Running gphoto from the command
line doesn't work?
I certainly had a camera working correctly with hal and the whole like.
--
Dan
I, too am having a similar or perhaps even the same issue that I
discovered just yesterday. I built CLFS using the SVN in November 2005.
With that build, digikam and such worked fine and I used my camera. I
have recently upgraded a large portion of the base CLFS packages from
the SVN in October/November. I am running x86_64 multilib. The system
is stable and everything has been working fine for me until yesterday
when I discovered that I could not access my camera. This was the first
time I tried since the upgrades I did, so something there isn't playing
the same. I've yet to figure out exactly what. I am now running kernel
2.6.18.3 and udev-100, etc. etc., mostly current packages. I have not
changed or updated digikam, it's dependent libraries, or KDE. I have
KDE 3.4.2. The problem does not seem to stem from the kernel or udev as
it appears to me as though that is working normally. The error I get
from digikam is "failed to connect the camera" I've not yet been able
to get any further details than that, but I suspect that some of the
digikam dependencies and/or digikam itself may need to be re-compiled
against the current packages in the base system. Or perhaps there is a
tweak in the udev rules or somewhere that will solve the issue. I don't
really have time to pursue this myself right now, but wanted to throw
out what I'm seeing since I think it may fit the discussion here BTW, I
am not using HAL or DBUS. The permissions at least in my case are
correct in /dev/bus/usb. Here is some output from udev, which looks
just fine as far as I can tell.
udevinfo -a -p /sys/class/usb_device/usbdev2.21
Udevinfo starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/class/usb_device/usbdev2.21':
KERNEL=="usbdev2.21"
SUBSYSTEM=="usb_device"
DRIVER==""
ATTR{dev}=="189:148"
looking at parent device '/devices/pci0000:00/0000:00:02.0/usb2/2-8':
KERNELS=="2-8"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{configuration}==""
ATTRS{serial}=="KJCCR35200094"
ATTRS{product}=="KODAK EasyShare DX6490 Zoom Digital Camera"
ATTRS{manufacturer}=="Eastman Kodak Company"
ATTRS{maxchild}=="0"
ATTRS{version}==" 2.00"
ATTRS{devnum}=="21"
ATTRS{speed}=="12"
ATTRS{bMaxPacketSize0}=="8"
ATTRS{bNumConfigurations}=="1"
ATTRS{bDeviceProtocol}=="00"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceClass}=="00"
ATTRS{bcdDevice}=="0100"
ATTRS{idProduct}=="0575"
ATTRS{idVendor}=="040a"
ATTRS{bMaxPower}==" 2mA"
ATTRS{bmAttributes}=="c0"
ATTRS{bConfigurationValue}=="1"
ATTRS{bNumInterfaces}==" 1"
looking at parent device '/devices/pci0000:00/0000:00:02.0/usb2':
KERNELS=="usb2"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{configuration}==""
ATTRS{serial}=="0000:00:02.0"
ATTRS{product}=="OHCI Host Controller"
ATTRS{manufacturer}=="Linux 2.6.18.3-lfs-stan ohci_hcd"
ATTRS{maxchild}=="10"
ATTRS{version}==" 1.10"
ATTRS{devnum}=="1"
ATTRS{speed}=="12"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{bNumConfigurations}=="1"
ATTRS{bDeviceProtocol}=="00"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceClass}=="09"
ATTRS{bcdDevice}=="0206"
ATTRS{idProduct}=="0000"
ATTRS{idVendor}=="0000"
ATTRS{bMaxPower}==" 0mA"
ATTRS{bmAttributes}=="e0"
ATTRS{bConfigurationValue}=="1"
ATTRS{bNumInterfaces}==" 1"
looking at parent device '/devices/pci0000:00/0000:00:02.0':
KERNELS=="0000:00:02.0"
SUBSYSTEMS=="pci"
DRIVERS=="ohci_hcd"
ATTRS{broken_parity_status}=="0"
ATTRS{enable}=="1"
ATTRS{modalias}=="pci:v000010DEd0000005Asv00001458sd00005004bc0Csc03i10"
ATTRS{local_cpus}=="3"
ATTRS{irq}=="225"
ATTRS{class}=="0x0c0310"
ATTRS{subsystem_device}=="0x5004"
ATTRS{subsystem_vendor}=="0x1458"
ATTRS{device}=="0x005a"
ATTRS{vendor}=="0x10de"
looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""
udevtest /sys/bus/usb/devices/usb2/usb_device:usbdev2.1
This program is for debugging only, it does not create any node,
or run any program specified by a RUN key. It may show incorrect results,
if rules match against subsystem specfic kernel event variables.
main: looking at device '/class/usb_device/usbdev2.1' from subsystem
'usb_device'
run_program: '/bin/sh -c 'K=usbdev2.1; K=${K#usbdev}; printf
bus/usb/%03i/%03i ${K%%.*} ${K#*.}''
run_program: '/bin/sh' (stdout) 'bus/usb/002/001'
run_program: '/bin/sh' returned with status 0
udev_rules_get_name: rule applied, 'usbdev2.1' becomes 'bus/usb/002/001'
udev_db_get_device: found a symlink as db file
udev_device_event: device '/class/usb_device/usbdev2.1' already in
database, validate currently present symlinks
udev_node_add: creating device node '/dev/bus/usb/002/001', major =
'189', minor = '128', mode = '0664', uid = '0', gid = '100'
main: run: '/sbin/udev_run_hotplugd'
main: run: '/sbin/udev_run_devd'
main: run: 'socket:/org/kernel/udev/monitor'
---------
I did try deleting my camera from digikam and having it autodetect it
again, which it did do, but it refuses to open it.
Stan
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
