On Sun, 2025-12-28 at 18:45 +0100, Ewan Chorynski wrote: > > [ 3.623000] NovaCore 0000:01:00.0: GSP MBOX0: 0xffffe000, MBOX1: 0x0 > [ 3.623026] NovaCore 0000:01:00.0: Using SEC2 to load and run the > booter_load firmware... > [ 3.626236] NovaCore 0000:01:00.0: SEC2 MBOX0: 0x31, MBOX10x0 > [ 3.626265] NovaCore 0000:01:00.0: Booter-load failed with error 0x31 > > Is this expected to happen ? Here is the full device description from > lspci : > > 01:00.0 VGA compatible controller: NVIDIA Corporation TU117M [GeForce GTX > 1650 Mobile / Max-Q] > (rev a1)
This should work on your GPU with my patches. Error 0x31 is a generic failure error code that indicates that booter_load failed to initialize, and that could be for any number of reasons. Unfortunately, the only way I've been able to debug such issues is to reproduce them in-house with a custom build of booter_load. I suggest that for now, you hold off until these commits are merged, along with my debugfs patches, and then I can try to find a similar GPU internally that exhibits the failure and see if there's something else missing. Turing is the most complicated of all GSP-capable GPUs to boot, partly because the firmware does a terrible job of reporting errors. I'm assuming that Nouveau boots just fine with the same firmware images? If you turn on debug logging in Nouveau, it should say that it's booting with 570.144. You can force it by deleting all the *535.113.01* images in /lib/firmware/nvidia/
