Sidebar Sidebar
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

Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
here is a diff between the current 0.6.5 config.plist from CDF (before applying additional changes like GPU acceleration, etc), compared to what I am using with OC 0.6.3. Unless there is something special added to OC 0.6.5 to support this security update...then I'm not seeing a problem that would be solved by updating OC.

Code: 
31,32d30
<         <key>Patch</key>
<         <array/>
35,36d32
<             <key>AllowRelocationBlock</key>
<             <false/>
76c72,88
<         <dict/>
---
>         <dict>
>             <key>PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)</key>
>             <dict>
>                 <key>agdpmod</key>
>                 <data>
>                 cGlrZXJhAA==
>                 </data>
>                 <key>rebuild-device-tree</key>
>                 <data>
>                 AA==
>                 </data>
>                 <key>shikigva</key>
>                 <data>
>                 UA==
>                 </data>
>             </dict>
>         </dict>
83c95,168
<         <array/>
---
>         <array>
>             <dict>
>                 <key>Arch</key>
>                 <string>x86_64</string>
>                 <key>BundlePath</key>
>                 <string>Lilu.kext</string>
>                 <key>Comment</key>
>                 <string>Patch engine</string>
>                 <key>Enabled</key>
>                 <true/>
>                 <key>ExecutablePath</key>
>                 <string>Contents/MacOS/Lilu</string>
>                 <key>MaxKernel</key>
>                 <string></string>
>                 <key>MinKernel</key>
>                 <string></string>
>                 <key>PlistPath</key>
>                 <string>Contents/Info.plist</string>
>             </dict>
>             <dict>
>                 <key>Arch</key>
>                 <string>x86_64</string>
>                 <key>BundlePath</key>
>                 <string>WhateverGreen.kext</string>
>                 <key>Comment</key>
>                 <string>Video patches</string>
>                 <key>Enabled</key>
>                 <true/>
>                 <key>ExecutablePath</key>
>                 <string>Contents/MacOS/WhateverGreen</string>
>                 <key>MaxKernel</key>
>                 <string></string>
>                 <key>MinKernel</key>
>                 <string></string>
>                 <key>PlistPath</key>
>                 <string>Contents/Info.plist</string>
>             </dict>
>             <dict>
>                 <key>Arch</key>
>                 <string>x86_64</string>
>                 <key>BundlePath</key>
>                 <string>AppleMCEReporterDisabler.kext</string>
>                 <key>Comment</key>
>                 <string>Disable AppleMCEReporter</string>
>                 <key>Enabled</key>
>                 <true/>
>                 <key>ExecutablePath</key>
>                 <string></string>
>                 <key>MaxKernel</key>
>                 <string></string>
>                 <key>MinKernel</key>
>                 <string>19.0.0</string>
>                 <key>PlistPath</key>
>                 <string>Contents/Info.plist</string>
>             </dict>
>             <dict>
>                 <key>Arch</key>
>                 <string>x86_64</string>
>                 <key>BundlePath</key>
>                 <string>NightShiftEnabler.kext</string>
>                 <key>Comment</key>
>                 <string>Enable Night Shift</string>
>                 <key>Enabled</key>
>                 <true/>
>                 <key>ExecutablePath</key>
>                 <string>Contents/MacOS/NightShiftEnabler</string>
>                 <key>MaxKernel</key>
>                 <string></string>
>                 <key>MinKernel</key>
>                 <string></string>
>                 <key>PlistPath</key>
>                 <string>Contents/Info.plist</string>
>             </dict>
>         </array>
89c174,176
<             <data>AAAAAAAAAAAAAACAAAAAAA==</data>
---
>             <data>
>             AAAAAAAAAAAAAACAAAAAAA==
>             </data>
91c178,180
<             <data>AAAAAAAAAAAAAACAAAAAAA==</data>
---
>             <data>
>             AAAAAAAAAAAAAACAAAAAAA==
>             </data>
118c207
<             <true/>
---
>             <false/>
153a243,244
>         <key>BlessOverride</key>
>         <array/>
165a257,258
>             <key>PickerMode</key>
>             <string>External</string>
174,177d266
<             <key>PickerMode</key>
<             <string>Builtin</string>
<             <key>PickerVariant</key>
<             <string>Auto</string>
179,180d267
<         <key>BlessOverride</key>
<         <array/>
212,213d298
<             <key>BlacklistAppleUpdate</key>
<             <true/>
225c310,311
<             <data></data>
---
>             <data>
>             </data>
227c313,316
<             <data></data>
---
>             <data>
>             </data>
>             <key>ScanPolicy</key>
>             <integer>0</integer>
232,233d320
<             <key>ScanPolicy</key>
<             <integer>0</integer>
244,245d330
<                 <key>UIScale</key>
<                 <data>AQ==</data>
247c332,338
<                 <data>v7+/AA==</data>
---
>                 <data>
>                 v7+/AA==
>                 </data>
>                 <key>UIScale</key>
>                 <data>
>                 Ag==
>                 </data>
251,252d341
<                 <key>boot-args</key>
<                 <string>-no_compat_check</string>
266d354
<                 <string>boot-args</string>
285,293c373
<         <key>UpdateDataHub</key>
<         <false/>
<         <key>UpdateNVRAM</key>
<         <false/>
<         <key>UpdateSMBIOS</key>
<         <false/>
<         <key>UpdateSMBIOSMode</key>
<         <string>Create</string>
<         <key>Memory</key>
---
>         <key>DataHub</key>
297c377
<         <key>DataHub</key>
---
>         <key>Memory</key>
302a383,390
>         <key>UpdateDataHub</key>
>         <false/>
>         <key>UpdateNVRAM</key>
>         <false/>
>         <key>UpdateSMBIOS</key>
>         <true/>
>         <key>UpdateSMBIOSMode</key>
>         <string>Create</string>
308,309d395
<             <key>GlobalConnect</key>
<             <false/>
311a398,399
>             <key>GlobalConnect</key>
>             <false/>
334,336c422
<             <string>Disabled</string>
<             <key>SetupDelay</key>
<             <integer>0</integer>
---
>             <false/>
344a431
>             <string>OpenCanopy.efi</string>
357c444
<             <string>Auto</string>
---
>             <string></string>
369,371c456
<             <key>TextRenderer</key>
<             <string>BuiltinGraphics</string>
<             <key>UgaPassThrough</key>
---
>             <key>ClearScreenOnModeSwitch</key>
375,377c460
<             <key>Resolution</key>
<             <string>Max</string>
<             <key>ForceResolution</key>
---
>             <key>DirectGopRendering</key>
379c462
<             <key>ClearScreenOnModeSwitch</key>
---
>             <key>ForceResolution</key>
381,382d463
<             <key>DirectGopRendering</key>
<             <true/>
385,386d465
<             <key>ReplaceTabWithSpace</key>
<             <false/>
390a470,473
>             <key>ReplaceTabWithSpace</key>
>             <false/>
>             <key>Resolution</key>
>             <string>Max</string>
392a476,479
>             <key>TextRenderer</key>
>             <string>BuiltinGraphics</string>
>             <key>UgaPassThrough</key>
>             <false/>
434a522,523
>             <key>DeduplicateBootOrder</key>
>             <false/>
 
