Bion | 23 Apr 10:09 2014
Picon

Re: NVIDIA and RT Kernel (Fedora 20)

Thank you for providing steps for successful configuration, Steve!


On Tue, Apr 22, 2014 at 9:21 PM, Steve Duell <steveduell <at> gmail.com> wrote:
Wow, guys - you did it!  Finally, after over 2 weeks, I've got an RT kernel working with the proprietary NVIDIA drivers.  Thanks to you, I can now have super low latency AND lots of windows open with no screen corruption.  Well done!

When I tried to do this on my own, I had to bounce back and forth between various sources, sometimes reading long threads and hunting down specific information in each one.  Now, in order to save fellow adventurers on this path from future headaches, I'd like to review the steps I took in one clean, step-by-step procedure:


1) Install Fedora

2) Make downloads more efficient by installing a plugin for yum:


yum install yum-plugin-fastestmirror
yum update

3) Add the RPM Fusion repositories so you can have access to necessary packages outside of official Fedora ones:

su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-$(rpm -E %fedora).noarch.rpm'

4) Make sure you have basic software development packages
installed so you can compile stuff: 

yum groupinstall "Development Tools"

5) Uninstall any other type of nvidia and/or noveau driver. Search theses terms in the package manager and remove any installed packages.

6) While still running stock kernel, install the most recent nvidia akmod:


sudo yum install akmod-nvidia.x86_64 xorg-x11-drv-nvidia-libs.x86_64

   (note: replace the x86_64 with i686 if you're running in 32bit.  You'll also need to install the xorg-x11-drv-nvidia-libs.i686 alongside x86_64 if you want to run 32bit opengl apps.)

7) Reboot and verify that the nvidia drivers work with the stock kernel.  It may take a while for it to finish booting, as the driver is compiled from the akmod at boot time. 
Possible troubleshooting:
The akmod installation scripts should disable noveau so if you run into problems, like a blank screen on startup, go to a virtual terminal by hitting CTRL+ALT+F2, login and do a "lsmod |grep noveau" (without the quotes) and see if there's a module called noveau and if there is you have to get rid of it.  If that command shows nothing than do a "lsmod | grep nvidia" and if that doesn't it means the nvidia module either didn't compile or is not loading.

8) Check to see if NVIDIA installed cleanly.  You should have access to 'Applications > Settings > Nvidia X Server Settings' from the application launcher.  Or, if you want to check in the terminal, you can:

lsmod |grep nvidia

which should output something like this:
nvidia               9665481  45
drm                   230882  4 nvidia
i2c_core               28502  2 drm,nvidia

9) Now, you can get ready to install the realtime kernel.  First, add the ccrma repositories:

rpm -Uvh http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/20/i386/planetccrma-repo-1.1-3.fc20.ccrma.noarch.rpm

note: the above command is only for Fedora 20. Commands to add repositories for other versions can be found at: http://ccrma.stanford.edu/planetccrma/software/installplanettwenty.html

10) Through the package manager, install "Planet CCRMA core packages (kernel and drivers)".  Take note, as it's installing, whether the kernel is PAE (physical address extension) or not, as you'll need to know for the next step.

11) Install either the kernel-rt-devel or kernel-rtPAE-devel package which matches the CCRMA kernel you just installed.

12) Reboot and give the system some extra time to compile the NVIDIA drivers.  After a while (about 3 minutes in my case), the system should finish booting and you'll have access to the Nvidia X Server Setings as described in step 8.

Done!

Good luck.


Thanks again for all the help in getting my install finished.  MUCH appreciated!

-Steve


On Tue, Apr 22, 2014 at 1:53 PM, Jeremy M Booth <bq20 <at> comcast.net> wrote:
Also, the kernel and kernel-devel packages installed have to match, so
if CCRMA installed kernel-rtPAE by default and you installed
kernel-rt-devel manually (which is for the non-PAE kernel), the akmod
won't compile.


On Tue, 22 Apr 2014 08:03:25 -0700
Steve Duell <steveduell <at> gmail.com> wrote:

> Jeremy,
>
> Thanks indeed for the detailed steps.  Here's how it went:
>
>
> 1. make sure you have basic software development packages
> installed so you can compile stuff
>
> (wasn't sure what I needed, so I just installed gcc c++ package)
>
> 2.  install the kernel-devel packages for stock kernel
>
> (no problem)
>
> 3. uninstall any other type of nvidia driver and/or noveau
>
> (I did this through the package manager - appeared to do the job)
>
> 4. install nvidia akmod while running stock kernel
>
> (check)
>
> 5. reboot and make sure akmod working first with stock kernel
>
> (Nvidia drivers built successfully & working great on the stock
> kernel.)
>
> 6. once it does then install the CCRMA stuff/realtime kernel but make
> sure you also install the kernel-rt-devel* BEFORE you reboot.
>
> (done)
>
> Upon rebooting into the CCRMA kernel, the bootloader animation made it
> almost to the end before the system started running through a
> checklist.  I saw in that list that it was attempting to build from a
> kmod package. Other entries appeared after that, and then the system
> hung on the message "starting Avahi DNS something...".  I waited 5
> minutes with no activity, then went to the virtual terminal and ran
> the grep commands.  They returned no nouveau or nvidia modules.  So I
> guess it's as you say - the nvidia drivers for this kernel didn't
> compile.
>
> I have some idea about why this may be:
>
> - Even though I attempted to install the regular i686 kernel package,
> I noticed that the package manager gave me a PAE version.  I don't
> think I need this, as I'm pretty sure I don't have 4 gigs of RAM. Is
> it possible to force the installation of the non-PAE version through
> the terminal?
>
> - Maybe there is another development package I need besides the gcc
> one?
>
> Anyway, thanks again for the help - you've helped me get farther
> along in the process than I've been able to so far on my own.  Much
> appreciated!
>
> -Steve
>
>
>
> On Mon, Apr 21, 2014 at 6:30 PM, Jeremy M Booth <bq20 <at> comcast.net>
> wrote:
>
> > If it helps to keep track of things to reinstall that's fine but
> > technically you shouldn't have to do that.  All the akmod is,
> > is the proprietary nvidia driver repackaged, so unless your machine
> > is over a decade old it shouldn't take more than 3 or 4 minutes.
> > Some akmods compile right after you install them so I guess just pay
> > attention to what's going on before you reboot as well. Also every
> > time you install a new kernel it will have to recompile itself,
> > which it does automatically. You need the kernel devel packages
> > first, because the akmod needs them to compile. Otherwise I'm not
> > sure whether it warns you about the dependencies or not.  I don't
> > see why any spin would hurt so long as it's still fedora.  So if
> > you're installing from scratch this is what I'd do:
> >
> > first to make downloads more efficient:
> >
> > yum install yum-plugin-fastestmirror
> > yum update
> >
> > 1. make sure you have basic software development packages
> > installed so you can compile stuff
> > 2.  install the kernel-devel packages for stock kernel
> > 3. uninstall any other type of nvidia driver and/or noveau
> > 4. install nvidia akmod while running stock kernel
> > 5. reboot and make sure akmod working first with stock kernel
> > 6. once it does then install the CCRMA stuff/realtime kernel but
> > make sure you also install the kernel-rt-devel* BEFORE you reboot
> >
> > Possible troubleshooting:
> > The akmod installation scripts should disable noveau so if you run
> > into problems, like a blank screen on startup, go to a virtual
> > terminal by hitting CTRL+ALT+F2, login and do a "lsmod |grep
> > noveau" (without the quotes) and see if there's a module called
> > noveau and if there is you have to get rid of it.  If that command
> > shows nothing than do a "lsmod | grep nvidia"
> > and if that doesn't it means the nvidia module either didn't compile
> > or is not loading.
> >
> > This setup definitely works though as I've been using the
> > fedora/ccrma/akmod combination for several releases now, but like
> > you said the information on the web is very spotty feel free to
> > report back with any problems.
> >
> > On Mon, 21 Apr 2014 16:41:51 -0700
> > Steve Duell <steveduell <at> gmail.com> wrote:
> >
> > > Thank, Jeremy!  I'll reinstall F20 from scratch and follow your
> > > steps. Just a few more questions:
> > >
> > >
> > > Should I install the akmod or the kernel-rt-devel package first?
> > > Or does it matter?  I gather that as long as they're both present
> > > at reboot, everything should come out fine.
> > >
> > > You mention a delay on first boot after installing the akmod.
> > > Can you estimate about how long it should take?  It's possible
> > > that the first time I tried this, I just gave up too soon.
> > >
> > > Also, is there any harm in using the CCRMA kernel with the Fedora
> > > Jam spin?  After weeks of trying to get various distros to play
> > > nice with my hardware, I'm to the point where I'd gladly accept
> > > one with most of the workhorse audio utilities pre-packaged for
> > > my convenience.
> > >
> > > Thanks again for the prompt reply.
> > >
> > > -Steve
> > >
> > >
> > > On Mon, Apr 21, 2014 at 11:21 AM, Jeremy M Booth
> > > <bq20 <at> comcast.net> wrote:
> > >
> > > > Also make sure you have the kernel-rt-devel* package installed
> > > > for the akmods to compile.
> > > >
> > > >
> > > >
> > > > On Sun, 20 Apr 2014 21:29:43 -0700
> > > > Steve Duell <steveduell <at> gmail.com> wrote:
> > > >
> > > > > Hey Folks,
> > > > >
> > > > > I'm new to linux, and have gone through several distributions
> > > > > over the last few weeks, looking for the right one.  I've
> > > > > tried and am very happy with Fedora 19 & 20 (both Xfce and
> > > > > LXDE editions). I've had no problems installing the RT
> > > > > kernel, but running the nouveau driver for graphics doesn't
> > > > > work well with my NVIDIA Geforce 8 chip. Once enough windows
> > > > > are open, or enough images load on a webpage, the display
> > > > > gets corrupted and I can't continue to use the computer
> > > > > without a reboot.
> > > > >
> > > > > I tried installing the proprietary drivers, which work fine
> > > > > on a stock kernel, but the CCRMA RT kernel will not boot
> > > > > after the nvidia drivers are installed.
> > > > >
> > > > > I've googled the issue pretty deeply, and I see lots of
> > > > > conflicting information about the exact steps to get the
> > > > > nvidia driver working with F20.  I'm hoping that one of the
> > > > > power-users on this list has already surmounted this issue
> > > > > and can walk a newbie through it, step-by-step.
> > > > >
> > > > > I'm perfectly happy to start all over with a clean install of
> > > > > fedora (any version) if it will make life easier for me or
> > > > > you.
> > > > >
> > > > > Thanks a ton,
> > > > >
> > > > > Steve
> > > >
> > > >
> >
> >



_______________________________________________
PlanetCCRMA mailing list
PlanetCCRMA <at> ccrma.stanford.edu
http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma


_______________________________________________
PlanetCCRMA mailing list
PlanetCCRMA <at> ccrma.stanford.edu
http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma
Steve Duell | 21 Apr 06:29 2014
Picon

NVIDIA and RT Kernel (Fedora 20)

Hey Folks,

I'm new to linux, and have gone through several distributions over the last few weeks, looking for the right one.  I've tried and am very happy with Fedora 19 & 20 (both Xfce and LXDE editions).  I've had no problems installing the RT kernel, but running the nouveau driver for graphics doesn't work well with my NVIDIA Geforce 8 chip.  Once enough windows are open, or enough images load on a webpage, the display gets corrupted and I can't continue to use the computer without a reboot.

I tried installing the proprietary drivers, which work fine on a stock kernel, but the CCRMA RT kernel will not boot after the nvidia drivers are installed.  

I've googled the issue pretty deeply, and I see lots of conflicting information about the exact steps to get the nvidia driver working with F20.  I'm hoping that one of the power-users on this list has already surmounted this issue and can walk a newbie through it, step-by-step.

I'm perfectly happy to start all over with a clean install of fedora (any version) if it will make life easier for me or you.

Thanks a ton,

Steve

  
_______________________________________________
PlanetCCRMA mailing list
PlanetCCRMA <at> ccrma.stanford.edu
http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma
Brian | 8 Apr 16:37 2014
Picon

Fedora Installation Help

Hi y'all,

Can anyone recommend a responsive and responsible forum for installation help?

I've been flailing with the Planet CCRMA since about Fedora 6, modprobing madly to get my
Audigy recognized and trying (mostly in vain) to mediate between PulseAudio and Alsa.
In my early days on a screaming 600 MHz machine I'd fire up Ardour and 45 minutes later
it would still be trying to draw the first screen.   Mostly I just use Audacity, Hydrogen, and
Zynaddsubfx in Windows--because they work.  Recently I actually briefly got Jack to work
In Fedora 19 with Hydrogen and Zynaddsubfx--a major breakthrough for me which was soon
wiped out when I played a Youtube and I guess the flashplayer reset the audio to some
configuration foreign to Jack.

So I rashly decided to upgrade to Fedora 20 and see if they've fixed some of this.  The Live
DVD just put multicolored snow on the screen.  So I tried a Yum update and it neglected to
bring in the keys.  And then though I'd get the Fedora ice cream cone I'd get no login screen
and no terminal.  After I learned to append a "3" to the vmlinuz line in the grub script I got
my terminal and yum seemed to be chugging along but after I tried to update grub I only get
grub rescue.  Using that I identified the location of the carcasses of my long-defunct Fedora
10 and Fedora 11 installations and found my Fedora 19 and 20 installations, but at this point
I need some hand-holding because I am very near but still so far away.

_______________________________________________
PlanetCCRMA mailing list
PlanetCCRMA <at> ccrma.stanford.edu
http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma
Thierry Coduys | 8 Apr 12:11 2014

LoMus 2014

Appel à contribution / Call for participation
Désolé en cas d’envois multiples / Sorry for possible crossposting

LoMus 2014

À la recherche des logiciels libres pour la création sonore et intermédias

Pour sa cinquième édition, LoMus 2014 s’adresse à tous ceux qui développent des logiciels libres musicaux ou qui peuvent contribuer au processus de la création musicale.

Un prix sera remis aux logiciels qui font preuve non seulement d’innovation, mais notamment d’inventivité face aux enjeux actuels de la création musicale.

Calendrier
31 mars 2014 - Appel à soumissions
28 avril 2014 - Date limite de soumission des logiciels
16 mai 2014 - Notification d'acceptation
23 mai 2014 - Remise du prix lors des JIM 2014


LoMus 2014

In search of open-source software for musical and intermedia creation

For its fifth edition, LoMus 2014 invites music and audio open-source software creators to submit original projects that either directly or indirectly contribute to musical creation.

A prize will be awarded to open-source sofware that proves to be not only innovatory but also inventive in the present context of music and audio creation.

Calendar
Mars 31, 2014 - Call for submissions 
April 28, 2014 - Submission deadline 
May 16, 2014 - Admission notification 
May 23, 2014 - JIM Awards Ceremony 2014
_______________________________________________
PlanetCCRMA mailing list
PlanetCCRMA <at> ccrma.stanford.edu
http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma
M. Edward (Ed) Borasky | 21 Mar 19:51 2014
Picon

Fwd: Grace only loads as root

Is your non-root user in the "jackuser" and "audio" groups? It needs
to be there to fire up 'jack'. Also, you may need to start up
'Qjackctl' before Grace.

On Fri, Mar 21, 2014 at 4:42 AM, Caio Barros <caio.barros <at> gmail.com> wrote:
> Hello everybody, new user of planetccrma repository here. (Thanks for the
> great work!)
>
> I installed common music and the cm-grace package but I noticed that I can
> only start Grace if I run it as root. If I run it as a regular user it just
> closes immediately without showing any gui. Is this normal behavior?
>
> If it is, than the problem is that Grace doesn't seems to see jack running
> (the opposite occurs with jack, i.e., i can only run it and load jack server
> successfully as a regular user).
>
> When running Grace as root I get the following error:
>
> Cannot connect to server socket err = No such file or directory
> Cannot connect to server request channel
> jack server is not running or cannot be started
>
> Thanks for the help!
>
> _______________________________________________
> PlanetCCRMA mailing list
> PlanetCCRMA <at> ccrma.stanford.edu
> http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma
>

--
Twitter: http://twitter.com/znmeb; Computational Journalism on a Stick
http://j.mp/CompJournoStickOverview

My poltergeist can beat up your zeitgeist.

--

-- 
Twitter: http://twitter.com/znmeb; Computational Journalism on a Stick
http://j.mp/CompJournoStickOverview

My poltergeist can beat up your zeitgeist.
Caio Barros | 21 Mar 12:42 2014
Picon

Grace only loads as root

Hello everybody, new user of planetccrma repository here. (Thanks for the great work!)

I installed common music and the cm-grace package but I noticed that I can only start Grace if I run it as root. If I run it as a regular user it just closes immediately without showing any gui. Is this normal behavior?

If it is, than the problem is that Grace doesn't seems to see jack running (the opposite occurs with jack, i.e., i can only run it and load jack server successfully as a regular user).

When running Grace as root I get the following error:

Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started

Thanks for the help!
_______________________________________________
PlanetCCRMA mailing list
PlanetCCRMA <at> ccrma.stanford.edu
http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma
Bion | 25 Feb 04:39 2014
Picon

cpufrequtils, kernel-tools problem on fedora 19

Hello list,

I am attempting to use the cpufrequtils set of programs (i.e. cpufreq-set, cpufreq-info, etc) and am having difficulty with the kernel-tools package I installed form planet ccrma. I'm using Fedora 19. After installing kernel-tools and kernel-tools-devel, cpufreq-set and the others are not getting found.

My installed kernel tools:

  kernel-tools.x86_640:3.10.25-200.rt23.1.fc19.ccrma                                                          

My uname -a:

Linux her-box 3.10.25-200.rt23.1.fc19.ccrma.x86_64.rt #1 SMP PREEMPT RT Fri Jan 10 12:09:13 PST 2014 x86_64 x86_64 x86_64 GNU/Linux

Reinstalling kernel-tools has not resolved this issue. Any help would be appreciated!

Cheers,
Bion
_______________________________________________
PlanetCCRMA mailing list
PlanetCCRMA <at> ccrma.stanford.edu
http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma
ycollette.nospam | 17 Feb 12:25 2014
Picon

miniAudicle and Chuck: no sound

Hello,

I meet a problem with miniAudicle on fedora 20 64 bits.
I installed Chuck and miniAudicle.
Then, I started jack vai qjackctl, then I started miniAudicle.
miniAudicle appears in the qjackctl connections pannel and is correctly connected.
When I start an example script from the chuck examples directory, no sounds are played.
If I start this example directly via chuck, chuck is again correctly wired in qjackctl and sounds are now
correctly emitted.

Do I miss something with miniAudicle ?

Best regards,

YC
agustin genoud | 15 Feb 18:35 2014
Picon

Stereo problem

Hi all!

i'm having troubles with my stereo output, the difference between the left and the right channel is almost imperceptible, it's not mono, but it's "almost mono". I'm running a fedora 19 planet ccrma, with a m-audio fast track ultra (this one).

I use pure data, but i tried with ardour an different software, the strange thing is that when i see the signal (i use QaRecord on the jack output, but i also have some audio meters on the master channel on pd) it is well balanced. I think this happens on the sound card, or maybe i have a trouble on the fedora sound setup. But i've tried without jack and with different audio servers and the result is the same. On the same computer i've tried with a different OS and the same algorithms on pd and the sound card responds normally,

any ideas?

best

agustin

--
don't let the tortuga run away from you

soundcloud / vimeo
_______________________________________________
PlanetCCRMA mailing list
PlanetCCRMA <at> ccrma.stanford.edu
http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma
pinux | 14 Feb 10:33 2014
Picon

rt kernel on fedora 20

Thank you very much for your nice work. the last kernel seems to work 
nicely, i'm obliged to you all.
  always work nicely thank again. till next. pino
Don Estabrook | 17 Jan 22:56 2014
Picon

Fedora 20 64-bit 3.12.5.-302.rt7.1

Hello -

Anyone out there have any experience with the latest CCRMA RT kernel on Fedora 20 ?  ie,

    3.12.5.-302.rt7.1.fc20.ccrma.x86_64+rt

installed with

    planetccrma-core-2013.12.19-1.fc20.ccrma.x86_64

On my HP Elitebook 8540w (Intel i7 <at> 2.67 GHz, 8 GiB RAM, nouveau nVidia driver), it works fine - I tested quickly with jack and Ardour, using the internal Intel HD sound card - but the computer freezes when I try to suspend, requiring a hard power-off to reboot.  I'm able to suspend and resume fine with the stock F20 kernel.

Not sure it's relevant, but it also throws kernel warnings with backtraces during boot-up, like these (from journalctl)

> kernel: WARNING: CPU: 2 PID: 858 at kernel/sched/core.c:2428 migrate_disable+0xed/0x100()

> kernel: WARNING: CPU: 2 PID: 858 at kernel/sched/core.c:2462 migrate_enable+0x17b/0x200()

> kernel: WARNING: CPU: 3 PID: 865 at kernel/sched/core.c:2428 migrate_disable+0xed/0x100()

some of which say the kernel is tainted (flags G W), while others say it isn't.  I don't seem to see those issues when I look at previous boots using the stock kernel.

I'd be happy to provide details, but first wanted to see if these are known issues...

Thanks!
Don
_______________________________________________
PlanetCCRMA mailing list
PlanetCCRMA <at> ccrma.stanford.edu
http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma

Gmane