I am having audio issues on NixOS. I have tried enabling all firmware. I’ve also tried both pipewire and pulseaudio. The audio is confirmed working on CachyOS live image.

Here is the error message found in the system log:

`Aug 01 01:43:19 nixos kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: error: sink MIXER1.0g623.1 not found

Aug 01 01:43:19 nixos kernel: skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: topology: add_route failed: -22

Aug 01 01:43:19 nixos kernel: skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: topology: could not load header: -22

Aug 01 01:43:19 nixos kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: error: tplg component load failed -22

Aug 01 01:43:19 nixos kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: error: failed to load DSP topology -22

Aug 01 01:43:19 nixos kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: ASoC: error at snd_soc_component_probe on 0000:00:1f.3: -22

Aug 01 01:43:19 nixos kernel: skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: failed to instantiate card -22

Aug 01 01:43:19 nixos kernel: skl_hda_dsp_generic skl_hda_dsp_generic: probe with driver skl_hda_dsp_generic failed with error -22`

Here is configuration.nix

      • areyouevenreal@lemm.eeOPEnglish
        11·
        3 months ago

        Error is the same as last time. Turns out even the live Nix image can’t do audio on this machine. Switched to a Linux distro that actually works. Still would be interesting to find out why this happened.

          • areyouevenreal@lemm.eeOPEnglish
            1·
            3 months ago

            It’s clearly not a UEFI problem when it works fine on another Linux distro. Likewise I don’t think it’s a needed kernel parameter, because I didn’t add anything to CachyOS to make it work, though I will double check the current parameters. It’s a fairly standard Intel audio device as well, not anything weird or even that new (tigerlake).

            I think this is an issue with how NixOS build their kernel and kernel modules. It’s not like it’s the only problem I have had with NixOS unfortunately.

            • paperdEnglish
              2·
              3 months ago

              NixOS ships a very minimal kernel and relies on you to declare what modules you want to load (or sometimes relies on nixos-generate-hardware to find some of those modules), so even if it is really standard hardware that “just works” on other distros, you still may need to dig out some kernel modules and explicitly load them.

              But if CachyOS works for you and makes you comfortable, that is good and you should use it.

              However “it worked on other distro X, thus is should work on other distro Y” probably isn’t a helpful way of thinking to get things working.

              • areyouevenreal@lemm.eeOPEnglish
                11·
                3 months ago

                However “it worked on other distro X, thus is should work on other distro Y” probably isn’t a helpful way of thinking to get things working.

                I am talking about the kernel here. It tells me that the device is actually supported. If something works on other distros driver wise, that means the one it doesn’t work on either has an old kernel or is doing something strange.

                NixOS ships a very minimal kernel and relies on you to declare what modules you want to load (or sometimes relies on nixos-generate-hardware to find some of those modules), so even if it is really standard hardware that “just works” on other distros, you still may need to dig out some kernel modules and explicitly load them.

                That explains it. Still is an odd choice. The whole point of Linux being modular, and knowing how to load stuff automatically, is that shit like this isn’t necessary. I can understand if this was Gentoo and we were talking about manually compiling kernels, but this is a pre compiled generic kernel. The expectation is that it just works.

                Do you have a source on where to configure these kernel settings?

                • paperdEnglish
                  2·
                  3 months ago

                  Yes it’s ```` boot.kernelParams = [ “snd-intel-dspcfg.dsp_driver=1” ];