MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro

[Dayo]

Take a look at the changelog. Have any related problems? Update. No? Then why touch things that just work?

Disagree. With that approach, we would still be living in caves today.

The udates are not just about fixing "problems" but more importantly, they implement improvements ... many of which are under the hood so to speak.

 

[vrds]

Disagree. With that approach, we would still be living in caves today.

The udates are not just about fixing "problems" but more importantly, they implement improvements ... many of which are under the hood so to speak.

And again, why don't take a look at the changelog? Isn't it what it's made for?

 

[Dayo]

And again, why don't take a look at the changelog? Isn't it what it's made for?

Of course I look at the change log.

The point is that you dont upgrade because you must. You upgrade because you can.

 

[vrds]

Of course I look at the change log.

The point is that you dont upgrade because you must. You upgrade because you can.

Nope. Don't understand me incorrect. My point is 'you should make your own conclusion based on...'.

 

[Dayo]

My point is 'you should make your own conclusion based on...'.

Got it

 

[Paolo-Sp]

Hello
First of all I want to thank all of you for making it possible to start MacPro with OpenCore which for me, is much better than the Catalina Patch.
I ask if any of one managed to activate Night Shift for the monitor as it. The changes to CoreBrightness.framework with Catalina are practically impossible because after change I can not make cteminal command "sudo codesign -f -s - /S*/L*/PrivateFrameworks/CoreBrightness.framework/Versions/Current/CoreBrightness" for re-sign file,
Please help me... Thank you very much

 

[cdf]

Hello
First of all I want to thank all of you for making it possible to start MacPro with OpenCore which for me, is much better than the Catalina Patch.
I ask if any of one managed to activate Night Shift for the monitor as it. The changes to CoreBrightness.framework with Catalina are practically impossible because after change I can not make cteminal command "sudo codesign -f -s - /S*/L*/PrivateFrameworks/CoreBrightness.framework/Versions/Current/CoreBrightness" for re-sign file,
Please help me... Thank you very much

This is what you want:

GitHub - cdf/NightShiftEnabler: Enable Night Shift on unsupported Mac models

Enable Night Shift on unsupported Mac models. Contribute to cdf/NightShiftEnabler development by creating an account on GitHub.

github.com

 

[TECK]

Well, the plugin works fine. Did you try that?

Do you know where we can get the Night Shift enabler plugin? Install instructions is possible, thanks!

Edit: man you are fast.
Looks like I have to install Lilu after all.

 

[TECK]

@cdf is this the only change I need to make into config.plist?

    <key>Kernel</key>
    <dict>
        <key>Add</key>
        <array>
            <dict>
                <key>BundlePath</key>
                <string>Lilu.kext</string>
                <key>Comment</key>
                <string/>
                <key>Enabled</key>
                <true/>
                <key>ExecutablePath</key>
                <string>Contents/MacOS/Lilu</string>
                <key>MaxKernel</key>
                <string/>
                <key>MinKernel</key>
                <string/>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
            </dict>
            <dict>
                <key>BundlePath</key>
                <string>NightShiftUnlocker.kext</string>
                <key>Comment</key>
                <string/>
                <key>Enabled</key>
                <true/>
                <key>ExecutablePath</key>
                <string>Contents/MacOS/NightShiftUnlocker</string>
                <key>MaxKernel</key>
                <string/>
                <key>MinKernel</key>
                <string>19.0.0</string>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
            </dict>
        </array>

 

[cdf]

@cdf is this the only change I need to make into config.plist?

Note that the guide is being updated and will touch on installing kexts like NightShiftEnabler. Regarding your configuration: The name of the plugin is NightShiftEnabler (it is the current successor to the previous "unlocker" plugin). By default, the plugin ignores macOS versions without Night Shift, so no need to specify MinKernel. Also, try replacing <string/> by <string></string> (Xcode should do the replacement automatically).

 

[Charles.tech]

