I was attempting to figure out how the Fedora nvidia-gpu-firmware package creates what seem to be sym-links from the various model directories to the single instance of the GSP firmware version file.
In the Fedora install can you report what this reports (adjust the path prefix if that file-system is mounted somewhere else) ? find /lib/firmware/nvidia/tu117 -ls I'm expecting to see symbolic links for the gsp.*.bin files to another directory. With this information I can give you instructions on duplicating the layout in the Debian install, but even without it I think this is what you'll need to do (in the running Debian instance): # this may already be installed sudo apt install firmware-nvidia-graphics # this may already exist sudo mkdir --parents /usr/lib/firmware/nvidia/tu117/gsp # this is the vital symbolic link sudo ln -s ../../tu116/gsp/gsp-535.113.01.bin /usr/lib/firmware/nvidia/tu117/gsp/ The kernel build is ready. I've used v6.15.6 with the config patch since it will be easy to compare its log against the Debian v6.15.6 log you've already shared and we can see if it matches the Fedora log of their v6.15.4. Here's confirmation the config option is in this kernel: $ dpkg-deb --fsys-tarfile ../../builds/linux-image-6.15.6_6.15.6-318_amd64.deb | tar -x -f - --to-stdout | grep DRM_NOUVEAU_GSP_DEFAULT CONFIG_DRM_NOUVEAU_GSP_DEFAULT=y The kernel package is in my Proton Drive at: https://drive.proton.me/urls/MN32XF7V30#2v1RKvNvLLUA The sha256.sum file is there also (ffd663ea8fbb33342857279f497f6513fefd5e5127f858e92acf839e054ac081). Download both files to the same directory then do: sha256sum -c sha256.sum That should report: linux-image-6.15.6_6.15.6-318_amd64.deb: OK Now install the kernel with: sudo apt install ./linux-image-6.15.6_6.15.6-318_amd64.deb Once/if we've sorted out the GSP firmware file and required sym-links you can go ahead and boot into this kernel to test. Please report back and share the boot log whether it works or not; e.g: sudo journalctl --dmesg > /tmp/dmesg-v6.15.6+debian_tj.log Note: as well as the Nvidia config change this kernel includes a handful of my own patches that I apply to all my builds. One of them reports all firmware files that are loaded and hopefully - if nouveau is using the firmware loader library - it'll tell us for sure which firmware files are being loaded. The patch stack on top of v6.15.6 mainline in this kernel is: $ git l -n 10 fd77d0df971df 2025-08-07 13:47:07 +0000 N Tj config: Debian v6.15.6 enable DRM_NOUVEAU_GSP_DEFAULT 18fc0cd28e807 2025-08-07 13:45:53 +0000 N Tj config: import Debian v6.15.6 config ca23184e137d6 2025-08-07 13:42:42 +0000 N Tj defconfig: add debian+tj v6.15 30e1edbe28128 2025-08-07 13:42:42 +0000 N Tj ath: add module_param country_default for regulatory domain control 852c7433a5467 2025-08-07 13:42:42 +0000 N Tj cfg80211: suppress regdom warning when phy not ready 39c61beb7d2ec 2025-08-07 13:42:42 +0000 N Tj debian: call linux-update-symlinks from postinst (v6.14+) 9ea18f3b0a5d4 2025-08-07 13:42:42 +0000 N Tj debian: no -dbg package using KDEB_NO_DBG=1 55762f40f581c 2025-08-07 13:42:42 +0000 N Tj firmware: report each loaded firmware file 1562d94823254 2025-07-10 16:08:55 +0200 N Greg Kroah-Hartman Linux 6.15.6 62901034ddc8a 2025-07-10 16:08:55 +0200 N Borislav Petkov (AMD) x86/process: Move the buffer clearing before MONITOR
