On 9/16/24 03:32, Gustav Degreef wrote:
On 9/15/24 22:51, Carlos E. R. wrote:
On 2024-09-15 19:57, Gustav Degreef wrote:
On 9/14/24 14:15, Carlos E. R. wrote:
On 2024-09-14 03:50, Lew Wolfgang wrote:
I found another thread very much related to the current audio problem : Leap 15.6 - no sound. Kernel module snd-sof-pci-intel-cnl cannot be loaded - English / Multimedia - openSUSE Forums <https://forums.opensuse.org/t/leap-15-6-no-sound-kernel-module-snd-sof-pci-intel-cnl-cannot-be-loaded/177876>
Seems to confirm the problem is with the kernel. I checked my Asus system for sof-firmware and it was installed, so as others have noted this is not the core problem. On the latest boot, my sound card is configured and I have sound, so like others have noted, the problem is intermittent and unpredictable. Apparently there is already a bug report and a fix and someone mentions that the recommendation is to update the kernel. Like me, another user 'fixed' the problem by not booting the latest 6.4.xxxs kernel, but instead booting an earlier 5.14.xxx kernel.
Does anyone have an idea when Leap 15.6 might have an updated kernel which fixes this issue with these Intel sound hardware?
You need to report the issue in Bugzilla.
Also, how to prevent my 5.14.xxx kernel from being deleted or removed from the GRUB menu (as updates come in), while I wait for a new kernel?
Lock it.
For instance, see https://forums.opensuse.org/t/locking-unlocking-kernel/173609/3
You might do it with YaST, but I'm not sure right now.
Thanks for your specific and practical advice Carlos. I will look into it. As for reporting the bug, I am quite visually impaired and it is a great effort even to track this audio issue down and report my experience on this list. I have never reported a bug and have no idea even where to start.
I guess it's up to me to report. I've got another one filed (Bug 1230111) that hasn't seen any action in almost two weeks. Which is a little surprising in that it's a segfault in libcrypto, a part of libopenssl. I thought that any crash in a crypto library was of concern in that it could lead to significant new vulnerabilities. Maybe someone's working on it without me knowing about it? This particular bug is a show stopper for us in upgrading to Leap 15.6. It crashes subversion access when SASL encryption is enabled. I'll collect my thoughts on the sound problem and try to submit a rational bug report. Regards, Lew