Hi
I want to install macOS and Windows10 on same NVMe drive with partition.
I tried installing windows at EFI after finished install opencore. but, it destroyed opencore system that I jast intall.
How can I install Both?
Please help me..

 

[Paolo-Sp]

In the link https://github.com/cdf/NightShiftEnabler I can download the NightShiftUnlocker.kext file that does not work.
The NightShiftEnabler is to be compiler but I can not make it

 

[startergo]

Hi
I want to install macOS and Windows10 on same NVMe drive with partition.
I tried installing windows at EFI after finished install opencore. but, it destroyed opencore system that I jast intall.
How can I install Both?
Please help me..

There is a way:

5. BootProtect
Type: plist string
Failsafe: None
Description: Attempt to provide bootloader persistence.
Valid values:

• None — do nothing.
• Bootstrap — create or update top-priority \EFI\OC\Bootstrap\Bootstrap.efi boot option (Boot9696)
  in UEFI variable storage at bootloader startup. For this option to work RequestBootVarRouting is required to be enabled.
  This option provides integration with third-party operating system installation and upgrade at the times they overwrite \EFI\BOOT\BOOTx64.efi file. By creating a custom option in Bootstrap mode this file path becomes no longer used for bootstraping OpenCore.

Bear in mind this option only works properly in the latest 0.5.9 from source. So you will have to compile it yourself. Once you boot at least once OC with this option you or Windows can do whatever they want with:

\EFI\BOOT\BOOTx64.efi file

As it is no longer used for loading OC. By the way if you replace

\EFI\BOOT\BOOTx64.efi

with the OC version you will restore OC boot as it is broken now. But you will loose Windows if you don't provide alternate path in entries. So you are better off using Bootprotect.
[automerge]1588949477[/automerge]

In the link https://github.com/cdf/NightShiftEnabler I can download the NightShiftUnlocker.kext file that does not work.
The NightShiftEnabler is to be compiler but I can not make it

Releases · cdf/NightShiftEnabler

Enable Night Shift on unsupported Mac models. Contribute to cdf/NightShiftEnabler development by creating an account on GitHub.

github.com

 

[Paolo-Sp]

It works
Thank you so much

 

[halalmeats]

Anyone have a relatively step-by-step guide to installing a linux distro to boot with OC? Only info I've found was a bit vague (skipping grub installation, or suggested chainloading?) or those my two options? any help appreciated!

 

[Charles.tech]

There is a way:

Bear in mind this option only works properly in the latest 0.5.9 from source. So you will have to compile it yourself. Once you boot at least once OC with this option you or Windows can do whatever they want with:

\EFI\BOOT\BOOTx64.efi file

As it is no longer used for loading OC. By the way if you replace

\EFI\BOOT\BOOTx64.efi

with the OC version you will restore OC boot as it is broken now. But you will loose Windows if you don't provide alternate path in entries. So you are better off using Bootprotect.
[automerge]1588949477[/automerge]

Releases · cdf/NightShiftEnabler

Enable Night Shift on unsupported Mac models. Contribute to cdf/NightShiftEnabler development by creating an account on GitHub.

github.com

thank you!! it worked!
I finally install windows without braking opencore but, I can't boot in windows.
Windows doesn't appear in boot select screen. Only macOS.


When I install oc, I couldn't find RequestBootVarRouting settings. so, maybe that is the problem.

How to turn on RequestBootVarRouting or How to add Windows into boot select screen?

 

[Dayo]

How to turn on RequestBootVarRouting or How to add Windows into boot select screen?

Have you taken some time to refer to the documentation that comes with OpenCore?

 

[dme881]

I cannot reboot into recovery mode in step 3 - not even by pressing Apple+R. What should I do?

Below is the output if I try to bless under Mojavee

