@Ruin as expected, worked perfectly. No problems at all, bios also shows gop version correctly (has the ability to show installed GPU gop information)
Thank you! I would say it is safe to use.

@Sylar76 I solved the issue with my GPU and mobo combo. First, a small refresher, the issue was that on reboot (reboot only, cold boot is fine) in UEFI mode, regardless of OS, the PC would hang/freeze on the UEFI logo. In BIOS CSM mode this doesn't happen as the UEFI GOP driver is never loaded.
Specs: ASUS Sabertooth 990FX R2.0 and NVIDIA 1650 Super
This is an issue with the *motherboard BIOS* and GPU UEFI driver combo, however, the one responsible is more likely the motherboard BIOS. A new GOP driver *might* have solved it or might not, I don't know as I never got around to updating successfully with a custom VBIOS from here.

SOLUTION:
Enable HPET in BIOS... Yes, that's it. An old timer chip on the motherboard that no OS uses any more since Windows 7-8. Just enabling it in BIOS > Advanced > Southbridge.
Why something from the Southbridge, let alone this impact the GPU, I do not know. The GPU is on PCI-E which is directly wired to the CPU through the Northbridge.

I guess the BIOS chip being connected to the Southbridge impacts this or maybe some synchronization somewhere fails without this legacy timer. Rn I don't have the time to look into it, but maybe someone that sees this post will and I wish them good luck in finding the root of the issue.

After trying to upgrade a motherboard from a Biostar B350GT5 to a MSI B550 Tomahawk, I'm greeted on the first boot by a screen telling me it only supports graphics cards with GOP. Which I'm pretty sure is the card's fault, as when I tried to switch from legacy to UEFI for the video card boot it didn't work. 8 beep for video failure and no display, though it did boot in Linux fine.

Look for a new VBIOS for the card, an XFX RX 560 P2SFG5, but XFX doesn't seem to provide any VBIOSes at all. So I'll have to try to fix the GOP.

I'm running Linux, so gopupd and the tools in this thread aren't going to work as is.

First step is to get the vbios. I turns out this isn't that hard. The kernel amdgpu DRI driver has a bunch of built in debug features, and one lets the vbios be downloaded. It shows up in debugfs as /sys/kernel/debug/dri/0/amdgpu_vbios. But it's only 100kB, hmm...

Examine the file, and it has a legacy image at the start and a GOP image at 0xea00. I few changes to GOPupd.py to change the file path separator from '\\\\' to '/' and the extract works fine on Linux fine to decode the ROM headers and pull out the EFI image. But now the EFIROM needs to be decompressed.

The windows executable to extract the data from the compressed ROM is of course useless to me. However, there is a python package on pipy that has two of the UEFI compression algorithms. Apparently they couldn't use a standard one like zlib or lzma. So I added the ability into GOPupd.py to decompress the ROM itself. This means it doesn't need the two stage process driven by the batch file or the extra executable.

The card has the 2.0.0.0.0 GOP, and this GOP doesn't list 1002-67FF RX 560 BAFFIN as supported. Seems like maybe XFX didn't test their UEFI BIOS at all? It's not listed in any of the 2.x GOPs. But is in the 1.69.0.15.50.

Here's where GOPupd logic is little weird. It asks if I want to update to the newest 2.x GOP. I don't, since it doesn't support RX 560, but I've got to say yes anyway otherwise it stops. Then it tells me my card isn't in the list and would I like 1.57.0.0.0 instead. I don't want that either, but need to say yes again. Now I've got a new VBIOS with 1.57.0.0.0. Then run GOPupd.py on this new VBIOS and it asks if I'd like to update to 1.69.0.15.50. And now I have the VBIOS I want. Looks like the logic doesn't let you go from a 2.x to 1.69 directly.

After a little digging, I find that one can get the amdvbflash tool for Linux. I make another backup of my VBIOS with this, and now it's 256kB. But the first 100kB is exactly the same as what I've already used. Flash the new VBIOS, reboot, and hope for the best.

