LinuxQuestions.org - udev-116-i486-1 and no access to camera with gtkam

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - udev-116-i486-1 and no access to camera with gtkam (https://www.linuxquestions.org/questions/slackware-14/udev-116-i486-1-and-no-access-to-camera-with-gtkam-594315/)

udev-116-i486-1 and no access to camera with gtkam

After upgrading from udev-111-i486-5 to mentioned version of udev I have no more any access to my camera with gtkam.

Under udev-111-i486-5 I added a rules file "99-libgphoto2.rules" to /etc/udev/rules.d/ and I could access my camera as user listed in /etc/group in plugdev.

This was the line in the rules file:

Code:

ATTRS{idVendor}=="04a9", ATTRS{idProduct}=="3074", MODE="660", GROUP="plugdev"

The correct values I got with

Code:

lsusb

and plugged-in camera.

So far my experience, I downgraded to the old version of udev to have a working connection to my camera.

Fluxx.

If you look at the post about 'udev and scanner' a few posts down the page, there seems to be a potential problem with udev.

Are you running Slackware 12.0? If so, why did you install the udev package from -current? Don't do that.
If you're running Slackware -current, then we'll go from there.

Sorry that I did not mention that I updated to Slackware current (I have it under my nickname at the left side of the topic, that I use Slackware current).

Yes, this happened with the update of the system during the last two days. After the error message I recompiled libgphoto, gphoto and gtkam, but no success.

The only solution was to downgrade the udev-package to the mentioned version. The rest of the system is "current".

Thank you for your reply,

Fluxx.

At this point, I don't know if udev or the other software is at fault (or perhaps the way udev is configured in -current, although that's not likely since we're now using pretty much a vanilla upstream configuration). PiterPunk is really the resident udev expert - I just put on a good act - so hopefully this will be figured out sooner rather than later. We're on good terms with the udev maintainers in a few other distributions, and I think we've all been working on 116 together for the most part, so we'll check with them tomorrow and see if they've gotten similar reports.
In the meantime, have a look at that other thread as mentioned above. In it, I mentioned a "udevinfo" command and PiterPunk mentioned creating a tarball of various files. Adjust the udevinfo line's device name as appropriate, and send those to us, please -- piterpunk@ and CC to rworkman@

Hi,

the solution was posted by niels.horn in this topic

http://www.linuxquestions.org/questi...=1#post2936048

and is working without problems for my camera in gtkam.

Thank you,

Fluxx.

Okay, the "solution" of course "works" but it's not ideal.
Please still send the requested information.

Here the output of

Code:

udevinfo --query=all --attribute-walk --name /dev/bus/usb/003/002 



looking at device '/devices/pci0000:00/0000:00:1d.1/usb3/3-1':

    KERNEL=="3-1"

    SUBSYSTEM=="usb"

    DRIVER=="usb"

    ATTR{product}=="Canon Digital Camera"

    ATTR{manufacturer}=="Canon Inc."

    ATTR{quirks}=="0x0"

    ATTR{maxchild}=="0"

    ATTR{version}==" 1.10"

    ATTR{devnum}=="2"

    ATTR{busnum}=="3"

    ATTR{speed}=="12"

    ATTR{bMaxPacketSize0}=="32"

    ATTR{bNumConfigurations}=="1"

    ATTR{bDeviceProtocol}=="00"

    ATTR{bDeviceSubClass}=="00"

    ATTR{bDeviceClass}=="00"

    ATTR{bcdDevice}=="0001"

    ATTR{idProduct}=="3074"

    ATTR{idVendor}=="04a9"

    ATTR{bMaxPower}=="100mA"

    ATTR{bmAttributes}=="c0"

    ATTR{bConfigurationValue}=="1"

    ATTR{bNumInterfaces}==" 1"

    ATTR{configuration}==""

    ATTR{dev}=="189:257"



  looking at parent device '/devices/pci0000:00/0000:00:1d.1/usb3':

    KERNELS=="usb3"

    SUBSYSTEMS=="usb"

    DRIVERS=="usb"

    ATTRS{serial}=="0000:00:1d.1"

    ATTRS{product}=="UHCI Host Controller"

    ATTRS{manufacturer}=="Linux 2.6.23.1-centr uhci_hcd"

    ATTRS{quirks}=="0x0"

    ATTRS{maxchild}=="2"

    ATTRS{version}==" 1.10"

    ATTRS{devnum}=="1"

    ATTRS{busnum}=="3"

    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"

    ATTRS{configuration}==""

    ATTRS{dev}=="189:256"



  looking at parent device '/devices/pci0000:00/0000:00:1d.1':

    KERNELS=="0000:00:1d.1"

    SUBSYSTEMS=="pci"

    DRIVERS=="uhci_hcd"

    ATTRS{msi_bus}==""

    ATTRS{broken_parity_status}=="0"

    ATTRS{modalias}=="pci:v00008086d00002659sv00001071sd00008048bc0Csc03i00"

    ATTRS{local_cpus}=="ffffffff"

    ATTRS{irq}=="17"

    ATTRS{class}=="0x0c0300"

    ATTRS{subsystem_device}=="0x8048"

    ATTRS{subsystem_vendor}=="0x1071"

    ATTRS{device}=="0x2659"

    ATTRS{vendor}=="0x8086"



  looking at parent device '/devices/pci0000:00':

    KERNELS=="pci0000:00"

    SUBSYSTEMS==""

    DRIVERS==""

    ATTRS{uevent}==""

Fluxx.

For the time being, this should work for you - put this in a custom 90-local.rules file:

Code:

SUBSYSTEM=="usb" \

  ATTR{product}=="Canon Digital Camera" \

  ATTR{manufacturer}=="Canon Inc." \

  GROUP:="plugdev" \

  MODE:="0664"

Please confirm whether or not this works.

Hi,

thank you for your reply, this is working without any errors!

Fluxx.