Sound has been working fine till update of either Suse 13.2 or Firefox 2 weeks ago. Now no sound. I have 2 sound cards. When I test the primary card “0” there is no sound. When I test the 2nd card “1”, sound is fine. if I switch card 2 to primary, it has no sound, but the old primary (now secondary) card HAS sound. When I try to reload drivers from the yast sound module, they will not reload. Any suggestions??
Use pavucontrol to send the source to the output you want
Where do I get it?
It’s part of the official release, so you should be able to find using YaST or zypper
zypper in pavucontrol
Or you could use Yast Software Management to find and install it.
That’s what I meant when I mentioned YaST. 
When I run pavucontrol it gives “FATAL ERROR: Unable to connect to pulse audio” Any suggestions?
Is the pulseaudio daemon running?
ps -A|grep pulse
Which desktop environment are you using?
You may want to review this sound troubleshooting guide
https://en.opensuse.org/SDB:Audio_troubleshooting
In particular, running the (/usr/sbin/alsa-info.sh) diagnostic script might help identify where the problem lies.
I am suspicious that your PC sound card-1 and card-2 could both be using alsa’s intel sound driver - which is one explanation for what you observed.
If you can run in an xterm/konsole as a regular user, with your pc connected to the internet, and provide the output of :
/usr/sbin/alsa-info.sh
per the suggestion of deano_ferrari that would help. Select the share/upload option and then when the script completes, look in the xterm/konsole and it will provide you a web address to share (where that address has the output of the script execution).
With that information we may have more insight into your PCs sound problem.
.
linux-bolh:/home/matt # ps -Algrep pulse error: list of session leaders OR effective group IDs was invalid I am running KDE desktop
linux-bolh:/home/matt # ps -Algrep pulse error: list of session leaders OR effective group IDs was invalid I am running KDE desktop upload=true&script=true&cardinfo= │q │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ├────┴(+)────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────3%──────┤ │ < EXIT > └────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘ Your ALSA information is located at http://www.alsa-project.org/db/?f=91207d6871382f17c29a5540e511d9985fae2ad9 Please inform the person helping you. linux-bolh:/home/matt #
Also, this ia a new Dell Cire i3 computer that came with windows 8 installed. I have killed the windows installation and had sound in linux unti the fatal upgrade to linux. linux-bolh:/home/matt # ps -Algrep pulse error: list of session leaders OR effective group IDs was invalid I am running KDE desktop upload=true&script=true&cardinfo= │q │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ├────┴(+)────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────3%──────┤ │ < EXIT > └────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘ Your ALSA information is located at http://www.alsa-project.org/db/?f=91207d6871382f17c29a5540e511d9985fae2ad9 Please inform the person helping you. linux-bolh:/home/matt #
Your alsa diagnostic output confirms PA is not running
Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - No
While it is possible have sound configured without PulseAudio, it is not usual, especially in a desktop environment like KDE. Do you have PulseAudio installed?
rpm -qa|grep pulse
I also note the following dmesg output
1.335194] systemd[1]: Failed to start Load Kernel Modules.
While this may not have anything to do with your sound issue, it should probably be checked in its own right, as it may signal other issues which need attention
systemctl status systemd-modules-load.service
I’ll let others advise about your ALSA mixer levels or any other issues that may be impacting here.
The script makes it clear that wrt the alsa sound driver, your PC has two identical alsa sound modules loaded automoatically, one for each sound device:
!!Loaded ALSA modules
!!-------------------
snd_hda_intel
snd_hda_intel
associated with:
!!Soundcards recognised by ALSA
!!-----------------------------
**0 [HDMI [/b] ]: HDA-Intel - HDA Intel HDMI
HDA Intel HDMI at 0xf7e14000 irq 48
** 1 [PCH[/b] ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xf7e10000 irq 49
from which we can see that the HDMI device is card-0 and the analog PCH device is card-1.
Further information is here:
!!PCI Soundcards installed in the system
!!--------------------------------------
**00:03.0**** Audio device: Intel Corporation **Xeon E3-1200** v3/4th Gen Core Processor HD Audio Controller (rev 06)
**00:1b.0** Audio device: Intel Corporation 8 Series/**C220 Series Chipset High Definition Audio Controller** (rev 05)
!!Advanced information - PCI Vendor/Device/Subsystem ID's
!!-------------------------------------------------------
00:03.0 0403: **8086:0c0c** (rev 06)
Subsystem: 1028:0622
--
00:1b.0 0403: **8086:8c20** (rev 05)
Subsystem: 1028:0622
!!Aplay/Arecord output
!!--------------------
APLAY
**** List of PLAYBACK Hardware Devices ****
**card 0: HDMI** [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
**card 1: PCH [HDA Intel PCH], device 0**: ALC662 rev3 **Analog** [ALC662 rev3 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
From the above I am guessing that the 00:03.0 (Xeon E3) [with PCI 8086:0c0c] is the HDMI and 00:1b.0 (C220 series HDA controller) [with PCI 8086:8c20] is the ALC662 analog sound.
Nominally all applications by default receive sound from card-0, which means with your PC’s current configuration, if you are not using HDMI you will have no sound. Hence we want card-0 to be the C220 (8086:8c20) (ie the ALC662 analog sound).
Often in openSUSE a user can change the sound card order in YaST > Hardware > Sound but the YaST sound application does NOT work well for two devices that use the same sound module. And as we have seen your PC has two instances of the same sound module.
I propose instead you add an entry to your PC’s /etc/modprobe.d/50-sound.conf file to force the card order using the PCI card identification.
It would help if you could post the content of your PC’s /etc/modprobe.d/50-sound.conf file.
In that absence of that information, try this (but it may not work as I do not know what is inside your PC’s /etc/modprobe.d/50-sound.conf file) which is to add the following to the 1st two lines of your PC’s /etc/modprobe.d/50-sound.conf file:
options snd_hda_intel index=0 vid=8086 pid=8c20
options snd_hda_intel index=1 vid=8086 pid=0c0c
Then reboot and test. In the above tried to assign card-0 (index=0) to the PCI device 8c20 which is your analogue sound.
The above may not work because existing content in the 50-sound.conf file may interfer with it. In which case please post the content of your 50-sound.conf file and I will provide an edit on how to edit the entire file (and not just add a couple of lines).
Once we have this working do not go to YaST > Hardware > Sound as that application will overwrite the 50-sound.conf file edits.
Let us know how/if this works.**
Iran the command you gave and this is what I got linux-bolh:/home/matt # systemctl status systemd-module-load.service systemd-module-load.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead)
Follow oldcpu’s suggestions regarding sound resolution.
CONTENTS of /etc/modprobe.d/50-sound.conf options snd slots=snd-hda-intel,snd-hda-intel # 3hqH.+vGEJoXTPdA:Haswell HD Audio Controller alias snd-card-0 snd-hda-intel # u1Nb.ofYCuj9Hk8C:Lynx Point High Definition Audio Controller alias snd-card-1 snd-hda-intel
**
With respect to the module loading failure (captured in the diagnostic output), it would be prudent to start a new thread to investigate that further if desired. It is unlikely to be related to your sound issue.
Without the code tags - what you provided is almost IMPOSSIBLE to read. Look at your post and look at my reply (where I added the code tags) ! Please learn how to use the code tags … ie code ] some text /code] with the appropriate code tag before after. I had to insert spaces in my ‘code’ instruction so you could see it.
Back to your sound problem …
I took what you provided and guessed but I could have it wrong.
I recommend you simply replace the entire /etc/modprobe.d/50-sound.conf file with:
options snd_hda_intel index=0 vid=8086 pid=8c20
options snd_hda_intel index=1 vid=8086 pid=0c0c
reboot and test.