And it doesn't happen. I figured since it booted fine in legacy mode, even if the GOP didn't work, I could still reset the bios settings and boot legacy. But nope, won't even post. Boots ok without the card installed. Also boots ok if I don't connect the extra power cable for the card, but the card isn't detected.

So I try booting without the card power connected, login remotely via ssh, and then connect the power and trigger a PCI bus rescan. But no luck. Maybe adding PCIe devices after powerup doesn't work on B350 chipsets or likely the driver is missing the logic to trigger a PCI-e link retrain because no one does PCI-e hotplug on consumer motherboards.

I've got an old PCI graphics card (and a pile of AGP cards, they'll be valuable antiques one day!) let me try that. Nope, system still won't boot with the RX 560 installed. PCI card doesn't work either. It's keyed dual voltage, but I wonder...

Can I buy a cheap PCI-e card anywhere locally... No, just expensive gaming cards.

But them I remember, I've got a computer at work! I forgot there was this office I used to go into everyday. Now where did I put my badge?

Copy the 256 kB firmware file off my computer and head in to the office. Pop the card into my workstation (253 days uptime, I could have made it year..), which thankfully has both an 8pin and 6pin power cable so I run two cards, and it boots! Reflash the XFX RX 560, put it back in my home computer, and it works again!

Enough of this I think. Maybe a different B550 board will support legacy video. But then it occurs to me that I put the new GOP into the 100kB VBIOS file (which did end with the complete GOP ROM, it wasn't cut off) and not into the 256 kB one. I take a look at the larger dump file and it's mostly empty after 100 Kb, but not entirely. There's a section with data in it. Maybe that data was important?

So let's try again. 1.69 GOP into firmware. Extra data is preserved. Flash new VBIOS. Reboot. And... success! It boots. Still in legacy mode, but at least it's not dead. Try UEFI mode and that works too. Display is corrupted as it first POSTs but the MB BIOS works ok after that.

Reinstall the MSI B550 board and now it works too. Success! Now I get started retweaking all my memory timings for the new board.

So things learned. Maybe google will index this so the next guy can find it:
XFX RX560 cards come with a broken GOP, but it can be fixed.
GOPupd.py works on Linux with minor editing.
AMD VBIOS can be dumped and flashed in Linux with amdvbflash.
The amdgpu_vbios file in debugfs is NOT the complete VBIOS! It's just the parts contained inside a PCIR. There might be extra data that is very important. Use amdvbflash to dump the whole bios.

Thanks @lordkag for making GOPupd python and not hiding the source. Something that's a pain about OC on Linux is that there are so many good OC tools, that are free, but they are always Windows executables only with no source. A ryzen memory timing tool would be about 99% compatible with Linux and there's plenty of people who could port it, but no source so it doesn't happen.

XFX RX560 cards have a bad bios.
I reflash my XFX RX460 4Gb to Saphire Radeon RX560 with GOP - it's good for me in all my system: Linux, Win10 and hackintosh (Mojave) :)

I've got the 2GB model. I did find once, thought I can't find it again, some forums posts about using Sapphire BIOS on XFX cards. Seemed like the results were it can work if you use the right VBIOS, or brick the card if you use the wrong one. XFX has six different RX 560 cards, so I didn't like my odds of getting the right vbios. Since the GOP isn't card specific for AMD, I figured that would be safer, and wouldn't possibly change the memory timing.

Hello,
First, big Up to Lordkag & co for the great job !
I solved my boot issue with old Radeon 6850 (BIOS Legacy) on my new motherboard MSI MAG B550M Mortar (UEFI) thanks to GOPupd.
I will share my tutorial for noobs

Zitat von jgn123 im Beitrag #1100

---

File Not Found
The system cannot find the file specified.
Using python from C:\Users\Jeff Nguyen\AppData\Local\Microsoft\WindowsApps\python.exe
Nguyen\AppData\Local\Microsoft\WindowsApps\python.exe" GOPupd.py" was unexpected at this time.
D:\Downloads\GOPUpd_v1.9.6.5>

---

My tutorial for contribution... ;)
Attachment : BIOS F3 with UEFI tested OK for Gigabyte Radeon HD 6850 (GV-R685D5-1GD)

