(omg)vflash | Fully Patched nvflash from X to Ada Lovelace [v5.780]

[StViolenceDay]

change on-boot description in PMID

I tried changing this ascii on-boot description followed PMID in 3 ways for my 1070ti:
Variant 1. Just swap to letters with each other. For this case Mobile TDP Tweaker shows that 32-bit checksum doesn't change. Flashing 1070ti failed - here is the part of detailed output got directly on-screen by using "-L con" extended logging flag
.\OMGVflash.exe -6 .\1070ti-modded.rom -L con

BCRT: Start Certificate 2.0 verification
Send VV Command...
Command id: 0x3000000E Command: NV_UCODE_CMD_COMMAND_VV failed
Command Status: NV_UCODE_CMD_STS_COMPLETE
Error Code = 0x00000011(17): NV_UCODE_ERR_CODE_CMD_VBIOS_VERIFY_BIOS_SIG_FAIL

Cert info block will be finalized during flash process.
Program page  Start: 0x00000000 Count: 0x2000(8192)
Command id: 0x30000005 Command: NV_UCODE_CMD_COMMAND_EWR failed
Command Status: NV_UCODE_CMD_STS_COMPLETE
Error Code = 0x0000006C(108): NV_UCODE_ERR_CODE_CMD_EWR_OK_TO_FLASH_CHECK_FAILED

Variant 2. Edit single letter. Mobile TDP Tweaker shows that 32-bit checksum is changed. Tryied flashing without fixing it - same error.
Variant 3. Edit single letter. Mobile TDP Tweaker shows that 32-bit checksum is changed, use the Quick Fix. Now the 32nit checksum is the same. Tryied flashing such quick-fixed VBIOS - same error

Do you have any of those mod variants working on 1080ti? If yes - may be there is some different code paths inside *flash.exe for 1080ti and 1070ti, and the 1070ti has another behaviour.
Unfortunately I haven't 1080ti at hand to test.


EDIT 1
Also I performed an experiment with "Just flash normal unmodded 1070 VBIOS into 1070ti". Flashing also fails, with another error:

BCRT: Start Certificate 2.0 verification
Send VV Command...
Cert info block will be finalized during flash process.
Program page  Start: 0x00000000 Count: 0x0A00(2560)
Command id: 0x30000005 Command: NV_UCODE_CMD_COMMAND_EWR failed
Command Status: NV_UCODE_CMD_STS_COMPLETE
Error Code = 0x0000005A(90): NV_UCODE_ERR_CODE_DEVID_MATCH_LIST_DEVID_MATCH_FAILED
Device ID in the rom image does not match the device ID in the chip.
Update aborted, please use a rom image that supports device ID 0x1B82.

 

[Deleted member 218758]

Do you have any of those mod variants working on 1080ti? If yes

Yes, Variant 2 works. Code 43 but works

Do not use Mobile TDP tweaker for rom changes, only for visualization.
Its location of 32bit checksum only aligns on mobile 1070/1080 bioses.

I will comment more soon
I know more people work on a viewer and editor.
Even being threaten by private-messages if they should publish stuff or not. "To not endanger my little project"
Setting the foundation here was important;

Don't only let me be the one who pushes forward
It's been many years of "nothing doing" or developers being bought-off left and right.
If you only wait for me, we won't move forward.
I have to keep some stuff private. Due to different/multiple reasons.

Also I performed an experiment with "Just flash normal unmodded 1070 VBIOS into 1070ti". Flashing also fails, with another error:

I will check closer, thank you

---

---

Dear @Veii,
Do you plan to post linux version since some of us are no longer microsoft bound...
Thank you.

I got so far 3 reports of failures:
~ USB FW issue on 2080Ti Winbound SW WriteProtect 1E03/4 (LHR included) & 1E2B (Engineering) // knew that one before publishing, i needed more time
The Falcon lock on ISSI 2080Ti has fallen and likely also different cards with ISSI EEPROM (1E07).
~ 4090 (AD102-301) Type A refuses to flash , identification error. Wip, collecting data of the issue. Resolved
~ TitanX/XP to 1080ti crossflash issues & now more Pascal CID crossflash issues.

There is work to do
I will see that i patch Pascal first, and fix my little mistakes.
If not possible, i might need to redo everything and update to 4.814.
If end up doing and deciding that full cert bypass is needed (but this breaks support for Workstation Class GPUs)
Any case, first sorting out issues i can ~ with Hardware i have here (Pascal)
Then working further on Turing if possible & once bugs are resolved ~ i'll redo it on linux
Falcon @ linux is more friendly to work with.
I'm working at the same time in getting biosmods to boot on Pascal and Turing. Custom memtimings included.

If you can, please upload me the current compiled nvflash-linux , both if possible 4.780 & 4.814.
Similar branch to 4.780 windows ~ will speed up transfering over patches.

Sadly i'm with limited/weak gear & fully decompiling nvflash eats over 32gb RAM.
Its huge.
With mapping out progress i'm only at 2/20 , or ~30/200 commands.
Its really huge.
Soo it will need some time

Please everyone , upload logs the way @StViolenceDay described
And/or simple pictures of -6 romname.exe & upon failure another attempt with just -A romname.exe.
Successes and failures, everything is of value.
Thanks guys~

 

[Surgical]

As a average consumer/gamer that is not into exstreme overclocking etc. I am asking the following question for others reading in the future to understand what this can mean for us.

In my case I have a GTX 1060 6GB. If someone uses this and compiles a ROM for example my card can this the possibly allow me/others to use something like DLSS on my older card or would something like this be helpful to finally be able to have better Nvidia drivers for linux gaming on like SteamOS as an example?

 

[Deleted member 218758]

As a average consumer/gamer that is not into exstreme overclocking etc. I am asking the following question for others reading in the future to understand what this can mean for us.

In my case I have a GTX 1060 6GB. If someone uses this and compiles a ROM for example my card can this the possibly allow me/others to use something like DLSS on my older card or would something like this be helpful to finally be able to have better Nvidia drivers for linux gaming on like SteamOS as an example?

I'll try to keep it short:

Its main goal is to lay a foundation for Bios editing and access to falcon
This includes every 3rd party tool which accesses the cards through falcon & mutex api ~ through nvflash.
That is // Afterburner, ProjectHydra, Boardpartner Tools like GALAX/EVGA control tools.

2ndary,
The free ability to talk with falcon without the need for a Engineers Bios card with engineers Certificate (in ROM)
Without the need of proprietary NVIDIA software. NVFlash is used by nvidia , by our boardpartners and by us the users.
NVFlash itself decides how much permissions to give you , up to the ROM and card you currently have in the system.
Or if you know its secret commands.

3rd,
Bypass and break SW locks that prevent flashing.
It's kind of like 1.) but for normal users.
Vendor rebrand, FE rebrand, just enthusiast level of functionality.

---

DLSS and anything related to Ray Tracing, needs RT cores.
DLSS itself is halfway in software with device identifier checks.
There are couple projects on github with FRS2.0 to DLSS and also in reverse ~ for games who support this.

