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.
Hi, I want to make some upgrade tests, but I can't get a working Clone (made with CCC). I made it from NVME to a spare SSD, then I bless opencore 2 times, but I can't boot it.

The clone won't even show up in the recovery mode startup disk :/
 
Last edited:
Short version of a long, convoluted question: Is there an EFI driver available that allows OpenCore to "see" HID devices attached to an ASM1142-based USB3 PCIe card? For unpleasant reasons, and in a stomach-churning abuse of a 5Gbps port, my KVM really wants to be plugged into the ASM1142 card and not the Mac Pro front panel USB. At present, OpenCore happily ignores the keyboard and mouse. Any chance of making them usable in OpenCore (he asked, fully expecting a reply of "no," accompanied by eye-rolling and hearty derisive laughter)?

Thanks in advance. (I did search for an answer and found nothing relevant; my apologies if this is a FAQ or something.)
 
  • Like
Reactions: hwojtek
Short version of a long, convoluted question: Is there an EFI driver available that allows OpenCore to "see" HID devices attached to an ASM1142-based USB3 PCIe card? For unpleasant reasons, and in a stomach-churning abuse of a 5Gbps port, my KVM really wants to be plugged into the ASM1142 card and not the Mac Pro front panel USB. At present, OpenCore happily ignores the keyboard and mouse. Any chance of making them usable in OpenCore (he asked, fully expecting a reply of "no," accompanied by eye-rolling and hearty derisive laughter)?

Thanks in advance. (I did search for an answer and found nothing relevant; my apologies if this is a FAQ or something.)
You want a EFI 1.x compatible version of XhciDxe? I don't think it exists yet. I think edk2, Clover, and OpenCore all have a XhciDxe with varying differences. I think they're meant for UEFI 2.x.

I started work on a version for EFI 1.x but didn't get very far. It sort of works in a Parallels VM (UEFI). I haven't done much testing. Some things are not working. Maybe the EFI 1.x stuff doesn't recognize the XhciDxe. I was building it for USB booting. I haven't tried keyboard/mouse with it at all.

Does EFI work with multiple keyboards? I've never tried that.
 

Attachments

  • joevt_Xhci.zip
    200.1 KB · Views: 65
Partial support for UEFI 2.x drivers in EFI 1.x is available with ForgeUefiSupport in OpenCore. Perhaps that could be useful for XhciDxe.
 
Partial support for UEFI 2.x drivers in EFI 1.x is available with ForgeUefiSupport in OpenCore. Perhaps that could be useful for XhciDxe.
I created the forge UEFI idea that exists in OpenCore while doing some RefindPlus work so I am aware of at least those EFI/UEFI differences. Since we have all the XhciDxe source code, we don't need to require OpenCore's or RefindPlus' ForgeUefiSupport option - we can just replace the UEFI 2.x stuff in the XhciDxe source code with an EFI 1.x equivalent.