My PC does not start, it beeps and displays an error message:
"There is no GOP (Graphics Output Protocol) support detected in this card."
- Cause: My old Gigabyte Radeon HD 6850 (GV-R685D5-1GD) graphics card in BIOS Legacy mode is too old for the new MSI MAG B550M Mortar motherboard in UEFI mode.

- Solution:
A. Borrow or buy a newer graphics card (UEFI) to start and activate the CSM (Compatibility Support Module) in the motherboard then replace the old card (if kept), or
B. Update the VBIOS of the graphics card with GOPupd, to add the GOP code and boot in UEFI mode.

The procedure is the same with other makes / models of motherboards and graphics cards.

Update the GOP code on an old graphics card (Legacy BIOS) to make it UEFI compatible:
0 - Download GOPupd on Win-Raid and extract to a short path like C:\VBIOS: (Page 1)
To determine the version or the presence of a UEFI GOP module in a BIOS file, drag and drop the BIOS file on the command file # AMD_ROM_Info.bat or # Nvidia_ROM_Info.bat

1 - Check the latest BIOS on the manufacturer's website and update if a more recent version exists with the manufacturer's flash software (Ex: VGA Tools @BIOS), then restart.
Backup the original BIOS first!

2 - Check the BIOS of the existing card on the Techpowerup database, for a possible update:
Users need to decide whether they want to keep the current VBIOS and update only the GOP, or opt for the one on the manufacturer's site, if it's newer than theirs.
The Techpowerup database should be used only as a last resort and only if it is a newer version and ONLY IF it is compatible with the card.
Recommendation, always update the GOP of a VBIOS already installed on the card, in order to exclude a bad flash.

3 - Save the BIOS of the graphics card with GPU-Z (novice) or nvflash (advanced), to the directory created.

4 - To modify the saved BIOS, use GOPupd, drop the VBIOS file on the GOPupd.bat file and follow the instructions to create a new BIOS file.
Ex: Drag the bios6850.bin (Legacy) file onto GOPupd.bat to get the new bios6850_updGOP.bin (UEFI) file


In case of error on the Python program: "The specified file was not found"
C:\Users\%User%\AppData\Local\Microsoft\WindowsApps\python.exe
- You must remove the old Python programs from the directory indicated.
- It is also possible to modify GOPupd.bat to force the launch of GOPupd.exe

5 - Load the new modified BIOS bios6850_updGOP.bin into the graphics card with the manufacturer's flash software.

6 - Switch off the PC and disconnect the power supply and the video cable.

7 - Reconnect power and video cable, then start the PC in UEFI mode ...
If the error persists, restart...

Note: UEFI mode has an impact on the functioning of the system, all devices must be UEFI compatible and the hard drive / SSD for Windows must be formatted in GPT.
Windows must be installed from UEFI media (USB key, DVD, etc.)

My tutorial in french version / version française

Procédure de mise à jour du BIOS de la carte video.

Mon PC ne démarre pas, il fait des Bips et affiche un message d'erreur :
"There is no GOP (Graphics Output Protocol) support detected in this card."
- Cause : Ma vieille carte graphique Gigabyte Radeon HD 6850 (GV-R685D5-1GD) en mode BIOS Legacy est trop ancienne pour la nouvelle carte mère MSI MAG B550M Mortar en mode UEFI.

- Solution :
A. Emprunter ou acheter une carte graphique plus récente (UEFI) pour démarrer et activer le CSM (Compatibility Support Module) dans la carte mère puis remettre la vieille carte (si conservée), ou
B. Mettre à jour le VBIOS de la carte graphique avec GOPupd, pour ajouter le code GOP et démarrer en mode UEFI.

