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 have booted it many times on the MacBookPro. No problems so far. As I said if you stay away from the platform properties it should be OK.
So, that means that - taking the sample info.plist from the guide on the first page - I do absolutely nothing regarding PlatformInfo etc, i.e. leave all as it is?
Hmm in the mentioned info.plist there is <00000000000000000000008000000000> for both Cpuid1Data and Cpuid1Mask. So I leave Cpuid1Data as it is and change Cpuid1Mask to AAAAAAAAAAAAAAAAAAAAAA== ??
Sorry for the dumb questions, I basically have not too much of an idea what I am doing ...
Yes, that will work. Alternatively, since you probably will not use the VMM flag at all, you can just make the fields blank:
XML:
<key>Cpuid1Data</key>
<data></data>
<key>Cpuid1Mask</key>
<data></data>Thanks for your reply!
Unfortunately I do not have a dual-bios version of the card.
I saw the steps for installing win10 include some kext adding and modification.. Can I just pop in a SSD with Win10 on it which has been installed to from another pc and select it from startup drive from OC Catalina??
Of course. It does show the Big Sur upgrade option - with or without the flag.
Last edited:
If it is EFI I am sure would be fine. Make sure that OpenCore is booting before the attempt. Also, since this drive is coming from another machine, make sure you have the bootcamp drivers needed to adapt to the Mac.
I am starting to wonder...with the different approaches to Big Sur there may be a need to pick between different config.plist files to multi boot OSs via OpenCore. Have we reached the wall? Has anyone actually installed Catalina and Big Sur (separately) with the safe Mojave install and can boot into each without changing configs? Is there a boot argument that will work with all? Point is those that need or want all OSs are at a stalemate. A stalemate I think was put in place directly from home. Mojave was it. Catalina is a gift. Big Sur...a dream. Please don't comment with I run Big Sur. Can you run them all on the same config? I know what's broken on Big Sur for OpenCore, but to those who claim victory show me what you've done?
This project caught my attention since buying a RX580. I have a boot screen, HWA and screen glitches removed. I love my Mac. We, the people, are trying to make these Arnold Schwarzenegger machines the new terminators without the hardware. Like him, they keep fighting. That fight takes info. There is a team out there trying to make this happen and then there are others that claim victory and don't show their work. Show your work as Leonard says. I am trying to help those below my skill level while learning from those above.
This project caught my attention since buying a RX580. I have a boot screen, HWA and screen glitches removed. I love my Mac. We, the people, are trying to make these Arnold Schwarzenegger machines the new terminators without the hardware. Like him, they keep fighting. That fight takes info. There is a team out there trying to make this happen and then there are others that claim victory and don't show their work. Show your work as Leonard says. I am trying to help those below my skill level while learning from those above.
Run, yes. Run as reliably as Catalina and with all the same features, not yet. And for that reason, it's probably best to hold out for now, unless you just want to experiment. The sample config in the guide will work for Mojave and Catalina, and also Big Sur after adding an extra firmware feature bit as described in post #3,499. If doing a clean install, make sure to install to an APFS-formatted drive. No need for VMM with Big Sur.
I got that. I'm running Mojave and Catalina with no problem. None. @cdf, this is your thing and I respect it and all that has been done. I just seem to think that @dosdude1 quit at this point because there was no way to go. I'm not saying he is a genius, but at this point you would think this is where Apple finally halted our efforts. I'm thinking the code is set for current and future OSs. The nMP now rules and future code and hardware will keep that in check. I just want what will work with what we have as shown. I think Catalina is the last standard as long as the protection is there. I think the only way is to change the configuration of the installation to allow cMP. Hell of a task. We're written out at this point. If you can't boot it what is the point?
just inserted a ssd with windows 10 gpt installed on, selected it in catalina startup disk, but it just booted back to Catalina..
OC is active and working as far as I can tell.
Patched installs had a totally different public in mind. That worked "well" up to Catalina.
Don't make sense to have all the work to patch Big Sur for Macs that you can't change the GPU, that's why patches today only work well with GPUs that have METAL support.
With Mac Pros, we can change the GPUs, AirPort and BT to the Apple baseline and focus just with the CPU issues, this is an enormous advantage when comparing with other Macs of the same era.
The biggest obstacle with Big Sur and MP5,1 right now is correct/functional USB support. After that is solved, if you have a supported GPU/AirPort/BT, the changes needed to overcome CPU problems will be minimal compared to what already is needed for Catalina.
Single CPU 5,1 with Nehalem. Security Update Catalina.
Changed the VMM flag and did start the update from System Prefs >Software Update. Update went without a hitch.
Attachments
Okay, so I followed the guide (using an external SSD with Big Sur), using the sample config.plist and like cdf recommended I left the fields for
I was being able to see the OC boot menu, and Big Sur does start booting, but at one point the machine just shuts down.
I have managed to get some screenshots with verbose mode, and it looks like there is first some messages stating "sks timeout strike", also causing a delay. Then, some messages about some illegal flags and finally a KP, apparently coming from "AppleSEPManager".
I get also this log when restarting again without OC:
Cpuid1Data and Cpuid1Mask emtpy (but maybe this is the culprit?)I was being able to see the OC boot menu, and Big Sur does start booting, but at one point the machine just shuts down.
I have managed to get some screenshots with verbose mode, and it looks like there is first some messages stating "sks timeout strike", also causing a delay. Then, some messages about some illegal flags and finally a KP, apparently coming from "AppleSEPManager".
I get also this log when restarting again without OC:
Code:
panic(cpu 0 caller 0xffffff800867c920): "AppleSEPManager panic for AppleKeyStore: sks request timeout"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleSEPManager/AppleSEPManager-665.61.1/AppleSEPManagerIntel.cpp:798
Backtrace (CPU 0), Frame : Return Address
0xffffffa208a0aa60 : 0xffffff80070b9aed
0xffffffa208a0aab0 : 0xffffff80071fc6e3
0xffffffa208a0aaf0 : 0xffffff80071ecd1a
0xffffffa208a0ab40 : 0xffffff800705ea2f
0xffffffa208a0ab60 : 0xffffff80070b938d
0xffffffa208a0ac80 : 0xffffff80070b9678
0xffffffa208a0acf0 : 0xffffff80078be3ca
0xffffffa208a0ad60 : 0xffffff800867c920
0xffffffa208a0ad70 : 0xffffff80085ce42a
0xffffffa208a0ad90 : 0xffffff800856d7ca
0xffffffa208a0ae40 : 0xffffff8007818a5f
0xffffffa208a0aea0 : 0xffffff800858766b
0xffffffa208a0af90 : 0xffffff800856df4d
0xffffffa208a0b000 : 0xffffff800856dc1d
0xffffffa208a0b060 : 0xffffff800856cbbd
0xffffffa208a0b110 : 0xffffff8007818a5f
0xffffffa208a0b170 : 0xffffff800858471a
0xffffffa208a0b260 : 0xffffff80085695f2
0xffffffa208a0b2d0 : 0xffffff800a09154d
0xffffffa208a0b390 : 0xffffff800a092ced
0xffffffa208a0b450 : 0xffffff800a09284e
0xffffffa208a0b560 : 0xffffff800a09385a
0xffffffa208a0b7d0 : 0xffffff800a09c4c6
0xffffffa208a0ba40 : 0xffffff800a0a4f6b
0xffffffa208a0ba90 : 0xffffff800784569e
0xffffffa208a0bae0 : 0xffffff800a0a0138
0xffffffa208a0bb20 : 0xffffff800784f86b
0xffffffa208a0bc80 : 0xffffff80071a7d81
0xffffffa208a0bd90 : 0xffffff80070bf0e7
0xffffffa208a0be00 : 0xffffff8007095905
0xffffffa208a0be60 : 0xffffff80070ad012
0xffffffa208a0bef0 : 0xffffff80071d0ec3
0xffffffa208a0bfa0 : 0xffffff800705f216
Kernel Extensions in backtrace:
com.apple.driver.AppleSEPManager(1.0.1)[03A4380B-7F76-3511-B7B6-50918E9B4BFE]@0xffffff800867a000->0xffffff8008689fff
dependency: com.apple.driver.IOSlaveProcessor(1)[4E412D35-D853-3C0B-9F54-5909B2C49A35]@0xffffff8009b44000->0xffffff8009b45fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[D0F1BFB8-C28E-3E70-891B-73B783189394]@0xffffff8009a2c000->0xffffff8009a53fff
dependency: com.apple.kec.corecrypto(11.1)[42C8D110-EAAE-3AA5-843C-8118CA487862]@0xffffff800a211000->0xffffff800a2a0fff
com.apple.driver.AppleKeyStore(2.0)[48F091B3-7A92-360C-8B0A-3AED2D847CF9]@0xffffff800855b000->0xffffff80085dafff
dependency: com.apple.driver.AppleCredentialManager(1.0)[785332B4-9031-39F9-AF26-C0E84350D8C4]@0xffffff80083ff000->0xffffff800844efff
dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[9BA70327-883F-3E4F-960A-14203BB191FD]@0xffffff8008600000->0xffffff8008614fff
dependency: com.apple.driver.AppleSEPManager(1.0.1)[03A4380B-7F76-3511-B7B6-50918E9B4BFE]@0xffffff800867a000->0xffffff8008689fff
dependency: com.apple.driver.AppleUSBTDM(511.60.2)[55D3152A-FFD7-35B6-9261-DC3FA3723676]@0xffffff80086ee000->0xffffff80086f5fff
dependency: com.apple.driver.IOSlaveProcessor(1)[4E412D35-D853-3C0B-9F54-5909B2C49A35]@0xffffff8009b44000->0xffffff8009b45fff
dependency: com.apple.driver.KernelRelayHost(1)[EE82BFE9-D412-361C-9356-87F85A6D0DAD]@0xffffff8009fdd000->0xffffff8009febfff
dependency: com.apple.kec.corecrypto(11.1)[42C8D110-EAAE-3AA5-843C-8118CA487862]@0xffffff800a211000->0xffffff800a2a0fff
dependency: com.apple.kext.CoreTrust(1)[C90E276E-1BF9-380A-A5D0-FFF34756CB73]@0xffffff800897d000->0xffffff8008983fff
com.apple.filesystems.apfs(1677.60.23)[1313BE58-4FFF-3553-A2FD-B4CF895BFEBE]@0xffffff800a081000->0xffffff800a1e3fff
dependency: com.apple.driver.AppleEFINVRAM(2.1)[E4DF1D8B-0DA9-33A8-A7B6-17DCA1678FC0]@0xffffff8008459000->0xffffff8008462fff
dependency: com.apple.driver.AppleEffaceableStorage(1.0)[7587E81D-37C4-3BE3-9B3E-3F81D594121F]@0xffffff800846c000->0xffffff8008471fff
dependency: com.apple.iokit.CoreAnalyticsFamily(1)[203FD04E-5295-3A56-A1BC-B04D3B36ACAB]@0xffffff80088a8000->0xffffff80088aefff
dependency: com.apple.iokit.IOStorageFamily(2.1)[AA8F8B9D-BA6E-3EBB-8195-4792042ADF71]@0xffffff8009b4c000->0xffffff8009b5dfff
dependency: com.apple.kec.corecrypto(11.1)[42C8D110-EAAE-3AA5-843C-8118CA487862]@0xffffff800a211000->0xffffff800a2a0fff
dependency: com.apple.security.AppleImage4(3.0.0)[50ECF21B-A875-39D8-8898-ADAF3DE514F5]@0xffffff80084ce000->0xffffff80084ddfff
Process name corresponding to current thread: diskarbitrationd
Boot args: -no_compat_check
Mac OS version:
20C69
Kernel version:
Darwin Kernel Version 20.2.0: Wed Dec 2 20:39:59 PST 2020; root:xnu-7195.60.75~1/RELEASE_X86_64
Kernel UUID: 82E2050C-5936-3D24-AD3B-EC4EC5C09E11
KernelCache slide: 0x0000000006e00000
KernelCache base: 0xffffff8007000000
Kernel slide: 0x0000000006e10000
Kernel text base: 0xffffff8007010000
__HIB text base: 0xffffff8006f00000
System model name: MacPro7,1 (Mac-27AD2F918AE68F61)
System shutdown begun: NO
Hibernation exit count: 0
System uptime in nanoseconds: 132028067803
Last Sleep: absolute base_tsc base_nano
Uptime : 0x0000001ebd7c7c26
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x00000027b7fc5ea4 0x0000000000000000
last started kext at 5977149886: >usb.!UHostBillboardDevice 1.0 (addr 0xffffff8009e51000, size 8192)
loaded kexts:
>usb.!UHostBillboardDevice 1.0
|SCSITaskUserClient 436.40.6
@!AEthernetAquantiaAqtionFirmware 1.0.36
>BCMWLANFirmware4378.Hashstore 1
>BCMWLANFirmware4377.Hashstore 1
>BCMWLANFirmware4364.Hashstore 1
>BCMWLANFirmware4355.Hashstore 1
>!AFileSystemDriver 3.0.1
@filesystems.tmpfs 1
@filesystems.hfs.kext 556.60.1
@BootCache 40
@!AFSCompression.!AFSCompressionTypeZlib 1.0.0
@!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1
>!ABCMWLANBusInterfacePCIeMac 1
>!A!II210Ethernet 2.3.1
@filesystems.apfs 1677.60.23
>!AAHCIPort 346
@private.KextAudit 1.0
>!AACPIButtons 6.1
>!ASMBIOS 2.1
>!AACPIEC 6.1
>!AAPIC 1.7
@!ASystemPolicy 2.0.0
@nke.applicationfirewall 310
|IOKitRegistryCompatibility 1
|EndpointSecurity 1
>usb.cdc.ecm 5.0.0
>usb.!UHub 1.2
>usb.cdc.ncm 5.0.0
>!AThunderboltDPOutAdapter 8.1.4
>!AThunderboltPCIUpAdapter 4.1.1
>usb.cdc 5.0.0
>usb.networking 5.0.0
>usb.!UHostCompositeDevice 1.2
>!AHPM 3.4.4
>!A!ILpssI2C!C 3.0.60
>!A!ILpssDmac 3.0.60
>!AThunderboltDPInAdapter 8.1.4
>!AThunderboltDPAdapter!F 8.1.4
>!AThunderboltPCIDownAdapter 4.1.1
>!ABSDKextStarter 3
|IOSurface 289.3
@filesystems.hfs.encodings.kext 1
>!AEthernetAquantiaAqtion 1.0.64
>!ABCMWLANCoreMac 1.0.0
|IOSerial!F 11
|IO80211!FV2 1200.12.2b1
|IOSkywalk!F 1
>IOImageLoader 1.0.0
>corecapture 1.0.4
>!AThunderboltNHI 7.2.8
|IOThunderbolt!F 9.3.2
|IOEthernetAVB!C 1.1.0
>mDNSOffloadUserClient 1.0.1b8
|IOAHCIBlock!S 332
>!AXsanScheme 3
>usb.!UVHCIBCE 1.2
>usb.!UVHCICommonBCE 1.0
>usb.!UVHCI 1.2
>usb.!UVHCICommon 1.0
>!AEffaceableNOR 1.0
|IOBufferCopy!C 1.1.0
|IOBufferCopyEngine!F 1
|IONVMe!F 2.1.0
>!A!ILpssI2C 3.0.60
|IOAHCI!F 294
>usb.!UXHCIPCI 1.2
>usb.!UXHCI 1.2
>!A!ILpssGspi 3.0.60
>usb.!UHostPacketFilter 1.0
|IOUSB!F 900.4.2
>!AEFINVRAM 2.1
>!AEFIRuntime 2.1
>!ASMCRTC 1.0
|IOSMBus!F 1.1
|IOHID!F 2.0.0
$!AImage4 3.0.0
|IOTimeSync!F 900.11
|IONetworking!F 3.4
>DiskImages 493.0.0
|IO!B!F 8.0.2f9
|IOReport!F 47
|IO!BPacketLogger 8.0.2f9
$quarantine 4
$sandbox 300.0
@kext.!AMatch 1.0.0d1
|CoreAnalytics!F 1
>!ASSE 1.0
>!AKeyStore 2
>!UTDM 511.60.2
|IOUSBMass!SDriver 184.40.6
|IOSCSIBlockCommandsDevice 436.40.6
|IO!S!F 2.1
|IOSCSIArchitectureModel!F 436.40.6
>!AMobileFileIntegrity 1.0.5
@kext.CoreTrust 1
>!AFDEKeyStore 28.30
>!AEffaceable!S 1.0
>!ACredentialManager 1.0
>KernelRelayHost 1
|IOUSBHost!F 1.2
>!UHostMergeProperties 1.2
>usb.!UCommon 1.0
>!ABusPower!C 1.0
>!ASEPManager 1.0.1
>IOSlaveProcessor 1
>!AACPIPlatform 6.1
>!ASMC 3.1.9
|IOPCI!F 2.9
|IOACPI!F 1.4
>watchdog 1
@kec.pthread 1
@kec.corecrypto 11.1
@kec.Libm 1Attachments
Do you have Filevault enabled? Also remove the -no_compat_check boot argument.
@cdf, @tsialex. You guys are great at what you do and have done for the cMP. I appreciate the responses and I'll continue with questions as they arise. I think the monkey wrench has been tossed, though. Has anyone looked at the patchers out there that are available? Can they be streamlined into the OpenCore process? The good about Mojave is it boots on its own. Catalina can with @dosdude1 install, but it is so limited. Applying OpenCore to that is just a waste since they don't vibe well (updates). Now we have the newbie on the block and want to make it work. I don't think it will be stable for all. The cMP is being forced out at this point and Apple is doing that to support the nMP sales.
Just above my statements sits @startergo saying to remove no_compat_check. I think that multiple OSs aren't available to us since BS. It's stick to this or that. Make a choice is basically the given. I love Catalina with OpenCore. It works and is functional. I have to admit I waited until the finalized version to use it because of the work being done here. You all did an outstanding job. My suggestion is to take post #1 and simplify it for all. The simple package in post #1314 on setting up HWA actually is a better way for the neophytes out there. You get a lot of questions from them and I never see anyone direct them to the easy way. Read post #1 is what I see. If they have a 3.1 no-one sends them to @Dayo posts. It's a learning curve even for you big brains out there. I've worked IT for years and can't stress more the simpler the explanation, the less questions asked.
This is not a rant. Just a statement. Do you really need BS (BS. That's funny.) just to prove it will run? I'll wait until this one is finalized and try from there. Let's not blow up our precious cMPs just yet. All I use this box for is a media center and menial communications. I'll buy a M1 or M2 soon to deal with the Apple future. Until this thing kicks it I will love it as always. Thanks for all your support and keep up the good work.
Just above my statements sits @startergo saying to remove no_compat_check. I think that multiple OSs aren't available to us since BS. It's stick to this or that. Make a choice is basically the given. I love Catalina with OpenCore. It works and is functional. I have to admit I waited until the finalized version to use it because of the work being done here. You all did an outstanding job. My suggestion is to take post #1 and simplify it for all. The simple package in post #1314 on setting up HWA actually is a better way for the neophytes out there. You get a lot of questions from them and I never see anyone direct them to the easy way. Read post #1 is what I see. If they have a 3.1 no-one sends them to @Dayo posts. It's a learning curve even for you big brains out there. I've worked IT for years and can't stress more the simpler the explanation, the less questions asked.
This is not a rant. Just a statement. Do you really need BS (BS. That's funny.) just to prove it will run? I'll wait until this one is finalized and try from there. Let's not blow up our precious cMPs just yet. All I use this box for is a media center and menial communications. I'll buy a M1 or M2 soon to deal with the Apple future. Until this thing kicks it I will love it as always. Thanks for all your support and keep up the good work.
Filevault is not enabled. Also removed that boot arg, but unfortunately, still restarts when booting macOS.
The KP log seemingly points to a problem with the Secure Enclave / the T2 chip (AppleSEPManager) but of course I have switched off T2 security, or OC wouldn't be able to start up anyways.
Any ideas? I mean when people can run this on a T2 MPB, it also should work on the MP 7,1 right?
Try this config with a debug build.
The specific files that need to be swapped:
- EFI/BOOT/
- BOOTx64.efi
- EFI/OC/Bootstrap/
- Bootstrap.efi
- EFI/OC/Drivers/
- OpenRuntime.efi
- OpenCanopy.efi(if you're using it)
- EFI/OC/
- OpenCore.efi
That statement was not addressed to you, only to the specific person and there is a reason for that. He is using a SUPPORTED Mac so he does not need that.