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.
[mention]Dayo [/mention]that information would be helpful for the RFP/OC thread.
The guide has been updated to OpenCore version 0.6.7.

Please note that in order to more strictly follow OpenCore's specification, the sample configuration for 0.6.7 has undergone exceptionally considerable changes. If your configuration is based on the sample, it is advised to recreate it from the new file.
maybe quote it and write some thougts about it, what that means for MyBootMgr Tools Users.?
 
MyBootMgr has always strictly followed OpenCore specs and there are no thoughts on this with respect to RP/OC apart from that it is a welcome development.

Btw, you either use this or that and should try to avoid mixing and matching ... unless you fully understand what you are doing of course.
 
Last edited:
Your (...) disk is a PCIe AHCI / NVMe,
SATA connected to a SATA3 card
or SATA connected to a south bridge SATA port?

Sorry Alex. No ofense. IMHO your question cannot be understood by mere mortals, as you are trowing all possible buzzword at once into the mix. but hey - thank you for the prosa. Let me translate & structure this into an informative text;

Basically we can have 4 Variants of Storage inside our cMacPro:
• SATA 2 (or SAS) Disk in a Drive Bay | AHCI protocol
• SATA 3 Disk on a PCIe Card | AHCI protocol
• AHCI Blade with ??? Connector on a PCIe Card | AHCI protocol
• SSD NVMe Blade with M.2 Connector on a PCIe Card | NVMe protocol

...and there are few other Blades with non M.2 Connector in the wild (e.g. Apple's own proprietary SSD Blades)
 
You guys do a really amazing job keeping our CMPs alive, congratulations and my sincere thanks !!!

OC updated to 0.6.7 working like a charm with Catalina, hardware acceleration included and also the Titan Ridge with all my "accessories" .. with the pertinent warm restart (for which I understand there is no solution?)
I still haven't changed to BS because of WMware Fusion 12, as you know better than I only works with Catalina on our CMP 5.1 ... although I will soon migrate my virtual machines to my NAS and say goodbye to WMware after many years so hello to BigSur thanks to your tireless work.
 
  • Like
Reactions: racer
Sorry Alex. No ofense. IMHO your question cannot be understood by mere mortals, as you are trowing all possible buzzword at once into the mix. but hey - thank you for the prosa. Let me translate & structure this into an informative text;

Basically we can have 4 Variants of Storage inside our cMacPro:
• SATA 2 (or SAS) Disk in a Drive Bay | AHCI protocol
• SATA 3 Disk on a PCIe Card | AHCI protocol
• AHCI Blade with ??? Connector on a PCIe Card | AHCI protocol
• SSD NVMe Blade with M.2 Connector on a PCIe Card | NVMe protocol

...and there are few other Blades with non M.2 Connector in the wild (e.g. Apple's own proprietary SSD Blades)
Seems you are missing that my question was directed to @RicheeThree and he understood perfectly what I was asking without any translation… o_O
 
Sorry if this is obvious all, but I'm just wondering how to do a fresh install of Big Sur. Currently running OC 0.6.7 (Martin Lo config) and Mojave on internal PCIe drive and want to test Big Sur compatibility with certain software and hardware.

Do I have to do a fresh install of Mojave on a spare SSD, install opencore, then upgrade to Big Sur - or can I go straight to Big Sur on the blank SSD somehow?

Thanks!
 
Hi all

Just out of curiosity, what are the undesired effects in the case DirectGopRendering is set to "true". I set it to "true" but so far I can't notice anything different. Btw, my gpu is a radeon rx 580 pulse.

Thanks.
 
Sorry if this is obvious all, but I'm just wondering how to do a fresh install of Big Sur. Currently running OC 0.6.7 (Martin Lo config) and Mojave on internal PCIe drive and want to test Big Sur compatibility with certain software and hardware.

Do I have to do a fresh install of Mojave on a spare SSD, install opencore, then upgrade to Big Sur - or can I go straight to Big Sur on the blank SSD somehow?

Thanks!
If you have OC already configured, use the boot picker to load the BS installer from a bootable USB. Or, you can install BS directly from within Mojave as long as OC virtualization is on. In either case, just select the separate drive you wish to install to.
 
  • Like
Reactions: Sharky II
Hey Guys. Two quick questions:
1. My late 2012 MBP is running Big Sur with OCLP 0.6.7 and it runs fine with everything working but the fans run almost all the time when I am only using Safari, nothing else is open in the background.
2. I got my son a mid 2012 MBA with 4gig ram and 256gig hard drive in it. It is currently running Catalina and I installed OCLP onto it and booted it into BS with an external disk. it runs very slow- is this because it only has 4 gigs or ram and would it be recommended to leave it on Catalina or is there a fix for this slowness
 
Used the lasted OCLP on the Mac Pro and everything worked great. Not so much on the iMac but it’s going to.
Only problem I’m having is that the Mac Pro won’t fully boot to the login screen unless a monitor is connected to it. Usually I boot it and then screen share from iMac to do things. But now the Mac Pro won’t show up on the network until I plug a screen in.
anyone know why that would do that?
 
If you have OC already configured, use the boot picker to load the BS installer from a bootable USB. Or, you can install BS directly from within Mojave as long as OC virtualization is on. In either case, just select the separate drive you wish to install to.
Thank you - I assume by 'If you have OC already configured' you mean on the new/blank drive and not just on the main boot drive? I've done that yes.

I don't know much about OC virtualisation so am happy to do it the 'old fashioned/normal way!
 
Folks, I'm having a nightmare creating a bootable Big Sur 11.2.2 USB installer... it's not being recognised as a bootable drive by my Mac Pro (4,1 -> 5,1 MP on Mojave with OC 0.6.7) nor my 2012 MacBook Pro (Catalina, Big Sur unsupported). It doesn't show on the Opencore boot picker screen nor in 'Startup Disk' in System Prefs.

1) The USB drives I've tried are formatted GUID Partition Map and OSX Journaled (Extended)

2) I've tried downloading Big Sur using installinstallmacos script as well as via the Software Update.