The most important for us, is modification on ROM level and the basic "ability" of doing something at all.

What we can do so far:
Geforce - 4000 series, SSID rebrand, PCI_ID rebrand, BoardID rebrand, EngCard rebrand to final-state cards (but wip, bugfixing)
Geforce - 2000 series, Biosmod flash (with potential CID rebrand ability) + free talk with Falcon.
// No certcheck but full full version wasnt pushed out yet - too buggy and too high chance of being sued. Also lacks needed goodies, that public nvflash doesnt have.

Pro-Enthusiasts need to work together on pushing baseline higher than Pascal & Turing
Normal enthusiasts and overclocker, can enjoy the free flash ability of public-signed XOC bioses ~ till Ada-Lovelace
Normal prosumer & overclocker, can rebrand their FE's and potentially skip some softlocks, like voltage limiters ~ till Ada-Lovelace
Everything bellow Pascal is 100% unlocked and the wild-west. Don't be stupid and jump 3-5 generations like i do (650 to 1030)

Once 1000/2000 series has community made viewers/editors;
// Bios-Viewers can be made till 4000 series. No issues there. Rom-modding will stop at 2000 series.
We can work on adding BAR support back.
It is possible, but it is a lot of work and way beyond my novice abilities.
For the last part, please nicely ask https://github.com/xCuri0/ReBarUEFI
She is much more talented than me, and could maybe find inspiration to work on this ~ once Pascal/Turing ROM edits are accepted.

 

[horace824]

HI im getting this:

NVIDIA Firmware Update Utility (Version 5.780.0)
Copyright (C) 1993-2022, NVIDIA Corporation. Veii Extreme Edition

Checking for matches between display adapter(s) and image(s)...

WARNING: Firmware image version (86.06.3C.40.1F) is not newer
         than the existing firmware (86.06.59.00.88).
WARNING: Firmware image PCI Subsystem ID (19DA.2438)
  does not match adapter PCI Subsystem ID (1462.3287).

Downgrading/Sidegrading firwmare detected.
(This is usually only needed for very special circumstances.)

Are you sure you want to continue?
Type "YES" to confirm (all caps):

YES

Downgrade/Sidegrade is permitted.

You are intending to override PCI Subsystem ID.
Are you sure you want to continue?
Press 'y' to confirm (any other key to abort): y
Overriding the PCI Subsystem ID mismatch.
Current      - Version:86.06.59.00.88 ID:10DE:1C02:1462:3287
               GP106 Board (Normal Board)
Replace with - Version:86.06.3C.40.1F ID:10DE:1C02:19DA:2438
               GP106 Board (Normal Board)

Update display adapter firmware?
Press 'y' to confirm (any other key to abort):

Nothing changed!

i used the pascal bios modder thing to xhange power limit and get this error



PROGRAMMING ERROR: EEPROM Program failed

i used the pascal bios modder thing to xhange power limit and get this error

 

[[scarb]]

this is absolutely amazing. i've only been part of the pc building community for 2 years, so i didnt even know this was ever a thing.
i wonder if i could some how use it on a laptop gpu?

 

[dartraiden]

Trying to flash Gigabyte P106-100 with BIOS from Gigabyte 1060 Windforce.

OMGVflash -6 Gigabyte.GTX1060.6144.170506.rom -L log.txt

Response:

BCRT: Start Certificate 2.0 verification
Send VV Command...
Cert info block will be finalized during flash process.
Program page  Start: 0x00000000 Count: 0x0A00(2560)
Command id: 0x30000005 Command: NV_UCODE_CMD_COMMAND_EWR failed
Command Status: NV_UCODE_CMD_STS_COMPLETE
Error Code = 0x0000005A(90): NV_UCODE_ERR_CODE_DEVID_MATCH_LIST_DEVID_MATCH_FAILED
Device ID in the rom image does not match the device ID in the chip.
Update aborted, please use a rom image that supports device ID 0x1C07.

 

[SakuraSamurai]

So I ran it with --check and it just restarted the graphics driver? Is that normal? No errors, but no success messages either.

I have a Quadro P4000 8GB (MXM 3.0b | Pascal) so I don't really know what BIOS I could try since the P5000 has 16GB of VRAM.

 

[Domrockt]

Soooo what about SR-IOV? Is there an „activate“ Button?

 

[Sambrownie]

Yes, Variant 2 works. Code 43 but works

Do not use Mobile TDP tweaker for rom changes, only for visualization.
Its location of 32bit checksum only aligns on mobile 1070/1080 bioses.

I will comment more soon
I know more people work on a viewer and editor.
Even being threaten by private-messages if they should publish stuff or not. "To not endanger my little project"
Setting the foundation here was important;
View attachment 310153View attachment 310154
Don't only let me be the one who pushes forward
It's been many years of "nothing doing" or developers being bought-off left and right.
If you only wait for me, we won't move forward.
I have to keep some stuff private. Due to different/multiple reasons.

I will check closer, thank you

---

---

I got so far 3 reports of failures:
~ USB FW issue on 2080Ti Winbound SW WriteProtect 1E03/4 (LHR included) & 1E2B (Engineering) // knew that one before publishing, i needed more time
The Falcon lock on ISSI 2080Ti has fallen and likely also different cards with ISSI EEPROM (1E07).
~ 4090 (AD102-301) Type A refuses to flash , identification error. Wip, collecting data of the issue.
~ TitanX/XP to 1080ti crossflash issues & now more Pascal CID crossflash issues.

There is work to do
I will see that i patch Pascal first, and fix my little mistakes.
If not possible, i might need to redo everything and update to 4.814.
If end up doing and deciding that full cert bypass is needed (but this breaks support for Workstation Class GPUs)
Any case, first sorting out issues i can ~ with Hardware i have here (Pascal)
Then working further on Turing if possible & once bugs are resolved ~ i'll redo it on linux
Falcon @ linux is more friendly to work with.
I'm working at the same time in getting biosmods to boot on Pascal and Turing. Custom memtimings included.

If you can, please upload me the current compiled nvflash-linux , both if possible 4.780 & 4.814.
Similar branch to 4.780 windows ~ will speed up transfering over patches.

Sadly i'm with limited/weak gear & fully decompiling nvflash eats over 32gb RAM.
Its huge.
With mapping out progress i'm only at 2/20 , or ~30/200 commands.
Its really huge.
Soo it will need some time

Please everyone , upload logs the way @StViolenceDay described
And/or simple pictures of -6 romname.exe & upon failure another attempt with just -A romname.exe.
Successes and failures, everything is of value.
Thanks guys~

Unfortunately I have no such old version...

 

[heavyarms2112]

@Veii when would you get this error message?

PROGRAMMING ERROR: Reading EEPROM status register failed
 Nvflash CPU side error Code:2Error Message: Falcon In HALT or STOP state, abort uCode command issuing process.
Exit Code: 2

Full log

Product name:NVIDIA GeForce GTX 1660 SUPERDID:0x21C410DE - SSID:0x37961028 - Pastebin.com

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

pastebin.com

Do we need to flash it in UEFI OS?

 

