systemwide low volume

sdf22, I do not have an audigy card. … But so many audigy card users have had trouble with their mixer, I can not help but think you need to look closer at your mixer settings. Now I note this from the amixer output that I asked you to run:

      Simple mixer control 'Audigy Analog/Digital Output Jack',0
        Capabilities: pswitch pswitch-joined
        Playback channels: Mono
        Mono: Playback [on]

      Simple mixer control 'External Amplifier',0
        Capabilities: pswitch pswitch-joined
        Playback channels: Mono
        Mono: Playback [off]

Are you deliberately using the SPDIF/Optical pass thru? If so, then OK. But if not, then should you not have Audigy Analog/Digital Output Jack equal OFF, and have External Amplifier equal ON ?

We need an audigy user to chime in here, as I can only speculate and wonder, not having your hardware.

I can test with more speakers, but my headphones are working fine… with my other pc-s…

External Amplifier, does nothing if i turn it on/off… if Audigy Analog/Digital Output Jack is off i can’t hear anything… i can only hear anything when Audigy Analog/Digital Output Jack is on.

Sorry lost in edit I agree changed my mind.

I would try another PCI slot did edit my post with similar.

Apologies for edit, after posting I thought the same.

I tried several soundcards with several pci slots… i’m really confused now…

Any errors in dmesg when you try to use it?

If I understand correctly the behaviour is the same regardless of distro, regardless of soundcard, regardless of PCI?

Certainly sounds unlikely to be software.

OK, then that means (I believe) that you are using SPDIF/Optical Passthru ? Which I think means digital audio ? Digital audio is also referred to as IEC958. Hence I am puzzled by this:

Simple mixer control ‘IEC958 Optical’,0
Capabilities: pvolume cvolume
Playback channels: Front Left - Front Right
Capture channels: Front Left - Front Right
Limits: Playback 0 - 100 Capture 0 - 100
Front Left: Playback 0 [0%] -99999.99dB] Capture 0 [0%] -99999.99dB]
Front Right: Playback 0 [0%] -99999.99dB] Capture 0 [0%] -99999.99dB]

Simple mixer control ‘IEC958 Optical Raw’,0
Capabilities: pswitch
Playback channels: Front Left - Front Right
Mono:
Front Left: Playback [off]
Front Right: Playback [off]
In addition to those, you also have several other controls to which (with my NOT having the hardware) I do not know what they do … such as Simple mixer control ‘Aux’,0 (at Capture 0 [0%] -34.50dB] [off] ) and Simple mixer control ‘Aux2’,0 (at Playback 0 [0%] -99999.99dB] Capture 0 [0%] ) Simple mixer control ‘Analog Mix’,0 (at Playback 0 [0%] -99999.99dB] Capture 0 [0%] ) .

Have you very carefully checked out if any of those could be causing muting?

My card only have insde spdif, my sound doesn’t go through spdif… When i slide the “potmeter” on my headphones, i can hear a little noise (when sliding it) when i slide it downwards its getting lower, and when i slide it back to max its getting louder, so it looks like the headphone got the strain…

Ok, can you also give a quality check of the rpms you have installed now? ie:
rpm -qa | grep alsa
rpm -qa | grep pulse
rpm -q libasound2
uname -a
cat /etc/modprobe.d/soundAnd post here the output.

Sometimes the script does not show everything I need .

Reference hardware, make certain you don’t have your connections backward to your PCs sound card. I know that sounds like a funny request, but inadvertently my maid has mistakenly broken the sound on my PCs a few times (knocking out the cables when vacuuming, and then putting them back in the wrong place), and I usually end up banging my head against the wall for some minutes before I figure that out (at some major cost to my ego). :slight_smile:

the output:
pastebin - collaborative debugging tool

that was the 2nd thing i tried, pulling out the jacks, and plugging back again, even pulled out my soundcard and put it back again.