I can definitely try to use the original config.plist that CDF supplied back when the guide reflected 0.6.3...I have it saved. Will try that to see if it makes any difference, but I'm doubtful that the problem is in config.plist, the security updater F__ed something up when it only halfway did whatever it did and then reported it couldn't complete, but it left my catalina partition in some broken state.
 
Dewdman42 said:
weird stuff for sure. like the main Catalina Drive has an empty /Applications folder, for example, but on the "Catalina - Data" volume, there is an /Applications folder that has all my apps. Did they all get moved to the protected DATA partition as part of this security update or something? Maybe apps were always on DATA, I'm not really sure, but I didn't think so.
Click to expand...
Yes it looks like it is doing some movement around but it never manages to restore the system volume structure. Nothing related to OC can help you. Now you have to create an image of that container and later on when you reinstall Catalina and boot from it, mount the image and do a backup task in CCC from DATA folder to your new Catalina drive. It will copy most of it back except the Applications bin and user/bin folders. You will have to do that manually. If you have brew installed run also brew doctor to link everything back. I wish there was a more automated process. Look also at this guide:
gist.github.com

APFS Container cloning/replicating under macOS 11.0 (Big Sur) - with a bootable system

APFS Container cloning/replicating under macOS 11.0 (Big Sur) - with a bootable system - readme.md
gist.github.com gist.github.com
 
  • Like
