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

[tsialex]

1185570 0x121722 Certificate in DER format (x509 v3), header length: 4, sequence length: 986
1251106 0x131722 Certificate in DER format (x509 v3), header length: 4, sequence length: 986

You have two SecureBoot certificates/dbs/pks, each one inside one store of the NVRAM volume, not six.

Your NVRAM is probably already very fragmented, at the moment the best indicator of fragmentation is the quantity of MemoryConfig entries and the incorrect free space indicator of the NVRAM Volume. Most dumps of bricked Mac Pros have around 29 or 30 MemoryConfig entries, I'll send you a PM later with instructions on what you need to send me for a BootROM check.

 

[TECK]

The guide now includes instructions for enabling the graphical boot picker.

You're not copying the drivers, for certain keyboards/mouses? BTW, Magic Mouse 2 is not working, even with the drivers. A regular USB mouse works. Also, since users are already in terminal, I would give them an exact curl/unzip/cp set of instructions to avoid confusion.

 

[cdf]

You're not copying the drivers, for certain keyboards/mouses? BTW, Magic Mouse 2 is not working, even with the drivers. A regular USB mouse works. Also, since users are already in terminal, I would give them an exact curl/unzip/cp set of instructions to avoid confusion.

Magic Trackpad 2 is working on my end. Tested in version 0.5.9 without adding any drivers.

 

[tommy chen]

You're not copying the drivers, for certain keyboards/mouses? BTW, Magic Mouse 2 is not working, even with the drivers. A regular USB mouse works. Also, since users are already in terminal, I would give them an exact curl/unzip/cp set of instructions to avoid confusion.

magic mouse and magic mouse 2 works well on my cMPs at Ndk bootpicker (OC 0.5.8)

 

[h9826790]

You're not copying the drivers, for certain keyboards/mouses? BTW, Magic Mouse 2 is not working, even with the drivers. A regular USB mouse works. Also, since users are already in terminal, I would give them an exact curl/unzip/cp set of instructions to avoid confusion.

I also tested both MM1 and MM2 works in latest 0.5.9 beta without any additional driver (OpenCanopy).

 

[dataid]

You're not copying the drivers, for certain keyboards/mouses? BTW, Magic Mouse 2 is not working, even with the drivers. A regular USB mouse works. Also, since users are already in terminal, I would give them an exact curl/unzip/cp set of instructions to avoid confusion.

For versions of OpenCore 0.5.8 and 0.5.9 daily with OpenCanopy I have not needed any additional mouse or keyboard driver using Apple Magic Mouse 2 or Apple USB wired keyboard with MacPro 5,1. Same is also true for NDK v1.8 BootPicker with OpenCore 0.5.8. No terminal settings required.

*** Important Note *** The mouse cursor does not show by default for OpenCore 0.5.8 with OpenCanopy or for OpenCore with NDK v1.8 BootPicker. OpenCore 0.5.9 is not yet final so I do not know if this will be corrected in the release version of 0.5.9.
To get around this issue I do a mouse down/up and move the mouse, voila the mouse cursor appears.

 

[TECK]

Thank you guys for confirming the Magic Mouse 2 compatibility, I’m going to remove the drivers and see if it helps with my upgraded BT card.

 

[cdf]

The guide now includes some instructions for installing Windows 10. The procedure is based on the dism approach outlined in post #1,225. A novelty is the use of an ExFat EFI driver, which unfortunately never made it in the classic Mac Pro.

 

[startergo]

The guide now includes some instructions for installing Windows 10. The procedure is based on the dism approach outlined in post #1,225. A novelty is the use of an ExFat EFI driver, which unfortunately never made it in the classic Mac Pro.

Interesting. So the EFI folder with the windows boot manager will be on the NTFS drive?:
bcdboot C:\Windows /s D: /f uefi

 

[cdf]

Interesting. So the EFI folder with the windows boot manager will be on the NTFS drive?:
bcdboot C:\Windows /s D: /f uefi

Yes. That command creates the EFI folder on the USB drive. Later in macOS, the folder is moved to the EFI partition of the Windows disk.

 

[startergo]

Yes. That command creates the EFI folder on the USB drive. Later in macOS, the folder is moved to the EFI partition of the Windows disk.

That all can be done without rebooting OSX with virtual box. And there is no need for USB.
[automerge]1590777298[/automerge]
I will PM you.

 

[cdf]

That all can be done without rebooting OSX with virtual box. And there is no need for USB.

Well, yes. But the idea is to do all this without having to use VirtualBox...

 

[startergo]

Well, yes. But the idea is to do all this without having to use VirtualBox...

Got you. Maybe it is worth mentioning that it is a good idea deleting the Windows bootx64.efi so that no one accidentally boots to Windows without OpenCore. Then the boot loader can be specified inside the Microsoft folder.

 

[cdf]

Got you. Maybe it is worth mentioning that it is a good idea deleting the Windows bootx64.efi so that no one accidentally boots to Windows without OpenCore. Then the boot loader can be specified inside the Microsoft folder.

