Become a MacRumors Supporter for $25/year with no ads, private forums, and more!

Dayo

macrumors 65816
Original poster
Dec 21, 2018
1,018
481
This is a guide to using OpenCore and RefindPlus, to multiboot Classic MacPros (3,1 to 5,1) as well as equivalent Xserve (2,1 and 3,1). It involves booting Mac OS from one or more OpenCore instances chain-loaded from RefindPlus and booting other OS types directly from RefindPlus.

Due to significant automation introduced as from v062, it appears the package is now too large to attach to this post ... You can download it HERE

The guide is focused on configuring a RefindPlus/OpenCore chain-loading arrangement and comes with a working configuration of RefindPlus and OpenCore that is literally "Plug and Play".

NB: This is the only post that is required reading for implementing this setup

The RefindPlus/OpenCore setup created by MyBootMgr is benign and can be implemented or removed without changing any fundamentals and can therefore be safely tested. Just make sure it is implemented on a physical disk that does not hold your main OS, or that only contains data, as this allows you to disconnect the disk if required and still boot into your OS. This is always preferable for boot loaders.

TL; DR
Start at STAGE 1 - PRE INSTALLATION under the IMPLEMENTATION section and follow the steps one after the other to implement a RefindPlus/OpenCore chain-loading arrangement.​



  • The BootBlesser App
    • This is used to bless either RefindPlus or OpenCore so that they can handle boot actions
  • The ConfigFactory App
    • This uses input you provide to configure RefindPlus and OpenCore
  • The DeployConfig App
    • This migrates RefindPlus and OpenCore from the staging folder to the target EFI System Partition or HFS Volume
  • The EnterRecovery App
    • This reboots your Mac into Recovery Mode for you if required
  • The FetchSetup App
    • This fetches your deployed "EFI Folder" to your staging area for you to facilitate upgrading MyBootMgr
  • The ResetStartDisk App
    • This helps reset your computer to a default start disk if required
  • The SwitchRunMode App
    • This enables switching back and forth between Release Mode, optimised for day-to-day running, and Debug Mode, optimised for trouble shooting.
  • The TweakESP App
    • This is used to mount and unmount EFI System Partitions if required.
  • The UninstallMgr App
    • This is used to remove MyBootMgr and the boot utilities from your Mac.
  • The ValidateOC App
    • This is used to run some high level checks on OpenCore to help determine if it is properly activated.
  • The WrangleConfig Tool
    • This is used to apply arbitrary automated modifications to the generated setup.



MyBootMgr is made up of this guide and a set of Helper Apps to enable you setup and manage RefindPlus and OpenCore:

Due to significant automation introduced as from v062, it appears the package is now too large to attach to this post ... You can download it HERE

If you follow this guide step by step, word for word, implement recommended steps, avoid those not recommended, don't second guess it by implementing things not explicitly written, you will not have issues and will be able to easily restore your previous state if required.

MyBootMgr specific issues raised in this thread will be addressed. Other issues, such as those outlined following, should be directed to more appropriate locations.

For help on understanding the workings of Mac OS EFI Loading, compatible GPUs, installing/configuring any supported or unsupported OS, the intricacies of configuring/running RefindPlus and/or OpenCore beyond the configuration provided and such, please refer to, and seek help from, subject specific threads such as:
  • RefindPlus Specific Issues: https://github.com/dakanji/RefindPlus/issues
    • Documentation is provided in a Docs folder created when you install MyBootMgr ... Read it.
      • This is admittedly not RefindPlus specific but should cover 99% of configuration questions
    • Use the link to the GitHub BugTracker above to raise RefindPlus specific issues.
      • There is a template for basic information required for a proper consideration of your issue.
      • The GitHub BugTracker also permits proper tracking and correlation of confirmed issues.
    • RefindPlus Discussion and Questions: https://github.com/dakanji/RefindPlus/discussions
      • Use this for general RefindPlus related questions such as configuration issues.
    • You can try rEFInd for overlapping items: https://sourceforge.net/p/refind/discussion/general
      • Bear in mind that the rEFInd forum is not a RefindPlus one and frame your queries accordingly.
  • OpenCore Specific Issues: https://forums.macrumors.com/threads/2207814
    • Documentation is provided in a Docs folder created when you install MyBootMgr ... Read it.
      • OpenCore's documentation is admittedly a difficult read but you need to get familiar with it if you want to fiddle with the configuration provided by MyBootMgr.
    • VMM Spoofing for installing/updating Mac OS is available for all supported cMP Models including cMP3,1, "unflashed" cMP4,1 and cMP5,1 on Nehalem CPUs.
      • Virtually all the capability available to a cMP5,1 running BootROM 144.0.0.0 on a Westmere CPU is also available on all supported cMP Models (including cMP3,1) with the correct configuration settings as provided by the ConfigFactory App.
      • You do not need a Westmere CPU or to flash cMP 5,1 firmware on cMP4,1 to access all of OpenCore's capabilities and any shortfall in functionality would not be OpenCore related.
      • While you should upgrade your BootROM to 144.0.0.0 (if running a "flashed" cMP4,1 or a cMP5,1) to maximise compatibility, the ConfigFactory App will detect your BootROM version and automatically configure RefindPlus and OpenCore to fill in missing capabilities as needed.
    • You can use the DosDude Patcher to install and maintain unsupported Mac OS and currently, you can operate DosDude installations alongside OpenCore.
    • However, you can overwrite your DosDude patched Mac OS installation with a vanilla version after installing RefindPlus/OpenCore. (Recommended)
  • GPU Compatibility: https://forums.macrumors.com/threads/2174600
  • GPU Acceleration: https://forums.macrumors.com/threads/2180095
  • Mac OS Loading: https://forums.macrumors.com/posts/29306039
  • The various "Mac OS X on Unsupported Macs" threads such as:
  • General cMP Upgrade Info: https://blog.greggant.com/posts/2018/05/07/definitive-mac-pro-upgrade-guide.html
    • Outdated in some aspects as at Sep 2020
  • Installing Windows: https://forums.macrumors.com/threads/2250317
    • The guide in the OpenCore thread also includes instructions on installing Windows.
    • This is for UEFI Windows which is not recommended here but is a viable option if preferred.
  • Installing Linux: Try a web search as difficult to get one single resource due to platform fragmentation.
    • The guide in the OpenCore thread includes instructions on installing Ubuntu Linux.
* Most Importantly, READ THE GUIDE.
* If you face or anticipate any issues, READ THE GUIDE AGAIN


Even if not multi booting into different OS Types, this guide can be used to easily enable OpenCore on a Classic MacPro in a way that is useful to first timers or experienced users that want to test different OpenCore Instances.

