Logitech Quickcam Messenger is not usable

The quickcam module does not declare support for this particular device:

alias: usb:v046Dp0840d*dc*dsc*dp*ic*isc*ip*
alias: usb:v046Dp0850d*dc*dsc*dp*ic*isc*ip*
alias: usb:v046Dp0870d*dc*dsc*dp*ic*isc*ip*

This may be because the driver in fact does not support it yet.

(In reply to comment #1)

Thanks for looking into this, Matt. I agree, it's not supported by this same
module. Apparently the link I posted was to another kernel module that is also
called quickcam.ko, but it is not the official kernel one.

BTW, I have gotten this hardware working using the module at
http://home.mag.cx/messenger/. It required a little bit of work:
1. Edit the quickcam.sh script to accept ID 046d:08f0 as a valid device
2. Apply this patch:
--- qc-usb-messenger-0.8/qc-memory.c-old 2005-02-24 19:40:37.000000000 -0500
+++ qc-usb-messenger-0.8/qc-memory.c 2005-02-24 19:41:12.000000000 -0500
@@ -233,7 +233,11 @@
    pos = (unsigned long)src;
    while ((long)size > 0) {
        physaddr = kvirt_to_pa(pos);
- if (remap_page_range(vma, start, physaddr, PAGE_SIZE, PAGE_SHARED))
+ if (remap_pfn_range(vma,
+ start,
+ physaddr >> PAGE_SHIFT,
+ PAGE_SIZE,
+ PAGE_SHARED))
            return -EAGAIN;
        start += PAGE_SIZE;
        pos += PAGE_SIZE;

The resulting quickcam.ko module works fine with this camera.

I suppose this is not Ubuntu's problem though, I guess you'll probably just wait
for it to be supported in the official kernel source.

This bug has been fixed in the latest kernel in our Dapper release. There are no
plans to fix this in breezy.

Based on some positive reports in our community forums, I purchased a Logitech Quickam Messenger webcam. I have now spent nearly two days exploring every solution my feeble mind can think of! I have come to the following conclusions, all this under a fully updated Feisty:

1.spcaxx cource code downloaded from Synaptic will not compile, at least I haven't had any success so far

2 EasyCam2 downloaded from Synaptic will not work, a makefile error message is displayed on startup

3. Ekiga will not recognize the webcam, although it shows up in Feisty's Hardware listing.

4.qc-usb-messenger-1.6 will not compile

5. The error messages thrown by the latter indicate that my computer, an HP Pavillion Media Centre, suffers from a BIOS APIC error 40.

I wonder whether this APIC error is what is causing the compile difficulties with the other source listings? Is it not possible to do a noapic boot?

If only I could fix the APIC error, I believe life would become much more simple! Many thanks, Maurice

This is broken again, in edgy, in fiesty.

and gutsy

Under gutsy using the latest quickcam module from http://home.mag.cx/messenger/source/ and issuing sudo ./quickcam.sh and ignoring any error message, the module works well and video works.

Please add this module to Ubuntu (I guess you'll have to change the name to avoid conflicts with the other quickcam module).

Bus 007 Device 002: ID 046d:08f6 Logitech, Inc.

The quickcam messenger is still broken in Gutsy. Perhaps we could get this working out of the box for hardy?

Linux andrew-desktop 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux

This webcam is still not supported out of the box in Hardy.

I've just compiled the qc-usb-messenger-1.8 source from http://home.mag.cx/messenger/ without any problems. My quickcam messenger is now working with camorama.

The module compiled from this source is called qcmessenger.ko so the name conflict mentioned above is no longer a problem.

I'm a novice when it comes to linux drivers, is it worth packaging this for Hardy or should the V4L guys just be approached about including the driver upstream?

Hi Ben,

Getting this driver upstream would be the best case scenario. Mainly because the Ubuntu kernel is rebased frequently with upstream so if this were upstream the Ubuntu kernels would automatically have this driver. It's a lot of extra work for the kernel team to maintain out of tree drivers so they typically require upstream submission first before considering to maintain out of tree drivers.

I'm curious though what your dmesg output looks like in Hardy after you've plugged the camera in. Also, lsusb output wouldn't hurt either.

Also, just to see if this is still an issue with the upcoming Intrepid Ibex 8.10 release, if you'd be willing to test the latest Alpha for Intrepid (you should be able to test via a LiveCD) that would be great. Information regarding the latest Alpha release can be found here - http://www.ubuntu.com/testing . Please let us know your results.

Finally, against 2.6.20 this will be closed as this does not qualify for a Stable Release Update - http://wiki.ubuntu.com/StableReleaseUpdates . But we will keep this open against the actively developed kernel. Thanks.

Thanks.

Hi Leann,

With the qcmessenger driver unloaded and temporarily blacklisted to stop it loading again, the output from dmesg is:
...
[ 4880.228709] usb 2-1: new full speed USB device using uhci_hcd and address 5
[ 4880.415533] usb 2-1: configuration #1 chosen from 1 choice
...

and output from lsusb:

...
Bus 002 Device 005: ID 046d:08f6 Logitech, Inc.
...

With the qcmessenger driver removed from the blacklist and the camera plugged, dmesg output is:

...
[ 5148.810751] usb 2-1: new full speed USB device using uhci_hcd and address 6
[ 5149.002534] usb 2-1: configuration #1 chosen from 1 choice
[ 5149.147413] qcmessenger [55.385792]: ----------LOADING QUICKCAM MODULE------------
[ 5149.147425] qcmessenger [55.385806]: struct quickcam size: 4752
[ 5149.147497] qcmessenger: QuickCam USB camera found (driver version QuickCam Messenger/Communicate USB 1.8 $Date: 2008/05/26 00:00:00 $)
[ 5149.147505] qcmessenger: Kernel:2.6.24-19-generic bus:2 class:FF subclass:FF vendor:046D product:08F6
[ 5149.147513] qcmessenger [55.385894]: poisoning qc in qc_usb_init
[ 5149.159122] qcmessenger [55.397517]: E00A contains 08F6
[ 5149.159133] qcmessenger: Sensor VV6450 detected
[ 5149.160423] input: Quickcam snapshot button as /devices/virtual/input/input8
[ 5149.178389] qcmessenger [55.416814]: Quickcam snapshot button registered on usb-0000:00:1d.1-1/input0
[ 5149.178868] qcmessenger: Registered device: /dev/video0
[ 5149.179145] usbcore: registered new interface driver qcmessenger
...

I am downloading the Ibex alpha and should find the time to test and report my results here in the next few days.

Ben

This is still an issue in Intrepid.
I have tested with the live cd and a new installation of Intrepid Alpha 3.

dmesg output still looks like this:

[ 313.209555] usb 2-1: new full speed USB device using uhci_hcd and address 3
[ 313.405928] usb 2-1: configuration #1 chosen from 1 choice

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

I've upgraded my test install of Intrepid - looks like this is still an issue.

uname -r:
2.6.27-1-generic

dmesg:
[ 287.720173] quickcam_messenger: Logitech Quickcam Messenger USB v0.01
[ 287.720173] usbcore: registered new interface driver QCM

lsusb:
Bus 002 Device 004: ID 046d:08f6 Logitech, Inc. Quickcam Messenger Plus

I used camorama to test and it failed with "Could not connect to video device (/dev/video0). Please check connection."

Also, I found that the quickcam_messenger module wasn't loaded on plugging, I had to manually modprobe it. Perhaps this is a problem limited to my installation - but it was a clean install of alpha 3 that I've just run apt-get dist-upgrade on.

I'm happy to help, just let me know if there is anything else you require.

Ben

I've upgraded to Intrepid too, but the cam didn't work yet.

2.6.27-4-generic

dmesg
[93811.960303] quickcam: QuickCam USB camera found (driver version QuickCam USB 0.6.6 $Date: 2006/11/04 08:38:14 $)

lsusb
Bus 004 Device 003: ID 046d:08f6 Logitech, Inc. Quickcam Messenger Plus

I tested with a few programs but no one detects it.

lsusb

Bus 002 Device 003: ID 046d:08f6 Logitech, Inc. Quickcam Messenger Plus

dmesg:

5419.799627] usb 2-1: USB disconnect, address 3
[ 5426.492023] usb 2-1: new full speed USB device using ohci_hcd and address 4
[ 5426.711608] usb 2-1: configuration #1 chosen from 1 choice
[ 5426.714405] quickcam: QuickCam USB camera found (driver version QuickCam USB 0.6.6 $Date: 2006/11/04 08:38:14 $)
[ 5426.714422] quickcam: Kernel:2.6.27-7-generic bus:2 class:FF subclass:FF vendor:046D product:08F

xawtv

This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.27-7-generic)
xinerama 0: 1280x1024+0+0
WARNING: No DGA direct video mode for this display.
can't open /dev/video0: No such file or directory
v4l-conf had some trouble, trying to continue anyway
v4l2: open /dev/video0: No such file or directory
v4l2: open /dev/video0: No such file or directory
v4l: open /dev/video0: No such file or directory
no video grabber device available

Hi! I have also the same problem.

lsusb

Bus 003 Device 004: ID 046d:08f6 Logitech, Inc. Quickcam Messenger Plus

dmesg

[ 510.056128] usb 3-1: USB disconnect, address 3
[ 527.904075] usb 3-1: new full speed USB device using uhci_hcd and address 4
[ 528.137235] usb 3-1: configuration #1 chosen from 1 choice
[ 528.140929] quickcam: QuickCam USB camera found (driver version QuickCam USB 0.6.6 $Date: 2006/11/04 08:38:14 $)
[ 528.140950] quickcam: Kernel:2.6.27-7-generic bus:3 class:FF subclass:FF vendor:046D product:08F6

xawtv

This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.27-7-generic)
xinerama 0: 1024x768+0+0
WARNING: No DGA direct video mode for this display.
can't open /dev/video0: No such file or directory
v4l-conf had some trouble, trying to continue anyway
v4l2: open /dev/video0: Nessun file o directory
v4l2: open /dev/video0: Nessun file o directory
v4l: open /dev/video0: Nessun file o directory
no video grabber device available