[Deleted member 218758]

Full log

Thank you.
I see~

This is worrysome.
I will need that version that i didn't want to release.
What a trouble.

I can resolve that but at what cost.
Lets wait it out and see.

Do we need to flash it in UEFI OS?

Nono, its just falcon denying.
Its not the "falcon forced to deny", vbios issue ~ well half

I will try to find a middle ground
But releasing that is begging for a takedown.
Let me first fix the other issues before considering what to do here.
And maybe i'll find another way to resolve that.

EDIT:
Please try to downgrade vbios version & and it might resolve too

EDIT2:
https://www.techpowerup.com/vgabios/214983/gigabyte-gtx1660super-6144-190918 this likely flashes @heavyarms2112
Should be ok as downgrade
What is the current bios you run - what powerlimit on that 1660 Super ?
Please tell me your exact model with a GPU-Z screenshot.
On 1000 series, if you missmatch 8pin amount or display out - you'll softbrick the card
Display matrix is ok as long as one port is correct, but if nothing is correct you softbrick it too. Same for memory amount
Only 3000 series does autocorrect.

 

[Wotwow]

Falcon this is GSP. GSP this is Guardian Service Processor.

Small recommendations:
Use the BIOS version to search the BIOS by the first 8 digits.
For example your bios: 90.04.7A.00.6A
Suitable for firmware: 90.04.7A.00.69
Not suitable for firmware: 90.04.7A.80.B2

There is line RTX 2080 in the BIOS with the PCB version of your board, download all the BIOSes and look for the same BIOS on this line.
This will give you a guarantee that the video card will work for a long time. Pay special attention to memory speed, It is possible to damage the memory of the video card.

I forgot to write that Nvidia will probably disable this tool soon.
Personally, I delete GSP (Falcon) firmware files in drivers.
The GSP firmware files are gsp_tu10x.bin and gsp_ga10x.bin.
Good luck.

 

[heavyarms2112]

Thank you.
I see~

This is worrysome.
I will need that version that i didn't want to release.
What a trouble.

I can resolve that but at what cost.
Lets wait it out and see.

Nono, its just falcon denying.
Its not the "falcon forced to deny", vbios issue ~ well half

I will try to find a middle ground
But releasing that is begging for a takedown.
Let me first fix the other issues before considering what to do here.
And maybe i'll find another way to resolve that.
View attachment 310172

EDIT:
Please try to downgrade vbios version & and it might resolve too

EDIT2:
https://www.techpowerup.com/vgabios/214983/gigabyte-gtx1660super-6144-190918 this likely flashes @heavyarms2112
Should be ok as downgrade
What is the current bios you run - what powerlimit on that 1660 Super ?
Please tell me your exact model with a GPU-Z screenshot.
On 1000 series, if you missmatch 8pin amount or display out - you'll softbrick the card
Display matrix is ok as long as one port is correct, but if nothing is correct you softbrick it too. Same for memory amount
Only 3000 series does autocorrect.

Thanks for the inputs. It's a Dell OEM1660 Super. 1 x 6-pin. The gigabyte seems to have 1 x 8-pin.

https://i.ebayimg.com/images/g/mkoAAOSwnfhjYks4/s-l1600.jpg

I'm trying to change memory strap on it.
Attached original bios on the card & gpu-z screenshot

 

[notoperable]

I don't get it. How is that better in terms of what allowed or not?
Its not like all of the sudden, say (and correct me if I am wrong), for example:
GeForce 3080, SKU 200-0 will now all of the sudden be able to use a VBIOS
released GeForce 3080, SKU 220 - Because I can flash any SKU 200-0 Vbios
from Vendor A to Vendor B - So I don't understand what's the magic here?

Flashing non-OC to OC bios on GeForce 30x0 was possible since nvflash v.5.6.92,
just add a -6 flag and as long as the SKU matches it will flash the bios and 29 times
out of 30 your card will work. I got an not-so-great 3080 from Dell (Omen 15) and
I flashed it basically with 30+ different bioses to peek-a-boo at some stuff after the
nvidia leak (which included bunch of juicy details how the signing works btw.) but
nvflash wont allow you to flash incompatible SKU iterations.

Basically, running > nvflash --version some.nifty.rom will spit 2 lines:

Chip SKU: 200-0
Project: G132-0030

and comparing it with your current running one VBIOS works as long as those 2 values above match
each other - in other words, as long as those match you can flash whatever you find in the database,
just add -6 param to it and use nvflash 5814 or 5692 - versions between crap out on and wont
detected the gpu properly (whatever linux or windows)

For example, flashing VBIOS for a SKU 220 on a 200-0 SKU is not possible (but also for a good reason)
Also, VBIOS from a 16GB card witha complete different memory channel layout is also a very bad idea.
But I maybe am missing the magic here. Sure, flash modded BIOS for 30x0 was not possible, as long as
the checksum wont verify - no-go, so swapping UEFI for a newer module was not possible. Still, VBIOS
is encrypted in the end so no magic modding tool will happen

 

[Deleted member 218758]

I'm trying to change memory strap on it.

Ah, thats why you fail on signature errors
I thought its on stock.

I'll inspect it later

I forgot to write that Nvidia will probably disable this tool soon.

It's their tool.
We in the current state barely differ from what GALAX publicly announced.
I move in a thin line, but its alright for now.
If i need to play with falcon, then we have a potential issue.
I know my place

i used the pascal bios modder thing to xhange power limit and get this error

Pascal TDP Mobile modder has no support for consumer GPUs
Programm still has a checksum file check left in place.
So user doesnt flash unbootable stuff. You triggered it.

~ 4090 (AD102-301) Type A refuses to flash , identification error. Wip, collecting data of the issue.

Resolved
4090 Type-A flashed.

 

[notoperable]

Does not compute ()
Like I mentioned in my previous post- I don't get what's the benefit there, checked with SKU 200 -> SKU 202 and
it won't go through (same what happens to other patched nvflash versions)

What am I missing?

 

[Wotwow]

Also, VBIOS from a 16GB card witha complete different memory channel layout is also a very bad idea.

Above I wrote how to find a suitable BIOS.
Different BIOSes have different video card memory voltages.
Therefore, BIOSes have different versions that are designed for different manufacturers of video memory.
Video cards with the wrong bios work, but after a year their memory starts to fall off.

 

[Deleted member 218758]

What am I missing?

Reboot
--protectoff
and try again with -6

You wont pass flash with an official version
if one flash fails, you can need a reboot

GeForce 3080, SKU 200-0 will now all of the sudden be able to use a VBIOS
released GeForce 3080, SKU 220 - Because I can flash any SKU 200-0 Vbios
from Vendor A to Vendor B

GA102-200 -> GA102-220
Will fail because 320 Bit vs 384 Bit Buswidth
10 vs 12gb is adaptive and fixed on rom level.

GA102-220-A1 vs GA102-225-A1 (Shader diff) is fixable (maybe not supported, but realistic to be)

GA102-200A1 vs GA102-202-A1 ~ unsure about the difference, but likely too
GA104-400 vs GA104-401 ~ likely too but also not because mem layout , with a mod yes.