This is achieved by first booting into RefindPlus and using this to either load OpenCore (for Mac OS) or other OS Types as while OpenCore is far more powerful and can provide such multi booting along with several other features, configuring RefindPlus is a lot easier and it is a lot more difficult to break things with RefindPlus.
  • You can easily load any operating system from RefindPlus
  • You can easily enable or disable SIP from RefindPlus
  • You can load Legacy Windows installations in addition to UEFI Windows
    • UEFI Windows is now the orthodox way of installing Windows but it comes with the risk of potentially damaging your cMP as it was not designed with multi-boot cMP setups in mind.
    • RefindPlus and OpenCore offer protection from this issue as long as you ensure that you never ever deliberately boot, or, inadvertently get booted into Windows from outside of either utility.
      • This can happen in many ways ... See HERE or HERE
    • Legacy Windows does not have this issue and it also does not have the issue of updates taking over your boot process (Boot Coups)
    • Legacy Windows implementations do not to have issues with updates consistently reportedly faced on UEFI Windows on each of the frequent updates.
  • You can manage multiple instances of OpenCore. For instance...
    • With Hardware Acceleration and Without (See HERE and HERE)
    • With VMM Spoofing and Without
    • OpenCore Release Version and Debug Version
    • Current OpenCore Version and Known Working Version for Recovery
    • Anything else that takes your fancy ... including a combination of the above
With this chain-loading arrangement, OpenCore would handle Mac OS booting and there can be multiple instances as mentioned. One path to Mac OS via RefindPlus should be maintained for recovery. You basically have all of the awesome power of OpenCore fully tamed by the simplicity of RefindPlus at your disposal.

This package includes one additional OpenCore instance in OC_ALT. You can add more instances by duplicating either of the provided OC or OC_ALT folders, renaming this folder and amending the OpenCore config file as you wish. Note however that the Helper Apps will only process the OC and OC_ALT folders.
  • MacPro3,1 to MacPro5,1 and Xserve3,1: This is written for MacPro3,1 to 5,1 as well as Xserve3,1. You can install on other units but these are not supported.
  • GPU: To get the Pre-Boot Configuration Screen AKA "Bootscreen", your GPU must fall into one of the following categories:
    • "Fully Compatible": GPUs that can load Mac OS and the Mac Pre-Boot Configuration Screen.
      • It does not matter whether the GPU uses GOP (Modern GPU) or UGA (Legacy GPU).
      • The capability to show the Pre-Boot Configuration Screen can be either from the factory or flashed afterwards.
      • GPUs flashed by MacVidCards, which are thus "Fully Compatible" on the surface, may in fact offer a poorer experience than if the GPU is left in a "Semi Compatible" state.
        • Examples of such flashed GPUs appear to disable AFPS drivers in the Mac's Early Boot Stage which may affect detection of some Mac OS Instances by boot loaders.
        • There is no need for such flashing as either one or both of RefindPlus and OpenCore can likely show Pre-Boot Configuration Screens with such otherwise "Semi Compatible" GPUs as they are.
    • "Semi Compatible": GPUs that can load Mac OS but not the Mac Pre-Boot Configuration Screen.
      • The GPU must be "GOP Capable" and GOP must be either "Usable" or "Fixable".
      • RefindPlus and OpenCore will both show Pre-Boot Configuration Screens when using GPUs with "Usable" GOP. This capability is avaliable on both utilities independent of the other.
        • "Usable" GOP in terms of Classic MacPros are actually GOP drivers that do not strictly conform to UEFI 2.x specifications.
        • This allows RefindPlus and OpenCore to activate them on Classic MacPros, which are actually EFI 1.x devices, without further action.
        • Most modern AMD GPU units come with "Usable" GOP while most modern Nvidia GPU units do not (They follow the UEFI 2.x specifications).
      • RefindPlus will show Pre-Boot Configuration Screens when using GPUs with "Fixable" GOP and OpenCore will also show such screens when it is chain-loaded from RefindPlus.
        • Modern Nvidia GPUs that are not branded "Mac Edition", as well as some variants of AMD GPUs, are fully UEFI 2.x compliant and as such, their GOP drivers need a "fix" to be activated on Classic MacPros.
        • RefindPlus can implement this fix on most such GPUs allowing Pre-Boot Configuration Screens on several GPUs where this was previously not available.
          • Every such GPU tested to date but likely there are some that cannot be fixed.
        • With this fix in place, Pre-Boot Configuration Screens will also be available in OpenCore when chain-loaded from RefindPlus.
        • You may need to upgrade to the lastest version of GOP for your GPU to enable RefindPlus apply this fix. Please refer to other online resources for details on this.
      • It is possible to to run RefindPlus/OpenCore without a Graphical Pre-Boot Screen with other Semi Compatible GPUs (Semi Compatible "UGA Only" units or "GOP Capable" units with "Unusable" and "Unfixable" GOP). Refer to the OTHER CONSIDERATIONS section for guidance on this.




This guide outlines things for two possible installation types, "ESP" and "HFS", which you decide based on your preferences.
  • ESP Type Installation
    • The EFI System Partition (ESP) is a hidden partition on your drive created when formatting the drive.
      • USB Sticks formatted as HFS+ (Mac OS Extended Journaled) also have EFI System Partitions that can be used in ESP Type installations. Note that these can be an order of magnitude slower to show the Pre-Boot Configuration Screen.
    • This partition is not something you create by yourself.
    • This package contains the TweakESP App which allows you to mount/unmount EFI System Partitions which are otherwise invisible. After mounting one, you will be able to see it in Finder.
    • You can only mount one at a time
  • HFS Type Installation (Not Recommended)
    • HFS Type installations refer to implementations on normal disk volumes which may be on a USB Stick or on a HD/SSD or other type of disk. This basically refers to normal folders/volumes that you can create yourself.
    • You cannot mount such with the TweakESP App.
    • Use HFS+ (Mac OS Extended Journaled) Volumes for HFS Type and not APFS.
    • Note that the debug version of OpenCore will not output debug logs with HFS Type implementations and that the debug version of RefindPlus will not store such logs on the HFS volumes but in the first ESP it finds.
Other Notes:
  • The /EFI/BOOT folder distributed is a RefindPlus folder.
    • As a result, the BOOTx64.efi file is a RefindPlus efi file and NOT the OpenCore efi file which has the same name.
    • The RefindPlus BOOTx64.efi file is modified from the upstream rEFInd release.
  • Try to make sure the package is not on the same physical disk as any operating system
    • This is because a last ditch recovery from an issue with an installed operating system is to disconnect the physical disk it is installed on but you will need to maintain access to this package.
    • The opposite, where you have issues with this package and need to boot into an operating system also applies.
  • UEFI Windows is not recommended ... Use Legacy Windows.
    • Both RefindPlus and OpenCore can protect your Mac from damage by UEFI Windows if configured correctly and the ConfigFactory App will configure both utilities to activate this protection.
    • That is, you can also boot into UEFI Windows directly from RefindPlus (v0.12.0.AN or later) without damaging your BootROM.
    • This protection can however fail in either of RefindPlus or OpenCore and you must ensure that you never boot into Windows, or get booted into Windows, knowingly or unknowingly, from outside RefindPlus or OpenCore if you insist on UEFI Windows.
    • Spare yourself problems on your Legacy Mac and stick with Legacy Windows.
    • You can find a guide to installing Legacy Windows on your Mac HERE
    • If you still wish to insist on UEFI Windows, ensure it is not installed on the disk containing your RefindPlus/OpenCore implementation.
  • OpenCanopy from OpenCore is not supported and is not distributed as there is no point having two graphical bootpickers.
    • You can theme RefindPlus by updating the images in the /EFI/BOOT/icons folder after installation.
    • You can set the OpenCore Text Bootpicker to only show up when specifically needed and to otherwise go directly to Mac OS. You can also set it so that it shows for a short period only before going to Mac OS.
    • If you do want to duplicate things and implement OpenCanopy anyway, please direct configuration or troubleshooting queries to the main OpenCore thread.
