No sound after upgrade from 22.04 LTS to 24.04 LTS - problem depends on kernel version

[Virginio Miranda]

user@hostname:~$ sudo alsa force-reload
[sudo] Passwort für user:
Terminating processes: 2610
.
Unloading ALSA sound driver modules: snd-seq-dummy snd-hrtimer snd-hda-codec-hdmi snd-hda-codec-realtek snd-hda-codec-generic snd-hda-intel snd-intel-dspcfg snd-intel-sdw-acpi snd-hda-codec snd-hda-core snd-hwdep snd-pcm snd-seq-midi snd-seq-midi-event snd-rawmidi snd-seq snd-seq-device snd-timer (failed: modules still loaded: snd-hrtimer snd-hda-codec-hdmi snd-hda-codec-realtek snd-hda-codec-generic snd-hda-intel snd-intel-dspcfg snd-intel-sdw-acpi snd-hda-codec snd-hda-core snd-hwdep snd-pcm snd-seq snd-seq-device snd-timer).
Loading ALSA sound driver modules: snd-seq-dummy snd-hrtimer snd-hda-codec-hdmi snd-hda-codec-realtek snd-hda-codec-generic snd-hda-intel snd-intel-dspcfg snd-intel-sdw-acpi snd-hda-codec snd-hda-core snd-hwdep snd-pcm snd-seq-midi snd-seq-midi-event snd-rawmidi snd-seq snd-seq-device snd-timer.
user@hostname:~$

This fixes the problem, but only until the next reboot. Then I have to enter the command again. Is there any way I can include this in a startup script, or find out what triggers this behaviour in the first place?

Edit /etc/modprobe.d/blacklist.conf and add to end of the file the follow:

blacklist snd_soc_avs

save and sudo alsa force-reload again.

Reboot and lets see how it performs.

[jensnolte]

Edit /etc/modprobe.d/blacklist.conf and add to end of the file the follow:

blacklist snd_soc_avs

save and sudo alsa force-reload again.

Reboot and lets see how it performs.

Unfortunately, this does not work, either, it stops the workaround with the alsa force reload from working. Only after removing it from blacklist.conf, it worked again.

[Virginio Miranda]

Hi jensnolte

The problem is the kernel is loading the wrong drive.with sudo alsa force-reload it loads the correct drive. When you reboot it loads the wrong drive.

I sugest you to blacklist snd_soc_avs because it use to be a problematic drive, but it seems not your case.

Try to realize witch drives the kernel is loading.

Use the latest Kernel. Reboot the PC. It will load the wrong drive. Type in konsole: $inxi -xxz -audio. Look at the drive.

Then, make sudo alsa force-reload. After that the kernel will load the correct drive. Check if everything is working, then do $inxi -xxz -audio again and look at the drive.

Maybe we can blacklist the wrong drive to not load when you reboot the PC.