With the smaller GOP found by "@Ausdauersportler" it would fit without any further mods for the linked bios in my posting #1120 and may work, if the GOP is compatible.
This 0xE300 sized AMD GCN4 GOP driver may already do the job.
Note: works in several Polaris MXM and PCI cards
You can always reprogram the card with a CH341A plus SOIC clip, even if it is bricked. Or at least it is VERY unlikely to get bricked worse than can be recovered by that. So if you are flashing an untested/experimental ROM it might be worth mastering the (fiddly!) art of getting this attached and reading from and writing to your card before you proceed. Ofc this needs to be done from another machine (or the same machine with a different GPU), probably easiest to do from Linux.Dare I ask about the chance of bricking the GPU from flashing your rom?
It will brick, because it is only the GOP-image and not complete rom.Dare I ask about the chance of bricking the GPU from flashing your rom?
It will brick, because it is only the GOP-image and not complete rom
Who do you answer?You have to be really REALLY patient. The boot process takes a long time, and reboots for at least four or five times, can't remember. The last boot will show a percentage number.%
I also played it safe with the DVi input.
I'm using Monterey 12.7.6 with OCLP 2.2.0 (and also without a boot screen).
Okay, I understand. Yes, it was secondhand. As I said, I have tested the switch in both positions. I'll install the original firmware and see what happens. Thanks.This is the most important clue. If you don't have OC/OCLP BootPicker, your GPU does not have the factory firmware.
If your GPU is a Sapphire Pulse that have a ROM switch, try to other position.
![]()
If not, you most probably have a 2nd hand sourced GPU that was previously used for crypto-mining with a custom GPU firmware and you'll need to re-flash the GPU factory firmware to have pre-boot configuration support with a Mac Pro and class 3+ UEFI PCs.
This is the post on how to re-flash the factory GPU firmware:
I've tried several graphics outputs with no results, including both positions of the GPU BIOS switch.
What could be the reason why, even after following all the steps, I still don't see a boot screen?
Thanks
_______________________________________________________________
Mac Pro 2009 (MP41)
Firmware 144.0.0.0.0 (latest) built on Fri Apr 12 12:48:00 2019
Bios Version $IBIOSI: MP51.88Z.F000.B00.1904121248
Bootloader AAPLEFI1.88Z.0005.I00.1010071430 built on Thu Oct 07 14:30:00 2010
Crossflash 4.1->5.1 (bootblock of MP51.007F.B03)
(U)efi version: 1.10
MP41, serial from firmware: YMXXXXXXXXG
MP41 backplane made in 2009
The firmware MAC in NVRAM matches with firmware MAC in dump
EnableGop 1.4 EFI module identified
Base_18 hardware descriptor, Fsys 0x04
Fs
Can't boot OCLP if your firmware is not updated.
bootblock of MP51.007F.B03
Need 144.
Mac Pro 2009 (MP41)
Firmware 144.0.0.0.0 (latest) built on Fri Apr 12 12:48:00 2019
Bios Version $IBIOSI: MP51.88Z.F000.B00.1904121248
Bootloader AAPLEFI1.88Z.0005.I00.1010071430 built on Thu Oct 07 14:30:00 2010
The Apple boot picker should be present immediately after the boot chime, if alt key is held. Nothing to do with what you describe.You have to be really REALLY patient. The boot process takes a long time, and reboots for at least four or five times, can't remember. The last boot will show a percentage number.%
I also played it safe with the DVi input.
Would it be possible to put e.g. a GT 120 in the cMP alongside a bricked AMD card, boot into Linux using this working card, then re-flash the bricked card from there? I imagine amdvbflash would not recognise an Nvidia card, else one would need to be very careful getting the identifier right. Just an idea. What do you think?You can always reprogram the card with a CH341A plus SOIC clip, even if it is bricked. Or at least it is VERY unlikely to get bricked worse than can be recovered by that. So if you are flashing an untested/experimental ROM it might be worth mastering the (fiddly!) art of getting this attached and reading from and writing to your card before you proceed. Ofc this needs to be done from another machine (or the same machine with a different GPU), probably easiest to do from Linux.
Please report if the card works.
Usually older versions read the information only from the vbios-image and that remains untouched. For AMDVBFLASH it seems totally identical.Amdvbflash reported no problems. Indeed, it doesn't seem to see any difference between the new bios and the old.
Well thanks anyway. The old cMP feels much more useful now. Already got Ubuntu Mate 24.04 as a boot option. Couldn't do it before.Usually older versions read the information only from the vbios-image and that remains untouched. For AMDVBFLASH it seems totally identical.
I only added (inserted) the GOPEnabler and didn't need the "short" GOP image found by "Ausdauersportler". But for future usage may helpful, perhaps s.o. will edit the automated script for AMD, avoiding to break the 0x20000 byte border.
My bad, I understood wrong. I thought it was booting repeatedly. SORRY ALLWhile BootBlock version AAPLEFI1.88Z.0005.I00.1010071430 will have a black screen at POST when cold booting with a PCIe switched card installed, it won't have issues with EnableGOP. Zero. Nada.
Also, from what you wrote, you seem to not understand what the BootBlock is. Look at this:
The BootBlock is first sector that is loaded at power on from the BootROM flash memory and is the code that instructs the hardware what to do immediately after power on and after it was installed at the factory is never updated again, at least not until you'll flash a reconstructed/never booted BootROM image.