Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Snipping tool for screenshots.

Here you'll find all/most versions of AMDVBFLASH: https://www.techpowerup.com/download/ati-atiflash/
Use the button left in the middle "Show older versions" and you'll get all hosted versions.

Something is wrong with the card, maybe a driver issue. GPU-Z shows wrong memory size, clockspeed, power draw,....
 
Last edited:
Ah hah. So now I am in Windows, and my darling wife may not appreciate me spending a few yours flashing this card tonight.

I am in Windows now. Here is a photo of the desktop showing card details. I do not recall how to do a screen grab of a Windows screen, so excuse the quality:

View attachment 2414136

View attachment 2414137

First problem: several places say to use AMDVBFlash 2.93 (August 15th, 2019). But that I cannot find that version.

I tried a later one and the screen showed a back window for a split second, and then disappeared.

Hmm ... this might get frustrating! I have the Windows PC running from the intel chip's GPU. And I updated Windows to current, because I thought the late versions of AMDVBFlash did not like the old Windows.

I have not chosen a bios yet. The information does show it's using Samsung RAM. I have not back it up as the switch is set to the bad bios - which does work in Windows when I booted it via the Windows BIOS screen. Without doing that the RX 580 did not show a signal to my monitor. All a bit strange.

So, the brand new shrink wrapped Sapphire Pulse was flashed with a MSI firmware?

GPU INFO.jpg


The most probable is that this was a GPU that someone tried to flash the firmware stolen from MacVidcards and then returned to the seller.

Btw, you can't know if the card really have a Samsung memory as GPU-Z says when the GPU is flashed with a incorrect firmware.
 
  • Like
Reactions: Ausdauersportler
So, the brand new shrink wrapped Sapphire Pulse was flashed with a MSI firmware?

View attachment 2414181

The most probable is that this was a GPU that someone tried to flash the firmware stolen from MacVidcards and then returned to the seller.

Btw, you can't know if the card really have a Samsung memory as GPU-Z says when the GPU is flashed with a incorrect firmware.

Hmm ... yeh.

I've gone through my records and my memory was wrong.

What happened was I bought a new RX 580, the correct one, but did not install it. Their price went right up, and I thought I should sell it and wait for their prices to come down. So I made a good profit on it.

But then I realised I wanted one (I had thought about twin thinner 460s and also some Pro cards which are good for CAD), so I bought another one - for more than I sold the card I bought new!!! The seller is a local Mac repairer and he claimed he never used it ... in fact, he not only buggered it up, but he even broke it's duel bios switch, and he never told me any of that. To break that switch, he must have gone berserk I reckon. The package was sold and it looked brand new too, it was all shrink wrapped. But those shrink plastic rolls with un-winders and hot air blow guns are cheap and every retailer has one!! Ebay can be a dangerous place if one doesn't test things immediately!

I got stung all right!

I was looking at a brand new XFX RX 580 today, with a three year warranty - but it turns out it's a Chinese style with the 2048 or something ... that doesn't work. For about $US90. The same retailer has a 6600XT for around $US155. I thought about that, but they can get complicated.

Mucking around with flashing, I saw various reports about the high prices of GPUs are going to get worse. I realised that is another reason why Apple leant towards dropping 3rd party GPUs - the amount of profit those companies make - AMD and Nvidia - would have been too much for Apple to take. So they gave up on the upgradeable model and kicked it into the gutter. Along with the 7,1 i guess which was a deception, sadly. But then if they had continued on with Intel or even AMD and threadrippers, I reckon the bargain 7,1s would not exist, and the cheap ones out there would never have come onto the market.

I did not install the card into the Windows computer properly or one part of that AMDVBFlash installation ... and I found the correct evidently 2.9x version as well. I will have a go soon, and I have only three bios's to try, because of the branding on the label which indicates just three bios available. I will try them one at a time until one works I guess. A bit painful but it serves me right ....

My son and I put the Windows PC together, and then he changed the motherboard with a mate who is training specialist doctor (friends from school), and their installation was very messy. The PC filters and blades are covered in brown thick dust and the thing is very noisy indeed. I will clean it and I feel like changing the fans to something quite. It's a Lian box and has a couple of nice things, and a whole lot of bad ones as well. I bought it's 1000 watt power supply years ago and it's still going, and at least it is quiet.

