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

[mode11]

That is not what I meant:

KB Parallels: Unable to start Virtual Machine - EFI Boot

The virtual machine loads with some EFI Shell commands:

kb.parallels.com

you need vm.bios.efi=1 for UEFI boot.

Thanks startergo. I gave it a try but it didn't work - it just got me to the screen I mentioned before instantly, rather than via a light grey Parallels 'configuring' screen.

I initially followed the instructions in the link you provided, which used efi=0. But as you would expect, that gave me a Parallels BIOS screen that said 'no boot device' (I understand you meant the link as reference rather than instruction).

 

[h9826790]

Yes, I should remove ?

Why macOS Recovery (and also macOS Installer) isn't detected as a Recovery when booting from OpenCore menu ?

Yes, you should remove that setting in the config.pilst if you want to set SIP status in recovery partition.

Why should OpenCore detects an installer as recovery partition?

 

[mode11]

Something to consider if you installed Windows using the guide: The EFI partition does not contain the Windows bootx64.efi (to help prevent Windows from starting outside of OpenCore). I wonder if the virtual machine needs this file...

I did install Windows exactly as in post 1, so the bootx64 file was removed. That could well be the problem then. I wonder if anyone's come up with a workaround - Parallels is pretty widely used. I could make a VM, but one of the handy features of Parallels is being able to go into the Boot Camp partition and do stuff without needing to reboot.

 

[mode11]

I keep a small Mojave drive with a few basic utilities and ALWAYS a copy of the last 2 working OC Catalina's EFI partition's contents in folders on the Mojave desk top. If something goes wrong I can swiftly use the latest to replace any messed up configuration.

It has been well worth the small effort required on several occasions.

If you don't, please don't come asking for someone on this forum to provide a rescue.

Good advice; I've now backed up OC to my Mojave disk. What utilities do you find handy on Mojave?

 

[jackluke]

Yes, you should remove that setting in the config.pilst if you want to set SIP status in recovery partition.

Why should OpenCore detects an installer as recovery partition?

Using this "csr-active-config" on OpenCore 0.59 config.plist : ZwAAAA== (that is the standard El Capitan SIP disabled 0x67)

now from OpenCore menu targeting any macOS Recovery (BigSur included) or macOS Installer, I can use csrutil authenticated-root disable (or nvram csr-active-config=w%08%00%00 ) without any "This tool needs to be executed from the Recovery OS".

 

[h9826790]

Using this "csr-active-config" on OpenCore 0.59 config.plist : ZwAAAA== (that is the standard El Capitan SIP disabled 0x67)

now from OpenCore menu targeting any macOS Recovery (BigSur included) or macOS Installer, I can use csrutil authenticated-root disable (or nvram csr-active-config=w%08%00%00 ) without any "This tool needs to be executed from the Recovery OS".

If you disable SIP in Mojave Recovery Partition, 77000000 will be written into the NVRAM.

If you disable SSV in Big Sur Recovery Partition (by running csrutil authenticated-root disable in terminal). 10080000 will be written into the NVRAM (SIP still enabled)

If you disable SIP in Mojave Recovery Partition, then disable SSV in Big Sur Recovery Partition (MUST in this correct order). Then 77080000 will be written into the NVRAM.

So, if you want to keep both SIP and SSV disabled, 77080000 should be the key value for csr-active-config. Which is dwgAAA== in Base64

 

[cdf]

I did install Windows exactly as in post 1, so the bootx64 file was removed. That could well be the problem then. I wonder if anyone's come up with a workaround - Parallels is pretty widely used. I could make a VM, but one of the handy features of Parallels is being able to go into the Boot Camp partition and do stuff without needing to reboot.

You could always try with bootx64.efi:

1. Back up your BootROM. This is very important. In fact, everyone should have a back up.
2. Mount the EFI volume of your Windows disk (not the one where OpenCore is installed) and back up /Volumes/EFI/EFI/Microsoft.
3. Insert your Windows installer USB drive and check the trash for the EFI folder that you deleted at the end of the Windows installation. If the folder is there, restore it to your desktop and go to step 5.
4. If the folder is not there, you will have to repeat some of the steps that you did to install Windows. It might be a good idea to review that part of the guide before proceeding. When you are ready, boot into the Windows installer and enter the command prompt. Use diskpart to identify the drive letters of your USB, say D, and Windows disk, say C. Exit diskpart and enter "D:" (use the actual letter). Back up the efi folder of the installer with "ren efi efi.bak". Then, enter "cd sources" and create the boot files with "bcdboot C:\Windows /s D: /f uefi" (again, use the actual letters). Exit the installer and reboot into macOS. You'll find the desired folder on the USB drive. Copy it to your desktop. Delete /USB/EFI and rename efi.bak to efi. Remove the USB drive. Finally, mount the EFI volume of your Windows disk.
5. The last step is to copy the EFI folder into /Volumes/EFI. You should now have the folders "Microsoft" and "Boot" in /Volumes/EFI/EFI. The bootx64.efi should be in /Volumes/EFI/EFI/Boot.

 

