Audio devices not being autodetected
up vote
0
down vote
favorite
Recently after my system updated packages, I restarted my computer and found that sound no longer works. aplay -l and pulseaudio both report that there are no sound devices, even though they were working fine previously.
I checked and found that the proper kernel modules were not loaded. Running sudo modprobe snd_hda_intel got my motherboard's sound device to immediately show up in pulseaudio, and sudo modprobe snd_usb_audio got my USB audio devices working as well.
I haven't edited any audio configuration files recently, but I'd like to get this working automatically so that Ubuntu will load the proper kernel modules at boot time after detecting my hardware.
Ubuntu 18.04.1 with Linux 4.15.0-39-generic
18.04 sound kernel pulseaudio alsa
asked Nov 7 at 1:20
erjiang
4951420
add a comment |
up vote
0
down vote
favorite
Recently after my system updated packages, I restarted my computer and found that sound no longer works. aplay -l and pulseaudio both report that there are no sound devices, even though they were working fine previously.
I checked and found that the proper kernel modules were not loaded. Running sudo modprobe snd_hda_intel got my motherboard's sound device to immediately show up in pulseaudio, and sudo modprobe snd_usb_audio got my USB audio devices working as well.
I haven't edited any audio configuration files recently, but I'd like to get this working automatically so that Ubuntu will load the proper kernel modules at boot time after detecting my hardware.
Ubuntu 18.04.1 with Linux 4.15.0-39-generic
18.04 sound kernel pulseaudio alsa
asked Nov 7 at 1:20
erjiang
4951420
Can you try to boot with the older kernel, to see if this is a regression for the 4.15.0-39-generic that you're running now?
– P.-H. Lin
Nov 7 at 3:04
Just tried with 4.15.0-38-generic and had the same issue.
– erjiang
Nov 9 at 22:19
Can you recall when did this happen? Or if you can see any snd_hda_intel related error messages on boot (in dmesg)? I would suggest you wait for the kernel update in maybe 2 days to see if it helps. You can open a bug report on launchpad later.
– P.-H. Lin
Nov 12 at 8:54
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Recently after my system updated packages, I restarted my computer and found that sound no longer works. aplay -l and pulseaudio both report that there are no sound devices, even though they were working fine previously.
I checked and found that the proper kernel modules were not loaded. Running sudo modprobe snd_hda_intel got my motherboard's sound device to immediately show up in pulseaudio, and sudo modprobe snd_usb_audio got my USB audio devices working as well.
I haven't edited any audio configuration files recently, but I'd like to get this working automatically so that Ubuntu will load the proper kernel modules at boot time after detecting my hardware.
Ubuntu 18.04.1 with Linux 4.15.0-39-generic
18.04 sound kernel pulseaudio alsa
asked Nov 7 at 1:20
erjiang
4951420
Recently after my system updated packages, I restarted my computer and found that sound no longer works. aplay -l and pulseaudio both report that there are no sound devices, even though they were working fine previously.
I checked and found that the proper kernel modules were not loaded. Running sudo modprobe snd_hda_intel got my motherboard's sound device to immediately show up in pulseaudio, and sudo modprobe snd_usb_audio got my USB audio devices working as well.
I haven't edited any audio configuration files recently, but I'd like to get this working automatically so that Ubuntu will load the proper kernel modules at boot time after detecting my hardware.
Ubuntu 18.04.1 with Linux 4.15.0-39-generic
18.04 sound kernel pulseaudio alsa
18.04 sound kernel pulseaudio alsa
asked Nov 7 at 1:20
erjiang
4951420
asked Nov 7 at 1:20
erjiang
4951420
asked Nov 7 at 1:20
erjiang
4951420
asked Nov 7 at 1:20
erjiang
4951420
asked Nov 7 at 1:20
erjiang
4951420
4951420
Can you try to boot with the older kernel, to see if this is a regression for the 4.15.0-39-generic that you're running now?
– P.-H. Lin
Nov 7 at 3:04
Just tried with 4.15.0-38-generic and had the same issue.
– erjiang
Nov 9 at 22:19
Can you recall when did this happen? Or if you can see any snd_hda_intel related error messages on boot (in dmesg)? I would suggest you wait for the kernel update in maybe 2 days to see if it helps. You can open a bug report on launchpad later.
– P.-H. Lin
Nov 12 at 8:54
add a comment |
Can you try to boot with the older kernel, to see if this is a regression for the 4.15.0-39-generic that you're running now?
– P.-H. Lin
Nov 7 at 3:04
Just tried with 4.15.0-38-generic and had the same issue.
– erjiang
Nov 9 at 22:19
Can you recall when did this happen? Or if you can see any snd_hda_intel related error messages on boot (in dmesg)? I would suggest you wait for the kernel update in maybe 2 days to see if it helps. You can open a bug report on launchpad later.
– P.-H. Lin
Nov 12 at 8:54
Can you try to boot with the older kernel, to see if this is a regression for the 4.15.0-39-generic that you're running now?
– P.-H. Lin
Nov 7 at 3:04
Can you try to boot with the older kernel, to see if this is a regression for the 4.15.0-39-generic that you're running now?
– P.-H. Lin
Nov 7 at 3:04
Just tried with 4.15.0-38-generic and had the same issue.
– erjiang
Nov 9 at 22:19
Just tried with 4.15.0-38-generic and had the same issue.
– erjiang
Nov 9 at 22:19
Can you recall when did this happen? Or if you can see any snd_hda_intel related error messages on boot (in dmesg)? I would suggest you wait for the kernel update in maybe 2 days to see if it helps. You can open a bug report on launchpad later.
– P.-H. Lin
Nov 12 at 8:54
Can you recall when did this happen? Or if you can see any snd_hda_intel related error messages on boot (in dmesg)? I would suggest you wait for the kernel update in maybe 2 days to see if it helps. You can open a bug report on launchpad later.
– P.-H. Lin
Nov 12 at 8:54
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2faskubuntu.com%2fquestions%2f1090653%2faudio-devices-not-being-autodetected%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
Can you try to boot with the older kernel, to see if this is a regression for the 4.15.0-39-generic that you're running now?
– P.-H. Lin
Nov 7 at 3:04
Just tried with 4.15.0-38-generic and had the same issue.
– erjiang
Nov 9 at 22:19
Can you recall when did this happen? Or if you can see any snd_hda_intel related error messages on boot (in dmesg)? I would suggest you wait for the kernel update in maybe 2 days to see if it helps. You can open a bug report on launchpad later.
– P.-H. Lin
Nov 12 at 8:54