<br><br><div><span class="gmail_quote">On 2/8/07, <b class="gmail_sendername">Keith Powell</b> <<a href="mailto:keith@keithg4jvx.force9.co.uk">keith@keithg4jvx.force9.co.uk</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I'm investigating my aMSN video problems.<br><br>At the moment, I have the MXhaard driver installed which I downloaded and<br>installed as a tarball.<br><br>I would like to uninstall it and try the atrpms version, to see if that
<br>improves things.<br><br>Please, how do I uninstall it, as I did a "modprobe gspca"?</blockquote><div><br>Modprobe just loads the driver to memory. It does not install anything. The installation script should have copied the module to /lib/modules/....
<br><br>Nonetheless, there should be no difference in performance using the tar ball or ATrpms'.<br>ATrpms uses the same tar ball. The only difference is that ATrpms drivers<br>always stay in a subdirectory called "updates":
<br><br>[lua:~] modinfo gspca<br>filename: /lib/modules/2.6.18-1.2257.fc5smp/updates/drivers/usb/media/gspca.ko<br><br>This way, an original kernel module will NEVER be replaced.<br>Also, when the kernel is upgraded there should be an appropriate kernel version in a few days.
<br>Sometimes, this may require some patches, for adapting the driver to the new kernel API. Therefore, using a rpm relieves the end user from any headache during the compilation process.<br> </div>So, is up to you when to use a pre-compiled rpm or a tar ball.
<br></div><br>-- <br>Paulo Roma Cavalcanti<br>LCG - UFRJ