[jackluke]

If you disable SIP in Mojave Recovery Partition, 77000000 will be written into the NVRAM.View attachment 932484

If you disable SSV in Big Sur Recovery Partition (by running csrutil authenticated-root disable in terminal). 10080000 will be written into the NVRAM (SIP still enabled)
View attachment 932485

If you disable SIP in Mojave Recovery Partition, then disable SSV in Big Sur Recovery Partition (MUST in this correct order). Then 77080000 will be written into the NVRAM.
View attachment 932486

So, if you want to keep both SIP and SSV disabled, 77080000 should be the key value for csr-active-config. Which is dwgAAA== in Base64View attachment 932487

Understood, but for me (I am using OpenCore 0.59) disabling SSV (that already includes SIP disabled) from opencore csr-active-config dwgAAA== doesn't worked, I need to do it from a BigSur Recovery (or its USB Installer) .

 

[startergo]

Understood, but for me (I am using OpenCore 0.59) disabling SSV (that already includes SIP disabled) from opencore csr-active-config dwgAAA== doesn't worked, I need to do it from a BigSur Recovery (or its USB Installer) .

<dict>
    <key>NVRAM</key>
    <dict>
        <key>Add</key>
        <dict>
            <key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
            <dict>
                <key>csr-active-config</key>
                <data>dwgAAA==</data>
            </dict>
        </dict>
        <key>Delete</key>
        <dict>
            <key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
            <array>
                <string>csr-active-config</string>
            </array>
        </dict>
    </dict>
</dict>

 

[jackluke]

Thanks @startergo just adding <string>csr-active-config</string> to the <key>Delete</key> worked.

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

            </dict>
            <key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
            <dict>
                <key>boot-args</key>
                <string>-no_compat_check amfi_get_out_of_my_way=1 keepsyms=1 debug=0x100 -lilubetaall</string>
                <key>csr-active-config</key>
                <data>dwgAAA==</data>
            </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>csr-active-config</string>
            </array>
        </dict>

 

[cdf]

Thanks @startergo just adding <string>csr-active-config</string> to the <key>Delete</key> worked.

Yes. It's important not to forget "Delete" if the entry has already been set in the NVRAM. Otherwise, the entry doesn't get changed.

 

[mode11]

You could always try with bootx64.efi:

1. Back up your BootROM. This is very important. In fact, everyone should have a back up.
2. Mount the EFI volume of your Windows disk (not the one where OpenCore is installed) and back up /Volumes/EFI/EFI/Microsoft.
3. Insert your Windows installer USB drive and check the trash for the EFI folder that you deleted at the end of the Windows installation. If the folder is there, restore it to your desktop and go to step 5.
4. If the folder is not there, you will have to repeat some of the steps that you did to install Windows. It might be a good idea to review that part of the guide before proceeding. When you are ready, boot into the Windows installer and enter the command prompt. Use diskpart to identify the drive letters of your USB, say D, and Windows disk, say C. Exit diskpart and enter "D:" (use the actual letter). Back up the efi folder of the installer with "ren efi efi.bak". Then, enter "cd sources" and create the boot files with "bcdboot C:\Windows /s D: /f uefi" (again, use the actual letters). Exit the installer and reboot into macOS. You'll find the desired folder on the USB drive. Copy it to your desktop. Delete /USB/EFI and rename efi.bak to efi. Remove the USB drive. Finally, mount the EFI volume of your Windows disk.
5. The last step is to copy the EFI folder into /Volumes/EFI. You should now have the folders "Microsoft" and "Boot" in /Volumes/EFI/EFI. The bootx64.efi should be in /Volumes/EFI/EFI/Boot.

That's brilliant, thanks. Luckily, I did still have the EFI folder in the trash of my memory stick, so that saves a job.

When you say back up your BootROM, do you mean with ROMTool? I've done this previously, but not since updating to 144.etc. I'll do it again. I seem to remember you have to disable SIP for this? Are there any complications booting into Recovery when using OpenCore (seem to remember reading something about that in this thread)?

 

[cdf]

That's brilliant, thanks. Luckily, I did still have the EFI folder in the trash of my memory stick, so that saves a job.