The idea is to be able to load the XhciDxe driver before the Startup Manager starts (using Driver#### and DriverOrder boot variables), so that you can boot from xHCI connected devices even without OpenCore or RefindPlus.

I wonder if the XhciDxe driver from the first Mac that supported USB 3.0 would be useful? Well, I think it would be nicer to have the XhciDxe source code working.
 
I created the forge UEFI idea that exists in OpenCore while doing some RefindPlus work so I am aware of at least those EFI/UEFI differences.
In that case, addressing those differences is surely not enough to get XhciDxe working in EFI 1.x...

I wonder if the XhciDxe driver from the first Mac that supported USB 3.0 would be useful?
I believe these are the first ones (from June 2012): MacBookAir5,1, MacBookAir5,2 MacBookPro9,1, MacBookPro10,1.

Edit: Unfortunately, it seems that USB 3.0 was initially supported in the OS but not in the firmware...
 
Last edited:
Updated: September 7, 2021

OpenCore on Legacy Apple Hardware

This guide explains how to use the excellent OpenCore bootloader on a Mac Pro 5,1 to install, run and update macOS Catalina and macOS Big Sur, resulting in a clean, unpatched operating system no different than on a supported Mac.

🚫 macOS Big Sur 11.3 and higher is currently not viable for the Mac Pro 5,1. A possible workaround is currently in testing.​

Why OpenCore?

There are several advantages to using OpenCore on a classic Mac Pro:

Boot picker screen (even with a standard graphics card)
View attachment 1723702
Software Update (just like on a supported Mac)
View attachment 1723703
Hardware acceleration (and DRM for Netflix on Safari)View attachment 1723704
Another approach to installing and running macOS on unsupported Macs consist of applying a series of rigid patches. Although effective, this strategy may be considered undesirable, because it alters system files—a potential problem for updates. With OpenCore, macOS remains entirely untouched. Necessary modifications take place cleanly in memory.

Why this Guide?

The purpose of this guide is to provide step-by-step hands-on instructions to using OpenCore on the Mac Pro 5,1. Included with the instructions is a basic sample configuration to get you started. Guidelines for creating a more advanced configuration customized to your machine are also detailed.

👍 The included sample configuration is about as minimal of a configuration as possible for using OpenCore on a Mac.​

Additional Resources

Since this guide appeared, other solutions to OpenCore on Apple hardware have been proposed. Here on MacRumors, you have a few options:
  1. This guide (step-by-step hands-on instructions)
  2. Martin's Package (very popular easy-to-install one-package-fits-all solution provided by @h9826790 with emphasis on hardware acceleration)
  3. MyBootMgr (great multi-boot solution provided by @Dayo with a rich suite of helper apps for setting up and maintaining RefindPlus and OpenCore)
  4. OC Plistlib Generator (diligent programmatic solution provided by @TECK for automating OpenCore updates)
Another great solution is the OpenCore Legacy Patcher (OCLP) provided by the Dortania team. This solution, which applies not only to the Mac Pro 5,1, probes your hardware to dynamically configure OpenCore for your Mac.

Requirements

This guide is aimed at systems with the following specifications:

Mac Pro modelEarly 2009 with MacPro5,1 firmware,* Mid 2010 or Mid 2012
Processor architectureWestmere (E56xx, L56xx, X56xx) / Gulftown (W36xx)
Boot ROM version144.0.0.0.0
GraphicsEFI (flashed) or a standard UEFI card (PC GPU) supported in Catalina or Big Sur
WirelessChipset supported in Catalina or Big Sur (BCM943224, BCM9435x, BCM9436x)

Need to upgrade your boot ROM? See the upgrade instructions.

Regarding Graphics: Several GPUs supported in macOS High Sierra are not supported in macOS Mojave or later. This includes all non-Kepler generation NVIDIA GPUs as well as AMD GPUs earlier than HD 7950. Several HD 78xx GPUs (Pitcairn) were rebadged as R9 2xx and are not supported in macOS Mojave or later. All classic Mac Pro factory GPUs had support removed with Mojave.

Acknowledgements

A big thank you to @vit9696 and the other talented developers of Acidanthera for making all of this possible. Special gratitude goes to @h9826790 for spearheading the hardware acceleration study and @startergo for the relentless testing that led to boot screen support. And thanks to all those that have contributed to this thread!


PART I
Basic Installation







PART II
Advanced Configuration





PART III
Maintenance





PART IV
Installing and Updating macOS




APPENDIX
Installing Windows and Linux
If you use the OCLP method to install Open Core when choosing the OS on setup do you have to choose an OS which is supported by the system or can you choose the OS you want to upgrade to which isn't at the moment supported until OC is installed?
 
My Mac Pro 5,1 is running Catalina 10.15.7 (19H1030), and the current OpenCore (0.73). With the latest mac/iOS security issue, I wanted to install the Security Update 2021-005, but "check for updates" says I'm up to date. I tried downloading the update, but it reports "This software is not supported on your system." but the log doesn't say why. Are other folks seeing this? How should I proceed with troubleshooting?
 
My Mac Pro 5,1 is running Catalina 10.15.7 (19H1030), and the current OpenCore (0.73). With the latest mac/iOS security issue, I wanted to install the Security Update 2021-005, but "check for updates" says I'm up to date. I tried downloading the update, but it reports "This software is not supported on your system." but the log doesn't say why. Are other folks seeing this? How should I proceed with troubleshooting?
Just went though this: The 2021-005 became only available after I had enrolled to the DeveloperSeed.
 
Last edited:
  • Like
Reactions: 0134168
My Mac Pro 5,1 is running Catalina 10.15.7 (19H1030), and the current OpenCore (0.73). With the latest mac/iOS security issue, I wanted to install the Security Update 2021-005, but "check for updates" says I'm up to date. I tried downloading the update, but it reports "This software is not supported on your system." but the log doesn't say why. Are other folks seeing this? How should I proceed with troubleshooting?
Have you enabled the VMM flag in your config.plist (see the 1st post)? You need that to show upgrades in Catalina.
 
Have you enabled the VMM flag in your config.plist (see the 1st post)? You need that to show upgrades in Catalina.
Right! I tried that, and indeed Software Update then prompted me to install that update, which seemed to go fine, then on the reboot after the black screen with apple and progress bar, I got the attached message (ERROR_3491501876). Fortunately, the reboot after that one was fine, but I was again running 19H1030, and am back to the state where it doesn't see the update, and won't let me install it manually. Hmmm.


Screen Shot 2021-09-16 at 10.57.34 AM.png
 
Last edited:
Right! I tried that, and indeed Software Update then prompted me to install that update, which seemed to go fine, then on the reboot after the black screen with apple and progress bar, I got the attached message (ERROR_3491501876). Fortunately, the reboot after that one was fine, but I was again running 19H1030, and am back to the state where it doesn't see the update, and won't let me install it manually. Hmmm.


View attachment 1833093
Well I am running out of suggestions....how are you enabling the -no_compat_check boot argument?
 
Well I am running out of suggestions....how are you enabling the -no_compat_check boot argument?
That's a good question - it was a long time ago that I set this up (and didn't take sufficient notes). It's not in my config.plist, but is there when I type `nvram boot-args`:

boot-args -no_compat_check

So I probably did the recovery NVRam procedure at some point. I no longer have Mojave handy, so it's not easy to check that. Thanks for your help, btw! You've given me lots of helpful things to search for and try.
 
My Mac Pro 5,1 is running Catalina 10.15.7 (19H1030), and the current OpenCore (0.73). With the latest mac/iOS security issue, I wanted to install the Security Update 2021-005, but "check for updates" says I'm up to date. I tried downloading the update, but it reports "This software is not supported on your system." but the log doesn't say why. Are other folks seeing this? How should I proceed with troubleshooting?
I have OC 0.7.3 installed with Martin's package on my 5,1. I just keep a copy of my OC config with the VMM flag enabled. I swap that, reboot and update. Then I put back the orig OC.conf with the VMM flag disabled so I have graphics acceleration back.
 
That's a good question - it was a long time ago that I set this up (and didn't take sufficient notes). It's not in my config.plist, but is there when I type `nvram boot-args`:

boot-args -no_compat_check

So I probably did the recovery NVRam procedure at some point. I no longer have Mojave handy, so it's not easy to check that. Thanks for your help, btw! You've given me lots of helpful things to search for and try.
I would try it in your config.plist. The "could not be installed on your computer" makes me think that might be an issue.
...and you are welcome. I'm sorry it hasn't worked yet but so many have helped me that I am happy to try and return the favor.
 
If you use the OCLP method to install Open Core when choosing the OS on setup do you have to choose an OS which is supported by the system or can you choose the OS you want to upgrade to which isn't at the moment supported until OC is installed?
What do you mean by "choosing the OS on setup"? Unless an unsupported OS has been previously patched, you won't be able to boot it without OpenCore, and it's not good practice to mix patched installs and OC.
 
Sorry for the bad description.
So, I have a blank ssd I set up the OCLP with Mojave and install to the blank SSD.
I then update to OS Catalina or Big Sur!
Or
Can I set the OCLP with Catalina and install to the blank SSD this jumping the middle process of the update?
Although my Mac only supports up to to Mojave at the moment without OC?
 
So, I have a blank ssd I set up the OCLP with Mojave and install to the blank SSD.
I then update to OS Catalina or Big Sur!
This will work.

Can I set the OCLP with Catalina and install to the blank SSD this jumping the middle process of the update?
Although my Mac only supports up to to Mojave at the moment without OC?
You'll only be able to boot Catalina (or its installer) once OC is installed. Unless you have a Mac-EFI graphics card to bless OC and another Mac to prepare your EFI folder, you'll need a natively bootable OS to install OC in the first place.
 
This will work.


You'll only be able to boot Catalina (or its installer) once OC is installed. Unless you have a Mac-EFI graphics card to bless OC and another Mac to prepare your EFI folder, you'll need a natively bootable OS to install OC in the first place.

Thank you cdf. I’ll have to install Mojave then update
 
Hi guys,

yesterday I had to reinstall Opencore, Mojave and Big Sur. Since the reinstallation of OC my windows partition (definitely working) is not showing up in the bootpicker anymore - do you know how I can get it back into my bootpicker? scan policy is set to 0 by the way...


Edit: Originally I used a bootable USB Stick for installation (if that makes a difference when trying to troubleshoot)
 
Last edited:
Hi guys,

yesterday I had to reinstall Opencore, Mojave and Big Sur. Since the reinstallation of OC my windows partition (definitely working) is not showing up in the bootpicker anymore - do you know how I can get it back into my bootpicker? scan policy is set to 0 by the way...


Edit: Originally I used a bootable USB Stick for installation (if that makes a difference when trying to troubleshoot)
Probably you have Windows installed in legacy mode. OC only can boot from efi Windows installations. Just press Alt BEFORE bootpicker loads. You will see your Windows installation.
 
Probably you have Windows installed in legacy mode. OC only can boot from efi Windows installations. Just press Alt BEFORE bootpicker loads. You will see your Windows installation.
Well if it was in legacy mode then it wouldn‘t have shown up until yesterday, right? Since I installed OC and macos new (windows is the same drive, no changes) It does not show up anymore
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.