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