When you say back up your BootROM, do you mean with ROMTool? I've done this previously, but not since updating to 144.etc. I'll do it again. I seem to remember you have to disable SIP for this? Are there any complications booting into Recovery when using OpenCore (seem to remember reading something about that in this thread)?

Yes, with ROMTool. You'll have to disable SIP, but there shouldn't be any issues with booting into recovery (Catalina or Mojave) through OpenCore. You can press the space bar to reveal the recovery volumes in the boot picker.

 

[Dayo]

Yes. It's important not to forget "Delete" if the entry has already been set in the NVRAM. Otherwise, the entry doesn't get changed.

I'll actually say just "Delete" every item "Added" as it does no harm if it had not been previously set.

 

[m4f1050]

While talking about recovery/boot and extra Mojave... If I have Time Machine turned on.. can't I just boot from USB and do a recovery from time machine? I cloned my original Catalina to boot from it and re-install over my original then I erased the partition and turned on Time Machine (use a 2TB mechanical drive for this, my "Data" drive). Can I have OpenCore on a USB install drive? Like I used to do for Hackintosh when it wouldn't boot...
[automerge]1594397731[/automerge]

It's already like that. But just for fun I switched it towards the power connector and it had no effect. Any other clues?

Any ideas anybody?

 

[Alex-IN]

While talking about recovery/boot and extra Mojave... If I have Time Machine turned on.. can't I just boot from USB and do a recovery from time machine? I cloned my original Catalina to boot from it and re-install over my original then I erased the partition and turned on Time Machine (use a 2TB mechanical drive for this, my "Data" drive). Can I have OpenCore on a USB install drive? Like I used to do for Hackintosh when it wouldn't boot...
[automerge]1594397731[/automerge]


Any ideas anybody?

Throw me into PM his folder all EFI

 

[startergo]

While talking about recovery/boot and extra Mojave... If I have Time Machine turned on.. can't I just boot from USB and do a recovery from time machine? I cloned my original Catalina to boot from it and re-install over my original then I erased the partition and turned on Time Machine (use a 2TB mechanical drive for this, my "Data" drive). Can I have OpenCore on a USB install drive? Like I used to do for Hackintosh when it wouldn't boot...
[automerge]1594397731[/automerge]


Any ideas anybody?

what is your config file?

 

[Tiem]

I did install Windows exactly as in post 1, so the bootx64 file was removed. That could well be the problem then. I wonder if anyone's come up with a workaround - Parallels is pretty widely used. I could make a VM, but one of the handy features of Parallels is being able to go into the Boot Camp partition and do stuff without needing to reboot.

You don't need a workaround. You need to understand what it's doing and how to tailor it to what you want.

Windows will always remove anything in its way (remember we are setting up a EUFI install, not a regular one). EFI too. If an EFI is not found but one exists on another disk, it will use that and naturally overwrite the boot.efi located in /Boot, replacing it with the boot loader from Windows.

To correct this, if you have traditional SSDs, remove any that aren't for Windows. If you have an M.2, naturally removing them is a huge PITA, so reverting what Windows did is the quickest and best bet.

This means pointing Windows to another EFI (or creating it) and moving the boot loader in a safe way. Copying the files from the Windows install is NOT the recommended way (as I think most people in the thread are suggesting).

Use diskpart to set things up correctly. This post sets you up from the ground up: https://www.tenforums.com/installation-upgrade/52837-moving-recreating-efi-partition.html

From there it's just a matter of copying your OC EFI to the root EFI partition on the partition that houses macOS. Conceptually, you can have both off the same partition but it's not ideal (and obviously will cause collisions).

There is no need for a VM or to complicate this matter further. But having a clear method for those wanting to dual boot (or triple boot).

 

[6DecadesLater]

While talking about recovery/boot and extra Mojave... If I have Time Machine turned on.. can't I just boot from USB and do a recovery from time machine? I cloned my original Catalina to boot from it and re-install over my original then I erased the partition and turned on Time Machine (use a 2TB mechanical drive for this, my "Data" drive). Can I have OpenCore on a USB install drive? Like I used to do for Hackintosh when it wouldn't boot...
[automerge]1594397731[/automerge]


Any ideas anybody?

This the card I have https://www.amazon.com/gp/product/B06Y66K3XD/ref=ppx_yo_dt_b_asin_title_o03_s00?ie=UTF8&psc=1
I chose it as I have 3 monitors (Apple LED Cinema 27" and 2 @ 24"). I am using 3 DP to miniDP adapters to hook monitors to XFX. Had your problem until I set the switch. All good since then. What is your monitor and connection type?

 

