“Dummy Output” instead of audio device on Debian 9
up vote
7
down vote
favorite
OS: Debian 9
Kernel:
Linux version 4.9.0-6-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02)
After 6+ months using my laptop, I don't see any audio device anymore.
I noticed this yesterday. Now all my audio cards are HDMI somehow. I work with my laptop connected to an external monitor via HDMI. But I haven't had any problem with audio before.
trex@beast:~$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
PCI info
trex@beast:~$ lspci -nn | grep -i audio
00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21)
I see some codec error:
trex@beast:~$ sudo dmesg | grep -i error | grep -v "wifi|fs"
[ 28.220604] snd_hda_intel 0000:00:1f.3: Codec #0 probe error; disabling it...
I tried to restart snd-hda-intel and reconfigure pulseaudio, no success
sudo apt-get install --reinstall linux-image-`uname -r`
sudo modprobe snd-hda-intel
rm -r ~/.config/pulse*
pulseaudio -k
linux audio debian hdmi
edited Nov 16 at 22:56
Richard Fearn
24015
asked Apr 9 at 9:02
srgbnd
1385
add a comment |
up vote
7
down vote
favorite
OS: Debian 9
Kernel:
Linux version 4.9.0-6-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02)
After 6+ months using my laptop, I don't see any audio device anymore.
I noticed this yesterday. Now all my audio cards are HDMI somehow. I work with my laptop connected to an external monitor via HDMI. But I haven't had any problem with audio before.
trex@beast:~$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
PCI info
trex@beast:~$ lspci -nn | grep -i audio
00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21)
I see some codec error:
trex@beast:~$ sudo dmesg | grep -i error | grep -v "wifi|fs"
[ 28.220604] snd_hda_intel 0000:00:1f.3: Codec #0 probe error; disabling it...
I tried to restart snd-hda-intel and reconfigure pulseaudio, no success
sudo apt-get install --reinstall linux-image-`uname -r`
sudo modprobe snd-hda-intel
rm -r ~/.config/pulse*
pulseaudio -k
linux audio debian hdmi
edited Nov 16 at 22:56
Richard Fearn
24015
asked Apr 9 at 9:02
srgbnd
1385
A copule of hints: 1) try googling with that exactCodec #0 … disabling it...phrase (enclose it in double quotes), and look how people solved similar problems (e.g. this). 2) Try playing withmodelandprobe_maskoptions for the module — see this and this.
– kostix
Apr 9 at 10:08
Please consult your/var/log/apt/history.logand try to figure whether you had your kernel package updated (you might have the older logs archived as/var/log/apt/history.log.N.gz— you may use thezlesscommand to view them; search for the substringkernel-imageto look for the mentions of the kernel package(s) there). If you indeed had your kernel image package updated before the breakage, consider filing a bug as this might well indicate a regression.
– kostix
Apr 9 at 10:10
You might also try to roll the kernel image package back — by installing it viadpkg -i /path/to/the/kernel-image-package.deb, with the package taken from the APT cache, which is/var/cache/apt/archives/. If it works, the problem is confirmed.
– kostix
Apr 9 at 10:12
add a comment |
up vote
7
down vote
favorite
up vote
7
down vote
favorite
OS: Debian 9
Kernel:
Linux version 4.9.0-6-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02)
After 6+ months using my laptop, I don't see any audio device anymore.
I noticed this yesterday. Now all my audio cards are HDMI somehow. I work with my laptop connected to an external monitor via HDMI. But I haven't had any problem with audio before.
trex@beast:~$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
PCI info
trex@beast:~$ lspci -nn | grep -i audio
00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21)
I see some codec error:
trex@beast:~$ sudo dmesg | grep -i error | grep -v "wifi|fs"
[ 28.220604] snd_hda_intel 0000:00:1f.3: Codec #0 probe error; disabling it...
I tried to restart snd-hda-intel and reconfigure pulseaudio, no success
sudo apt-get install --reinstall linux-image-`uname -r`
sudo modprobe snd-hda-intel
rm -r ~/.config/pulse*
pulseaudio -k
linux audio debian hdmi
edited Nov 16 at 22:56
Richard Fearn
24015
asked Apr 9 at 9:02
srgbnd
1385
OS: Debian 9
Kernel:
Linux version 4.9.0-6-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02)
After 6+ months using my laptop, I don't see any audio device anymore.
I noticed this yesterday. Now all my audio cards are HDMI somehow. I work with my laptop connected to an external monitor via HDMI. But I haven't had any problem with audio before.
trex@beast:~$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
PCI info
trex@beast:~$ lspci -nn | grep -i audio
00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21)
I see some codec error:
trex@beast:~$ sudo dmesg | grep -i error | grep -v "wifi|fs"
[ 28.220604] snd_hda_intel 0000:00:1f.3: Codec #0 probe error; disabling it...
I tried to restart snd-hda-intel and reconfigure pulseaudio, no success
sudo apt-get install --reinstall linux-image-`uname -r`
sudo modprobe snd-hda-intel
rm -r ~/.config/pulse*
pulseaudio -k
linux audio debian hdmi
linux audio debian hdmi
edited Nov 16 at 22:56
Richard Fearn
24015
asked Apr 9 at 9:02
srgbnd
1385
edited Nov 16 at 22:56
Richard Fearn
24015
asked Apr 9 at 9:02
srgbnd
1385
edited Nov 16 at 22:56
Richard Fearn
24015
edited Nov 16 at 22:56
Richard Fearn
24015
edited Nov 16 at 22:56
Richard Fearn
24015
24015
asked Apr 9 at 9:02
srgbnd
1385
asked Apr 9 at 9:02
srgbnd
1385
asked Apr 9 at 9:02
srgbnd
1385
1385
A copule of hints: 1) try googling with that exactCodec #0 … disabling it...phrase (enclose it in double quotes), and look how people solved similar problems (e.g. this). 2) Try playing withmodelandprobe_maskoptions for the module — see this and this.
– kostix
Apr 9 at 10:08
Please consult your/var/log/apt/history.logand try to figure whether you had your kernel package updated (you might have the older logs archived as/var/log/apt/history.log.N.gz— you may use thezlesscommand to view them; search for the substringkernel-imageto look for the mentions of the kernel package(s) there). If you indeed had your kernel image package updated before the breakage, consider filing a bug as this might well indicate a regression.
– kostix
Apr 9 at 10:10
You might also try to roll the kernel image package back — by installing it viadpkg -i /path/to/the/kernel-image-package.deb, with the package taken from the APT cache, which is/var/cache/apt/archives/. If it works, the problem is confirmed.
– kostix
Apr 9 at 10:12
add a comment |
A copule of hints: 1) try googling with that exactCodec #0 … disabling it...phrase (enclose it in double quotes), and look how people solved similar problems (e.g. this). 2) Try playing withmodelandprobe_maskoptions for the module — see this and this.
– kostix
Apr 9 at 10:08
Please consult your/var/log/apt/history.logand try to figure whether you had your kernel package updated (you might have the older logs archived as/var/log/apt/history.log.N.gz— you may use thezlesscommand to view them; search for the substringkernel-imageto look for the mentions of the kernel package(s) there). If you indeed had your kernel image package updated before the breakage, consider filing a bug as this might well indicate a regression.
– kostix
Apr 9 at 10:10
You might also try to roll the kernel image package back — by installing it viadpkg -i /path/to/the/kernel-image-package.deb, with the package taken from the APT cache, which is/var/cache/apt/archives/. If it works, the problem is confirmed.
– kostix
Apr 9 at 10:12
A copule of hints: 1) try googling with that exact
Codec #0 … disabling it... phrase (enclose it in double quotes), and look how people solved similar problems (e.g. this). 2) Try playing with model and probe_mask options for the module — see this and this.– kostix
Apr 9 at 10:08
A copule of hints: 1) try googling with that exact
Codec #0 … disabling it... phrase (enclose it in double quotes), and look how people solved similar problems (e.g. this). 2) Try playing with model and probe_mask options for the module — see this and this.– kostix
Apr 9 at 10:08
Please consult your
/var/log/apt/history.log and try to figure whether you had your kernel package updated (you might have the older logs archived as /var/log/apt/history.log.N.gz — you may use the zless command to view them; search for the substring kernel-image to look for the mentions of the kernel package(s) there). If you indeed had your kernel image package updated before the breakage, consider filing a bug as this might well indicate a regression.– kostix
Apr 9 at 10:10
Please consult your
/var/log/apt/history.log and try to figure whether you had your kernel package updated (you might have the older logs archived as /var/log/apt/history.log.N.gz — you may use the zless command to view them; search for the substring kernel-image to look for the mentions of the kernel package(s) there). If you indeed had your kernel image package updated before the breakage, consider filing a bug as this might well indicate a regression.– kostix
Apr 9 at 10:10
You might also try to roll the kernel image package back — by installing it via
dpkg -i /path/to/the/kernel-image-package.deb, with the package taken from the APT cache, which is /var/cache/apt/archives/. If it works, the problem is confirmed.– kostix
Apr 9 at 10:12
You might also try to roll the kernel image package back — by installing it via
dpkg -i /path/to/the/kernel-image-package.deb, with the package taken from the APT cache, which is /var/cache/apt/archives/. If it works, the problem is confirmed.– kostix
Apr 9 at 10:12
add a comment |
1 Answer
1
active
oldest
votes
up vote
8
down vote
accepted
In my case the problem was caused by the fact that another service (namely, timidity, started at the system level) was using the sound card, so pulseaudio (started at the user level) was not using it.
To check this, you can do sudo fuser /dev/snd/* and see if another process is using the sound card. If yes, you should arrange for the process not to start, and this will fix the problem.
To give more details, I was able to isolate the problem by editing /etc/pulse/daemon.conf to set log-level = debug, restarting pulseaudio with pulseaudio -k (then pulseaudio is automatically respawned by systemd), and this is how I noticed the problem:
Aug 7 11:37:34 zeta pulseaudio[22178]: D: [pulseaudio] module-udev-detect.c: /devices/pci0000:00/0000:00:1f.3/sound/card0 is busy: yes
answered Aug 7 at 9:51
a3nm
373312
1
And for those who are as stupid as I am, be sure to check that the song you're playing as test doesn't start too softly for you to hear. This took me another 10 minutes after nuking timidity from my system. Anyway, thanks, this worked for me!
– Luc
Aug 10 at 1:09
Thanks! Tried all kinds of things after upgrading Ubuntu 18.04 to 18.10 and just getting "Dummy Output"... reinstalled alsa, removed~/.config/pulse, addedsnd-hda-inteloptions to/etc/modprobe.d/alsa-base.conf, added my user to theaudiogroup... but removingtimidityfinally fixed it.
– Richard Fearn
Nov 16 at 22:41
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
8
down vote
accepted
In my case the problem was caused by the fact that another service (namely, timidity, started at the system level) was using the sound card, so pulseaudio (started at the user level) was not using it.
To check this, you can do sudo fuser /dev/snd/* and see if another process is using the sound card. If yes, you should arrange for the process not to start, and this will fix the problem.
To give more details, I was able to isolate the problem by editing /etc/pulse/daemon.conf to set log-level = debug, restarting pulseaudio with pulseaudio -k (then pulseaudio is automatically respawned by systemd), and this is how I noticed the problem:
Aug 7 11:37:34 zeta pulseaudio[22178]: D: [pulseaudio] module-udev-detect.c: /devices/pci0000:00/0000:00:1f.3/sound/card0 is busy: yes
answered Aug 7 at 9:51
a3nm
373312
1
And for those who are as stupid as I am, be sure to check that the song you're playing as test doesn't start too softly for you to hear. This took me another 10 minutes after nuking timidity from my system. Anyway, thanks, this worked for me!
– Luc
Aug 10 at 1:09
Thanks! Tried all kinds of things after upgrading Ubuntu 18.04 to 18.10 and just getting "Dummy Output"... reinstalled alsa, removed~/.config/pulse, addedsnd-hda-inteloptions to/etc/modprobe.d/alsa-base.conf, added my user to theaudiogroup... but removingtimidityfinally fixed it.
– Richard Fearn
Nov 16 at 22:41
add a comment |
up vote
8
down vote
accepted
In my case the problem was caused by the fact that another service (namely, timidity, started at the system level) was using the sound card, so pulseaudio (started at the user level) was not using it.
To check this, you can do sudo fuser /dev/snd/* and see if another process is using the sound card. If yes, you should arrange for the process not to start, and this will fix the problem.
To give more details, I was able to isolate the problem by editing /etc/pulse/daemon.conf to set log-level = debug, restarting pulseaudio with pulseaudio -k (then pulseaudio is automatically respawned by systemd), and this is how I noticed the problem:
Aug 7 11:37:34 zeta pulseaudio[22178]: D: [pulseaudio] module-udev-detect.c: /devices/pci0000:00/0000:00:1f.3/sound/card0 is busy: yes
answered Aug 7 at 9:51
a3nm
373312
1
And for those who are as stupid as I am, be sure to check that the song you're playing as test doesn't start too softly for you to hear. This took me another 10 minutes after nuking timidity from my system. Anyway, thanks, this worked for me!
– Luc
Aug 10 at 1:09
Thanks! Tried all kinds of things after upgrading Ubuntu 18.04 to 18.10 and just getting "Dummy Output"... reinstalled alsa, removed~/.config/pulse, addedsnd-hda-inteloptions to/etc/modprobe.d/alsa-base.conf, added my user to theaudiogroup... but removingtimidityfinally fixed it.
– Richard Fearn
Nov 16 at 22:41
add a comment |
up vote
8
down vote
accepted
up vote
8
down vote
accepted
In my case the problem was caused by the fact that another service (namely, timidity, started at the system level) was using the sound card, so pulseaudio (started at the user level) was not using it.
To check this, you can do sudo fuser /dev/snd/* and see if another process is using the sound card. If yes, you should arrange for the process not to start, and this will fix the problem.
To give more details, I was able to isolate the problem by editing /etc/pulse/daemon.conf to set log-level = debug, restarting pulseaudio with pulseaudio -k (then pulseaudio is automatically respawned by systemd), and this is how I noticed the problem:
Aug 7 11:37:34 zeta pulseaudio[22178]: D: [pulseaudio] module-udev-detect.c: /devices/pci0000:00/0000:00:1f.3/sound/card0 is busy: yes
answered Aug 7 at 9:51
a3nm
373312
In my case the problem was caused by the fact that another service (namely, timidity, started at the system level) was using the sound card, so pulseaudio (started at the user level) was not using it.
To check this, you can do sudo fuser /dev/snd/* and see if another process is using the sound card. If yes, you should arrange for the process not to start, and this will fix the problem.
To give more details, I was able to isolate the problem by editing /etc/pulse/daemon.conf to set log-level = debug, restarting pulseaudio with pulseaudio -k (then pulseaudio is automatically respawned by systemd), and this is how I noticed the problem:
Aug 7 11:37:34 zeta pulseaudio[22178]: D: [pulseaudio] module-udev-detect.c: /devices/pci0000:00/0000:00:1f.3/sound/card0 is busy: yes
answered Aug 7 at 9:51
a3nm
373312
answered Aug 7 at 9:51
a3nm
373312
answered Aug 7 at 9:51
a3nm
373312
answered Aug 7 at 9:51
a3nm
373312
373312
1
And for those who are as stupid as I am, be sure to check that the song you're playing as test doesn't start too softly for you to hear. This took me another 10 minutes after nuking timidity from my system. Anyway, thanks, this worked for me!
– Luc
Aug 10 at 1:09
Thanks! Tried all kinds of things after upgrading Ubuntu 18.04 to 18.10 and just getting "Dummy Output"... reinstalled alsa, removed~/.config/pulse, addedsnd-hda-inteloptions to/etc/modprobe.d/alsa-base.conf, added my user to theaudiogroup... but removingtimidityfinally fixed it.
– Richard Fearn
Nov 16 at 22:41
add a comment |
1
And for those who are as stupid as I am, be sure to check that the song you're playing as test doesn't start too softly for you to hear. This took me another 10 minutes after nuking timidity from my system. Anyway, thanks, this worked for me!
– Luc
Aug 10 at 1:09
Thanks! Tried all kinds of things after upgrading Ubuntu 18.04 to 18.10 and just getting "Dummy Output"... reinstalled alsa, removed~/.config/pulse, addedsnd-hda-inteloptions to/etc/modprobe.d/alsa-base.conf, added my user to theaudiogroup... but removingtimidityfinally fixed it.
– Richard Fearn
Nov 16 at 22:41
1
1
And for those who are as stupid as I am, be sure to check that the song you're playing as test doesn't start too softly for you to hear. This took me another 10 minutes after nuking timidity from my system. Anyway, thanks, this worked for me!
– Luc
Aug 10 at 1:09
And for those who are as stupid as I am, be sure to check that the song you're playing as test doesn't start too softly for you to hear. This took me another 10 minutes after nuking timidity from my system. Anyway, thanks, this worked for me!
– Luc
Aug 10 at 1:09
Thanks! Tried all kinds of things after upgrading Ubuntu 18.04 to 18.10 and just getting "Dummy Output"... reinstalled alsa, removed
~/.config/pulse, added snd-hda-intel options to /etc/modprobe.d/alsa-base.conf, added my user to the audio group... but removing timidity finally fixed it.– Richard Fearn
Nov 16 at 22:41
Thanks! Tried all kinds of things after upgrading Ubuntu 18.04 to 18.10 and just getting "Dummy Output"... reinstalled alsa, removed
~/.config/pulse, added snd-hda-intel options to /etc/modprobe.d/alsa-base.conf, added my user to the audio group... but removing timidity finally fixed it.– Richard Fearn
Nov 16 at 22:41
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1312163%2fdummy-output-instead-of-audio-device-on-debian-9%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
A copule of hints: 1) try googling with that exact
Codec #0 … disabling it...phrase (enclose it in double quotes), and look how people solved similar problems (e.g. this). 2) Try playing withmodelandprobe_maskoptions for the module — see this and this.– kostix
Apr 9 at 10:08
Please consult your
/var/log/apt/history.logand try to figure whether you had your kernel package updated (you might have the older logs archived as/var/log/apt/history.log.N.gz— you may use thezlesscommand to view them; search for the substringkernel-imageto look for the mentions of the kernel package(s) there). If you indeed had your kernel image package updated before the breakage, consider filing a bug as this might well indicate a regression.– kostix
Apr 9 at 10:10
You might also try to roll the kernel image package back — by installing it via
dpkg -i /path/to/the/kernel-image-package.deb, with the package taken from the APT cache, which is/var/cache/apt/archives/. If it works, the problem is confirmed.– kostix
Apr 9 at 10:12