MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro

[cdf]

if I clone my boot drive to a fresh SSD, boot from and set it as my primary boot disk and follow these upgrade instructions and I have problems - will I be able to switch my old Mojave drive back in and boot/run exactly as I did before? Or will there have been a hardware (firmware?) update that I can’t roll back?

Yes to your first question. In fact, you should always have a disk with a Mojave installation lying around that you can insert in your Mac Pro to boot natively in case you face any issues with your OC setup. If you don’t have native boot-screen support, the process typically requires removing the disk with the problematic setup to let your Mac Pro pick up the Mojave installation.

The OC setup described in the guide will not result in any irreversible changes to the firmware. Any such changes will occur deliberately when you possibly do the required firmware update to the latest BootROM (144.0.0.0.0) or when you optionally add EnableGOP to get native boot-screen support.

…I also read that there are issues with usb 1.0 (and to connect keyboards etc via a usb 2.0 hub) but all my ports are usb 2.0. I use a Magic Keyboard and mouse via Bluetooth so I’m concerned they might not work. Should I use a corded mouse and keyboard for the install? Do Bluetooth peripherals no longer work after install?

Your Mac Pro’s USB ports internally connect to both USB 2.0 (EHCI) and 1.1 (UHCI) controllers. The problem is that modern versions of macOS no longer include drivers for the USB 1.1 controller. Fortunately, your Mac Pro’s firmware does have such a driver, so provided that any USB 1.1 devices (such as keyboards, mice and Bluetooth adapters) are connected prior to booting, they will still work in modern versions of macOS until disconnected. Though not necessary, having a wired keyboard and mouse for doing the initial setup is a good idea.

 

[Upgrader]

Yes to your first question. In fact, you should always have a disk with a Mojave installation lying around that you can insert in your Mac Pro to boot natively in case you face any issues with your OC setup. If you don’t have native boot-screen support, the process typically requires removing the disk with the problematic setup to let your Mac Pro pick up the Mojave installation.

The OC setup described in the guide will not result in any irreversible changes to the firmware. Any such changes will occur deliberately when you possibly do the required firmware update to the latest BootROM (144.0.0.0.0) or when you optionally add EnableGOP to get native boot-screen support.



Your Mac Pro’s USB ports internally connect to both USB 2.0 (EHCI) and 1.1 (UHCI) controllers. The problem is that modern versions of macOS no longer include drivers for the USB 1.1 controller. Fortunately, your Mac Pro’s firmware does have such a driver, so provided that any USB 1.1 devices (such as keyboards, mice and Bluetooth adapters) are connected prior to booting, they will still work in modern versions of macOS until disconnected. Though not necessary, having a wired keyboard and mouse for doing the initial setup is a good idea.

Thanks cdf.

I think I'm already on BootROM 144.0.0.0.0. I'd like native boot-screen support but I've survived without it for years so I won't add EnableGOP. I'd like to retain my ability to switch back to my Mojave SSD if required.

 

[Upgrader]

Yes to your first question. In fact, you should always have a disk with a Mojave installation lying around that you can insert in your Mac Pro to boot natively in case you face any issues with your OC setup. If you don’t have native boot-screen support, the process typically requires removing the disk with the problematic setup to let your Mac Pro pick up the Mojave installation.

The OC setup described in the guide will not result in any irreversible changes to the firmware. Any such changes will occur deliberately when you possibly do the required firmware update to the latest BootROM (144.0.0.0.0) or when you optionally add EnableGOP to get native boot-screen support.



Your Mac Pro’s USB ports internally connect to both USB 2.0 (EHCI) and 1.1 (UHCI) controllers. The problem is that modern versions of macOS no longer include drivers for the USB 1.1 controller. Fortunately, your Mac Pro’s firmware does have such a driver, so provided that any USB 1.1 devices (such as keyboards, mice and Bluetooth adapters) are connected prior to booting, they will still work in modern versions of macOS until disconnected. Though not necessary, having a wired keyboard and mouse for doing the initial setup is a good idea.

