[PlanetCCRMA] Re: PlanetCCRMA/NVidia
Peter Baker
keys_sax at tpg.com.au
Fri Jun 1 09:08:01 PDT 2007
Hi Matt
You make some good points but luckily I only have one machine to look
after :-)
Cheers
peter
Matt Barber wrote:
> 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.
>
> 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.
>
> Matt
>
> On 6/1/07, *Peter Baker* <keys_sax at tpg.com.au
> <mailto:keys_sax at tpg.com.au>> wrote:
>
> Hi All
>
> I´ve noticed lots of email traffic about this and about ntfs at times.
> As I finally replaced my 10 year old machine with a brand new one, I´m
> now starting to play with planetccrma which is great!!
>
> A friend of mineś solution which works well is not to use rpms but use
> the shell script from the nvidia site. When it can´t find an
> appropriate
> rpm the script prompts you and asks if it should build and install the
> nvidia kernel modules. Of course you need to rerun the script each
> time
> you get a new kernel but its pretty painless. See
> http://www.nvidia.com/object/unix.html which also has legacy stuff
>
> This works really well for me
>
> Also on a related note, ntfs-3g from extras seems to work very
> well with
> reading/writing ntfs partitions and avoids the kernel module kmod
> approach
>
> Hope this helps someone
>
> cheers
> Peter
>
> Matt Barber wrote:
> > Hello,
> >
> > Sure thing, glad it was helpful.
> >
> > Matt
> >
> >
> > --__--__--
> >
> > Message: 5
> > Date: Thu, 31 May 2007 20:50:51 +0200
> > From: Louis van Dompselaar <louis at dompselaar.org
> <mailto:louis at dompselaar.org>
> > <mailto:louis at dompselaar.org <mailto:louis at dompselaar.org>>>
> > To: planetccrma at ccrma.Stanford.EDU
> <mailto:planetccrma at ccrma.Stanford.EDU>
> > <mailto:planetccrma at ccrma.Stanford.EDU
> <mailto:planetccrma at ccrma.Stanford.EDU>>
> > Subject: [PlanetCCRMA] PlanetCCRMA/NVidia
> >
> > This is a multi-part message in MIME format.
> > --------------090503030300080602010107
> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> > Content-Transfer-Encoding: 7bit
> >
> > I'd like to thank Matt again for the instructions below. I only
> > now came to
> > trying them and finally got kmod-nvidia-legacy to work on
> ccrma/fc6!
> >
> >
> > Matt Barber <mailto: brbrofsvl%40gmail.com
> > <mailto: brbrofsvl%40gmail.com <mailto:brbrofsvl%40gmail.com>>>
> > /Sun May 20 13:09:03 2007/
> >
> ------------------------------------------------------------------------
> >
> > You have to hack the spec file, and there are only a couple of
> > things that
> > need to be changed for nvidia --
> >
> > substitute your current ccrma kernel name ( output of uname -r )
> > for the
> > fedora kernel in kversion definition. Mine looks like this:
> >
> > %{!?kversion: %define kversion 2.6.21-0143.rt1.3.fc6.ccrmart }
> >
> >
> > in the kvariants definition line, remove all of the variants
> except
> > %{?upvar} -- since you're not building variants for a xen
> kernel
> > (etc...).
> >
> > my line looks like this:
> >
> > %{!?kvariants: %define kvariants %{?upvar}}
> >
> > I usually delete all the corresponding preceding definitions
> as well,
> > leaving only
> >
> > %define upvar ""
> >
> >
> > write it, and then
> >
> > rpmbuild -ba --target i686 nvidia-kmod.spec
> >
> > (this will make both the module and a .src.rpm for you to use
> > later if you
> > wish)
> >
> >
> >
> > --------------090503030300080602010107
> > Content-Type: text/html; charset=ISO-8859-1
> > Content-Transfer-Encoding: 7bit
> >
> > <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
> > <html>
> > <head>
> > </head>
> > <body bgcolor="#ffffff" text="#000000">
> > I'd like to thank Matt again for the instructions below. I
> > only now
> > came to<br>
> > trying them and finally got kmod-nvidia-legacy to work on
> > ccrma/fc6!<br>
> > <br>
> > <br>
> > Matt Barber<a href="mailto:brbrofsvl%40gmail.com
> <mailto:brbrofsvl%40gmail.com>
> > <mailto: brbrofsvl%40gmail.com <mailto:brbrofsvl%40gmail.com>>"
> > title="[PlanetCCRMA] kmod-ntfs"></a><br>
> > <i>Sun May 20 13:09:03 2007</i>
> > <hr><!--beginarticle-->
> > <pre>You have to hack the spec file, and there are only a couple
> > of things that
> > need to be changed for nvidia --
> >
> > substitute your current ccrma kernel name ( output of uname
> -r )
> > for the
> > fedora kernel in kversion definition. Mine looks like this:
> >
> > %{!?kversion: %define kversion 2.6.21-0143.rt1.3.fc6.ccrmart}
> >
> >
> > in the kvariants definition line, remove all of the variants
> except
> > %{?upvar} -- since you're not building variants for a xen kernel
> > (etc...).
> >
> > my line looks like this:
> >
> > %{!?kvariants: %define kvariants %{?upvar}}
> >
> > I usually delete all the corresponding preceding definitions
> as well,
> > leaving only
> >
> > %define upvar ""
> >
> >
> > write it, and then
> >
> > rpmbuild -ba --target i686 nvidia-kmod.spec
> >
> > (this will make both the module and a .src.rpm for you to use
> > later if you
> > wish)</pre>
> > <br>
> > </body>
> > </html>
> >
> > --------------090503030300080602010107--
> >
> >
> >
> > --__--__--
> >
> > _______________________________________________
> > PlanetCCRMA mailing list
> > PlanetCCRMA at ccrma.stanford.edu
> <mailto:PlanetCCRMA at ccrma.stanford.edu>
> <mailto:PlanetCCRMA at ccrma.stanford.edu
> <mailto:PlanetCCRMA at ccrma.stanford.edu>>
> > http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma
> >
> >
> > End of PlanetCCRMA Digest
> >
> >
>
>
More information about the PlanetCCRMA
mailing list