Thanks,
Cri.

yeah!| same problem here!!!!

I can confirm it's still not working in Intrepid (Ubuntu 8.10).
Linux kernel 2.6.27-7-generic (2.6.27-7.12-generic).

The USB id's are detected, the quickcam kernel module loaded, but no /dev/video* device
Kernel log shows:
[ 16.921947] quickcam: QuickCam USB camera found (driver version QuickCam USB 0.6.6 $Date: 2006/11/04 08:38:14 $)
[ 16.921952] quickcam: Kernel:2.6.27-7-generic bus:4 class:FF subclass:FF vendor:046D product:08F6
[ 16.927008] usbcore: registered new interface driver quickcam

ls -al /dev/video*
ls: cannot access /dev/video*: No such file or directory

I can confirm this on candidate images for Intrepid RC

Oct 22 23:16:00 ubuntu kernel: [ 3278.301482] quickcam: QuickCam USB camera found (driver version QuickCam USB 0.6.6 $Date: 2006/11/04 08:38:14 $)
Oct 22 23:16:00 ubuntu kernel: [ 3278.301503] quickcam: Kernel:2.6.27-7-generic bus:4 class:FF subclass:FF vendor:046D product:08F6
Oct 22 23:16:00 ubuntu kernel: [ 3278.310143] usbcore: registered new interface driver quickcam
Oct 22 23:16:00 ubuntu kernel: [ 3278.361539] usbcore: registered new interface driver snd-usb-audio

ubuntu@ubuntu:~$ ls -al /dev/video*
ls: cannot access /dev/video*: No such file or directory
ubuntu@ubuntu:~$

2.6.27-13 hasn't fixed it either.

It does work with 2.6.26.7 and the qc-usb-messenger driver 1.8 (qcmessenger.ko).
However, that drivers can't be used in 2.6.27, plus the 2.6.27 kernel claims to support the webcam.

I've fetched and compiled:

http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-intrepid.git;a=tree;f=ubuntu/qc-usb;h=af08ea6e38e756093ada807ed79ca409afd7c174;hb=111d4d24b402fb77a7b63f816e9a729d0a11fb58

