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
I'm referring to Night Shift and DRM. When we do minimal spoofing, these do not work without userspace patching. On the other hand, they should work with full spoofing.
In theory, the firmware features are only for installing Big Sur; I haven't confirmed hardware acceleration yet.
Since Hackintosh guys can do that (with Xeon + Vega, no iGPU), they can even do Sidecar. Therefore, there should be a way for 5,1 to activate that via complete SMBIOS spoofing.
However, since this is not the preferred way to run a 5,1. Therefore, we haven't dig deep in this direction so far.
Of course, they have newer motherboard etc. That may make the difference. But the chance to make a 5,1 "fully functional" still exist.
Sidecar is handled by the T2 chip in iMacPro1,1 so there is no way to enable it when SMBIOS is spoofed to the iMacPro1,1 on a non-T2 machine.
@pastrychef Can you please confirm if you have the DRM working on Big Sur on your hack?
New DRM enabling method for systems with AMD GPU
DRM works if you use iMacPro1,1 system definition even if you don't have WhateverGreen installed. It always has.
www.tonymacx86.com
Last edited:
I have a fully working installation of Catalina on my cMP 5,1 (flashed from 4,1) using OpenCore 0.62 with no changes other than those specified in post #1 and would like to install the Big Sur beta 11.0.1. Are these the only changes needed to the config.plist to enable installation of Big Sur from the Catalina desktop? If so, once installed do I need to undo these changes? Is it necessary to sign in and out of iCloud before installing Big Sur? Finally, is the code above added to the config.plist or do I find these keys and change what I have to these values?
Thanks!
Assuming that you've completed Part II of the guide: simply replace
XML:
<dict>
<key>BoardProduct</key>
<string>Mac-7BA5B2D9E42DDD94</string>
</dict>
XML:
<dict>
<key>BoardProduct</key>
<string>Mac-7BA5B2D9E42DDD94</string>
<key>FirmwareFeatures</key>
<data>A1QM4A==</data>
<key>FirmwareFeaturesMask</key>
<data>P/8f/w==</data>
</dict>In my preliminary testing, this was the only change necessary to install Big Sur 11.0.1 with the full installer in Catalina 10.15.7. The change is still considered experimental. But in theory, it should be safe: you shouldn't need to sign in and out of Apple services; you can also keep the change afterwards.
So far, that's just a guess, can't see any prove yet.Sidecar is handled by the T2 chip in iMacPro1,1 so there is no way to enable it when SMBIOS is spoofed to the iMacPro1,1 on a non-T2 machine.
@pastrychef Can you please confirm if you have the DRM working on Big Sur on your hack?
This video claims DRM works with simple device injection (maybe he has iMacPro1,1 smbios, which he did not specify)New DRM enabling method for systems with AMD GPU
DRM works if you use iMacPro1,1 system definition even if you don't have WhateverGreen installed. It always has.
But this post makes me believe there is still a chance.
Activate AMD hardware acceleration
It can't be T2 or QuickSync requirements as my hack is using RX-580 with a Xeon CPU E5-1650 v3 @ 3.50GHz and it can AirPlay natively just fine to AppleTV (note that its also not a WiFi or BT requirement as there is no WiFi or BT in this machine). It must be some other check that is preventing...
forums.macrumors.com
I know I shouldn't be surprised, given the genius of people on this forum, but your instructions worked flawlessly; I am now running Big Sur on my cMP!
One very minor question: I renamed my drives in finder, but when booting using the graphical boot screen, the drives still have the old names. Any way to fix this?
May I suggest that you edit your first post with an addendum that tells people the secret to getting Big Sur to install over Catalina using OpenCore? I'm afraid others may not find post 4,410 that solves the problem...
Thanks again.
Hi there,So far, that's just a guess, can't see any prove yet.
But this post makes me believe there is still a chance.
Activate AMD hardware acceleration
It can't be T2 or QuickSync requirements as my hack is using RX-580 with a Xeon CPU E5-1650 v3 @ 3.50GHz and it can AirPlay natively just fine to AppleTV (note that its also not a WiFi or BT requirement as there is no WiFi or BT in this machine). It must be some other check that is preventing...
Regarding a vanilla Open core installation, - the description states to use two regular SATA drives, because there might be some problems when NVME drives are in use. If I comply with that and put both installations on STAT drives, - can I put those installs back on faster NVME drives later on? Or does this mean NVME boot drive option is gone with open core? Once everything is properly installed like the wiki description in this post describes can copy clone it back to my I/O Crest NVME card to have faster speeds again?
You can try, it should work actually. We don't suggest install OpenCore onto NVMe because users' report show that some users can't boot OpenCore from NVMe (the reason / exact condition still unknown at this moment). And there is practically no performance difference.
First question. Can a 1 Tb Samsung EVO 860 be used for the "A" drive where the EFI and OpenCore files get located? I got the drive formatted in GUID APFS. I did diskutil list, found and mounted the EFI partition for the Samsung drive. There was no EFI folder on the EFI partition when I first mounted and opened it. So I copied the entire OpenCore-0.6.2-release onto the EFI partition. I then opened the folder, found the folder labeled OC and copied the config.plist into that folder. I did the recovery reboot, found the correct EFI partition, ran the mount command and ran the bless command. Then I rebooted. No boot picker. I checked the nvram, and that returned an error. I checked the the VMM flag for the CPU and it was not listed. I have also tried just putting the EFI folder from the downloaded and unzipped OpenCore 0.6.2 release and the config.plist into the OC folder in that. That gave slightly better results, but it failed too. I'm certain I'm not understanding something. What am I doing wrong? Thanks for any help. cMP 4,1 upgraded to 5,1, running Mojave. The original 2 Tb HDD is in slot 1 and the SSD is in slot 2.
Consider splitting your post into two or three paragraphs so that readers can read and understand what you are writing.
Makes a big difference in getting responses.
Hey Alex,
While I have deep regards for all posts from h9826790, I have the same bifurcation as you with two 970s (one EVO, 1 EVO+) with Mojave on one and Catalina on the other. While I had difficulties installing OC to the blades during the summer, I finally got them working well. That's on my 12-core, but I also used a 960 for Mojave and an eSATA3 SSD as the Catalina drive on my 6-core. That's fine too. Also, you can clone the Mojave volume with SuperDuper or CCC, but with CCC, you can also clone the the Catalina volume AND add the EFI data at the end with EFICloner. But, as someone informed me on this thread, you can just do the normal clone and then copy the EFI folder manually for the cloned Catalina volume. Good luck.
See post #3,324.
Because Big Sur is still in beta, the procedure might change. But once Big Sur is released, I'll make sure to update the wiki.
To avoid issues, OpenCore should be installed on a SATA disk and so should your fall-back Mojave installation. Your other macOS installations can be anywhere, really. I will clarify this in the wiki when I get the chance.
You should have dragged the contents of the X64 folder into the EFI volume. Make sure that you end up with a structure like this:
EFI volume/EFI folder/OC and BOOT folders
They include documentation and utilities. You don't need them for the installation.
The config.plist file should go in the OC folder.
I did the bless --mount /Volumes/EFI --setBoot
hit return and everything seems to have gone OK.
what do the "--" do?
hit return and everything seems to have gone OK.
what do the "--" do?
I shut down. When I rebooted I got an Open Core screen and the number 1 beside my HDD that has Mojave, since Catalina has not yet been installed on the SSD. It appears that I may have OpenCore installed.
The first screen was there for just about four or five seconds and then the regular screen for Mojave displayed.
The first screen was there for just about four or five seconds and then the regular screen for Mojave displayed.
OpenCore is now installed. The Parallels shortcut icon on the desktop does not like the change and has turned generic.
-- is just part of the parameter that is passed to the command (in this case, the command is bless and the parameters are --mount /Volumes/EFI and --setBoot).
-- is usually for parameters that are longer than a single character.
- is usually for parameters that are just a single character.
Type
man bless (or just type bless and right click on the bless word and select "Open man Page") to see all the parameters used by the bless command. Notice that none of them are single letter parameters.Type
man diff for an example of a command that has single letter parameters and alternative whole word parameters for most of them.With single letter parameters, you can string multiple parameters together. For example,
ioreg -f -i -l -w0 can be written as ioreg -filw0.
The short answer is no. The longer one: Do you see that Windows in the OC boot picker? If you don't, there is no way you can boot it.