I seem hypnotised by the pleasant appearance of the Mac interface. It should not mater, but the Windows one is worse than a Mac was back in system 8 days. I presume Win 11 looks good. I am not doing any of it tonight as I've had some fab red wine from the Barossa, and I fear I may wreck things!

Thanks for the assistance! MP
 
Last edited:
Well Tsialex, now I know why the switch was damaged. I think the fellow tried to rip it out, because the other memory could not be fixed. I have tried, but the viewing apps - several different versions of AMDVBFlash - cannot access the card.

I might get lucky with the remaining bios though. Here is a pic of it, but I am not sure how reliable its information is, and I presume the driver date is somehow due to the AMDVBFlash driver that the software requires one to do to use AMDVBFlash, at least the later versions of that software do.

I guess I will risk the card, of course I'll back up this bios. But I know its not doing what is required. If not successful I may buy a 6600XT and flash that so it would work in the 5,1. New ones are cheap and it would run off the same power as an RX 580. Other cards are rare - no 6800s here - everything seems to be 70 series now which do not work.

Switch_other_semi_operational_way.gif
 
Last edited:
You should try to flash the fitting rom, if you can't get a refund.
Maybe the card has a sticker with SKU on it and open the housing to identify the VRAM.
 
You should try to flash the fitting rom, if you can't get a refund.
Maybe the card has a sticker with SKU on it and open the housing to identify the VRAM.
No way I'd get a refund, I've had the card quite a while.

As far as the VRAM goes, that makes sense, but from the thread on flashing one, a card like mine which PN number is S88-4E353-830SA, the 353 part of that number indicates it has Samsung memory but there are 4 bios which may work ... so I reckon I will have to operate the windows computer on its Intel CPU graphics processor, and flash the card and test it on the mac. So four flashes I think and eventually it should work. Otherwise I'll buy a used one, they come up now and then. I'll make sure I can return it if it doesn't work!!! Thanks again ...
 
Hi Guys.
I've been here before but had to make a new account cause i can't find my old one.

I'm about to attempt this upgrade, but wanted to get a few questions out of the way. but first, a bit about my system:

it's a 4,1 flashed to 5,1 with 144 firmware. Currently I have no system running on it but have had linux, win, and mojave running.
i have the original nvidia g120 and an rx580 in it right now. both were working under RHEL [my last working system install]. i use the gt120 for pre-bootscreen stuff. right now grub was the last bootloader i had on it. my original backup copy of osx [which i upgraded to mojave] will not boot anymore. the grey screen comes up with an apple and progress bar but then just stays grey. I was able to get into the mac utilities menu though, and could not start from the startup disk picker utility [it does see the OSx system image though].

what i'd like to do is put a baremetal host like kvm on it and then have vms for different applications.


So my questions are:

is there an installer that works in linux? i don't have a working copy of OSx. if not, what flavour of OSx should i install [or can install] to get this working [and how do you get it]? can the flash be done from a usb?

my assumption is that i will have to reinstall a copy of osx and then follow this procedure. it would be nice to know which to use and anything else precautionary to prevent bricking during this process. the last 2 times i flashed the firmware everything was fine.

any help is appreciated.
 
Last edited:
I had Tsialex make a clean ROM, but to do so you need to access the Mac.

But if you do not have a working mac, it's more difficult to make an install USB drive. If you have access to a Mac, then it is not difficult. I've not made an install disk from using a Windows pc. It said to be possible. I thought using a "virtual machine".

You can download an OS from Apple directly, or Major geeks has them, Dr Mac, . I recommend Diskmaker though.

Links to Apple for downloads:
https://apps.apple.com/us/app/macos-mojave/id1398502828
https://itunes.apple.com/us/app/macos-high-sierra/id1246284741

I used Diskmaker - the ex Lion Diskmaker - software to easily make a boot usb install disk and he has different downloads for making each OS and making a boot disk is very easy, although please follow his instructions. It's free but I donated because I found it great. That Parisian did what Apple should have done. https://diskmakerx.com/download/
 
Last edited:
i can see the mojave volume in recovery mode, just can't boot to it. tried target disk mode, holding cmd-x, mounting the drive and setting the boot volume.

there are a lot of 'dead' [untitled] entries in diskutil list. i can see the efi partition, mojave, preboot, recovery, vm in a container partition and another partition named macos base system.