[m4f1050]

This the card I have https://www.amazon.com/gp/product/B06Y66K3XD/ref=ppx_yo_dt_b_asin_title_o03_s00?ie=UTF8&psc=1
I chose it as I have 3 monitors (Apple LED Cinema 27" and 2 @ 24"). I am using 3 DP to miniDP adapters to hook monitors to XFX. Had your problem until I set the switch. All good since then. What is your monitor and connection type?

XFX GTS XXX Edition RX 580 4GB OC+ 1386Mhz DDR5 W/Backplate 3xDP HDMI DVI Graphic Cards RX-580P4DFD6

XFX GTS XXX Edition RX 580 4GB OC+ 1386Mhz DDR5 W/Backplate 3xDP HDMI DVI Graphic Cards RX-580P4DFD6

www.amazon.com

I have the 4GB version. Only 1 monitor via DVI running at 2650x1440. No issues with switching back and forth Compute/Gaming, so I don't think I have the same problem you had. It must be config.
[automerge]1594401588[/automerge]

While talking about recovery/boot and extra Mojave... If I have Time Machine turned on.. can't I just boot from USB and do a recovery from time machine? I cloned my original Catalina to boot from it and re-install over my original then I erased the partition and turned on Time Machine (use a 2TB mechanical drive for this, my "Data" drive). Can I have OpenCore on a USB install drive? Like I used to do for Hackintosh when it wouldn't boot...

Will this approach work?

 

[cdf]

You really shouldn't be doing this way. Use the command

bcdboot

from the Windows installer command prompt.

Copying the files from the Windows install is NOT the recommended way (as I think most people in the thread are suggesting).

I think there is a misunderstanding here: The EFI files that we are moving into place are not actually those of the installer, but rather those that we have properly created with bcdboot and temporarily stored on the USB drive (see the wiki).

 

[David403]

Good advice; I've now backed up OC to my Mojave disk. What utilities do you find handy on Mojave?

Hackintool
Chronosync
Etrecheck
Geekbench
iStat Menus
Lifespan
Onyx (but from Mojave you can only use it on Mojave - so I also keep the Catalina version)
Techtool Pro
(full) Xcode

Plus ... most of the utilites from https://eclecticlight.co/downloads/

 

[Tiem]

I think there is a misunderstanding here: The EFI files that we are moving into place are not actually those of the installer, but rather those that we have properly created with bcdboot and temporarily stored on the USB drive (see the wiki).

The logic behind it all is what my problem is. I don't understand why you guys feel the need to do all this song and dance and then when someone has an issue, you slap a bandaid on it like it's fixed.

Copying files over doesn't really change how Windows installer and boot loader behave. Moreover, you cannot create a Windows 10 2004 installer outside of Windows anymore given that one of the files is too big. There are workarounds but your guide will break for future versions.

Anyway not to cause a fuss, I'm gonna just shut up about it now.

 

[6DecadesLater]

View attachment 932611

XFX GTS XXX Edition RX 580 4GB OC+ 1386Mhz DDR5 W/Backplate 3xDP HDMI DVI Graphic Cards RX-580P4DFD6

XFX GTS XXX Edition RX 580 4GB OC+ 1386Mhz DDR5 W/Backplate 3xDP HDMI DVI Graphic Cards RX-580P4DFD6

www.amazon.com

I have the 4GB version. Only 1 monitor via DVI running at 2650x1440. No issues with switching back and forth Compute/Gaming, so I don't think I have the same problem you had. It must be config.
[automerge]1594401588[/automerge]


Will this approach work?

You don't say what monitor you have. Can you change settings on it? It may be a mismatch between the card and monitor. I didn't do anything special to the config.plist set up. Just followed the guide in the first post - including opencanopy, changing boot screen background color, disabling GOP, hardware acceleration, etc

 

[mode11]

Has anyone experienced any kernel panics with their Mac Pro whilst it's sleeping? I've been getting them quite frequently since installing Catalina. The Problem Report always seems to mention "Kernel Extensions in backtrace: com.apple.iokit.IOUSBMassStorageDriver(157.121.1)", with dependencies of com.apple.iokit.IOPCIFamily, com.apple.iokit.IOUSBHostFamily, com.apple.iokit.IOStorageFamily and com.apple.iokit.IOSCSIArchitectureModelFamily.

I've got a USB3 card, but no external drives are currently plugged in. My USB3 hub does have a card reader though (with nothing in it).

From Googling, I've seen quite a lot of reports of this with Catalina, including with 16" MBPs, with various suspected causes.