Created attachment 34802 [details] syslogmessages from gspca_main with different debug options Since the Typhoon Webshot 350 has been on compatibility lists like http://ovcam.org/ov511/cameras.html for years now but never worked for me I decided to report a bug. Apparently this webcam should work with gspca_ov519 now. lsusb says: Bus 002 Device 005: ID 05a9:a518 OmniVision Technologies, Inc. D-Link DSB-C310 Webcam However, when connecting the webcam and starting cheese there's no picture: ~ % LC_ALL=C cheese libv4l2: error dequeuing buf: Input/output error I loaded gspca_main with several debug options and started cheese. Because it is much output I attach the syslog messages. I run the radeon testing branch of the kernel (2.6.36-rc8-21901-g21c74a8-dirty) but it happens with the mainline kernel too, though I didn't check if the debug messages are really the same. If you need more information, let me know how to gather it.
Probably, your userspace application is not using libv4l. AFAIK, ov519 has a proprietary format. The decoder for it is at libv4l. Unfortunately, a few Linux distros are not packaging v4l-utils, nor they are using the versions of applications like cheese that work with libv4l. See: https://fedoraproject.org/wiki/Features/BetterWebcamSupportF13 and http://linuxtv.org/wiki/index.php/Libv4l_Progress
I don't think that is the problem. I tried vlc, mplayer and wxcam, but none worked. Vlc is a bit strange with that, but at least mplayer or wxcam should run. Then I tried guvcview. This was a surprise. With guvcview it WORKS. I have Archlinux and v4l-utils 0.8.1 is installed. I tried the qv4l2 utility and it works too. So you're right, it is in v4l. But there's still the problem of the other programs not working with it. Or is it mplayer's and wxcam's fault? With wxcam the syslog gets also spammed with messages like Oct 24 19:57:00 localhost kernel: ov519: Invalid packet nr: 177 (expect: 0) Oct 24 19:57:00 localhost kernel: ov519: Invalid packet nr: 244 (expect: 0) Oct 24 19:57:00 localhost kernel: ov519: Invalid packet nr: 55 (expect: 0) mplayer doesn't do that but it doesn't show a picture either. I use driver=v4l2, because with driver=v4l it just spams ioctl mcapture failed: Invalid argument V: 13.7 343/343 0% 0% 0.0% 0 0 chris@chrispc ~ % mplayer -tv driver=v4l2:device=/dev/video3 tv:// MPlayer SVN-r32492-4.5.1 (C) 2000-2010 MPlayer Team 159 audio & 349 video codecs mplayer: could not connect to socket mplayer: No such file or directory Failed to open LIRC support. You will not be able to use your remote control. Playing tv://. TV file format detected. Selected driver: v4l2 name: Video 4 Linux 2 input author: Martin Olschewski <olschewski@zpr.uni-koeln.de> comment: first try, more to come ;-) v4l2: your device driver does not support VIDIOC_G_STD ioctl, VIDIOC_G_PARM was used instead. Selected device: USB Camera Capabilities: video capture read/write streaming supported norms: inputs: 0 = ov519; Current input: 0 Current format: unknown (0x3831354f) tv.c: norm_from_string(pal): Bogus norm parameter, setting default. v4l2: ioctl enum norm failed: Invalid argument Error: Cannot set norm! Selected input hasn't got a tuner! v4l2: Cannot get fps v4l2: ioctl set mute failed: Invalid argument v4l2: ioctl query control failed: Invalid argument Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory [vdpau] Error when calling vdp_device_create_x11: 1 [VO_XV] Could not grab port 63. ========================================================================== Cannot find codec matching selected -vo and video format 0x3831354F. ========================================================================== v4l2: select timeout v4l2: ioctl set mute failed: Invalid argument v4l2: 1 frames successfully processed, 0 frames dropped. Exiting... (End of file)