Logitech Quickcam Fusion doesn't work

Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description didn't include enough information.

Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available here: <http://wiki.ubuntu.com/DebuggingKernelProblems> Thanks!

Change Status of Unconfirmed to Needs Info.

I'm not the original author of this bug, but am also the owner of a Logitech Fusion I'd love to see working

uname -a:

Linux plasken 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux

dmesg attached

webcam output:
andersja@plasken:~$ webcam
reading config file: /home/andersja/.webcamrc
video4linux webcam v1.5 - (c) 1998-2002 Gerd Knorr
grabber config:
  size 1024x576 [16 bit YUV 4:2:2 (packed, YUYV)]
  input (null), norm (null), jpeg quality 75
  rotate=0, top=0, left=0, bottom=240, right=320
ioctl: VIDIOC_REQBUFS(count=1;type=VIDEO_CAPTURE;memory=MMAP): Invalid argument
ioctl: VIDIOC_DQBUF(index=0;type=VIDEO_CAPTURE;bytesused=0;flags=0x0 [];field=ANY;;timecode.type=0;timecode.flags=0;timecode.frames=0;timecode.seconds=0;timecode.minutes=0;timecode.hours=0;timecode.userbits="";sequence=0;memory=unknown): Invalid argument
capturing image failed

updated to include 2.6.20 and confirmed

community support (ubuntuforums) reference:
http://www.ubuntuforums.org/showthread.php?t=194793

with the ubuntuforums reference above, webcam is working fine for ekiga (only?)

Kopete shows a device with 'black' output,
trying to adjust brightness yields:
(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1241381168 (LWP 25884)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6 0xb5a4cf25 in Kopete::AV::VideoInput::setBrightness ()
   from /usr/lib/libkopete_videodevice.so.0
#7 0xb5a4f686 in Kopete::AV::VideoDevice::setBrightness ()
   from /usr/lib/libkopete_videodevice.so.0
#8 0xb5a56674 in Kopete::AV::VideoDevicePoo...

This is not a bug in Ubuntu, but a shortcoming of the linux-uvc driver. Many Linux applications access devices via the "read" method - the other alternative would be the "mmap" method. For example, luvcview can use either (the -g flag switches to the "read" method), Ekiga uses the "mmap" method, and Kopete uses the "read" method.

The linux-uvc driver currently only supports the "mmap" method. Applications that only use the "read" method will not work. Apparently supporting "read" isn't all that difficult, and it's a pretty big shortcoming, so I would expect it to be supported soon by linux-uvc.

To conclude, this isn't an Ubuntu bug, just a result of a missing (and very important) feature in the linux-uvc driver.

No installation technique seems to work on Feisty Fawn 7.04
on a 64-bit
Dell Dimension 9200.

I can tell my camera is the first hardware version of the Logitech QuickCam Fusion because
http://mxhaard.free.fr/spca5xx.html
lists the device code as
0x046d 0x08c1
and that's the code reported by dmesg, included below.

This page doesn't even include the Fusion:
https://wiki.ubuntu.com/HardwareSupportComponentsMultimediaWebCamerasLogitech

digg this:
http://digg.com/linux_unix/Logitech_gives_Linux_users_the_finger

Results of following instuctions at
http://ubuntuforums.org/showthread.php?t=194793
and ideas at
http://ubuntuforums.org/showthread.php?t=205782
http://ubuntuforums.org/showthread.php?t=338373

# uname -r
2.6.20-16-generic

# caminfo
CVideoDeviceInput: Warning: no channel info available.
Detected 1 Video4Linux devices.
Device node : /dev/video0
Name of device : "USB Video Class device"
Minimum size : 48x32
Current size : 0x0
Maximum size : 0x0
Video inputs : 1
 Input 0
  Name : "(null)"
  Type : Unknown
  Audio : no
  Tuners : 0
Audio inputs : 0

Last part of the output of dmesg:

[21194.423644] atkbd.c: Unknown key pressed (translated set 2, code 0x9f on isa0060/serio0).
[21194.423650] atkbd.c: Use 'setkeycodes e01f <keycode>' to make it known.
[21194.442091] atkbd.c: Unknown key pressed (translated set 2, code 0xb9 on isa0060/serio0).
[21194.442094] atkbd.c: Use 'setkeycodes e039 <keycode>' to make it known.
[21194.548689] atkbd.c: Unknown key released (translated set 2, code 0x9f on isa0060/serio0).
[21194.548693] atkbd.c: Use 'setkeycodes e01f <keycode>' to make it known.
[21194.684395] atkbd.c: Unknown key released (translated set 2, code 0xb9 on isa0060/serio0).
[21194.684399] atkbd.c: Use 'setkeycodes e039 <keycode>' to make it known.
[80921.699583] usb 6-4: new high speed USB device using ehci_hcd and address 3
[80922.013411] usb 6-4: configuration #1 chosen from 1 choice
[80923.564509] Linux video capture interface: v2.00
[80924.721648] 3:3:3: cannot set freq 16000 to ep 0x86
[80926.722145] usbcore: registered new interface driver snd-usb-audio
[80926.722367] uvcvideo: Found UVC 1.00 device <unnamed> (046d:08c1)
[80926.740419] uvcvideo: Failed to query (135) UVC control 1 (unit 0) : -32 (exp. 26).
[80926.740424] uvcvideo: Failed to initialize the device (-5).
[80926.740608] usbcore: registered new interface driver uvcvideo
[80926.740686] USB Video Class driver (v0.1.0)
[81557.240278] usb 6-4: USB disconnect, address 3
[81561.804369] usb 6-4: new high speed USB device using ehci_hcd and address 4
[81562.114588] usb 6-4: configuration #1 chosen from 1 choice
[81562.114775] uvcvideo: Found UVC 1.00 device <unnamed> (046d:08c1)
[81563.127742] 4:3:3: cannot set freq 16000 to ep 0x86
[83096.829396] uvcvideo: Failed to query (1) UVC control 2 (unit 0) : -32 (exp. 26).
[83096.842248] uvcvideo: Failed to query (1) UVC control 1 (unit 0) : -32 (exp. 26).
[83096.846364] uvcvideo: Failed to query (1) UVC control 1 (unit 0) : -75 (exp. 26).
[83905.003367] usb 6-4: USB disconnect, address 4
[83967.997179] usb 6-4: new high speed USB device using ehci_hcd and address ...

I mean it FAILS to work,
not that it works.

There is no way to edit my previous post for a simple correction!

http://webcam-osx.sourceforge.net/cameras/index.php

lists both models, progress there might help here
as OS X is Linux based, right?

OSX is partially based on FreeBSD - the userland, I believe - but the kernel is based on Mach. It's unlikely that OSX's USB interface is similar to Linux's to simplify porting the drivers.

In any case, as I said in my other post, the fix is relatively simple. All that is needed is for the "read" method of interfacing to be supported, not just the "mmap" method. That should be all that's necessary. You could probably find out more by talking to the linux-uvc guys, to see what needs to be done and whether or not anyone is working on this already.

However, this is definitely *not* an Ubuntu bug, and does not need to remain open here.

Changing to "invalid" status - this is not an Ubuntu bug, just the result of an unimplemented feature in the linux-uvc driver.

Too bad this bug is being shoved off with status 'not our problem'. While this may be true from a developers point of view, to the ordinary user it's simply: 'My cam don't work with this Ubuntu thing. With Windows it does. Ergo: Windows rules / Ubuntu sucks'. This is not helping in fixing bug #1. And quite frankly, I much sooner expect you and/or the maintainers of the kernel source package to do the talking with the linux-uvc guys since you/they know a LOT more about these things than we ordinary users do. Besides, I have a feeling they'd be a lot more sensitive to hear comment like that coming from people how actually know what they're talking about. Keep those lines short and please don't shove user's problems back to the people who report them. I'm not reopening this bug but I'm politely asking you to reconsider and try to solve this bug in a proactive way.

Thanks.

iGadget, perhaps it wasn't obvious, but I'm just a regular user too - I'm not involved with either Ubuntu or linux-uvc :) The only reason I posted any comments to this bug report is because I ran into the problem with my camera and stumbled on this listing, and thought I'd provide some details.

I'd write the patch for linux-uvc myself, but providing the update to this thread is about all I have free time for right now - and I returned my camera anyway (in exchange for one that doesn't use UVC), so I don't have a way to test it.

