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

[mangombia]

I was successful updating OC to 0.5.9 and changing from NDK to OpenCanopy. Operational-wise everything works as expected, and I was even able to apply the Catalina 10.15.5 Supplemental Update earlier today. However, I noted that it seems my boot chime has disappeared, so I commanded an NVRAM reset from the OC/OpenCanopy boot picker, and it rebooted with the chime the first time, but not since. Any ideas?

And for what it is worth, the NVRAM output (nvram -xp in Terminal) has no entries or data for any EFI devices such as

efi-backup-boot-device
efi-backup-boot-device-data
efi-boot-device
efi-boot-device-data

Which appear on my media server that I did not do an NVRAM reset through OC/OpenCanopy.

 

[joevt]

And for what it is worth, the NVRAM output (nvram -xp in Terminal) has no entries or data for any EFI devices such as

efi-backup-boot-device
efi-backup-boot-device-data
efi-boot-device
efi-boot-device-data

Which appear on my media server that I did not do an NVRAM reset through OC/OpenCanopy.

Boot chime may require volume of Internal Speakers to be set to non-zero (disconnect sound output devices from line out and headphones to be sure the correct volume is being set).

There's a method to enable boot chime on newer Macs (not sure this has anything to do with MP5,1).

How to Enable the Classic Startup Chime on Newer Macs

The discovery of a simple Terminal command that brings back the classic startup chime on newer Macs has gone viral in recent days. Apple disabled the...

www.macrumors.com

Use the bless command or Startup Disk preferences panel to bless Open Core to restore the efi*boot-device* variables.

Use my script and gfxutil to view EFI boot vars (which may be different than those Mac boot vars):

Documentation on all parameters for nvram...?

I don't think anyone's going to document all the options. If you have a question about a specific set of options, then we can try to answer that. Note that "nvram -p" only shows macOS nvram variables. There are many more that you can see with the dmpstore command in an EFI Shell. The nvram...

forums.macrumors.com

Maybe NVRAM reset should be done with keyboard instead of boot loader? Command-Option-P-R?

 

[startergo]

In OC configurator you can query the current nvram data and system volume :

Get NVRAM data drop down menu at the bottom left.

 

[mangombia]

In OC configurator you can query the current nvram data and system volume :
View attachment 921107
Get NVRAM data drop down menu at the bottom left.

This is what I get when invoking that command:

[automerge]1591145125[/automerge]

This is what I get when invoking that command:

And when I try and bring up OC config.plist with OC Configurator I get a popup warning that the "Bootloader looks like it is not installed or the NVRAM is not native."

 

[TECK]

You need to get in safe mode with networking and update the video drivers.

The video drivers are latest from Windows Update so I can use my 4K screen, I was using the text bootpicker before which does not have any issues. Right now everything is fuxored so I need to either re-install Windows again clean or to a system wipe, which will leave the drivers in place but get rid of personal information. Is unfortunate I cannot use OpenCanopy but I'm using Windows every day so I will get back to text bootpicker.

 

[startergo]

The video drivers are latest from Windows Update so I can use my 4K screen, I was using the text bootpicker before which does not have any issues. Right now everything is fuxored so I need to either re-install Windows again clean or to a system wipe, which will leave the drivers in place but get rid of personal information. Is unfortunate I cannot use OpenCanopy but I'm using Windows every day so I will get back to text bootpicker.

Is the safe mode freezing in OpenCanopy as well? Loading in VirtualBox?
[automerge]1591145737[/automerge]

This is what I get when invoking that command: View attachment 921110
[automerge]1591145125[/automerge]


And when I try and bring up OC config.plist with OC Configurator I get a popup warning that the "Bootloader looks like it is not installed or the NVRAM is not native."

What is your firmware revision? I remember the chime disappearance on some cMP's during firmware upgrade on some revisions.

 

[mangombia]

Is the safe mode freezing in OpenCanopy as well? Loading in VirtualBox?
[automerge]1591145737[/automerge]

What is your firmware revision? I remember the chime disappearance on some cMP's during firmware upgrade on some revisions.

Is has been 144.0.0.0.0 since that became available.

 

[startergo]

Is has been 144.0.0.0.0 since that became available.

try triple consecutive NVRAM reset.

 

[mangombia]

try triple consecutive NVRAM reset.

Through the OC/OpenCanopy picker? I can try that. I've thought about doing the OPT-CMD-R-P as well and re-blessing OC to see if that fixes it. I may first try and disable OpenCanopy and go back to the text picker to see if that has an effect.

 

[joevt]

Through the OC/OpenCanopy picker? I can try that. I've thought about doing the OPT-CMD-R-P as well and re-blessing OC to see if that fixes it. I may first try and disable OpenCanopy and go back to the text picker to see if that has an effect.

I think Multi NVRAM reset is something you do with Opt-Cmd-P-R (different behavior after the first or second time?). Open Core probably doesn't have different behavior after the first time (unless documentation says otherwise?)

 