Looking to upgrade or uninstall MyBootMgr?
Refer to the OTHER CONSIDERATIONS section for instructions.



FOR INFORMATION ONLY ... NOT RECOMMENDED
  1. Install and Use RefindPlus without OpenCore
    • Download rEFInd from the rEFInd Website and install, following instructions provided there
    • Once done, replace the rEFInd efi file with one from MyBootMgr (BOOTx64.efi).
      • Ensure that you rename to match.
    • Also replace the default rEFInd configuration file with the /Users/Shared/MyBootMgr/EFI/BOOT/config.conf file to configure the additonal options provided.
    • For full compatibility, copy in the icons in /Users/Shared/MyBootMgr/EFI/BOOT/icons folder to the rEFInd icons folder.
    • Skip the rest of this guide and refer to the rEFInd project for configuration/operation guidance.
  2. Install and Use OpenCore without RefindPlus
    • Run the ConfigFactory App and answer the questions as required
    • Delete everything inside the /Users/Shared/MyBootMgr/EFI/BOOT folder
    • Get a copy of the BOOTx64.efi file from the same version of OpenCore and copy into the /Users/Shared/MyBootMgr/EFI/BOOT folder
    • Assume RefindPlus stands for OpenCore in the rest of instructions
    • Once done, please refer to the OpenCore Thread for configuration/operation guidance



  1. Get MyBootMgr
    • Download and mount the MyBootMgr dmg file and run MyBootMgrSetup
      • Due to significant automation introduced as from v062, it appears the package is now too large to attach to this post ... You can download it HERE
    • This will create a /Users/Shared/MyBootMgr folder for you
      • If this folder is already present, it will be backed up as MyBootMgr_BAK
        • If a MyBootMgr_BAK folder is already present in such cases, it will be overwritten
    • Within this folder will be a MyTools folder containing the Helper Apps that make up MyBootMgr
  2. SKIP THIS STEP IF ON MAC OS v10.10 (YOSEMITE) OR OLDER
    • Run the EnterRecovery App to boot your computer into Mac Recovery Mode.
      • The app will inform you if SIP is already disabled in which case you can move on to the next stage.
    • In the Mac Recovery Mode, run Terminal from the "Utilities" menu item and enter csrutil disable && reboot
    • Log in as normal once rebooted.
    • You should never need the EnterRecovery App on the same machine again and can use RefindPlus to enable or disable SIP once RefindPlus is installed.
  1. Run the ConfigFactory App and provide the required responses
    • This will build and configure both RefindPlus and OpenCore to your specifications
    • The configured files will be saved in /Users/Shared/MyBootMgr/EFI
    • You will need to specify where you want to implement your setup when running the app
      • Remember to avoid using a partition on the same physical disk as your startup drive, or, preferably, any OS installation. This is important if you ever need to reset things.
  2. Deploy RefindPlus and OpenCore
    • Run the DeployConfig App to deploy RefindPlus and OpenCore to your EFI System Partition or HFS Volume.
    • The app will offer to deploy to the location you designated with the ConfigFactory App.
      • You can select another location if you have changed your mind in the interim but you really should rerun the ConfigFactory App and change the setting there.
    • If you already have an EFI folder in the EFI System Partition or HFS Volume, it will be backed up as EFI_BAK
      • If an EFI_BAK folder is already present in such cases, it will be overwritten
  3. Test RefindPlus
    • Run the BootBlesser App, select RefindPlus and then, Soft Bless
      • You must be booted into Mac OS without using OpenCore to Soft Bless. That is, natively or directly through RefindPlus
      • Remember to select ESP Type or HFS Type to match your implementation mode. If you make a mistake and bless the wrong target or type, run the ResetStartDisk App
    • Reboot your machine and you should be booted into RefindPlus where you should be presented with two OpenCore Instances, your Mac installations and any other OS you have installed.
      • If running a Semi Compatible GPU without GOP or with "Unusable" and "Unfixable" GOP, and thus without a bootscreen, refer to the OTHER CONSIDERATIONS section for guidance on running RefindPlus under such conditions.
    • In the unlikely event of a failure to load, just reboot and you will be in your normal boot mode since only soft blessed and you can go back to fix things.
  4. Test OpenCore
    • Boot into Mac OS using one of the OpenCore instances provided in RefindPlus and run the ValidateOC App to get output to help determine whether OpenCore is loaded properly.
      • If running a Semi Compatible GPU without GOP or with "Unusable" and "Unfixable" GOP, and thus without a bootscreen, refer to the OTHER CONSIDERATIONS section for guidance on running OpenCore under such conditions.
    • In the unlikely case of a failure to load OpenCore, just reboot and you will be in your normal boot mode since only soft blessed and you can go back to fix things
    • If you have somehow messed things up, shut down, disconnect the physical disk, reset nvram and select a start disk once booted
  5. Observe and Verify Installation
    • Do a few reboots after soft blessing each time to make sure all is working as expected.
      • You may want to keep in this state for a couple of days
  6. Finalise Installation (When satisfied everything is working as it should)
    • Shut down your Mac then switch the power off at the socket
    • Wait for 5 seconds then switch the power back on at the socket
      • Disconnect any drives containing any non-Mac OS operating systems if present
    • Wait for 15 seconds then press the power button to restart
    • Immediately hold the "OPT", "CMD", "P" and "R" keys down together until you hear the fourth chime.
    • Release the keys and RefindPlus will be loaded.
    • Boot into Mac OS without using OpenCore. That is, natively or directly through RefindPlus
    • Run the SwitchRunMode App to switch from Debug to Release Mode
    • Run the BootBlesser App and Firm Bless RefindPlus.
    • Shut down and reconnect any drives previously disconnected
    • Power on boot into Mac OS using an OpenCore Instance
    • Select your Startup Disk in System Preferences and reboot using the "restart" option
  1. You can manually amend the configuration files produced by the ConfigFactory App if required but most typical options are already covered by the app. You can always rerun and redeploy if required.
    • Use the TweakESP App to mount your EFI (ESP Type Only) if you want to manually amend the configuration files. You can obviously directly edit such if in HFS Type.
    • IMPORTANT: Make sure the OpenCore LauncherOption config key is kept at Disabled.
      • This setting, to protect OpenCore against Boot Coups, where another boot process takes over the configured/expected boot setup, is not applicable in this chain-loading environment as MyBootMgr involves what would appear to an OpenCore installation with this flag set, to be a Boot Coup by RefindPlus.
      • If you do experience a Boot Coup against RefindPlus by Linux or UEFI Windows (Not an issue with Legacy Windows, which, like Mac OS, does not attempt Boot Coups), refer to the OTHER CONSIDERATIONS section of this guide for suggestions on reasserting control.
  2. Use the WrangleConfig Tool to automate amendments you find yourself making on each release of MyBootMgr.
    • For instance, if you like to use OpenCanopy which is not supported by MyBootMgr and find yourself adding this in on every update, you can script the implementation in the WrangleConfig Tool and set the ConfigFactory App up to run this automatically.
  3. OPTIONAL: Getting disks connected to PCIe slots to identify as internal disks
    • The ConfigFactory App will give you convenient options to use either Innie.kext or AHCI_3rdParty_SATA.kext to have such drives identify as internal drives. If these do not work, or you prefer a manual process, you can implement the steps below:
      • Rerun the ConfigFactory App and disable the kexts
      • Install Hackintool
      • Go to the PCIe tab in Hackintool
      • Click on the heading of the Subclass column so that the data is sorted by subclass
      • Look for SATA Controller and Mass Storage entries
      • Right click on each in turn and select Copy Device Path
      • Save each somewhere such as TextEdit.
        • You will have text like PciRoot(0x0)/Pci(0x1F,0x2)
      • Amend <key>DeviceProperties</key> (NB: The standalone top level instance and NOT the one under "ProtocolOverrides") in your installed /EFI/OC/config.plist and /EFI/OC_ALT/config.plist files as below then redeploy with the DeployConfig App:
