Tommaso, dmesg output is not strange, it is a standard output for the trace level you set. Did you modified the exposure settings? I couldn't find any references to that in the posted output.
Best regards, Paulo 2009/7/22 Tommaso Gardumi <[email protected]>: > Here again Paulo, > After the modification of /etc/modprobe.d/uvcvideo.conf > still no success. > the output of dmesg is even more strange now: > > > > > Il giorno mer, 22/07/2009 alle 14.01 +0100, Paulo Assis ha scritto: > > Tommaso, > > I find it strange that you cannot change the exposure setting, please > set the trace parameter to 255, > edit /etc/modprobe.d/uvcvideo.conf and add: > options uvcvideo trace=255 > > now reload the uvcvideo module, and check dmesg after tweaking the > exposure control (set it to manual, disable "Exposure, Auto Priority" > and change the "Exposure (Absolute)" value). > > Best regards, > Paulo > > > 2009/7/22 Tommaso Gardumi <[email protected]> >> >> Hi Paul, >> no good news in the direction you suggested me. >> Just to be more specfic this my graphic card: >> dmesg | grep intel >> [ 10.484033] agpgart-intel 0000:00:00.0: Intel 965GM Chipset >> [ 10.484804] agpgart-intel 0000:00:00.0: detected 7676K stolen memory >> [ 10.487429] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ >> 0xd0000000 >> >> And again, don't know if it's normal but look at this output: >> dmesg | grep video >> [ 1.239259] pci 0000:00:02.0: Boot video device >> [ 10.842081] Linux video capture interface: v2.00 >> [ 10.919121] uvcvideo: Found UVC 1.00 device USB2.0 Camera (0402:5606) >> [ 10.935215] usbcore: registered new interface driver uvcvideo >> [ 109.687343] uvcvideo: UVC non compliance - GET_MIN/MAX(PROBE) >> incorrectly supported. Enabling workaround. >> [ 171.749878] uvcvideo: Failed to query (129) UVC control 3 (unit 1) : >> -32 (exp. 1). >> [ 171.750501] uvcvideo: Failed to query (129) UVC control 3 (unit 1) : >> -32 (exp. 1). >> [ 173.143512] uvcvideo: device USB2.0 Camera requested null bandwidth, >> defaulting to lowest. >> >> Thanks >> >> >> >> >> Il giorno mar, 21/07/2009 alle 17.42 +0100, Paulo Assis ha scritto: >> >> Hi, >> The colors are completly wrong it looks like a color channel is missing or >> maybe switched. >> Are you sure this is not a graphic card issue ? Could you try disabling >> hardware acceleration: >> guvcview --hwd_acel=0 >> This prevents the use of hardware overlays, it decreases performance but >> could if the colors are OK it may signal a problem with you graphic card. >> >> best regards, >> Paulo >> >> 2009/7/21 Tommaso Gardumi <[email protected]> >> >> Sorry the strange values was an attempt to correct the default broken >> visualisation. >> >> I've set everithing back to default but what i get is always the same. >> I've noticed that when i try to switch to Auto exposure i get this >> error: >> VIDIOC_S_CTRL - Unable to set control: Errore di I/O >> Exposure, Auto Priority change to 1 failed >> VIDIOC_G_CTRL - Unable to get control: Errore di I/O >> hardware get failed >> >> And if i set to manual exposure and try to change the value nothing >> happens. >> Even switching between MJPG and YUYV and changing resolution and fps to >> any possible combination leave me with this quality (.jpg attached) >> >> >> Il giorno mar, 21/07/2009 alle 17.05 +0200, Laurent Pinchart ha scritto: >> >> > On Tuesday 21 July 2009 17:02:37 Paulo Assis wrote: >> > > Also make sure to set an appropriate value to exposure and white >> > > balance. >> > > hue also seems to be set at an invalid value!!! >> > > >> > > guvcview output: >> > > Hue, -4:1:4, default 0 >> > >> > As this is consecutive to an Ubuntu upgrade, my guess is that libv4l2 >> > might >> > not set proper default values. >> > >> > Regards, >> > >> > Laurent Pinchart >> > >> >> > _______________________________________________ Linux-uvc-devel mailing list [email protected] https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
