I didn't notice it was that oldI'm always surprised by people who respond to threads that have been dead for years.
Who waits for a response for more than 20 months?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MP 1,1-5,1 Mac Pro 5.1 with RX560 and Boot Screen
- Thread starter maitrenageur
- Start date
- Sort by reaction score
I'm picking up an RX560 with the hope to use it in a dual boot Mac Pro 5,1. I will need to flash the BIOS on the card. Any help is appreciated. I dual boot, so I need the boot screen.
From what I understand, the process on a Windows PC is:
- Use AMDVBFlash -s to get the current BIOS from the card
- Use GOPUpdate to update the BIOS
- Use AMDVBFlash -p to flash the updated BIOS back to the video card
After using GOPUpdate, is there a step that I'm missing? According to http://themacelite.wikidot.com/creating-a-mac-pro-efi-vbios-with-enablegop I should also be using OpenCorePkg, but the instructions use a Mac for this step.
[update]
It looks like I need to edit the BIOS that I've created with GOPUpdate as Trying to use the instructions for OpenCorePkg tells me that I don't have enough room... Except there is no place to download the required "atomdis" program.
I need to create a video BIOS for a Sapphire HD5830 card and/or an Asus RX560 O2G card.
Last edited:
Imo it's way more easier and useful to add EnableGop to the Mac firmware, so you can just pop in "any" modern GPU and have the boot screen.
Sounds good...
Using the video at Ultimate Mac Pro 5,1 One More Thing... Enable_GOP - YouTube, I've created my firmware with the EnableGOPDirect 1.4 EFI module.
I've flashed the firmware and the machine still boots fine with my nVidia GTX680 card... Now to install the AMD card.
Thank you for all the help!
Last edited:
I'm having an issue with this Mac Pro and I'm wondering if the firmware mod that adds EnableGop is causing it...
I have tried several times to wipe the hard drive, install Mac OS (Mojave and Catalina) and use the App Store or iCloud. I can not complete the verification steps for either.
When I use iCloud I accept the terms and conditions and click continue, and the terms and conditions page comes back again.
If I try to use the App Store, it tells me that my Apple ID has not been used with the App Store and that I need to review my account information. I review the information and it's all correct, but the Continue button is disabled.
Would this firmware mod alter some kind of digital signature that Apple uses for iCloud and the App Store?
I have tried several times to wipe the hard drive, install Mac OS (Mojave and Catalina) and use the App Store or iCloud. I can not complete the verification steps for either.
When I use iCloud I accept the terms and conditions and click continue, and the terms and conditions page comes back again.
If I try to use the App Store, it tells me that my Apple ID has not been used with the App Store and that I need to review my account information. I review the information and it's all correct, but the Continue button is disabled.
Would this firmware mod alter some kind of digital signature that Apple uses for iCloud and the App Store?
No, EnableGop is a module that resides in a completely different area of the BootROM from where the hardwareIDs are stored. The most probable is that your BootROM image could be currently missing one/more/all of the 7 hardwareIDs that are necessary for identification as a real Mac when logging into iCloud/Messages/FaceTime.
Another thing, AppStore does not validate the hardwareIDs of the Mac for the log in process, only later with FairPlay and etc when running the apps, so, your issues with AppStore is not related to the BootROM.
You can always re-flash your backup without EnableGop injected and see if the problems stop.
Is there a way to view these seven hardwareIDs and validate them?
My issue in the App Store occurs when I'm asked to review my personal details, name and address and such. I just can't click Continue there. What's really odd is if I click "back" on that screen I go back to the country selection screen and the Continue button on that screen is now disabled. It wasn't disabled the first time I went through this screen.
Some of the hardwareIDs, like SON, MLB SN and BuildDate, require BootROM image inspection since macOS does not expose it publicly.
>AboutThisMac still have your SSN?
Did you fully updated Mojave BEFORE trying to log in to iCloud? Messages works?
My Dumper reads them all, reports in the GUI version if all are present and in expected order. Also it tells if checksums are wrong.
As people would show those readouts in boards, I hide them with the GUI variant. Using the Dumper / test_nvram in cli variant shows those data points, tho it can not validate them for the App Store / Apple Services.
See the signature.
My serial number is still there.
I have fully updated Mojave. I just checked and there are no pending updates.
I can log into Messages, and send messages to myself.
This is very odd... Things are acting a bit differently this morning...
When I log into the AppleID website everything seems fine, EXCEPT that my phone number is unavailable for iMessage and FaceTime because I don't have a SIM associated. I'm going to assume that its because it's not an iPhone. I've never seen this before.
The App store still has that last Continue button disabled.
I just tried to sign into iCloud through the Preferences panel this morning and something different is happening. I'm told that my Apple ID could not be used to sign in to iCloud (34608). That's the first time I've seen that.
You have something going wrong, but at first look is not the BootROM since you wrote that you can login to Messages, this alone eliminates any basic BootROM issues since Messages validate the hardwareIDs. The Mac AppStore issues are not directly related to the BootROM, like I already wrote.
Solve all issues that your AppleID and iCloud could have with AppleID/iCloud websites first. Talk to Apple support, check if you need to accept any agreements and etc.
After that, do a clean install WITHOUT adding your AppleID or iCloud while running the Install Assistant, first do all the software updates and only after fully updated and rebooted, you'll add your AppleID/iCloud accounts.
Thanks!
The Dumper doesn't seem to indicate any issues. The CRC32 checksum is OK.
That means, technically the content is ok, as far as the method goes.
That doesnt means, the content is valid. For example, if someone cloned another machine, and there are two machines with same IDs.
If you do not know the history of the machine (was the backplane replaced, was it built from parts), you should compare the system serial with the serial of the sticker.
And if you want more details, compare the board serial with the serial the CLI variant reads (using test_nvram in Terminal). Downside is, that the backplane serial is under the CPU cage, so you need to dismantle the Mac a bit.
Of course, never post such serials. The Dumper is hiding them, for a reason.
You can let Alex check the firmware, as he has the experience in checking the firmware from a logical view. My Dumper checks the firmware more technical. Reading all checksums, appearance of data points in right order and position, wrong headers, etc etc.
Last edited:
See what @tsialex said - also make sure you can login with your appleid at appleid.apple.com and make sure that there is nothing going on with your appleid and password.