F13: UVC camera suddenly stopped working?

dillinga · #1 11th June 2010, 05:43 AM

Hi Guys,

Finally got around to dual-booting and all was going well. I was surprised to see that the webcam on my Vaio worked straight away. However, some time between one boot and another the webcam mysteriously stopped working..

Here is the last time it worked:

Jun 6 23:12:51 dillinga kernel: uvcvideo: Found UVC 1.00 device <unnamed> (05ca:1837)
Jun 6 23:12:51 dillinga kernel: input: UVC Camera (05ca:1837) as /devices/pci0000:00/0000:00:1a.7/usb1/1-2/1-2:1.0/input/input12

Then the next boot:

Jun 6 23:41:48 dillinga kernel: uvcvideo: Found UVC 1.00 device <unnamed> (05ca:1837)
Jun 6 23:41:48 dillinga kernel: uvcvideo: UVC non compliance - GET_DEF(PROBE) not supported. Enabling workaround.
Jun 6 23:41:48 dillinga kernel: uvcvideo: Failed to query (129) UVC probe control : -32 (exp. 26).
Jun 6 23:41:48 dillinga kernel: uvcvideo: Failed to initialize the device (-5).
Jun 6 23:41:48 dillinga kernel: usbcore: registered new interface driver uvcvideo
Jun 6 23:41:48 dillinga kernel: USB Video Class driver (v0.1.0)

I've checked the rpmdb and I can't see anything installed between these times. I thought this might have been an issue introduced after the full 'yum update' but I can see I booted using the newer kernel each time so this seems unlikely.

I can still see the device in lsusb:

Bus 001 Device 002: ID 05ca:1837 Ricoh Co., Ltd Visual Communication Camera VGP-VCC4 [R5U870]

An rmmod uvcvideo && modprobe uvcvideo just shows the same error.

Any ideas?

Tony

---------- Post added at 08:43 PM CDT ---------- Previous post was at 07:51 PM CDT ----------

So I decided to boot into windows and make sure all was OK - and it was.

Then I came back into Fedora and suddenly the camera was working again!

I thought I'd reboot just to see if anything changed and alas here I am again with no webcam and the same error.

Any ideas why this might be happening?

Thanks

misiu_mp · #2 28th June 2010, 09:48 AM

I have the same problem with a Logitech 046d:08c1 (fusion?). It worked once, then it stopped and I'm getting the same dmesg log as described above. (Tried on current F11, F12, F13).
Curiously, according to http://www.ideasonboard.org/uvc/, my camera is supposed to be fully supported.

**AdamW** · #3 28th June 2010, 09:55 PM

it sounds like the cam needs some kind of firmware which Windows uploads to it.

I suspect it works whenever you do a warm reboot from Windows to Linux, but fails whenever you cold boot into Linux - i.e. any time you shut down the system fully then boot Linux, it'll fail. is that accurate?

misiu_mp · #4 29th June 2010, 07:50 PM

Not really. I didn't use the cam for months so it must have been stone cold. Recently I plugged it in for the first time since into a computer and it was running fedora. And the cam worked! I then unplugged it and plugged it into another computer running fedora and it did not work again.

**AdamW** · #5 29th June 2010, 10:18 PM

Hum. That's my guess out of the window then. Not sure what else could explain it. It could just be temperamental hardware?

dillinga · #6 3rd July 2010, 05:32 PM

Same for me really. Sometimes it works after booting into windows and then back to Fedora and other not at all...

SiliconSlick · #7 3rd July 2010, 08:09 PM

You could try playing with uvcvideos quirks and trace options. Not sure the best to use. I see a lot of recommendations for using quirks=2. So I would try (to start with):

rmmod uvcvideo
modprobe uvcvideo quirks=2 trace=15

FWIW, here's the closest thing I could find in terms of documentation for each (from uvcvideo.h):

Code:

[snip]
/* Devices quirks */
#define UVC_QUIRK_STATUS_INTERVAL       0x00000001
#define UVC_QUIRK_PROBE_MINMAX          0x00000002
#define UVC_QUIRK_PROBE_EXTRAFIELDS     0x00000004
#define UVC_QUIRK_BUILTIN_ISIGHT        0x00000008
#define UVC_QUIRK_STREAM_NO_FID         0x00000010
#define UVC_QUIRK_IGNORE_SELECTOR_UNIT  0x00000020
#define UVC_QUIRK_FIX_BANDWIDTH         0x00000080
#define UVC_QUIRK_PROBE_DEF             0x00000100
[snip]
/* ------------------------------------------------------------------------
 * Debugging, printing and logging
 */

#define UVC_TRACE_PROBE         (1 << 0)
#define UVC_TRACE_DESCR         (1 << 1)
#define UVC_TRACE_CONTROL       (1 << 2)
#define UVC_TRACE_FORMAT        (1 << 3)
#define UVC_TRACE_CAPTURE       (1 << 4)
#define UVC_TRACE_CALLS         (1 << 5)
#define UVC_TRACE_IOCTL         (1 << 6)
#define UVC_TRACE_FRAME         (1 << 7)
#define UVC_TRACE_SUSPEND       (1 << 8)
#define UVC_TRACE_STATUS        (1 << 9)
#define UVC_TRACE_VIDEO         (1 << 10)
[snip]