i'm thinking either grub is in the way, even after resetting nvram. i didn't target the drive properly in the cli command. or there are too many partitions and it can't find the right one.

have to remove gt120 to reinstall. will it still show recovery mode on the metal card? or do i have to install sierra then upgrade to mojave?
 
By the way, I took my sapphire card apart - no spring screws, missing heat sink, too many contact points too large an area for my thermal grizzly extreme (its thick too even if heating), I put the GPU away and bought a used one. It works fine. I wonder if I should have spent some more and bought a new 6600XT, they are new and cheap but need flashing.
 
Last edited:
repair disk just stalls.

not sure if my osx disk is mbr or gpt, either way i'm pretty sure it's just not being found. i'll try resetting nvram/pram several times. if that doesn't work it could be something like the os partition is labelled differently from what is on the mbr.
 
Start from the minimum config and then test and work up?

So pulling RAM because maybe one of the RAM cards might be faulty. Afterall things were working, then suddenly were not. Use only one drive and only one GPU. Remove all the PCI cards as well (but for the GPU).

I'd start with just a single stick (depending on each stick's size - you'll need at least 4 GB RAM but maybe its got a minimum of 8) and see what happens.

I think you need to pop a drive into one of the SATA drives (easy place is a DVD port) pop a system install USB thumb drive into an original USB slot, and re-start and let the computer install a fresh OS Mac OS onto that drive (which the install will format). You might have an original OS DVD install disc and you might have a DVD drive in the computer.

A High Sierra install USB would be fine. Ultimately Apple desk at a store might supply you an install drive ... or buy one from Ebay - that is if you do not have access to another Mac. With a mac, its easy to make a USB install drive.

A sata SSD drive can go into the DVD drive area and plug in easily, they cost from $US12 up, $50 for a Crucial 500 GB version I think (but check for mac OS compatibility) from Amazon.

There are lots of Unix versions that install from USB drives too and theat also run off the USB slot. You must know all that! There would be instructions inside the Linux booted via the USB port to interrogate the hardware as well.

But it seems to me if you want to easily interrogate what is wrong with the Apple hardware its very easy to do so via a clean install of Mac OS onto a minimum spec 4,1=>5,1..
 
Last edited:
  • Like
Reactions: MacNB2
Start from the minimum config and then test and work up?

So pulling RAM because maybe one of the RAM cards might be faulty. Afterall things were working, then suddenly were not. Use only one drive and only one GPU. Remove all the PCI cards as well (but for the GPU).

I'd start with just a single stick (depending on each stick's size - you'll need at least 4 GB RAM but maybe its got a minimum of 8) and see what happens.

I think you need to pop a drive into one of the SATA drives (easy place is a DVD port) pop a system install USB thumb drive into an original USB slot, and re-start and let the computer install a fresh OS Mac OS onto that drive (which the install will format). You might have an original OS DVD install disc and you might have a DVD drive in the computer.

A High Sierra install USB would be fine. Ultimately Apple desk at a store might supply you an install drive ... or buy one from Ebay - that is if you do not have access to another Mac. With a mac, its easy to make a USB install drive.

A sata SSD drive can go into the DVD drive area and plug in easily, they cost from $US12 up, $50 for a Crucial 500 GB version I think (but check for mac OS compatibility) from Amazon.

There are lots of Unix versions that install from USB drives too and theat also run off the USB slot. You must know all that! There would be instructions inside the Linux booted via the USB port to interrogate the hardware as well.

But it seems to me if you want to easily interrogate what is wrong with the Apple hardware its very easy to do so via a clean install of Mac OS onto a minimum spec 4,1=>5,1..
i'm not sure how to proceed. none of that [that i could do] has worked. i do have a dvd player and the original install disc, but it's on the 144 firmware. then there's something about metal cards. need non metal gt120 to access the startup but then need to have the metal installed to upgrade the os.

all i really need to do is get the thing flashed so i can use [any?] card at startup. then i can lose the gt120 and just proceed with a linux install [the idea is to run KVM bare metal. wanted debian, but might be more practical to go with ubuntu. anyone tried BSD?]. but have to install OSx or get the drive [with OSx on it] working.

also, i'm not sure what to do about the bootloader. just go with opencore, grub, or can we just go stock now with the gpu flash? what would be best for KVM?