Added some of my own debug statements (USER_OPT=-DDEBUG barfed up compile errors)

 quickcam: QuickCam USB camera found (driver version QuickCam USB 0.6.6 $Date: 2006/11/04 08:38:14 $)
 quickcam: Kernel:2.6.27-7-generic bus:4 class:FF subclass:FF vendor:046D product:08F6
 quickcam: qc_stv_set(qc=ffff88005e5d4000,reg=0x1440,val=0)
 quickcam: qc_stv_set(): TEST_BUGR(dev==NULL)
 quickcam: qc_stv_set(): TEST_OK
 quickcam: ret=1=usb_control_msg(qc->dev, usb_sndctrlpipe=0000000080000300, 0x04, 0x40, reg=5184, 0, qc->dmabuf=ffff88005e5d66d8, 1, 3*250)
 quickcam: SIZE(sensors)=4
 quickcam: Testing sensor #0
 quickcam: qc_get_i2c(qc=ffff88005e5d4000,sensor=ffffffffa056bdc0,reg=0x0000)
 quickcam: qc_get_i2c(): TEST_BUGR(dev==NULL)
 quickcam: qc_get_i2c(): TEST_BUGR OK
 quickcam: qc_stv_set(qc=ffff88005e5d4000,reg=0x0423,val=1)
 quickcam: qc_stv_set(): TEST_BUGR(dev==NULL)
 quickcam: qc_stv_set(): TEST_OK
 quickcam: ret=-32=usb_control_msg(qc->dev, usb_sndctrlpipe=0000000080000300, 0x04, 0x40, reg=1059, 0, qc->dmabuf=ffff88005e5d66d8, 1, 3*250)
 quickcam: Failed qc_stv_set()=-32
 quickcam: qc_get_i2c(): qc_stv_set(qc, STV_REG23, 1) failed
 quickcam: qc_get_i2c failed, code=-32
 quickcam: qc_get_i2c() failed in SIZE(sensors) loop at 0
 usbcore: registered new interface driver quickcam

It seems to fail in usb_control_msg() for request 0x04, type 0x40, value 1059, index 0.
I'm kinda stranded there cause I haven't got the foggiest idea what that means and how to check if the webcam possibly doesn't understand that request nor what request should be sent instead.

I hope this extra info helps someone in tracking down the problem.

Expanding on a driver working for 2.6.26.7:

Instead of using the 0.6.6 driver that Ubuntu uses, i've used the driver that did work with previous kernels:
http://home.mag.cx/messenger/source/qc-usb-messenger-1.8.tar.gz

Get rid of the various sem_getcount() calls, patches can be found from various sources, like:
http://bugs.gentoo.org/attachment.cgi?id=167504

make all
insmod ./qcmessenger.ko

and voila:

[ 2359.948163] qcmessenger: QuickCam USB camera found (driver version QuickCam Messenger/Communicate USB 1.8 $Date: 2008/05/26 00:00:00 $)
[ 2359.948172] qcmessenger: Kernel:2.6.26.7 bus:4 class:FF subclass:FF vendor:046D product:08F6
[ 2359.948183] qcmessenger [ 3.272230]: poisoning qc in qc_usb_init
[ 2359.952998] qcmessenger [ 3.276804]: E00A contains 08F6
[ 2359.952998] qcmessenger: Sensor VV6450 detected
[ 2359.954060] input: Quickcam snapshot button as /devices/virtual/input/input7
[ 2359.958612] qcmessenger [ 3.282952]: Quickcam snapshot button registered on usb-0000:00:1d.0-2/input0
[ 2359.958666] qcmessenger: Registered device: /dev/video1
[ 2359.958738] usbcore: registered new interface driver qcmessenger

No support for v4l2, but v4l in Ekiga works.

Good news and bad news.
I've managed to get my quickcam messenger (0x08f6) working, but with the qc-usb-messenger-1.8 driver (qcmessenger.ko), not the 0.6.6 one on which Ubuntu's quickcam.ko is based.
I've spent an hour or so comparing the sources to see if I can fix the 0.6.6
driver, but it ain't as simple as applying the same fixes or some simple
fixes to qc_stv_set() or somesuch.
See above (https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/22070/comments/21) for more details
I haven't got the hardware specs, which leaves me out of my depth to see the relevant differences
between both drivers.

 Ubuntu (based on qc-usb-0.6.6, sensors: hdcs1000, hdcs1020, pb0100, vv6410):
0x046D:0x0840 QuickCam Express
0x046D:0x0850 LEGO cam / QuickCam Web
0x046D:0x0870 Dexxa WebCam USB
0x046D:0x08F6 Logitech QuickCam Messenger
 but in fact, the Messenger won't work with this driver.

 qc-usb-messenger-1.8 (vv6450 sensor) :
0x046D:0x08F0 QuickCam Messenger
0x046D:0x08F5 QuickCam Communicate
0x046D:0x08F6 QuickCam Messenger (new)
0x046D:0x08DA QuickCam Messenger (new)
Will work, get the sources here: http://home.mag.cx/messenger/
Then apply the patch i've attached here:

patch -p1 < qc-usb-messenger-1.8_2.6.27-v4l.patch
make all
insmod ./qcmessenger.ko

You will get a V4L device (not a V4L2) and it works in xawtv and Ekiga.

The other bad news is that the current Skype version (2.0.0.72) will crash when you will try to use the webcam.
Other people experienced the same, looks like there's no fix for that (yet).

Quickcam Ultra Vision doesn't work.
Kernel: 2.6.27-7

Oct 26 13:15:26 kelvan-desktop kernel: [ 1351.070686] pwc: Philips webcam module version 10.0.13 loaded.
Oct 26 13:15:26 kelvan-desktop kernel: [ 1351.070702] pwc: Supports Philips PCA645/646, PCVC675/680/690, PCVC720[40]/730/740/750 & PCVC830
/840.
Oct 26 13:15:26 kelvan-desktop kernel: [ 1351.070709] pwc: Also supports the Askey VC010, various Logitech Quickcams, Samsung MPC-C10 and
MPC-C30,
Oct 26 13:15:26 kelvan-desktop kernel: [ 1351.070715] pwc: the Creative WebCam 5 & Pro Ex, SOTEC Afina Eye and Visionite VCS-UC300 and VCS
-UM100.
Oct 26 13:15:26 kelvan-desktop kernel: [ 1351.079857] usbcore: registered new interface driver Philips webcam
Oct 26 13:15:26 kelvan-desktop kernel: [ 1351.236195] uvcvideo: Failed to query (1) UVC control 1 (unit 0) : -110 (exp. 26).

