Final update (hopefully): It seems that I have been able to fix the issue. I’m not sure what exactly caused the problem but either removing fluidsynth or installing the wireplumber ppa fixed the issue and I have working audio again. I’ve also removed pulseaudio and undid my edit to the modprobe blacklist, as they were only done as a temporary solution and they are no longer necessary.
For the past three days, I’ve been having this issue where my computer starts with no audio and the only sound device listed is a “dummy output” device. I’ve tried looking online for solution but the only solution I found has to be redone manually every time I start/restart my computer. It also seems like this issue is common with and possibly specific to the sound card my computer has, which is an “Intel Sunrise Point-LP HD Audio”.
The solution that worked for me was to add blacklist snd_soc_avs
to the modprobe blacklist and then run the two commands sudo alsa force-reload
and pulseaudio
. Adding snd_soc_avs to the blacklist permanently brought back my actually audio devices but it didn’t fix the audio nor did it remove the dummy output device. The two commands I listed do restore the audio and remove the dummy output device but they only work for the current session and I have to run them again after starting/restarting my computer.
I have no problem doing this if there isn’t a permanent solution but I would like a permanent solution, if possible.
I’m not sure how long everything takes normally but systemd-udev-settle.service took over two minutes. When running it with --user the longest was xdg-desktop-portal.service, which took 6 seconds. The third command gives:
UNIT LOAD ACTIVE SUB DESCRIPTION ● casper-md5check.service loaded failed failed casper-md5check Verify Live ISO checksums ● systemd-udev-settle.service loaded failed failed Wait for udev To Complete Device Initialization ● vboxdrv.service loaded failed failed VirtualBox Linux kernel module
Also, no I did check and fluidsynth was the only thing removed. I think it did for some reason add some of Wine’s dependencies to autoremove but I’ll deal with those later.Yeah not sure about that. My guess is the casper-md5check is irrelevant, not sure why udev would be affected by installing/uninstalling audio stuff, and also not sure if that actually slows down your boot, my guess would be no. vboxdrv and virtualbox are probably also irrelevant.
I think I should have included
systemctl --user list-units --failed
previously.Ok and that command doesn’t list anything.