1. Introduction
Upgrading an operating system (OS) can bring new features, enhanced security, and better performance. However, it can also introduce unforeseen issues such as the disappearance of output sound devices when Ubuntu is upgraded.
Issues with sound output devices typically stem from driver incompatibilities, PulseAudio issues, ALSA problems, or even corrupt configuration files. This problem can be frustrating but can be resolved with a few troubleshooting steps.
In this tutorial, we’ll explore the possible causes and solutions for sound output issues in a post-upgrade Ubuntu environment.
2. Common Causes
Let’s look at some of the common causes of sound output device disappearance in Ubuntu.
2.1. Driver Incompatibility
When Ubuntu is upgraded, the kernel and system components are also updated. Occasionally, these updates may not be fully compatible with existing sound drivers leading to issues with sound output device recognition.
2.2. PulseAudio Issues
PulseAudio is the default sound server in many Linux distros, including Ubuntu. It acts as an intermediary between applications and the sound hardware. In addition, it provides advanced features like mixing multiple audio streams, adjusting volume levels, and audio routing.
After a system upgrade, PulseAudio might function incorrectly due to configuration changes or conflicts with new system settings.
2.3. ALSA Mixer Problems
ALSA (Advanced Linux Sound Architecture) is an important component of the Linux audio system. It works with PulseAudio to manage sound devices. Moreover, it provides kernel-driven sound card drivers and handles the low-level hardware interaction for sound cards.
In case ALSA isn’t working correctly, it can cause the sound output devices to disappear.
2.4. Configuration File Corruption
Configuration files related to sound settings can become corrupt during the upgrade process. As a result, it leads to issues with output sound device recognition.
2.5. Hardware Compatibility
Newer versions of Ubuntu may drop support for certain older hardware, causing issues with sound output devices.
3. Basic Troubleshooting Steps
Now, let’s look at some of the troubleshooting steps we can take to mitigate issues with the recognition of output sound devices on Ubuntu.
3.1. Checking Sound Settings
The first step in troubleshooting is to check the sound settings. We can achieve this by opening the Settings application and navigating to the Sound section.
We can ensure that the correct output device is selected and the volume isn’t too low or muted.
However, if the device isn’t listed or has no sound controls, we can proceed to the next steps.
3.2. Restart PulseAudio
Restarting the PulseAudio sound server can resolve many sound issues. To achieve this, we can open the terminal and then use the pulseaudio command to stop PulseAudio:
$ pulseaudio -k
Next, we start PulseAudio again:
$ pulseaudio --start
Finally, we can return to the Settings application and check whether the audio device is available.
3.3. Check ALSA Mixer Settings
If issues persist after restarting PulseAudio, we can adjust ALSA mixer settings to ensure the sound devices aren’t muted or set to an incorrect volume level.
Let’s open the terminal and enter the alsamixer command:
We can use the arrow keys to navigate and adjust volume levels for the audio devices and ensure that the channels are not muted MM but unmuted 00.
If we still can’t see the sound device listed, let’s try to reinstall ALSA and PulseAudio.
3.4. Reinstall ALSA and PulseAudio
Reinstalling ALSA and PulseAudio can help if there are issues with the installed packages.
To reinstall them, let’s start by purging each from the system:
$ sudo apt remove --purge alsa-base pulseaudio
Then, we can install both again:
$ sudo apt install alsa-base pulseaudio
Finally, we restart the system to effect the changes and then we can check the sound settings.
3.5. Check Driver Updates and System Logs
Of course, we can ensure we have the latest sound drivers installed.
To achieve this, let’s open the terminal and update the package list:
$ sudo apt update
Then, it’s good practice to upgrade all the packages including the drivers:
$ sudo apt upgrade
Next, we reboot the system and check the sound devices.
System logs can also provide clues about what might be causing the sound issues. In this case, let’s use the dmesg command to check the system logs:
$ dmesg | grep audio
[ 18.049872] sof-audio-pci-intel-cnl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100
[ 18.049925] sof-audio-pci-intel-cnl 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver
[ 18.049949] sof-audio-pci-intel-cnl 0000:00:1f.3: enabling device (0000 -> 0002)
...
Here, we can look for errors and warning messages related to audio devices and take appropriate action based on the log output.
4. Advanced Troubleshooting
If the problem persists even after basic troubleshooting steps, we can consider some advanced steps such as manually loading ALSA modules or rolling back the kernel version.
To manually load ALSA modules, let’s list the available sound modules:
$ lsmod | grep snd
snd_ctl_led 24576 0
snd_soc_skl_hda_dsp 28672 6
snd_soc_intel_hda_dsp_common 20480 1 snd_soc_skl_hda_dsp
snd_soc_hdac_hdmi 36864 1 snd_soc_skl_hda_dsp
...
Then, we can load the required module:
$ sudo modprobe snd-hda-intel
This command loads snd-hda-intel.
On the other hand, we can also consider rolling back to an earlier kernel version.
We can do this by rebooting the system and accessing the GRUB menu during boot. Next, we select advanced options for Ubuntu and choose an earlier kernel version to boot.
If the sound works with the older kernel, we may need to stay on that version or wait for a fix in future updates.
5. Conclusion
In this article, we looked at how to resolve sound issues after an Ubuntu system upgrade. They can be troublesome but are usually resolved with systematic troubleshooting.
Checking sound settings, restarting PulseAudio, adjusting ALSA mixer settings, and ensuring driver compatibility are some methods that can often restore the sound output devices.
If problems persist, more advanced steps like manually loading ALSA modules or rolling back the kernel version might be necessary. Notably, the Ubuntu community and forums are valuable resources for additional support and information in more specific environments and circumstances.