On Sun, 10 Nov 2019 17:37:13 -0000 Cătălin George Feștilă <mythcat(a)fedoraproject.org&gt; wrote: Two things. Is there any message from alsa during boot? Look in journalctl -b to see the last boot. Run the script you find here, https://gist.github.com/craftyjon/902247 and run it as bash alsa-info.sh Paste the output somewhere, and provide a link here to the output. I think it is too large to send as an attachment, but maybe not. If alsa doesn't find your devices, you will have no sound, because it is the basis for all sound in linux. It is usually very good about finding devices, so there is something interfering.

alsa-info.sh http://alsa-project.org/db/?f=57ea2d275137a9b2de34641a84df5cd4c2f10c66 journalctl -b https://paste.centos.org/view/97ca9d38#L78

On Mon, 11 Nov 2019 19:44:39 -0000 Cătălin George Feștilă <mythcat(a)fedoraproject.org&gt; wrote: Neither of these are complete. The part of the journal dealing with sound device activation isn't there. When you do the journalctl -b, do a search (less commands) /snd to find the part of the boot dealing with loading the sound card drivers. The alsa-info output confirms that alsa didn't load any modules, though it found intel and nvidia devices. Try redirecting the output into a txt file that you can upload, e.g. bash alsa-info.sh > alsainfo.txt or edit and copy with Ctrl-A, Ctrl-C, and then paste using Ctrl-V. I have no way to know why the modules for the cards failed, but the suggesting by Colin to try an F31 kernel instead of an F30 kernel is a good one. It's possible there are compiler or key incompatibilities, so the kernel refused to load the modules because they were improperly signed. The fact that you are booted into an F30 kernel also leads me to question whether the upgrade to F31 succeeded.