Hey,

This is the message I received when trying to flash it via nvflash:

Zitat

---

Nothing changed!

ERROR: PCI Block corrupted - no valid PCI data structure found. GetNewPCIBlockInfo failed

---

Also, when I checked the file via gopupd.bat (ISBN=1, DEBUG=1, ROMSCAN=1) - it tells me that the ROM you've provided me is missing it's ISBN

Zitat

---

ISBN was not found!

---

Here's the ending of the file structure of the original ROM dump:

Zitat

---

Image 13 -- Offset 0xF8E00

------------NV_ROM_HEADER-----------

Signature: 4E56
Initialization Size: 0x00 (0x00)
Reserved: 000000000000000000000000000000000000E001
PCIR Offset: 0x20 (abs 0xF8E20)

------------------------------------

-------------PCIR_HEADER------------

Signature: NPDS
Vendor ID: 10DE
Device ID: 0000
Reserved: 00
Length: 0x18
Revision: 00 (PCI 2.3)
ClassCode: 00-00-00 (or 00-00-00)
Image Length: 0x2E (0x5C00)
Code Revision: 0x00
Code Type: 0x70 (Nvidia NBSI - Signature)
Indicator: 0x80 (Last image)
Reserved: 00

------------------------------------

-------------NPDE_HEADER------------

Signature: NPDE
PCI data extension revision 100
NPDE Length 0x0C
Image Length 0x2E (0x5C00)
Indicator 0x80 (Last image)
Unknown 0x04

------------------------------------

Found ISBN at offset 0x78238

----------ISBN_HEADER---------

Signature: ISBN
Header Size: 0x0C
Unk01: 0x01
Unk02: 0x01
BV Signature: BV
Checksum v1: 0x39994431
Checksum v2: 0x2A129830
BV Signature: BV
ISBN Body Size: 0x1AE8
Unk03: 0x1000000

------------------------------

----------CERT_HEADER---------

Type: 0x22
Header Size: 0x28
Nr of map elements: 0x00
Certificate size: 0x00
Flags v01 : 0x1AD8
Flags v02 : 0x28
Flags v03 : 0x5E
Flags v04 : 0x7FE
Flags v05 : 0x8FC
Flags v06 : 0xAB0

------------------------------

Extracted cert_nr1.lic

----------MAP_Content---------

Flags | Offset | Size | Hash

Master Hash : 5E000000FE070000FC080000B00A0000

------------------------------

----------CERT_HEADER---------

Type: 0x01
Header Size: 0x36
Nr of map elements: 0x37343031
Certificate size: 0x63703430
Flags v01 : 0x70
Flags v02 : 0x00
Flags v03 : 0x00
Flags v04 : 0x00
Flags v05 : 0x35500000
Flags v06 : 0x52333439
Flags v07 : 0x31
Flags v08 : 0x00
Flags v09 : 0x00
Flags v10 : 0x20000

------------------------------

---

And here's the ending of the file structure of the tu104_updGOP.rom you've provided me:

Zitat

---

Image 13 -- Offset 0xF8E00

------------NV_ROM_HEADER-----------

Signature: 4E56
Initialization Size: 0x00 (0x00)
Reserved: 000000000000000000000000000000000000E001
PCIR Offset: 0x20 (abs 0xF8E20)

------------------------------------

-------------PCIR_HEADER------------

Signature: NPDS
Vendor ID: 10DE
Device ID: 0000
Reserved: 00
Length: 0x18
Revision: 00 (PCI 2.3)
ClassCode: 00-00-00 (or 00-00-00)
Image Length: 0x2E (0x5C00)
Code Revision: 0x00
Code Type: 0x70 (Nvidia NBSI - Signature)
Indicator: 0x80 (Last image)
Reserved: 00

------------------------------------

-------------NPDE_HEADER------------

Signature: NPDE
PCI data extension revision 100
NPDE Length 0x0C
Image Length 0x2E (0x5C00)
Indicator 0x80 (Last image)
Unknown 0x04

------------------------------------

ISBN was not found!

---

Thanks again and kind regards,

@hydropepon

Well, according to some hex checkings, I've found that the 0x50013 Turing UEFI Gop Table has been extracted from a TU116 card (GTX 1660).
That card has a specific Device ID and Subvendor ID which is different from the one used on RTX 2080 card.

Furthermore, the EFI compressed size of the GOP Table is 2 kb smaller than the previous 0x50009 Turing gop table you linked before.

That's the reason for which the resulting bios file size is 1017 kb big instead of 1019 kb.

You have also to consider that GOP Uefi Updater tool remove unnecessary padding data and thus the bios file size is smaller.

I will do more investigations about this but as I've no RTX card I can't do tests on myself and I'm very sorry about this.

@Sylar76

It's no problem at all, in fact, I'm very appreciative that you're even looking into this - take your're time and thank you again.

1. A small note, the original VBIOS GOP(the one I linked) is 0x50005 (70KB) and the latest version that I've managed to update it to without any issues is 0x50009 (also 70KB). Every other following GOP that I've tried was 68KB and updates using them resulted in the same aforementioned issues.

2. Something interesting that I've managed to dig up which hopefully you may find useful: https://www.techpowerup.com/vgabios/?arc...memSize=&since=
Those are the VBIOSes for the NVIDIA branded Founders Edition RTX 2080 Ti:
Version: 90.02.0B.00.0E / 2018-08-29 00:00:00 / GOP 0x50005 - 70KB / ROM size 1023KB
Version: 90.02.17.00.04 / 2018-10-11 00:00:00 / GOP 0x50009 - 70KB / ROM size 1023KB
Version: 90.02.30.00.05 / 2019-01-13 00:00:00 / GOP 0x5000B - 68KB / ROM size 1023KB