La procédure est identique avec d'autres marques/modèles de cartes mères et carte graphiques.

Mise à jour du code GOP sur une carte graphique ancienne (BIOS Legacy) pour la rendre compatible UEFI :
0 - Télécharger GOPupd sur Win-Raid et extraire vers un chemin court comme C:\VBIOS : (Page 1)
Pour déterminer la version ou la présence d'un module UEFI GOP dans un fichier BIOS, faire un glisser/déposer du fichier BIOS sur le fichier de commandes #AMD_ROM_Info.bat ou #Nvidia_ROM_Info.bat

1 - Vérifier le dernier BIOS sur le site constructeur et mettre à jour si une version plus récente existe avec le logiciel de flash du fabricant (Ex : VGA Tools @BIOS), puis redémarrer.
Faire un Backup du BIOS original avant !

2 - Vérifier les BIOS de la carte existants sur la base de données Techpowerup, pour une éventuelle mise à jour.
Les utilisateurs doivent décider s'ils veulent conserver le VBIOS actuel et ne mettre à jour que le GOP, ou opter pour celui sur le site du fabricant, s'il est plus récent que le leur.
La base de données Techpowerup ne doit être utilisée qu'en dernier recours et uniquement s'il s'agit d'une version plus récente et UNIQUEMENT SI elle est compatible avec la carte.
Recommandation, toujours mettre à jour le GOP d'un VBIOS déjà installé sur la carte, afin d'exclure un mauvais flash.

3 - Sauvegarder le BIOS de la carte graphique avec GPU-Z (novice) ou nvflash (avancé), vers le répertoire créé.

4 - Pour modifier le BIOS sauvegardé, utiliser GOPupd, déposer le fichier VBIOS sur le fichier GOPupd.bat et suivre les instructions pour créer un nouveau fichier BIOS.
Ex : Faire glisser le fichier bios6850.bin (Legacy) sur GOPupd.bat pour obtenir le nouveau fichier bios6850_updGOP.bin (UEFI)


En cas d'erreur sur le programme Python : "Le fichier spécifié est introuvable"
C:\Users\%Utilisateur%\AppData\Local\Microsoft\WindowsApps\python.exe
- Il faut supprimer les anciens programmes Python du répertoire indiqué.
- Il est possible aussi de modifier GOPupd.bat pour forcer le lancement de GOPupd.exe

5 - Charger le nouveau BIOS modifié bios6850_updGOP.bin dans la carte graphique avec le logiciel de flash du fabricant.
Note : En cas de blocage si même numéro de version, charger d'abord un BIOS plus ancien (original), puis redémarrer et charger le dernier BIOS modifié UEFI (+ récent).

6 - Eteindre le PC et déconnecter l'alimentation et le câble vidéo.

7 - Reconnecter alimentation et câble vidéo, puis démarrer le PC en mode UEFI...
Si l'erreur persiste, redémarrer

Note : le mode UEFI a un impact sur le fonctionnement du système, tous les périphériques doivent être compatibles UEFI et le disque dur/SSD pour Windows doit être formaté en GPT.
L'installation de Windows doit se faire depuis un support UEFI (clé USB, DVD...)

Attachment added to tutorial : BIOS F3 with UEFI tested OK for Gigabyte Radeon HD 6850 (GV-R685D5-1GD)

It works for an amd 8650g laptop, when selecting uefi it does not give me a signal to the screen


my laptop hp2072la bios insyde f2.a rev 3.7

Hey there,

could somebody please help me out with my GOP updated VBIOS for my laptop's 1080 GTX?
I am trying to update it via "GOPUpd v1.9.6.5.k mod v0.4.1 beta".

I have extracted my VBIOS via GPU-Z and when updating it via the script, I am given this output:

Zitat

---

Different sizes in ROM header and PCI structure of Legacy ROM!

EFI ROM is not last image!

Do you want to update GOP to 0x30012? Y for yes or N for no: y