Thanks. You still have not rolled back completely yet.
duke@linux-7tdg:/tmp> rpm -qa | grep alsa
alsa-1.0.18-8.9
** alsa-oss-32bit-1.0.17.git20080715-2.26**
alsa-utils-1.0.18-6.4
alsa-plugins-32bit-1.0.18-6.12
** alsa-oss-1.0.17.git20080715-2.26**
alsa-plugins-1.0.18-6.13
alsa-firmware-1.0.17-1.42
duke@linux-7tdg:/tmp> rpm -qa | grep pulse
libpulse0-0.9.12-9.5
duke@linux-7tdg:/tmp> rpm -q libasound2
libasound2-1.0.18-8.9Please try to do so. Then restart.

I note the latest kernel:
duke@linux-7tdg:/tmp> uname -a
Linux linux-7tdg 2.6.27.21-0.1-default #1 SMP 2009-03-31 14:50:44 +0200 x86_64 x86_64 x86_64 GNU/Linux
Its possible that kernel simply breaks your sound and you have to:
a. wait until the 1.0.19 alsa comes out for that kernel, and/or
b. write a bug report on the new kernel compatibility with your hardware

Are you going to show him how to use dmesg? Or just leave him hanging with this suggestion?

Edit - rather than wait … sdf22 take a look here:
http://www.linfo.org/dmesg.html

here it goes:
duke@linux-7tdg:/tmp> dmesg | grep sound
ALSA sound/pci/emu10k1/emu10k1_main.c:219: Audigy2 value: Special config.

You both seem to be going down the software route I’ll step out, seems pointless and confusing to investigate both angles at the same time.

IMO it isn’t, it doesn’t work with different soundcards either or distros.

dmesg may be showing something related to pci’s or such like rather than just sound. From the sounds of things the only common thing is the MB.

Unfortunately IMHO the advice to “use dmesg” was less than helpful. I learned that the hard way by suggesting that many times users look at dmesg, and then users did NOT have a clue as to what I was talking about, nor as to what they should look for. So I eventually learned reference giving that advice. Now adays, I typically look for occurences of “sound”, “snd”, “hda”, “alsa” in the dmesg.

How about posting the output so we can look at it? The EASY way to do that which I also recommend is to copy and paste this (with your PC connected to the internet):
dmesg > dmesg.txt && curl -F file=@dmesg.txt nopaste.com/a
then post here the URL. Just the URL.

duke@linux-7tdg:/tmp> rpm -qa | grep alsa
alsa-1.0.18-8.9
alsa-utils-1.0.18-6.4
alsa-plugins-32bit-1.0.18-6.12
alsa-oss-32bit-1.0.17-1.37

alsa-plugins-1.0.18-6.13
alsa-oss-1.0.17-1.43
alsa-firmware-1.0.17-1.42
duke@linux-7tdg:/tmp> rpm -qa | grep pulse
libpulse0-0.9.12-9.5
duke@linux-7tdg:/tmp> rpm -q libasound2
libasound2-1.0.18-8.9
duke@linux-7tdg:/tmp> uname -a
Linux linux-7tdg 2.6.27.21-0.1-default #1 SMP 2009-03-31 14:50:44 +0200 x86_64 x86_64 x86_64 GNU/Linux
duke@linux-7tdg:/tmp> cat /etc/modprobe.d/sound

options snd slots=snd-emu10k1

Ikk3.up6Wra2JIU9:SB0400 Audigy2 Value

alias snd-card-0 snd-emu10k1

Alsa should be ok now… but i don’t think its a problem with packages.

What sound test are you using to determine LOW VOLUME ?

Are you using the recommended speaker tests ?
SDB:AudioTroubleshooting - openSUSE - how to test your sound

speaker-test -Dplug:front -c2 -l5 -twav
speaker-test -c2 -l5 -twav

Theese didn’t give me any sound i can hear…
then i tried with amarok and i can hear something low volume with it.

That makes me think you are picking up cross talk, … suggesting cables connected wrong, or something mistakenly muted in your mixer.

Can you reboot to another OS to test your sound and do a sanity check on your hardware?

Did you copy and paste the curl/dmesg command I suggested?

Of course, i copy pasted what u wrote in your post(dmesg > dmesg.txt && curl -F file=@dmesg.txt nopaste.com/a) i run that command again here is the new result: dmesg.txt - nopaste.com (beta)

I tried my system already with other distro livecds… ubuntu, xubuntu… none of them had working sound.