XML:
<key>DeviceProperties</key>
<dict>
    <key>Add</key>
    <dict>
        <key>PciRootStuff_1</key>
        <dict>
            <key>built-in</key>
            <data>AA==</data>
        </dict>
        <key>PciRootStuff_2</key>
        <dict>
            <key>built-in</key>
            <data>AA==</data>
        </dict>

        ...

        <key>PciRootStuff_N</key>
        <dict>
            <key>built-in</key>
            <data>AA==</data>
        </dict>
    </dict>
    <key>Delete</key>
    <dict/>
</dict>
RefindPlus.jpg
  1. How do I remove MyBootMgr?
    • MyBootMgr will be removed on running the UninstallMgr App
    • On first run, the app will delete the deployed RefindPlus/OpenCore fileset, empty the trash and reboot your computer
    • After this reboot, running the app a second time will remove the staging folders such as /Users/Shared/MyBootMgr and contents including the UninstallMgr App itself
      • After this, go to System Preferences, select a default boot disk and restart from System Preferences
      • If you don't run the app a second time, the deployed files would have been deleted but the staging folder would remain for use later if you so wish.
      • If you run most of the other apps after the first run of the UninstallMgr App, the run count will be reset to zero.
  2. I am on Mac OS "ABC" ... How do I Upgrade to, or Install, Mac OS "XYZ"?
    • Such installations and upgrades are out of scope here and you should ask on a more appropriate thread.
    • You can however try the following (make a new thread or ask on a suitable thread for support):
      • Install MyBootMgr as outlined in this guide.
      • Boot into Mac OS via an OpenCore instance with VMM Spoofing active
      • Install desired Mac OS "XYZ"
        • Get a copy of the Mac OS "XYZ" installer by using the installinstallmacos.py script.
        • Run the following Terminal Command to download and run the script: mkdir -p /Users/Shared/MyBootMgr/InstallMacOS && cd /Users/Shared/MyBootMgr/InstallMacOS && curl -O -L https://raw.githubusercontent.com/munki/macadmin-scripts/main/installinstallmacos.py && sudo python installinstallmacos.py
        • Select your desired installer to have it downloaded to your /Users/Shared/MyBootMgr/InstallMacOS folder where the script will create a dmg file contaning the installer which you can mount.
        • Run the installer and follow prompts
  3. How do I boot using MyBootMgr without a Graphical Pre-Boot Screen?
    • In RefindPlus
      • The Default OpenCore Instance is always mapped to Keyboard Key '1' on start and pressing this key will load this. Similarly, the Alternate OpenCore Instance is always mapped to Keyboard Key '2'. Installed operating systems are mapped to Keyboard Keys '3,4,5 ... 8,9,0'.
        • If you have a USB Stick with a "Valid OS", including Mac OS Installers and DosDude1 or similar Patchers, this will come in at position '3' and displace the internal OS keys accordingly. Hence, when you need to boot into such, attach the USB Stick, restart your machine and press Keyboard Key '3'.
        • You may want to use Keyboard Key '3' (without USB attached) to boot into Mac OS directly from RefindPlus and access your debug log to check the keyboard mapping.
    • In OpenCore
      • Blind booting in OpenCore is trickier but your operating systems should be listed in alphabetical order mapped to Keyboard Keys from '1' if the HideAuxilliary key in the OpenCore Config file is set to Hide which is what MyBootMgr uses by default. You can infer what key to use accordingly.
      • Note however that if you have the ScanPolicy key in the OpenCore Config file set to 0, this alphabetical order may include one or more 'EFI' entries.
  4. How do I update MyBootMgr?
    • Run Step 1 of "STAGE 1: PRE INSTALLATION" which will create a /Users/Shared/MyBootMgr folder
    • Run the FetchSetup App to get your currently installed implementation of MyBootMgr
      • The app will create a /Users/Shared/MyBootMgrOld folder for you
      • If this folder is already present, it will be backed up as MyBootMgrOld_BAK
        • If a MyBootMgrOld_BAK folder is already present, it will be overwritten
      • Within this folder will be a subfolder containing your currently installed EFI folder
    • Bring in any Drivers/Kexts you have added to MyBootMgrOld outside the ConfigFactory App to /Users/Shared/MyBootMgr
    • Use FileMerge (Type name into Spotlight to find) to compare your MyBootMgrOld/OC/config.plist file with the newly distributed one in MyBootMgr/OC/config.plist and update the new one with key items from your old one if you have made changes outside of the ConfigFactory App.
      • Repeat for your OC_ALT folder.
        • Only if not preserving OC_ALT as a known working instance.
        • In such cases, overwrite the MyBootMgr/EFI/OC_ALT folder with your MyBootMgrOld/EFI/OC_ALT folder instead
      • Carry out equivalent for any other OC_XYZ folders you may have.
    • Carry out similar for your EFI/BOOT/custom.conf file if you have made manual amendments to the file
    • Run the DeployConfig App to deploy RefindPlus and OpenCore to your designated EFI System Partition or HFS Volume and reboot.
      • The app only deploys the MyBootMgr/EFI/OC, MyBootMgr/EFI/OC_ALT and MyBootMgr/EFI/BOOT folders and their contents. You will need to manually deploy any additional folders you may have.
    • Execute a triple NVRAM Reset (Optional Beneficial Step)
      • Shut down your Mac, wait for 5 seconds, then press the power button to restart.
      • Hold the "OPT", "CMD", "P" and "R" keys down together until you hear the fourth chime.
      • Boot into Mac OS without using OpenCore. That is, natively or directly through RefindPlus
      • Run the BootBlesser App and Firm Bless RefindPlus.
      • Reboot into Mac OS using an OpenCore Instance
      • Select your Startup Disk in System Preferences and reboot using the "restart" option
    • When satisfied everything is working as it should, run the SwitchRunMode App to switch from Debug to Release Mode
  5. How do I update RefindPlus?
    • You should only upgrade RefindPlus via MyBootMgr updates.
    • However, you can manually upgrade RefindPlus as follows:
      • Replace EFI/BOOT/BOOTx64.efi
      • Update EFI/BOOT/config.conf
      • Update EFI/BOOT/custom.conf
    • These steps can be automated with the WrangleConfig Tool if, for instance, MyBootMgr has stopped receiving updates
  6. How do I update OpenCore?
    • You should only upgrade OpenCore via MyBootMgr updates.
    • However, you can manually upgrade OpenCore as follows:
      • Typically, you need to update the following files as a minimum with OpenCore:
        • EFI/BOOT/BOOTx64.efi
        • EFI/OC/OpenCore.efi
        • EFI/OC/Drivers/OpenRuntime.efi
      • However, as we have swapped BOOTx64.efi for a RefindPlus file, you should only update the other two (as a minimum).
      • Apart from that, update config as needed
      • You may also want to refer to THIS GUIDE
        • Remember that BOOTx64.efi is modified in our implementation
    • These steps can be automated with the WrangleConfig Tool if, for instance, MyBootMgr has stopped receiving updates
  7. I installed/updated UEFI Windows or Linux and now it only boots into UEFI Windows or Linux
    • To recover from a Linux Boot Coup
      • Boot into Linux and follow the instructions HERE
    • To recover from a UEFI Windows Boot Coup
      • If you experience a Boot Coup by UEFI Windows, your NVRAM is likely to have been compromised and unless remediated, your Mac will be "bricked" in short order.
      • Shutdown your machine, create a new thread (No point posting to this thread) and ask for help.
  8. The RefindPlus boot screen flashes on and off a few times on boot
    • No idea why this happens but just wait until it settles.
    • Alternatively, power down using the power button, disconnect the power cable, wait for 15 Seconds, reconnect it, wait for 5 seconds, restart and immediately hold down the "Option", "Command", "P" and "R" keys until you hear the boot chime the fourth time. Release the keys and log in as normal.
      • Disable SIP by toggling the shield Icon in RefindPlus if required as it would have been re-enabled by this process.
  9. I am concerned about being unable to boot into an unsupported Mac OS version if the disk containing RefindPlus/OpenCore fails or is lost
    • Failsafe Option 1: Ensure that you maintain a supported Mac OS Version. If the disk with RefindPlus/OpenCore fails, simply boot into this and implement RefindPlus/OpenCore on another disk
    • Failsafe Option 2: Implement a duplicate of your setup on another disk. If the main one fails, the other will kick in automatically if you have an ESP Type implementation.
      • You may want to make it look different to your main implementation so that you know that the main one has failed whenever this appears. The easiest way is to go into custom.conf and implement a distinct Title Banner.
      • You don't need to update this fallback setup once it is implemented.
  10. How do I set things up for FileVault?
    • Activating FileVault is outside the scope of MyBootMgr.
    • It will however configure your setup to ensure that you can boot into FileVault encrypted volumes.
  11. RefindPlus works, but OpenCore is not loading when I select an OpenCore instance from RefindPlus
    • Bless OpenCore with the BootBlesser App to load OpenCore directly.
    • If OpenCore loads when you reboot, then RefindPlus is interfering with OpenCore.
      • Raise an issue on the RefindPlus GitHub Repo and follow the requirements of the issue template.
    • If you end up with the same result when you reboot, ask for help on the main OpenCore thread.
      • Attach your OpenCore debug log and config files
        • Attach the files and do not paste directly in your post.
      • OpenCore debug logs are stored in your selected ESP.
        • Use the TweakESP App to mount the ESP to get at them.
        • Logs are not available with HFS Type implementations.
  12. One or more drives do not show up when RefindPlus is loaded
    • This can happen when disks are not yet fully initiated when RefindPlus attempts to scan them
    • Press the "ESC" key to Rescan the disks
    • If you face this issue frequently, use the RefindPlus scan_delay config option to add a delay before scanning disks
  • MyBootMgr-057:
    • Initial version based on OpenCore v0.5.7
    • Incoporates HWAccel from @h9826790 (See HERE)
  • MyBootMgr-057a:
    • Updated RadeonBoost to v1.2.
  • MyBootMgr-057b:
    • Combined DriveLabel_Refind.scpt and DriveLabel_OpenCore.scpt into single DriveLabel.scpt file.
    • Updated OpenCore Icon in Refind.
  • MyBootMgr-057c:
    • Changed distributed config files to explicitly switch off VMM and eliminate one step in instructions
    • Fixed property label in distributed DefaultVolume.scpt file
  • MyBootMgr-057d:
    • Changed OpenCore ScanPolicy setting to 0 so as not to throw users without APFS off
    • Amended Refind config to show Legacy Windows
    • Added AHCI_3rdParty_SATA.kext to simplify making external SATA/PCIe drives internal on cMP3,1
    • Updated RadeonBoost to v1.3
  • MyBootMgr-057e:
    • Removed RadeonBoost
    • Fixed issue that meant the OpenCore instance in the /EFI/OC_ALT folder used the config file in the /EFI/OC folder. (I.E., both instances were the same)
  • MyBootMgr-058:
    • Updated for OpenCore v0.5.8
    • Updated Lilu to v1.4.4
    • Updated Whatevergreen to v1.3.9
    • Updated distributed BootBlesser App to v2.0 for compatibility with new Bootstrap efi
      • Breaks compatibility with OpenCore v0.5.7 and earlier
    • Updated distributed EFI_Util App to v1.1 for consistency with BootBlesser App
      • Maintains compatibility with older versions of OpenCore
    • Changed folder name for helper apps to myUtils to avoid confusion with OpenCore's Utilities folder
    • Added OpenCore's Docs folder
    • Changed OC_Alt folder name to OC_ALT for consistent all uppercase format in OpenCore EFI
    • Renamed default OpenCore instance in Refind to OpenCore as opposed to OpenCore Accel and the second OpenCore instance in Refind to OpenCore ALT as opposed to OpenCore Basic
      • This is to reflect that users may choose to vary installations on other parameters and not just acceleration
    • Added debug versions of OpenCore.efi for both OC and OC_ALT
    • Removed gxutil
  • MyBootMgr-058a:
    • Fixed invalid HaltLevel value
      • Incorrectly amended from v0.5.7 value
    • Added missing ResetSystem.efi file
    • Updated icons
  • MyBootMgr-059:
    • Updated OpenCore to v0.5.9
      • Fixed ConsoleAttributes key
      • Added CrScreenshotDxe.efi
    • Updated Lilu to v1.4.5
    • Updated Whatevergreen to v1.4.0
    • Updated Refind to v0.12.0
      • Updated config file
      • Updated icons
      • Updated banner
      • Optimised image sizes
  • MyBootMgr-059a:
    • Updated Refind to v0.12.0.AB
      • Extends bootscreen provision to cMP 5.1 Firmware (No longer limited to cMP 3,1)
        • Requires GPU with valid GOP
    • Updated BootBlesser to v1.2
      • v1.1 did not correctly detect volume specified in DiskLabel.scpt
  • MyBootMgr-060:
    • Updated OpenCore to v0.6.0
    • Updated Lilu to v1.4.6
    • Updated Whatevergreen to v1.4.1
    • Updated NVMeFix to v1.0.3
    • Updated Refind to v0.12.0.AC (Changelog)
  • MyBootMgr-060a:
    • Updates Refind to v0.12.0.AE (Changelog)
    • Updates Distributed OpenCore Config
      • Fixes "ThirdPartyDrives" Key (Reset to TRUE ... Thanks @osxfr33k)
      • Fixes "ProvideConsoleGop" key (Reset to TRUE)
      • Fixes "ReplaceTabWithSpace" key (Reset to TRUE)
    • Updates Distributed Refind Config
      • Fixes "csr_values" Token (Reset to 10 and 877)
  • MyBootMgr-060b:
    • Updates Refind to v0.12.0.AF (Changelog)
    • Updates Distributed OpenCore Config
      • Reinstated "agdpmod=pikera" to boot arguments for GPU Acceleration Config (Thanks @osxfr33k)
        • May benefit some non-Navi GPUs and does not appear to be detrimental to others.
  • MyBootMgr-060c:
  • MyBootMgr-061:
    • Updated OpenCore to v0.6.1
      • Removed misc unused drivers such as OpenCanopy as the text bootpicker, or better still, no bootpicker, is preferred in OpenCore with this setup since RefindPlus already provides a graphical bootpicker.
    • Updated Lilu to v1.4.7
    • Updated Whatevergreen to v1.4.2
    • Updated Refind to v0.12.0.AH (Changelog)
    • Updated BootBlesser to v2.1
      • Previous versions searched an invalid path for boot files on HFS Volumes and could not bless such.
  • MyBootMgr-062:
    • General
      • Largely automates installation and configuration of RefindPlus and OpenCore
    • OpenCore
      • Updated to v0.6.2
      • Updated Lilu to v1.4.8
      • Updated Whatevergreen to v1.4.3
      • Updated NVMeFix to v1.0.4
      • Reintroduces RadeonBoost as Optional Kext
    • RefindPlus
    • MyTools
      • BootBlesser: Updated to v3.0
      • ConfigFactory: New App (v1.0)
      • DeployConfig: New App (v1.0)
      • EnterRecovery: New App (v1.0)
      • SwitchRunMode: New App (v1.0)
      • ResetStartDisk: No Change
      • TweakESP: New App (v1.0)
        • Replaces EFI_Util (Retired)
      • UninstallMgr: New App (v1.0)
      • VerifyOC: New App (v1.0)
  • MyBootMgr-062a:
    • General
      • Fixes Setting Automation Bugs
      • Refer to v062 Release Log for Featureset
  • MyBootMgr-062b:
    • General
      • Disables the option for OpenCore to respect SIP settings from RefindPlus which, if activated, caused OpenCore to fail to load.
        • Recommended to update to this version if running v062 or v062a.
        • You can accept the option to reuse saved settings from those versions if offered when running v062b
  • MyBootMgr-062c:
    • General
      • Misc Improvements
  • MyBootMgr-062d:
    • General
      • Further Enhancement
  • MyBootMgr-062e:
    • General
      • Finetuned and Enhanced
  • MyBootMgr-062f:
    • General
      • Accomodates situations where only one disk and/or Mac OS instance is present when running the ConfigFactory App
  • MyBootMgr-063:
    • OpenCore
      • Updated to v0.6.3
      • Updated Lilu to v1.4.9
      • Updated Whatevergreen to v1.4.4
    • RefindPlus
  • MyBootMgr-064:
    • OpenCore
      • Updated to v0.6.4
      • Updated Lilu to v1.5.0
      • Updated Whatevergreen to v1.4.5
    • RefindPlus
  • MyBootMgr-064a:
    • General
      • Multiple Fixes and Enhancements
  • MyBootMgr-065:
    • OpenCore
      • Updated to v0.6.5
      • Updated NVMeFix to v1.0.5
      • Updated Whatevergreen to v1.4.6
    • RefindPlus
  • MyBootMgr-065a:
    • General
      • Enables DRM Streaming on Mac OS v11.0 (Big Sur)
    • OpenCore
      • Updated Lilu to v1.5.1 (Pre-Release)
      • Updated Whatevergreen to v1.4.7 (Pre-Release)
  • MyBootMgr-066:
    • OpenCore
      • Updated to v0.6.6
      • Updated Lilu to v1.5.1
      • Updated Whatevergreen to v1.4.7
      • Updated Innie to v1.3.0
      • Updated NightShiftEnabler to v1.1.0
    • RefindPlus
    • MyTools
      • WrangleConfig (New Tool)
  • MyBootMgr-066a:
    • OpenCore
      • Fixes multiple misconfigured keys
      • Limits Firmware Update Restrictions to only when VMM is off
  • MyBootMgr-066b:
    • OpenCore
      • Rolls Innie back to v1.2.1
      • Removes Deletion of NVRAM Firmware Flags and Mask in Big Sur
  • MyBootMgr-066c:
    • OpenCore
      • Sets WriteFlash to 'true'
      • Restores Deletion of NVRAM Firmware Flags and Mask in Big Sur if Required
  • MyBootMgr-066d:
    • OpenCore
      • Restores WriteFlash to 'false'
    • RefindPlus
  • MyBootMgr-066e
    • General
      • Fixes Misc Packaging Issues with v066d
  • MyBootMgr-066f
    • General
      • Misc Config Optimisation
      • Resolves some instances where Boot Loaders did not appear in RefindPlus
  • MyBootMgr-067:
    • OpenCore
      • Updated to v0.6.7
      • Updated Whatevergreen to v1.4.8
    • RefindPlus
      • Updated to v0.13.1.AA then, v0.13.1.AB (Changelog and Changelog)
      • Structure of RefindPlus files in EFI\Boot is changed:
        • Overrides folder has been removed
        • Overrides now go into a custom.conf file
    • WrangleConfig
      • Update paths to match changes to RefindPlus structure above as required
  • MyBootMgr-067a
    • General
      • Misc Optimisation and Improvements



  • MyBootMgr-068:
    • MyBootMgr
      • ConfigFactory now sets OpenCore up to prevent SMC updates in addition to preventing firmware updates
    • OpenCore
      • Updated to v0.6.8 (Changelog)
      • Updated Lilu to v1.5.2
      • Updated Whatevergreen to v1.4.9
      • Updated NVMeFix to v1.0.6
    • RefindPlus
  • MyBootMgr-068a:
    • OpenCore
      • Removed Acidanthera WIFI Patches (Not Ready)
    • RefindPlus
  • MyBootMgr-068b:
    • MyBootMgr
      • Adds support for XServe2,1 (Early 2008 XServe)
      • Now handles up to 100 separate disk ids with up to 100 partitions on each.
        • Up from 10 respectively.
    • OpenCore
      • Updates legacy audio patch
    • RefindPlus
 
Last edited:

Dayo

macrumors 65816
Original poster
Dec 21, 2018
1,018
481
why so complicated...
Detailed, yes, but complicated, No.

Several of the steps are optional, meaning you can skip them but better to use them, and several are with clear instructions to skip. You just need to follow a simple sequence of actions.

For instance, in Stage 1, Only Steps 1 & 2 (plus Step 5 if on Retina Display) are required for most on a cMP 3,1.
That's only three actions.

If you do have observations on unnecessary complications, I will be very happy to make amendments.
 
Last edited:
Comment

Dayo

macrumors 65816
Original poster
Dec 21, 2018
1,018
481
Start from the first item under "STAGE 1: PRE INSTALLATION", that is, "Download and copy the attached zip file to your /Users/Shared folder and unzip it there". Then work your way down each item in order.
 
Comment

papadj3

macrumors regular
Nov 23, 2018
113
11
Expert Dayo:
Is this possible for a cMP 5,1 dual processor? Can I follow the instructions as written? I am a real Newbie!!
I want to use OC (I am using 0.5.5 on my startup disk) and remind so I can boot into my legacy bootcamp SSD- Any help will be greatly appreciated!!
 
Comment

Dayo

macrumors 65816
Original poster
Dec 21, 2018
1,018
481
First off, I'm no expert and this is basically a Noob to Noob Guide. The Experts tend to leave things out of their guides as they imagine everyone knows certain things.

