[pulseaudio-discuss] 2 sound devices, one mostly won't play, but works

Doug dmcgarrett at optonline.net
Tue Mar 29 12:50:45 PDT 2011

On 03/29/2011 04:23 AM, Patrick Shirkey wrote:
> On 03/29/2011 06:52 PM, Doug wrote:
>> On 03/29/2011 02:39 AM, Patrick Shirkey wrote:
>>> On 03/29/2011 04:53 PM, Doug wrote:
>>>> On 03/29/2011 01:26 AM, Doug wrote:
>>>> Here I am again: Now the top sliders control the volume on the 
>>>> bottom port.  I don't know shat I did.  I still can't get any sound 
>>>> out of the
>>>> speaker connected to the top port, but I can get the bonging noise 
>>>> on the headphones of the second port.  Actually, with all this
>>>> confusion, I really don't know which port is connected to what, 
>>>> since now the top port seems to be connected to the headphones,
>>>> Do you know if anyone using PCLOS has ever gotten this thing to work?
>>>> --doug
>>> You might want to try with alsamixer
>>> It may be that your settings have become confused.
>>> You can drop an .asoundrc file into your home folder for testing.
>>> You may also get somewhere with   "/etc/alsa/pulse-default.conf"
>>> Cheers.
>> All right.  I managed to get two sound sources running at the same 
>> time (thru one card) and couldn't stop the one, so I shut the machine
>> down (gracefully) and when I rebooted and loaded a radio station, it 
>> came out the MOBO device into the speakers.  I looked up
>> /usr/bin/alsamixer.gui and it seems to only know the MOBO device, and 
>> only the master has any effect on the volume.  The panel
>> volume control works again.  I conclude that PA is not working at all 
>> right now.  There is no file pulse-default.conf anywhere on the
>> machine.  All the alsa files in /usr/bin as one might expect, altho 
>> alsamixer.gui puts a drawing out with a zillion i/o keys. There is
>> no .asound* on the machine.
>> Unfortunately, I'm a retired hardware engineer, and I'm not all that 
>> good with software.  I sort of know how to find things on the machine,
>> and I know some _very basic_ bash programming, and I can edit files 
>> if I know what to put in them.  I was always told by the software
>> guys not to do it in hardware if it could be done in software, but if 
>> Radio Shack still had the parts, I would be building a switch about now.
>> There's DigiKey, of course. . . .
>> It's almost 4AM here.  I give up for the night.
> At least you are making progress :-)
> alsamixer -c0
> alsamixer -c1
> Will let you see the settings for each card at alsamixer level.
> It does sound like your system has something not quite right with it's 
> pulseaudio setup though.
> Can you tell us which version of pa you are using?
> pulseaudio --version
> Cheers.
Here's the output:
[doug@(none) ~]$ pulseaudio --version
pulseaudio 0.9.22-4pclos2010

PCLOS has all the latest updates as of a day or so ago. It's a rolling 
distro.  They tell
you not to install anything that doesn't come from their repo, but they 
will probably
put on an update for pa if it's needed.  That would most likely take a 
few days.

I haven't opened the pavctl since rebooting, and the system is still 
playing thru the
mobo (SiS) interface.

alsamixer -c0 shows the SiS device, and the volume level goes up and 
down with the
panel volume control.

alsamixer -c1 shows the Trident device, with nothing happening.

The f6 command on either screen is supposed to let you select the sound 
card; when I tell
it to use the Trident, it asks me for a card name, so I tried Trident 
and 4DWAVE-NX, but
that doesn't seem to be what it wants.  It defaults to hw:1, but that's 
not what it wants, either.
I think it wants some kind of driver file.  (Note that when I first 
opened this thread, the
system was actually playing thru the Trident card, apparently using pa.)

Thank you for your patience!  --doug


Blessed are the peacemakers...for they shall be shot at from both sides. --A. M. Greeley

More information about the pulseaudio-discuss mailing list