For reference, he's my makeModulesClosure overlay:

final: prev: {
  makeModulesClosure = args: (prev.makeModulesClosure args).overrideAttrs (prevAttrs: {
    builder = final.runCommand "modules-closure.sh" { } ''
      cat ${prevAttrs.builder} > $out
      chmod +x $out
      echo 'rm -rf "$out/lib/firmware/nvidia"' >> $out
      echo 'mkdir -p "$out/lib/firmware/nvidia"' >> $out
      echo 'cp --no-preserve=mode -r "$firmware/lib/firmware/nvidia/ga10"{2,7} "$out/lib/firmware/nvidia/"' >> $out
      echo 'pushd "$out/lib/firmware/nvidia/ga107"' >> $out
      echo 'rm -rf gsp.xz' >> $out
      echo 'ln -s ../ga102/gsp ./gsp' >> $out
      echo 'popd' >> $out
    '';
  });
}

In case someone wants to play with NVK+GSP:

• first you need Linux 6.7 with latest stable firmware and mesa-git;
• then you need to fix the symlink of your GPU in linux-firwmare or makeModulesClosure (it's symlinking "gsp.xz" instead of "gsp", and needs to copy "nvidia" folder in the closure)
• since you're already touching the closure, remove all the other GPUs to save 60Mb in your initrd
• make sure to not enable hardware.nvidia
• boot.kernelParams = [ "nouveau.config=NvGspRm=1" "nouveau.debug=\"GSP=debug\"" ];
• Now, you should be able to see the firmware loading in dmesg;
• Downgrade DXVK by adding the 1.10.3 DLLs in the game's folder

And that's it right now, everything requiring Vulkan 1.2+ is a no-go

In reply to @atemu12:matrix.org
Also, can't nouveau (OGL) benefit from re-clocking too now?

In reply to @k900:0upti.me
Is the linux-firmware thing a make-modules-closure bug or an upstream linux-firmware bug?

In reply to @k900:0upti.me
If the symlink isn't broken

Either:

1. The "gsp" folder should be xz-ed during the make of linux-firmware and, for some reason, it isn't
2. During the link creation, the .xz suffix is being wrongly added

In reply to @charles:computer.surgery
also, someday we'll have mesa 23.3.1 on nixos-unstable...