I'm going to upgrade BS with Monterey on a cloned SSD just to be safe. Worst case scenario, I pull the drive and reinsert my current Big Sur volume. Figured that's the safest way to proceed for the time being.Sound like safe assumptions
Sounds like a solid plan.
You are quite welcome! Keep us posted, but I assume all will go smoothly. Thanks for the chat!
Yeah I do plan to get a new SSD and back up my Mojave which is on my original 512Gb apple drive and it is getting old now anyway. Yeah my Firmware is BOOT rom version 144.0.0.0.0
It sounds amazing that it can work like that with a USB, OpenCore doesn't change the boot Rom does it?
Cubase 12 only supports now officially Big Sur and Monterey I think Monterey seems like the best move for what I been told. Only thing is that my legacy WiFi might not work in Monterey but they have a patch that might fix that. As I am not sure I want to start messing around with the WiFi card that is already installed.
Thanks for all help flaubertHow to download and install macOS - Apple Support
Download and install current or previous versions of the Mac operating system on compatible Mac computers.support.apple.com
You can convert it to UEFI with the command: mbr2gpt /convert /allowfullOS
You need to make sure you have "_no_compat_check" in your boot arguments. My guess is your config.plist is spoofing a MacPro7,1 which cannot run Mojave.
Here is the relevant part from the first post - you need to put these lines back into your config.plist in the NVRAM key -
| ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ |
|---|
| <key>NVRAM</key> <dict> <key>Add</key> <dict> <key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key> <dict> <key>boot-args</key> <string>-no_compat_check</string> </dict> ⋮ </dict> <key>Delete</key> <dict> <key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key> <array> <string>boot-args</string> </array> </dict> |
Personally, I just followed the OCLP guide, as I wasn't aware of this thread's existence when I installed Big Sur.
Is always a good idea to understand what you are doing with OC and learn from the first post guide. I don't understand why people are posting OCLP related stuff in this thread.
Because it uses OpenCore and is also mentioned in the first post? I've read the first post guide, but as I said earlier, I wasn't aware of this thread when I used OCLP, so that was my first experience with OpenCore. For somebody just looking to install Big Sur or Monterey, the OCLP route is by far the easiest that I've seen. Sure, take the time to read-up on what's under the hood, but there's nothing wrong with somebody going that route.
Do you have the factory bluetooth/wireless card? I have the factory Broadcom BCM43xx. Easiest way to get support is just running the patcher portion of the OCLP patcher, if you'd like to go the more hands-on route, the dortania guide has a Bluetooth section:
I edited my post, see update. Things changed with Monterey, it's covered in the link I provided.
In your instructions, you mention to remove this code, if I run Catalina or later:
<key>NVRAM</key>
<dict>
<key>Add</key>
<dict>
<key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
<dict>
<key>boot-args</key>
<string>-no_compat_check</string>
</dict>
</dict>
<key>Delete</key>
<dict>
<key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
<array>
<string>boot-args</string>
</array>
</dict>I only see the first post say "If you're using OpenCore to boot only Catalina and later, then you can clean up the NVRAM". You need to keep these lines if you are spoofing the MacPro7,1.
Actually, you don’t need to remove the no_compat_check boot arg to enable hardware acceleration. You only need this boot arg if you want to boot Mojave (or earlier) when using the (recommended) MacPro7,1 board ID. If you want hardware acceleration in Mojave, then take a look at the spoiler at the end of the section Complete you setup.