Sorry, I hit the wrong button.
On Fri, 31 Jan 2025 09:02:37 -0700
Charles Curley <charlescur...@charlescurley.com> wrote:
> You did not mention what sort of hardware you are running. Running
> lspci as root should give us what we need. Something like:
root@peregrine:~# lspci -vs 1f.3
0000:00:1f.3 Audio device: Intel Corporation Raptor Lake-P/U/H cAVS (rev 01)
Subsystem: CLEVO/KAPOK Computer Raptor Lake-P/U/H cAVS
Flags: bus master, fast devsel, latency 32, IRQ 164, IOMMU group 13
Memory at 6003230000 (64-bit, non-prefetchable) [size=16K]
Memory at 6003000000 (64-bit, non-prefetchable) [size=1M]
Capabilities: [50] Power Management version 3
Capabilities: [80] Vendor Specific Information: Len=14 <?>
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl
root@peregrine:~#
where 1f.3 is the slot/function number from a prior run of lspci.
Notice the list of kernel drivers and modules. Rooting around in the
output from dmesg or journalctl with those should locate any messages
about initializing the sound card, including any error messages.
> I hope you can help me by either confirming I should send a bugreport
> on package
> firmware-sof-signed or suggest an alternative action.
I suggest getting some more information to this list before filing a
bug report. I'm not convinced it is a bug.
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescurley.com/blog/
