Audio device no longer automatically configured after 18.04 to 18:10 update
The chipset audio device is no longer automatically configured on reboot; it worked okay until update from 18.04 to 18.10. Forcing alsa to reload fixes it, but only until the next boot.
The device (as reported by lspci) is:
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05)
But the corresponding alsa device isn't created. After boot, pactl list | grep -A2 'Sink #' shows:
Sink #0
State: SUSPENDED
Name: auto_null
Forcing alsa to reload (with sudo alsa force-reload) makes the device appear and work normally - that same command now shows:
Sink #1
State: SUSPENDED
Name: alsa_output.pci-0000_00_1b.0.analog-stereo
The device is properly detected and configured if the system is booted of USB install media. So presumably the problem is some vestage of the 18.04 config that is messing up under 18.10.
I've purged alsa's config with:
sudo apt-get remove --purge alsa-base pulseaudio
sudo apt-get install alsa-base pulseaudio
Which didn't fix the problem.
I don't have a ~/.asoundrc
Some askubuntu answers on similar-sounding issues suggest editing /etc/default/speech-dispatcher, but that doesn't exist (and creating it with RUN=no doesn't help either.
Others suggest (re)installing the Intel chipset sound driver kernel module (with sudo modprobe snd-hda-intel) which also doesn't address the issue.
sound alsa 18.10
asked Jan 17 at 13:12
Finlay McWalterFinlay McWalter
101
New contributor
Finlay McWalter is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
The chipset audio device is no longer automatically configured on reboot; it worked okay until update from 18.04 to 18.10. Forcing alsa to reload fixes it, but only until the next boot.
The device (as reported by lspci) is:
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05)
But the corresponding alsa device isn't created. After boot, pactl list | grep -A2 'Sink #' shows:
Sink #0
State: SUSPENDED
Name: auto_null
Forcing alsa to reload (with sudo alsa force-reload) makes the device appear and work normally - that same command now shows:
Sink #1
State: SUSPENDED
Name: alsa_output.pci-0000_00_1b.0.analog-stereo
The device is properly detected and configured if the system is booted of USB install media. So presumably the problem is some vestage of the 18.04 config that is messing up under 18.10.
I've purged alsa's config with:
sudo apt-get remove --purge alsa-base pulseaudio
sudo apt-get install alsa-base pulseaudio
Which didn't fix the problem.
I don't have a ~/.asoundrc
Some askubuntu answers on similar-sounding issues suggest editing /etc/default/speech-dispatcher, but that doesn't exist (and creating it with RUN=no doesn't help either.
Others suggest (re)installing the Intel chipset sound driver kernel module (with sudo modprobe snd-hda-intel) which also doesn't address the issue.
sound alsa 18.10
asked Jan 17 at 13:12
Finlay McWalterFinlay McWalter
101
New contributor
Finlay McWalter is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
The chipset audio device is no longer automatically configured on reboot; it worked okay until update from 18.04 to 18.10. Forcing alsa to reload fixes it, but only until the next boot.
The device (as reported by lspci) is:
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05)
But the corresponding alsa device isn't created. After boot, pactl list | grep -A2 'Sink #' shows:
Sink #0
State: SUSPENDED
Name: auto_null
Forcing alsa to reload (with sudo alsa force-reload) makes the device appear and work normally - that same command now shows:
Sink #1
State: SUSPENDED
Name: alsa_output.pci-0000_00_1b.0.analog-stereo
The device is properly detected and configured if the system is booted of USB install media. So presumably the problem is some vestage of the 18.04 config that is messing up under 18.10.
I've purged alsa's config with:
sudo apt-get remove --purge alsa-base pulseaudio
sudo apt-get install alsa-base pulseaudio
Which didn't fix the problem.
I don't have a ~/.asoundrc
Some askubuntu answers on similar-sounding issues suggest editing /etc/default/speech-dispatcher, but that doesn't exist (and creating it with RUN=no doesn't help either.
Others suggest (re)installing the Intel chipset sound driver kernel module (with sudo modprobe snd-hda-intel) which also doesn't address the issue.
sound alsa 18.10
asked Jan 17 at 13:12
Finlay McWalterFinlay McWalter
101
New contributor
Finlay McWalter is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
The chipset audio device is no longer automatically configured on reboot; it worked okay until update from 18.04 to 18.10. Forcing alsa to reload fixes it, but only until the next boot.
The device (as reported by lspci) is:
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05)
But the corresponding alsa device isn't created. After boot, pactl list | grep -A2 'Sink #' shows:
Sink #0
State: SUSPENDED
Name: auto_null
Forcing alsa to reload (with sudo alsa force-reload) makes the device appear and work normally - that same command now shows:
Sink #1
State: SUSPENDED
Name: alsa_output.pci-0000_00_1b.0.analog-stereo
The device is properly detected and configured if the system is booted of USB install media. So presumably the problem is some vestage of the 18.04 config that is messing up under 18.10.
I've purged alsa's config with:
sudo apt-get remove --purge alsa-base pulseaudio
sudo apt-get install alsa-base pulseaudio
Which didn't fix the problem.
I don't have a ~/.asoundrc
Some askubuntu answers on similar-sounding issues suggest editing /etc/default/speech-dispatcher, but that doesn't exist (and creating it with RUN=no doesn't help either.
Others suggest (re)installing the Intel chipset sound driver kernel module (with sudo modprobe snd-hda-intel) which also doesn't address the issue.
sound alsa 18.10
sound alsa 18.10
asked Jan 17 at 13:12
Finlay McWalterFinlay McWalter
101
New contributor
Finlay McWalter is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Jan 17 at 13:12
Finlay McWalterFinlay McWalter
101
New contributor
Finlay McWalter is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Jan 17 at 13:12
Finlay McWalterFinlay McWalter
101
New contributor
Finlay McWalter is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Jan 17 at 13:12
Finlay McWalterFinlay McWalter
101
asked Jan 17 at 13:12
Finlay McWalterFinlay McWalter
101
101
New contributor
Finlay McWalter is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Finlay McWalter is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Finlay McWalter is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Finlay McWalter is a new contributor. Be nice, and check out our Code of Conduct.
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%2f1110548%2faudio-device-no-longer-automatically-configured-after-18-04-to-1810-update%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Finlay McWalter is a new contributor. Be nice, and check out our Code of Conduct.
Finlay McWalter is a new contributor. Be nice, and check out our Code of Conduct.
Finlay McWalter is a new contributor. Be nice, and check out our Code of Conduct.
Finlay McWalter is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f1110548%2faudio-device-no-longer-automatically-configured-after-18-04-to-1810-update%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
