Re: [PATCH v11 00/12] gpu: nova-core: add Turing support

[Timur Tabi <ttabi@nvidia.com>]

On Mon, 2026-03-09 at 13:29 -0700, John Hubbard wrote:
> On 3/9/26 1:18 PM, Timur Tabi wrote:
> > On Mon, 2026-03-09 at 13:04 -0700, John Hubbard wrote:
> > > 
> > > I have that exact card available, so I'll give this a quick test and see
> > > what's missing or wrong, now that Alex has pushed the entire Turing support
> > > set up to drm-rust-next.
> > 
> > The TU117 is technically a mobile chip, and its VBIOS is different.  My initial version of the
> > Turing patches would "ignore" the problematic VBIOS sections, so perhaps this changed.
> > 
> 
> No repro on the latest drm-rust-next branch:
> 
> NovaCore 0000:e1:00.0: Probe Nova Core GPU driver.
> NovaCore 0000:e1:00.0: NVIDIA (Chipset: TU117, Architecture: Turing, Revision: a.1)
> NovaCore 0000:e1:00.0: Found BIOS image: size: 0xe600, type: Ok(PciAt), last: false
> NovaCore 0000:e1:00.0: Found BIOS image: size: 0x11000, type: Ok(Efi), last: false
> NovaCore 0000:e1:00.0: Found BIOS image: size: 0xc200, type: Ok(FwSec), last: false
> NovaCore 0000:e1:00.0: Found BIOS image: size: 0x22400, type: Ok(FwSec), last: false
> NovaCore 0000:e1:00.0: Invalid signature for NpdeStruct: [1, 1, 66, 86]
> NovaCore 0000:e1:00.0: Invalid signature for NpdeStruct: [1, 1, 66, 86]

So this is the problematic section that gets ignored.  It's on my TODO list to fix this, but last
time I looked at it, the documentation I had on the VBIOS layout did not align with the VBIOS on my
TU117.

> [    2.246095] NovaCore 0000:01:00.0: NVIDIA (Chipset: TU117, Architecture: Turing, Revision: a.1)
> [    2.722681] NovaCore 0000:01:00.0: Booter-load failed with error 0x31
> 
> However nouveau does not probe either with this firmware so that's not
> really this patchset fault.

So Booter-load error 0x31 means that Booter technically did start, but it aborted very early. 
Unfortunately, this is very difficult to debug in the field.  Normally what I would do is build
custom versions of booter-load to see where it fails.  I cannot do this without the card in my hand.

The first thing I would do is verify that GspFwWprMeta does not have nonsensical values.