Oct 26 13:15:27 kelvan-desktop kernel: [ 1352.237191] uvcvideo: Failed to query (1) UVC control 1 (unit 0) : -110 (exp. 26).
Oct 26 13:15:28 kelvan-desktop kernel: [ 1353.236195] uvcvideo: Failed to query (1) UVC control 1 (unit 0) : -110 (exp. 26).
Oct 26 13:15:29 kelvan-desktop kernel: [ 1354.236323] uvcvideo: Failed to query (1) UVC control 1 (unit 0) : -110 (exp. 26).
Oct 26 13:15:30 kelvan-desktop kernel: [ 1355.237323] uvcvideo: Failed to query (1) UVC control 1 (unit 0) : -110 (exp. 26).
Oct 26 13:15:31 kelvan-desktop kernel: [ 1355.976578] uvcvideo: Failed to query (135) UVC control 2 (unit 2) : -110 (exp. 2).
Oct 26 13:15:31 kelvan-desktop kernel: [ 1356.264203] uvcvideo: Failed to query (1) UVC control 1 (unit 0) : -110 (exp. 26).
Oct 26 13:15:32 kelvan-desktop kernel: [ 1357.264181] uvcvideo: Failed to query (1) UVC control 1 (unit 0) : -110 (exp. 26).
Oct 26 13:15:33 kelvan-desktop kernel: [ 1358.260186] uvcvideo: Failed to query (1) UVC control 1 (unit 0) : -110 (exp. 26).
Oct 26 13:15:34 kelvan-desktop kernel: [ 1359.261321] uvcvideo: Failed to query (1) UVC control 1 (unit 0) : -110 (exp. 26).

/dev/video0 is there, but not usable

@LOONATIC

i followed you instruction but when i type "make all" in gives:

/home/enrico/Desktop/qc-usb-messenger-1.8/qc-driver.c: In function ‘qc_v4l_ioctl’:
/home/enrico/Desktop/qc-usb-messenger-1.8/qc-driver.c:2916: warning: passing argument 1 of ‘printk’ makes pointer from integer without a cast
make[2]: *** [/home/enrico/Desktop/qc-usb-messenger-1.8/qc-driver.o] Error 2
make[1]: *** [_module_/home/enrico/Desktop/qc-usb-messenger-1.8] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-2.6.27-7-generic'
make: *** [qcmessenger.ko] Error 2

Derek:

I get something similar, it might have something to do with the message that the shell scripts "quickcam.sh" gives:
[!] Kernel compiler and gcc seem to be different versions.

The only version that gets mentioned by the script is 4.3.2, though...

I have no idea how to fix that, but I thought the info might help others...

I have done a fresh install of the intrepid beta, with all updates...

Anyone know why this isn't supported in the UVC video driver which is including upstream in the linux kernel?

Perhaps it would be better to ask on the UVC video mailing list why this isn't the case and try to get it included there. Doing so would be much better for all distributions of Linux.

UVC video website: http://linux-uvc.berlios.de/

@loonatic: could not get my webcam (046d:08da) to work with your patch - but the quickcam-1.8 sources worked ok with the Hardy kernel.

However, after a while I found out that the Intrepid kernel actually supports the 046d:08da webcam, but the apps I was using for testing need fixing as stated in https://bugs.launchpad.net/ubuntu/+source/libv4l/+bug/260918

with the LD_PRELOAD trick from bug #260918, my quickcam messenger works perfectly.

I got the same as Derek I think. (mine is 046d:08f6 Logitech, Inc. Quickcam Messenger Plus)
@PRDR, I have this message too, but I think it doesn't matter, just press enter (but you'll probably get our error...)

here is what I got:

