snd_intel_dspcfg: dsp_driver=1 was a leftover from testing. I' ve removed all parameters, add added the debug options you've asked. http://alsa-project.org/db/?f=6e30e9f598bd2f03b2f5cff0df261f78719ea29d Some googling reveals that others suffer from the same problen on the same laptop as well. Some report that the device appears after pci-bus rescanning however that did not work in my case so I agree there might be an issue with probing the relatek device. Unfortunately I'm not a kernel dev so I don't even know where to start looking however I'm happy to investigate with your help. Gesendet: Mittwoch, 09. Februar 2022 um 16:51 Uhr Von: "Pierre-Louis Bossart" <pierre-louis.bossart@xxxxxxxxxxxxxxx> An: dmummenschanz@xxxxxx, alsa-devel@xxxxxxxxxxxxxxxx Betreff: Re: Aw: Re: Cannon Lake PCH cAVS (ALC892) not detected by kernel driver On 2/9/22 01:14, dmummenschanz@xxxxxx wrote: > The information about the codec is based on the string windows > provides: > > HDAUDIO\FUNC_01&VEN_10EC&DEV_0892&SUBSYS_15580351&REV_1003\4&16AF2B56&& > 0001 > > Here is the alsa-info output for the 5.16 mainline kernel: > > [1]http://alsa-project.org/db/?f=38c48cd24dc4ba9a9487dd96f857120cc9ce43 67 The use of this option is not clear: snd_intel_dspcfg: dsp_driver=1 This means you are trying to force the use of the legacy driver. is this intentional? Can you remove it and see what happens? The results show you don't have a driver bound to the PCI device, so likely something goes boink in the probe. It wouldn't hurt to enable dynamic debug as well. options snd_hda_intel dyndbg=+p options snd_intel_dspcfg dyndbg=+p References 1. http://alsa-project.org/db/?f=38c48cd24dc4ba9a9487dd96f857120cc9ce4367