iirc, the system had opencore to do the firmware upgrade. then i installed a bunch of different OS over the years. now i'm not exactly sure what's happening. if the firmware is supposed to point to an MBR or gpt table, if it's opencore doing it. i suspect it is like i posted, all those weird entries and things are just mislabelled now. i thought nvram/pram reset was supposed to ignore all that, but it doesn't seem to want to find the current OSx drive or the linux drive [tested them separately one at a time].
 
Hi,

I finally have a Mac boot screen for the GTX 770/780 and GTX 960/970. I downloaded the stock VBIOS firmware from the TechPowerUp site, used GOP_Updater, and then inserted EnableGop_1.4.efi. Now, all the cards show a Mac boot screen. That's really great!

However, I don't fully understand why GOP_Updater is necessary, since the stock VBIOS for the GTX 770/780 and 960/970 already contains an Nvidia GOP, as shown in the attached screenshot. Although GOP_Updater installs a newer GOP version, without it, EnableGop does not display a Mac boot screen with any of these cards.

There's a catch, though. While the EnableGop-patched GTX 770/780 and 960/970 work in a Mac Pro (Firmware 144.0.0.0) and can boot into macOS or UEFI Windows (installed from USB), the GTX 960/970, unlike the 770/780, will no longer work in a PC and cannot boot Legacy Windows MBR. The PC simply beeps six times right after power on, indicating an issue with the graphics card.

I have confirmed that the problem arises only after patching the VBIOS with EnableGop, not with GOP_Updater. I also see no differences in the feedback when patching the Kepler or Maxwell series; everything looks identical.

What could be causing the issue where the GTX 960/970 only work in a Mac but not in a PC?

Thanks!
 

Attachments

  • picture2.PNG
    picture2.PNG
    57 KB · Views: 29
  • picture1.PNG
    picture1.PNG
    84.9 KB · Views: 26
  • Screen Shot 2024-10-23 at 12.29.49 AM.png
    Screen Shot 2024-10-23 at 12.29.49 AM.png
    282.7 KB · Views: 28
Last edited:
Can you attach all files?

Some vbios have incomplete (dummy placeholder) instead full GOP image.
Are you responding to me? From what I can tell incomplete or missing GOP isn't the case.

You can download the original vbios from https://www.techpowerup.com/vgabios/169674/zotac-gtx960-2048-141225
It shows UEFI supported.

Attached is the modified vbios after patching with GOP_Updater. This file works in UEFI and BIOS (PCI Legacy) mode, which I've tested.

The problem starts after using vBiosInsert.sh to insert EnableGop_1.4.efi. Attached as well, called macEFI. I'm using OpenCore-1.0.2-RELEASE, which is the latest I can find. Same issue, however, in 1.0.1 too.
 

Attachments

  • Zotac.GTX960.2048.141225_macEFI.rom.zip
    146.9 KB · Views: 19
  • Zotac.GTX960.2048.141225_updGOP.rom.zip
    133.6 KB · Views: 18
Are you responding to me? From what I can tell incomplete or missing GOP isn't the case.

You can download the original vbios from https://www.techpowerup.com/vgabios/169674/zotac-gtx960-2048-141225
It shows UEFI supported.

Attached is the modified vbios after patching with GOP_Updater. This file works in UEFI and BIOS (PCI Legacy) mode, which I've tested.

The problem starts after using vBiosInsert.sh to insert EnableGop_1.4.efi. Attached as well, called macEFI. I'm using OpenCore-1.0.2-RELEASE, which is the latest I can find.

Why inject EnableGop to the GPU firmware with a MacPro5,1?

  • More complex than injecting to the MacPro5,1 BootROM and error prone process.
  • Some GPUs does not even have the space to do it.
  • I also had the same problem as you found, some GPUs are not compatible with some PCs anymore, requiring a reflash of the GPU firmware to use it.
  • Makes the GPU incompatible with MacPro3,1, since the boot process completely hangs when you ask for the BootPicker.

Inject EnableGop to the MacPro5,1 BootROM, just update the GPU GOP to the most recent version and have a lot simpler/universal solution.
 
Last edited:
i'm not sure how to proceed. none of that [that i could do] has worked. i do have a dvd player and the original install disc, but it's on the 144 firmware. then there's something about metal cards. need non metal gt120 to access the startup but then need to have the metal installed to upgrade the os.

