Thanks Martin, I'm an idiot.. added the space to my lucview command as you suggested and it's working fine now, excellent! For the record, I have ekiga 2.0.1 so I must just need an upgrade.
Cheers, Rich. On 10/1/06, Martin Rubli <[EMAIL PROTECTED]> wrote: > Hey Richard, > > > I'm running 2.6.17-1.257_FC5 and have compiled uvcvideo from source. > > It seems to have installed OK as uvccapture can happily grab still > > images. I can't get anything else working though. > > If you can capture images at all, that's already a good sign. It means the > driver works and the problem is (probably) elsewhere. :-) > > > 'xawtv -hwscan' - sees the device OK > > This is xawtv-3.95, running on Linux/i686 (2.6.17-1.2157_FC5) > > looking for available devices > > /dev/video0: OK [ -device /dev/video0 ] > > type : v4l2 > > name : DViCO FusionHDTV DVB-T Plus > > flags: overlay capture tuner > > > > /dev/video1: OK [ -device /dev/video1 ] > > type : v4l2 > > name : DViCO FusionHDTV DVB-T Plus > > flags: overlay capture tuner > > > > /dev/video2: OK [ -device /dev/video2 ] > > type : v4l2 > > name : USB Video Class device > > flags: capture > > Another good sign, although xawtv is known not to work correctly with UVC > webcams. > > > 'luvcview -d/dev/video2' > > uvcview version 0.1.7 > > Video driver: x11 > > A window manager is available > > video /dev/video0 > > Unable to set format: 22. > > Init v4L2 failed !! exit fatal > > Look closely: > > video /dev/video0 > > Yes, luvcview is really picky about parsing the command line arguments. > You must have a space after "-d", then it should work. > > > I have also tried ekiga which also detects the webcam but give me > > 'Failed to open device' messages. > > I am running as root and have granted rwx permissions to all for > > /dev/video2 just to be sure that wasn't the problem. > > Ekiga 2.0.2 is the first version to work correctly with UVC webcams AFAIK. > Which version are you using? > > > Does anyone have any advice on what I should try now? > > A few things come to mind: Don't give up, report bugs where appropriate, > and help us improve webcam support on Linux. :-) > > > 'cat /var/log/messages' > > Oct 1 11:02:19 mythbox syslogd 1.4.1: restart. > > Oct 1 11:19:14 mythbox kernel: usb 1-3: new high speed USB device > > using ehci_hcd and address 4 > > Oct 1 11:19:14 mythbox kernel: usb 1-3: configuration #1 chosen from 1 > > choice > > Oct 1 11:19:14 mythbox kernel: uvcvideo: Found UVC 1.00 device > > <unnamed> (046d:08c1) > > Oct 1 11:19:15 mythbox kernel: 4:3:1: cannot set freq 0 to ep 0x86 > > Oct 1 11:19:16 mythbox kernel: 4:3:2: cannot set freq 0 to ep 0x86 > > Oct 1 11:19:17 mythbox kernel: 4:3:3: cannot get freq at ep 0x86 > > Oct 1 11:19:33 mythbox kernel: uvcvideo: Failed to query (132) UVC > > control 4 (unit 2) : -32. > > Oct 1 11:21:42 mythbox gconfd (mythtv-5036): starting (version > > 2.14.0), pid 5036 user 'mythtv' > > Oct 1 11:21:42 mythbox gconfd (mythtv-5036): Resolved address > > "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only > > configuration source at position 0 > > Oct 1 11:21:42 mythbox gconfd (mythtv-5036): Resolved address > > "xml:readwrite:/home/mythtv/.gconf" to a writable configuration source > > at position 1 > > Oct 1 11:21:42 mythbox gconfd (mythtv-5036): Resolved address > > "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only > > configuration source at position 2 > > Oct 1 11:32:01 mythbox kernel: uvcvideo: Failed to query (135) UVC > > control 2 (unit 2) : -110. > > Oct 1 11:32:01 mythbox kernel: uvcvideo: Failed to query (130) UVC > > control 2 (unit 2) : -75. > > Oct 1 11:32:02 mythbox kernel: uvcvideo: Failed to query (135) UVC > > control 2 (unit 2) : -110. > > Oct 1 11:32:02 mythbox kernel: uvcvideo: Failed to query (130) UVC > > control 2 (unit 2) : -75. > > Oct 1 11:32:02 mythbox kernel: uvcvideo: Failed to query (131) UVC > > control 2 (unit 2) : -32. > > Oct 1 11:32:03 mythbox kernel: uvcvideo: Failed to query (135) UVC > > control 2 (unit 2) : -110. > > Yes, these are bad. If you see those you might need to retry whatever > caused the error or replug the camera. It's caused by a bug in the Fusion > firmware that occurs one some USB controllers. We're currently testing a > quick workaround and are still analyzing the problem so that future > cameras won't have the same problems. > > Cheers, > Martin > _______________________________________________ Linux-uvc-devel mailing list Linux-uvc-devel@lists.berlios.de https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