...and did I read correctly that Open Core will only reliably go up to a Monterey install?

 

[flaubert]

...and did I read correctly that Open Core will only reliably go up to a Monterey install?

Yes, that is correct.

 

[Upgrader]

One more question - I saw another user was having lots of trouble getting Open Core to install and boot and part of the advice was to install their GFX card in slot 2. Is this standard advice and a requirement on the 5,1? I ask as my boot drive is currently in slot 2. Thanks.

 

[Upgrader]

Any such changes will occur deliberately when you possibly do the required firmware update to the latest BootROM (144.0.0.0.0) or when you optionally add EnableGOP to get native boot-screen support.

Just to be clear - I'm reading about EnableGOP and it appears that it's a runtime command only - so this doesn't change the Mac's firmware right? I could enable and disable EnableGOP without jeopardising my ability to switch my old Mojave SSD back into my Mac?

 

[cdf]

One more question - I saw another user was having lots of trouble getting Open Core to install and boot and part of the advice was to install their GFX card in slot 2. Is this standard advice and a requirement on the 5,1? I ask as my boot drive is currently in slot 2. Thanks.

This is not a requirement, but because of the many system variations, you may need to experiment to determine what works best for you. The guide on page 1 mentions this in regard to determining boot order priority of your drives.

Just to be clear - I'm reading about EnableGOP and it appears that it's a runtime command only - so this doesn't change the Mac's firmware right? I could enable and disable EnableGOP without jeopardising my ability to switch my old Mojave SSD back into my Mac?

EnableGOP is added to firmware (see the Appendix in the guide). It will not affect your ability to boot any version of macOS. However, if the flashing process is not done correctly, it is possible to brick your Mac. Read the instructions carefully and make sure you understand everything before proceeding. Of course, it’s still possible to enjoy OC and the boot screen it provides without EnableGOP. That’s how we did it for many years!

 

[flaubert]

If you don't mind spending a little money, you can get EnableGOP as part of @tsialex 's boot rom reconstruction service. This makes it really convenient to be able to use Option-Boot to choose different boot disks; the boot picker you get with OpenCore is also very helpful, but by the time you get the Picker option visible OpenCore has been loaded, which can be limiting as far was what you are going to boot into (the config.plist for booting into Mojave would have different optimizations than the config.plist for booting Monterey, for example).

 

[Upgrader]

If you don't mind spending a little money, you can get EnableGOP as part of @tsialex 's boot rom reconstruction service. This makes it really convenient to be able to use Option-Boot to choose different boot disks; the boot picker you get with OpenCore is also very helpful, but by the time you get the Picker option visible OpenCore has been loaded, which can be limiting as far was what you are going to boot into (the config.plist for booting into Mojave would have different optimizations than the config.plist for booting Monterey, for example).

I don't have room for my old Mojave disk to be permanently installed to be able to switch between but thanks for the shout - it may be helpful down the line.

 

[Macschrauber]

Mavericks is so slim. It can be even installed on a 32 GB Stick. I have old ssds with as less as 32GB for such test and rescue systems.

 

[michaelfanoe]

HI and thanks for the great forum. I have been sneaking on the site for many years and been doing hackingtosh for years - after 5-6 y of hiatus on just running plain boring windows - i decided to go all in on Mac Pro because its such a beautfyl piece of junk. I have Monterey Boot SSD - Mojave backup SSD and a full legacy Win10 pro install on SSD and 1tb timemachine and loads of drives i want to make use of. So happy for this Opencore, cadeus to all of you ! Are there any special manual settings i need to attend to, before installing an experimental LINUX on a seperate SSD ? things i need to be carefull about. Will it f... up my nice install ? does the OP support this in bootpick - sorry im fairly new to it all. Again, thx.

 

[eVasilis]

Hi all