Reactions: Dewdman42
That is excellent news startergo I see light at the end of the tunnel...what you are suggesting is still WAY better then wipe and reinstall!

I'll take a look at that GitHub thread and PM you maybe later if I can't figure it out.

But did you ever figure out a way to get the security update applied?
 
Dewdman42 said:
That is excellent news startergo I see light at the end of the tunnel...what you are suggesting is still WAY better then wipe and reinstall!

I'll take a look at that GitHub thread and PM you maybe later if I can't figure it out.

But did you ever figure out a way to get the security update applied?
Click to expand...
I just created the image from the Disk Utility. I saw that article later. I may try again once I have a full backup.
 
cdf said:
The guide has been updated to OpenCore version 0.6.5.
Click to expand...
The plistlib generator was also updated to 1.0.8 release. Notable changes (see commit):
  • OpenCore 0.6.5
  • Submodule OcBinaryData, 712 files updated
@cdf, please put a note into OP, so users update the OcBinaryData files. The plistlib generator will do this for you automatically.
 
Last edited:
startergo said:
I just created the image from the Disk Utility. I saw that article later.
Click to expand...

Did you ever manage to get the security update applied to catalina in some other way?

I do have brew installed, But it wasn't clear to me what that doctor command would do for me in your explanation, perhaps you are hoping that after restoring from the DATA backup, that would fix everything...

I guess what you're suggesting is that we have to reinstall Catalina no matter what because the security updater FUBAR'd the volume structure in some way we don't understand (yet).

Once we have catalina installed again on a correct structured volume, then we can RESTORE from somewhere, provided we have a backup to restore from. it sounds like you basically didn't have one, so you backed up your DATA partition first...which at least allowed you to get some stuff back...(knock on wood)... mostly. And hopefully it's right...though I'm a little nervous about broken links between DATA and normal partition in that process... I will read the GitHub stuff first.

I also have most of my stuff backed up on TimeMachine, so I might prefer to restore from there after reinstall of Catalina.
 
Dewdman42 said:
I also have most of my stuff backed up on TimeMachine, so I might prefer to restore from there after reinstall of Catalina
Click to expand...
That is probably the best way to restore. I made an image of the whole container not only from the DATA volume.
 
Dewdman42 said:
I can't seem to figure out how to specify the whole container as the source in CCC. How did you do that?
Click to expand...
You got me wrong. I said image from Disk Utility as a whole container. in CCC Back up from folder (select your DATA volume from the container of the mounted image) to your current booted drive.
 
Hi guys,
Just did a fresh OC/Catalina install on my 5,1 on a Sata SSD.
Kexts added:
lilu
Whatevergreen
AppleMCERReportDisabler
NighshiftEnabler

Hybridization

Wifi seems to have disappeared on this install for some reason.

System info just shows the Software Versions but no interface.

Was working fine on previous OC 0.6.3



Any help appreciated.

Edit: I remember what I did on the last system. I reverted back to Dosdude!
 
Last edited:
Hey there!
I've just set up my 5.1 following this guide, and I have an odd problem. When I boot the system, I get a blank grey screen for about 1-2 seconds, then the screen goes black and has no further video. Not even sure if the system is booting. If I reset the PRAM (NVRAM?) (CMD-OPT-P-R) I get video for one boot cycle, but upon reboot I again have to reset the PRAM to get the system to boot. Note - When the screen goes blank, the monitor is still receiving video, it is simply a black screen. But the monitor is definitely getting a "sync" signal.
System specs below:
MP5,1 - Dual 6-core Xeon 2.8Ghz
64GB DDR3 1333 (8x8GB)
OpenCore 0.65
Boot ROM 144.0.0.0
MacVidCards Flashed Sapphire RX580 8gb
Sonnet Allegro USB 3 card
Sonnet Tempo Dual SSD Card
Booting from onboard SATA or the Tempo card does not seem to make any difference.
 
