Created attachment 286295 [details] LOGS I have sound only under 4.19.x series. I have NOT sound at all under newer kernel series. Previously NO SOUND issue was resolved in 4.19.10 release and works well. Today we have 5.4.3 5.3.16 4.19.89 and sound works ONLY in 4.19.x Similar issue was posted here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784485 Current issue I reported here too https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856308 I tried Manjaro KDE x64 and Kubuntu daily. Logs in ZIP file came from Kubuntu live session. DMI: ASUSTeK COMPUTER INC. VivoBook 15_ASUS Laptop X542UF/X542UF, BIOS X542UF.307 06/13/2019 HW ID's 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) sudo hwinfo --sound 20: PCI 1f.3: 0403 Audio device [Created at pci.386] Unique ID: nS1_.b28td23g3aB SysFS ID: /devices/pci0000:00/0000:00:1f.3 SysFS BusID: 0000:00:1f.3 Hardware Class: sound Model: "Intel Sunrise Point-LP HD Audio" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x9d71 "Sunrise Point-LP HD Audio" SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x1a00 Revision: 0x21 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xef528000-0xef52bfff (rw,non-prefetchable) Memory Range: 0xef500000-0xef50ffff (rw,non-prefetchable) IRQ: 132 (1577 events) Module Alias: "pci:v00008086d00009D71sv00001043sd00001A00bc04sc03i00" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Driver Info #1: Driver Status: snd_soc_skl is active Driver Activation Cmd: "modprobe snd_soc_skl" Config Status: cfg=new, avail=yes, need=no, active=unknown Regards
I downloaded lastest fresh ISO with Manjaro KDE Sounds back in some release between 5.4.2-1 and 5.4.6-2 Disabling SND_HDA_INTEL_DETECT_DMIC does job IMHO. https://gitlab.manjaro.org/packages/core/linux54/commit/a5e06eb91a3b385a85f2be17b533a36806002c30 https://bugs.archlinux.org/task/64720 https://cateee.net/lkddb/web-lkddb/SND_HDA_INTEL_DETECT_DMIC.html
The machine seems with the DMIC and we need SOF driver for supporting it. With the kconfig, it automatically falls back to the SOF driver, and you seem either not enabling it properly or missing the firmware. Please make sure that you enabled all relevant SOF drivers *and* install the dedicated firmware files (topology files etc you see in the kernel messages). If the things still don't work properly, we need to address the remaining issues in the upstream side.