EFI found at IODeviceTree:/efi
Mount point for /Volumes/EFI is /Volumes/EFI
Mount point is '/Volumes/EFI'
No BootX creation requested
No boot.efi creation requested
found ioreg "FirmwareFeaturesMask"; featureMaskValue=0xFF1FFF3F
found ioreg "FirmwareFeatures"; featureFlagsValue=0xC00C5403
isPreBootEnvironmentUEFIWindowsBootCapable=0
preboot environment is not UEFI boot capable
isDVDWithElToritoWithUEFIBootableOS=0
Checking if disk is complex (if it is associated with booter partitions)
GPT detected
Booter partition required at index 2
System partition found
Preferred system partition found: disk2s1
Returning booter information dictionary:
<CFBasicHash 0x7fb4f17003d0 [0x7fff8dd988e0]>{type = mutable dict, count = 3,
entries =>
    0 : <CFString 0x10887abe0 [0x7fff8dd988e0]>{contents = "System Partitions"} = (
    disk2s1,
    disk0s1
)
    1 : <CFString 0x10887b3c0 [0x7fff8dd988e0]>{contents = "Data Partitions"} = (
    disk0s1
)
    2 : <CFString 0x10887b3e0 [0x7fff8dd988e0]>{contents = "Auxiliary Partitions"} = (
)
}

Relative path of /Volumes/EFI/EFI/BOOT/BOOTx64.efi is \EFI\BOOT\BOOTx64.efi
IOMedia disk0s1 has UUID E52A9D55-6418-4CD8-82C0-2455E8897110
Setting EFI NVRAM:
    efi-boot-device='<array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>E52A9D55-6418-4CD8-82C0-2455E8897110</string></dict></dict><key>BLLastBSDName</key><string>disk0s1</string></dict><dict><key>IOEFIDevicePathType</key><string>MediaFilePath</string><key>Path</key><string>\EFI\BOOT\BOOTx64.efi</string></dict></array>'
Could not set boot device property: 0xe00002e2

 

[startergo]

I cannot reboot into recovery mode in step 3 - not even by pressing Apple+R. What should I do?

Below is the output if I try to bless under Mojavee

EFI found at IODeviceTree:/efi
Mount point for /Volumes/EFI is /Volumes/EFI
Mount point is '/Volumes/EFI'
No BootX creation requested
No boot.efi creation requested
found ioreg "FirmwareFeaturesMask"; featureMaskValue=0xFF1FFF3F
found ioreg "FirmwareFeatures"; featureFlagsValue=0xC00C5403
isPreBootEnvironmentUEFIWindowsBootCapable=0
preboot environment is not UEFI boot capable
isDVDWithElToritoWithUEFIBootableOS=0
Checking if disk is complex (if it is associated with booter partitions)
GPT detected
Booter partition required at index 2
System partition found
Preferred system partition found: disk2s1
Returning booter information dictionary:
<CFBasicHash 0x7fb4f17003d0 [0x7fff8dd988e0]>{type = mutable dict, count = 3,
entries =>
    0 : <CFString 0x10887abe0 [0x7fff8dd988e0]>{contents = "System Partitions"} = (
    disk2s1,
    disk0s1
)
    1 : <CFString 0x10887b3c0 [0x7fff8dd988e0]>{contents = "Data Partitions"} = (
    disk0s1
)
    2 : <CFString 0x10887b3e0 [0x7fff8dd988e0]>{contents = "Auxiliary Partitions"} = (
)
}

Relative path of /Volumes/EFI/EFI/BOOT/BOOTx64.efi is \EFI\BOOT\BOOTx64.efi
IOMedia disk0s1 has UUID E52A9D55-6418-4CD8-82C0-2455E8897110
Setting EFI NVRAM:
    efi-boot-device='<array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>E52A9D55-6418-4CD8-82C0-2455E8897110</string></dict></dict><key>BLLastBSDName</key><string>disk0s1</string></dict><dict><key>IOEFIDevicePathType</key><string>MediaFilePath</string><key>Path</key><string>\EFI\BOOT\BOOTx64.efi</string></dict></array>'
