emerging the media-video/qc-usb-messenger-1.8-r2 package was successful, but the module load brings up errors within demsg output. Any hints how to solve that situation? Many Thanks in Advance!
Created attachment 188671 [details] Additional Information
Various QuickCam models (including QuickCam messenger) are now supported by gspcav2 [1], which is in the kernel. I'd like to test it and remove qc-usb-messenger if gspcav2 can replace it. I don't have my QuickCam right now, so if anyone could test it... [1] http://moinejf.free.fr/webcam.html
Unfortunately I can not do your requested test, because my model is a Logitech QuickCam Communicate (046d:08f5), which seems not to be supported by gspcav2. (have not found my web cam ID on the advised link) The only hint I have found on the Web is: http://www.quickcamteam.net/devices/non-uvc-webcams Which state that the used chip should be a "ST6422", which I was not able to find on the Kernel configuration.
I got a Logitech Quickcam messenger USB (046d:08f6) and it is not supported by qspcav2. I used qc-usb-messenger in the past, now it stop working. Last try was with versione 1.8-r2 and 2.6.29 and this were the result while trying to use xawtv: Apr 26 18:45:36 eagle3 BUG: unable to handle kernel paging request at ffff880117768540 Apr 26 18:45:36 eagle3 IP: [<ffff880117768540>] 0xffff880117768540 Apr 26 18:45:36 eagle3 PGD 202063 PUD 13067 PMD 80000001176001e3 Apr 26 18:45:36 eagle3 Oops: 0011 [#1] PREEMPT SMP Apr 26 18:45:36 eagle3 last sysfs file: /sys/devices/platform/coretemp.1/temp1_input Apr 26 18:45:36 eagle3 CPU 0 Apr 26 18:45:36 eagle3 Modules linked in: qcmessenger videodev v4l1_compat v4l2_compat_ioctl32 ipv6 snd_pcm_oss snd_mixer_oss snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device bridge stp llc usbhid hid snd_hda_codec_realtek snd_hda_intel iwlagn snd_hda_codec iwlcore lib80211 mac80211 snd_hwdep snd_pcm ehci_hcd uhci_hcd cfg80211 snd_timer nvidia(P) snd snd_page_alloc usbcore tifm_7xx1 tifm_core [last unloaded: v4l2_compat_ioctl32] Apr 26 18:45:36 eagle3 Pid: 10211, comm: v4l-conf Tainted: P 2.6.29-tuxonice #1 VGN-NR21Z_S Apr 26 18:45:36 eagle3 RIP: 0010:[<ffff880117768540>] [<ffff880117768540>] 0xffff880117768540 Apr 26 18:45:36 eagle3 RSP: 0018:ffff880117659d40 EFLAGS: 00010282 Apr 26 18:45:36 eagle3 RAX: 0000000000000000 RBX: 00000000fffffe00 RCX: 0000000000000000 Apr 26 18:45:36 eagle3 RDX: ffff8801251f7600 RSI: ffff8801251be3d0 RDI: ffff8801251f7600 Apr 26 18:45:36 eagle3 RBP: ffff8801251be000 R08: 0000000000000000 R09: ffff8801251f7cc0 Apr 26 18:45:36 eagle3 R10: ffff880117659e68 R11: 0000000000000000 R12: ffff8801251f7600 Apr 26 18:45:36 eagle3 R13: ffff8801251f7600 R14: ffff8801251f7600 R15: ffff880111b483c0 Apr 26 18:45:36 eagle3 FS: 00007f204fc4a6f0(0000) GS:ffffffff80737040(0000) knlGS:0000000000000000 Apr 26 18:45:36 eagle3 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b Apr 26 18:45:36 eagle3 CR2: ffff880117768540 CR3: 0000000111652000 CR4: 00000000000006e0 Apr 26 18:45:36 eagle3 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Apr 26 18:45:36 eagle3 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Apr 26 18:45:36 eagle3 Process v4l-conf (pid: 10211, threadinfo ffff880117658000, task ffff88012ffe6300) Apr 26 18:45:36 eagle3 Stack: Apr 26 18:45:36 eagle3 ffffffffa091103a ffff880117659e68 0000000000000051 ffff8801251be0d8 Apr 26 18:45:36 eagle3 ffff8801251be040 ffff8801251f7600 ffff8801251be048 0000000000000001 Apr 26 18:45:36 eagle3 ffffffffa08f7981 0000000000000000 ffff880117f0d200 ffff8801176fb2b0 Apr 26 18:45:36 eagle3 Call Trace: Apr 26 18:45:36 eagle3 [<ffffffffa091103a>] ? 0xffffffffa091103a Apr 26 18:45:36 eagle3 [<ffffffffa08f7981>] ? 0xffffffffa08f7981 Apr 26 18:45:36 eagle3 [<ffffffff802c1ca5>] ? 0xffffffff802c1ca5 Apr 26 18:45:36 eagle3 [<ffffffff802c1b70>] ? 0xffffffff802c1b70 Apr 26 18:45:36 eagle3 [<ffffffff802bc4e4>] ? 0xffffffff802bc4e4 Apr 26 18:45:36 eagle3 [<ffffffff802cb31b>] ? 0xffffffff802cb31b Apr 26 18:45:36 eagle3 [<ffffffff80236e30>] ? 0xffffffff80236e30 Apr 26 18:45:36 eagle3 [<ffffffff805971d2>] ? 0xffffffff805971d2 Apr 26 18:45:36 eagle3 [<ffffffff80597060>] ? 0xffffffff80597060 Apr 26 18:45:36 eagle3 [<ffffffff802d5742>] ? 0xffffffff802d5742 Apr 26 18:45:36 eagle3 [<ffffffff802bc300>] ? 0xffffffff802bc300 Apr 26 18:45:36 eagle3 [<ffffffff8020c69b>] ? 0xffffffff8020c69b Apr 26 18:45:36 eagle3 Code: 00 00 00 18 85 76 17 01 88 ff ff 18 85 76 17 01 88 ff ff 00 00 00 00 00 00 00 00 10 77 ec 3a 01 88 ff ff 00 00 00 00 00 00 00 00 <c0> 70 9f 1f 01 88 ff ff 00 76 1f 25 01 88 ff ff 00 bf 8e 3e 01 Apr 26 18:45:36 eagle3 RIP [<ffff880117768540>] 0xffff880117768540 Apr 26 18:45:36 eagle3 RSP <ffff880117659d40> Apr 26 18:45:36 eagle3 CR2: ffff880117768540 Apr 26 18:45:36 eagle3 ---[ end trace af5bb4676cef9703 ]---
(In reply to comment #4) > I got a Logitech Quickcam messenger USB (046d:08f6) and it is not supported by > qspcav2. I used qc-usb-messenger in the past, now it stop working. Last try was > with versione 1.8-r2 and 2.6.29 and this were the result while trying to use > xawtv: Correct, the camera is not supported by qspcav2 but by the qc-usb-messenger ebuild. And correct again that since 2.6.29 the kernel module oopses. I have seen it myself on my ppc box. Today I created a first patch for 2.6.30.4 which I hope to be able to test later tonight once my wife gets off the computer. The patch should allow me at least to load the kernel module again and to figure out what is going on. I'll keep you posted. Cheers, Thomas
The problem is apparent on ppc, too. Hence the "Hardware" field should be changed to "All". Cheers, Thomas
Hi folks, I just committed patches for the qc-usb-messenger ebuild. It works now on kernel s 2.6.30.x again. The related bug is [https://bugs.gentoo.org/show_bug.cgi?id=279992]. Cheers, Thomas
*** This bug has been marked as a duplicate of bug 277605 ***