[TECK]

Is the safe mode freezing in OpenCanopy as well? Loading in VirtualBox?

I don't know how to start in safe mode with OpenCanopy. In VirtualBox it loads the repair.

 

[zozomester]

You may try my 0.5.9 package. Or compare your config / EFI folder to my package.

I have OpenCanopy running since 0.5.9 beta
View attachment 920623

How do I change the background to black? For me, it's white .....
Thank!

 

[Charles.tech]

How do I change the background to black? For me, it's white .....
Thank!

?

 

[iModFrenzy]

Soo while back I posted about my Sapphire Pulse 5700XT not displaying any text on the boot picker page when DirectGPORendering is set to false. However, now both options give me no text. So not sure what the issue is here...

For anyone using certain 5700XTs, the text randomly appeared when adding drives or removing them(I could still boot without text visible so it wasn't a connection issue). Luckily, after finishing my Windows 10 install, the text has stuck on boot so no issues now.

Windows 10 threw a fit not wanting to boot during the initial install/after the install completed and I needed to configure the user,etc. After the ENTIRE setup, I've had no issues booting.

Looking forward to OpenCore 6.0...

Also when setting the config for HiDPI displays, what exactly does this do? I can still set retina scaling for my 4k display in system preferences, is it just a cosmetic boot screen option?

 

[Norbert Mikołajczyk]

I've some problem with my Windows Legacy after the OC installation.
I hesitate to do the conversion to the UEFI because of the risk of bricking cMP.
So the problem is: Even if I disable or remove the OC files I cannot boot from Windows into macOS anymore using bootcamp "restart your mac in macos". Earlier it worked every time.
I need to do the NVRAM reset to escape from the Windows Boot Loop. Very annoying.
I searched google but with no results.
I wonder what has changed that "restart your mac in macos" isn't working anymore?
I have two Mojave installations on separate disks: Backup 10.4.6 and my main 10.4.6 with OC.
Is it something with the blessing OC maybe?
What should I do make it work again?

 

[h9826790]

Also when setting the config for HiDPI displays, what exactly does this do? I can still set retina scaling for my 4k display in system preferences, is it just a cosmetic boot screen option?

Correct, that's for the loading screen (and boot picker etc).

Once you boot to the OS, you can set whatever resolution you want in system preferences.

 

[donvito4ever]

Hi again!!

I'm updating from OC 0.5.8 to 0.5.9 my own Mac Pro 5.1 (the other that tonight don't boot fine and solved is of my wife) and I have a doubt:

In the config.plist of 0.5.8 I have this:

<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>bluetoothHostControllerSwitchBehavior</key>
                <string>always</string>
            </dict>
        </dict>
        <key>Block</key>
        <dict>
            <key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
            <array>
                <string>boot-args</string>
                <string>bluetoothHostControllerSwitchBehavior</string>
            </array>
        </dict>
        <key>LegacyEnable</key>
        <false/>
        <key>LegacySchema</key>
        <dict/>
    </dict>

But, in the config.plist of 0.5.9, the key Block is changed for Delete... this is correct??

May I write this on the 0.5.9 config.plist?

<key>NVRAM</key>
    <dict>
        <key>Add</key>
        <dict>
            <key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key>
            <dict>
                <key>UIScale</key>
                <data>AQ==</data>
                <key>DefaultBackgroundColor</key>
                <data>AAAAAA==</data>
            </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>bluetoothHostControllerSwitchBehavior</key>
                <string>always</string>
            </dict>
        </dict>
        <key>Delete</key>
        <dict>
            <key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key>
            <array>
                <string>UIScale</string>
                <string>DefaultBackgroundColor</string>
            </array>
            <key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
            <array>
                <string>boot-args</string>
                <string>bluetoothHostControllerSwitchBehavior</string>
            </array>
        </dict>
        <key>LegacyEnable</key>
        <false/>
        <key>LegacyOverwrite</key>
        <false/>
        <key>LegacySchema</key>
        <dict/>
        <key>WriteFlash</key>
        <false/>
    </dict>

 

[Charles.tech]

Hi again!!

I'm updating from OC 0.5.8 to 0.5.9 my own Mac Pro 5.1 (the other that tonight don't boot fine and solved is of my wife) and I have a doubt:

In the config.plist of 0.5.8 I have this:

<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>bluetoothHostControllerSwitchBehavior</key>
                <string>always</string>
            </dict>
        </dict>
        <key>Block</key>
        <dict>
            <key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
            <array>
                <string>boot-args</string>
                <string>bluetoothHostControllerSwitchBehavior</string>
            </array>
        </dict>
        <key>LegacyEnable</key>
        <false/>
        <key>LegacySchema</key>
        <dict/>
    </dict>

But, in the config.plist of 0.5.9, the key Block is changed for Delete... this is correct??

May I write this on the 0.5.9 config.plist?

