On 9/13/24 00:11, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: Audio Issues When In-place Upgrading to Leap 15.6 Message-ID :<bfae55f3-467d-43c2-b2a0-7dcd58c62841@gmail.com> Date & Time: Thu, 12 Sep 2024 23:16:39 -0500
[DCR] == "David C. Rankin"<drankinatty@gmail.com> has written:
DCR> On 9/12/24 9:38 PM, Lew Wolfgang wrote: LW> > I've also got another older laptop here from work that I LW> > recently did a full install of Leap 15.6 and it works fine with LW> > its internal speakers. Both laptops are HP.
LW> > So something is blocking my speakers in there somewhere. It must be LW> > something in 15.6 because 15.5 and previous worked fine. Is this time LW> > for a bug report?
DCR> This sounds suspiciously like a driver problem. [...]
It's not true.
The audio device, Canon Lake PCH caVS, is an Intel sound chip, and this is a special one that requires separate sof-firmware, and although 15.5 is distributed with this firmware included, for some reason, 15.6 omits it, and it won't sound unless he install it separately himself.
Hi Masaru, sof-firmware-2023.09.2-150600.1.2.noarch is installed on the non-functioning laptop. Looking on laptop2, which had the full install on a blank disk and has working speakers, also has sof-firmware installed. But this lappie doesn't have the Canon Lake PCH caVS sound chip. Yast2 Sound identifies it as Sunrise Point-LP HD Audio, but it's "Not Configured". Yet the speakers work. Go figure. So, seeing that a non-configured sound chip still works, on laptop1 (with the bad speakers) I set the chip to non-configured using the Yast2 Sound screen. Speakers still don't work. So I tried to re-configure it and it errors out with this message: "kernel module snd-sof-pci-intel-cnl could not be loaded. This can be caused by incorrect module parameters, including invalid IO or IRQ parameters." So at this point, laptop1's speakers are still mute, and my BlueTooth buds still work, even with the unconfigured Cannon Lake thing. This so reminds me of the rabbit holes we used to run through with sound back in the old days! I'm thinking the only thing for me do do now, short of submitting a bug report, is to do a full 15.6 install. My feeling is that will work. Any suggestions? Regards, Lew