Odd, you shouldn't have two devices unless you physically have two boxes
plugged in! avcctrl is struggling because the avcap1 device does not
correspond to actual hardware, and it seems odd that it is always deferring
to this path. What other USB devices do you have installed? Try removing them
all, rmmod the avc2210k module, and replug just the video capture box. What
happens then? Do you just get the one device?
John.
Thanks - we 're making progress - a device is now created:- crw-rw-rw- 1 root usb 180, 0 Apr 6 21:06 /dev/avcap0 crw-rw-rw- 1 root usb 180, 1 Apr 6 21:24 /dev/avcap1
I've copied all the correct drivers to /var/lib/firmware/ now (I missed some files and put the drivers for the the 2210, instead of the 2310). I'm using udev and multilib is installed - /usr/sbin/multiload
/etc/multiload.conf is as the standard install.
So now I'm getting the following:- Apr 6 21:24:36 jdally usb 2-6: new high speed USB device using ehci_hcd and address 12 Apr 6 21:24:36 jdally usb 2-6: configuration #1 chosen from 1 choice Apr 6 21:24:37 jdally usb 2-6: USB disconnect, address 12 Apr 6 21:24:38 jdally usb 2-6: new high speed USB device using ehci_hcd and address 13 Apr 6 21:24:39 jdally usb 2-6: configuration #1 chosen from 1 choice Apr 6 21:24:39 jdally AVC2x10K : attached new device at index 0 Apr 6 21:24:39 jdally AVC2x10: found vidcap IC id SAA7115
and the light on the front of the box has turned green (was orange). But avcctrl still seems to be struggling:- # avcctrl -v -i 0 lib init AVCCONFInit running retrieve int array string =1,2 got int array rc=0 retrieve int array string =3,4 got int array rc=0 error handler init running aarg DEVOpenDevice - dpath=|/dev/avcap1| DEVOpenDevice - hdev=|0| error: unable to open device (null) lib term
and the same if I run it with avcctrl -v -i 0 (as two devices are created).
Cheers
John
