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 Manually Configured OpenCore on the Mac Pro
- Thread starter cdf
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
I just thought about my flashed 7970. You are correct. I forgot that I had to do the same. It's been a few years....Still I say keep all kexts on the system as we are all so used to doing. It's safer.
I have not flashed R9 280X I'll check it sometime later
it's safe for me to keep their kexts in OpenCore)) I don't like to change something in the system
Since updating to OpenCore 0.60 from 0.59 I have had two problems.
(1) I have been unable to boot into Big Sur (beta 3) from the OpenCanopy boot/ picker and
(2) I have been unable to spoof to iMacPro 1,1 (using code at post 7) to be able to update to beta 4.
It just shows as my cMP 5,1.
I followed post 1 rigorously. I even tried starting from scratch with a completely new install of Opencore 0.60
It's not that I haven't done these things with previous versions of either OpenCore or 'spoofing' iMacPro 1,1 for Big Sur installations or update of betas
I upgraded from OpenCore O.57 to 0.58 to 0.59. (and now 0.60)
I also spoofed iMacPro 1,1 to install Big Sur beta 1, then again spoofed to iMacPro 1,1 for an OTA upgrade to beta 2 and again to beta 3.
I tried not spoofing and just set VMM on as per post 3459 (when I had a working 0.59) - said I was up to date.
Is there there other something else I can try?
(1) I have been unable to boot into Big Sur (beta 3) from the OpenCanopy boot/ picker and
(2) I have been unable to spoof to iMacPro 1,1 (using code at post 7) to be able to update to beta 4.
It just shows as my cMP 5,1.
I followed post 1 rigorously. I even tried starting from scratch with a completely new install of Opencore 0.60
It's not that I haven't done these things with previous versions of either OpenCore or 'spoofing' iMacPro 1,1 for Big Sur installations or update of betas
I upgraded from OpenCore O.57 to 0.58 to 0.59. (and now 0.60)
I also spoofed iMacPro 1,1 to install Big Sur beta 1, then again spoofed to iMacPro 1,1 for an OTA upgrade to beta 2 and again to beta 3.
I tried not spoofing and just set VMM on as per post 3459 (when I had a working 0.59) - said I was up to date.
Is there there other something else I can try?
Does anyone have success with MacPro 4,1-5,1 and OpenCore with macOS Big Sur and have working firewire? I have it working in macOS Catalina however Big Sur in system profile sees I have a firewire card but my audio device will Lock and sync but not activate.
Update: After waiting so long for the installation to complete I have a winner. My USB installed and is running macOS Catalina USB as formatted. I can see it in bootlicker and I can launch successfully. It just took so long to complete the process. How can I help you now?
@vit9696 I know this is a weird request, but could you add to OpenCore a feature that allows to boot with BigSur KernelCollection (or BootKernelExtensions.kc) using an "automatic exited single user mode" ?
Currently I can use CMD+S from OpenCore, and then type "exit" to continue booting, but if you could automatize this routine and possibly showing the apple logo with loading bar during it.
Currently I can use CMD+S from OpenCore, and then type "exit" to continue booting, but if you could automatize this routine and possibly showing the apple logo with loading bar during it.
Many thanks nobullone. So you installed Catalina to your external hard drive, and it boots straight up from OC's boot picker? My setup is a little different. I didn't install Catalina to my USB drive, I cloned my existing NVMe install across to it using Carbon Copy Cloner. The USB drive with Catalina is seen in the OC boot picker, but immediately fails when I try booting from it (returning to the boot picker after a few seconds). Not sure what the problem could be.
If you cloned it from the NVMe, do you now have two installs of OC in EFI on USB and NVMe? Can't be good.
Hey. I could only assume that there is something wrong with the clone image. Try it on another USB drive. If you are able to boot an installation through open core and that install drive shows in bootpicker then an operating system should boot, also. I spent a lot of time doing this for you so show me your work. LOL!
The EFI volume on the USB drive is empty - the creator of CCC said the contents of the NVMe EFI aren’t cloned, as in legit Mac installs it’s only ever used temporarily, for firmware updates etc.
Last edited:
I’ll try reformatting the drive and cloning again. It’s a mix of APFS and HFS+ partitions at the moment. I’ll report back!
It didn't work after reformatting and creating 2 APFS partitions - same result. Interestingly, it will boot into the Recovery partition on the USB drive, just not the main macOS install (this may have been working previously - I didn't test). I'm now trying the clone using SuperDuper!, in case that does something slightly different when cloning.
If I have no joy with that, I'll try dedicating the whole drive to the macOS backup. It'll be a pain if it won't boot USB drives with multiple partitions, but if it works it will at least help to isolate the issue.
Just a random thought - might this have something to do with 'blessing' the install, to make it bootable?
Update: cloning macOS with SuperDuper! rather than CCC made it bootable off USB... to a point. It loads slowly, as you would expect off USB 2, then when the progress bar gets to the end only one of my three screens lights up (the one using DVI) and it slows a garbled picture. The mouse cursor moves, but that's as far as it goes. Does anyone have any idea why this might be?
Instead of cloning try a straight installation. USB drives are tricky. You'll never know it's bad until you try and make it an installer or opsys. Some just won't boot. My installation took about 2 hours on a non-powered 128GB USB drive. I'm glad my first shot went in. Otherwise, I would be tackling this until I won or conceded. Has anyone else mentioned this problem? I figured it was the multiple bootable EFIs confusing the boot loader.
The thing is, this is primarily a backup of my system drive - the ability to boot from it is a bonus, that could be useful should I need to boot this or another Mac from an external drive with my full / current install. I've already got a 3.5" SATA HDD with a stock install of Mojave 10.14.6 on it that I can slot in and boot from if necessary.
Just to be clear - my USB drive is a 2.5" HDD in a USB 3 enclosure, not a thumb drive. Also, there shouldn't be multiple EFIs. To check, I mounted the EFI volume of my external HDD and there was nothing in it, whether the clone was done by CCC or SD.
I've wiped the drive so there's now a single volume (no partitions) and am currently cloning my system drive across. We'll see if that makes it bootable.
I'm surprised by the lack of comments on this issue - I would have thought everyone on the forum would have a bootable backup of their system drive - has no one tried booting from it? I probably wouldn't have if it weren't necessary to clone to non-encrypted APFS on the first run, then boot into the clone and turn on FileVault (can't do an initial clone of Catalina directly to an encrypted drive).
Last edited:
Yes - 0.59 works fine (kept a copy of the whole EFI). Just staying with it at present ...