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
Plistlib Generator 1.2.0 was released with support for OC 0.7.4 (see notable changes), you will need to perform several minor changes to your current setup.py file (note the Drivers format changed again in 0.7.4), prior executing the usual upgrade process. If you have any questions, please ask them into dedicated thread. cc @cdf
I just upgraded to 0.7.4 including hybridization and using SurPlus. I used the regular system panel upgrade method with VMM off. It went without a hitch and I am now at BS 11.6 on my MP5,1.
I do think there is a mistake in the instructions on page 1 (sorry if this has already been pointed out but I have been watching the SurPlus thread and not this one but came back here for the execution). In setting up the hardware acceleration, it indicates to find
<key>Patch</key>
<array/>
but that should be
<key>Add</key>
<array/>
I do think there is a mistake in the instructions on page 1 (sorry if this has already been pointed out but I have been watching the SurPlus thread and not this one but came back here for the execution). In setting up the hardware acceleration, it indicates to find
<key>Patch</key>
<array/>
but that should be
<key>Add</key>
<array/>
Sorry for chiming in here with my question:
I'm (usually) in Mojave on a Mac Pro 4,1, patched to 5,1. I now installed Big Sur on a separate SSD using a nightly build of OCLP including Surplus. Now I don't know how to boot back into my Mojave installation. I chose the Mojave disk from the Startup Volume control panel within Big Sur. At boot it takes me to the OC boot picker showing the BigSur and Mojave installations, but when I select the latter, I only get a "forbidden" sign, and the machine shuts off.
Please tell me I haven't trashed it somehow. Should I reset NVRAM to boot without OC? But if that also fails I'm left with nothing.
Thanks in advance!
Edit: Managed to boot back into Mojave via the Apple boot menu. My understanding is that booted this way, Mojave is running without OpenCore? Shouldn't I be able to boot into Mojave from the OC BootPicker as well? Is it maybe because the machine set in SMBios (Mac Pro 7,1, I think) is incompatible with Mojave?
I'm (usually) in Mojave on a Mac Pro 4,1, patched to 5,1. I now installed Big Sur on a separate SSD using a nightly build of OCLP including Surplus. Now I don't know how to boot back into my Mojave installation. I chose the Mojave disk from the Startup Volume control panel within Big Sur. At boot it takes me to the OC boot picker showing the BigSur and Mojave installations, but when I select the latter, I only get a "forbidden" sign, and the machine shuts off.
Please tell me I haven't trashed it somehow. Should I reset NVRAM to boot without OC? But if that also fails I'm left with nothing.
Thanks in advance!
Edit: Managed to boot back into Mojave via the Apple boot menu. My understanding is that booted this way, Mojave is running without OpenCore? Shouldn't I be able to boot into Mojave from the OC BootPicker as well? Is it maybe because the machine set in SMBios (Mac Pro 7,1, I think) is incompatible with Mojave?
Last edited:
You should start your Mac in recovery mode and open the Terminal. Then type the following command.
Code:
nvram boot-args="-no_compat_check"
True but if the poster had just asked the question as a generic OpenCore question it would have been a reasonable question to ask about a situation any OpenCore user could find themselves in regardless of how they installed OpenCore and the answer given by @ZNDK, a suitable and helpful one.
Unfortunately, most just simply cannot get out of the box of the vehicle used to install OpenCore and are unable to adjust their queries to suit the place where they are asking such questions by the simple expedient of generalising such queries. If the poster had simply done this, no one would have batted an eyelid.
Having said that, I agree wholeheartedly that if you think the vehicle used to install OpenCore is important, you should be making your query in a channel relevant to that vehicle.
I have High Siera, El Capitan, Catalina, etc on the same cMP and can boot all.
As @ZNDK mentioned, you have to add
-no_compat_check to the boot-args.OCLP is OpenCore but was made to make it "simple" for folks to get unsupported Macs working with newer macOS (i.e. Big Sur onwards).
By default it does not turn ON no-compatilibity mode for older macOS's.
Here's screenshot of where to add it into the Opencore config.plist:
Yup agree.
Time for dedicate thread on this site for OCLP for MacPro's rather than GitHub ?
It does NOT operate according to the method advocated on this thread (post #1). Therefore, any and all questions pertaining to the specific OCLP implementation ought to be asked elsewhere, NOT here. Folks resorting to a purportedly "easier" method should address their questions about their chosen implementation to the advocates of said implementation, not here.
It would be nice if somebody makes one. I will keep on using @cdf ’s instructions and will therefore appreciate this thread being about that and other advanced options. Since I realize that many find the instructions too complicated, I am thankful for OCLP. It deserved its own thread.
I wholeheartedly agree. Actually, @cdf’s instructions, comprehensive and precise as they are for Mac Pro users, are a little complicated for me (not necessarily for most other users), so, from the very beginning, I implemented several shortcuts for my own use. This usually makes it easier for me to update OC when a new version is released, but I am perfectly aware that I'm on my own if I don't adhere strictly to @cdf’s method. If something goes wrong when I update, it's my fault (through sloppiness or ignorance), not @cdf’s, and it's my responsibility to clean my own mess.
The rumor that i will stop using BBEdit and terminal to edit my OC config file is greatly exaggerated. 🤣
Actually I've been waiting for this and just saw that there is a dedicated OCLP thread now, great news!
Lets be honest: over 9000 posts about.... all kinds of issues related to OC but, how many related to the approach as in this very thread?
I've installed OC as described in post #1 , and watching new posts here regularly gave me the impression that this thread has become a sort of dumping place for any issue regardless the procedure of CDF's OC , OCLP, Martin's package or whatever....
Hope this thread doesnt derail so much in the future, as it definitely deserves a place for itself.
Last edited:
I have been using PlistEdit Pro over 10 years. Fairly cheap and really easy to use. Especially for editing entries that are Numbers and Data which can be entered in Hex, Decimal or even ASCII. No more Base64 conversions, etc. Booleans are simple pull downs YES or NO and it will enter then as TRUE or FALSE.
Avoids all sorts of syntax errors because you are not editing a raw plist text file.
It's similar to Xcode's plist editor but not as heavy.
Just my opinion.
Discussing OC-related matters is perfectly fine (such as the recent discussion on volume names). The problem is when there is a complete disregard for the material maintained in the original post.
Anyone else experience issues with a black screen after the Apple menu progress bars finishes where you can’t see the user accounts, but you can still logon on either blindly or via ARD or Screens, and where you think/know SwitchResX might be the culprit? Trying to find a way to get around this and can’t remember what it is. SIP disabled, SwitchResX uninstalled, NVRAM reset 3x but problem persists.
Is this for all outputs? Depending on spoofing and video card, you may need agdpmod.
I don‘t believe my question is specific to OCLP. Had I not mentioned it, the first question would probably have been „How did you install it? Did you follow the instructions at the beginning of this thread?“
Also, I have read more than once on MacRumors things like „There‘s already a thread about XYZ, please don‘t start a new one.
However, it wasn‘t my intention to p*ss anyone off, I apologize if my question was inappropriate.
Last edited:
Thank you for,your reply!
So, when using OpenCore, I need the no-compatibility flag even when booting an OS version that‘s natively supported by my machine? Is my actual hardware irrelevant as soon as I use the SMBIOS of another machine?
Last edited: