For the list :D
2009/12/9 Chris Wilkinson <blobster...@yahoo.com.au>: > Hi Paulo, > > My camera is working. I uninstalled then reinstalled everything related to > v4l, then again rebuilt the uvcvideo kernel module as per your instructions. > This time it worked and persists across reboots! :-) > > It is now I discover why the webcam was so cheap - in bright daylight image > is actually quite good, but from dusk onward our friends & family are going > to see some really grainy/slow-framerate video of us on skype - unless we > install a small sun in our apartment for night-skyping... :-) > > Never mind, its as good as I could expect for a AU$29 webcam, but best of > all I'm glad it now works in openSUSE 11.0! :-) > > Thanks for your help. > > Kind regards, > > Chris Wilkinson, Brisbane, Australia. > > ________________________________ > From: Paulo Assis <pj.as...@gmail.com> > To: linux-uvc development discussions <linux-uvc-devel@lists.berlios.de> > Sent: Wed, 9 December, 2009 8:02:36 AM > Subject: [Linux-uvc-devel] Fwd: New UVC webcam not working > > Hi, > This is my configuration for 2.6.31 (/etc/modprobe.d/uvcvideo.conf): > ------------//-------------- > #options for uvcvideo > options uvcvideo nodrop=1 trace=15 > ------------//-------------- > > but in your case you have to make sure you add all the correct modules > first (unload all the old ones): > Try following the v4l-dvb wiki first > (http://www.linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers) > especially the "Unresolved Symbols" section: > > ....... > > Unresolved Symbols > > * if you tried the second method ("make unload" followed by an > appropriate modprobe command) but encountered errors in relation to > unresolved symbols, e.g. using the saa7134 module as an example: > > sudo modprobe saa7134 > FATAL: Error inserting saa7134 (/lib/modules/[your kernel > version]/kernel/drivers/media/video/saa7134/saa7134.ko):\ > Unknown symbol in module, or unknown parameter (see dmesg) > > please try a system reboot before filing an error report. Irregardless > of what caused the unresolved symbols errors, usually, after > performing the reboot, you will find that the install was actually > successful and the drivers will work as intended. > > * Special case: If your system uses compressed kernel modules, > after running the "make install" command of the V4L-DVB installation > process, you could end up with a mixture of new modules (*.ko) and > their older compressed version (*.ko.gz) installed. If the system > attempts to concurrently load both sets into memory, you are bound to > run into modprobe insertion errors (eg. unknown symbol or unknown > parameter). All conflicting *.ko.gz files must be removed. The > following command line can help you locate these conflicting files in > all your installed kernels: > > for file in `find /lib/modules -name "*.ko"`; do if [[ -e $file.gz ]]; > then echo "$file.gz should be removed"; fi; done > > Usually all conflicting module files resulting of v4l-dvb installation > will be located in: > > /lib/modules/[your kernel version]/kernel/drivers/media > > Once the conflicting *.ko.gz have been moved elsewhere or renamed (to > *.ko.gz.disabled for example), use the v4l-dvb reload command and, to > be safe, also add a "depmod" step in order to rebuild modules > dependencies): > > make reload > depmod -a > > Your new modules should now be loaded correctly. > > ....... > > Best regards, > Paulo > _______________________________________________ > Linux-uvc-devel mailing list > Linux-uvc-devel@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/linux-uvc-devel > > ________________________________ > Win 1 of 4 Sony home entertainment packs thanks to Yahoo!7. Enter now. _______________________________________________ Linux-uvc-devel mailing list Linux-uvc-devel@lists.berlios.de https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