So, AFAICT, quirks=2 has something to do with probing the device and trace=15 will get debug stuff in the system log for PROBE/DESCR/CONTROL/FORMAT (probably all you really want is PROBE but the more the better).

Something to try...

SS

dillinga · #8 4th July 2010, 01:06 AM

Thanks SS. Just gave this a go. It does provide some more info (annoyingly) but the end result is the same:

uvcvideo: Adding mapping Brightness to control 00000000-0000-0000-0000-000000000101/2.
uvcvideo: Adding mapping Contrast to control 00000000-0000-0000-0000-000000000101/3.
uvcvideo: Adding mapping Hue to control 00000000-0000-0000-0000-000000000101/6.
uvcvideo: Adding mapping Saturation to control 00000000-0000-0000-0000-000000000101/7.
uvcvideo: Adding mapping Sharpness to control 00000000-0000-0000-0000-000000000101/8.
uvcvideo: Adding mapping Gamma to control 00000000-0000-0000-0000-000000000101/9.
uvcvideo: Adding mapping Backlight Compensation to control 00000000-0000-0000-0000-000000000101/1.
uvcvideo: Adding mapping Gain to control 00000000-0000-0000-0000-000000000101/4.
uvcvideo: Adding mapping Power Line Frequency to control 00000000-0000-0000-0000-000000000101/5.
uvcvideo: Adding mapping Hue, Auto to control 00000000-0000-0000-0000-000000000101/16.
uvcvideo: Adding mapping Exposure, Auto to control 00000000-0000-0000-0000-000000000001/2.
uvcvideo: Adding mapping Exposure, Auto Priority to control 00000000-0000-0000-0000-000000000001/3.
uvcvideo: Adding mapping Exposure (Absolute) to control 00000000-0000-0000-0000-000000000001/4.
uvcvideo: Adding mapping White Balance Temperature, Auto to control 00000000-0000-0000-0000-000000000101/11.
uvcvideo: Adding mapping White Balance Temperature to control 00000000-0000-0000-0000-000000000101/10.
uvcvideo: Adding mapping White Balance Component, Auto to control 00000000-0000-0000-0000-000000000101/13.
uvcvideo: Adding mapping White Balance Blue Component to control 00000000-0000-0000-0000-000000000101/12.
uvcvideo: Adding mapping White Balance Red Component to control 00000000-0000-0000-0000-000000000101/12.
uvcvideo: Adding mapping Focus (absolute) to control 00000000-0000-0000-0000-000000000001/6.
uvcvideo: Adding mapping Focus, Auto to control 00000000-0000-0000-0000-000000000001/8.
uvcvideo: Adding mapping Zoom, Absolute to control 00000000-0000-0000-0000-000000000001/11.
uvcvideo: Adding mapping Zoom, Continuous to control 00000000-0000-0000-0000-000000000001/12.
uvcvideo: Adding mapping Privacy to control 00000000-0000-0000-0000-000000000001/17.
uvcvideo: Probing generic UVC device 2
uvcvideo: Found format YUV 4:2:2 (YUYV).
uvcvideo: - 640x480 (30.0 fps)
uvcvideo: - 320x240 (30.0 fps)
uvcvideo: - 176x144 (30.0 fps)
uvcvideo: - 160x120 (30.0 fps)
uvcvideo: Found a Status endpoint (addr 82).
uvcvideo: Found UVC 1.00 device <unnamed> (05ca:1837)
uvcvideo: Forcing device quirks 0x2 by module parameter for testing purpose.
uvcvideo: Please report required quirks to the linux-uvc-devel mailing list.
uvcvideo: Added control 00000000-0000-0000-0000-000000000101/2 to device 2 entity 2
uvcvideo: Added control 00000000-0000-0000-0000-000000000101/3 to device 2 entity 2
uvcvideo: Added control 00000000-0000-0000-0000-000000000101/6 to device 2 entity 2
uvcvideo: Added control 00000000-0000-0000-0000-000000000101/7 to device 2 entity 2
uvcvideo: Added control 00000000-0000-0000-0000-000000000101/8 to device 2 entity 2
uvcvideo: Added control 00000000-0000-0000-0000-000000000101/9 to device 2 entity 2
uvcvideo: Added control 00000000-0000-0000-0000-000000000101/1 to device 2 entity 2
uvcvideo: Added control 00000000-0000-0000-0000-000000000101/5 to device 2 entity 2
uvcvideo: Scanning UVC chain: OT 3 <- XU 4 <- PU 2 <- IT 1
uvcvideo: Found a valid video chain (1 -> 3).
uvcvideo: UVC non compliance - GET_DEF(PROBE) not supported. Enabling workaround.
uvcvideo: Failed to query (129) UVC probe control : -32 (exp. 26).
uvcvideo: Failed to initialize the device (-5).
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v0.1.0)

SiliconSlick · #9 4th July 2010, 01:19 AM

It seems to be a probe problem so you could probably just set trace=1 (PROBE). I would try different combinations of the sums of 2, 4 and 256 for the (PROBE) quirks. e.g. quirks=262 would toggle all the ones labeled PROBE.

At the very least the trace of just the probe should reduce the spam.

SS (who doesn't have such a device here to test with)