Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
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.
Open Core version 0.5.7 was just released:

Repository: acidanthera/OpenCorePkg · Tag: 0.5.7 · Commit: 80a82ed · Released by: vandroiy2013
v0.5.7
  • Added TimeMachine detection to picker
  • Added early preview version of OpenCanopy
  • Fixed FS discovery on NVMe with legacy drivers
  • Added DirectGopCacheMode option for FB cache policy
  • Added KeyFiltering option to workaround buggy KB drivers
  • Added tool and custom entry separation in audio assistant
  • Added OpenControl tool to configure full NVRAM access from Shell
  • Added boot.efi debug protocol support for 10.15.4+
  • Added boot.efi performance logging for 10.15.4+
  • Added ProtectUefiServices quirk to fix DevirtualiseMmio on Z390
  • Replaced BOOTCAMP Windows with Windows to match the original
  • Added bundled OpenShell originally available as OpenCoreShell
  • Rework readlabel utility into disklabel with encoding support
  • Renamed FwRuntimeServices driver to OpenRuntime
  • Renamed AppleUsbKbDxe driver to OpenUsbKbDxe
  • Update builtin firmware
  • Fixed PowerTimeoutKernelPanic on 10.15.4
  • Fixed 4K section alignment in OpenRuntime to fix Linux booting on SKL
  • Introduced SyncRuntimePermissions to fix multiple memory permission flaws
  • Introduced RebuildAppleMemoryMap to fix macOS booting on Dell 5490
  • Removed ShrinkMemoryMap in favour of more advanced RebuildAppleMemoryMap
  • Marked EnableWriteUnprotector as deprecated on modern systems
  • Introduced ProtectMemoryRegions to fix memory region handling
  • Removed ProtectCsmRegion in favour of ProtectMemoryRegions
  • Renamed PickerAttributes to ConsoleAttributes
  • Introduced PickerAttributes as a matter of UI configuration

—​

Okay, saw that. Question: how to update a stable 0.5.6 OC install on a 5,1?
 
How can I get opencore with Mac OS 10.15.4 on it install pcie card with two 2.5 SSD to play nicely with windows 10 on pcie card with one SSD what is the setting in config Plist
 
To update OC simply repeat the steps in section 3 of the guide.

Okay, did that with the Config.plist at the top of the thread, and now my NVME drives are again indicated as external. VideoProc is also showing no hardware acceleration as well. I noted that the above config.plist lacks entries for the Lilu & WhateverGreen kexts.
 
Okay, did that with the Config.plist at the top of the thread, and now my NVME drives are again indicated as external. VideoProc is also showing no hardware acceleration as well. I noted that the above config.plist lacks entries for the Lilu & WhateverGreen kexts.

The guide in this thread provides a basic configuration. To enable more advanced features, you will have to include the kexts and modify the config file. Have a look at these instructions in the hardware acceleration thread:


Note: Because you have a dual-processor machine, make sure to include AppleMCEReporterDisabler.
 
The guide in this thread provides a basic configuration. To enable more advanced features, you will have to include the kexts and modify the config file. Have a look at these instructions in the hardware acceleration thread:


Note: Because you have a dual-processor machine, make sure to include AppleMCEReporterDisabler.

mangombia , Just share experience, you may like me, dual core Xeon Model.
Try to use the package of below by startergo.
I am using the REL057-2020-04-04.zip and become normal boot the OC with Hardware acceleration.


 
Dear all
I searching if it is possible to deploy OpenCore on Mojave Cmp 5.1 without installing Catalina?
Because my software (major CS6) are not compatible with Catalina.
Thank you
 
Dear all
I searching if it is possible to deploy OpenCore on Mojave Cmp 5.1 without installing Catalina?
Because my software (major CS6) are not compatible with Catalina.
Thank you

Yes, of course. Just skip section 6 in the guide.
 
The guide in this thread provides a basic configuration. To enable more advanced features, you will have to include the kexts and modify the config file. Have a look at these instructions in the hardware acceleration thread:


Note: Because you have a dual-processor machine, make sure to include AppleMCEReporterDisabler.

Thanks for that. I made those changes for Lilu, WhateverGreen & MCEReporterDisabler, GPU acceleration is back, but my NVME drives still show as external. Would removing Lilu but adding the NvmExpressDxe.efi driver from 0.5.7 release fix it?
 
Thank you very much,

not sure I understand,

<array>
<string>mbasd=1</string>
</array>
<key>block</key>

like that? not sure it's that
Please refer to my sample.

You make it too simple here. I can't tell if you put them in the right section, with the correct format.

If in doubt, upload your config to here.
[automerge]1586275486[/automerge]
Thanks for that. I made those changes for Lilu, WhateverGreen & MCEReporterDisabler, GPU acceleration is back, but my NVME drives still show as external. Would removing Lilu but adding the NvmExpressDxe.efi driver from 0.5.7 release fix it?
NO, do NOT remove Lilu.

If you want to remove innie, you can just remove innie, but not with Lilu together. Other kexts also depend on that.
 
Please refer to my sample.

You make it too simple here. I can't tell if you put them in the right section, with the correct format.

If in doubt, upload your config to here.
[automerge]1586275486[/automerge]

NO, do NOT remove Lilu.