Could anyone please tell me why I have an "EFI" boot option in the opencore boot menu and how to get rid of it? Recently, I deleted the "Microsoft" folder from the EFI boot partition and formatted the windows drive and that is when it appeared.

Thanks

 

[eVasilis]

Anyone?

 

[mrkapqa]

Hello, I had 2 of EFI Bootoption available. Deleting eg. Compressing first and then deleting an onymous "system" folder in the EFI partition onwhere OC is stored got rid of the one superfluous EFI Bootoption. I have been told it is an leftover of a previous OCLP installation. When I booted the MacPro today I noticed also the other EFI Option gone at OpenCore Menü; don't know why but suppose it is OK that way.

 

[Macschrauber]

Hello, I had 2 of EFI Bootoption available. Deleting eg. Compressing first and then deleting an onymous "system" folder in the EFI partition onwhere OC is stored got rid of the one superfluous EFI Bootoption. I have been told it is an leftover of a previous OCLP installation. When I booted the MacPro today I noticed also the other EFI Option gone at OpenCore Menü; don't know why but suppose it is OK that way.

if you had used the ESP tools of my Dumper package you had seen the ESPs like that example:

Macschrauber-s-Rom-Dump/ESP_tools.md at main · Macschrauber/Macschrauber-s-Rom-Dump

A tool for dumping and analysing Mac firmwares. Plus flashing for Mac Pro 4.1 / 5.1 - Macschrauber/Macschrauber-s-Rom-Dump

github.com

 

[mrkapqa]

if you had used the ESP tools of my Dumper package you had seen the ESPs like that example:
View attachment 2391107

Macschrauber-s-Rom-Dump/ESP_tools.md at main · Macschrauber/Macschrauber-s-Rom-Dump

A tool for dumping and analysing Mac firmwares. Plus flashing for Mac Pro 4.1 / 5.1 - Macschrauber/Macschrauber-s-Rom-Dump

github.com

yes, i had somehow used those, but among the noteworthy to the case it showed only "BOOT: Windows, Windows ( active) ESP" > which confused me (since it states "active"); and "OpenCore (MartinLo 1.0.x) ESP" it would not take into account the other maybe incriminating folder "system" causing the second EFI entry, maybe because it was on the same SSD/HDD as where OpenCore (MartinLo 1.0.x) ESP was/is stored?

 

[Macschrauber]

yes, i had somehow used those, but among the noteworthy to the case it showed only "BOOT: Windows, Windows ( active) ESP" > which confused me (since it states "active"); and "OpenCore (MartinLo 1.0.x) ESP" it would not take into account the other maybe incriminating folder "system" causing the second EFI entry, maybe because it was on the same SSD/HDD as where OpenCore (MartinLo 1.0.x) ESP was/is stored?

I dont tested what happens when someone is mixing up a Windows ESP and OpenCore in the same ESP. This is something what should not be done.

Otherwise, I see one Windows ESP and one MartinLo ESP, each on different disks. Active means that Bootx64.efi is present in /EFI/Boot.

So this Windows ESP could be booted directly and would sign the bootrom with certificates.

If you mount that Windows ESP with the tool, it asks to deactivate Bootx64.efi by renaming it to Bootx64.efioff

This is no 100% lockout, as Windows updates or repairs could write that .efi file again. But better than nothing, anyway.

OpenCore does not need that file to boot Uefi Windows. So its a little protection, better than none.

Of course, the best protection is a bootrom backup and to check it regulary.

 

[Upgrader]

Hi all, advice needed please.

I had planned on a manual OC upgrade but a last minute job has come in that requires me to upgrade asap and start work.

My main OC requirement is that my 5,1 runs steady on Monterey for the next year until the M4 Mac Studios arrive. I won’t need a boot screen (the boot picker will do) or any other tweaks - I just need a reliable install.

Given my requirements, are there any major drawbacks to OCLP over a manual install?

Thanks.

 

[mrkapqa]

I dont tested what happens when someone is mixing up a Windows ESP and OpenCore in the same ESP. This is something what should not be done.

it seems there was a leftover of a previos OCLP or something on the same HDD where OC is installed, therefore it must have been picked up and shown constantly 2 EFI entries (icons) during Boot-up-Picker œOC; after deleting the "System" folder on the same HDD, the one EFI (certainaly superfluous) disappeared, as eventually did the other.

I did not have Windows EFI and OC on the same HDD, misunderstanding;

the folder structure on the HDD looked like in this screenshot.

 

[mrkapqa]

Hi all, advice needed please.

I had planned on a manual OC upgrade but a last minute job has come in that requires me to upgrade asap and start work.

My main OC requirement is that my 5,1 runs steady on Monterey for the next year until the M4 Mac Studios arrive. I won’t need a boot screen (the boot picker will do) or any other tweaks - I just need a reliable install.

Given my requirements, are there any major drawbacks to OCLP over a manual install?

Thanks.

can't remeember what didn't function, but it was enough for me to dislike it immediately on the MacPro;
with MartinLo package the experience was much better, and it was not difficult to install;
there must a also manual install, but that seemed to difficult to me;

Activate AMD hardware acceleration

I created a new "easy to install package" as per many requested (based on the official OpenCore). [The attached package updated to 1.0.0] For those who only need HWAccel, post #594 has everything you need. This new package mainly offer HWAccel + boot screen. Also, this package should work in...

forums.macrumors.com

 

[Macschrauber]

it seems there was a leftover of a previos OCLP or something on the same HDD where OC is installed, therefore it must have been picked up and shown constantly 2 EFI entries (icons) during Boot-up-Picker œOC; after deleting the "System" folder on the same HDD, the one EFI (certainaly superfluous) disappeared, as eventually did the other.

I did not have Windows EFI and OC on the same HDD, misunderstanding;

the folder structure on the HDD looked like in this screenshot.

yes that is a mixup with OpenCore and OpenCoreLegacy Patcher. OCLP mimics an efi bootloader in an Apple System Folder, so the folder System.

 

[eVasilis]

Hi all

Could anyone please tell me why I have an "EFI" boot option in the opencore boot menu and how to get rid of it? Recently, I deleted the "Microsoft" folder from the EFI boot partition and formatted the windows drive and that is when it appeared.

Thanks

Well, I cannot figure it out. Still there! FYI, I have never, ever installed OCLP on my mac pro so that gets me confused.

 

[Macschrauber]

Well, I cannot figure it out. Still there! FYI, I have never, ever installed OCLP on my mac pro so that gets me confused.

See https://forums.macrumors.com/thread...opencore-on-the-mac-pro.2207814/post-33227018 for some helpers mounting and identifying ESPs.

 

[paalb]

upgrade asap and start work

I just need a reliable install

Given my requirements, are there any major drawbacks to OCLP over a manual install?

In both cases, you’re best of reading all the documentation.

I found it confusing if to find out what parts of the OCLP documentation that were pertinent to my mac. I had to experiment with several OCLP installations on my MacBook Pro before it worked. It’s half a year ago now so I do not remember the details but when my first install got problems, I had to remove some files while in secure boot and terminal. I was not sure this would help, but luckily, it worked.

On my two MacPros following the instructions in first post here sentence after sentence everything worked at first try on both.

This documentation is fine-tuned over several years and is excellent.

 

[eVasilis]

See https://forums.macrumors.com/thread...opencore-on-the-mac-pro.2207814/post-33227018 for some helpers mounting and identifying ESPs.

I did run your esp tools and there're 3 active esps", the opencore, which is active, one in the vanilla Mojave disk and one in the nvme one that I use to run monterey. The culprit is the monterey one as I still had the extra efi boot option when I removed the mojave disk. However, the extra efi option only appeared when I removed windows from my mac pro. The question now is, is it safe to delete the contents of the nvme efi? - Cheers!

PS. The opencore EFI is on an ssd in sata bay 1, not on the nvme.