You have an edge case scenario , because you already run a consumer Card.
You dont run neither a reference card, nor can mod the bios.
There is no need of specific rebrand usage, but nvflash is much more than that.
Have you ever used MSI Afterburner ? Also based on partial functionality of nvflash.

EDIT:
Any case, you attempt hardrebrand, when it was said "only till 2000 series"
No CID rebrands past Turing. Within Turing and Pascal - seems to need some bugfixing.
You're at the mercy of Falcon. Nvflash does its job sending the full flash command.

---

If falcon modification is allowed by the user, tool will be taken down. Because several reasons - majorly "security".
People are open to modify it and take away weight of my shoulders. Falcon talk ability exists. Go experiment
We also still need a bios viewer and editor.
If everyone waits on me, it won't happen soon. Go make it
The tools to fullflash a rom exist. SPI is not a full flash.

 

[t3rbin]

maybe I'm about to write the obvious, but someone still might not have figured out how to fix stupid 8 bit crc. you can use HxD to calculate it on the selection. open the calculator and set in hex - byte, subtract the obtained value from HxD to 0.

 

[Deleted member 218758]

Now lets find 32bit one
8 bit is nicely separated
There are 4 x 8bit ones, and two which are important - top and bottom header.
32bit is a bigger annoyance.

Does not compute ()

Can you give a -L log.txt too ?
A full one please.
But yes, no CID modification on/for newer Ampere & onwards. It will fail due to cert trouble and generally falcon access trouble.
Not nvflash's fault, it just forwards, attempts but will fail.

 

[t3rbin]

Now lets find 32bit one
8 bit is nicely separated
There are 4 x 8bit ones, and two which are important - top and bottom header.
32bit is a bigger annoyance.

but for the 32-bit one, isn't it enough to bring the bill and subtract (all the ones you added) in the text area? I thought that was simple too...

 

[Mussels]

Downside: welcome to the same shit AMD has dealt with and second hand GPUs being fakes/modded to death

I'm all for being able to mod our cards, but seeing the things done in bulk due to eth mining has really soured me to it.

 

[Wotwow]

I made bios rtx 2080 Super Bigben.

Those. I changed part of the professional card and inserted it into the bios rtx.
Your program flashed it, it did not find any changes in the certificate. Here is the log:

Spoiler: Log1

Product name:NVIDIA GeForce GTX 1660 SUPER
DID:0x21C410DE - SSID:0x40121458
Product name:NVIDIA GeForce RTX 2080 SUPER
DID:0x1E8110DE - SSID:0x13A110DE

NV Driver Version : 53709
<0>: DisplayID = 00000800
Pad(0/8): DispMask=00000000, MODE=I2C, USED=Used, PWR=OFF
Pad(1/8): DispMask=00000300, MODE=AUX, USED=Used, PWR=OFF
Pad(2/8): DispMask=00000400, MODE=I2C, USED=Used, PWR=OFF
Pad(3/8): DispMask=00001800, MODE=AUX, USED=Used, PWR=ON
Pad(4/8): DispMask=00006000, MODE=AUX, USED=Used, PWR=OFF
Pad(5/8): DispMask=00000000, MODE=I2C, USED=Used, PWR=OFF
Pad(6/8): DispMask=00000000, MODE=I2C, USED=Used, PWR=OFF
Pad(7/8): DispMask=00000000, MODE=AUX, USED=Unused, PWR=OFF
Counts of USB-C connected monitor : 00
Disable D3 cold capability before unloading driver...

Disable D3 cold capability successfully on GPU index 0x00.
Disable D3 cold capability successfully on GPU index 0x01.
*** NVFLASH LOG FILE ***
Command-line : -i1 -6 TU104BIG.rom -L oo.lof
NVIDIA Firmware Update Utility (Version 5.780.0)
Copyright (C) 1993-2022, NVIDIA Corporation. Veii Extreme Edition

Command: flash
FindDevices:
Device:0000:00:00:00=1022:1480:1022:1480
Device:0000:00:00:02=1022:1481:1022:1481
Device:0000:00:01:00=1022:1482:0000:0000
Device:0000:00:01:01=1022:1483:FFFF:FFFF
Device:0000:00:01:02=1022:1483:FFFF:FFFF
Device:0000:00:02:00=1022:1482:0000:0000
Device:0000:00:03:00=1022:1482:0000:0000
Device:0000:00:03:01=1022:1483:FFFF:FFFF
Device:0000:00:04:00=1022:1482:0000:0000
Device:0000:00:05:00=1022:1482:0000:0000
Device:0000:00:07:00=1022:1482:0000:0000
Device:0000:00:07:01=1022:1484:FFFF:FFFF
Device:0000:00:08:00=1022:1482:0000:0000
Device:0000:00:08:01=1022:1484:FFFF:FFFF
Device:0000:00:14:00=1022:790B:1022:790B
Device:0000:00:14:03=1022:790E:1022:790E
Device:0000:00:18:00=1022:1440:0000:0000
Device:0000:00:18:01=1022:1441:0000:0000
Device:0000:00:18:02=1022:1442:0000:0000
Device:0000:00:18:03=1022:1443:0000:0000
Device:0000:00:18:04=1022:1444:0000:0000
Device:0000:00:18:05=1022:1445:0000:0000
Device:0000:00:18:06=1022:1446:0000:0000
Device:0000:00:18:07=1022:1447:0000:0000
Device:0000:01:00:00=15B7:5002:15B7:5002
Device:0000:02:00:00=1022:43EE:1B21:1142
Device:0000:02:00:01=1022:43EB:1B21:1062
Device:0000:02:00:02=1022:43E9:FFFF:FFFF
Device:0000:03:00:00=1022:43EA:FFFF:FFFF
Device:0000:03:06:00=1022:43EA:FFFF:FFFF
Device:0000:03:07:00=1022:43EA:FFFF:FFFF
Device:0000:03:09:00=1022:43EA:FFFF:FFFF
Device:0000:04:00:00=10DE:21C4:1458:4012 GPU
Device:0000:04:00:01=10DE:1AEB:1458:4012
Device:0000:04:00:02=10DE:1AEC:1458:4012
Device:0000:04:00:03=10DE:1AED:1458:4012
Device:0000:05:00:00=1D89:0160:1D89:0160
Device:0000:06:00:00=10EC:8168:1462:7C91
Device:0000:2A:00:00=10EC:8125:1462:7C91
Device:0000:2B:00:00=10DE:1E81:10DE:13A1 GPU
Device:0000:2B:00:01=10DE:10F8:10DE:13A1
Device:0000:2B:00:02=10DE:1AD8:10DE:13A1
Device:0000:2B:00:03=10DE:1AD9:10DE:13A1
Device:0000:2C:00:00=1022:148A:1022:148A
Device:0000:2D:00:00=1022:1485:1022:1485
Device:0000:2D:00:01=1022:1486:1022:1486
Device:0000:2D:00:03=1022:149C:1022:148C
Device:0000:2D:00:04=1022:1487:1462:EC91
Filter-out on-motherboard PLX bridge device.
No PLX/PEX switch was detected, skip to filter-out non-NVIDIA PLX/PEX switch.
One to one mode
Testing adapter: NVIDIA GeForce RTX 2080 SUPER (10DE,1E81,10DE,13A1) S:00,B:2B,D:00,F:00

