Laurent,

Thanks so much for your help.

Here is all I could find from dmesg:

Boot video device is 0000:01:00.0
...
Linux video capture interface: v2.00
uvcvideo: Found UVC 1.00 device <unnamed> (046d:0994)
uvcvideo: UVC non compliance - GET_DEF(PROBE) not supported. Enabling 
workaround.
input: UVC Camera (046d:0994) as /class/input/input6
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v0.1.0)
...
uvcvideo: Failed to submit URB 0 (-28).

BTW, the camera connects to the computer via a USB connect, as you can see.

If there is other useful dianostic information I can provide using other 
commands, please tell me what I need to do.

Thanks again.

Laurent Pinchart wrote:
> Hi Bob,
> 
> On Monday 29 December 2008, Bob Marcum wrote:
> 
>>I am trying to diagnose and fix a problem I have using my videocam setup
>>and need some guidance.
>>
>>I am using a Logitech Orbit AF on Linux, using uvcvideo-0280330fd4a0, in
>>Skype communications.  When I make a connect I get the following log out to
>>the terminal:
>>
>> Starting the process...
>>Skype Xv: Xv ports available: 1
>>Skype XShm: XShm support enabled
>>Skype Xv: Using Xv port 65
>>Skype V4L2: Failed to activate streaming
>>Skype V4L2: Failed to initialise mmap buffers for capture
>>Skype Xv: Xv ports available: 0
>>Skype XShm: XShm support enabled
>>Skype Xv: Xv ports available: 0
>>
>>Note the "ports available: 1".  Seems to me I have to have available and
>>use at least two ports (one upstream and one down) to get two-way video
>>communications.  Note a few lines down, after the process has assigned the
>>one port available that "Xv ports available: 0".  Looks like a
>>configuration issue to me but I haven't a clue as to how to make any
>>adjustments that might fix this problem.
> 
> 
> Please note that "Xv ports" refer to interfaces between applications and the 
> X 
> server to display video through the X Video Extension (Xv), not to TCP/UDP 
> ports. They are anyway completely unrelated to the uvcvideo driver.
> 
> What might indicate uvcvideo problems, however, are the two V4L2 messages. 
> Please check your kernel log (using dmesg) for messages printed by the 
> uvcvideo driver.
> 
> Best regards,
> 
> Laurent Pinchart
> 
_______________________________________________
Linux-uvc-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Reply via email to