On 1/31/2023 4:16 PM, Jason Montleon wrote:
On Tue, Jan 31, 2023 at 7:37 AM Cezary Rojewski cezary.rojewski@intel.com wrote:
On 2023-01-30 1:22 PM, Sasa Ostrouska wrote:
Dear Czarek, many thanks for the answer and taking care of it. If needed something from my side please jest let me know and I will try to do it.
Hello Sasa,
Could you provide us with the topology and firmware binary present on your machine?
Audio topology is located at /lib/firmware and named:
9d71-GOOGLE-EVEMAX-0-tplg.bin -or- dfw_sst.bin
Firmware on the other hand is found in /lib/firmware/intel/. 'dsp_fw_kbl.bin' will lie there, it shall be a symlink pointing to an actual AudioDSP firmware binary.
Maybe this is the problem.
I think most of us are pulling the topology and firmware from the chromeos recovery images for lack of any other known source, and it looks a little different than this. Those can be downloaded like so: https://gist.github.com/jmontleon/8899cb83138f2653f520fbbcc5b830a0
After placing the topology file you'll see these errors and audio will not work until they're also copied in place. snd_soc_skl 0000:00:1f.3: Direct firmware load for dsp_lib_dsm_core_spt_release.bin failed with error -2 snd_soc_skl 0000:00:1f.3: Direct firmware load for intel/dsp_fw_C75061F3-F2B2-4DCC-8F9F-82ABB4131E66.bin failed with error -2
Once those were in place, up to 6.0.18 audio worked.
Is there a better source for the topology file?
The reasoning for these asks is fact that problem stopped reproducing on our end once we started playing with kernel versions (moved away from status quo with Fedora). Neither on Lukasz EVE nor on my SKL RVP. However, we might be using newer configuration files when compared to equivalent of yours.
Recent v6.2-rc5 broonie/sound/for-next - no repro Our internal tree based on Mark's for-next - no repro 6.1.7 stable [1] - no repro
Of course we will continue with our attempts. Will notify about the progress.
Kind regards, Czarek
Hi Jason,
as I understand you've tried to do bisect, can you instead try building kernels checking out following tags: v6.1 v6.1.1 v6.1.2 v6.1.3 v6.1.4 v6.1.5 v6.1.6 v6.1.7 v6.1.8 and report when it stops working, so it narrows scope of what we look at? I assume that kernel builds are done using upstream stable kernel (from https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/).
Thanks, Amadeusz