Benjamin, could you do a test for us (with my custom kernel build) ?
We want to determine what happens when this option is enabled but the firmware
cannot be found. I tried to determine it from the source-code but there are so
many levels of indirection it will be easier to simply test.
The firmware for TU117 GSP is sym-linked to the TU116, that is in turn
sym-linked to TU102 files. So, to *temporarily, for this test only* prevent
that firmware being found do:
$ sudo mv /usr/lib/firmware/nvidia/tu102/gsp/gsp-535.113.01.bin{,.disabled}
Then check the tu117 sym-link is now broken:
$ realpath -e /usr/lib/firmware/nvidia/tu117/gsp/gsp-535.113.01.bin
realpath: /usr/lib/firmware/nvidia/tu117/gsp/gsp-535.113.01.bin: No such file
or directory
Reboot and share the kernel log. I'm hoping it falls back to the VBIOSInit
routine and you see the same messages we saw originally, with those "table '*'
not found" messages.
To reinstate the firmware file do:
$ sudo mv /usr/lib/firmware/nvidia/tu102/gsp/gsp-535.113.01.bin{.disabled,}
$ realpath -e /usr/lib/firmware/nvidia/tu117/gsp/gsp-535.113.01.bin
/usr/lib/firmware/nvidia/tu102/gsp/gsp-535.113.01.bin
