From: "Ewan Chorynski" <ewan.chorynski@ik.me>
To: "Timur Tabi" <ttabi@nvidia.com>,
"ewan.chorynski@ik.me" <ewan.chorynski@ik.me>,
"Alexandre Courbot" <acourbot@nvidia.com>,
"dakr@kernel.org" <dakr@kernel.org>,
"aliceryhl@google.com" <aliceryhl@google.com>,
"airlied@gmail.com" <airlied@gmail.com>,
"John Hubbard" <jhubbard@nvidia.com>,
"simona@ffwll.ch" <simona@ffwll.ch>
Cc: "Alistair Popple" <apopple@nvidia.com>,
"Eliot Courtney" <ecourtney@nvidia.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"rust-for-linux@vger.kernel.org" <rust-for-linux@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>,
"Joel Fernandes" <joelagnelf@nvidia.com>,
"Edwin Peer" <epeer@nvidia.com>
Subject: Re: [PATCH v11 00/12] gpu: nova-core: add Turing support
Date: Mon, 09 Mar 2026 22:16:43 +0100 [thread overview]
Message-ID: <DGYKAXUZE263.3VQZGY7KJ5FEY@ik.me> (raw)
In-Reply-To: <5390ee90b722b29e686d948bc855da1eb62a4f6b.camel@nvidia.com>
On Mon Mar 9, 2026 at 10:05 PM CET, Timur Tabi wrote:
> On Mon, 2026-03-09 at 22:00 +0100, Ewan Chorynski wrote:
>> On Mon Mar 9, 2026 at 9:29 PM CET, 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:
>>
>> I guess I may have an issue with my linux-firmware. I have no stable
>> right now so I can't download the latest one but I'll try
>> soon. On which commit on linux-firmware are you ?
>
> There's only one version of linux-firmware that works with Nova, and you didn't have it, it wouldn't
> boot at all.
>
> Although, now that I think about it, I'm assuming that on Turing, if gen_bootloader is absent,
> NovaCore will not even try to boot. That file was added recently and is missing in most distros
> today.
>
> /lib/firmware/nvidia/tu102/gsp/gen_bootloader-570.144.bin (or its zstd compressed version)
>
> If you have this file, then you have everything you need to boot NovaCore on Turing.
I had this file installed but I think I broke something when I updated.
I tried to redo my installation from the tarball I had and now it is
probing, so the issue was indeed on my side with my firmware.
Thanks for trying the repro and sorry for the false alarm.
Have a good day
Ewan
next prev parent reply other threads:[~2026-03-09 21:16 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 4:52 Alexandre Courbot
2026-03-06 4:52 ` [PATCH v11 01/12] gpu: nova-core: create falcon firmware DMA objects lazily Alexandre Courbot
2026-03-06 4:52 ` [PATCH v11 02/12] gpu: nova-core: falcon: add constant for memory block alignment Alexandre Courbot
2026-03-06 4:52 ` [PATCH v11 03/12] gpu: nova-core: falcon: rename load parameters to reflect DMA dependency Alexandre Courbot
2026-03-06 6:23 ` Eliot Courtney
2026-03-06 4:52 ` [PATCH v11 04/12] gpu: nova-core: falcon: remove FalconFirmware's dependency on FalconDmaLoadable Alexandre Courbot
2026-03-06 4:52 ` [PATCH v11 05/12] gpu: nova-core: move brom_params and boot_addr to FalconFirmware Alexandre Courbot
2026-03-06 4:52 ` [PATCH v11 06/12] gpu: nova-core: add PIO support for loading firmware images Alexandre Courbot
2026-03-06 4:52 ` [PATCH v11 07/12] gpu: nova-core: falcon: remove unwarranted safety check in dma_load Alexandre Courbot
2026-03-06 4:52 ` [PATCH v11 08/12] gpu: nova-core: firmware: add comments to justify v3 header values Alexandre Courbot
2026-03-09 4:54 ` Eliot Courtney
2026-03-06 4:52 ` [PATCH v11 09/12] gpu: nova-core: firmware: fix and explain v2 header offsets computations Alexandre Courbot
2026-03-09 4:55 ` Eliot Courtney
2026-03-09 12:10 ` Gary Guo
2026-03-10 1:49 ` Alexandre Courbot
2026-03-06 4:52 ` [PATCH v11 10/12] gpu: nova-core: make Chipset::arch() const Alexandre Courbot
2026-03-06 4:52 ` [PATCH v11 11/12] gpu: nova-core: add gen_bootloader firmware to ModInfoBuilder Alexandre Courbot
2026-03-06 4:52 ` [PATCH v11 12/12] gpu: nova-core: use the Generic Bootloader to boot FWSEC on Turing Alexandre Courbot
2026-03-09 5:07 ` Eliot Courtney
2026-03-09 1:52 ` [PATCH v11 00/12] gpu: nova-core: add Turing support Alexandre Courbot
2026-03-09 2:06 ` John Hubbard
2026-03-09 2:20 ` Alexandre Courbot
2026-03-09 19:48 ` Ewan Chorynski
2026-03-09 20:04 ` John Hubbard
2026-03-09 20:18 ` Timur Tabi
2026-03-09 20:29 ` John Hubbard
2026-03-09 20:39 ` Timur Tabi
2026-03-09 21:00 ` Ewan Chorynski
2026-03-09 21:05 ` Timur Tabi
2026-03-09 21:16 ` Ewan Chorynski [this message]
2026-03-09 21:22 ` Timur Tabi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DGYKAXUZE263.3VQZGY7KJ5FEY@ik.me \
--to=ewan.chorynski@ik.me \
--cc=acourbot@nvidia.com \
--cc=airlied@gmail.com \
--cc=aliceryhl@google.com \
--cc=apopple@nvidia.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=ecourtney@nvidia.com \
--cc=epeer@nvidia.com \
--cc=jhubbard@nvidia.com \
--cc=joelagnelf@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=ttabi@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®