gawell@gawell-desktop:~$ wget http://home.mag.cx/messenger/source/qc-usb-messenger-1.8.tar.gz
--2008-11-04 17:50:46-- http://home.mag.cx/messenger/source/qc-usb-messenger-1.8.tar.gz
Résolution de proxyweb.utc.fr... 195.83.155.55
Connexion vers proxyweb.utc.fr|195.83.155.55|:3128... connecté.
requête Proxy transmise, en attente de la réponse... 200 OK
Longueur: 168690 (165K) [application/x-gzip]
Saving to: `qc-usb-messenger-1.8.tar.gz.1'

100%[==============================================================================================================>] 168 690 --.-K/s in 0,03s

2008-11-04 17:50:47 (6,02 MB/s) - « qc-usb-messenger-1.8.tar.gz.1 » sauvegardé [168690/168690]

gawell@gawell-desktop:~$ tar xzf ./qc-usb-messenger-1.8.tar.gz
gawell@gawell-desktop:~$ cd ./qc-usb-messenger-1.8
gawell@gawell-desktop:~/qc-usb-messenger-1.8$ sudo patch -p1 < qc-usb-messenger-1.8_2.6.27-v4l.patch
patching file qc-driver.c
patching file qc-memory.c
gawell@gawell-desktop:~/qc-usb-messenger-1.8$ make all
make -C "/lib/modules/2.6.27-7-generic/build" SUBDIRS="/home/gawell/qc-usb-messenger-1.8" modules V=1 USER_OPT="-DHAVE_UTSRELEASE_H=1"
make[1]: entrant dans le répertoire « /usr/src/linux-headers-2.6.27-7-generic »
test -e include/linux/autoconf.h -a -e include/config/auto.conf || ( \
 echo; \
 echo " ERROR: Kernel configuration is invalid."; \
 echo " include/linux/autoconf.h or include/config/auto.conf are missing."; \
 echo " Run 'make oldconfig && make prepare' on kernel src to fix it."; \
 echo; \
 /bin/false)
mkdir -p /home/gawell/qc-usb-messenger-1.8/.tmp_versions ; rm -f /home/gawell/qc-usb-messenger-1.8/.tmp_versions/*
make -f scripts/Makefile.build obj=/home/gawell/qc-usb-messenger-1.8
  gcc -Wp,-MD,/home/gawell/qc-usb-messenger-1.8/.qc-driver.o.d -nostdinc -isystem /usr/lib/gcc/i486-linux-gnu/4.3.2/include -D__KERNEL__ -Iinclude -I/usr/src/linux-headers-2.6.27-7-generic/arch/x86/include -include include/linux/autoconf.h -Iubuntu/include -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -O2 -m32 -msoft-float -mregparm=3 -freg-struct-return -mpreferred-stack-boundary=2 -march=i586 -mtune=generic -ffreestanding -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -Iinclude/asm-x86/mach-default -fno-stack-protector -fno-omit-frame-pointer -fno-optimize-sibling-calls -pg -Wdeclaration-after-statement -Wno-pointer-sign -DNOKERNEL -DHAVE_UTSRELEASE_H=1 -DMODULE -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(qc_driver)" -D"KBUILD_MODNAME=KBUILD_STR(qcmessenger)" -c -o /home/gawell/qc-usb-messenger-1.8/.tmp_qc-driver.o /home/gawell/qc-usb-messenger-1.8/qc-driver.c
/home/gawell/qc-usb-messenger-1.8/qc-driver.c: In function ‘qc_v4l_ioctl’:
/home/gawell/qc-usb-messenger-1.8/qc-driver.c:2912: attention : passing argument 1 of ‘printk’ makes pointer from integer withou...

@Gawell: I know, I get the errors. I was wondering (out of utter ignorance, of course) if those errors could be due to some kind of incompatibility between versions of gcc (whatever that might mean).

Could you try this patch against the Kernel and see if it makes your camera work? qc-usb-messenger-1.8 shouldn't be necessary as the in Kernel driver seems to work.

I'd be glad to try the patch and report back, but I would need instructions (hopefully fool-proof instructions...)

First I've to say sorry for my bad English. I hope everybody can understand ;-)

I have try to patch philips patch against the kernel.

What I've done:
apt-get install linux-source
cd /usr/src
sudo -s
tarf xvfj linux-source-2.6.27.tar.bz2
cd linux-source-2.6.27
patch -p1 < add-support-for-all-quickcam-messengers-of-the-same-family.patch
cp /boot/config-2.6.27-7-generic ./.config
make menuconfig //Load configfile .config and save
make-kpkg clean
fakeroot make-kpkg --initrd --append-to-version=-quickcam kernel_image kernel_headers

Compiling works fine after I disabled virtualization (https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/287172), but when I try to install the kernel, dpkg return this error Massage:

--------------------------------
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-2.6.27.2-linux-image-2.6.27-quickcam.postinst line 1181.
dpkg: Fehler beim Bearbeiten von linux-image-2.6.27.2-linux-image-2.6.27-quickcam (--configure):
 Unterprozess post-installation script gab den Fehlerwert 2 zurück
Fehler traten auf beim Bearbeiten von:
 linux-image-2.6.27.2-linux-image-2.6.27-quickcam
E: Sub-process /usr/bin/dpkg returned an error code (1)
------------------------------------
I ignored the massage and installed linux-headers. After reboot /dev/video0 exist and the webcam workes fine with camorama.

Ekiga still wont work:
------------------------------------
libv4l2: error getting capabilities: Invalid argument.
------------------------------------

Edit:
Works with Ekiga to, when I use V4L...

Hi,

I followed the same steps, got a /dev/video0, but both camorama and cheese eventually become stuck without ever showing a frame.

Nov 22 14:28:10 newton kernel: [ 551.074454] usb 7-2.6: USB disconnect, address 9
Nov 22 14:28:10 newton kernel: [ 551.100205] usbvideo: USB camera disconnected.
Nov 22 14:28:12 newton kernel: [ 553.064158] usb 7-2.6: new full speed USB device using ehci_hcd and address 10
Nov 22 14:28:12 newton kernel: [ 553.158024] usb 7-2.6: configuration #1 chosen from 1 choice
Nov 22 14:28:12 newton kernel: [ 553.166601] videodev: "QCM USB Camera" has no release callback. Please fix your driver for proper sysfs support, see http://lwn.net/Articles/36850/
Nov 22 14:28:12 newton kernel: [ 553.166607] usbvideo: QCM on /dev/video0: canvas=320x240 videosize=320x240
Nov 22 14:28:12 newton kernel: [ 553.166647] input: QCM button as /devices/pci0000:00/0000:00:1d.7/usb7/7-2/7-2.6/input/input11
Nov 22 14:28:13 newton pulseaudio[7548]: alsa-util.c: Device hw:1 doesn't support 44100 Hz, changed to 22050 Hz.
Nov 22 14:28:13 newton pulseaudio[7548]: alsa-util.c: Device hw:1 doesn't support 2 channels, changed to 1.

from "strace camorama":

open("/dev/video0", O_RDWR) = 15
ioctl(15, EXT2_IOC_GETVERSION or VIDIOCGCAP, 0x7fff47670820) = 0
ioctl(15, SONYPI_IOCSBLUE or VIDIOCGWIN, 0x7fff47670870) = 0
ioctl(15, VIDIOCSWIN, 0x7fff47670870) = 0
ioctl(15, SONYPI_IOCSBLUE or VIDIOCGWIN, 0x7fff47670870) = 0
ioctl(15, VIDIOCGPICT, 0x7fff4767085c) = 0
mmap(NULL, 233472, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f1e3f472000
ioctl(15, VIDIOCGMBUF, 0x7fff47670898) = 0
mmap(NULL, 460800, PROT_READ|PROT_WRITE, MAP_SHARED, 15, 0) = 0x7f1e33f71000
ioctl(15, VIDIOCMCAPTURE, 0x7fff47670920) = 0

[...]

ioctl(15, SONYPI_IOCGBATFLAGS or VIDIOCSPICT, 0x7fff4767085c) = 0
ioctl(15, SONYPI_IOCGBATFLAGS or VIDIOCSPICT, 0x7fff4767085c) = 0
ioctl(15, SONYPI_IOCGBATFLAGS or VIDIOCSPICT, 0x7fff4767085c) = 0
ioctl(15, SONYPI_IOCGBATFLAGS or VIDIOCSPICT, 0x7fff4767085c) = 0
ioctl(15, SONYPI_IOCGBATFLAGS or VIDIOCSPICT, 0x7fff4767085c) = 0

[...]

ioctl(15, VIDIOCSYNC <unfinished ...>

PS: Whats the proper way to just build the patched quickcam module without having to install a complete kernel?

Hi:

I followed the steps posted in https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/287172, in order to build just the patched quickcam module (with the patch posted by philips):

1$ apt-get source linux-image-$(uname -r)
2$ cd linux-2.6.27
3$ cp /boot/config-$(uname -r) .config
4$ patch -p1 < ../add-support-for-all-quickcam-messengers-of-the-same-family.patch
5$ make ubuntu/qc-usb/quickcam.ko

The compilation process seems to have gone fine, only a few warnings:

5$ make ubuntu/qc-usb/quickcam.ko
  HOSTCC scripts/basic/fixdep
  HOSTCC scripts/basic/docproc
  HOSTCC scripts/kconfig/conf.o
scripts/kconfig/conf.c: In function ‘conf_askvalue’:
scripts/kconfig/conf.c:104: warning: ignoring return value of ‘fgets’, declared with attribute warn_unused_result
scripts/kconfig/conf.c: In function ‘conf_choice’:
scripts/kconfig/conf.c:306: warning: ignoring return value of ‘fgets’, declared with attribute warn_unused_result
  HOSTCC scripts/kconfig/kxgettext.o
  SHIPPED scripts/kconfig/zconf.tab.c
  SHIPPED scripts/kconfig/lex.zconf.c
  SHIPPED scripts/kconfig/zconf.hash.c
  HOSTCC scripts/kconfig/zconf.tab.o
In file included from scripts/kconfig/zconf.tab.c:2486:
scripts/kconfig/confdata.c: In function ‘conf_write’:
scripts/kconfig/confdata.c:501: warning: ignoring return value of ‘fwrite’, declared with attribute warn_unused_result
scripts/kconfig/confdata.c: In function ‘conf_write_autoconf’:
scripts/kconfig/confdata.c:739: warning: ignoring return value of ‘fwrite’, declared with attribute warn_unused_result
scripts/kconfig/confdata.c:740: warning: ignoring return value of ‘fwrite’, declared with attribute warn_unused_result
In file included from scripts/kconfig/zconf.tab.c:2487:
scripts/kconfig/expr.c: In function ‘expr_print_file_helper’:
scripts/kconfig/expr.c:1090: warning: ignoring return value of ‘fwrite’, declared with attribute warn_unused_result
  HOSTLD scripts/kconfig/conf
scripts/kconfig/conf -s arch/x86/Kconfig
  CHK include/linux/version.h
  UPD include/linux/version.h
  CHK include/linux/utsrelease.h
  UPD include/linux/utsrelease.h
  SYMLINK i...

Well, I definitely must be doing something wrong... I just took a look a the patch, and it actually patches files that do not have anything to do with what I compiled. In fact, there is another module called "quickcam_messenger", but it is not loaded when the camera is plugged in. Even if I load it manually before, when I plug in the camera, the "quickcam" module is loaded.

 I do not know how to prevent this loading of the quickcam module, and I do not know if the quickcam_messenger alone would work...

Compiling (after patching):
1$ make drivers/media/video/usbvideo/quickcam_messenger.ko

 CHK include/linux/version.h
  CHK include/linux/utsrelease.h
  CALL scripts/checksyscalls.sh
  CC [M] drivers/media/video/usbvideo/quickcam_messenger.o
  MODPOST 2 modules
  CC drivers/media/video/usbvideo/quickcam_messenger.mod.o
  LD [M] drivers/media/video/usbvideo/quickcam_messenger.ko

and installing:
2$ cp drivers/media/video/usbvideo/quickcam_messenger.ko /lib/modules/2.6.27-7-generic/kernel/drivers/media/video/usbvideo/quickcam_messenger.ko

doesn't seem to make a difference.

@PRDR Can you try just booting fresh and running `insmod drivers/media/video/usbvideo/quickcam_messenger.ko` then plugging the camera in? Maybe you have an old driver in place.

Compiling the qc-usb-messenger-1.8 to Ubuntu 8.10 get the following error:

/qc-driver.c:1619: error: request for member ‘counter’ in something not a structure or union
(and in tens of other lines). It's the macro sem_getcount(&qc->lock):

#define sem_getcount(sem) atomic_read(&(sem)->count)

Probably the structure has changed in the new kernel...

Other error: qc-driver.c:2898: error: ‘struct video_device’ has no member named ‘type’

All of that I could "comment out" as most of that was debug messages or "not-so-important" parts of the structure, but the following error I couldn't get around:

qc-memory.c:207: error: implicit declaration of function ‘mem_map_reserve’
qc-memory.c:225: error: implicit declaration of function ‘mem_map_unreserve’

My system is an up-to-date Ubuntu 8.10:
$ uname -a
Linux jobim 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686 GNU/Linux

I had the same issue, but I posted in a duplicate bug (#209901)
exactt closed that ticket by <a href="https://bugs.launchpad.net/ubuntu/+source/linux/+bug/209901/comments/26">suggesting this link</a>. I applied that patch, compiled and copied the related modules.
I now have a video device created by udev. This is good. However I can only get a black picture from the camera using xawtv or camorama.

I also get a ioctl error which I believe is related: ioctl: VIDIOC_QUERYCAP(driver="";card="";bus_info="";version=0.0.0;capabilities=0x0 []): Unknown error 515

Thanks for pointing me to the right direction exactt :)

I've heard that part mentioned in the past, about USB bandwidth being used up, but I just think its curious that its basically happening only on this board (for me)!

Thanks for your help, though, and whatever you guys come up with, I'm sure it'll be a great help and I know it took a lot to get here. Thanks.

Yes, it will only happen to the ST6422, as most 'boards' have a secondary "Low-Bandwidth Mode" to switch to when -ENOSPC is received from the USB subsystem. However, the ST6422 lacks this functionality. As I say, the real issue is in the USB subsystem. This has been addressed in the latest kernels i.e. Maverick.

Leave it with me and I'll see what I can do.

Did you try the new kernel with only the cam plugged in?

What was the output?

I have some more news from one of the ST6422 kernel devs.

Apparently, it's a fluke that this works in Maverick.

I am in the process of writing a patch to write the wrongs.

Watch this space.

Sorry Lee, but I think that the output you're referring to is what I had posted in comment #78. That was with only the cam plugged in (except keyboard and mouse, unless you wanted me to unplug one or both of those as well).

Re: the patch -- great news!

Ah, so #78 was with only the cam plugged in?

No problem.

Okay, I have applied the patch to Lucid.

Can you try it for me, then post your logs here please?

http://people.canonical.com/~ljones/lp22070-lucid/

Lee, sorry for the long response. I've got word back about the camera situation. The new kernel patches appear to have worked! Although the camera does not work as a microphone (but I think this may have been intentional on your part? If I'm not mistaken, your custom kernel has no usb sound drivers).

In any case, attached is the dmesg output, including that while the camera was used (about 3 times).

The USB sound drivers are contained in the *.deb file:
  ./lib/modules/2.6.32-26-generic/kernel/sound/usb/snd-usb-audio.ko

Can you plug your camera in and send me your resulting /var/log/udev file please?

I am in the process of compiling you some more kernels, I'll let you know when they are ready for testing (should be 30-60mins).

OK I've installed the new kernel you posted and got the udev log you wanted.

Also, I figured out what was wrong with the usb audio: I had blacklisted it on that machine before on advice I had seen somewhere else regarding webcam issues! It should be fine now.

I also have the dmesg output and will post that too if you need it.

So, did everything work with the new kernel? Video and audio?

Can you send me the log please?

Sorry again for the delay. I don't actually have much physical access to this machine and do most things remotely and by instructing someone else.

OK, so here's the dmesg output, taken while the camera was being used with Skype.

Video is chopped in half horizontally: top half has video, bottom half is black. Quickcam does not show up as a capture device, so there is no way for Skype or something to capture audio.

Checking lsmod shows that snd_usb_audio is indeed loaded, but it still doesn't work.

At least we are moving forward. Half is better than none.

I think I'll make the patch less aggressive, this may give you your other half of the picture back.

Have a quick go at testing it for video, then we'll work on the sound.

Once tested, if you can post your entire /var/log/kern.log it would be much appreciated.

Kernels:
  http://people.canonical.com/~ljones/lp22070-Quickcam-patch-lucid/

OK so I had to trim /var/kern/log a bit...because it ballooned up to 400+ MB. Hope that its ok that I cut it down to about 4.3MB. It was pretty much repeating itself after that point.

Also there was absolutely no video this time (and no audio, but I know you said we'd work on that later).

You did the right thing by trimming the log. :)

I don't know why video didn't work at all this time. All I did was to revert the changes back to when you saw a full picture. I'll make you a couple more kernels and stick them up at the following URL:
  http://people.canonical.com/~ljones/lp22070-Quickcam-patch-lucid/

You will notice that they have 100, 200 and 300 near the end of the file name.

If you can try all 3 for your architecture and report back the results, I'd be much obliged.

Sure hope the clue as to why video didn't work wasn't at around megabyte 399 or something! (Also, typo in my previous comment: of course I meant /var/log/kern.log)

OK, I will post my results as soon as I get them for all three kernels. This may take a while so maybe by/before the weekend.

Thanks!

No rush.

I have also ordered a camera with a STV06xx in it.

If you still have the issue by the time it arrives, as least I can debug it locally. :)

Well, as promised, here are the /var/log/kern.log's for each of those kernels. Also, as for the video and audio in each one, the results are as follows:

100: Full video, no problems. Audio did not work (device never recognized by Pulseaudio).
200: Half video screen. Audio did not work (device never recognized by Pulseaudio).
300: Only a small sliver of video across the top made it through. Audio did not work (device never recognized by Pulseaudio).

So the audio never worked, but at least in the 100, video seems to have worked perfectly.

I will attach each file successively.

I've been working with another developer who has a great deal of experience in this area. He has recently submitted a patch-set upstream. We are currently waiting for a verdict.

If you wish to follow the thread you can find the relevant start point here:
https://patchwork.kernel.org/patch/285642/

This should now be fixed.

Hello,

sorry if I missed it, but I did not find the patch mentioned for maverick, and the way to implement it. Thanks for any help!
(quicktime messenger plus webcam on maverick with 2.6.36-27)

Here is the upstream patch:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=c0b33bdc5b8d9c1120dece660480d4dd86b817ee

Thank you Lee Jones,

I should have mentioned earlier that I am not a programmer, just a basic user trying to get this camera working. That is to say, I am not aware of relations between git community files and ubuntu repositories automatic kernel updates and I probably got something wrong.
Here is what I did with the 13 files you gave me the adress of:
replace files from the http://moinejf.free.fr/gspca-2.12.18.tar.gz with them
make
sudo make install

It does not work either (I still don't have any "video*" in /dev/)

Thanks for any further help! :)

No, that won't work.

Can you send me your dmsg output?

here:
[17606.745052] usb 2-2: USB disconnect, address 5
[17611.913097] usb 2-2: new full speed USB device using ohci_hcd and address 6
[17612.295869] gspca_stv06xx: disagrees about version of symbol gspca_frame_add
[17612.295876] gspca_stv06xx: Unknown symbol gspca_frame_add (err -22)
[17612.296581] gspca_stv06xx: disagrees about version of symbol gspca_dev_probe
[17612.296584] gspca_stv06xx: Unknown symbol gspca_dev_probe (err -22)

Well I'm not entirely sure how old your out-of-tree version of GSPCA is, but I would have thought it's pretty old. All recent GSPCA development has been completed in the kernel tree and is available in the latest kernels. By issuing "make install" you deleted the most recent kernel modules (contained in /lib/modules/<blar>/gspca-<blar>.ko) and replaced them with modules I can't verify the age of. You need to upgrade to the latest Maverick kernel (and/or replace the old GSPCA modules with the current ones) and paste your dmesg again.

Hi,

it does not seem like I have an old module,

In ...
/lib/modules/2.6.35-27-generic/kernel/drivers/media/video/gspca/stv06xx

I found :
-rw-r--r-- 1 root root 35308 2011-02-23 01:51 gspca_stv06xx.ko

Thanks

nevermind previous comment...
will do what suggested
Thks

Hi,

It is still not working with latest modules on 2.6.35.27 kernel on this computer (mobo Asus m2n-x) BUT it is recognized:

987.501408] usb 1-9.2: new full speed USB device using ehci_hcd and address 6
[ 988.337249] Linux video capture interface: v2.00
[ 988.382897] gspca: v2.12.0 registered
[ 988.514240] gspca_stv06xx: disagrees about version of symbol gspca_frame_add
[ 988.514248] gspca_stv06xx: Unknown symbol gspca_frame_add (err -22)
[ 988.514448] gspca_stv06xx: disagrees about version of symbol gspca_frame_add
[ 988.514456] gspca_stv06xx: Unknown symbol gspca_frame_add (err -22)
[ 988.515555] gspca_stv06xx: disagrees about version of symbol gspca_dev_probe
[ 988.515559] gspca_stv06xx: Unknown symbol gspca_dev_probe (err -22)
[ 988.515831] gspca_stv06xx: disagrees about version of symbol gspca_dev_probe
[ 988.515835] gspca_stv06xx: Unknown symbol gspca_dev_probe (err -22)
[ 988.516738] gspca_stv06xx: disagrees about version of symbol gspca_frame_add
[ 988.516742] gspca_stv06xx: Unknown symbol gspca_frame_add (err -22)
[ 988.517415] gspca_stv06xx: disagrees about version of symbol gspca_dev_probe
[ 988.517422] gspca_stv06xx: Unknown symbol gspca_dev_probe (err -22)
[ 988.665081] usbcore: registered new interface driver snd-usb-audio

AND
it is working perfectly on my netbook (nb30)
It is probably due to a hardware problem, as I have been experiencing several issues with this computer (though never with USB, that's why I allowed myself to point out this issue with the webcam)

Thanks a lot anyway for your support!

It still appears that your GSPCA loadable modules aren't agreeing with your kernel version. I doubt they are from the same kernel version, hence the "Unknown symbol" and "disagrees about". There should be no ambiguity between versions.

Hi,

I am a bit lost!

I reinstalled linux headers 2.6.35.27 via synaptics, I thought this would update gspca modules.
Could you briefly describe/send me a link on how/ I should proceed to install the latest module/ make sure I have it running?

Do I have to compile something? only the "stv006x" part, all the gspca module, ...?

Should I just download the files from git and copy them in:
/lib/modules/2.6.35-27-generic/kernel/drivers/media/video/gspca/ ?
or /sys/module/videodev/holders/gspca_main ?
/sys/module/gspca_main ?

I am loading 2.6.35.27 headers on start up, but I still have previous ones installed (2.6.35.22 and 2.6.35.25). Would that be likely to fix ambiguities to uninstall these headers?

Thanks for your help

This should do it:

sudo apt-get install linux-image-2.6.35-28-generic

Thanks but this version (2.6.35-28) is not in the official Ubuntu 10.10 rep.
I don't know if I should upgrade then, and if upgrading, why just to 35-28 as there are some newer versions.
I'm afraid of messing up the relatively stable system I have if I add the kernel team repository without much knowing about what I'm doing.

In which case, download the *.deb

  sudo aptitude download linux-image-2.6.35-27-generic

Extract it

  dpkg -x linux-image-2.6.35-27-generic /tmp

And copy the modules you need from the extracted deb

  cp /tmp/lib/modules/<blar> to /lib/modules/<blar>

You can see if they updated correctly using modinfo

  modinfo gspca_stv06xx

It did not work :

modinfo gspca_stv06xx

filename: /lib/modules/2.6.35-27-generic/kernel/drivers/media/video/gspca/stv06xx/gspca_stv06xx.ko
license: GPL
description: STV06XX USB Camera Driver
author: Erik Andrén
srcversion: E909E7274670A817439B742
alias: usb:v046Dp08F6d*dc*dsc*dp*ic*isc*ip*
alias: usb:v046Dp08F5d*dc*dsc*dp*ic*isc*ip*
alias: usb:v046Dp08F0d*dc*dsc*dp*ic*isc*ip*
alias: usb:v046Dp0870d*dc*dsc*dp*ic*isc*ip*
alias: usb:v046Dp0850d*dc*dsc*dp*ic*isc*ip*
alias: usb:v046Dp0840d*dc*dsc*dp*ic*isc*ip*
depends: gspca_main
vermagic: 2.6.35-27-generic SMP mod_unload modversions 686
parm: dump_bridge:Dumps all usb bridge registers at startup (bool)
parm: dump_sensor:Dumps all sensor registers at startup (bool)

dmesg:

usb 1-9.4: new full speed USB device using ehci_hcd and address 7
[ 147.303639] gspca_stv06xx: disagrees about version of symbol gspca_frame_add
[ 147.303648] gspca_stv06xx: Unknown symbol gspca_frame_add (err -22)
[ 147.304348] gspca_stv06xx: disagrees about version of symbol gspca_dev_probe
[ 147.304351] gspca_stv06xx: Unknown symbol gspca_dev_probe (err -22)

I'd say this is unrelated to this bug.

You'd be better off creating another (newer) one and someone will pick it up.

Yes, I will do that, but as I said, I 'm skeptikal about the nature of my problems (hardware/software):
I have kernel panics, non human readable MCE, and a bunch of errors written in white or red appearing on first boots...
However, just for your interest, it seems to work a bit better today though I did not do anything special : no disagreement about version between stv06xx and gspca, just a bandwidth problem!
Thanks

Well the bandwidth problem is solved in a latter kernel.

You'd have to upgrade your distribution to make use of it though.