I'm using a Debian stable box with a Dell monitor and the Dell AX510 "stereo soundbar". The "soundbar" has a large frontal speaker as well as two headphone jacks on the left.

While the hardware itself is operational (I can hear static when I crank up the volume), I cannot make it produce any sound. I'm running KDE and have filled up the master bar through alsamixer.

The desktop itself also has a headphone jack on the desktop itself. I really do not mind using either the soundbar or that particular headphone jack; I'm just looking to have some sound output through either source. I'm going to be using headphones anyway since this is a work computer.

Audio-related lspci output:

jason@debian:~$ lspci | grep Audio                                                                                                                                                                                                                                             
01:00.1 Audio device: NVIDIA Corporation GF108 High Definition Audio Controller (rev a1) 

And some machine specs:

jason@debian:~$ uname -r
jason@debian:~$ cat /etc/debian_version                                                                                                                                                                                                                                        

I see that you have tagged your question with alsa and you have used alsamixer, so my question may sound silly, but are you sure you are not running pulseaudio?

Try ps aux | grep pulse. If you see a line with pulseaudio --start, then pulseaudio is running. In this case pavucontrol should allow you to figure out what is wrong.

  • Thanks for the comment. I checked the process log and, indeed, pulseaudio was running. I installed pavucontrol and opened up a YouTube video to produce some sound. I'm seeing the sound meter in the "Output Devices" tab of pavucontrol going up and down, indicating non-zero volume, yet I still have no sound through any one of my options. – Jason Nov 11 '15 at 8:59

Turns out this was a BIOS issue. Don't want to pollute the knowledge base with irrelevant details, but pulseaudio or alsa had nothing to do with it. Thank you all for your time.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.