all i really need to do is get the thing flashed so i can use [any?] card at startup. then i can lose the gt120 and just proceed with a linux install [the idea is to run KVM bare metal. wanted debian, but might be more practical to go with ubuntu. anyone tried BSD?]. but have to install OSx or get the drive [with OSx on it] working.

also, i'm not sure what to do about the bootloader. just go with opencore, grub, or can we just go stock now with the gpu flash? what would be best for KVM?

iirc, the system had opencore to do the firmware upgrade. then i installed a bunch of different OS over the years. now i'm not exactly sure what's happening. if the firmware is supposed to point to an MBR or gpt table, if it's opencore doing it. i suspect it is like i posted, all those weird entries and things are just mislabelled now. i thought nvram/pram reset was supposed to ignore all that, but it doesn't seem to want to find the current OSx drive or the linux drive [tested them separately one at a time].
Tsialex
i'm not sure how to proceed. none of that [that i could do] has worked. i do have a dvd player and the original install disc, but it's on the 144 firmware. then there's something about metal cards. need non metal gt120 to access the startup but then need to have the metal installed to upgrade the os.

all i really need to do is get the thing flashed so i can use [any?] card at startup. then i can lose the gt120 and just proceed with a linux install [the idea is to run KVM bare metal. wanted debian, but might be more practical to go with ubuntu. anyone tried BSD?]. but have to install OSx or get the drive [with OSx on it] working.

also, i'm not sure what to do about the bootloader. just go with opencore, grub, or can we just go stock now with the gpu flash? what would be best for KVM?

iirc, the system had opencore to do the firmware upgrade. then i installed a bunch of different OS over the years. now i'm not exactly sure what's happening. if the firmware is supposed to point to an MBR or gpt table, if it's opencore doing it. i suspect it is like i posted, all those weird entries and things are just mislabelled now. i thought nvram/pram reset was supposed to ignore all that, but it doesn't seem to want to find the current OSx drive or the linux drive [tested them separately one at a time].
Tsialex can check your hardware by you sending him data on your computer, and he'll send a file to update the firmware including enabling almost all GPUs that can work in a classic mac to work without issues and also without having to flash the GPU (a risky procedure).
 
  • Like
Reactions: 0134168
Why inject EnableGop to the GPU firmare?

  • Complex and prone to error process.
  • Some GPUs do not even have the space to do it.
  • Like you found, you will have issues with some GPUs when using it back with PCs, requiring removal.
  • Makes the GPU completely incompatible with MacPro3,1.

Inject EnableGop to the MacPro5,1 BootROM, just update the GPU GOP to the most recent version and have a lot simpler/universal solution.
Really, I don´t know why people don´t understnd this. @tsialex sent me the reconstructed ROM and never a single problem. And i have tried with so many GPU´s.
 
  • Like
Reactions: Melbourne Park
Why inject EnableGop to the GPU firmare?

  • Complex and prone to error process.
  • Some GPUs do not even have the space to do it.
  • Like you found, you will have issues with some GPUs when using it back with PCs, requiring removal.
  • Makes the GPU completely incompatible with MacPro3,1.

Inject EnableGop to the MacPro5,1 BootROM, just update the GPU GOP to the most recent version and have a lot simpler/universal solution.
How did you verify the last point? EnableGop - where ever you install it - does not interfere with normal boot process unless you press the alt/option key or force the picker via NVRAM settings. But the result would be the very same in the MacPro3,1, with or without the non working EnableGop driver you get a black screen and stalled boot process (tested this on iMacs and the MacPro3,1).

Your first point is true for the firmware patching and flashing, too. Read here :) But in general I would prefer the firmware mod instead of touching multiple cards.
 
How did you verify the last point? EnableGop - where ever you install it - does not interfere with normal boot process unless you press the alt/option key or force the picker via NVRAM settings. But the result would be the very same in the MacPro3,1, with or without the non working EnableGop driver you get a black screen and stalled boot process (tested this on iMacs and the MacPro3,1).

The last time I've tested and the first post of the thread says that EnableGop is not compatible with MacPro3,1:

[*]The current version of the driver is NOT compatible with the MacPro3,1, it will make the boot process hang and should not be installed there, in the MacPro3,1 BootROM or the GPU firmware