Anyway, this is probably not such a good idea for the cMP 5,1 ... unless you are actually an expert and can navigate the potential pitfalls.

Main issue is that Refind only shows Boot Screen on cMP 3,1 (Unless you have Apple EFI GPU I suppose)


RefindPlus now shows boot screen on all cMP models running GPUs with valid Usable or Fixable GOP
 
Last edited:
Comment

papadj3

macrumors regular
Nov 23, 2018
113
11
Thanks Anyway!
You are right-"The Experts tend to leave things out of their guides as they imagine everyone knows certain things."
If you come across a procedure for a cMP 5,1 please post on your thread!!
 
Comment

Dayo

macrumors 65816
Original poster
Dec 21, 2018
1,018
481
It will probably work on a CMP 5,1 running a GPU with Apple EFI but I haven't tested and can't say for certain.

It works on a cMP 3,1 to 5,1 running a GPU with valid Usable or Fixable GOP.
 
Last edited:
Comment

George Deley

macrumors newbie
Apr 10, 2020
5
0
Detailed, yes, but complicated, No.

Several of the steps are optional, meaning you can skip them but better to use them, and several are with clear instructions to skip. You just need to follow a simple sequence of actions.

For instance, in Stage 1, Only Steps 1 & 2 (plus Step 5 if on Retina Display) are required for most on a cMP 3,1.
That's only three actions.