3) I've tried using the Terminal as well as 'Install Disk Creator' to create the drive.

4) I've tried two different USB thumb drives

Can anyone suggest what I could be doing wrong?

Thanks
 
Folks, I'm having a nightmare creating a bootable Big Sur 11.2.2 USB installer... it's not being recognised as a bootable drive by my Mac Pro (4,1 -> 5,1 MP on Mojave with OC 0.6.7) nor my 2012 MacBook Pro (Catalina, Big Sur unsupported). It doesn't show on the Opencore boot picker screen nor in 'Startup Disk' in System Prefs.

1) The USB drives I've tried are formatted GUID Partition Map and OSX Journaled (Extended)

2) I've tried downloading Big Sur using installinstallmacos script as well as via the Software Update.

3) I've tried using the Terminal as well as 'Install Disk Creator' to create the drive.

4) I've tried two different USB thumb drives

Can anyone suggest what I could be doing wrong?

Thanks
Is OpenCore configured to boot from USB drives?

Are you plugging your USB drive into a factory USB port, or into a PCIe expansion card? If the latter, OC cannot boot from 3rd party USB cards. Please try a factory port instead.
 
  • Like
Reactions: Sharky II
Hi,

I tried both actually (USB2 factory port and USB3 PCIe) - but I finally got the boot loader to see the Big Sur USB installer drive - I had to plug it into the Mac just as the Mac 'bongs'/chimes. Strange. If it's plugged in when the Mac is turned on, it doesn't see it... bizarre. For some reason I can't get OSX 'Startup Disk' in System Prefs to see the Big Sur USB boot drive.

With regards to the blank/fresh 'test' SSD, I'm going to put it in an internal drive bay just to be safe, but I just want to be 100% - as I'm doing a clean install, I do need to install OC on the SSD and bless the drive before installing Big Sur on it, right?

Thanks!

Edit: Some level of success achieved...!

I have some other issues, the installer for my PCIe audio drive won't work and so I tried to drag the pref pane and kext from Mojave to Big Sur, but I can't get access to SSD / System / Library / Extensions, even with SIP disabled.

I will address this issue another time... its 3am!

Thanks again for your help, all.
Screenshot 2021-03-07 at 02.53.32.png
 
