Bugzilla – Bug 1208789
degradation of support for DIGMA notebook: no sound & no wifi
Last modified: 2023-09-19 23:39:47 UTC
Initially I switched to OpenSuSE Tumbleweed from Fedora due to sound support "right after install". Too lazy to build kernel each time it upgrades. I do not remember exact OpenSuSE Thumbleweed version, but I still have the kernel with correct support for my hardware & boot it currently - it is in boot menu yet. Also I've got WiFi not working on new kernel. Details (output on good kernel): ----> 13:41:38 Wed Mar 01 olli@digma ~ $ uname -a Linux digma 6.1.10-1-default #1 SMP PREEMPT_DYNAMIC Mon Feb 6 07:27:26 UTC 2023 (2a0570b) x86_64 x86_64 x86_64 GNU/Linux ----> 13:43:19 Wed Mar 01 olli@digma ~ $ $ lspci -v |grep audio -A 10 00:1f.3 Multimedia audio controller: Intel Corporation Comet Lake PCH-LP cAVS DeviceName: Onboard - Sound Subsystem: Emdoor Digital Technology Co., Ltd Device 0206 Flags: bus master, fast devsel, latency 32, IRQ 133 Memory at b1418000 (64-bit, non-prefetchable) [size=16K] Memory at b1200000 (64-bit, non-prefetchable) [size=1M] Capabilities: <access denied> Kernel driver in use: sof-audio-pci-intel-cnl Kernel modules: snd_hda_intel, snd_soc_skl, snd_sof_pci_intel_cnl $ lspci -v |grep Atheros -A 10 02:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) Subsystem: AzureWave Device 2b51 Flags: bus master, fast devsel, latency 0, IRQ 134 Memory at b1000000 (64-bit, non-prefetchable) [size=2M] Capabilities: <access denied> Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci $ head -n 2 /etc/*release* NAME="openSUSE Tumbleweed" # VERSION="20230226" I think that ouput on "bad kernel" wouldn't help (same hardware, but not supported - modules not used), but if you really need it, or other details - just ask - I'll boot to current kernel (AFAIR, this is 6.1.12-1-default).
PLease attach dmesg output from both working and non-working kernels.
I cannot reproduce the bug. Seems that something disabled the sound and wifi when I filled the information. I was playing w/ QubesOS installation & rebooted back to OpenSuSE & to my surprise the sound & wifi work on both new & old kernels.
Created attachment 866552 [details] dmesg with wrong sound (no sound, wrong sound card) I'm not sure that this is kernel related - maybe sof-firmware, but something went wrong & I've no sound. Unfortunately I can't tell which updates are a reason for this, but I've no sound again & I did nothing for this - it just stopped working once on reboot in my OpenSuSE Thumbleweed (works in Win11, so that is not broken hardware). Please reroute this bug to proper place. ----> 00:19:19 Tue Apr 25 olli@digma ~ $ rpm -qa |grep sof-firmware sof-firmware-2.2.4-1.2.noarch ----> 00:19:35 Tue Apr 25 olli@digma ~ $ uname -a Linux digma 6.2.10-1-default #1 SMP PREEMPT_DYNAMIC Thu Apr 6 10:36:55 UTC 2023 (ba7816e) x86_64 x86_64 x86_64 GNU/Linux ----> 00:19:39 Tue Apr 25 olli@digma ~ $ lspci |grep audio 00:1f.3 Multimedia audio controller: Intel Corporation Comet Lake PCH-LP cAVS ----> 00:19:50 Tue Apr 25 olli@digma ~ $ I see Pro Audio as a soundcard when look in sound settings via GUI. But this is incorrect according to lspci I've Intel Corporation Comet Lake PCH-LP cAVS . Hope that info from old report help a bit. I've tried to boot old kernel 6.2.9-1-default, but still no sound.
Qubes OS 4.1.2 has sound with my card (them fixed support for such a sound card), but Xen Dom0 there is based on old fedora..
----> 01:39:03 Wed Aug 02 olli@digma ~ $ cat /etc/*release* NAME="openSUSE Tumbleweed" # VERSION="20230729" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20230729" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20230729" BUG_REPORT_URL="https://bugzilla.opensuse.org" SUPPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org" DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed" LOGO="distributor-logo-Tumbleweed" ----> 01:46:25 Wed Aug 02 olli@digma ~ $ With above, I see that properly configured with alsactl sound works. However, KDE has stored _sound_ configuration, and KDE applies it also when connection to WiFi activated (since I 1st time played sound with aplay & only later entered password to restore KDE wifi connection (credentials for WiFi are saved inside KDE wallet, AFAIR). For one confused with alsamixer I would recommend to read https://www.freecodecamp.org/news/how-to-fix-broken-audio-in-headphones-and-speakers-linux/ the article at February 16, 2022/#Linux by Md. Fahim Bin Amin - a few images, step by step _short_ guide. Just don't forget that console tool alsamixer in some places require mouse (the "space" is ignored, but mouse double click works). I set the bug to MINOR. Feel free to reroute to alsamixer & KDE internals or close as RESOLVED.
DIGMA lapptop has a physical switch on the left side, that, according to user guide, disables Video camera on the laptop lid. Switching this physical switch to OFF may cause sound become off in reality and in alsamixer (softwware trigger "Speaker" when specific card selected is not green), but not always. I don't know is this behavior was expected & just comment here for those who're stuck in "no sound" situation: opening alsamixer, selecting sof-essx8336 and triggering "Speaker" to green state fixes the sound. If not - loading KDE sound controls (or pavucontrol GUI from terminal) after triggering to green in terminal app alsamixer does the trick - sound is present in reality in my case & this is the workaround.
Currently sound support does not survive hibernates. Though the kernel appeared with updates normally keeps WiFi support on restore from hibernate. Nice. ----> 02:31:10 Wed Sep 20 olli@digma ~ $ uname -a Linux digma 6.5.3-1-default #1 SMP PREEMPT_DYNAMIC Thu Sep 14 08:46:53 UTC 2023 (786e0d6) x86_64 x86_64 x86_64 GNU/Linux ----> 02:38:39 Wed Sep 20 olli@digma ~ $ With this kernel I was able to configure sound to be working by running alsamixer & after it - pavucontrol. Though require from user to use both tools to enable sound is bad design.