Sound card works with ALSA, but not showing in volume mixer
up vote
0
down vote
favorite
After a system upgrade I noticed I had no sound. In the volume mixer I see that my integrated sound card is not shown, while another one (HDMI) is.
I managed to find that the device name is CARD=MID
using aplay -L
and I can indeed hear sound when I perform this:
$ for dev in `aplay -L | grep "CARD=MID"`; do aplay -D $dev /usr/share/sounds/alsa/Front_Right.wav 2> /dev/null && echo $dev; done
default:CARD=MID
sysdefault:CARD=MID
I can also hear sound with speaker-test
, without any arguments.
In alsamixer
the card is as well shown, it appears as the default one (HDA Intel MID
), and I can adjust the volume from there when I play sound with aplay
or speaker-test
.
In order to get the sound card work in the system, I stopped pulseaudio and removed the local configuration files at ~/.config/pulse/
, but nothing changed on restart.
I think that the system upgrade could have left some sound configuration in a broken state, but I don't know where to look into.
Edit:
I attach the output of lsof -n /dev/snd/*
in some situations.
With pulseaudio stopped:
$ lsof -n /dev/snd/*
$
with pulseaudio running:
$ lsof -n /dev/snd/*
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
pulseaudi 3463 etuardu 16u CHR 116,14 0t0 13058 /dev/snd/controlC1
pulseaudi 3463 etuardu 23u CHR 116,14 0t0 13058 /dev/snd/controlC1
$
while playing sound with speaker-test:
$ lsof -n /dev/snd/*
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
pulseaudi 3463 etuardu 16u CHR 116,14 0t0 13058 /dev/snd/controlC1
pulseaudi 3463 etuardu 23u CHR 116,14 0t0 13058 /dev/snd/controlC1
speaker-t 3481 etuardu mem CHR 116,2 13523 /dev/snd/pcmC0D0p
speaker-t 3481 etuardu 3r CHR 116,33 0t0 2850 /dev/snd/timer
speaker-t 3481 etuardu 4u CHR 116,2 0t0 13523 /dev/snd/pcmC0D0p
speaker-t 3481 etuardu 5u CHR 116,5 0t0 11209 /dev/snd/controlC0
$
linux debian sound-card alsa pulse-audio
|
show 5 more comments
up vote
0
down vote
favorite
After a system upgrade I noticed I had no sound. In the volume mixer I see that my integrated sound card is not shown, while another one (HDMI) is.
I managed to find that the device name is CARD=MID
using aplay -L
and I can indeed hear sound when I perform this:
$ for dev in `aplay -L | grep "CARD=MID"`; do aplay -D $dev /usr/share/sounds/alsa/Front_Right.wav 2> /dev/null && echo $dev; done
default:CARD=MID
sysdefault:CARD=MID
I can also hear sound with speaker-test
, without any arguments.
In alsamixer
the card is as well shown, it appears as the default one (HDA Intel MID
), and I can adjust the volume from there when I play sound with aplay
or speaker-test
.
In order to get the sound card work in the system, I stopped pulseaudio and removed the local configuration files at ~/.config/pulse/
, but nothing changed on restart.
I think that the system upgrade could have left some sound configuration in a broken state, but I don't know where to look into.
Edit:
I attach the output of lsof -n /dev/snd/*
in some situations.
With pulseaudio stopped:
$ lsof -n /dev/snd/*
$
with pulseaudio running:
$ lsof -n /dev/snd/*
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
pulseaudi 3463 etuardu 16u CHR 116,14 0t0 13058 /dev/snd/controlC1
pulseaudi 3463 etuardu 23u CHR 116,14 0t0 13058 /dev/snd/controlC1
$
while playing sound with speaker-test:
$ lsof -n /dev/snd/*
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
pulseaudi 3463 etuardu 16u CHR 116,14 0t0 13058 /dev/snd/controlC1
pulseaudi 3463 etuardu 23u CHR 116,14 0t0 13058 /dev/snd/controlC1
speaker-t 3481 etuardu mem CHR 116,2 13523 /dev/snd/pcmC0D0p
speaker-t 3481 etuardu 3r CHR 116,33 0t0 2850 /dev/snd/timer
speaker-t 3481 etuardu 4u CHR 116,2 0t0 13523 /dev/snd/pcmC0D0p
speaker-t 3481 etuardu 5u CHR 116,5 0t0 11209 /dev/snd/controlC0
$
linux debian sound-card alsa pulse-audio
"volume mixer" meansalsamixer
orpavucontrol
?
– Ipor Sircer
Nov 29 at 1:36
I meant the gui volume mixer of my desktop environment (gnome control center / audio). I installedpavucontrol
and the card is not shown there neither. On the other hand it is visible and working inalsamixer
.
– etuardu
Nov 29 at 2:03
Then it seems to be apulseaudio
bug, or some application take your soundcard when pulseaudio starts, so it cannot bind to it. Try restarting pulseaudio with-v -v -v
parameters to see what's going on. (update your question with this output)
– Ipor Sircer
Nov 29 at 2:15
This is the output ofpulseaudio -v -v -v
when started: pastebin.com/raw/jjCdB3iN
– etuardu
Nov 29 at 2:31
D: [pulseaudio] module-udev-detect.c: /devices/pci0000:00/0000:00:1b.0/sound/card0 is busy: yes
, so one app is already using your soundcard.
– Ipor Sircer
Nov 29 at 2:41
|
show 5 more comments
up vote
0
down vote
favorite
up vote
0
down vote
favorite
After a system upgrade I noticed I had no sound. In the volume mixer I see that my integrated sound card is not shown, while another one (HDMI) is.
I managed to find that the device name is CARD=MID
using aplay -L
and I can indeed hear sound when I perform this:
$ for dev in `aplay -L | grep "CARD=MID"`; do aplay -D $dev /usr/share/sounds/alsa/Front_Right.wav 2> /dev/null && echo $dev; done
default:CARD=MID
sysdefault:CARD=MID
I can also hear sound with speaker-test
, without any arguments.
In alsamixer
the card is as well shown, it appears as the default one (HDA Intel MID
), and I can adjust the volume from there when I play sound with aplay
or speaker-test
.
In order to get the sound card work in the system, I stopped pulseaudio and removed the local configuration files at ~/.config/pulse/
, but nothing changed on restart.
I think that the system upgrade could have left some sound configuration in a broken state, but I don't know where to look into.
Edit:
I attach the output of lsof -n /dev/snd/*
in some situations.
With pulseaudio stopped:
$ lsof -n /dev/snd/*
$
with pulseaudio running:
$ lsof -n /dev/snd/*
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
pulseaudi 3463 etuardu 16u CHR 116,14 0t0 13058 /dev/snd/controlC1
pulseaudi 3463 etuardu 23u CHR 116,14 0t0 13058 /dev/snd/controlC1
$
while playing sound with speaker-test:
$ lsof -n /dev/snd/*
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
pulseaudi 3463 etuardu 16u CHR 116,14 0t0 13058 /dev/snd/controlC1
pulseaudi 3463 etuardu 23u CHR 116,14 0t0 13058 /dev/snd/controlC1
speaker-t 3481 etuardu mem CHR 116,2 13523 /dev/snd/pcmC0D0p
speaker-t 3481 etuardu 3r CHR 116,33 0t0 2850 /dev/snd/timer
speaker-t 3481 etuardu 4u CHR 116,2 0t0 13523 /dev/snd/pcmC0D0p
speaker-t 3481 etuardu 5u CHR 116,5 0t0 11209 /dev/snd/controlC0
$
linux debian sound-card alsa pulse-audio
After a system upgrade I noticed I had no sound. In the volume mixer I see that my integrated sound card is not shown, while another one (HDMI) is.
I managed to find that the device name is CARD=MID
using aplay -L
and I can indeed hear sound when I perform this:
$ for dev in `aplay -L | grep "CARD=MID"`; do aplay -D $dev /usr/share/sounds/alsa/Front_Right.wav 2> /dev/null && echo $dev; done
default:CARD=MID
sysdefault:CARD=MID
I can also hear sound with speaker-test
, without any arguments.
In alsamixer
the card is as well shown, it appears as the default one (HDA Intel MID
), and I can adjust the volume from there when I play sound with aplay
or speaker-test
.
In order to get the sound card work in the system, I stopped pulseaudio and removed the local configuration files at ~/.config/pulse/
, but nothing changed on restart.
I think that the system upgrade could have left some sound configuration in a broken state, but I don't know where to look into.
Edit:
I attach the output of lsof -n /dev/snd/*
in some situations.
With pulseaudio stopped:
$ lsof -n /dev/snd/*
$
with pulseaudio running:
$ lsof -n /dev/snd/*
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
pulseaudi 3463 etuardu 16u CHR 116,14 0t0 13058 /dev/snd/controlC1
pulseaudi 3463 etuardu 23u CHR 116,14 0t0 13058 /dev/snd/controlC1
$
while playing sound with speaker-test:
$ lsof -n /dev/snd/*
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
pulseaudi 3463 etuardu 16u CHR 116,14 0t0 13058 /dev/snd/controlC1
pulseaudi 3463 etuardu 23u CHR 116,14 0t0 13058 /dev/snd/controlC1
speaker-t 3481 etuardu mem CHR 116,2 13523 /dev/snd/pcmC0D0p
speaker-t 3481 etuardu 3r CHR 116,33 0t0 2850 /dev/snd/timer
speaker-t 3481 etuardu 4u CHR 116,2 0t0 13523 /dev/snd/pcmC0D0p
speaker-t 3481 etuardu 5u CHR 116,5 0t0 11209 /dev/snd/controlC0
$
linux debian sound-card alsa pulse-audio
linux debian sound-card alsa pulse-audio
edited Nov 29 at 14:01
asked Nov 29 at 1:06
etuardu
3972619
3972619
"volume mixer" meansalsamixer
orpavucontrol
?
– Ipor Sircer
Nov 29 at 1:36
I meant the gui volume mixer of my desktop environment (gnome control center / audio). I installedpavucontrol
and the card is not shown there neither. On the other hand it is visible and working inalsamixer
.
– etuardu
Nov 29 at 2:03
Then it seems to be apulseaudio
bug, or some application take your soundcard when pulseaudio starts, so it cannot bind to it. Try restarting pulseaudio with-v -v -v
parameters to see what's going on. (update your question with this output)
– Ipor Sircer
Nov 29 at 2:15
This is the output ofpulseaudio -v -v -v
when started: pastebin.com/raw/jjCdB3iN
– etuardu
Nov 29 at 2:31
D: [pulseaudio] module-udev-detect.c: /devices/pci0000:00/0000:00:1b.0/sound/card0 is busy: yes
, so one app is already using your soundcard.
– Ipor Sircer
Nov 29 at 2:41
|
show 5 more comments
"volume mixer" meansalsamixer
orpavucontrol
?
– Ipor Sircer
Nov 29 at 1:36
I meant the gui volume mixer of my desktop environment (gnome control center / audio). I installedpavucontrol
and the card is not shown there neither. On the other hand it is visible and working inalsamixer
.
– etuardu
Nov 29 at 2:03
Then it seems to be apulseaudio
bug, or some application take your soundcard when pulseaudio starts, so it cannot bind to it. Try restarting pulseaudio with-v -v -v
parameters to see what's going on. (update your question with this output)
– Ipor Sircer
Nov 29 at 2:15
This is the output ofpulseaudio -v -v -v
when started: pastebin.com/raw/jjCdB3iN
– etuardu
Nov 29 at 2:31
D: [pulseaudio] module-udev-detect.c: /devices/pci0000:00/0000:00:1b.0/sound/card0 is busy: yes
, so one app is already using your soundcard.
– Ipor Sircer
Nov 29 at 2:41
"volume mixer" means
alsamixer
or pavucontrol
?– Ipor Sircer
Nov 29 at 1:36
"volume mixer" means
alsamixer
or pavucontrol
?– Ipor Sircer
Nov 29 at 1:36
I meant the gui volume mixer of my desktop environment (gnome control center / audio). I installed
pavucontrol
and the card is not shown there neither. On the other hand it is visible and working in alsamixer
.– etuardu
Nov 29 at 2:03
I meant the gui volume mixer of my desktop environment (gnome control center / audio). I installed
pavucontrol
and the card is not shown there neither. On the other hand it is visible and working in alsamixer
.– etuardu
Nov 29 at 2:03
Then it seems to be a
pulseaudio
bug, or some application take your soundcard when pulseaudio starts, so it cannot bind to it. Try restarting pulseaudio with -v -v -v
parameters to see what's going on. (update your question with this output)– Ipor Sircer
Nov 29 at 2:15
Then it seems to be a
pulseaudio
bug, or some application take your soundcard when pulseaudio starts, so it cannot bind to it. Try restarting pulseaudio with -v -v -v
parameters to see what's going on. (update your question with this output)– Ipor Sircer
Nov 29 at 2:15
This is the output of
pulseaudio -v -v -v
when started: pastebin.com/raw/jjCdB3iN– etuardu
Nov 29 at 2:31
This is the output of
pulseaudio -v -v -v
when started: pastebin.com/raw/jjCdB3iN– etuardu
Nov 29 at 2:31
D: [pulseaudio] module-udev-detect.c: /devices/pci0000:00/0000:00:1b.0/sound/card0 is busy: yes
, so one app is already using your soundcard.– Ipor Sircer
Nov 29 at 2:41
D: [pulseaudio] module-udev-detect.c: /devices/pci0000:00/0000:00:1b.0/sound/card0 is busy: yes
, so one app is already using your soundcard.– Ipor Sircer
Nov 29 at 2:41
|
show 5 more comments
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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%2f1379253%2fsound-card-works-with-alsa-but-not-showing-in-volume-mixer%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
"volume mixer" means
alsamixer
orpavucontrol
?– Ipor Sircer
Nov 29 at 1:36
I meant the gui volume mixer of my desktop environment (gnome control center / audio). I installed
pavucontrol
and the card is not shown there neither. On the other hand it is visible and working inalsamixer
.– etuardu
Nov 29 at 2:03
Then it seems to be a
pulseaudio
bug, or some application take your soundcard when pulseaudio starts, so it cannot bind to it. Try restarting pulseaudio with-v -v -v
parameters to see what's going on. (update your question with this output)– Ipor Sircer
Nov 29 at 2:15
This is the output of
pulseaudio -v -v -v
when started: pastebin.com/raw/jjCdB3iN– etuardu
Nov 29 at 2:31
D: [pulseaudio] module-udev-detect.c: /devices/pci0000:00/0000:00:1b.0/sound/card0 is busy: yes
, so one app is already using your soundcard.– Ipor Sircer
Nov 29 at 2:41