PulseAudio

Sat Feb 20 01:44:19 UTC 2010

Ah, okay, that makes sense.

I can't check into this any further right now, I'm so far behind here,
but I'm going to take a stab at it again on Monday. Thanks for the
tips and have a great weekend :)

On Fri, Feb 19, 2010 at 4:00 PM, Tyler Aviss <tjaviss-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org> wrote:
> Modern pulseaudio behavior is to run a "session" when you login to X.
>  /etc/X11/Xsession.d/70pulseaudio
>
> The /etc/init.d/ one doesn't do anything unless you do a bunch of
> reconfiguration to use system-wide pulse, which actually tends to
> cause more issues rather than less.
>
> To see if you're already got a pulse session, try:
>  pulseaudio --check && echo OK
>
> To kill one (although I think gnome respawns them)
>  pulseaudio -k
>
> It looks like ALSA did find your card, try "aplay -l" to list it from alsa.
>
>
> Another problem may be that though your card is intel-HDA compatible,
> there are actually a whole whackload of sub-models that your specific
> chipset might fall under. Check for funky entries under:
>  /etc/modprobe.d/alsa-base.conf
>  /etc/modprobe.d/snd-hda-intel.conf
>
> The second one will have model-specific info. If the model is wrong,
> your sound won't work. For example I have:
>  options snd-hda-intel model=m51va
>
> Other options can be:
>  options snd-hda-intel model=realtek
>  options snd-hda-intel model=m51va
>  options snd-hda-intel model=6stack
>  options snd-hda-intel model=3stack
>  options snd-hda-intel model=acer
>  etc etc
>
> You'd have to rmmod and them modprobe the driver (snd_hda_intel) to
> try new ones after editing the config, or stop/start ALSA, or reboot.
>
> I think the Nvidia one might be realtek based? I'd have to check my
> other machine which has an Nvidia chipset and get back to you on that
> for the params that worked on that one...
>
>
>
>
>
> On Fri, Feb 19, 2010 at 1:48 PM, Thomas Milne
> <tbrucemilne-TcoXwbchSccMMYnvST3LeUB+6BGkLq7r at public.gmane.org> wrote:
>> Sitting at the machine now. In the sound prefs (the speaker icon in
>> the panel) it does show the sound card and even will show what
>> application is using it and so on, but still no sound. I'm not sure
>> what to check to see if the correct 'profile' is being used, but
>> nothing appears to be muted anywhere.
>>
>> I'm not sure how to see if the daemon is running, it doesn't respond
>> the way I'm used to:
>>
>> scribe at scribe14:~$ sudo /etc/init.d/pulseaudio restart
>> [sudo] password for scribe:
>>  * PulseAudio configured for per-user sessions
>> scribe at scribe14:~$ pulseaudio
>> E: socket-server.c: bind(): Address already in use
>> E: module.c: Failed to load  module "module-esound-protocol-unix"
>> (argument: ""): initialization failed.
>> E: main.c: Module load failed.
>> E: main.c: Failed to initialize daemon.
>> scribe at scribe14:~$ pulse-session
>> E: main.c: Daemon startup failed.
>>
>> That could be because it's already running, though, no?
>>
>> There was no .asoundrc file to nuke.
>>
>> Thanks!
>>
>> On Wed, Feb 17, 2010 at 8:44 AM, Tyler Aviss <tjaviss-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org> wrote:
>>> I found a couple things when updating to karmic on various machines
>>> that could case this:
>>>  - Gnome/pulse found a different "default" soundcard than what they should have
>>>  - PA set the volume to nothing in the sound panel mixer, or turned on mute
>>>  - Wrong "profile" in the hardware settings of the sound prefs
>>>
>>> If you have a .asoundrc file in your homedir you may need to nuke that too
>>>
>>> Are you seeing your soundcard? Is the pulseaudio daemon loading?
>>>
>>> On Wed, Feb 17, 2010 at 8:23 AM, Thomas Milne
>>> <tbrucemilne-TcoXwbchSccMMYnvST3LeUB+6BGkLq7r at public.gmane.org> wrote:
>>>> Ha! So it finally got to me. So far on my home machine it's been no
>>>> problem, so I've been wondering why everyone hates Pulse so much.
>>>>
>>>> Until now. At work we upgraded all the machines to Karmic Koala and
>>>> now a lot of them have no sound. If you saw how we do our jobs, you
>>>> would understand what a horrifying thing this is ;)
>>>>
>>>> Anyhow, I remember some threads on here a while ago about fixing this
>>>> by using good 'ol OSS, but as these are work computers I thought I
>>>> would ask before I start trying some of the solutions. Is this really
>>>> the tried and true method?
>>>>
>>>> I also found this link. Anyone else solve it like this?
>>>>
>>>> http://swiss.ubuntuforums.org/showthread.php?t=1395089
>>>>
>>>> Thanks!
>>>>
>>>> --
>>>> TBM
>>>> --
>>>> The Toronto Linux Users Group.      Meetings: http://gtalug.org/
>>>> TLUG requests: Linux topics, No HTML, wrap text below 80 columns
>>>> How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists
>>>>
>>>
>>>
>>>
>>> --
>>> Tyler Aviss
>>> Systems Support
>>> LPIC/LPIC-2/CLA
>>>
>>> “Even enemies will help each other if they are together on a boat that
>>> is in trouble. ” – Sun Tzu
>>> --
>>> The Toronto Linux Users Group.      Meetings: http://gtalug.org/
>>> TLUG requests: Linux topics, No HTML, wrap text below 80 columns
>>> How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists
>>>
>>
>>
>>
>> --
>> TBM
>> --
>> The Toronto Linux Users Group.      Meetings: http://gtalug.org/
>> TLUG requests: Linux topics, No HTML, wrap text below 80 columns
>> How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists
>>
>
>
>
> --
> Tyler Aviss
> Systems Support
> LPIC/LPIC-2/CLA
>
> “Even enemies will help each other if they are together on a boat that
> is in trouble. ” – Sun Tzu
> --
> The Toronto Linux Users Group.      Meetings: http://gtalug.org/
> TLUG requests: Linux topics, No HTML, wrap text below 80 columns
> How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists
>

-- 
TBM
--
The Toronto Linux Users Group.      Meetings: http://gtalug.org/
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists