[PlanetCCRMA] Nvidia working with 2.6.33.6-147.2.4.rt28.1.fc13.ccrma.x86_64.rt

William Blackburn bill_- at hotmail.com
Wed Sep 22 17:08:41 PDT 2010 

Hello , I wanted to post that I have managed to get the nvidia developer driver  driver  260.24 working with the 2.6.33.6-147.2.4.rt28.1.fc13.ccrma.x86_64.rtkernel.  I do get the warnings from abrt tool but that is nothing new.   I just wanted to let everyone that in case you are reluctant to try it.  If you need assistance, I will be happy to point you in the right direction. 

> From: planetccrma-request at ccrma.Stanford.EDU
> Subject: PlanetCCRMA Digest, Vol 31, Issue 24
> To: planetccrma at ccrma.Stanford.EDU
> Date: Wed, 22 Sep 2010 12:00:02 -0700
> 
> Send PlanetCCRMA mailing list submissions to
> 	planetccrma at ccrma.stanford.edu
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma
> or, via email, send a message with subject or body 'help' to
> 	planetccrma-request at ccrma.stanford.edu
> 
> You can reach the person managing the list at
> 	planetccrma-owner at ccrma.stanford.edu
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of PlanetCCRMA digest..."
> 
> 
> Today's Topics:
> 
>    1. Re: fc13: alsa-tools, jconvolver (Geoff King)
>    2. Re: fc13: alsa-tools, jconvolver (Bernardo Barros)
>    3. Re: [SOLVED] firewire on CCRMA-Fedora-12 (linux media 4)
>    4. Re: fc13: alsa-tools, jconvolver (Geoff King)
>    5. Re: fc13: alsa-tools, jconvolver (Bernardo Barros)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Tue, 21 Sep 2010 19:21:19 -0400
> From: Geoff King <gsking1 at gmail.com>
> Subject: Re: [PlanetCCRMA] fc13: alsa-tools, jconvolver
> To: Fernando Lopez-Lezcano <nando at ccrma.Stanford.EDU>
> Cc: Bernardo Barros <bernardobarros2 at gmail.com>,	Jeff Sandys
> 	<jpsandys at gmail.com>, planetccrma at ccrma.Stanford.EDU
> Message-ID: <1285111279.8657.3.camel at blaster>
> Content-Type: text/plain; charset="UTF-8"
> 
> Just tried the new akmod-nvidia for ccrma.  Works great!  I was
> previously using the nvidia installer and patch.
> Thanks, Geoff
> 
> 
> > You could try enabling the planetcore-testing repository and installing 
> > akmod-nvidia. That will take care of pretty much everything, including 
> > adding parameters to the kernel boot line that do the righ thing with 
> > the nouveau driver. The kernel module will hopefully be compiled on your 
> > next boot. Make sure you have the kernel-rtPAE-devel or kernel-rt-devel 
> > packages installed before doing any of this...
> > 
> > -- Fernando
> 
> 
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Tue, 21 Sep 2010 23:29:54 -0300
> From: Bernardo Barros <bernardobarros2 at gmail.com>
> Subject: Re: [PlanetCCRMA] fc13: alsa-tools, jconvolver
> To: Geoff King <gsking1 at gmail.com>
> Cc: Fernando Lopez-Lezcano <nando at ccrma.Stanford.EDU>,
> 	planetccrma at ccrma.Stanford.EDU, Jeff Sandys <jpsandys at gmail.com>
> Message-ID:
> 	<AANLkTinFm8BsE8ZFO271+j-D=LNiyYppdTo9dT1B0oF+ at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
> 
> Here it worked great too. I can see a big difference in system and
> jack performance, that is: less memory and no xruns on very low
> latencies (11ms) with the normal generic last fedora kernel.
> 
> But the rt-kernel does not start up anymore. That's just me?
> 
> 2010/9/21 Geoff King <gsking1 at gmail.com>:
> > Just tried the new akmod-nvidia for ccrma. ?Works great! ?I was
> > previously using the nvidia installer and patch.
> > Thanks, Geoff
> >
> >
> >> You could try enabling the planetcore-testing repository and installing
> >> akmod-nvidia. That will take care of pretty much everything, including
> >> adding parameters to the kernel boot line that do the righ thing with
> >> the nouveau driver. The kernel module will hopefully be compiled on your
> >> next boot. Make sure you have the kernel-rtPAE-devel or kernel-rt-devel
> >> packages installed before doing any of this...
> >>
> >> -- Fernando
> >
> >
> >
> 
> 
> 
> ------------------------------
> 
> Message: 3
> Date: Tue, 21 Sep 2010 20:49:56 -0700
> From: linux media 4 <linuxmedia4 at netscape.net>
> Subject: Re: [PlanetCCRMA] [SOLVED] firewire on CCRMA-Fedora-12
> To: planetccrma at ccrma.Stanford.EDU
> Message-ID: <4C997CE4.5090506 at netscape.net>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> 
> >> Hi,
> >>
> >> This week I installed CCRMA-Fedora-13 but had to abandon it because I
> >> couldn't get the firewire driver working with my Focusright Saffire Pro
> >> 10 (the jack ports had long numerical names and wouldn't let certain
> >> ports connect with other ports). I googled around for quite a while, but
> >> found no solution.
> >>
> >> So I installed CCRMA-Fedora-12. At first it was saying that it couldn't
> >> find jack_firewire.so, but I found a post that mentioned that you have
> >> to install libffado-devel (along with libffado of course). But now jackd
> >> fails with the message:
> >>
> >> bash>   /usr/bin/jackd -dfirewire -r96000 -p1024 -n3
> >> [CUT]
> >> JACK server starting in realtime mode with priority 60
> >> 01345759929:  (ffado.cpp)[  92] ffado_streaming_init: libffado 2.999.0-
> >> built Jul 18 2010 21:25:26
> >> firewire ERR: FFADO: Error creating virtual device
> >> Cannot attach audio driver
> >> JackServer::Open() failed with -1
> >> no message buffer overruns
> >> Failed to start server
> >>
> >> I did a bit of googling around tonight but ran out of time. Does anyone
> >> know how to get this working?
> >>
> >> Here are the details...
> >>
> >> bash>   uname -r
> >> 2.6.31.12-1.rt20.1.fc12.ccrma.i686.rtPAE
> >>
> >> bash>   yum list jack-audio-connection-kit
> >> Installed Packages
> >> jack-audio-connection-kit.i686  1.9.4-1.fc12.ccrma  @planetccrma
> >>
> >> bash>   yum list ffado
> >> Installed Packages
> >> ffado.i686  2.0.1-3.20100706.svn1864.fc12  @updates
> >>
> >> bash>   yum list libraw1394
> >> Installed Packages  libraw1394.i686 2.0.5-2.fc12 @updates
> >>
> >> Any ideas of how to get firewire working would be appreciated. I would
> >> prefer to work with CCRMA-Fedora-12 because it's already up and running,
> >> and besides, I couldn't get my wireless connection working with
> >> CCRMA-Fedora-13.
> >>
> >> Thanks,
> >> Rocco
> 
> > Following a hint while googling, I temporarily changed the permissions
> > on /dev/raw1394 to make myself the owner. It worked. So that tells me
> > the base of the problem.
> >
> > As you can see...
> >
> > bash>  ls -la /dev/raw1394
> > crw-rw---- 1 root root 171, 0 2010-09-20 21:54 /dev/raw1394
> >
> > ... raw1394 is in the group "root".
> >
> > I seldom ask anyone to hold my hand, but all the googling isn't telling
> > me how to properly set up firewire to allow "normal users" to use it,
> > and I don't want to experiment with things that can cause problems on my
> > system. There seems to be a lot of layers to setting up permissions and
> > I'm not understanding. What is the proper way of setting things up to
> > allow normal users to access firewire?
> >
> > Thank you,
> > Rocco
> 
> I want to include what I did to allow a normal user to have access to 
> firewire, in case anyone else runs into this situation...
> 
> Create the file:
> /lib/udev/rules.d/50-raw-firewire.rules
> 
> Copy this into the file:
> KERNEL=="raw1394", NAME="raw1394", GROUP="audio"
> 
> Use an application to make a user part of the group "audio"
> In KDE I went to:
> -> Administration
> -> Users and Groups
> -> Click "Users" Tab
> -> highlight user you want to add to the audio group
> -> Click "Properties"
> -> Choose "Groups" Tab
> -> Check the "audio" group
> 
> If no application exists, then, in the file "/etc/group" add the user's 
> name at the end of "audio". For instance, mine looks like this...
> 
> audio:x:63:rocco
> 
> Rocco
> 
> 
> 
> ------------------------------
> 
> Message: 4
> Date: Wed, 22 Sep 2010 08:55:08 -0400
> From: Geoff King <gsking1 at gmail.com>
> Subject: Re: [PlanetCCRMA] fc13: alsa-tools, jconvolver
> To: Bernardo Barros <bernardobarros2 at gmail.com>
> Cc: Fernando Lopez-Lezcano <nando at ccrma.Stanford.EDU>,
> 	planetccrma at ccrma.Stanford.EDU, Jeff Sandys <jpsandys at gmail.com>
> Message-ID:
> 	<AANLkTikfzm2ZBXF5-SH=XNBa2GVQ1cRHs_z8yN7iAVa=@mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
> 
> Bernardo,
> If it doesn't work on the rt kernel, are you sure you have the ccrma
> version of akmod-nvidia?
> You can look at packages installed like this:  "rpm -qa | grep akmod"
> 
> You would either need to enable the repository as previously discussed
> or download and install the rpm
> (http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetcore/testing/13/)
> 
> Hope that helps.
> Geoff
> 
> 
> On Tue, Sep 21, 2010 at 10:29 PM, Bernardo Barros
> <bernardobarros2 at gmail.com> wrote:
> > Here it worked great too. I can see a big difference in system and
> > jack performance, that is: less memory and no xruns on very low
> > latencies (11ms) with the normal generic last fedora kernel.
> >
> > But the rt-kernel does not start up anymore. That's just me?
> >
> > 2010/9/21 Geoff King <gsking1 at gmail.com>:
> >> Just tried the new akmod-nvidia for ccrma. ?Works great! ?I was
> >> previously using the nvidia installer and patch.
> >> Thanks, Geoff
> >>
> >>
> >>> You could try enabling the planetcore-testing repository and installing
> >>> akmod-nvidia. That will take care of pretty much everything, including
> >>> adding parameters to the kernel boot line that do the righ thing with
> >>> the nouveau driver. The kernel module will hopefully be compiled on your
> >>> next boot. Make sure you have the kernel-rtPAE-devel or kernel-rt-devel
> >>> packages installed before doing any of this...
> >>>
> >>> -- Fernando
> >>
> >>
> >>
> >
> 
> 
> 
> ------------------------------
> 
> Message: 5
> Date: Wed, 22 Sep 2010 11:55:13 -0300
> From: Bernardo Barros <bernardobarros2 at gmail.com>
> Subject: Re: [PlanetCCRMA] fc13: alsa-tools, jconvolver
> To: Geoff King <gsking1 at gmail.com>
> Cc: Fernando Lopez-Lezcano <nando at ccrma.Stanford.EDU>,
> 	planetccrma at ccrma.Stanford.EDU, Jeff Sandys <jpsandys at gmail.com>
> Message-ID:
> 	<AANLkTinEScE6sdspBmZ8QArA2NQg1k4Wuct3Uh5XMvWK at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
> 
> I think so:
> 
> [bernardo at localhost ~]$ rpm -qa | grep akmod
> akmod-nvidia-256.53-1.1.fc13.ccrma.3.x86_64
> akmods-0.3.6-3.fc12.noarch
> 
> 2010/9/22 Geoff King <gsking1 at gmail.com>:
> > Bernardo,
> > If it doesn't work on the rt kernel, are you sure you have the ccrma
> > version of akmod-nvidia?
> > You can look at packages installed like this: ?"rpm -qa | grep akmod"
> >
> > You would either need to enable the repository as previously discussed
> > or download and install the rpm
> > (http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetcore/testing/13/)
> >
> > Hope that helps.
> > Geoff
> >
> >
> > On Tue, Sep 21, 2010 at 10:29 PM, Bernardo Barros
> > <bernardobarros2 at gmail.com> wrote:
> >> Here it worked great too. I can see a big difference in system and
> >> jack performance, that is: less memory and no xruns on very low
> >> latencies (11ms) with the normal generic last fedora kernel.
> >>
> >> But the rt-kernel does not start up anymore. That's just me?
> >>
> >> 2010/9/21 Geoff King <gsking1 at gmail.com>:
> >>> Just tried the new akmod-nvidia for ccrma. ?Works great! ?I was
> >>> previously using the nvidia installer and patch.
> >>> Thanks, Geoff
> >>>
> >>>
> >>>> You could try enabling the planetcore-testing repository and installing
> >>>> akmod-nvidia. That will take care of pretty much everything, including
> >>>> adding parameters to the kernel boot line that do the righ thing with
> >>>> the nouveau driver. The kernel module will hopefully be compiled on your
> >>>> next boot. Make sure you have the kernel-rtPAE-devel or kernel-rt-devel
> >>>> packages installed before doing any of this...
> >>>>
> >>>> -- Fernando
> >>>
> >>>
> >>>
> >>
> >
> 
> 
> 
> ------------------------------
> 
> _______________________________________________
> PlanetCCRMA mailing list
> PlanetCCRMA at ccrma.stanford.edu
> http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma
> 
> 
> End of PlanetCCRMA Digest, Vol 31, Issue 24
> *******************************************
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://cm-mail.stanford.edu/pipermail/planetccrma/attachments/20100923/81ca78a1/attachment.html>

More information about the PlanetCCRMA mailing list