Re: Support for 8086:ae20 Intel Smart Sound Technology on Fujitsu Lifebook

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




> [~] cat /sys/bus/pci/devices/0000\:00\:1f.3/device 
> 0x02c8

so that's CometLake LP

> [~] cat /sys/bus/pci/devices/0000\:00\:1f.3/class
> 0x040100

this one means the audio DSP is enabled, but might not be required for
your platform.

> [~] sudo lspci -vvv -s 00:1f.3
> 00:1f.3 Multimedia audio controller: Intel Corporation Comet Lake PCH-LP cAVS
>         Subsystem: Fujitsu Client Computing Limited Comet Lake PCH-LP cAVS
>         Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
>         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
>         Latency: 32, Cache Line Size: 64 bytes
>         Interrupt: pin A routed to IRQ 173
>         IOMMU group: 13
>         Region 0: Memory at a2130000 (64-bit, non-prefetchable) [size=16K]
>         Region 4: Memory at 604e000000 (64-bit, non-prefetchable) [size=1M]
>         Capabilities: [50] Power Management version 3
>                 Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0-,D1-,D2-,D3hot+,D3cold+)
>                 Status: D3 NoSoftRst+ PME-Enable+ DSel=0 DScale=0 PME-
>         Capabilities: [80] Vendor Specific Information: Len=14 <?>
>         Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
>                 Address: 00000000fee008d8  Data: 0000
>         Kernel driver in use: snd_hda_intel

and this means the kernel did not detect an interface that requires the DSP.

Looking at your alsa-info log, an alternate explanation is that your
distribution forces the use of the

snd_intel_dspcfg: dsp_driver=1 option, which will select the HDaudio
legacy.

If you happen to have a device with microphones attached to the PCH, not
the HDaudio codec, then by design you *cannot* use the legacy HDaudio
driver (snd-hda-intel). you will have to use the SOF driver
(snd-sof-pci-intel-cnl).

Can you check in /etc/modprobe.d/*.conf if you see a configuration that
sets this module parameter?

If you see this option set, try to comment it out and reboot. You should
really avoid setting the dsp_driver option since it will bypass the
autodetection and might result in the wrong driver being used.




[Index of Archives]     [ALSA User]     [Linux Audio Users]     [Pulse Audio]     [Kernel Archive]     [Asterisk PBX]     [Photo Sharing]     [Linux Sound]     [Video 4 Linux]     [Gimp]     [Yosemite News]

  Powered by Linux