Last edited:
cMP 3,1, oclp 0.0.14, oc 0.6.8, 20D80 work quite nice on a 3.5" hdd, non-metal graphics not so sluggish, "voodoo" onboard audio doesn't work but, thankfully, firewire audio does. Good job.
generic.png
 
  • Like
Reactions: Ausdauersportler
Me again ... sorry.
I installed OC EFI on a removable stick in case OC is failing, so i can fallback to my native mojave installation. Everything fine since my forst OC install via Martins package 0.6.4. Then upgraded to 0.6.6 and now 0.6.7.

Problem: cMP 5.1 does not boot into mojave without stick. System boots and shuts down a minute after chime. Due to my unflashed RX580 i do not see whats going on.

Problem occured when:
I tried to boot without stick the first time with 0.6.7. Wanted to run latest security updates for mojave without OC.
Did this then finally within OC - no problem. With OC active via stick no problems to boot and work with mojave, Big Sur or their recoveries.

Situation here:
cMP 5.1, latest Firmware, RX580 Pulse, OC 0.6.7 installed and upgraded via Martins package (a great one). Mojave install with all updates, Big Sur on a separate SSD.

Tried:
  1. Blessed again with Martins Script and rebootet.
  2. Tried to reboot in recovery and set sudo boot-args="-no_compat_check" as an idea from another forum though i know that my cMP should boot mojave native without problems. Problem here: terminal says: commands "sudo" or only "boot-args ----" are unknown.
Does anyone see what's going wrong here? Would love to know, that my native system is bootable.

thanks in advance
 
Last edited:
Me again ... sorry.
I installed OC EFI on a removable stick in case OC is failing, so i can fallback to my native mojave installation. Everything fine since my forst OC install via Martins package 0.6.4. Then upgraded to 0.6.6 and now 0.6.7.

Problem: cMP 5.1 does not boot into mojave without stick. System boots and shuts down a minute after chime. Due to my unflashed RX580 i do not see whats going on.

Problem occured when:
I tried to boot without stick the first time with 0.6.7. Wanted to run latest security updates for mojave without OC.
Did this then finally within OC - no problem. With OC active via stick no problems to boot and work with mojave, Big Sur or their recoveries.

Situation here:
cMP 5.1, latest Firmware, RX580 Pulse, OC 0.6.7 installed and upgraded via Martins package (a great one). Mojave install with all updates, Big Sur on a separate SSD.

Tried:
  1. Blessed again with Martins Script and rebootet.
  2. Tried to reboot in recovery and set sudo boot-args="-no_compat_check" as an idea from another forum though i know that my cMP should boot mojave native without problems. Problem here: terminal says: commands "sudo" or only "boot-args ----" are unknown.
Does anyone see what's going wrong here? Would love to know, that my native system is bootable.

thanks in advance
Are you sure you did not install OC on the Mojave drive? You are correct that Mojave should boot without OpenCore.
 
macOS 11.3 Beta 3 will not boot on OC 0.6.7 on the 5,1. Despite previous betas and other versions of macOS working great.
IMG_6F8D3626E29A-1.jpeg
 
  • Like
Reactions: VitaminK
Man oh man I think these open core EFI’s really ****ed my Mac pros firmware up. Big Sur was acting funny so I wanted to do a re install. But I also wanted to add a separate hard drive for a vanilla high sierra install. So I removed every drive except the new ssd and everything from the pcie slots. Put the stock 120 gpu in and rebooted to boot the HS usb.
first, it boots, flashes the white screen then goes to the black screen immediately.
rebooted and reset nvram and the smc. Now it gets a white screen like it should but if I press option to get the real boot picker it takes a really long time to show any drives.
Then, I finally boot HS usb and it says this 🤣 except there is absolutely no macOS version on the Mac Pro, only a blank new ssd and the HS boot drive. And it’s the latest version of HS you can download.

I’m thinking I should reflash the firmware and see what happens. Can I download it somewhere or just try using a Vanilla Mojave installer and see if it will ask me to upgrade the firmware and do it that way?
 

Attachments

  • 8449A85F-EBDE-4B6D-AC23-AD71AD3046B5.jpeg
    8449A85F-EBDE-4B6D-AC23-AD71AD3046B5.jpeg
    37.4 KB · Views: 83
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.