Hi, On Saturday 29 November 2008, micu wrote: > Hey Laurent et al., > > thanks a lot for your answer!
You're welcome. > Am Mittwoch, 26. November 2008 00:15:24 schrieb Laurent Pinchart: > > > * http://trac.qutecom.org/ticket/18 > > > > Could you please check the kernel log for messages printed by the > > uvcvideo driver after you get that error message from QuteCom ? > > When I *connect* my camera to my computer, most of the time I get something > like this: > > usb 6-3: new high speed USB device using ehci_hcd and address 5 > > usb 6-3: configuration #1 chosen from 1 choice > > uvcvideo: Found UVC 1.00 device <unnamed> (046d:09a4) > > uvcvideo: UVC non compliance - GET_DEF(PROBE) not supported. Enabling > > workaround. input: UVC Camera (046d:09a4) as > > /devices/pci0000:00/0000:00:1a.7/usb6/6-3/6-3:1.0/input/input13 Nothing to worry about there. > Sometimes I get: > > ALSA /build/buildd/linux-ubuntu-modules-2.6.24-2.6.24/debian/build/build-generic /sound/alsa-driver/usb/usbaudio.c:1296: 10:3:1: cannot get freq at ep > > 0x86 uvcvideo: Failed to set UVC probe control : -110 (exp. 26). That looks like a camera bug. What worries me is that your camera is not documented as potentially suffering from this problem :-/ I'll forward the information. > *Don't* get a kernel log message when Qutecom crashes at all. Then Qutecom is at fault. Even if it receives an unexpected answer from the camera it shouldn't crash. > > That's to be expected, camorama only supports the deprecated V4L1 API. > > Ahh.. good to know, thx! ;) > > > There are/were known issues with mplayer. Try > > > > mplayer tv:// -tv driver=v4l2:fps=25 > > AAAAAhhh.... works pretty well, thanks a lot! (Oh that cleverness of me: > not able to read the mplayer output correctly... :/) Best regards, Laurent Pinchart _______________________________________________ Linux-uvc-devel mailing list Linux-uvc-devel@lists.berlios.de https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
