Comment 2 for bug 1886696

Revision history for this message
Yakir Levi (yakirl) wrote :

Ok so I guess it's true what they say, when you go to the doctor you suddenly feel well.
I was debugging this issue for quite some time, and just after I submitted the bug I found the trick. This is basically just a workaround, the bug is still real.

So as the guy here: https://forums.linuxmint.com/viewtopic.php?f=48&t=311714&start=20 explains, the sof driver is still new and buggy, so the best workaround is to disable it and roll back to intel driver.
But apperantly 'snd_hda_intel.dmic_detect=0' is depracted in newer versions. So what I did was to change in '/etc/default/grub' the line:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
to:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash snd-intel-dspcfg.dsp_driver=1"

and then run 'sudo update-grub' and reboot

Also, Im not sure it mandatory but I left those 2 lines in /etc/modprobe.d/alsa-base.conf :
options snd-hda-intel model=auto
options snd-hda-intel snd-intel-dspcfg.dsp_driver=1

After the reboot, there were no dmesg errors, but still snd-hda-intel was down, so I had to manually do:
$ sudo modprobe snd-hda-intel

And it works.
By the way this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864871?comments=all looks kinda similar but still not the same. I tried before to edit /etc/pulse/default.pa as suggested but this messes up my pulseaudio daemon, as I saw in systemctl, so I reversed it.

I shared in details to help anyone that encounter similar problems, and maybe to get some feedback about the workaround. Everything seems to work now (didnt check mic)