Persistent Dummy Output

Question

The soundcard I want to use is detected and works (it only recently switched to dummy output and didn't allow me to go back).

HDMI is no longer listed under Audio and Video - KDE Control Module; everything under audio module is set to dummy output and its the only 'soundcard' on the list now. I can view my previous sound cards in alsamixer, but changing the settings from there does nothing.

How can I get my real soundcards to work again?

I have already tried the following answers without success:

How do I get my sound working?

EDIT:

name@name-desktop:~$ lspci -vvv | grep -A8 Audio
00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri HDMI/DP Audio Controller
        Subsystem: ASRock Incorporation Kaveri HDMI/DP Audio Controller
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin B routed to IRQ 43
        Region 0: Memory at ff764000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: <access denied>
        Kernel driver in use: snd_hda_intel
        Kernel modules: snd_hda_intel
--
00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD] FCH Azalia Controller (rev 01)
        Subsystem: ASRock Incorporation FCH Azalia Controller
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 32, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 16
        Region 0: Memory at ff760000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: <access denied>
        Kernel driver in use: snd_hda_intel

Could this image possibly help?:

There is another soundcard but I'm unsure of what its for because it never outputs sound, but it does have a lot of settings: that sound card is labelled as "HD-Audio Generic".

So I went into Software & Updates under the Additional drivers tab and I see this:

It was on Do not use the device so I changed it and applied the settings but unfortunately the soundcard isn't back even after reboot.

Answer 1

I don't know what's the problem or why it happens, but that worked for me.

pulseaudio --kill
pulseaudio --start

Answer 2

First, replace any previous configurations:

sudo apt update
sudo rm -R /etc/pulse/*
sudo apt-get -o DPkg::Options::="--force-confmiss" --reinstall install pulseaudio

Then, run the following commands:

sudo apt-get install --reinstall linux-image-$(uname -r)
sudo modprobe snd-hda-intel
rm -r ~/.config/pulse*
pulseaudio -k

source

---

If alsa is somehow messed up, then running the following commands may fix the issue:

sudo apt update
sudo apt -o DPkg::Options::="--force-confmiss" --reinstall install libasound2 libasound2-data libasound2-dev libasound2-plugin-smixer libatopology-dev libatopology2 alsa-utils pulseaudio
rm -r ~/.config/pulse*
pulseaudio -k

Answer 3

There doesn't seem to be a solution to this so I just re-installed Kubuntu and the sound works perfect.

Downside: wiped everything else (but I didn't have much on my ssd so it was fine)

Answer 4

For those using the snd_hda_intel module

1. Check if you are using the snd_hda_intel kernel module:

   lsmod | grep snd_hda_intel
   lspci -nnk | grep -A2 Audio
   

2. If so, add two lines (you may need only the first line) to alsa-base.conf using the commands below.

   echo "options snd-hda-intel model=generic" | sudo tee -a /etc/modprobe.d/alsa-base.conf
   echo "options snd-hda-intel dmic_detect=0" | sudo tee -a /etc/modprobe.d/alsa-base.conf
   

NOTE: It was suggested to also add a third line but my system worked without me adding it. Add that using this command:

echo "blacklist snd_soc_skl" | sudo tee -a /etc/modprobe.d/blacklist.conf

REF: Fix No Sound (Dummy Output) Issue In Ubuntu With SND HDA Intel

Answer 5

For me, the problem was caused by one application that locked the sound device. In my case, it was mplayer, but it could be something else for you. To get a list of these applications, run:

# fuser -v /dev/snd/*
                     USER       PID ACCESS COMMAND
/dev/snd/controlC0:  ...      899378 F.... mplayer
/dev/snd/pcmC0D0p:   ...      899378 F...m mplayer
/dev/snd/timer:      ...      899378 f.... mplayer

After stopping that application, I forced a restart of pulseaudio:

/usr/bin/pulseaudio -k && sleep 1 && /usr/bin/pulseaudio --start

For more details, please check the Arch Wiki, where I found the trick:

The only device shown is "dummy output" or newly connected cards are not detected

If the only playback device is the Dummy Output, PulseAudio cannot access your sound devices. It is possible there is an issue with logind giving permissions, see General troubleshooting#Session permissions for more information.

An application might also not have been configured to work with PulseAudio. This happens with FluidSynth for example. To see which application is responsible for a direct access to the sound card via alsa, run the following command:

# fuser -v /dev/snd/*

Try to close these applications. pulseaudio, if running, should take again precedence over these applications and all the applications relying on pulseaudio should work again like expected.

Answer 6

In my case:

Settings > Multimedia > Audio Volume > Advanced and there switching around between 4.1 and Analog Stereo Output/Duplex

Sound is back...

Answer 7

If you only care about analog stereo, a very simple solution is to use a C-Media USB audio device. My built in audio card is just not detected. The problem may be with my motherboard because it used to work. If I wanted to use 5.1 I guess I could buy a card.

Answer 8

There can be many different causes of this problem, but I'll give an answer for my particular situation. I started experiencing this after upgrading to Ubuntu 20.04 from 18.04. The problem turned out to be permissions. My account was in the pulse-access group in /etc/group. For 18.04, this was sufficient. It appears that for Ubuntu 20.04 there was a change such that the account must now be in the pulse group instead.

Answer 9

I solved this on my E200 HA by putting the following lines in /etc/modprobe.d/alsa-base.conf

options snd-usb-audio index=-2
options snd-hda-intel mode="olpc-xo-1_5"

The first stopped the dummy output and got the soundcard recognised, but I had to put in the second line as sound was coming out of both speakers and headphones at the same time.

Answer 10

I had drivers errors on ALSA in the past, which disappeared after Focal Fossa upgrade. But when I upgraded to Jammy Jellyfish, I got this new bug of dummy output. What I found is that when I'm using LTS kernels, like versions 5.15, 6.6, and 6.12, the sound simply works.

Answer 11

Today - seemingly having the same problem - I did the following, using Synaptic package manager:

Reinstalled the following packages:

linux-sound-base (1.0.25+dfsg-0ubuntu5)
pulseaudio (1:8.0-0ubuntu3)

... and my card is back available.

Edit: problem came back after reboot!

Edit2: minimal (temporary) remedy is sudo dpkg-reconfigure pulseaudio

Answer 12

Go to Settings > Software & Updates > Additional Drivers. You will find a driver similar to audio: set it to Do not use this device. Then apply changes and restart.

Then system will use the inbuilt audio

If not working check whether it has changed by repeating the above.