There are other ROM images in this binary! Please report it!

EFI is NOT last image!

Fixing ID, last-image-bit and checksum for EFI image.


File "GP104_updGOP.rom" with updated GOP 0x30012 was written!

---

I have attached a full screenshot as well as the original VBIOS and the modified one.

Could some please check whether the created VBIOS is usable or possibly provide some hints as to how I can check it myself?
I don't want to risk bricking my GPU unless it's absolutely unavoidable :-/

Thank you very much in advance for any advice you can spare.

Hi @FrozenLord,
a method to test the file is to drag it to #Nvidia_ROM_Info.bat (or #AMD_ROM_Info.bat!)

Zitat von Ruin im Beitrag #1167

---

a method to test the file is to drag it to #Nvidia_ROM_Info.bat

---

Zitat von FrozenLord im Beitrag #1166

---

There are other ROM images in this binary! Please report it!
EFI is NOT last image!
Different sizes in ROM header and PCI structure of Legacy ROM!

---

NVIDIA Firmware Update Utility (Version 5.353.0)
Simplified Version For OEM Only
Checking for matches between display adapter(s) and image(s)...
 
Adapter: GeForce GTX 1080     (10DE,1BE0,1462,11F4) H:--:NRM  S:00,B:01,D:00,F:00
 
WARNING: Firmware image PCI Subsystem ID (1462.11FF)
  does not match adapter PCI Subsystem ID (1462.11F4).
 
Please press 'y' to confirm override of PCI Subsystem ID's:
Overriding PCI subsystem ID mismatch
Current      - Version:86.04.2B.00.1B ID:10DE:1BE0:1462:11FF
               GP104 Board (Normal Board)
Replace with - Version:86.04.2B.00.1B ID:10DE:1BE0:1462:11FF
               GP104 Board (Normal Board)
 
Update display adapter firmware?
Press 'y' to confirm (any other key to abort):
Identifying EEPROM...
EEPROM ID (C2,2534) : MX MX25U8033E 1.65-2.0V 8192Kx1S, page
Error preserving Inforom Image.
NOTE: Exception caught.
Nothing changed!
 

ERROR: Failed to merge Inforom image.
 

The updated (but not flashable) VBIOS does not show any strange output when checking it via the NVIDIA_ROM_Info:

Dumping info from = Prema_EVOC_1080_updGOP.ROM
 

NVIDIA Firmware Update Utility (Version 5.660.0)
Copyright (C) 1993-2020, NVIDIA Corporation. All rights reserved.
 

Sign-On Message       : GP104 E2915 SKU 10 VGA BIOS
Build GUID            : 00000000000000000000000000000000
IFR Subsystem ID      : 1462-11FF
Subsystem Vendor ID   : 0x1462
Subsystem ID          : 0x11FF
Version               : 86.04.2B.00.1B
Image Hash            : 422147CC033D8B27172063E374995522
Product Name          : GP104 Board
Device Name(s)        : GeForce GTX 1080
Board ID              : 0xED0E
Vendor ID             : 0x10DE
Device ID             : 0x1BE0
Hierarchy ID          : Normal Board
Chip SKU              : 750-0
Project               : 2915-0010
Build Date            : 07/05/16
Modification Date     : 07/17/16
UEFI Version          : 0x30012
UEFI Variant ID       : 0x0000000000000007 ( GP1xx )
UEFI Signer(s)        : Microsoft Corporation UEFI CA 2011
XUSB-FW Version ID    : N/A
XUSB-FW Build Time    : N/A
InfoROM Version       : G001.0000.01.03
InfoROM Backup        : Present
License Placeholder   : Not Present
GPU Mode              : N/A
 
Press any key to exit...
 

Just for reference, this is the unpatched output:

Dumping info from = Prema_EVOC_1080.ROM
 

NVIDIA Firmware Update Utility (Version 5.660.0)
Copyright (C) 1993-2020, NVIDIA Corporation. All rights reserved.
 

