Bug#1020221: linux-image-5.10.0-18-amd64: no sound on Acer Chromebook Spin 11 R751T (google reef device)

[no2spam <no2spam-br@gmx.com>]

On Sun, 18 Sep 2022 18:23:48 +0200
Diederik de Haas <didi.debian@cknow.org> wrote:



Hi,

Thanks for responding.
Yes, you are correct - sound doesn't work even on 5.19 kernel. I've tried kernels 5.15, 5.16, 5.17, 5.18 without luck.

I've mentioned 5.19 kernel output as it selects different drivers from 5.10 and seems to look for google reef related SOF topology file.



debian 5.10.140 loads the following driver:

[   20.444527] snd_hda_intel 0000:00:0e.0: DSP detected with PCI class/subclass/prog-if info 0x040100
[   20.474985] da7219 i2c-DLGS7219:00: Using default DAI clk names: da7219-dai-wclk, da7219-dai-bclk
[   20.474994] da7219 i2c-DLGS7219:00: Invalid micbias pulse level
[   21.400901] snd_soc_skl 0000:00:0e.0: DSP detected with PCI class/subclass/prog-if info 0x040100
[   21.402273] snd_soc_skl 0000:00:0e.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[   22.077993] HDMI HDA Codec ehdaudio0D2: Max dais supported: 3


kernel 5.19 loads:
[    5.070897] da7219 i2c-DLGS7219:00: Using default DAI clk names: da7219-dai-wclk, da7219-dai-bclk
[    5.070919] da7219 i2c-DLGS7219:00: Invalid micbias pulse level
[    5.181117] snd_hda_intel 0000:00:0e.0: DSP detected with PCI class/subclass/prog-if info 0x040100
[    5.386487] snd_soc_skl 0000:00:0e.0: DSP detected with PCI class/subclass/prog-if info 0x040100
[    7.094171] snd_soc_skl 0000:00:0e.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[    7.898666] HDMI HDA Codec ehdaudio0D2: Max dais supported: 3
[    7.920335] snd_soc_skl 0000:00:0e.0: Direct firmware load for 5a98-reef-reef-8-tplg.bin failed with error -2
[    7.920345] snd_soc_skl 0000:00:0e.0: tplg fw 5a98-reef-reef-8-tplg.bin load failed with -2, trying alternative tplg name bxt_da7219_mx98357a-tplg.bin
[    7.920382] snd_soc_skl 0000:00:0e.0: Direct firmware load for bxt_da7219_mx98357a-tplg.bin failed with error -2
[    7.920385] snd_soc_skl 0000:00:0e.0: tplg bxt_da7219_mx98357a-tplg.bin failed with -2, falling back to dfw_sst.bin
[    7.920417] snd_soc_skl 0000:00:0e.0: Direct firmware load for dfw_sst.bin failed with error -2
[    7.920420] snd_soc_skl 0000:00:0e.0: Fallback tplg fw dfw_sst.bin load failed with -2
[    7.920422] snd_soc_skl 0000:00:0e.0: Failed to init topology!
[    7.920424] snd_soc_skl 0000:00:0e.0: ASoC: error at snd_soc_component_probe on 0000:00:0e.0: -2
[    7.920451] bxt_da7219_max98357a bxt_da7219_mx98357a: ASoC: failed to instantiate card -2
[    7.920573] bxt_da7219_max98357a: probe of bxt_da7219_mx98357a failed with error -2


As I understand the problem is matching kernel driver with the right Apollo Lake SOF driver from firmware-sof-signed (v1.7-1) package. But Sound Open Firmware is too complicated for me.




> On Sunday, 18 September 2022 13:02:47 CEST no2spam wrote:
> > Package: src:linux
> > Version: 5.10.140-1
> >
> > dmesg of Liquorix 5.19 kernel on the same machine (using Antix-21
> > (Debian bullseye without systemd):
>
> Why do you think the output of some 'random' 5.19 kernel is relevant
> for a bug in Debian's 5.10.140 kernel?
>
> If it does work with a different (newer or older) Debian kernel, that
> would be useful to know.
>
> FWIW: I did look through the dmesg output and I got the impression it
> didn't work with the 'random' 5.19 kernel either.