Your first point is true for the firmware patching and flashing, too. Read here :) But in general I would prefer the firmware mod instead of touching multiple cards.

I don't see why you make a parallel between upgrading Mojave firmware and EnableGop injection to the BootROM since upgrading MacPro5,1 firmware is an Apple official procedure.

Anyway, doing it to the MacPro5,1 BootROM is a one time operation, the process is relatively simple and very good documented, while doing it to the GPUs is always something and you need to do each one of the GPUs you gonna use.
 
  • Like
Reactions: 0134168
The last time I've tested and the first post of the thread says that EnableGop is not compatible with MacPro3,1:
Sorry, @Bmju said, but I tested it. Not compatible means it does not provide an EFI picker.
You can add multiple modules to the firmware as long as you do not make use of it.
So your claim is simply wrong!
I don't see why you make a parallel between upgrading Mojave firmware and EnableGop injection to the BootROM since upgrading MacPro5,1 firmware is an Apple official procedure.
Open your eyes, it is not simple, check the numerous red printed boxes and the following discussion. It is simple for you after hundred of mods and flashes, while flashing a GPU is simple for me, after hundreds of ...

The adoption rate of firmware flashes compared to GPU BIOS flashes is 1:1000 when try an estimation based on posts on the iMac GPU thread and even this procedure is a nightmare for most users willing to mod an iMac. Same is true for adding PC graphics cards to cMP. While most users are willing to do the pure hardware mod only a few a willing to experiment with flashing. These guys survive with a mining BIOS and use AMDGOP injection instead of fixing the root cause.
Anyway, doing it to the MacPro5,1 BootROM is a one time operation, the process is relatively simple and very good documented, while doing it to the GPUs is always something and you need to do each one of the GPUs you gonna use.
GPU vBIOS flashing is a one time operation and support by all vendors, they all provide tools.
 
Last edited:
  • Like
Reactions: Borowski
Sorry, @Bmju said, but I tested it. Not compatible means it does not provide an EFI picker.
You can add multiple modules to the firmware as long as you do not make use of it.
So your claim is simply wrong!

So, why do it to the MacPro3,1 if you gonna have the boot process HANG when you need it?!? In my point of view this completely incompatible, as I wrote from the start.

Open your eyes, it is not simple, check the numerous red printed boxes and the following discussion. It is simple for you after hundred of mods and flashes, while flashing a GPU is simple for me, after hundreds of ...

The adoption rate of firmware flashes compared to GPU BIOS flashes is 1:1000 when try an estimation based on posts on the iMac GPU thread and even this procedure is a nightmare for most users willing to mod an iMac. Same is true for adding PC graphics cards to cMP. Which most users are willing to do the pure hardware mod only a few a willing to experiment with flashing. These guys survive with a mining BIOS and use AMDGOP injection instead of fixing the root cause.

I respect your different experience with iMacs, but completely disagree with your view point since this discussion is about a MacPro5,1, see below.

Since seems you are not going to convince me and I'm not going to convince you…

GPU vBIOS flashing is a one time operation and support by all vendors, they all provide tools.

Did you remember the original post to this discussion? The specific user case? Remember that is someone that changes the GPUs between his Mac and PCs, have at least two GPUs.

My points are valid, is an error prone process, some GPUs do not have space and you need to remove EnableGop to have the GPU usable with a PC later. I have the problem of the GPU not working with PCs anymore in my lab almost every week and I do not flash GPUs anymore specifically because of that - I always go back to the most recent factory firmware, update the GOP module to the most recent version available and nothing else.


P.S.:

Added MacPro5,1 to my post that originated this discussion to make it clear to someone that finds it without reading the context:

Why inject EnableGop to the GPU firmware with a MacPro5,1?

  • More complex than injecting to the MacPro5,1 BootROM and error prone process.
  • Some GPUs does not even have the space to do it.
  • I also had the same problem as you found, some GPUs are not compatible with some PCs anymore, requiring a reflash of the GPU firmware to use it.
  • Makes the GPU incompatible with MacPro3,1, since the boot process completely hangs when you ask for the BootPicker.

Inject EnableGop to the MacPro5,1 BootROM, just update the GPU GOP to the most recent version and have a lot simpler/universal solution.
 
  • Love
Reactions: 840quadra
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.