@lordkag:

Python error:

Thank you very much Lordkag, I successfully updated my XFX Double Dissipation 7950 Boost with your tool and flashed my card. Now booting in full UEFI with CSM disabled.

@astrakan

Usually the boot time is faster when Fast Boot is enabled and Secure Boot disabled, which is where UEFI Boot and in particularly GOP is needed. You said you installed with Win7 option in UEFI mode, but if you used the present configuration, chances are Win7 option is equal to CSM enabled, thus a clean reinstall with CSM disabled is something to consider. The GOP is active and works, as can be seen from your tests. Not sure about Display Port vs DVI-D, but you can flash an older 1.57.0.0.0 version, by going to #GOP_Files and rename/switch amd_gop.efirom with amd_gop_1.57.0.0.0.efirom. The delay added by your HDDs is to be expected, larger drives have higher initialization time, maybe the spin-up time (which can be checked with CrystalDiskInfo, for instance) can be used as a reference. Maybe they can be initialized faster if you RAID them and Intel EFI RAID takes control during boot, but I wouldn't expect a magical boost, simply because chasing a faster boot and adding slower components is a contradiction. There may be a few more things to consider, but beyond this point it starts to be a little off-topic. GOPupd only deals with providing the GOP, not with boot times or OEM implementations.

@lsdmax

You need Python 3.x if you want to use the script instead of the executable. Either set the path from GOPupd.bat or remove the script so that the executable is used instead.

Thanks lordkag for your Gop Utility. My MSI GTX N660-2GD5/OC works in UEFI mode very well.

Zitat von lordkag im Beitrag #228

---

@astrakan

Usually the boot time is faster when Fast Boot is enabled and Secure Boot disabled, which is where UEFI Boot and in particularly GOP is needed. You said you installed with Win7 option in UEFI mode, but if you used the present configuration, chances are Win7 option is equal to CSM enabled, thus a clean reinstall with CSM disabled is something to consider. The GOP is active and works, as can be seen from your tests. Not sure about Display Port vs DVI-D, but you can flash an older 1.57.0.0.0 version, by going to #GOP_Files and rename/switch amd_gop.efirom with amd_gop_1.57.0.0.0.efirom. The delay added by your HDDs is to be expected, larger drives have higher initialization time, maybe the spin-up time (which can be checked with CrystalDiskInfo, for instance) can be used as a reference. Maybe they can be initialized faster if you RAID them and Intel EFI RAID takes control during boot, but I wouldn't expect a magical boost, simply because chasing a faster boot and adding slower components is a contradiction. There may be a few more things to consider, but beyond this point it starts to be a little off-topic. GOPupd only deals with providing the GOP, not with boot times or OEM implementations.

---

I've tried to build with efirom the compressed efi image but something got wrong as my GM200 vga doen't boot anymore in uefi mode (I had to boot in legacy and flash the old bios image).

I think I'll be waiting for lordkag to update his own tool.

@astrakan

I haven't read the manual of your board, but I assume there is no dedicated option for CSM Enabled/Disabled? Although Fast Boot would imply CSM Disabled. Not sure what is the reason for those WinX options, they are misleading and completely ignoring Linux world (no matter of its UEFI support). If you can't find other options in the manual for decreasing boot time (like CSM related or UEFI - Legacy priority or sign-on messages), I guess you are left with those 20 seconds. There isn't an official timer for UEFI Boot, it depends on configurations, OEM implementation, bugs and the list is open. Generally, the GOP is the last piece to complete the UEFI circle, that is to replace legacy OROMs and disable CSM, which is just Compatibility Support Module. Once you go to pure UEFI, not only do you gain seconds by dropping the long initialization of legacy OROMs, but you also drop the compatibility layer for legacy emulation. Your board already had EFI drivers for replacing the rest of Legacy ROMs, the GOP was the last piece to the puzzle. I suggest to open a support ticket on MSI forums, I suppose your board is still under warranty and they should have at least suggestions, if not fixes.

@plutomaniac

Thanks for old, present and future GOPs. Keep up the good work and in 20 years or so you might receive a new title.

@Sylar76

The first step should have been to remove the ffs container. Then EFIROM compression would come next, followed by the addition of custom EFI headers. I have a dirty script for the automation of this process, but it is not public because it is dirty and it has zero value for 99,99% users.

Released Version 1.9.1:
- updated GM2xx to 0x2000D, thanks to Plutomaniac.
- updated GM1xx_MXM to 0x10034, thanks to Plutomaniac.
- 0x2000D seems to be on pair with 0x10034, the newest codebase that I have encountered.

Zitat von lordkag im Beitrag #233

---

@Sylar76

The first step should have been to remove the ffs container. Then EFIROM compression would come next, followed by the addition of custom EFI headers. I have a dirty script for the automation of this process, but it is not public because it is dirty and it has zero value for 99,99% users.

---

Zitat von lordkag im Beitrag #233

---

@astrakan

I haven't read the manual of your board, but I assume there is no dedicated option for CSM Enabled/Disabled? Although Fast Boot would imply CSM Disabled. Not sure what is the reason for those WinX options, they are misleading and completely ignoring Linux world (no matter of its UEFI support). If you can't find other options in the manual for decreasing boot time (like CSM related or UEFI - Legacy priority or sign-on messages), I guess you are left with those 20 seconds. There isn't an official timer for UEFI Boot, it depends on configurations, OEM implementation, bugs and the list is open. Generally, the GOP is the last piece to complete the UEFI circle, that is to replace legacy OROMs and disable CSM, which is just Compatibility Support Module. Once you go to pure UEFI, not only do you gain seconds by dropping the long initialization of legacy OROMs, but you also drop the compatibility layer for legacy emulation. Your board already had EFI drivers for replacing the rest of Legacy ROMs, the GOP was the last piece to the puzzle. I suggest to open a support ticket on MSI forums, I suppose your board is still under warranty and they should have at least suggestions, if not fixes.

---

Thanks for the great work
i have accidentally flashed a legacy bios on my UEFI chip.Managed to bake a new UEFI/GOP enabled and flash it back on my GPU.running perfect so far

For those interested, here is NVFlash 5.265, which seems to be the first version to mention a GP1xx GOP, most likely the first version to fully support Pascal. Also a noticeable size increase.

Edit: An older version can be found <here>. And as always, patched versions can be found on <JoeDirt's thread>.

Posted a very minor release, which only adds support for detecting upcoming Pascal and detecting a new GOP type, called GOP Override. Don't have any info on what that GOP would do.

I would like to report that this worked successfully on my Zotac GTX 650 1GB Synergy Edition (GK107)!

Thank you very much!

Version 1.9.3
- updated AMD GOP to 1.60.0.15.50, thanks to TPU. Not sure why the strange numbers, but it is newer, signed and has the universal tables.
- updated GM2xx to 0x2000E, thanks to TPU.
- added support for very old Nvidia GOP releases, older than 0x10008. The version is stored in hex, thus I can only rely on my database to identify the matching GOP type.