Re: debugging webcamd in CURRENT

From: Hans Petter Selasky <hps_at_selasky.org>
Date: Mon, 20 Mar 2017 14:21:28 +0100
On 03/20/17 14:14, Matthias Apitz wrote:
>
> Hello,
>
> I have a very recent 12-CURRENT on amd64 (r314251) with all ports from beginning
> of March.
>
> While testing multimedia/webcamd in debug mode it says:
>
> # /usr/local/sbin/webcamd -i 0 -d ugen0.2 -U webcamd -G webcamd -H
> : USB HID core driver
> Linux video capture interface: v2.00
> IR NEC protocol handler initialized
> IR RC5(x/sz) protocol handler initialized
> IR RC6 protocol handler initialized
> IR JVC protocol handler initialized
> IR Sony protocol handler initialized
> IR SANYO protocol handler initialized
> IR LIRC bridge handler initialized
> IR XMP protocol handler initialized
> b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV receiver chip loaded successfully
> uvcvideo: Unable to create debugfs directory
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> USB Video Class driver (1.1.1)
> cpia2: V4L-Driver for Vision CPiA2 based cameras v3.0.1
> pvrusb2: V4L in-tree version:Hauppauge WinTV-PVR-USB2 MPEG2 Encoder/Tuner
> pvrusb2: Debug mask is 31 (0x1f)
> USBVision USB Video Device Driver for Linux : 0.9.11
> em28xx: Registered (Em28xx v4l2 Extension) extension
> em28xx: Registered (Em28xx dvb Extension) extension
> Attached to ugen0.2[0]
> uvcvideo: Found UVC 1.00 device HD WebCam (1bcf:2c67)
> Waiting for HAL USB device.
> Creating /dev/video0
> uvcvideo: Failed to submit URB 0 (-32).
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> Questions about this:
>
> 1. Why it is unable to create the debugfs directory?
> 2. The UVC driver in
> multimedia/webcamd/work/webcamd-4.8.0.4/media_tree/drivers/media/usb/uvc
> is from between 2013-2016, is there any more recent version?
> 3. Why is it sometimes failing with 'Failed to submit URB 0 (-32)'?
>

Hi,

The latest version is in ports. You can compile webcamd with debugging. 
Then there are some options listed by "webcamd -s" which you can turn on 
using "webcamd -m xxx=yyy" to get more verbose debugging. You can also 
try starting "usbdump -i usbusX -f Y -s 65536" where X and Y are numbers 
after ugen, before plugging the device, to see which USB errors are 
happening.

--HPS

--HPS
Received on Mon Mar 20 2017 - 12:22:29 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:10 UTC