Could not set boot device property: 0xe00002e2

This output is from which command? The bless command should be done from recovery or you should disable SIP to bless from Mojave.

 

[dme881]

This output is from which command? The bless command should be done from recovery or you should disable SIP to bless from Mojave.

Yes, but Im not able to boot via a USB or the Recovery partition. Open Core shows up now when I boot normally, but can only chose the original Mojave disk. Using startup panel and selecting the USB does not allow it to boot.
Waited with black screen for 1 hours, nothing.

EDIT; OpenCore started without bless, and when stating with OpenCore+MacOs USB stick, Displayports where black. HDMI worked.

 

[cdf]

Anyone have a relatively step-by-step guide to installing a linux distro to boot with OC? Only info I've found was a bit vague (skipping grub installation, or suggested chainloading?) or those my two options? any help appreciated!

Chainloading is not necessary: OpenCore can take care of all your booting needs. I will probably eventually add a section to the guide for third-party-OS installation.

 

[dme881]

I had a windows 10 bootcamp setup with Mojave. Catalina recognizes it but refuses to boot. Open Core does not see the disc. How to make OpenCore see the bootcamp installation?

EDIT: So I read the OpenCore documentation, and adjusted the ScanPolicy to 4136704. OpenCore Crashed

EDIT2: So it seems like my Bootcamp installation was MBR record, even for Windows 10. For anyone else reading this: Make sure your bootcamp is not MBR, but EFI. If MBR, convert: https://www.windowscentral.com/how-convert-mbr-disk-gpt-move-bios-uefi-windows-10
Happy days

 

[halalmeats]

Chainloading is not necessary: OpenCore can take care of all your booting needs. I will probably eventually add a section to the guide for third-party-OS installation.

That would be amazing!

 

[Enricote]

I had a windows 10 bootcamp setup with Mojave. Catalina recognizes it but refuses to boot. Open Core does not see the disc. How to make OpenCore see the bootcamp installation?

EDIT: So I read the OpenCore documentation, and adjusted the ScanPolicy to 4136704. OpenCore Crashed

EDIT2: So it seems like my Bootcamp installation was MBR record, even for Windows 10. For anyone else reading this: Make sure your bootcamp is not MBR, but EFI. If MBR, convert: https://www.windowscentral.com/how-convert-mbr-disk-gpt-move-bios-uefi-windows-10
Happy days

I have been reading a lot here about this particular problem. My windows 10 (bootcamp) is in Legacy BIOS Mode so I can not see Windows in the OpenCore Boot picker. I just can open windows because I still have a flashed GPU with EFI selector.

Can you please confirm us that procedure you mention in you EDIT2 (Microsoft MBR2GPT command line tool) transformed your Legacy BIOS windows to UEFI Mode without issues and from then you can open Windows from Opencore Boot picker?

My Bootcamp Windows 10 is in a Partition of one SSD (different drives for my Mojave and my Catalina with Opencore)

Sorry if something is not clear. I am just a nonprofressional user. I know this problem has been treated in many places here but not in the users level, I should say. Thank you all the people here!

 

[Neanderphil]

There is a way:

Bear in mind this option only works properly in the latest 0.5.9 from source. So you will have to compile it yourself. Once you boot at least once OC with this option you or Windows can do whatever they want with:

\EFI\BOOT\BOOTx64.efi file

As it is no longer used for loading OC. By the way if you replace

\EFI\BOOT\BOOTx64.efi

with the OC version you will restore OC boot as it is broken now. But you will loose Windows if you don't provide alternate path in entries. So you are better off using Bootprotect.
[automerge]1588949477[/automerge]

Releases · cdf/NightShiftEnabler

Enable Night Shift on unsupported Mac models. Contribute to cdf/NightShiftEnabler development by creating an account on GitHub.

github.com

I had previously read that UEFI installations of windows 10 can corrupt the NVRAM By adding additional boot certificates. Is this safe with opencore now? Thanks