Xomagen said:
Hey there!
I've just set up my 5.1 following this guide, and I have an odd problem. When I boot the system, I get a blank grey screen for about 1-2 seconds, then the screen goes black and has no further video. Not even sure if the system is booting. If I reset the PRAM (NVRAM?) (CMD-OPT-P-R) I get video for one boot cycle, but upon reboot I again have to reset the PRAM to get the system to boot. Note - When the screen goes blank, the monitor is still receiving video, it is simply a black screen. But the monitor is definitely getting a "sync" signal.
System specs below:
MP5,1 - Dual 6-core Xeon 2.8Ghz
64GB DDR3 1333 (8x8GB)
OpenCore 0.65
Boot ROM 144.0.0.0
MacVidCards Flashed Sapphire RX580 8gb
Sonnet Allegro USB 3 card
Sonnet Tempo Dual SSD Card
Booting from onboard SATA or the Tempo card does not seem to make any difference.
Click to expand...
You might have to boot the debug version and enable the debug logging.

#OpenCore Debugging​

  • Supported version: 0.6.5
Needing to figure out why you're getting issues or stalling? Well, you've come to the right place:

#File Swaps​

To start, make sure you're using either the DEBUG or NOOPT versions of OpenCore. This will provide much more info than the RELEASE version, 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
replace.6929333c.png


  • Note: Generally best to debug systems without OpenCanopy, if required make sure this file is from DEBUG else there will be virtually no debug information.

#Config Changes​

Next, head to your config.plist and locate the Misc section, we have a couple entries we'll want to play with here:

#Misc​

Here we'll want to enable the following:

  • AppleDebug: YES
    • Provides much more debugging information, specifically relating to boot.efi and will also store the log to disk.
  • ApplePanic: YES
    • This will allow kernel panics to be stored to disk, highly recommend keeping keepsyms=1 in boot-args to preserve as much info as possible.
  • DisableWatchdog: YES
    • Disables the UEFI watchdog, used for when OpenCore is stalling on something non-critical.
  • Target: 65
    • Used for enabling different levels of debugging
ValueComment
0x01Enable Logging
0x02Enable Onscreen debug
0x04Enable logging to Data Hub.
0x08Enable serial port logging.
0x10Enable UEFI variable logging.
0x20Enable non-volatile UEFI variable logging.
0x40Enable logging to file.
To calculate the target, we can use a HEX calculator and then convert it to decimal. For us we want to have our values on stored onto a .txt file for later viewing:

  • 0x01 — Enable Logging
  • 0x40 — Enable logging to file.
0x01 + 0x40 = 0x41

0x41 converted to decimal becomes 65

So we can set Misc -> Debug -> Target -> 65

  • DisplayLevel: 2147483714(or calculate one below)
    • Used for setting what is logged
ValueComment
0x00000002DEBUG_WARN in DEBUG, NOOPT, RELEASE.
0x00000040DEBUG_INFO in DEBUG, NOOPT.
0x00400000DEBUG_VERBOSE in custom builds.
0x80000000DEBUG_ERROR in DEBUG, NOOPT, RELEASE.
A full list can be found in DebugLib.h (opens new window).

We just want the following:

  • 0x00000002 — DEBUG_WARN in DEBUG, NOOPT, RELEASE.
  • 0x00000040 — DEBUG_INFO in DEBUG, NOOPT.
  • 0x80000000 — DEBUG_ERROR in DEBUG, NOOPT, RELEASE.
Just like with Target, we use a HEX calculator then convert to decimal:

0x80000042 Converted to decimal Misc -> Debug -> DisplayLevel -> 2147483714
Click to expand...
 
OK, I've got some results. I'm posting two logs, the one titled opencore-2021-01-06-001800.txt is from the failed boot, and the other is from a subsequent reboot while resetting PRAM.
 

Attachments

  • opencore-2021-01-06-001800.txt
    256 KB · Views: 103
  • opencore-2021-01-06-001800.txt
    256 KB · Views: 183
Xomagen said:
Strangely, The second log is a successful boot, which is a Catalina install that I am actually using to send you this message. I even got the text-based simple boot picker.
Click to expand...
It is the same log file:

Code: 
00:000 00:000 OC: OpenCore DBG-065-2021-01-04 is loading in Optional mode (0/0)...
00:018 00:018 OC: Boot timestamp - 2021.01.06 00:18:00
 
startergo said:
It is the same log file:

Code: 
00:000 00:000 OC: OpenCore DBG-065-2021-01-04 is loading in Optional mode (0/0)...
00:018 00:018 OC: Boot timestamp - 2021.01.06 00:18:00
Click to expand...
Whoops. Now I feel dumb...
Here's the second file:
 
Suddenly I am unable to u
startergo said:
You did not attach it. Anyway try the suggestion I gave you.
Click to expand...
Yeah, weirdly my browser suddenly stopped letting me upload files... Sorry. Anyhow the APFS.efi driver seems to have done the trick, thank you very much for the assist!
 
  • Like
Reactions: startergo
Xomagen said:
Anyhow the APFS.efi driver seems to have done the trick
Click to expand...
Just so you understand what is actually going on, cards flashed by MacVids often disable APFS in the Early Boot Stage (before OpenCore is started) for unknown reasons.

You then need to manually enable APFS for a boot manager such as OpenCore to use APFS as if your Macs does not have APFS support.

You can manually enable APFS by loading a driver as you have just done but probably better to use OpenCore's inbuilt capability as apfs drivers can vary for different Mac OS versions and you will be loading a specific version driver. The inbuilt function will load the specific one for the specific Mac OS version you are booting.

To activate, remove the apfs.efi file and just set "EnableJumpstart" to "true" in your OpenCore Config. Set "HideVerbose" to true to hide scrolling text.

For anyone thinking of flashing their cards, there is no reason to flash cards anymore.
 
Last edited:
  • Like
Reactions: paalb
Can I run Catalina on E2008MP3,1 with OpenCore?
I also have M2010MP5,1 running Catalina on with OpenCore.
Is BootROM important?
I feel it can install it with Catalina Patcher on OpenCore, is that impossible?
I don't use NVMe, use SATA.
 
Gr1f said:
Hi guys,
Just did a fresh OC/Catalina install on my 5,1 on a Sata SSD.
Kexts added:
lilu
Whatevergreen
AppleMCERReportDisabler
NighshiftEnabler

Hybridization

Wifi seems to have disappeared on this install for some reason.

System info just shows the Software Versions but no interface.

Was working fine on previous OC 0.6.3



Any help appreciated.

Edit: I remember what I did on the last system. I reverted back to Dosdude!
Click to expand...
So managed to get this to work.

Used the Mojave kext found here
github.com

GitHub - khronokernel/IO80211-Patches: Repo for patched IO80211Family Kexts

Repo for patched IO80211Family Kexts. Contribute to khronokernel/IO80211-Patches development by creating an account on GitHub.
github.com github.com

and dropped it into OC/Kexts

Then added the following into config.plist

Code: 
            <dict>
                <key>Comment</key>
                <string></string>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
                <key>Enabled</key>
                <true/>
                <key>MaxKernel</key>
                <string>20.99.99</string>
                <key>MinKernel</key>
                <string>19.0.0</string>
                <key>ExecutablePath</key>
                <string>Contents/MacOS/IO80211Mojave</string>
                <key>Arch</key>
                <string>Any</string>
                <key>BundlePath</key>
                <string>IO80211Mojave.kext</string>
            </dict>
            <dict>
                <key>Comment</key>
                <string></string>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
                <key>Enabled</key>
                <true/>
                <key>MaxKernel</key>
                <string>20.99.99</string>
                <key>MinKernel</key>
                <string>19.0.0</string>
                <key>ExecutablePath</key>
                <string>Contents/MacOS/AirPortBrcm4331</string>
                <key>Arch</key>
                <string>Any</string>
                <key>BundlePath</key>
                <string>IO80211Mojave.kext/Contents/PlugIns/AirPortBrcm4331.kext</string>
            </dict>

Interfaces:


en3:


Card Type: AirPort Extreme (0x14E4, 0x8E)
Firmware Version: Broadcom BCM43xx 1.0 (5.106.98.102.31)
MAC Address: ———————
Locale: ETSI
Country Code: IE
Supported PHY Modes: 802.11 a/b/g/n
Supported Channels: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 36, 40, 44, 48, 52, 56, 60, 64, 100, 104, 108, 112, 116, 120, 124, 128, 132, 136, 140
Wake On Wireless: Supported
Status: Connected


Massive thanks to @EETagent !
 
  • Like
Reactions: JedNZ, octoviaa, Takubon and 3 others
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back