Disable NV driver before start if NV driver loaded.




The NVFlash succeed to disable the NV Driver automatically.
Failed to raise ROM and uC perf clocks.
Flashing on blank EEPROMs will be slow.
Adapter: NVIDIA GeForce RTX 2080 SUPER (10DE,1E81,10DE,13A1) S:00,B:2B,D:00,F:00

Identify EEPROM.
Action: Identify EEPROM.
uproc 05 ucode is not found for this GPU.
uproc 02 ucode is not found for this GPU.
uproc 04 ready to be used.
Preparing secure operation after kicked start.
Actual SPI clock frequency (Hz): 18000000
Serial EEPROM identified.
EEPROM ID (9D,7014) : ISSI IS25WP080 1.65-1.95V 8192Kx1S, page

Action: Identify EEPROM.
Serial EEPROM identified.
EEPROM ID (9D,7014) : ISSI IS25WP080 1.65-1.95V 8192Kx1S, page

Action: Read EEPROM image.
Reading EEPROM bytes.
Start: 0x00000000
Count: 1048576(0x00100000)
Read complete.

Testing Image: TU104BIG.rom
IFR image mode
Invalid OTA signed VBIOS firmware image.
Current - Parsed Production VBIOS version: 90.04.7A.00.69
Replace with - Parsed Production VBIOS version: 90.04.7A.00.69

Mismatch Type: Computed: 0x00000300

Downgrading/Sidegrading firwmare detected.
(This is usually only needed for very special circumstances.)

Are you sure you want to continue?
Type "YES" to confirm (all caps):


Downgrade/Sidegrade is permitted.
Mismatch Type: Adjusted: 0x00000000

Current - Version:90.04.7A.00.69 ID:10DE:1E81:10DE:13A1
GPU Board (Normal Board)
Replace with - Version:90.04.7A.00.69 ID:10DE:1E81:10DE:13A1
GPU Board (Normal Board)
Action: Flash image.
Action: Identify EEPROM.
Serial EEPROM identified.
EEPROM ID (9D,7014) : ISSI IS25WP080 1.65-1.95V 8192Kx1S, page

Action: Read EEPROM image.
Reading EEPROM bytes.
Start: 0x00000000
Count: 1048576(0x00100000)
Read complete.
G001.0000.02.04
INFOROM_FLASH_TYPE: 0x04
INFOROM_FLASH_TYPE_NOT_NONE_TO_NONE
Final PCI expansion ROM size is 23552(0x5C00) bytes
Final InfoROM Offset = 0x000D1A00 ( Absolute Offset 0x000FA000)
RFRD Settings | ROMImage | Final |
InfoRomOffset | 0x000FA000 | 0x000FA000 |
InfoRomSize | 0x00004000 | 0x00004000 |

InfoROM Offsets | ROMImage | InputAlt | Final |
NBSI OpRom Offset | 0x0F9E00 | 0x000000 | 0x077C00 |
NPDS Struct Offset | 0x0F9E20 | 0x000020 | 0x0F9E20 |
NPDE Offset | 0x0F9E40 | 0x000040 | 0x0F9E40 |
NBSI DIR Offset | 0x0F9FE0 | 0x000FE0 | 0x0F9FE0 |
JFFS Offset | 0x0FA000 | 0x001000 | 0x0FA000 |
Num of Objects = 7
Num of RW Objects = 2
Size of image with dummy RO blocks = 2688
Num of Objects = 7
Num of RW Objects = 2
Size of image with dummy RO blocks = 2688
Skip proceeding with preservation table for Pascal or newer chip.
EEPROM size: 00100000
Image size: 000FFA00
Unused size: 00000600
Filled size: 00000600

BCRT: Start Certificate 2.0 verification
Send VV Command...
cmd: ROMDIR
Cert info block will be finalized during flash process.
Program page Start: 0x00000000 Count: 0x2000(8192)
Program page Start: 0x00002000 Count: 0x1000(4096)
Program page Start: 0x00004000 Count: 0x2000(8192)
Program page Start: 0x00006000 Count: 0x2000(8192)
Program page Start: 0x00008000 Count: 0x2000(8192)
Program page Start: 0x0000A000 Count: 0x2000(8192)
Program page Start: 0x0000C000 Count: 0x2000(8192)
Program page Start: 0x0000E000 Count: 0x2000(8192)
Program page Start: 0x00010000 Count: 0x2000(8192)
Program page Start: 0x00012000 Count: 0x2000(8192)
Program page Start: 0x00014000 Count: 0x2000(8192)
Program page Start: 0x00016000 Count: 0x2000(8192)
Program page Start: 0x00018000 Count: 0x2000(8192)
Program page Start: 0x0001A000 Count: 0x2000(8192)
Program page Start: 0x0001C000 Count: 0x2000(8192)
Program page Start: 0x0001E000 Count: 0x2000(8192)
Program page Start: 0x00020000 Count: 0x2000(8192)
Program page Start: 0x00022000 Count: 0x2000(8192)
Program page Start: 0x00024000 Count: 0x2000(8192)
Program page Start: 0x00026000 Count: 0x2000(8192)
Program page Start: 0x00028000 Count: 0x0600(1536)
Program page Start: 0x00028600 Count: 0x2000(8192)
Program page Start: 0x0002A600 Count: 0x2000(8192)
Program page Start: 0x0002C600 Count: 0x2000(8192)
Program page Start: 0x0002E600 Count: 0x156E(5486)
Program page Start: 0x0002FB6E Count: 0x0057(87)
Program page Start: 0x0002FBC5 Count: 0x2000(8192)
Program page Start: 0x00031BC5 Count: 0x2000(8192)
Program page Start: 0x00033BC5 Count: 0x2000(8192)
Program page Start: 0x00035BC5 Count: 0x0ADE(2782)
Program page Start: 0x000366A3 Count: 0x0090(144)
Program page Start: 0x00036733 Count: 0x0036(54)
Program page Start: 0x00036769 Count: 0x000D(13)
Program page Start: 0x00036776 Count: 0x0C8A(3210)
Program page Start: 0x00037400 Count: 0x2000(8192)
Program page Start: 0x00039400 Count: 0x2000(8192)
Program page Start: 0x0003B400 Count: 0x2000(8192)
Program page Start: 0x0003D400 Count: 0x2000(8192)
Program page Start: 0x0003F400 Count: 0x2000(8192)
Program page Start: 0x00041400 Count: 0x2000(8192)
Program page Start: 0x00043400 Count: 0x2000(8192)
Program page Start: 0x00045400 Count: 0x2000(8192)
Program page Start: 0x00047400 Count: 0x1000(4096)
Program page Start: 0x00048400 Count: 0x2000(8192)
Program page Start: 0x0004A400 Count: 0x2000(8192)
Program page Start: 0x0004C400 Count: 0x2000(8192)
Program page Start: 0x0004E400 Count: 0x2000(8192)
Program page Start: 0x00050400 Count: 0x2000(8192)
Program page Start: 0x00052400 Count: 0x2000(8192)
Program page Start: 0x00054400 Count: 0x2000(8192)
Program page Start: 0x00056400 Count: 0x2000(8192)
Program page Start: 0x00058400 Count: 0x2000(8192)
Program page Start: 0x0005A400 Count: 0x2000(8192)
Program page Start: 0x0005C400 Count: 0x2000(8192)
Program page Start: 0x0005E400 Count: 0x2000(8192)
Program page Start: 0x00060400 Count: 0x2000(8192)
Program page Start: 0x00062400 Count: 0x2000(8192)
Program page Start: 0x00064400 Count: 0x2000(8192)
Program page Start: 0x00066400 Count: 0x2000(8192)
Program page Start: 0x00068400 Count: 0x2000(8192)
Program page Start: 0x0006A400 Count: 0x2000(8192)
Program page Start: 0x0006C400 Count: 0x2000(8192)
Program page Start: 0x0006E400 Count: 0x2000(8192)
Program page Start: 0x00070400 Count: 0x2000(8192)
Program page Start: 0x00072400 Count: 0x2000(8192)
Program page Start: 0x00074400 Count: 0x1C00(7168)
Program page Start: 0x00076000 Count: 0x0B04(2820)
Program page Start: 0x00076B04 Count: 0x10FC(4348)
Program page Start: 0x00077C00 Count: 0x0400(1024)
Program page Start: 0x00078000 Count: 0x2000(8192)
Program page Start: 0x0007A000 Count: 0x2000(8192)
Program page Start: 0x0007C000 Count: 0x2000(8192)
Program page Start: 0x0007E000 Count: 0x2000(8192)
Program page Start: 0x00080000 Count: 0x2000(8192)
Program page Start: 0x00082000 Count: 0x2000(8192)
Program page Start: 0x00084000 Count: 0x2000(8192)
Program page Start: 0x00086000 Count: 0x2000(8192)
Program page Start: 0x00088000 Count: 0x2000(8192)
Program page Start: 0x0008A000 Count: 0x2000(8192)
Program page Start: 0x0008C000 Count: 0x2000(8192)
Program page Start: 0x0008E000 Count: 0x2000(8192)
Program page Start: 0x00090000 Count: 0x2000(8192)
Program page Start: 0x00092000 Count: 0x2000(8192)
Program page Start: 0x00094000 Count: 0x2000(8192)
Program page Start: 0x00096000 Count: 0x2000(8192)
Program page Start: 0x00098000 Count: 0x2000(8192)
Program page Start: 0x0009A000 Count: 0x2000(8192)
Program page Start: 0x0009C000 Count: 0x2000(8192)
Program page Start: 0x0009E000 Count: 0x2000(8192)
Program page Start: 0x000A0000 Count: 0x2000(8192)
Program page Start: 0x000A2000 Count: 0x2000(8192)
Program page Start: 0x000A4000 Count: 0x2000(8192)
Program page Start: 0x000A6000 Count: 0x2000(8192)
Program page Start: 0x000A8000 Count: 0x2000(8192)
Program page Start: 0x000AA000 Count: 0x2000(8192)
Program page Start: 0x000AC000 Count: 0x2000(8192)
Program page Start: 0x000AE000 Count: 0x2000(8192)
Program page Start: 0x000B0000 Count: 0x2000(8192)
Program page Start: 0x000B2000 Count: 0x2000(8192)
Program page Start: 0x000B4000 Count: 0x2000(8192)
Program page Start: 0x000B6000 Count: 0x2000(8192)
Program page Start: 0x000B8000 Count: 0x2000(8192)
Program page Start: 0x000BA000 Count: 0x2000(8192)
Program page Start: 0x000BC000 Count: 0x2000(8192)
Program page Start: 0x000BE000 Count: 0x2000(8192)
Program page Start: 0x000C0000 Count: 0x2000(8192)
Program page Start: 0x000C2000 Count: 0x2000(8192)
Program page Start: 0x000C4000 Count: 0x2000(8192)
Program page Start: 0x000C6000 Count: 0x2000(8192)
Program page Start: 0x000C8000 Count: 0x2000(8192)
Program page Start: 0x000CA000 Count: 0x2000(8192)
Program page Start: 0x000CC000 Count: 0x2000(8192)
Program page Start: 0x000CE000 Count: 0x2000(8192)
Program page Start: 0x000D0000 Count: 0x2000(8192)
Program page Start: 0x000D2000 Count: 0x2000(8192)
Program page Start: 0x000D4000 Count: 0x2000(8192)
Program page Start: 0x000D6000 Count: 0x2000(8192)
Program page Start: 0x000D8000 Count: 0x2000(8192)
Program page Start: 0x000DA000 Count: 0x2000(8192)
Program page Start: 0x000DC000 Count: 0x2000(8192)
Program page Start: 0x000DE000 Count: 0x2000(8192)
Program page Start: 0x000E0000 Count: 0x2000(8192)
Program page Start: 0x000E2000 Count: 0x2000(8192)
Program page Start: 0x000E4000 Count: 0x2000(8192)
Program page Start: 0x000E6000 Count: 0x2000(8192)
Program page Start: 0x000E8000 Count: 0x2000(8192)
Program page Start: 0x000EA000 Count: 0x2000(8192)
Program page Start: 0x000EC000 Count: 0x2000(8192)
Program page Start: 0x000EE000 Count: 0x2000(8192)
Program page Start: 0x000F0000 Count: 0x2000(8192)
Program page Start: 0x000F2000 Count: 0x2000(8192)
Program page Start: 0x000F4000 Count: 0x2000(8192)
Program page Start: 0x000F6000 Count: 0x2000(8192)
Program page Start: 0x000F8000 Count: 0x2000(8192)
Program page Start: 0x000FA000 Count: 0x2000(8192)
Program page Start: 0x000FC000 Count: 0x2000(8192)
Program page Start: 0x000FE000 Count: 0x2000(8192)
Primary image flashing completes.
Program page Start: 0x00078000 Count: 0x2000(8192)
Program page Start: 0x0007A000 Count: 0x1000(4096)
Program page Start: 0x0007C000 Count: 0x2000(8192)
Program page Start: 0x0007E000 Count: 0x2000(8192)
Program page Start: 0x00080000 Count: 0x2000(8192)
Program page Start: 0x00082000 Count: 0x2000(8192)
Program page Start: 0x00084000 Count: 0x2000(8192)
Program page Start: 0x00086000 Count: 0x2000(8192)
Program page Start: 0x00088000 Count: 0x2000(8192)
Program page Start: 0x0008A000 Count: 0x2000(8192)
Program page Start: 0x0008C000 Count: 0x2000(8192)
Program page Start: 0x0008E000 Count: 0x2000(8192)
Program page Start: 0x00090000 Count: 0x2000(8192)
Program page Start: 0x00092000 Count: 0x2000(8192)
Program page Start: 0x00094000 Count: 0x2000(8192)
Program page Start: 0x00096000 Count: 0x2000(8192)
Program page Start: 0x00098000 Count: 0x2000(8192)
Program page Start: 0x0009A000 Count: 0x2000(8192)
Program page Start: 0x0009C000 Count: 0x2000(8192)
Program page Start: 0x0009E000 Count: 0x2000(8192)
Program page Start: 0x000A0000 Count: 0x0600(1536)
Program page Start: 0x000A0600 Count: 0x2000(8192)
Program page Start: 0x000A2600 Count: 0x2000(8192)
Program page Start: 0x000A4600 Count: 0x2000(8192)
Program page Start: 0x000A6600 Count: 0x156E(5486)
Program page Start: 0x000A7B6E Count: 0x0057(87)
Program page Start: 0x000A7BC5 Count: 0x2000(8192)
Program page Start: 0x000A9BC5 Count: 0x2000(8192)
Program page Start: 0x000ABBC5 Count: 0x2000(8192)
Program page Start: 0x000ADBC5 Count: 0x0ADE(2782)
Program page Start: 0x000AE6A3 Count: 0x0090(144)
Program page Start: 0x000AE733 Count: 0x0036(54)
Program page Start: 0x000AE769 Count: 0x000D(13)
Program page Start: 0x000AE776 Count: 0x0C8A(3210)
Program page Start: 0x000AF400 Count: 0x2000(8192)
Program page Start: 0x000B1400 Count: 0x2000(8192)
Program page Start: 0x000B3400 Count: 0x2000(8192)
Program page Start: 0x000B5400 Count: 0x2000(8192)
Program page Start: 0x000B7400 Count: 0x2000(8192)
Program page Start: 0x000B9400 Count: 0x2000(8192)
Program page Start: 0x000BB400 Count: 0x2000(8192)
Program page Start: 0x000BD400 Count: 0x2000(8192)
Program page Start: 0x000BF400 Count: 0x1000(4096)
Program page Start: 0x000C0400 Count: 0x2000(8192)
Program page Start: 0x000C2400 Count: 0x2000(8192)
Program page Start: 0x000C4400 Count: 0x2000(8192)
Program page Start: 0x000C6400 Count: 0x2000(8192)
Program page Start: 0x000C8400 Count: 0x2000(8192)
Program page Start: 0x000CA400 Count: 0x2000(8192)
Program page Start: 0x000CC400 Count: 0x2000(8192)
Program page Start: 0x000CE400 Count: 0x2000(8192)
Program page Start: 0x000D0400 Count: 0x2000(8192)
Program page Start: 0x000D2400 Count: 0x2000(8192)
Program page Start: 0x000D4400 Count: 0x2000(8192)
Program page Start: 0x000D6400 Count: 0x2000(8192)
Program page Start: 0x000D8400 Count: 0x2000(8192)
Program page Start: 0x000DA400 Count: 0x2000(8192)
Program page Start: 0x000DC400 Count: 0x2000(8192)
Program page Start: 0x000DE400 Count: 0x2000(8192)
Program page Start: 0x000E0400 Count: 0x2000(8192)
Program page Start: 0x000E2400 Count: 0x2000(8192)
Program page Start: 0x000E4400 Count: 0x2000(8192)
Program page Start: 0x000E6400 Count: 0x2000(8192)
Program page Start: 0x000E8400 Count: 0x2000(8192)
Program page Start: 0x000EA400 Count: 0x2000(8192)
Program page Start: 0x000EC400 Count: 0x1C00(7168)
Program page Start: 0x000EE000 Count: 0x0B04(2820)
Program page Start: 0x000EEB04 Count: 0x10FC(4348)
Program page Start: 0x000EFC00 Count: 0x0400(1024)
Program page Start: 0x000F0000 Count: 0x2000(8192)
Program page Start: 0x000F2000 Count: 0x2000(8192)
Program page Start: 0x000F4000 Count: 0x2000(8192)
Program page Start: 0x000F6000 Count: 0x2000(8192)
Program page Start: 0x000F8000 Count: 0x1E00(7680)
Backup image flashing completes.
Verifying update...
Action: Read EEPROM image.
Reading EEPROM bytes.
Start: 0x00000000
Count: 1048576(0x00100000)
Read complete.
Update successful.