<key>NVRAM</key>
    <dict>
        <key>Add</key>
        <dict>
            <key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key>
            <dict>
                <key>UIScale</key>
                <data>AQ==</data>
                <key>DefaultBackgroundColor</key>
                <data>AAAAAA==</data>
            </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>bluetoothHostControllerSwitchBehavior</key>
                <string>always</string>
            </dict>
        </dict>
        <key>Delete</key>
        <dict>
            <key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key>
            <array>
                <string>UIScale</string>
                <string>DefaultBackgroundColor</string>
            </array>
            <key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
            <array>
                <string>boot-args</string>
                <string>bluetoothHostControllerSwitchBehavior</string>
            </array>
        </dict>
        <key>LegacyEnable</key>
        <false/>
        <key>LegacyOverwrite</key>
        <false/>
        <key>LegacySchema</key>
        <dict/>
        <key>WriteFlash</key>
        <false/>
    </dict>

It is a change from previous version
I had a same problem as you
Try the vanilla config.plist for 0.5.9 first

 

[startergo]

I don't know how to start in safe mode with OpenCanopy. In VirtualBox it loads the repair.

View attachment 921145

It is in troubleshoot.

Windows startup settings - Microsoft Support

Learn how to change Windows startup settings, including enabling Safe Mode.

support.microsoft.com

[automerge]1591177302[/automerge]

I cannot boot from Windows into macOS anymore using bootcamp "restart your mac in macos"

Can you try pointing to the actual Mac drive rather then using "restart your mac in macos"
[automerge]1591177415[/automerge]

May I write this on the 0.5.9 config.plist?

Yes

 

[Norbert Mikołajczyk]

Can you try pointing to the actual Mac drive rather then using "restart your mac in macos"

Yes, there is one macOS drive visible (there should be visible 2 maOS drives?)
No matter what I select and how I restart it still boots back to windows.
Maybe I should reinstall the newest Bootcamp 6.1?

 

[donvito4ever]

@startergo Thanks!

 

[startergo]

Maybe I should reinstall the newest Bootcamp 6.1?

If you are on the older one you need to upgrade it.

May I write this on the 0.5.9 config.plist?

There are other differences apart from delete . You have to compare your config file against the updated one in the first post.

 

[h9826790]

Hi again!!

I'm updating from OC 0.5.8 to 0.5.9 my own Mac Pro 5.1 (the other that tonight don't boot fine and solved is of my wife) and I have a doubt:

In the config.plist of 0.5.8 I have this:

<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>bluetoothHostControllerSwitchBehavior</key>
                <string>always</string>
            </dict>
        </dict>
        <key>Block</key>
        <dict>
            <key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
            <array>
                <string>boot-args</string>
                <string>bluetoothHostControllerSwitchBehavior</string>
            </array>
        </dict>
        <key>LegacyEnable</key>
        <false/>
        <key>LegacySchema</key>
        <dict/>
    </dict>

But, in the config.plist of 0.5.9, the key Block is changed for Delete... this is correct??

May I write this on the 0.5.9 config.plist?

<key>NVRAM</key>
    <dict>
        <key>Add</key>
        <dict>
            <key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key>
            <dict>
                <key>UIScale</key>
                <data>AQ==</data>
                <key>DefaultBackgroundColor</key>
                <data>AAAAAA==</data>
            </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>bluetoothHostControllerSwitchBehavior</key>
                <string>always</string>
            </dict>
        </dict>
        <key>Delete</key>
        <dict>
            <key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key>
            <array>
                <string>UIScale</string>
                <string>DefaultBackgroundColor</string>
            </array>
            <key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
            <array>
                <string>boot-args</string>
                <string>bluetoothHostControllerSwitchBehavior</string>
            </array>
        </dict>
        <key>LegacyEnable</key>
        <false/>
        <key>LegacyOverwrite</key>
        <false/>
        <key>LegacySchema</key>
        <dict/>
        <key>WriteFlash</key>
        <false/>
    </dict>

That's one of the changes

And your code looks correct to me.

Anyway, there is a new useful tool in 0.5.9 which is the ConfigValidity utility.

If your config is wrong, it will warn you.

e.g. If I let it check the 0.5.8 config (despite that's 100% correct for 0.5.8, some entries are no longer valid in 0.5.9), it will warn me that Block is invalid in the NVRAM section (and something else).

But if I let it check a correct 0.5.9 config.plist will shows nothing, but just finish the check in 1ms.

 

[Norbert Mikołajczyk]

[automerge]1591177881[/automerge]

If you are on the older one you need to upgrade it.

I have the newest one installed.

 

[startergo]

[automerge]1591177881[/automerge]


I have the newest one installed.

Try gdisk:
"The program requires a hard disk identifier as an option. You can specify this in either of two forms. The first way is as a number followed by a colon, as in:
gdisk 0:
Disks are numbered starting from 0, so the preceding command launches gdisk on the first disk. The second way to specify a disk device is via a harder-to-remember name:
gdisk32 \\.\physicaldrive0"
option p. What is the result?