Using the S.T.A.R.T. - SuSE Terminal Audio Reporting Tool bash script file, here are some sound setup outputs in openSUSE 11.4. I did manually add in the alsa-firmware file:
1 . Verify your Alsa Packages are installed for Operational Testing …
rpm --query --all --queryformat '%{NAME}-%{VERSION}-%{RELEASE}-%{ARCH} -> %{VENDOR}
’ alsa alsa-utils alsa-firmware ‘libasound2*’
alsa-firmware-1.0.23-3.7-noarch -> openSUSE
libasound2-1.0.23-10.2-x86_64 -> openSUSE
alsa-utils-1.0.23-10.2-x86_64 -> openSUSE
alsa-1.0.23-10.2-x86_64 -> openSUSE
libasound2-32bit-1.0.23-10.2-x86_64 -> openSUSE
You should expect to have at least four Alsa Packages Installed.
32 bit files are not required when using 64bit openSUSE install.
called ----> alsa-utils <--------- from the openSUSE Repository.
called ----> libasound2-32bit <— from the openSUSE Repository.
called ----> alsa <--------------- from the openSUSE Repository.
called ----> libasound2 <--------- from the openSUSE Repository.
called ----> alsa-firmware <------ from the openSUSE Repository.
Press <enter> to continue…
Here are the basic sound setups that I find in openSUSE 11.4:
5 . Checking your audio setup in four steps for detailed information …
Command: cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.23.
Command: cat /proc/asound/modules
0 snd_ctxfi
1 snd_hda_intel
Command: cat /proc/asound/cards
0 [XFi ]: SB-XFi - Creative X-Fi
Creative X-Fi 20K2 SB0880
1 [NVidia ]: HDA-Intel - HDA NVidia
HDA NVidia at 0xf8080000 irq 17
Command: cat /etc/modprobe.d/50-sound.conf
options snd slots=snd-ctxfi,snd-hda-intel
NXNs.Y0UpzuBS6C1:nVidia Corporation
alias snd-card-1 snd-hda-intel
svHJ.n6K5fZqwjGB:SB X-Fi Titanium PCI-e [SB0880]
alias snd-card-0 snd-ctxfi
If this does not provide the required info, then another approach to obtain more
information on your hardware and your sound configuration, is to run the ALSA script.
Press <enter> to continue…
So to reiterate about Pulseaudio, here are the pulse packages installed into openSUSE 11.4 M6 by default:
9 . Check your Pulseaudio package Installation …
Command: rpm --query --all --queryformat '%{NAME}-%{VERSION}-%{RELEASE}-%{ARCH} -> %{VENDOR}
’ ‘pulseaudio’
pulseaudio-module-lirc-0.9.22-4.1-x86_64 -> openSUSE
pulseaudio-esound-compat-0.9.22-4.1-x86_64 -> openSUSE
pulseaudio-module-x11-0.9.22-4.1-x86_64 -> openSUSE
pulseaudio-module-zeroconf-0.9.22-4.1-x86_64 -> openSUSE
pulseaudio-utils-0.9.22-4.1-x86_64 -> openSUSE
pulseaudio-0.9.22-4.1-x86_64 -> openSUSE
pulseaudio-module-gconf-0.9.22-4.1-x86_64 -> openSUSE
pulseaudio-module-jack-0.9.22-4.1-x86_64 -> openSUSE
pulseaudio-module-bluetooth-0.9.22-4.1-x86_64 -> openSUSE
You need the several programs (around 8) installed to use Pulse Audio from openSUSE
Press <enter> to continue…
Here is what is using the audio in openSUSE 11.4:
12. Determining which application is using sound device ...
Command: lsof /dev/dsp* /dev/audio* /dev/mixer* /dev/snd/*
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
pulseaudi 2366 james 26u CHR 116,17 0t0 9289 /dev/snd/controlC0
pulseaudi 2366 james 32u CHR 116,17 0t0 9289 /dev/snd/controlC0
Sometimes, when one has basic sound functioning, but then it appears to stop in
the middle of a session (to be restored after a reboot) it may be because an
application has seized your audio device, and the application is not sharing nor
letting go the audio device. To determine what application is using one's sound,
simply run this command from the S.T.A.R.T. script or use the CLI command above.
If one runs this command at different times, when one's sound is working and not
working, one can learn better as to what the output means, and be better able to
point one's finger at the offending application that has seized the audio device.
Press <enter> to continue...
So notice that pulse is using the outputs and is thusly enabled. I ran the Alsa setup script and generated this diagnostic output from my computer:
http://www.alsa-project.org/db/?f=1dbee254083dfc141bedb71c41153761e5dee277
One last thing I notice is that the mixer, called KMIX in KDE 4.6 looks like the old mixer that was called KMIX-PULSE. There is still a file called kmix-pulse, but it is version 4.4.4 which tells me it has not been updated for KDE 4.6 and may not be needed because the new KMIX is really kmix-pulse, but that is just speculation on my part.
Thank You,