Firmware image updated.
- New version: 90.04.7A.00.69
- Old version: 90.04.7A.00.69

InfoROM image updated.
- New version: G001.0000.02.04
- Old version: G001.0000.02.04

A reboot is required for the update to take effect.

Falcon CLOSE

I rebooted and checked the bios. The program, in fact, did not flash some parts of the BIOS.
Here is the log:

Spoiler: Log2

NVIDIA Firmware Comparison
Comparing TU104BIG.rom...
Current - Version:90.04.7A.00.69 ID:10DE:1E81:10DE:13A1
GPU Board (Normal Board)
Compare with - Version:90.04.7A.00.69 ID:10DE:1E81:10DE:13A1
GPU Board (Normal Board)

ERROR: Size difference between file(0xD7400) and adapter ROM space (0xD7A00)
NOTE: Make sure to compare with entire saved image file.
Primary Firmware Image
Legacy BIOS ........................................ Pass
UEFI ............................................... Pass
Firmware Certificate ............................... Pass
Secondary Firmware Image
Legacy BIOS ........................................ Pass
UEFI ............................................... Pass
Firmware Certificate ............................... Mismatch
InfoROM ................................................ Mismatch
Unallocated Space ...................................... Mismatch


MISMATCH ERROR: Command Compare error
Exit Code: 7

Log verify, does not want to flash INFOROM.

Spoiler: Log3

Command-line : --verify TU104BIG.rom --log output2a.log
NVIDIA Firmware Update Utility (Version 5.780.0)
Copyright (C) 1993-2022, NVIDIA Corporation. Veii Extreme Edition

Command: verify

NOTE: NO ROM INDEX HAS BEEN SPECIFIED. PERFORMING CHECKS FOR ALL ROM IMAGES AVAILABLE
FindDevices:
Device:0000:00:00:00=1022:1480:1022:1480
Device:0000:00:00:02=1022:1481:1022:1481
Device:0000:00:01:00=1022:1482:0000:0000
Device:0000:00:01:01=1022:1483:FFFF:FFFF
Device:0000:00:01:02=1022:1483:FFFF:FFFF
Device:0000:00:02:00=1022:1482:0000:0000
Device:0000:00:03:00=1022:1482:0000:0000
Device:0000:00:03:01=1022:1483:FFFF:FFFF
Device:0000:00:04:00=1022:1482:0000:0000
Device:0000:00:05:00=1022:1482:0000:0000
Device:0000:00:07:00=1022:1482:0000:0000
Device:0000:00:07:01=1022:1484:FFFF:FFFF
Device:0000:00:08:00=1022:1482:0000:0000
Device:0000:00:08:01=1022:1484:FFFF:FFFF
Device:0000:00:14:00=1022:790B:1022:790B
Device:0000:00:14:03=1022:790E:1022:790E
Device:0000:00:18:00=1022:1440:0000:0000
Device:0000:00:18:01=1022:1441:0000:0000
Device:0000:00:18:02=1022:1442:0000:0000
Device:0000:00:18:03=1022:1443:0000:0000
Device:0000:00:18:04=1022:1444:0000:0000
Device:0000:00:18:05=1022:1445:0000:0000
Device:0000:00:18:06=1022:1446:0000:0000
Device:0000:00:18:07=1022:1447:0000:0000
Device:0000:01:00:00=15B7:5002:15B7:5002
Device:0000:02:00:00=1022:43EE:1B21:1142
Device:0000:02:00:01=1022:43EB:1B21:1062
Device:0000:02:00:02=1022:43E9:FFFF:FFFF
Device:0000:03:00:00=1022:43EA:FFFF:FFFF
Device:0000:03:06:00=1022:43EA:FFFF:FFFF
Device:0000:03:07:00=1022:43EA:FFFF:FFFF
Device:0000:03:09:00=1022:43EA:FFFF:FFFF
Device:0000:04:00:00=10DE:21C4:1458:4012 GPU
Device:0000:04:00:01=10DE:1AEB:1458:4012
Device:0000:04:00:02=10DE:1AEC:1458:4012
Device:0000:04:00:03=10DE:1AED:1458:4012
Device:0000:05:00:00=1D89:0160:1D89:0160
Device:0000:06:00:00=10EC:8168:1462:7C91
Device:0000:2A:00:00=10EC:8125:1462:7C91
Device:0000:2B:00:00=10DE:1E81:10DE:13A1 GPU
Device:0000:2B:00:01=10DE:10F8:10DE:13A1
Device:0000:2B:00:02=10DE:1AD8:10DE:13A1
Device:0000:2B:00:03=10DE:1AD9:10DE:13A1
Device:0000:2C:00:00=1022:148A:1022:148A
Device:0000:2D:00:00=1022:1485:1022:1485
Device:0000:2D:00:01=1022:1486:1022:1486
Device:0000:2D:00:03=1022:149C:1022:148C
Device:0000:2D:00:04=1022:1487:1462:EC91
Filter-out on-motherboard PLX bridge device.
No PLX/PEX switch was detected, skip to filter-out non-NVIDIA PLX/PEX switch.
Select a display adapter:
<0> NVIDIA GeForce GTX 1660 SUPER (10DE,21C4,1458,4012) S:00,B:04,D:00,F:00
<1> NVIDIA GeForce RTX 2080 SUPER (10DE,1E81,10DE,13A1) S:00,B:2B,D:00,F:00
Select a number (ESC to quit):
1

========================== Image Index 0 ====================================
Action: Verify ROM image.

Disable NV driver before start if NV driver loaded.




The NVFlash succeed to disable the NV Driver automatically.
Adapter: NVIDIA GeForce RTX 2080 SUPER (10DE,1E81,10DE,13A1) S:00,B:2B,D:00,F:00

Action: Identify EEPROM.
uproc 05 ucode is not found for this GPU.
uproc 02 ucode is not found for this GPU.
uproc 04 ready to be used.
Preparing secure operation after kicked start.
Actual SPI clock frequency (Hz): 18000000
Serial EEPROM identified.
EEPROM ID (9D,7014) : ISSI IS25WP080 1.65-1.95V 8192Kx1S, page

Action: Read EEPROM image.
Reading EEPROM bytes.
Start: 0x00000000
Count: 1048576(0x00100000)
Read complete.
Current - Version:90.04.7A.00.69 ID:10DE:1E81:10DE:13A1
GPU Board (Normal Board)
Compare with - Version:90.04.7A.00.69 ID:10DE:1E81:10DE:13A1
GPU Board (Normal Board)
Skip proceeding with preservation table for Pascal or newer chip.
G001.0000.02.04
INFOROM_FLASH_TYPE: 0x04
INFOROM_FLASH_TYPE_NOT_NONE_TO_NONE
Final PCI expansion ROM size is 23552(0x5C00) bytes
Final InfoROM Offset = 0x000D1A00 ( Absolute Offset 0x000FA000)
RFRD Settings | ROMImage | Final |
InfoRomOffset | 0x000FA000 | 0x000FA000 |
InfoRomSize | 0x00004000 | 0x00004000 |

InfoROM Offsets | ROMImage | InputAlt | Final |
NBSI OpRom Offset | 0x0F9E00 | 0x000000 | 0x077C00 |
NPDS Struct Offset | 0x0F9E20 | 0x000020 | 0x0F9E20 |
NPDE Offset | 0x0F9E40 | 0x000040 | 0x0F9E40 |
NBSI DIR Offset | 0x0F9FE0 | 0x000FE0 | 0x0F9FE0 |
JFFS Offset | 0x0FA000 | 0x001000 | 0x0FA000 |
Num of Objects = 7
Num of RW Objects = 2
Size of image with dummy RO blocks = 2688
Num of Objects = 7
Num of RW Objects = 2
Size of image with dummy RO blocks = 2688

To exclude the known mismatch fields in InfoROM block, proceeding with InfoROM preservation type same as the type of image in EEPROM too.
INFOROM_FLASH_TYPE_NOT_NONE_TO_NONE
Leverage current InfoROM offset and remove the existed InfoROM before composing new InfoROM
InfoROM PCI base offset: Current offset = 0xF9E00
New offset = 0xF9E00
Final PCI expansion ROM size is 23552(0x5C00) bytes
Final InfoROM Offset = 0x000D1A00 ( Absolute Offset 0x000FA000)
RFRD Settings | ROMImage | Final |
InfoRomOffset | 0x000FA000 | 0x000FA000 |
InfoRomSize | 0x00004000 | 0x00004000 |

InfoROM Offsets | ROMImage | InputAlt | Final |
NBSI OpRom Offset | 0x0F9E00 | 0x000000 | 0x0F9E00 |
NPDS Struct Offset | 0x0F9E20 | 0x000020 | 0x0F9E20 |
NPDE Offset | 0x0F9E40 | 0x000040 | 0x0F9E40 |
NBSI DIR Offset | 0x0F9FE0 | 0x000FE0 | 0x0F9FE0 |
JFFS Offset | 0x0FA000 | 0x001000 | 0x0FA000 |
Num of Objects = 7
Num of RW Objects = 2
Size of image with dummy RO blocks = 2688
Num of Objects = 7
Num of RW Objects = 2
Size of image with dummy RO blocks = 2688

BCRT: Start Certificate 2.0 verification
Send VV Command...
cmd: ROMDIR
Populating the backup image...
File size: 1047040(0xFFA00)
Adapter size: 1047040(0xFFA00)
File firmware image matches adapter firmware image.
Falcon CLOSE

 

[Deleted member 218758]

but for the 32-bit one, isn't it enough to bring the bill and subtract (all the ones you added) in the text area? I thought that was simple too...

can you be more clear ?
Or visualize clear ?