[PlanetCCRMA] Nvidia driver with the ccrma rt-kernel.

Tue Aug 31 17:00:04 PDT 2010

Hello,
As far as I know, it is quite common for a linux user to have an nvidia GPU card.  These cards are really neat.  I was thinking that I could make a Fedora "How-To" for installing the nvidia patch and getting the driver working properly with the 2.6.33 rt kernel.  These are the instructions I used to get it working.  It can be found here  http://forums.fedoraforum.org/showthread.php?p=1383861 at post #14.
(thanks to jerboyd for these steps)Re: Planet CCRMA RT Kernel with Nvidia akmod supporti figured out how to get nvidia going with the official nvidia binary. here goes.

1. download the latest driver for your card from nvidia
2. open a terminal and extract the files from the binary with 'sh NVIDIA(filename).bin -x'
3. cd into the extracted directory
4. place the attached patch into the root of the extracted directory
5. run 'patch -p1 < nvidia_33_rt.patch'
6. if it askes you which file to patch choose kernel/nv-linux.h
7. after this add rdblacklist=nouveau to your /boot/grub/grub.conf
8. reboot into init 3 
9. log in as root
10. cd to the root of the extracted nvidia binary directory and run './nvidia-installer'
11. reboot

we could get this working with the akmod package but i don't know how to patch a source rpm. if anyone knows how to do that please let me know.Attached Filesnvidia_33_rt.patch (1.7 KB, 12 views)take cares,
William Blackburn (tertl3)

> From: planetccrma-request at ccrma.Stanford.EDU
> Subject: PlanetCCRMA Digest, Vol 30, Issue 22
> To: planetccrma at ccrma.Stanford.EDU
> Date: Tue, 31 Aug 2010 12:00:01 -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: Installing Google Voice Chat for Linux on Fedora	instead
>       of Debian (Niels Mayer)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Mon, 30 Aug 2010 16:07:48 -0700
> From: Niels Mayer <nielsmayer at gmail.com>
> Subject: Re: [PlanetCCRMA] Installing Google Voice Chat for Linux on
> 	Fedora	instead of Debian
> To: linux-audio-user <linux-audio-user at lists.linuxaudio.org>,
> 	alsa-user at lists.sourceforge.net
> Cc: PlanetCCRMA mailinglist <planetccrma at ccrma.Stanford.EDU>
> Message-ID:
> 	<AANLkTin_+c3EskgzqPZXNZbQVBz_uZYCewyPu9PkXYY9 at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
> 
> Duh.... even better than wrappering the GoogleTalkPlugin for using a
> different device, you can just go to
> http://mail.google.com/mail/#settings/chat
> and look for "Voice and video chat:" settings.
> 
> It'll say "Detecting devices..." for a while, especially if you're not
> using pulseaudio, in which case it will time out
> multiple times outputting 9 lines of
> socket(): Address family not supported by protocol
> socket(): Address family not supported by protocol
> ....
> 
> But if you wait long enough, eventually you're given the same listing
> as "aplay -L" so you can choose the equivalent of
> "front:CARD=Headset,DEV=0" for both microphone and speakers (or even a
> different device for microphone if you've got a webcam with a built in
> usb mic). It's silly to use the "aplay -L" listing as you're given
> additional choices that make no sense for voice chatting:
> surround40:CARD=Headset,DEV=0 ; surround41:CARD=Headset,DEV=0 ;
> surround50:CARD=Headset,DEV=0 ; surround51:CARD=Headset,DEV=0 ;
> surround71:CARD=Headset,DEV=0 ; iec958:CARD=Headset,DEV=0 ...
> 
> As final confusion, http://mail.google.com/mail/#settings/chat also
> lists "aplay -L" outputs for the microphone, so you end up seeing
> nonsense like "7.1 Surround output to Front, Center, Side, Rear and
> Woofer speakers" as a potential choice of microphone source.
> 
> Fortunately it works with both "speaker" and microphone" set to the
> "front" source of the desired card.
> 
> I never realized the gmail Settings->Chat options would do anything
> useful beyond saying ""Detecting devices..." forever, as I never
> thought of waiting till pulseaudio timed out 9 times before checking
> the web page... Thus the previous attempt at wrappering
> GoogleTalkPlugin ... at least it taught me their plugin is setting
> some interesting environment variables:
> LD_LIBRARY_PATH=/opt/google/chrome:/opt/google/chrome/lib:
> GNOME_DISABLE_CRASH_DIALOG=SET_BY_GOOGLE_CHROME
> SANDBOX_LD_LIBRARY_PATH=/opt/google/chrome:/opt/google/chrome/lib:
> CHROME_WRAPPER=/opt/google/chrome/google-chrome
> CHROME_VERSION_EXTRA=beta
> 
> Niels
> http://nielsmayer.com
> 
> PS: For those getting reports of echo on the caller end, there is a
> Settings->Chat option for echo-cancellation that appeared to be set by
> default. There's also a "send call quality info back to google" button
> that is also selected by default -- those worried about these kinds of
> things may want to change this option.
> 
> 
> 
> ------------------------------
> 
> _______________________________________________
> PlanetCCRMA mailing list
> PlanetCCRMA at ccrma.stanford.edu
> http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma
> 
> 
> End of PlanetCCRMA Digest, Vol 30, Issue 22
> *******************************************

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://ccrma-mail.stanford.edu/pipermail/planetccrma/attachments/20100901/33f6243e/attachment.html 