On Wednesday 22 November 2006 01:22, Alex Pounds wrote: > On Tue, Nov 21, 2006 at 05:23:23PM +0100, Martin Rubli wrote: > > On Sun, 19 Nov 2006 21:33:10 +0100, Alex Pounds <[EMAIL PROTECTED]> > > > > wrote: > > >aMSN gives me "Error getting camera capabilities". > > > > IIRC aMSN is known to not work right with the uvcvideo driver. > > Well, it seems to suggest it supports V4L2, so I thought it would work OK.
aMSN developers probably tested the software using another V4L2 driver which didn't complain. I'm pretty sure the Linux UVC driver is not at fault here, it just doesn't implement some non-mandatory functions which don't make sense for webcams, or is stricter when checking parameters. > > >Kopete gives me a variation on a green screen, a Q, and every so often > > >it'll actually work in the settings box but I've not yet got it to work > > >in an actual IM conversation. > > > > I've never gotten around to test Kopete. What version are you using? > > Kopete 0.12.3. I don't know if it uses Phonon. Kopete doesn't use Phonon yet. It will in KDE4. Kopete's V4L2 support isn't stable yet, and I don't think the developers plan to do anything about it before KDE4. > > >Ekiga says that it couldn't open the device. > > > > Which version of Ekiga? We've had reports about Ekiga 2.0.2 not working > > with the split version. I'll look into that ... > > I'm on 2.0.3. I basically run a Debian Etch machine. I'll give a more > exact error at some point but it's a really hectic week for me and the > driver is playing up. I wasn't getting the camera as a video device, so > I reloaded the module by doing an rmmod uvcvideo followed by > modprobe uvcvideo, and that modprobe has hung. :( No output in dmesg about > it. modprobe hung with no message in dmesg ? That's weird. Try modprobe trace=15 to make the driver more verbose. Cheers, Laurent Pinchart _______________________________________________ Linux-uvc-devel mailing list [email protected] https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
