Figured that out about 2 hours ago. Now I’m up and running with Monterey! Thanks for responding. Should you set it back to the original state after install?
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
Yes, that's the usual procedure. Leaving the VMM flag can lead to performance loss and potential power management issues. Monterey is still a moving target, but it looks like the VMM flag won't be necessary for installations after all:
SurPlus - The Big Sur/Monterey fix you've been waiting for.
I can confirm that Monterey beta 9 (21A5543b) is installable and bootable without the VMM flag. The installation merely requires adding a FirmwareFeatures bit to the corresponding PlatformNVRAM variables. Sure. If the VMM flag ends up being required for OTA updates (as is the case in Catalina...
forums.macrumors.com
I wonder if Windows 11 will still suffer from the occasional hang at the Windows loading screen... If you could keep us posted, that would be great.
Not until now, everything runs smoothly. After the Windows installation, i downloaded the Boot Camp ESD for the `iMac18,1` model with `brigadier -m iMac18,1` and only installed the missing drivers for Bluetooth and Wifi manually and don't used the Bootcamp installer, because only the missing drivers should be installed. After Wifi was working, Windows downloaded updates for drivers and in general. I installed additionally the drives for the RX 580 from AMD for Windows 11. Now everything is working and the Device Manager shows no unknown devices. Thanks again for the great appendix in post #1.
Edit: I think a better way to install the missing drivers is to use: https://www.driverscape.com/manufacturers/apple/laptops-desktops/macpro5,1/703
Last edited:
The issue is: the config.plist spoofs the Mac Pro (4/5,1) to be an iMac Pro, while it should be spoofing to a MacPro7,1 in order to drive a multimonitor setup.
The next iteration of the guide here will focus on the latest version of macOS and will therefore use the MacPro7,1 board ID. This spoofing is fine for the latest version of macOS but requires extra settings to boot Mojave and earlier...
I needed to swap out my Windows drive so decided to give this a whirl. It has worked just fine! Being a dirty BIOS booter for the longest time my only slip-up was putting the Microsoft EFI directory in the wrong place initially; I read the instruction...
...as a command, whereas it really means "create an EFI directory on the EFI volume and put the Microsoft directory into it".
The install went just as the instructions dictate though the initial setup experience is long-winded and slow, as Windows clearly hadn't finished installing the graphics drivers and nothing was accelerated. I also entirely destroyed my first attempt by installing the Titan Ridge Thunderbolt drivers while having Thunderbolt devices attached. As soon as the driver came to life it froze the whole machine, requiring a full NVRAM and SMC reset before even OpenCore's boot menu would be displayed again. The install was borked and just sat there showing the Windows logo on boot with no spinner.
All the remains is to find that Bluetooth driver from the iMac18,1. I just haven't had time after reinstall. All of my operating systems are now booting reliably from NVME drives, with the bays being used for the emergency Mojave install and "bulk storage".
Note that if your Titan Ridge card has been flashed, you should use the Apple version of the driver.
How about in Big Sur and Monterey?
Yes, with "-no_compat_check" and SecureBootModel set to Disabled. See post #9,120.
I also applied the 0.7.4 package to my MacBook Pro Retina from 2012 to see if I could extend it's lifespan to yet another OS generation. It previously ran Big Sur no problem using the standard 0.7.4 and previous OC packages. It's a bit sluggish with Monterey though. Still runs but won't sleep, hangs a couple of seconds on window close etc.., Any thoughts on any tweaks to the OC package to get it to run smoother? Also it notes the screen as a 48" screen which it isn't (15.2" Retina) making the resolution of the standard MacOS windows small, still useable but small. Any insight would be appreciated.
The issue is mainly to do with Apple Apps like FCP and Compressor. With Big Sur on FCP 10.5.4, only HEVC Decode and no Encode. 1:26:00 minute Swordsmith clip took 25 minutes to render (4K UHD 10-bit HDR to 4K UHD 8-bit) with most of the Xeon Cores on ~40% loading while RX580 is idle most of the time (except when FCP is decoding).
FCP does use the AMD dGPU for H.264 Encode & Decode and took 2 minutes to render out.
On the other, VideoProc App uses VideoToolBox API and has no problems transcoding HEVC to H.264 in realtime (took less than 2 minutes (~ 32 fps vs 3 fps with FCP).
Not experimented with Monterey yet.
UPDATE:
Issue persists with iMacPro1,1 spoofed board-ID with FCP 10.5.4 too. I believe version 10.4.6 did work well under iMacPro1,1. I'll downgrade mine and test with both spoofed ID's.
Last edited:
FCP / Compressor is very picky on using HEVC hardware encoding.
Please follow the exact settings as per this video (e.g. disable "Allow Frame Reordering")
Thanks. Yes I completely forgot about that "Allow Frame Reordering" checkbox needed to be off.
So I ran 12 tests : 3 OS's (Mojave, Catalina & Big Sur) for each of OpenCore spoofed Board ID's (iMacPro1,1 & MacPro7,1) and H.264 & HEVC Encode & Decode via Apple Apps & 3rd Party Apps.
Conclusion: Mojave is the only problem child with MacPro7,1 spoofed board ID. It can neither decode or encode H.264 nor HEVC. With iMacPro1,1 board-ID it had no problem whatsoever.
With the Catalina & Big Sur both spoofed board ID's enabled H/W encode and decode.
So, if anyone needs to run Mojave (for whatever reasons) with AMD GPU & OpenCore for video application, iMacPro1,1 board-ID is better.
Also, with iMacPro1,1 board-ID, I had no problems attaching 3 screens on the RX580.
Probably more or less gotten to a point where OC configs have to target "Legacy" (Catalina and Earlier) or Current Mac OS.
MyBootMgr already has one OC instance just targeting BigSur/Monterey updates but think I will add a new instance (fourth) for this reason as will like to provide the option to install/run/update whatever a user happens to want to use.
Might become a challenge down the line though
MyBootMgr already has one OC instance just targeting BigSur/Monterey updates but think I will add a new instance (fourth) for this reason as will like to provide the option to install/run/update whatever a user happens to want to use.
Might become a challenge down the line though
I followed the instructions on page 1 and was able to run Big Sur 11.2.3 on my Mac Pro5.1 since several months. Now with OC 0.7.4 and the integration of SurPlus I wanted to update to 11.6, but Software-Update doesn't show the update, it says "you are using the latest version 11.2.3. I have gone through my config file several times but can't find what's wrong. Would be great, if a more clever person could help me out... and yes, the VMM flag is turned ON.
The update should show up if you use hybridization spoofing (in which case, you won't need the VMM flag).