Sign-On Message       : GP104 E2915 SKU 10 VGA BIOS
Build GUID            : 00000000000000000000000000000000
IFR Subsystem ID      : 1462-11FF
Subsystem Vendor ID   : 0x1462
Subsystem ID          : 0x11FF
Version               : 86.04.2B.00.1B
Image Hash            : 422147CC033D8B27172063E374995522
Product Name          : GP104 Board
Device Name(s)        : GeForce GTX 1080
Board ID              : 0xED0E
Vendor ID             : 0x10DE
Device ID             : 0x1BE0
Hierarchy ID          : Normal Board
Chip SKU              : 750-0
Project               : 2915-0010
Build Date            : 07/05/16
Modification Date     : 07/17/16
UEFI Version          : 0x30002
UEFI Variant ID       : 0x0000000000000007 ( GP1xx )
UEFI Signer(s)        : Microsoft Corporation UEFI CA 2011
XUSB-FW Version ID    : N/A
XUSB-FW Build Time    : N/A
InfoROM Version       : G001.0000.01.03
InfoROM Backup        : Present
License Placeholder   : Not Present
GPU Mode              : N/A
 
Press any key to exit...
 

I did flash the preferred, non-updated VBIOS to my GPU again, hoping I might just be lucky and it would keep the updated GOP, but...

nvflash64.exe --version
 
NVIDIA Firmware Update Utility (Version 5.353.0)
Simplified Version For OEM Only
Adapter: GeForce GTX 1080     (10DE,1BE0,1462,11F4) H:--:NRM  S:00,B:01,D:00,F:00
 
Identifying EEPROM...
EEPROM ID (C2,2534) : MX MX25U8033E 1.65-2.0V 8192Kx1S, page
Reading adapter firmware image...
IFR Data Size         : 2172 bytes
IFR CRC32             : 0A7DEB3B
IFR Image Size        : 2560 bytes
IFR Image CRC32       : 5B716E58
IFR Subsystem ID      : 1462-11FF
Image Size            : 256512 bytes
Version               : 86.04.2B.00.1B
~CRC32                : 1E3DF9E6
Image Hash            : 422147CC033D8B27172063E374995522
OEM String            : NVIDIA
Vendor Name           : NVIDIA Corporation
Product Name          : GP104 Board
Product Revision      : Chip Rev
Device Name(s)        : GeForce GTX 1080
Board ID              : ED0E
PCI ID                : 10DE-1BE0
Subsystem ID          : 1462-11FF
Hierarchy ID          : Normal Board
Chip SKU              : 750-0
Project               : 2915-0010
CDP                   : N/A
Build Date            : 07/05/16
Modification Date     : 07/17/16
Build GUID            : 00000000000000000000000000000000
UEFI Support          : Yes
UEFI Version          : 0x30002 (Apr  1 2016 @ 20605201 )
UEFI Variant Id       : 0x0000000000000007 ( GP1xx )
UEFI Signer(s)        : Microsoft Corporation UEFI CA 2011
InfoROM Version       : G001.0000.01.03
InfoROM Backup Exist  : YES
License Placeholder   : Absent
GPU Mode              : N/A
Sign-On Message       : GP104 E2915 SKU 10 VGA BIOS
 

Unfortunately, I am now stuck with either the VBIOS I prefer, but an old GOP-version, or the updated GOP but the non-preferred VBIOS :-/
The other conclusion seems to be that the VBIOS structure (see files attached in my previous post) do seem to be incompatible with the update script.

GOPUpd v1.9.6.5.k mod v0.4.2 beta

[103020] v0.4.2 beta
built on: GOPUpd_v1.9.6.5.k
- Updated: Ampere GOP to 0x60009

Download

@clackersx

I noticed something about the AMD GOP file.
Because you always have the latest GOP file for the (5700XT) ;) and an X570 motherboard (PCI-E 4.0).
Could you please check which version of PCI your card is running on?

pci express render test: