One nice thing about doing it with RPM is that you know exactly what it's putting on your system, and you have full control over installing or uninstalling -- useful if you like or need to tinker with hardware, e.g., or like to run tests on kernels. They are also especially useful if you sysadmin a number of computers -- you can just put the RPMS on a server and install from there as needed, with other kmods and packages. I rebuild csound (csound's "sndinfo" utility conflicts with that from snd; also for csoundapi object in PD), mplayer (for jack support), and wine (for compatibility with ccrma's libjack) as well, and it's nice to have all the rpms in one place.
<br><br>It looks to me like it's becoming more and more standard for distributions to have their package managers handle third-party modules. I know this is the case with ubuntu, for instance.<br><br>Matt<br><br><div>
<span class="gmail_quote">On 6/1/07, <b class="gmail_sendername">Peter Baker</b> <<a href="mailto:keys_sax@tpg.com.au">keys_sax@tpg.com.au</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;">
Hi All<br><br>I´ve noticed lots of email traffic about this and about ntfs at times.<br>As I finally replaced my 10 year old machine with a brand new one, I´m<br>now starting to play with planetccrma which is great!!<br><br>
A friend of mineś solution which works well is not to use rpms but use<br>the shell script from the nvidia site. When it can´t find an appropriate<br>rpm the script prompts you and asks if it should build and install the<br>
nvidia kernel modules. Of course you need to rerun the script each time<br>you get a new kernel but its pretty painless. See<br><a href="http://www.nvidia.com/object/unix.html">http://www.nvidia.com/object/unix.html</a> which also has legacy stuff
<br><br>This works really well for me<br><br>Also on a related note, ntfs-3g from extras seems to work very well with<br>reading/writing ntfs partitions and avoids the kernel module kmod approach<br><br>Hope this helps someone
<br><br>cheers<br>Peter<br><br>Matt Barber wrote:<br>> Hello,<br>><br>> Sure thing, glad it was helpful.<br>><br>> Matt<br>><br>><br>> --__--__--<br>><br>> Message: 5<br>> Date: Thu, 31 May 2007 20:50:51 +0200
<br>> From: Louis van Dompselaar <<a href="mailto:louis@dompselaar.org">louis@dompselaar.org</a><br>> <mailto:<a href="mailto:louis@dompselaar.org">louis@dompselaar.org</a>>><br>> To: <a href="mailto:planetccrma@ccrma.Stanford.EDU">
planetccrma@ccrma.Stanford.EDU</a><br>> <mailto:<a href="mailto:planetccrma@ccrma.Stanford.EDU">planetccrma@ccrma.Stanford.EDU</a>><br>> Subject: [PlanetCCRMA] PlanetCCRMA/NVidia<br>><br>> This is a multi-part message in MIME format.
<br>> --------------090503030300080602010107<br>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>> Content-Transfer-Encoding: 7bit<br>><br>> I'd like to thank Matt again for the instructions below. I only
<br>> now came to<br>> trying them and finally got kmod-nvidia-legacy to work on ccrma/fc6!<br>><br>><br>> Matt Barber <mailto: brbrofsvl%40gmail.com<br>> <mailto:<a href="mailto:brbrofsvl%40gmail.com">
brbrofsvl%40gmail.com</a>>><br>> /Sun May 20 13:09:03 2007/<br>> ------------------------------------------------------------------------<br>><br>> You have to hack the spec file, and there are only a couple of
<br>> things that<br>> need to be changed for nvidia --<br>><br>> substitute your current ccrma kernel name ( output of uname -r )<br>> for the<br>> fedora kernel in kversion definition. Mine looks like this:
<br>><br>> %{!?kversion: %define kversion 2.6.21-0143.rt1.3.fc6.ccrmart }<br>><br>><br>> in the kvariants definition line, remove all of the variants except<br>> %{?upvar} -- since you're not building variants for a xen kernel
<br>> (etc...).<br>><br>> my line looks like this:<br>><br>> %{!?kvariants: %define kvariants %{?upvar}}<br>><br>> I usually delete all the corresponding preceding definitions as well,
<br>> leaving only<br>><br>> %define upvar ""<br>><br>><br>> write it, and then<br>><br>> rpmbuild -ba --target i686 nvidia-kmod.spec<br>><br>> (this will make both the module and a .src.rpm for you to use
<br>> later if you<br>> wish)<br>><br>><br>><br>> --------------090503030300080602010107<br>> Content-Type: text/html; charset=ISO-8859-1<br>> Content-Transfer-Encoding: 7bit<br>
><br>> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><br>> <html><br>> <head><br>> </head><br>> <body bgcolor="#ffffff" text="#000000">
<br>> I'd like to thank Matt again for the instructions below.&nbsp; I<br>> only now<br>> came to<br><br>> trying them and finally got kmod-nvidia-legacy to work on<br>> ccrma/fc6!<br>
<br>> <br><br>> <br><br>> Matt Barber<a href="mailto:<a href="mailto:brbrofsvl%40gmail.com">brbrofsvl%40gmail.com</a><br>> <mailto:<a href="mailto:brbrofsvl%40gmail.com">
brbrofsvl%40gmail.com</a>>"<br>> title="[PlanetCCRMA] kmod-ntfs"></a><br><br>> <i>Sun May 20 13:09:03 2007</i><br>> <hr><!--beginarticle--><br>
> <pre>You have to hack the spec file, and there are only a couple<br>> of things that<br>> need to be changed for nvidia --<br>><br>> substitute your current ccrma kernel name ( output of uname -r )
<br>> for the<br>> fedora kernel in kversion definition. Mine looks like this:<br>><br>> %{!?kversion: %define kversion 2.6.21-0143.rt1.3.fc6.ccrmart}<br>><br>><br>> in the kvariants definition line, remove all of the variants except
<br>> %{?upvar} -- since you're not building variants for a xen kernel<br>> (etc...).<br>><br>> my line looks like this:<br>><br>> %{!?kvariants: %define kvariants %{?upvar}}<br>><br>
> I usually delete all the corresponding preceding definitions as well,<br>> leaving only<br>><br>> %define upvar ""<br>><br>><br>> write it, and then<br>><br>> rpmbuild -ba --target i686
nvidia-kmod.spec<br>><br>> (this will make both the module and a .src.rpm for you to use<br>> later if you<br>> wish)</pre><br>> <br><br>> </body><br>> </html>
<br>><br>> --------------090503030300080602010107--<br>><br>><br>><br>> --__--__--<br>><br>> _______________________________________________<br>> PlanetCCRMA mailing list<br>>
<a href="mailto:PlanetCCRMA@ccrma.stanford.edu">PlanetCCRMA@ccrma.stanford.edu</a> <mailto:<a href="mailto:PlanetCCRMA@ccrma.stanford.edu">PlanetCCRMA@ccrma.stanford.edu</a>><br>> <a href="http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma">
http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma</a><br>><br>><br>> End of PlanetCCRMA Digest<br>><br>><br><br></blockquote></div><br>