QuickCam Team Forums

Full Version: dynctrl doesnt get triggered by udev (ubuntu/hardy)
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hi,

the dynamic controls dont get added by the udev script as they should. I investigated a bit and found out that the script is looking for "idVendor" and "idProduct" files in the /sys diectory tree. The script logfile states:

Code:
VID of new device: ''
PID of new device: ''
ERROR: Unable to extract USB VID from '/sys/sys/devices/pci0000:00/0000:00:1d.7/../idVendor'.


I found two files which appear to hold those IDs: "vendor" and "device".
So I changed the script to look for those files. But it still fails:

Code:
VID of new device: '0x8086'
PID of new device: '0x265c'
ERROR: Device is not handled by uvcvideo but by 'ehci_hcd'.


Any ideas?


cheers,
Janosch

The VID and PID that your modified script extracted definitely don't belong to a Logitech webcam. VID 8086 seems to be Intel. It's also obvious that the first path with the /sys/sys can't be right.

First of all, could you post the output of "lsusb" and the complete section of the log file?

You can also look if you can find other idVendor and idProduct files in your /sys tree. The correct directory should have a vendor ID of 046d and the product ID corresponding to your camera (check this list).
VID 8086 = Intel
PID 265C = 82801FB (ICH6) USB 2.0 EHCI Controller

Source = Craig Hart's pcidevs.txt

Thanks.
Ok I obviously used the wrong device. I ran uvcdynctrl manually for testing purposes.
I have the same issue in Ubuntu Hardy. After looking at /tmp/uvcdynctrl-udev.log, I find that Ubuntu Hardy does not define PHYSDEVPATH variable in the udev script, as discussed in this thread;
http://forums.quickcamteam.net/showthread.php?tid=161

Any workaround?
Reference URL's