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, OpenCore can boot Snow Leopard and High Sierra.
Well, we have it on good authority (@vit9696) that full spoofing with properly generated identifiers is actually the best approach. All the features you mention should just work without any problems. The identifiers (including the serial number) should be those appropriate for the model you choose (iMac Pro).
When we developed the VMM-flag and hybridization strategy, the idea was to preserve as much as possible the original machine's identity. This seemed like a good idea, and because the strategy has proven safe and effective, we have just stuck with it, but with Big Sur, things are different (VMM is ineffective), and we may very well opt for full spoofing...
Look, fully SMBIOS spoofing another Mac has several other implications, like sleep not working correctly and other problems. No solution is really perfect, the best compromise is to use it without SMBIOS enabling VMM when updates are released - unless you use AMD hardware acceleration.
If you need AMD hardware acceleration you then go for the hybrid mode.
[automerge]1595260239[/automerge]
Sure, Big Sur changed things, but for now VMM spoofing and hybrid mode for people that need AMD hardware acceleration is the best solution for Catalina. Too soon to know implications of changes needed for Big Sur.
DRM video playback with Safari will work for Netflix/Prime when you enable AMD hardware acceleration, but it's a much more complex topic than video playback.
It's better that you read the FAQ here:
Activate AMD hardware acceleration
[For existing OpenCore users, you can always download my latest OpenCore package at post #1314 for update] Full HWAccel achieved now! Everything is covered in the OpenCore thread. The step by step tutorial to enable AMD hardware acceleration is now at here, but I strongly recommend you go...
forums.macrumors.com
Has anyone used OpenCore Configurator? The changes to config.plist seem pretty innocuous except for the SMBIOS section where it inserts a lot of blank fields in. It doesn't alter the actual BoardProduct, just the other fields around it to blanks. It's also seemingly easier to just modify the VMM value therein via 00000000 00000000 00000000 00000000 for AAAAAAAAAAAAAAAAAAAAAA in Cpuid1Mask. Of course VMM enabled is 00000000 00000000 00000080 00000000 (AAAAAAAAAAAAAACAAAAAAA).
Hi, I am using h9826790 package from Active AMD Hardware acceleration thread on Mojave since March mainly for HW acceleration but I also welcome other things like boot picker. Everything worked fine and I don't have any reason upgrade from Open Core 0.5.6 to newer.
But something happened two weeks ago because Mac Pro right now won't go sleep (I didn't change any in setup, everything same). However is not sleep issue I know from past like on High Sierra with RX 560/70/80 where Mac Pro stuck somewhere with spinning fans. It just won't go sleep. When I hit mouse or keyboard monitors wakes up and I can use Mac Pro like nothing happened.
So firstly I install latest security update and reinstall Mojave. Still won't go sleep. After that I check Sharing in System preferences - everything is turned off.
I update Open Core to 0.5.9 and I decided update to Catalina because I wanted do it anyway but didn't have time. Everything is working with Catalina perfectly (Strangely. I have feeling that is actually better than Mojave) but it still won't go Sleep. AppleMCEReporterDisabler kext is in Open Core.
I decided boot from drive where I don't have Open Core with some older version of Mojave and try sleeping. And it works. But drive with Open Core remain in Mac Pro.
Right now I am thinking about NVRAM reset. I didn't try it because I am not sure how to reactive Open Core after that (just bless it?). But I dit SMC reset.
I also discover that new recommendation not use Open Core on NVME SSD - I have Open Core on NVME drive... Maybe there might be problem?
My setup:
Mac Pro mid 2010
CPU: 2 x X5670
GPU: Sapphire Radeon RX Vega 64 8 GB
RAM: 32 GB
OS: Catalina 15.6 (latest)
Startup disk: WD NVMe SSD Black 1 TB.
Thanks all of you for amazing work you done here and for any advice what I should do next.
But something happened two weeks ago because Mac Pro right now won't go sleep (I didn't change any in setup, everything same). However is not sleep issue I know from past like on High Sierra with RX 560/70/80 where Mac Pro stuck somewhere with spinning fans. It just won't go sleep. When I hit mouse or keyboard monitors wakes up and I can use Mac Pro like nothing happened.
So firstly I install latest security update and reinstall Mojave. Still won't go sleep. After that I check Sharing in System preferences - everything is turned off.
I update Open Core to 0.5.9 and I decided update to Catalina because I wanted do it anyway but didn't have time. Everything is working with Catalina perfectly (Strangely. I have feeling that is actually better than Mojave) but it still won't go Sleep. AppleMCEReporterDisabler kext is in Open Core.
I decided boot from drive where I don't have Open Core with some older version of Mojave and try sleeping. And it works. But drive with Open Core remain in Mac Pro.
Right now I am thinking about NVRAM reset. I didn't try it because I am not sure how to reactive Open Core after that (just bless it?). But I dit SMC reset.
I also discover that new recommendation not use Open Core on NVME SSD - I have Open Core on NVME drive... Maybe there might be problem?
My setup:
Mac Pro mid 2010
CPU: 2 x X5670
GPU: Sapphire Radeon RX Vega 64 8 GB
RAM: 32 GB
OS: Catalina 15.6 (latest)
Startup disk: WD NVMe SSD Black 1 TB.
Thanks all of you for amazing work you done here and for any advice what I should do next.
Please, excuse my ignorance. Up to now, I've assumed I only need to modify the EFI volume of my Catalina and my Windows (Boot Camp) internal disks. However, do I also need to modify the EFI volume of my Snow Leopard disk (High Sierra is also on the same disk as Snow Leopard)?
You only need to install OpenCore once, on ANY EFI partition. You don't need to modify the macOS EFI volume, or Windows EFI volume. You can install that even on a USB thumb drive EFI volume which is completely empty.
OpenCore is a boot loader. It's NOT an additional software that must attach to the OS drive.
Once you installed a copy of OpenCore, boot via it, you can use it to boot to any other supported OS drive.
Last edited:
Hello,
first of all: Thank you for all your work. Great wiki (first post) that helped me to build my own config file (attached)
Everything works great - OC 0.5.9 (my version) and the HW Acc (Lilu 1.4.5 / WhateverGreen 1.4.0) and the OpenCanopy Boot Picker. Today I try to make a test install of macos 10.15 with the original installer from Apple. I prepare the config file (attached) with the Cpuid1Mask value to get the VMM status and also I proof the config file before (see picture VMM-Valid-Config). I reboot and test the VMM status (it's there) but then I get a big surprise: The macos 10.15 installer shows me up all APFS drives greyed out and only a HFS+ drive for valid install - I don't try to install there because of importand data. If I click the drive where I want to install 10.15 a small baloon help shows me the hint that I need a firmware update before. I can press the drive icon but there is NO install button that I can click.
The config file is build by myself... I double check my entrys but I am not be able to find my mistake. I am looking for help / a hint...
Thank's for reading.
first of all: Thank you for all your work. Great wiki (first post) that helped me to build my own config file (attached)
Everything works great - OC 0.5.9 (my version) and the HW Acc (Lilu 1.4.5 / WhateverGreen 1.4.0) and the OpenCanopy Boot Picker. Today I try to make a test install of macos 10.15 with the original installer from Apple. I prepare the config file (attached) with the Cpuid1Mask value to get the VMM status and also I proof the config file before (see picture VMM-Valid-Config). I reboot and test the VMM status (it's there) but then I get a big surprise: The macos 10.15 installer shows me up all APFS drives greyed out and only a HFS+ drive for valid install - I don't try to install there because of importand data. If I click the drive where I want to install 10.15 a small baloon help shows me the hint that I need a firmware update before. I can press the drive icon but there is NO install button that I can click.
The config file is build by myself... I double check my entrys but I am not be able to find my mistake. I am looking for help / a hint...
Thank's for reading.
Attachments
Disable SMBIOS spoofing for Catalina installation / update.
I actually think this is important to note at the initial instructional level. I've noticed that some folks have said things like look for the "APPLE" folder in the EFI folder and this has been misleading. Somehow this needs to be made clear everywhere.
Awesome...🖖 thank you very much. That hit the nail. Sometimes I don't see the wood because of the trees 🤪
It has installed, updates with the combo update 10.15.6 and I copy the WiFi Kexts and fix the permissions because I use the old AirPort Extreme (0x14E4, 0x8E) card. Now I can do a data migration and further tests but before I need to do a bootable backup... I need more infos about this to go on. But for now I am very happy that all is working fine.
Follow up to post #2870
I continued to have problems where each restart or shutdown I had to reset the NVRAM or it would never reach a boot loader. I tried many solutions including the ones suggested (thanks) but without success. I finally moved OC to another EFI on a SATA data drive (not the original Mojave disk). I then booted into recovery and blessed that new EFI. Now it boots to the OC bootpicker without resetting the NVRAM. As a test before doing this I moved it to a USB and that worked too. Decided in the end to internalize it and not tie up a USB port.
Last edited:
Well what I have done is use a USB stick to boot opencore with the VMM flag to enable updates but use the no compatibility boot argument to boot "normally" for day to day operations - take the USB out. When OC settles down and Big Sur is released perhaps I'll make the jump to OC full time but in the mean time I don't have to redo my legacy WIN10 install for UEFI....
I put OC on an otherwise blank USB thumb drive (per post #1 instructions) but it only boots to OC when I do a Restart (just using Mojave right now). If I boot from a complete shutdown it always boots directly into Mojave without OC. Is there something else I need to configure?
Hm, after updating to Catalina 10.15.6 I am experiencing issues related to the Hardware Acceleration, at rare or pretty specific times one of my screens start to turn on and off, the entire system freezes except the cursor, and just once happened that a bunch of saturated colors appeared on my secondary display.
Has this happened to anyone? I enabled acceleration on my RX480, it was working fine on 10.15.5
Has this happened to anyone? I enabled acceleration on my RX480, it was working fine on 10.15.5
Check console, if there is a GPURestart crash report (when freeze happened), then most likely it's macOS issue.
@h9826790 do you tried to upgrade BigSur through opencore spoofing using the new method that apple labels "Incremental update image"
I made an attempt here (my customized opencore setup is based on 0.5.9): https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28699756
but after the "BigSur OTA update" starts to download then fails some checks, maybe the sealed snapshot volume is the issue.
I made an attempt here (my customized opencore setup is based on 0.5.9): https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28699756
but after the "BigSur OTA update" starts to download then fails some checks, maybe the sealed snapshot volume is the issue.
Yes, that works.
Once click the "More info..." it will download the 4.96GB incremental update image, but not the full 12.88GB full update image.
And it seems this more like the iOS OTA update. It has pretty long preparation time.
Last edited:
I proceeded too (MacBook Penryn core2duo), and after the stage2 installer 29 minutes remaining I encountered the big apple logo with big loading bar (that is typically the EFI SMC firmware update), so I was undecided if force power-off or waiting for it, then I took the risk to wait (I have no skills to desolder and flash an EFI EEPROM), and the big loading bar completed in about 3 minutes, after reboot I quickly booted a Mojave volume and checked that firmware was still machine stock, so reboot again with alt-option to OpenCore and continuing the "macOS Installer" stage2 or stage3 , but I guess it worked.
yes, the small updater works
but allways: no H264 HWacc, PCIe drives are external
and kernel panics with dual CPU
:- (
but allways: no H264 HWacc, PCIe drives are external
and kernel panics with dual CPU
:- (
use the same EFI folder from martin on all of my cMPs
in mojave and catalina it all works
on bigsur the H265 HWacc works but all other i wrote has problems,
and start only on a single CPU
what i missed?
This is the error I get when I try to do the incremental update.
I am using smbios 'hybridization' so I have modified my Board ID, but everything else is still the same. I will try enabling the VMM flag and see I get different behavior, but perhaps I need to spoof a iMacPro to download the incremental update.
Update: I have to have the VMM flag enabled to do the incremental update.
I am using smbios 'hybridization' so I have modified my Board ID, but everything else is still the same. I will try enabling the VMM flag and see I get different behavior, but perhaps I need to spoof a iMacPro to download the incremental update.
Update: I have to have the VMM flag enabled to do the incremental update.
Last edited: