And also NVIDIA GPU Firmware Update Tool for DisplayID | NVIDIA (custhelp.com)
Sorry, i’m wrong, the other update is for older generation
Unfortunately, the original GOP version of my GPU is already “0x60015”, but DisplayPort 1.4 is still malfunctioning in this version, and NVIDIA’s official update tool hasn’t been updated for a long time, so it can’t take effect on it. I’ve contacted both NVIDIA and the GPU OEMs during the past six months, but they only shirk their responsibilities to each other and don’t want to fix the problem … 
After searching, I found that only Asus and Zotac noticed the problem and updated their GOP version to “0x60018”, I had to try to extract these VBIOS myself and modify the GOP using this tool, but some kind of signature mechanism introduced by the Ampere architecture seems to make this impossible.
1 Like
I’m having the same problem with my 3060Ti, nvflashk can’t write to the modified VBIOS, it just shows:
Error Code = 0x00000040(64): NV_UCODE_ERR_CODE_CERT20_VDPA_SIG_INVALID
ERROR: Invalid firmware image detected.
@CirnoSalt I can see this becoming a big problem for the 3000 and 4000 series as more new models of monitors are released.
Nividia really need to pull their finger out and update their firmware tools with the latest GOP version.
@karfel
The NVIDIA TU100 family doesn’t support RBAR, what your looking is to add a GOP as your dump vbios doesn’t contain one, this is probably because the system has an Intel iGPU for boot and it uses the GOP driver from the mboard bios.
The results in the laptop boot could be instable.
For REBAR mods a mboard bios mod is necessary, this is the current project present in this forum, followed by the NvStrapsReBar for enabling Resizable BAR on Turing 20/16 series.
Good luck.
I just got a 4090, is there any update for this card?
Did you tried the version 0x60017 that has already the gop update tool?
Update the card to 0x60017 and then flash it with nvflashk.
1 Like
Since the introduction of the Ampere microarchitecture, NVIDIA has implemented additional digital signatures and policies to ensure the integrity of firmware, rendering current tools inapplicable to graphics cards based on Ampere and newer architectures. The presence of these increased digital signatures and policy constraints means that developing universal patches for all firmware versions will be prohibitively costly for NVIDIA. Consequently, I believe that more graphics cards will be unable to receive software patches and updates throughout their lifecycle if these restrictions are not alleviated.
Currently, the new GOP tools for graphics cards based on the Ampere and newer architectures is limited by digital signature restrictions, and only a subset of devices/firmware can be updated to the latest GOP version.
A new version of the GOP tools will be released in the future, so stay tuned.
Does this mean that I can update with GOP tool, but I would not be able to flash it because of the missing signature?
BTW, latest GOP tool has 0x7000b for Ada Lovelace.
Thank you for your attention.
Yes but not entirely, these digital signatures are saved in the firmware and verified on boot, so future versions of the GOP tools will support saving these digital signatures as well as refreshing. This also makes it impossible to change the size of the GOP until there are more options to skip digital signatures, so only firmware of specific GOP versions can be updated.
2 Likes
Thanks for your answer. What happens if I flash a firmware with broken signature now?
At least since the Turing microarchitecture, verifying digital signatures has become a mandatory requirement for device initialization. If the firmware lacks a proper digital signature, the device initialization process cannot be completed.
So, I can flash my card, but the system will not boot, right?
Firmware that does not pass digital signature verification cannot be flashed using NVFLASH, but you can still use a version with the verification removed (if available) or use a programmer to flash it. However, as mentioned before, an incorrect digital signature will prevent the device from completing initialization.
2 Likes
I was wondering if updating the EFIROM alone using the command nvflash -u file.efirom will work on 4090…
What do you think?
As mentioned in the post above, efirom does not contain a digital signature, which prevents NVFLASH from verifying the digital signature. Consequently, this method cannot be used to update the VBIOS. Additionally, the various functional modules of the VBIOS are stored in different blocks. Theoretically, unless the modules in the VBIOS are designed to be interchangeable, the flashing software will not know which block to modify.
2 Likes
EFI of what? Your washing machine???
NVIDIA Firmware Update Utility (Version 5.821.0)
Copyright (C) 1993-2023, NVIDIA Corporation. All rights reserved.
Sign-On Message :
Build GUID : Blank
Build Number : 0
IFR Subsystem ID : Blank
Subsystem Vendor ID : 0x0000
Subsystem ID : 0x0000
Version : Unavailable (Invalid) (Disabled Image)
Image Hash : N/A
Device Name(s) : Unknown
Board ID : Blank
Vendor ID : 0x0000
Device ID : 0x0000
Hierarchy ID : N/A
Chip SKU : N/A
Project : N/A
Build Date : Blank
Modification Date : Blank
UEFI Version : No Version Found or Out-dated ( )
UEFI Variant ID : No Variant ID Found ( No Variant ID Found )
UEFI Signer(s) : Unknown signer
XUSB-FW Version ID : N/A
XUSB-FW Build Time : N/A
InfoROM Version : No Version Found
InfoROM Backup : Not Present
License Placeholder : Not Present
GPU Mode : N/A
CEC OTA-signed Blob : Not Present
EDIT: Original post edited and added the info provided by Dagal.
Thank you for your attention to this post and for sharing the new version of GOP firmware.
Unfortunately, for Ampere and newer architecture devices, firmware alone is not enough, and corresponding digital signature data is required, so the content you submitted cannot be used.
This is not your fault, I will complete the new version as soon as possible to support these contents, and I will let you know when the new version is completed.
Thank you again for sharing.
1 Like