<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
Juan and Geoff and everyone,<div><br></div><div>Thats great!. I never boot into the stock kernel now that I got the driver working on the CCRMA kernel. I also hope that rpm fusion would patch the driver for both kernels if that is even possible. However, some non-rt users can be quite hostile about real time kernels. I have noticed this in the #fedora and #fedora-social IRC channels. Anyways, I am glad there are some people(us) who have noticed a difference using the CCRMA kernel. If anyone is interested, I have started a wiki that could use some editing or additions. I am going to get it integrated soon. For now, it is located here <a href="https://fedoraproject.org/w/index.php?title=User:Tertl3/real-time">https://fedoraproject.org/w/index.php?title=User:Tertl3/real-time</a>. Its just a quick run through for using a cool script that checks for some additional real time config settings. Well, I have said too much.</div><div><br></div><div>Take Cares</div><div>-William </div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div><br>> From: planetccrma-request@ccrma.Stanford.EDU<br>> Subject: PlanetCCRMA Digest, Vol 31, Issue 1<br>> To: planetccrma@ccrma.Stanford.EDU<br>> Date: Wed, 1 Sep 2010 10:52:46 -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. Nvidia driver with the ccrma rt-kernel. (William Blackburn)<br>> 2. Re: Installing Google Voice Chat for Linux on Fedora instead<br>> of Debian (Niels Mayer)<br>> 3. Re: Nvidia driver with the ccrma rt-kernel. (Juan Reyes)<br>> 4. Re: Nvidia driver with the ccrma rt-kernel. (Geoff King)<br>> <br>> <br>> ----------------------------------------------------------------------<br>> <br>> Message: 1<br>> Date: Wed, 1 Sep 2010 01:00:04 +0100<br>> From: William Blackburn <bill_-@hotmail.com><br>> Subject: [PlanetCCRMA] Nvidia driver with the ccrma rt-kernel.<br>> To: <planetccrma@ccrma.Stanford.EDU><br>> Message-ID: <SNT133-w605BA56A608F5A5DB39E1AB68B0@phx.gbl><br>> Content-Type: text/plain; charset="iso-8859-1"<br>> <br>> <br>> Hello,<br>> 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.<br>> (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.<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.Attached Filesnvidia_33_rt.patch (1.7 KB, 12 views)take cares,<br>> William Blackburn (tertl3)<br>> <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>> <br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL: http://ccrma-mail.stanford.edu/pipermail/planetccrma/attachments/20100901/33f6243e/attachment-0001.html <br>> <br>> ------------------------------<br>> <br>> Message: 2<br>> Date: Tue, 31 Aug 2010 18:07:10 -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>> <AANLkTiknNS540tT5=rWkh5pcxfR8NaAX0Or=w-dAjtrX@mail.gmail.com><br>> Content-Type: text/plain; charset=UTF-8<br>> <br>> Now that I've discovered the way of setting hardware devices in<br>> http://mail.google.com/mail/#settings/chat , there's issues that limit<br>> my using GoogleTalkPlugin to "[Logitech USB Headset]" -- a USB headset<br>> that works well.<br>> <br>> However,<br>> <br>> (1) I have an old Hauppauge PVR-500 dual analog TV card and<br>> /opt/google/talkplugin/GoogleTalkPlugin thinks it's a video camera for<br>> chatting. However, the PVR-500 doesn't work w/ Google Talk, causing<br>> people to attempt to contact by video, but then failing due to this<br>> video device. (However, I could hook up an external old camcorder that<br>> outputs composite or svideo to the PVR500 and it would nicely hardware<br>> mpeg-encode the signal for me, however GoogleTalkPlugin doesn't seem<br>> to recognize any of the output formats.)<br>> <br>> There doesn't seem to be a way of telling it not to use a video camera<br>> because i don't have one on this computer.<br>> <br>> (2) Attempting to connect a variety of soundcards for input and<br>> output, I found that many, including motherboard soundcards and<br>> built-in snd-hda-intel hardware cannot talk to the GoogleTalkPlugin.<br>> The following errors are issued for output:<br>> <br>> (a) sample format mismatch (seen on Terratec DMX6Fire and M-Audio Delta 66).<br>> <br>> ALSA lib pcm.c:7320:(snd_pcm_set_params) Sample format not available<br>> for PLAYBACK: Invalid argument<br>> ALSA lib pcm.c:7320:(snd_pcm_set_params) Sample format not available<br>> for CAPTURE: Invalid argument<br>> <br>> (above occurs talking to an envy24/ice1712's analog capture or pcm<br>> outs. ... this error doesn't occur talking to the cards's 2-channels<br>> of spdif output, or capturing from the spdif input. For the output<br>> case, the spdif output can be sent to the card's built-in digital<br>> mixer, which can then be routed (via http://mudita24.googlecode.com or<br>> envy24control(1)) to the appropriate analog output for listening on<br>> headphones and works correctly with GoogleVoicePlugin...<br>> unfortunately, w/o a hardware spdif loopback this hack doesn't work<br>> for using the card's microphone input).<br>> <br>> (b) Channel count mismatch on Playback with totally standard output<br>> devices, both motherboard and USB:<br>> <br>> ALSA lib pcm.c:7326:(snd_pcm_set_params) Channels count (1) not<br>> available for PLAYBACK: Invalid argument<br>> <br>> (this seems to happen with some USB stereo soundcards and the<br>> motherboard via snd-hda-intel audio hardware, when connecting to<br>> "front" device.)<br>> <br>> Note that these audio issues would probably not occur if I was running<br>> pulseaudio, however, it is a mistake for Google to assume that<br>> everybody in Linuxland uses pulseaudio. (And even if pulseaudio were<br>> running, there'd be similar problems talking to multichannel<br>> soundcards such as the M-audio delta series).<br>> <br>> It sure would be nice to use the Terratec Dmx6Fire's handy microphone<br>> input with a sensitivity knob, overload-LED, etc, and built-in digital<br>> mixer, hardware-metering, and full control via<br>> http://mudita24.googlecode.com<br>> working properly, as it's nice being able to have proper microphone<br>> metering, and full mixer control for audio input/output... However,<br>> the current limitations seem to make that difficult.<br>> <br>> Perhaps my earlier "wrappering" approach and setting up a separate<br>> ALSA environment for google talk was the right way after all, at least<br>> for such "prosumer" soundcards. That way I could use plughw to match<br>> bit depths on PCM output; I'd have to figure out how to do that on<br>> input.<br>> <br>> How exactly could one work around<br>> "ALSA lib pcm.c:7320:(snd_pcm_set_params) Sample format not available<br>> for CAPTURE: Invalid argument"<br>> for capture inputs? Is there anything like plughw that works for capture too?<br>> <br>> -- Niels.<br>> http://nielsmayer.com<br>> <br>> <br>> <br>> ------------------------------<br>> <br>> Message: 3<br>> Date: Wed, 01 Sep 2010 12:05:47 -0400<br>> From: Juan Reyes <juanig@ccrma.Stanford.EDU><br>> Subject: Re: [PlanetCCRMA] Nvidia driver with the ccrma rt-kernel.<br>> To: William Blackburn <bill_-@hotmail.com><br>> Cc: planetccrma@ccrma.Stanford.EDU<br>> Message-ID: <1283357147.32194.14.camel@blueberry.maginvent.org><br>> Content-Type: text/plain; charset="ISO-8859-1"<br>> <br>> <br>> Thanks a lot William!.<br>> <br>> Got my PlanetCCRMA rt-Kernel on F-13 working this way using 'jerboyd'<br>> instructions.<br>> <br>> Maybe I am wrong, but the only problem is that if I want to work on the<br>> regular Fedora stock Kernels I have to re-install the NVidia binary<br>> which in turn de-installs the 'rt-Kernel' nvidia binary.<br>> <br>> AFAIK, 'akmods' and 'akmod-nvidia' from RMPFUSION work on the stock<br>> Fedora Kernels but they don't with PlanetCCRMA's rt-Kernel. Furthermore<br>> seems to me that both binaries cannot coexist on the same system.<br>> <br>> My hope is that RMPFUSION will be able to patch their 'akmod-nvidia'<br>> binary so that I will be able to use 'akmods', which are really<br>> convenient.<br>> <br>> --* Juan<br>> <br>> On Wed, 2010-09-01 at 01:00 +0100, William Blackburn wrote:<br>> > Hello,<br>> > <br>> > <br>> > As far as I know, it is quite common for a linux user to have an<br>> > nvidia GPU card. These cards are really neat. I was thinking that I<br>> > could make a Fedora "How-To" for installing the nvidia patch and<br>> > getting the driver working properly with the 2.6.33 rt kernel. These<br>> > are the instructions I used to get it working. It can be found here<br>> > http://forums.fedoraforum.org/showthread.php?p=1383861 at post #14.<br>> > <br>> <br>> <br>> <br>> <br>> <br>> ------------------------------<br>> <br>> Message: 4<br>> Date: Wed, 1 Sep 2010 13:52:42 -0400<br>> From: Geoff King <gsking1@gmail.com><br>> Subject: Re: [PlanetCCRMA] Nvidia driver with the ccrma rt-kernel.<br>> To: juanig@ccrma.Stanford.EDU<br>> Cc: William Blackburn <bill_-@hotmail.com>,<br>> planetccrma@ccrma.Stanford.EDU<br>> Message-ID:<br>> <AANLkTi=xWmJscNxHSEJUi-Ee7AkgnZT8AgYtTOCk6vfe@mail.gmail.com><br>> Content-Type: text/plain; charset=UTF-8<br>> <br>> Juan,<br>> You are right about having to re-install nvidia with every kernel switch.<br>> <br>> I have been using the FC13-rt kernel and the nvidia 256.xx driver for<br>> a few months now and it has worked great. I do notice warnings<br>> showing up in the system log "dmesg" when using VDPAU to accelerate<br>> video and some OpenGL stuff. For this reason, I have set media<br>> players like VLC and mplayer to not use VDPAU. I never had any real<br>> issues, just lots of kernel warnings, but thought wise to avoid that.<br>> <br>> Geoff<br>> <br>> On Wed, Sep 1, 2010 at 12:05 PM, Juan Reyes <juanig@ccrma.stanford.edu> wrote:<br>> ><br>> > Thanks a lot William!.<br>> ><br>> > Got my PlanetCCRMA rt-Kernel on F-13 working this way using 'jerboyd'<br>> > instructions.<br>> ><br>> > Maybe I am wrong, but the only problem is that if I want to work on the<br>> > regular Fedora stock Kernels I have to re-install the NVidia binary<br>> > which in turn de-installs the 'rt-Kernel' nvidia binary.<br>> ><br>> > AFAIK, 'akmods' and 'akmod-nvidia' from RMPFUSION work on the stock<br>> > Fedora Kernels but they don't with PlanetCCRMA's rt-Kernel. Furthermore<br>> > seems to me that both binaries cannot coexist on the same system.<br>> ><br>> > My hope is that RMPFUSION will be able to patch their 'akmod-nvidia'<br>> > binary so that I will be able to use 'akmods', which are really<br>> > convenient.<br>> ><br>> > ?--* Juan<br>> ><br>> > On Wed, 2010-09-01 at 01:00 +0100, William Blackburn wrote:<br>> >> Hello,<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 1<br>> ******************************************<br></div> </body>
</html>