Mint v19.3 audio popping

[jalin]

any particular kernel update approach you prefer? I see there are different ways not everyone agrees what's best

[MrEen]

I would always recommend the Update Manager. I believe there should be a 5.4 kernel sitting there waiting for you now.

[jalin]

updated to 5.3.0.62.115

thanks for that, boot time is much faster ! (I think it fixed the swap drive issue I had after moving partitions to make room)

anyhow, I tried the different options again and same results. 2 is the only one that doesn't make pops, but 2 also has no normal audio output

[MrEen]

Using 2 again, after the reboot, run this and paste the output:

Code: Select all

dmesg | grep -C1 -E 'ALSA|HDA|sof|HDMI|snd[_-]|sound|hda.codec|hda.intel'

[jalin]

Code: Select all

[    0.189273] ACPI: Added _OSI(Linux-Dell-Video)
[    0.189273] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[    0.189273] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
--
[    1.256711] integrity: Loading X.509 certificate: UEFI:db
[    1.256722] integrity: Loaded X.509 cert 'Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53'
[    1.256723] integrity: Loading X.509 certificate: UEFI:db
[    1.256733] integrity: Loaded X.509 cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4'
[    1.257565] ima: Allocated hash algorithm: sha1

[MrEen]

WOW. Nothing of any use.

Sorry, but for now I'm out of ideas. I'll let you know if I come up with anything.

[jalin]

thank you!

[MrEen]

You're welcome.

I suspect we're not going to really resolve this properly, but I still hope I can think of some workaround that that will mask the issue.

[jalin]

Is 2 not popping because no driver is actually loaded?

[MrEen]

That's correct.

[jalin]

can I do a manual install on an alternative driver?

[MrEen]

No. The driver is in the kernel, so it's already in your system. It's initial function was for users with a digital microphone array that wouldn't work with the legacy snd-hda-intel driver. Eventually, the code will change, and most users will be one the new driver even without the special mic issue, but I don't know of a way to force it other than what we've already tried. For example, the dsp_driver=1 forces snd-hda-intel, but I really don't know what the other numbers represent. You might want to try some higher numbers, but only single digits. I think I saw a bug report where a user might have used 6 or 7 to have some success with something, but I don't remember what the something was, and am pretty sure it wasn't the new sof-audio-pci driver.

I hope that mostly made sense. It's a rather difficult thing to explain sometimes as no one really knows the big picture of this whole driver change. I've watched bug reports for the new driver for a while, and most of them are from the developers that are creating the driver! If they don't have a full grasp of this, how are us lowly users supposed to understand any of it?

[MrEen]

Looks like I may have misremembered, although I'm pretty sure I hadn't. Based on this code, there shouldn't be anything higher than 4:

Code: Select all

enum {
	SND_INTEL_DSP_DRIVER_ANY = 0,
	SND_INTEL_DSP_DRIVER_LEGACY,
	SND_INTEL_DSP_DRIVER_SST,
	SND_INTEL_DSP_DRIVER_SOF,
	SND_INTEL_DSP_DRIVER_LAST = SND_INTEL_DSP_DRIVER_SOF
};

I looked back at your alsa-info output and saw that the sof driver is loading for you:

Code: Select all

snd_sof
snd_sof_intel_byt
snd_sof_intel_hda
snd_sof_intel_hda_common
snd_sof_intel_ipc
snd_sof_xtensa_dsp

Based on the above, I would think the dsp_driver=3 should force the new driver, but you said 3+ were all no good, so I'm not sure where to go from here. I guess we could take a look at the alsa-info output again after using dsp_driver=3 to see if there's anything more we can do.

[jalin]

output of alsa-info with dsp_driver=3:

http://alsa-project.org/db/?f=1e230eaff ... ad167f3f16

Should note, 3 is actually different than the others. It has the usual startup and shutdown booms, but also it has a constant unending boom that does not stop as long as linux is running

[MrEen]

Well, damn!!

You are running on the new driver:

Code: Select all

APLAY

**** List of PLAYBACK Hardware Devices ****
card 0: sofsklhdacard [sof-skl_hda_card], device 0: HDA Analog (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofsklhdacard [sof-skl_hda_card], device 1: HDA Digital (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofsklhdacard [sof-skl_hda_card], device 3: HDMI1 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofsklhdacard [sof-skl_hda_card], device 4: HDMI2 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofsklhdacard [sof-skl_hda_card], device 5: HDMI3 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0

ARECORD

**** List of CAPTURE Hardware Devices ****
card 0: sofsklhdacard [sof-skl_hda_card], device 0: HDA Analog (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofsklhdacard [sof-skl_hda_card], device 1: HDA Digital (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofsklhdacard [sof-skl_hda_card], device 6: DMIC32 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofsklhdacard [sof-skl_hda_card], device 7: DMIC16 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Actually, maybe if we blacklist the legacy driver again, you might have working sound AND no booms:

Code: Select all

sudo tee /etc/modprobe.d/blacklist-snd-hda-intel.conf <<<'blacklist snd-hda-intel'

[jalin]

now no booms, also no sound

'Dummy Output' is only device

[MrEen]

Damn. I thought that had a good chance of working. And I don't understand why you got that Dummy Output with that option.

I'm afraid I'm out of ideas for the time being again.

Let's see if this gives us any clue:

Code: Select all

dmesg | grep -C1 -E 'ALSA|HDA|sof|HDMI|snd[_-]|sound|hda.codec|hda.intel'

[jalin]

Dummy Output seems to be the case when no driver is loaded or recognized

Code: Select all

[    0.189560] ACPI: Added _OSI(Linux-Dell-Video)
[    0.189560] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[    0.189560] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
--
[    1.252216] integrity: Loading X.509 certificate: UEFI:db
[    1.252232] integrity: Loaded X.509 cert 'Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53'
[    1.252232] integrity: Loading X.509 certificate: UEFI:db
[    1.252244] integrity: Loaded X.509 cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4'
[    1.253062] ima: Allocated hash algorithm: sha1
--
[    4.342483] thermal thermal_zone8: failed to read out thermal zone (-61)
[    4.353038] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040380
[    4.393868] pci_bus 0000:05: Allocating resources

[MrEen]

Ahh, I figured it out. Even though aplay shows the sof driver in use, this part is showing the realtec module, that requires snd-hda-intel:

Code: Select all

[    6.283336] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC3271: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
[    6.283340] snd_hda_codec_realtek ehdaudio0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[    6.283342] snd_hda_codec_realtek ehdaudio0D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
[    6.283343] snd_hda_codec_realtek ehdaudio0D0:    mono: mono_out=0x0
[    6.283344] snd_hda_codec_realtek ehdaudio0D0:    inputs:
[    6.283346] snd_hda_codec_realtek ehdaudio0D0:      Headset Mic=0x19
[    6.283348] snd_hda_codec_realtek ehdaudio0D0:      Headphone Mic=0x1b
[    6.283350] snd_hda_codec_realtek ehdaudio0D0:      Internal Mic=0x12

Like I said, I'm stuck for now.

[jalin]

so I'm using 2 drivers simultaneously