Description of problem: I have been trying to find a solution to this for a while. In mdv as well. At around the introduction of 2.6.34 kernels my webcam became almost useless in all light levels. I use it mainly in Skype, and at first blamed Skype. Today I ran a test on PCLOS 2010 running 2.6.32.12 kernel and the same latest Skype Beta 2.2.0.25 that I am using in Mageia. The result was perfect. I then searched Google and eventually found the exact issue in Arch Linux (link above). The image in this bug report shows the problem. I don't understand the solution details, but this really needs fixing in Mageia. Version-Release number of selected component (if applicable): My webcam is (041e:4053) How reproducible: Steps to Reproduce: 1. 2. 3.
I added this link to the above bug, but it is missing from the report. I used the URL field - where did it go? https://bbs.archlinux.org/viewtopic.php?id=109501
The URL field is hidden in the bug report page... it should be fixed indeed.
Assignee: bugsquad => tmbSource RPM: kernel modules => kernel
This looks relevant :- https://qa.mandriva.com/show_bug.cgi?id=55713#c11 I will try to use the patched ov51x_jpeg and 2.6.38.6-desktop-1.mga with my camera, and post results.
OK after talking to pterjan on #mageia-dev I have tried to use a test version of gspca_zc3xx.ko results:- [baz@jackodesktop ~]$ su Password: [root@jackodesktop baz]# lsmod | grep gspca gspca_zc3xx 50909 0 gspca_main 27725 1 gspca_zc3xx usbcore 167270 9 uas,usb_storage,uhci_hcd,ohci_hcd,ehci_hcd,usbhid,gspca_zc3xx,gspca_main videodev 70993 1 gspca_main [root@jackodesktop baz]# rmmod gspca_zc3xx [root@jackodesktop baz]# insmod ./gspca_zc3xx.ko Message from syslogd@jackodesktop at May 24 11:08:45 ... kernel:Oops: 0000 [#1] SMP Message from syslogd@jackodesktop at May 24 11:08:45 ... kernel:last sysfs file: /sys/devices/pci0000:00/0000:00:02.2/usb1/1-7/1-7:1.0/host7/target7:0:0/7:0:0:0/block/sdd/sdd2/uevent Message from syslogd@jackodesktop at May 24 11:08:45 ... kernel:Process insmod (pid: 19886, ti=df2a6000 task=df2f0c90 task.ti=df2a6000) Message from syslogd@jackodesktop at May 24 11:08:45 ... kernel:Stack: Message from syslogd@jackodesktop at May 24 11:08:45 ... kernel:Call Trace: Killed [root@jackodesktop baz]# Message from syslogd@jackodesktop at May 24 11:08:45 ... kernel:Code: c1 e2 08 81 ca 80 00 00 80 89 7c 24 08 c7 44 24 04 01 00 00 00 c7 04 24 c0 00 00 00 e8 53 00 76 ff 85 c0 78 18 8b 83 48 02 00 00 <0f> b6 30 89 f0 8b 5d f4 8b 75 f8 8b 7d fc 89 ec 5d c3 89 44 24 Message from syslogd@jackodesktop at May 24 11:08:45 ... kernel:EIP: [<f45581f7>] reg_r_i+0x77/0xb0 [gspca_zc3xx] SS:ESP 0068:df2a7d0c Message from syslogd@jackodesktop at May 24 11:08:45 ... kernel:CR2: 0000000000000000 ^C [root@jackodesktop baz]# uname -r 2.6.38.6-desktop-1.mga [root@jackodesktop baz]#
CC: (none) => pterjan
Is there anything that can be done to fix these issues with gspca_zc3xx or is it just deprecated in favour of UVC? It seems a shame that something that used to work so well in Mandriva with older kernels is now so totally broken. FWIW I finally gave up and bought a new UVC webcam and it is perfect.
pinging because this bug still has the NEW status and nothing happened to it it more than 4 months. @ tmb Please set status to ASSIGNED if you think this bug was assigned correctly. If for workflow reasons you can't do that, then please put OK on the whiteboard instead. Did you see that the reporter gave up and bought a new UVC webcam? I don't have the slightest idea how many users still need the patch, but since none of them came here to tell they're having the same issue, I'm wondering whether it wouldn't be better to just close this bug.
CC: (none) => marja11
3-monthly ping
(In reply to comment #7) > 3-monthly ping I tried to test again with current kernel etc. but spent an hour searching for the camera in question. I will keep looking, but as there have been no further comments, then perhaps closing it with the option to re-open is the best way to go, as it no longer affects me. Barry
Thanks for the feedback, Barry. Closing as old then. Of course it can be reopened if needed.
Status: NEW => RESOLVEDResolution: (none) => OLD