Hi Ivan,

On Friday 10 October 2008, Ivan Babkin wrote:
> Hi!
>
> I have a problem with a built-in camera in my Samsung Q310 laptop.
>
> After "modprobe uvcvideo trace=15" I get the following in dmesg:
>
> [ 4149.432261] uvcvideo: Adding mapping Brightness to control
> 00000000-0000-0000-0000-000000000101/2.
> [ 4149.434693] uvcvideo: Adding mapping Contrast to control
> 00000000-0000-0000-0000-000000000101/3.
> [ 4149.436971] uvcvideo: Adding mapping Hue to control
> 00000000-0000-0000-0000-000000000101/6.
> [ 4149.439150] uvcvideo: Adding mapping Saturation to control
> 00000000-0000-0000-0000-000000000101/7.
> [ 4149.440291] uvcvideo: Adding mapping Sharpness to control
> 00000000-0000-0000-0000-000000000101/8.
> [ 4149.441371] uvcvideo: Adding mapping Gamma to control
> 00000000-0000-0000-0000-000000000101/9.
> [ 4149.442396] uvcvideo: Adding mapping Backlight Compensation to
> control 00000000-0000-0000-0000-000000000101/1.
> [ 4149.443594] uvcvideo: Adding mapping Gain to control
> 00000000-0000-0000-0000-000000000101/4.
> [ 4149.444610] uvcvideo: Adding mapping Power Line Frequency to control
> 00000000-0000-0000-0000-000000000101/5.
> [ 4149.445796] uvcvideo: Adding mapping Hue, Auto to control
> 00000000-0000-0000-0000-000000000101/16.
> [ 4149.446867] uvcvideo: Adding mapping Exposure, Auto to control
> 00000000-0000-0000-0000-000000000001/2.
> [ 4149.447994] uvcvideo: Adding mapping Exposure, Auto Priority to
> control 00000000-0000-0000-0000-000000000001/3.
> [ 4149.449215] uvcvideo: Adding mapping Exposure (Absolute) to control
> 00000000-0000-0000-0000-000000000001/4.
> [ 4149.450386] uvcvideo: Adding mapping White Balance Temperature, Auto
> to control 00000000-0000-0000-0000-000000000101/11.
> [ 4149.451682] uvcvideo: Adding mapping White Balance Temperature to
> control 00000000-0000-0000-0000-000000000101/10.
> [ 4149.452923] uvcvideo: Adding mapping White Balance Component, Auto to
> control 00000000-0000-0000-0000-000000000101/13.
> [ 4149.454236] uvcvideo: Adding mapping White Balance Blue Component to
> control 00000000-0000-0000-0000-000000000101/12.
> [ 4149.455529] uvcvideo: Adding mapping White Balance Red Component to
> control 00000000-0000-0000-0000-000000000101/12.
> [ 4149.456818] uvcvideo: Adding mapping Focus (absolute) to control
> 00000000-0000-0000-0000-000000000001/6.
> [ 4149.457984] uvcvideo: Adding mapping Focus, Auto to control
> 00000000-0000-0000-0000-000000000001/8.
> [ 4149.459119] uvcvideo: Probing generic UVC device 3
> [ 4149.459731] uvcvideo: Found format YUV 4:2:2 (YUYV).
> [ 4149.459735] uvcvideo: - 640x480 (20.0 fps)
> [ 4149.459737] uvcvideo: - 160x120 (24.0 fps)
> [ 4149.459739] uvcvideo: - 176x144 (24.0 fps)
> [ 4149.459741] uvcvideo: - 320x240 (24.0 fps)
> [ 4149.459742] uvcvideo: - 352x288 (24.0 fps)
> [ 4149.459744] uvcvideo: - 800x600 (7.0 fps)
> [ 4149.459746] uvcvideo: - 1024x768 (7.0 fps)
> [ 4149.459748] uvcvideo: - 1280x800 (7.0 fps)
> [ 4149.459749] uvcvideo: - 1280x960 (7.0 fps)
> [ 4149.459751] uvcvideo: - 1280x1024 (7.0 fps)
> [ 4149.459755] uvcvideo: Found UVC 1.00 device USB2.0 UVC PC Camera
> (174f:5931)
> [ 4149.466351] uvcvideo: Added control
> 00000000-0000-0000-0000-000000000101/2 to device 3 entity 3
> [ 4149.466357] uvcvideo: Added control
> 00000000-0000-0000-0000-000000000101/3 to device 3 entity 3
> [ 4149.466360] uvcvideo: Added control
> 00000000-0000-0000-0000-000000000101/6 to device 3 entity 3
> [ 4149.466364] uvcvideo: Added control
> 00000000-0000-0000-0000-000000000101/7 to device 3 entity 3
> [ 4149.466367] uvcvideo: Added control
> 00000000-0000-0000-0000-000000000101/8 to device 3 entity 3
> [ 4149.466370] uvcvideo: Added control
> 00000000-0000-0000-0000-000000000101/9 to device 3 entity 3
> [ 4149.466374] uvcvideo: Added control
> 00000000-0000-0000-0000-000000000101/1 to device 3 entity 3
> [ 4149.466381] uvcvideo: Scanning UVC chain: OT 4 <- PU 3 <- IT 1
> [ 4149.466385] uvcvideo: Found a valid video chain (1 -> 4).
> [ 4149.521015] uvcvideo: Failed to query (135) UVC control 1 (unit 0) :
> -32 (exp. 26).

This is a non-fatal message. No worries there. As a side note, I will soon 
remove it as it confuses many users.

> [ 4150.339102] uvcvideo: UVC device initialized.
> [ 4150.339164] usbcore: registered new interface driver uvcvideo
> [ 4150.339171] USB Video Class driver (SVN r257)
> [ 4150.346123] uvcvideo: Trying format 0x56595559 (YUYV): 10000x10000.
> [ 4150.346131] uvcvideo: Using default frame interval 142857.1 us (7.0
> fps).
>
> The driver creates /dev/video0, and a few program list "USB2.0 UVC PC
> Camera" as an installed webcam.

Good so far.

> But the problem is that the camera is not really usable: all programs
> I've tried so far do not capture any image from it.
>
> I had only very limited success with running "luvcview -f yuv" (I use
> version 0.2.1 from ubuntu hardy).
> In this case, luvcview captures and outputs only the first frame and
> hangs completely: only "kill -KILL pid" helps.
> Here is what I get in dmesg:
>
> [ 4164.797148] uvcvideo: Trying format 0x56595559 (YUYV): 320x240.
> [ 4164.797155] uvcvideo: Using default frame interval 41666.6 us (24.0
> fps). [ 4165.657184] uvcvideo: Setting frame interval to 1/15 (666666).
>
> Does this mean the camera is not supported by uvcvideo driver?

It means the camera is detected by the driver, and should work unless it is 
buggy (the driver can also be buggy, but experience showed that there are now 
more issues in the cameras themselves than in the driver :-)).

> Any help will be appreciated.

Could you please set the quirks parameter to 16 when loading the driver ? You 
can run the following two commands as root to unload the driver and reload it 
with quirks set to the right value.

rmmod uvcvideo
modprobe uvcvideo quirks=16

If it helps, please let me know and I'll issue a proper fix.

Best regards,

Laurent Pinchart
_______________________________________________
Linux-uvc-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Reply via email to