Anyway, just in case someone wants to take this to linux-uvc, here's all you need to tell them, in layman's terms.
linux-uvc does not support the "read" call, only the "mmap" call. Many applications, including Kopete, the most popular multi-protocol Linux chat client with webcam support, only use the "read" call - thus supporting "read" within linux-uvc should be a priority.

For the record, however, they are well aware that read support is needed, they just haven't gotten around to doing it yet.

But don't yell at me! ;)

Nate,

My apologies for yelling at you, that surely wasn't how I meant it :)
Knowing now that you're actually not a hotshot bugfixer, I should indeed take matters more lightly. Thanks for contributing to this bugreport anyway, hopefully it will help in fixing this issue anytime soon.

If anyone of the Ubuntu team is listening: perhaps it would be a good idea to put a bounty on this issue? Maybe that would allow the linux-uvc guys to fix this issue before Gutsy is released.

No problem, iGadget :)

This would indeed be a good target for a bounty. It's a relatively simple modification (key word being relatively, of course), and the main developer for the project seems pretty busy. I'm not sure how much work has been done on linux-uvc in the past 6 months (I did check the svc just to make sure read wasn't already implemented, however).

I'd be willing to play with it myself, but like I said, I returned my UVC based camera, and I don't really have a reason to dole out $50-70 for a new one just to write the patch :) 'Course, if someone has an old one they're not using, I'd be glad to take it off their hands for development purposes :)

So anyway, I don't know much about the Ubuntu project, or how bounties get set, but yes, this would probably be a good target for one.