- Basically, as you can see: all 3 versions have a ROM size that's 1023 KB, the two older ones have a GOP that's 70KB and the newest one has a GOP that's 68KB.
- Trying to update the two older versions with the 70KB GOP's to 0x50013 results in the ROM size falling to 1021KB.
- Updating the newest of the three (the one with the 68KB GOP (0x5000B)) - does not result in any file size changes in the ROM and it remains 1023KB.

Kind regards,

I think then, there is something wrong in the dumping process (gpu-z or nvflash) of such bioses. Did you try to compare a 0x5000B founder's edition bios with a previous one (dumped via gpu-z or nvflash) updated to the same 0x5000B gop table ?

Maybe there could be some differences.

@Sylar76

Just did, updating both the older 70KB GOP based ones to GOP 0x5000B results in the same 2KB ROM size reduction - 1023KB to 1021KB. Updating the newest GOP 0x5000B 68KB based ROM to GOP 0x5000B (by swapping the GOP file in the #GOP_Files folder) results in no changes in the final ROM size, which remains at 1023 KB.

Have to get to work now - here's hoping I don't perish before we(or more likely just you) figure this out...

Kind regards,

After brushing this file, the EFI boot screen appears, which is great.
Dataland.HD7750.1024.120413_updGOP.rom is able to flash successfully, but the boot fails, and the screen is blank.
Dataland 7750 1G vbios_updGOP.rom flashing error, see the attachment below


gpu-z7750vbios_updGOP.rom flashed successfully. And boot successfully
Attach a picture of the brush result

Just a quick message to thank you clever chaps for all these tools.
Lost_N_BIOS helped me out about 2 years ago now with my retired ASUS board after I botched it.

After waiting for 10 years, I've finally upgraded to a beefy Ryzen 3700X and Gigabyte X570 Auros Pro.
I'm still using my Sapphire R9 285 2GB (Dual Bios) for the moment so thought I'd switch from legacy boot (CSM) to UEFI booting.
Maybe I'll pickup a cheap RX 580/RX 590 or upcoming Navi card eventually.

When booting with CSM enabled the card works perfectly both before and after booting Linux.
Unfortunately when switching to UEFI booting the screen colours were occasionally garbled in GRUB and the UEFI menu.
As the card was released in 2014 it had an early version of the GOP driver (it even says 1.55.0.0.0 Testing in the motherboard menus!)

Good news however!
I've taken a legacy bios file for the card, updated it with the tool and the card is now working as expected. (v1.67.0.15.50)
Closed source shoddy software and vendors moving on is to blame!

So why am I posting?
When I tried updating the UEFI files the tool reported error messages.
The resulting files were too big to flash.
I thought I'd take a chance on updating the non-UEFI bios file which worked.
I guess there's an issue updating the early GOP implementation with the later standardised one.

TechPowerUp's BIOS Collection
------------------------------------------
R9 285 Dual X
Legacy: https://www.techpowerup.com/vgabios/1617...5-2048-140814-3
UEFI : https://www.techpowerup.com/vgabios/1642...5-2048-140814-4

R9 285 Dual X Overclocked
Legacy: https://www.techpowerup.com/vgabios/1640...5-2048-140814-2
UEFI: https://www.techpowerup.com/vgabios/168323/168323

*File I used in bold*
*Flashing Tool - ATIFlash UEFI Shell*

New VEGA AMD GOP Table 2.10.0.0.0

I'll update GOP Uefi Tool later.

Maybe there is something wrong with GOP Updater v1.9.6.5g, cause i get this:

Dumping info from = Vega 20.rom


ID of ROM file = 1002-66AF


***************************************************************
*** Extracting with UEFIRomExtract by AndyV ***
***************************************************************

Found compressed EFI ROM start at 0x58
Input size: 43944, Output size: 74000, Scratch size: 13360

---------------------------------------------------------------

***************************************************************
*** Extracting with GOPupd... ***
***************************************************************

AMD GOP 2.8.0.0.0 LibBuild ---- Dated: Jul 26 2019 11:24:53

AMD_Build 2218 AMD_ChangeList 1974379 GOP BIOS_IDTF 0xDEADBEEF

Most likely signed by: Microsoft Corporation UEFI CA 2011

Machine Code = x64

Checksum CRC32 = 2D0A75F8

---------------------------------------------------------------

***************************************************************
*** Processing with Python... ***
***************************************************************

You have a newer version! Please report it in the forum!


---------------------------------------------------------------

As you can see, my ROM only has 2.8.0.0.0 GOP, anyway it tells me, i would have a newer version and should report it.

Edit.

I've checked gop database and it has been added so it's very strange. Could you please attach your vega .rom file ?

Sylar76,can you put the program on the forum as usual? I can hardly download from the online disk,thanks

I am also getting the same message with a Navi bios with 2.7 and it saying it is a newer version

I've removed previous link and added only the AMD GOP Uefi Table 2.10.0.0.0.

Well, I've a lot of problems (and I don't know why) to properly edit and change the python code
to accomodate the 2.10.0.0.0 AMD Gop Uefi Table.

Thus, if anyone can help me it will be very appreciated.

Hi mates, I want to update my old ASUS R9 280X Direct CU II TOP Overclocked Edition, but I don't know how to do it, can you explain me please???
Thank you so much, regards.

@RaskaipikaFWR
ASUS official R9280X-DC2T-3GD5 VBIOS update
https://dlcdnets.asus.com/pub/ASUS/vga/A..._R9280XDC2T.rar