[PlanetCCRMA] Need help getting realtime kernel working with Fedora 8 and nvidia

[Matt Barber]

Paul,

It seems unlikely that the JACK problem is related to the nvidia
driver -- start a new thread.  In the meantime, post a copy of the
output error message when you start jack - the problem I've seen most
often on Fedora 7 is related to something like the following not being
in /etc/security/limits.conf

----
## Automatically appended by the Planet CCRMA jack-audio-connection-kit
* - rtprio 99
* - memlock 4194304
* - nice -10
----


See here, for instance:

http://ccrma-mail.stanford.edu/pipermail/planetccrma/2008-April/014711.html

Since Fedora has its own JACK, if it was installed when you installed
the rest of the OS, sometimes you might see something different there
involving a jackuser group... if this is the case, you can usually
just comment that out and copy the above in.

There are other things that can keep jackd from starting, though, some
having to do with your specific hardware, so posting error messages is
always a good idea.

Thanks,

Matt

On Wed, May 14, 2008 at 6:11 PM, Paul Vallee <pv.vallee at gmail.com> wrote:
> Hi all,
>
> First of all, thanks for your help Matt, Juan and Hector. I couldn't have
> done it without you. I tried following Matt's instructions but ran into a
> roadblock when I discovered that the spec file had changed and I couldn't
> edit it properly to get the desired result. Then I stumbled upon the
> rpmfusion site and realized that we are now in the world of kmod "2.0".  No
> more fiddling with the spec file. Just add a couple of prameters to the
> rpmbuild command line and kmodtool does the rest.
>
> I followed the instructions here:
>
> http://rpmfusion.org/Packaging/KernelModules/Kmods2#head-a6ef94d0e888ea41a2335d30fe7da26814e23f8f
>
> and the nvidia driver installed on the planetccrma kernel without incident.
> Nice!
>
> When I rebooted, however, I was still having the same problems with extra
> characters being emitted when I press keys on the keyboard, erratic mouse
> behavior and Xwindows freezing eventually. I did a little more research and
> decided to try out the latest testing kernel from planetccrma. Good
> decision. I installed it, then installed the nvidia kernel module again for
> the new kernel and was pleasantly surprised to find out that I now had a
> working system with none of the problems described above. Good response, no
> perceivable delays in X.
>
> Thanks again, all. I've been struggling with this for about a week and it's
> such a good feeling to finally be at this stage of the process.
>
> Next, I installed the planetccrma-apps package. Now I have a new problem.
> JACK. It seems to start up when needed, but then exits immediately with
> status 1. I will do some more research and see if I can get it working on my
> own. If I can't though, I'm wondering if I should continue bleating about it
> in this topic or start a new topic for the JACK problem?
>
> Paul
>
>
>
> On Wed, May 14, 2008 at 10:35 AM, Matt Barber <brbrofsvl at gmail.com> wrote:
> > Juan,
> >
> > Terrific news.  Thanks for the info -- I'm sorry I missed your
> > february post.  Note that my method still works for Fedora 7 - I
> > suppose I should not have assumed that things hadn't changed for 8.
> > This change is for the better, though, and makes the drivers a lot
> > more flexible.  If you're running 8, could you take a look and see
> > what happens if you try to compile the fglrx drivers using the same
> > method?  I'll get to it later this week, but I'm anxious to know...
> >
> >
> > Thanks,
> >
> > Matt
> >
> >
> >
> >
> > On Wed, May 14, 2008 at 12:08 PM, Juan I Reyes
> > <juanig at ccrma.stanford.edu> wrote:
> > > Hi Matt,
> > >
> > > Sorry for getting so late to this post. I used your instructions for
> > > kmod-nvidia for a while, but on F8 I could not use them anymore (thanks
> > > a lot). I sent a post to PlanetCCRMA last February with the procedure I
> > > am using now:
> > >
> > >
> http://ccrma-mail.stanford.edu/pipermail/planetccrma/2008-February/014423.html
> > >
> > > Looks like Livna is using RPM Fusion in order to facilitate KMOD
> > > compilation in different Kernels.
> > >
> > > Once I have the KMOD SRPM,  All I have to do is to compile kmod-nvidia
> > > module for a ccrma rt kernel as:
> > >
> > > 'rpmbuild -ba --define "kernels $(uname -r)" --target i686 \
> > > nvidia-kmod.spec'
> > >
> > >  --* Juan
> > >
> > > On Fri, 2008-05-09 at 11:35 -0400, Matt Barber wrote:
> > >> By the way,
> > >>
> > >> After you install the kmod-nvidia package, you might have trouble with
> > >>  yum update   when there's a fedora kernel update, since it will try
> > >> to update to the new one rather than install the new one (I think this
> > >> causes a dependency conflict because kernels are installonly by
> > >> default in yum, but updating tries to take away the old kmod-nvidia
> > >> package - again, someone who knows yum better please advise).
> > >>
> > >> I am thinking you can fix this by adding "kmod-nvidia" to an
> > >> installonlypkgs line in yum.conf -- or if you don't want to do that,
> > >> if you get an error from   yum update   saying you have dependency
> > >> issues involving  kmod-nvidia  I have found success by running
> > >>
> > >> yum install kernel kmod-nvidia
> > >>
> > >> first before running yum update.
> > >>
> > >> Best,
> > >>
> > >> Matt
> > >
> > >
> > >
> >
>
>
>
> --
> Kind Regards,
>
>
> Paul Vallee
> pv.vallee at gmail.com
>
> .