[PlanetCCRMA] PlanetCCRMA Digest, Vol 31, Issue 1

Wed Sep 1 12:57:52 PDT 2010

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