If you want to remove innie, you can just remove innie, but not with Lilu together. Other kexts also depend on that.

Here's my config.plist. I'm fairly certain it is correct, but NVMEs still appear as external.
 

Attachments

  • config.txt
    8.4 KB · Views: 122
Thanks for that. I made those changes for Lilu, WhateverGreen & MCEReporterDisabler, GPU acceleration is back, but my NVME drives still show as external. Would removing Lilu but adding the NvmExpressDxe.efi driver from 0.5.7 release fix it?

The easiest way for your drives to be seen as internal is to add Innie. (Install the plugin like the other kexts.) Another way (the way Apple does it) is with the built-in DeviceProperty (see posts #1,171 and #1,176).
 
I can't see any mbasd=1 in your config. Did you upload the updated one?

For NVMe external, please try innie first if not yet done.

Thanks for catching that omission. Here is the updated config.plist (in txt format). After much sleuthing, and using GFXUTIL I was able to modify the Device Properties entries for these NVME drives. Am now fully functional (at least the 5,1 is, can't speak for myself).

I realize people say it makes no performance difference whether NVME drives are seen as internal or external, but I like to hide my internal drives from the Finder desktop, and have external drives appear when they're connected (think USB drives).

Now I may start to consider setting up a graphical boot picker screen in OpenCore. Any instructions, tutorials or advice on that front?
 

Attachments

  • config.txt
    8.8 KB · Views: 126
  • Like
Reactions: zoltm and h9826790
Please refer to my sample.

You make it too simple here. I can't tell if you put them in the right section, with the correct format.

If in doubt, upload your config to here.
[automerge]1586275486[/automerge]

NO, do NOT remove Lilu.

If you want to remove innie, you can just remove innie, but not with Lilu together. Other kexts also depend on that.


I have put it as such:


<key>NVRAM</key>
<dict>
<key>Add</key>
<dict>
<key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
<dict>
<key>boot-args</key>
----->> <string>agdpmod=pikera shikigva=80 mbasd=1 -wegtree -no_compat_check no32exec=0</string>
<key>csr-active-config</key>
<data>dwAAAA==</data>
</dict>
</dict>
<key>Block</key>
<dict>
<key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
<array>
<string>boot-args</string>
</array>
</dict>
<key>LegacyEnable</key>
<false/>
 
  • Like
Reactions: zoltm
The latest config in the guide sets the option to reinstall the Apple User Interface Theme protocol. This option makes it possible to set the DefaultBackgroundColor variable (which I believe was disabled by a BootROM update sometime during the High Sierra and Mojave days). This variable defines the background of the Apple loading screen and FileVault login screen. The default on the cMP is light gray. On newer Macs, the default is black.
 
The latest config in the guide sets the option to reinstall the Apple User Interface Theme protocol. This option makes it possible to set the DefaultBackgroundColor variable (which I believe was disabled by a BootROM update sometime during the High Sierra and Mojave days). This variable defines the background of the Apple loading screen and FileVault login screen. The default on the cMP is light gray. On newer Macs, the default is black.
Code:
<key>ConsoleAttributes</key>
            <integer>112</integer>
..............

<key>PickerAttributes</key>
            <integer>1</integer>
The above sets the grey background as well
 
The above sets the grey background as well

Sure. But my comment is not about the OC boot picker, but rather the boot.efi interface, in particular the loading screen. My point is that the DefaultBackgroundColor variable can be made to work (like it does on other Macs and like it did in the past).
 
Sure. But my comment is not about the OC boot picker, but rather the boot.efi interface, in particular the loading screen. My point is that the DefaultBackgroundColor variable can be made to work (like it does on other Macs and like it did in the past).
Are you talking about this:
Code:
<key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key>
            <dict>
                <key>DefaultBackgroundColor</key>
                <data>
                AAv7+w==
[automerge]1586314142[/automerge]
Sure. But my comment is not about the OC boot picker, but rather the boot.efi interface, in particular the loading screen. My point is that the DefaultBackgroundColor variable can be made to work (like it does on other Macs and like it did in the past).
Are you talking about this:
Code:
<key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key>
            <dict>
                <key>DefaultBackgroundColor</key>
                <data>
                v7+/AA==
 
Last edited:
Are you talking about this:

I had similar in v0.5.6 ... along with
Code:
<key>PickerAttributes</key>
<integer>112</integer>

This gave a nice native cMP looking light grey picker screen and loading screen in v0.5.6 on my cMP 3,1.
v0.5.7 changed PickerAttributes extensively and moved picker appearance items stuff into ConsoleAttributes.

Equivalent in v0.5.7 is ...

Code:
<key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key>
<dict>
    <key>DefaultBackgroundColor</key>
    <data>v7+/AA==</data>
    ...

and

Code:
<key>ConsoleAttributes</key>
<integer>112</integer>
<key>PickerAttributes</key>
<integer>0</integer>

PickerAttributes is "0" as I prefer to chainload OC from Refind and don't want icons etc in OC.
 
Would you please introduce what I should edit to get a icon boot menu?
I have study many threads but cannot find a tutorial.

I am using package open core 0.5.7 for cMP from h9826790
 
  • Like
Reactions: zoltm
Where can I download the OpenCore 0.5.7 for cMP.zip?
Thank!

 
  • Like
Reactions: zozomester
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.