I've been debating this point. It's so nice to have OpenCore pick up the bootx64.efi automatically without any manual configuration! I've had this setup for a while now and never booted directly by mistake...

I do agree that there should be a word of caution regarding the presence of Windows UEFI in the cMP.

 

[startergo]

I've been debating this point. It's so nice to have OpenCore pick up the bootx64.efi automatically without any manual configuration! I've had this setup for a while now and never booted directly by mistake...

I do agree that there should be a word of caution regarding the presence of Windows UEFI in the cMP.

If someone removed OC for troubleshooting there is very high chance of booting to Windows.

 

[cdf]

If someone removed OC for troubleshooting there is very high chance of booting to Windows.

A Windows update could restore a previously deleted bootx64.efi. At the end of the day, users need to be informed, so that they can take the precautions they deem necessary.

 

[startergo]

A Windows update could restore a previously deleted bootx64.efi. At the end of the day, users need to be informed, so that they can take the precautions they deem necessary.

The safest approach if there is no OC is to remove the Windows drive until OC starts working again. Another approach specifically for the updates is to do the update in virtual box and later delete the Windows bootx64.efi before rebooting OSX.

 

[dataid]

Thank you guys for confirming the Magic Mouse 2 compatibility, I’m going to remove the drivers and see if it helps with my upgraded BT card.

*** Important Note *** The mouse cursor does not show by default for OpenCore 0.5.8 with OpenCanopy or for OpenCore with NDK v1.8 BootPicker. OpenCore 0.5.9 is not yet final so I do not know if this will be corrected in the release version of 0.5.9.
To get around this issue, after the OpenCanopy or NDK BootPicker screen appears I do a mouse down/up and move the mouse, voila the mouse cursor appears.
[automerge]1590811655[/automerge]
Graphical depiction of OpenCanopy settings for OpenCore 0.5.8 and 0.5.9 on MacPro 5,1 these correspond to settings in the Boot section of config.plist.

You can also see that in the Tools section of config.plist I have enabled OpenShell.efi to appear on the BootPicker screen as an option by unchecking HideAuxiliary (making it false) and adding OpenShell.efi to the Tools section of config.plist and checking (making true) Auxiliary and Enabled in config.plist. OpenShell is a nice tool for exploring the pre-boot environment. It is part of the UEFI standard.
For a manual of commands available with OpenShell go to the UEFI website.

 

[dataid]

Graphical depiction of OpenCore settings for playing the BootChime in OpenCore 0.5.8 and 0.5.9 on a MacPro 5,1. To enable to BootChime you must adjust settings in the Audio subsection of UEFI as shown and add to the Drivers subsection of UEFI, the driver AudioDxe.efi in the config.plist. There are two screenshots below showing the required settings.
The AudioDevice address corresponds to my stock MacPro 5,1 2010. Different Macs may have a different AudioDevice address, a different AudioCodec number and a different AudioOut number.

[automerge]1590813286[/automerge]
Attached are screenshots showing OpenCore 0.5.8 with NDK BootPicker v1.8
At this time I have found there is greater flexibility in NDK vs OpenCanopy for displaying different icons for operating systems and auxiliary tools.
Note the first screenshot is the default BootPicker screen.
Screenshot 2 is seen after pressing the spacebar which reveals the additional selections.
Screenshot 3 shows the auxiliary tool I have included in the UEFI drivers section OpenShell.efi, its appearance is controlled by HideAuxiliary in MISC | Boot | HideAuxilary (false). The NDK BootPicker icons were customized.

 

[dme881]

Updated to Catalina 10.15.5 (19F96). Now when the screen sleeps, they won't wake back up. Vega 64. Anyone have the same problem?

OC 0.5.8 and whateverGreen 1.3.9 (Both latest)

 

[cdf]

@dataid has your Mac lost its native boot chime?

 

[dataid]

@dataid has your Mac lost its native boot chime?

I believe my machine lost the native boot chime when using OpenCore; however, at times I had used a utility to turn off the Apple native boot chime while doing installs at night before using OpenCore. So when I started using OpenCore the possibility is that the boot chime was off and I attributed the absence of the chime to OpenCore working without its’ boot chime setting enabled.

What is your experience?
Does OpenCore start running after the native Apple boot chime?

 

[Dayo]

What is your experience?
Does OpenCore start running after the native Apple boot chime?

The boot chime settings in OpenCore are for the benefit of Hacks, the primary target users of OpenCore, which do not have native chimes and should not be set on a cMP.

 

[cdf]

What is your experience?
Does OpenCore start running after the native Apple boot chime?

Exactly. Also, because the chime respects the output settings in System Preferences, it is possible to mute it that way. And after an NVRAM reset, the chime always comes back.

 

[Norbert Mikołajczyk]

Hi guys, setting up the OpenCore.
What to do to make already installed windows 10 visible for opencore?
I see there is a tutorial how to install windows 10 with opencore, but what should I do if I have it already installed and working?
Where can I download needed files that I need to transfer from usb to efi folder?