<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
Hello,<div><br></div><div>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 <a href="http://forums.fedoraforum.org/showthread.php?p=1383861">http://forums.fedoraforum.org/showthread.php?p=1383861</a> at post #14.</div><div><br></div><div>(thanks to jerboyd for these steps)</div><div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div class="smallfont" style="font: normal normal normal 11px/normal verdana, geneva, lucida, 'lucida grande', arial, helvetica, sans-serif; font-family: verdana, geneva, lucida, 'lucida grande', arial, helvetica, sans-serif; font-size: 11px; -webkit-border-horizontal-spacing: 1px; -webkit-border-vertical-spacing: 1px; "><strong>Re: Planet CCRMA RT Kernel with Nvidia akmod support</strong></div><hr size="1" style="color: rgb(209, 209, 225); background-color: rgb(209, 209, 225); font-family: verdana, geneva, lucida, 'lucida grande', arial, helvetica, sans-serif; font-size: 11px; -webkit-border-horizontal-spacing: 1px; -webkit-border-vertical-spacing: 1px; "><div id="post_message_1389203" style="font-family: verdana, geneva, lucida, 'lucida grande', arial, helvetica, sans-serif; font-size: 11px; -webkit-border-horizontal-spacing: 1px; -webkit-border-vertical-spacing: 1px; ">i figured out how to get nvidia going with the official nvidia binary. here goes.<br><br>1. download the latest driver for your card from nvidia<br>2. open a terminal and extract the files from the binary with 'sh NVIDIA(filename).bin -x'<br>3. cd into the extracted directory<br>4. place the attached patch into the root of the extracted directory<br>5. run 'patch -p1 < nvidia_33_rt.patch'<br>6. if it askes you which file to patch choose kernel/nv-linux.h<br>7. after this add rdblacklist=nouveau to your /boot/grub/grub.conf<br>8. reboot into init 3 <br>9. log in as root<br>10. cd to the root of the extracted nvidia binary directory and run './nvidia-installer'<br>11. reboot<br><br>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.</div><div style="padding-top: 6px; padding-right: 6px; padding-bottom: 6px; padding-left: 6px; font-family: verdana, geneva, lucida, 'lucida grande', arial, helvetica, sans-serif; font-size: 11px; -webkit-border-horizontal-spacing: 1px; -webkit-border-vertical-spacing: 1px; "><fieldset class="fieldset" style="margin-bottom: 6px; font-size: 11px; "><legend style="color: rgb(34, 34, 156); font: normal normal normal 11px/normal tahoma, verdana, geneva, lucida, 'lucida grande', arial, helvetica, sans-serif; ">Attached Files</legend><table cellpadding="0" cellspacing="3" border="0"><tbody><tr><td style="font: normal normal normal 11px/normal verdana, geneva, lucida, 'lucida grande', arial, helvetica, sans-serif; font-size: 11px; "><img class="inlineimg" src="http://forums.fedoraforum.org//forum/images/attach/patch.gif" alt="File Type: patch" width="16" height="16" border="0" title="File Type: patch" style="vertical-align: baseline; "></td><td style="font: normal normal normal 11px/normal verdana, geneva, lucida, 'lucida grande', arial, helvetica, sans-serif; font-size: 11px; "><a href="http://forums.fedoraforum.org/attachment.php?attachmentid=19943&d=1281382713" style="color: rgb(0, 0, 0); ">nvidia_33_rt.patch</a> (1.7 KB, 12 views)</td></tr></tbody></table></fieldset></div><div>take cares,</div><div><br></div><div>William Blackburn (tertl3)</div><div><br></div><br>> From: planetccrma-request@ccrma.Stanford.EDU<br>> Subject: PlanetCCRMA Digest, Vol 30, Issue 22<br>> To: planetccrma@ccrma.Stanford.EDU<br>> Date: Tue, 31 Aug 2010 12:00:01 -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: Installing Google Voice Chat for Linux on Fedora        instead<br>> of Debian (Niels Mayer)<br>> <br>> <br>> ----------------------------------------------------------------------<br>> <br>> Message: 1<br>> Date: Mon, 30 Aug 2010 16:07:48 -0700<br>> From: Niels Mayer <nielsmayer@gmail.com><br>> Subject: Re: [PlanetCCRMA] Installing Google Voice Chat for Linux on<br>>         Fedora        instead of Debian<br>> To: linux-audio-user <linux-audio-user@lists.linuxaudio.org>,<br>>         alsa-user@lists.sourceforge.net<br>> Cc: PlanetCCRMA mailinglist <planetccrma@ccrma.Stanford.EDU><br>> Message-ID:<br>>         <AANLkTin_+c3EskgzqPZXNZbQVBz_uZYCewyPu9PkXYY9@mail.gmail.com><br>> Content-Type: text/plain; charset=UTF-8<br>> <br>> Duh.... even better than wrappering the GoogleTalkPlugin for using a<br>> different device, you can just go to<br>> http://mail.google.com/mail/#settings/chat<br>> and look for "Voice and video chat:" settings.<br>> <br>> It'll say "Detecting devices..." for a while, especially if you're not<br>> using pulseaudio, in which case it will time out<br>> multiple times outputting 9 lines of<br>> socket(): Address family not supported by protocol<br>> socket(): Address family not supported by protocol<br>> ....<br>> <br>> But if you wait long enough, eventually you're given the same listing<br>> as "aplay -L" so you can choose the equivalent of<br>> "front:CARD=Headset,DEV=0" for both microphone and speakers (or even a<br>> different device for microphone if you've got a webcam with a built in<br>> usb mic). It's silly to use the "aplay -L" listing as you're given<br>> additional choices that make no sense for voice chatting:<br>> surround40:CARD=Headset,DEV=0 ; surround41:CARD=Headset,DEV=0 ;<br>> surround50:CARD=Headset,DEV=0 ; surround51:CARD=Headset,DEV=0 ;<br>> surround71:CARD=Headset,DEV=0 ; iec958:CARD=Headset,DEV=0 ...<br>> <br>> As final confusion, http://mail.google.com/mail/#settings/chat also<br>> lists "aplay -L" outputs for the microphone, so you end up seeing<br>> nonsense like "7.1 Surround output to Front, Center, Side, Rear and<br>> Woofer speakers" as a potential choice of microphone source.<br>> <br>> Fortunately it works with both "speaker" and microphone" set to the<br>> "front" source of the desired card.<br>> <br>> I never realized the gmail Settings->Chat options would do anything<br>> useful beyond saying ""Detecting devices..." forever, as I never<br>> thought of waiting till pulseaudio timed out 9 times before checking<br>> the web page... Thus the previous attempt at wrappering<br>> GoogleTalkPlugin ... at least it taught me their plugin is setting<br>> some interesting environment variables:<br>> LD_LIBRARY_PATH=/opt/google/chrome:/opt/google/chrome/lib:<br>> GNOME_DISABLE_CRASH_DIALOG=SET_BY_GOOGLE_CHROME<br>> SANDBOX_LD_LIBRARY_PATH=/opt/google/chrome:/opt/google/chrome/lib:<br>> CHROME_WRAPPER=/opt/google/chrome/google-chrome<br>> CHROME_VERSION_EXTRA=beta<br>> <br>> Niels<br>> http://nielsmayer.com<br>> <br>> PS: For those getting reports of echo on the caller end, there is a<br>> Settings->Chat option for echo-cancellation that appeared to be set by<br>> default. There's also a "send call quality info back to google" button<br>> that is also selected by default -- those worried about these kinds of<br>> things may want to change this option.<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 30, Issue 22<br>> *******************************************<br></div>                                            </body>
</html>