If you do have observations on unnecessary complications, I will be very happy to make amendments.

Do you know if I can boot from a PCIe nmve drive using this method?
 
Comment

Dayo

macrumors 65816
Original poster
Dec 21, 2018
1,018
481
*********************************
June 2020 Update
While the attached script probably still works, changes to OpenCore might have broken it, or will break it, at some point.

myOC.tool is what I actually use and keep up to date. It has a lot of params but running it without any params will fetch and build OC from the current codebase.

Pass a specific released version number to get a build of that version. (Example: myOC.tool 0 0.5.9 to build v0.5.9). Note the first param "0" before the version number.

To build v0.5.9 patched to run from an "OC_XYZ" folder, run myOC.tool 0 0.5.9 XYZ.
To do the same for the current codebase on github, run myOC.tool 0 HEAD XYZ
*********************************

So turns out the two OpenCore instances in releases up to myBootMgr-057d were simply running the same thing as they picked the same config file since OpenCore.efi is hard coded to load a config file from the /EFI/OC folder.

myBootMgr-057e onwards comes with a patched version of OpenCore.efi in the /EFI/OC_ALT folder. The patch is to make it pick up the config.plist file in the same folder.

If you do not want to run a patched file by a third party, you can do the patching yourself and build OpenCore. You need to have Apple Developer Tools installed.

This specific patch is no longer needed as of OpenCore 0.6.4.

This guide is for OpenCore 0.5.7 but will apply for any other version.

It can also be used to build OpenCore versions from the repo before release by the devs. Just get the current source from the front page and skip the patching bit. Zip packages will be in the ZipPkg folder. If you need a NOOPT version, pass "NOOPT" as a parameter to the script.

To patch for myBootMGR...
  • Go to the developer's Github Releases Page and select an archive file (zip or tar.gz) of the source code of the release you want to patch.

SourceCode.jpg


  • Move the downloaded archive file to your Desktop
    • Unpack the archive file
    • Rename the folder as "AltOpenCore"
  • Do a search of your ~/Desktop/AltOpenCore folder for \\OC and open any files found in your fav text editor. TextEdit will do.
    • Change all instances of L"EFI\\OC to L"EFI\\OC_ALT
      • NB: Do not add a " to the ends of the search or replacement strings
  • Download and unzip the attached MakeAltOC.zip file
    • You can open the MakeAltOC.tool file in your fav text editor to examine the script (Bash)
  • Open a Terminal window and type "chmod +x", add a space in front of this, drag the MakeAltOC.tool file onto Terminal and press "Enter" to make the file executable
  • Drag the file onto Terminal again and press "Enter" to build your patched OpenCore
  • Once the build is complete, go into ~/Desktop/AltOpenCore/Binaries
    • Select the package type you want: DEBUG or RELEASE.
    • Copy the OpenCore.efi file from here into your /Users/shared/myBootMgr/EFI/OC_ALT folder and overwrite the distributed version with your self compiled version
  • Deploy
NOTE
To build v0.5.9, find and replace macbuild.tool with build_oc.tool in the attached script.
 

Attachments

  • MakeAltOC-5.zip
    1.3 KB · Views: 216
Last edited:
Comment

Dayo

macrumors 65816
Original poster
Dec 21, 2018
1,018
481
Do you know if I can boot from a PCIe nmve drive using this method?
OpenCore and RefindPlus can boot stuff on NMVe drives if setup to do so but that is not the subject of this thread.
 
Last edited:
Comment

Dreamus911

macrumors newbie
Apr 29, 2020
2
0
Hi Dayo. Thank you very much for the detailed walkthrough. I can confirm that I managed to get Refind and OC working on my MacPro 3,1 with Asus Dual OC Radeon RX580 and Mac OS Mojave using DosDude1's install. However, the only issue I encountered was that when booting using both OC instances I got graphical glitches in some games, that were resolved on removing RadeonBoost.kext. I assume you had this issue too, so removed it from the latest release? What is the function of the RadeonBoost.kext?

The other issue I noticed, is that even if you change the SIP preferences in Refind, when booting into DosDude's Mojave SIP is always disabled. Is there a way to turn it back on, or does it always have to be disabled for DosDude's patching to work?

Thanks again.
 
Comment

Dayo

macrumors 65816
Original poster
Dec 21, 2018
1,018
481
Hi.

I run a cMP 3,1 with Dosdude Patched Mojave as well.

Dosdude patch always disables SIP. Can't recollect the details why but I think it is to allow the various unsigned kexts to work.

Basically most likely a lowest common denominator setting to allow a one click installation setup.

RadeonBoost is supposed to help Radeon GPUs. I use it but decided to remove from this distribution as it was making things a bit too opinionated.

Better to let people discover and decide whether they want it or not themselves. Many might not even use Radeons.

I.E., was not removed because of issues found.

It is not critical so if not working for you, you can just remove it or set up one instance of OC not to have it.
 
Comment

byally

macrumors newbie
May 20, 2019
3
0
Please mention that Refind bootscreen is NOT working on cmp 4&5.1! OpenCore only. Otherwise your guide is very useful!
 
Comment

Dayo

macrumors 65816
Original poster
Dec 21, 2018
1,018
481
Thanks for the feedback. If you read the "Notes" section near the beginning, you would find this is already stated as being the case if you don't have a GPU with APPLE EFI.

RefindPlus now shows boot screen on all cMP models running GPUs with
valid Usable or Fixable GOP.
 
Last edited:
  • Like
Reactions: byally
Comment

byally

macrumors newbie
May 20, 2019
3
0
Thanks for the feedback. If you read the "Notes" section near the beginning, you would find this is already stated as being the case if you don't have a GPU with APPLE EFI.

Yes, now I noticed. Just didn't understand that while reading for the first time.

By the way, do you know how can I install Windows 10 in UEFI mode, to boot it from OpenCore? Some simple detailed guide, like this one? I had MBR installation of Windows 10 on the separate SSD, I used command mbr2gpt, converted the disk, and now when I try to boot Windows from OpenCome it boots, but results in error no bootable drive; what is interesting that I can boot in safe mode. And none of recovery options help. So I thought better I reinstall Windows 10.
 
Comment

Dayo

macrumors 65816
Original poster
Dec 21, 2018
1,018
481
By the way, do you know how can I install Windows 10 in UEFI mode, to boot it from OpenCore?
If you refer to the same "Notes" section, you will find information on installing Windows which would answer your question.

I had MBR installation of Windows 10 on the separate SSD, I used command mbr2gpt, converted the disk, and now when I try to boot Windows from OpenCore it boots, but results in error no bootable drive
OpenCore does not support Legacy Windows. It could be that the conversion did not take.
 
  • Like
Reactions: byally
Comment

startergo

macrumors 68040
Sep 20, 2018
3,266
1,401
try to boot Windows from OpenCome it boots, but results in error no bootable drive; what is interesting that I can boot in safe mode.
You may need to re-examine the BCD store inside the ESP partition and make sure it points to the correct partition. You can use bootice:
 
  • Like
Reactions: byally
Comment

joevt

macrumors 68030
Jun 21, 2012
2,942
1,322
To have multiple copies of the same boot loader, I would put them into different partitions. That way you don't need a patch like OC_ALT. A FAT partition is required for writing log files or other files but normally, I use an HFS+ partition because a long time ago when I tried FAT, there was a 30 second delay in startup of the boot loader (using rEFIt or rEFInd). I haven't tried recently though but MacPro3,1 firmware hasn't changed since then so I don't expect a difference. Maybe boot loader from EFI folder doesn't have the 30 second delay - I forget the actual situation.
 
Comment

startergo

macrumors 68040
Sep 20, 2018
3,266
1,401
To have multiple copies of the same boot loader, I would put them into different partitions. That way you don't need a patch like OC_ALT. A FAT partition is required for writing log files or other files but normally, I use an HFS+ partition because a long time ago when I tried FAT, there was a 30 second delay in startup of the boot loader (using rEFIt or rEFInd). I haven't tried recently though but MacPro3,1 firmware hasn't changed since then so I don't expect a difference. Maybe boot loader from EFI folder doesn't have the 30 second delay - I forget the actual situation.
I put my OC on an HFS+ partition in EFI folder but the log file is not written. Maybe any HFS.efi will do loaded during boot?
 
Comment

joevt

macrumors 68030
Jun 21, 2012
2,942
1,322
I put my OC on an HFS+ partition in EFI folder but the log file is not written. Maybe any HFS.efi will do loaded during boot?
Do any EFI file system drivers support writing, other than the default FAT driver? I don't know if I'd want to load a third party HFS EFI driver to support writing. I guess it would be nice to have OpenCore or Clover be able to write to HFS partition for their logs. The other option is to patch them so they write logs to a specific folder in an EFI or FAT partition so that you can tell which boot loader created the log.
 
Comment

Dayo

macrumors 65816
Original poster
Dec 21, 2018
1,018
481
To have multiple copies of the same boot loader, I would put them into different partitions. That way you don't need a patch like OC_ALT.
That's an option and I had such for a while but in the case of chain loading from Refind which is the aim here, such partitions must be "USB" (HFS+) Volumes unless possible to point the Refind config to another EFI which I have not been able to figure out.

In any case, I later decided I preferred to have all my boot stuff in one location which this gives.

A FAT partition is required for writing log files or other files but normally, I use an HFS+ partition because a long time ago when I tried FAT, there was a 30 second delay in startup of the boot loader (using rEFIt or rEFInd). I haven't tried recently though but MacPro3,1 firmware hasn't changed since then so I don't expect a difference. Maybe boot loader from EFI folder doesn't have the 30 second delay - I forget the actual situation.
The 30 second thing doesn't seem to affect me on EFI (mostly). I do have instances where it happens and I have noticed that when this is the case, a drive I have in a PCIe slot does not mount. Immediately rebooting from Refind or OpenCore (I requested the option to reboot from OpenCore that was added in v0.5.8) solves this.

It's not the typical Refind 30 Second thing I suppose as the reboot cures it.
 
Comment

ryderpat

macrumors newbie
Sep 14, 2015
18
0

i try this tutorial on my 3.1 dual Quad-core Xeon Harpertown..
is that work...??
 
Last edited:
Comment
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.