MP 1,1-5,1 RefindPlus|OpenCore by MyBootMgr

[MacNB2]

Here is my config file

The key to getting h/w acceleration is spoofing the BoardID of either iMacPro1,1 or MacPro7,1.

Your config file does not contain that spoof.
You need BoardProduct = Mac-7BA5B2D9E42DDD94 (for iMacPro1,1):

 

[kirreip]

It is working now. I had that line on the wrong place in my config file... 🙈
But thanks for helping. Everything is now up and running.

 

[Farravi]

Edit : had an error and have attached the debug log below recommended by the prompt.

I think i may have to start over again.

I reinstalled the Mojave via recovery but it wasn’t a fresh install. Any ideas how to delete it all and reinstall Mojave.

 

[Dayo]

It is working now.

ConfigFactory sets up multiple instances with different configurations by default and it was odd when you said GPU Acceleration was not working. I asked for the ConfigFactory debug log to verify what had been set up but you did not provide this.

It seems you chose a configuration, OC_ALT, that does not include GPU Acceleration as it is targeted mainly at updates. Anyway, thanks to the feedback you got, you have been able to switch this on.

Not clear why you haven't just picked the default instance which has GPU Acceleration switched on but you have now activated the acceleration on an instance with VMM switched on and you will want to switch this off as not best for day-to-day use. To do this, clear the "Cpuid1Data" and "Cpuid1Mask" entries and also remove the "-revsbvmm" boot argument

I reinstalled the Mojave via recovery but it wasn’t a fresh install.

Not sure what is going on in your case, but I gave step by step instructions about a week ago that you should just follow and be done with it.

This did not include anything about reinstalling Mac OS as whether your installation is fresh or not has nothing to do with the basic outcomes ... certainly not with ConfigFactory. Regardless, if you have decided you need to reinstall, best ask about that on an appropriate thread or create a new one.

 

[Farravi]

Not sure what is going on in your case, but I gave step by step instructions about a week ago that you should just follow and be done with it.

That is exactly what I did. Step by step.

This did not include anything about reinstalling Mac OS as whether your installation is fresh or not has nothing to do with the basic outcomes ... certainly not with ConfigFactory. Regardless, if you have decided you need to reinstall, best ask about that on an appropriate thread or create a new one.

I included the debug list on Sunday and then after tried a fresh install of Mojave.

 

[Dayo]

I see an edit with the log now. Must have been added after the page turned over ... original post was on Saturday

That is exactly what I did. Step by step.

Lost on the multiple edits in that post. Follow the steps again exactly as written.

Before implementing Steps 6 & 7, you should have been able to boot into Mojave without using OpenCore or anything else.

There is no point reinstalling Mojave. It has nothing to do with anything going on and not sure what is getting messed up in the process. I mentioned calming down before. Don't just try this or that option/method at every road block. Take things step by step.

You need to get to the point where you are able to boot into Mojave natively. This is the most important basic step that needs to be in place first. Everything else comes after this.

 

[kirreip]

ConfigFactory sets up multiple instances with different configurations by default and it was odd when you said GPU Acceleration was not working. I asked for the ConfigFactory debug log to verify what had been set up but you did not provide this.

It seems you chose a configuration, OC_ALT, that does not include GPU Acceleration as it is targeted mainly at updates. Anyway, thanks to the feedback you got, you have been able to switch this on.

Not clear why you haven't just picked the default instance which has GPU Acceleration switched on but you have now activated the acceleration on an instance with VMM switched on and you will want to switch this off as not best for day-to-day use. To do this, clear the "Cpuid1Data" and "Cpuid1Mask" entries and also remove the "-revsbvmm" boot argument

I have chosen to go with OC_ALT because OC always booted into recovery mode (don‘t know why). I wanted to update to 11.6.1 anyway and OC_ALT worked fine, so… When I was done, I edited the config file (as you recommend) after reading and according to the first post of the opencore thread. The only thing that did not work was GPU acceleration. This, because I edited the wrong entry.
Now it works.

 

[Dayo]

OC always booted into recovery mode (don‘t know why).

Would have been possible to tell if the debug log had been provided.
Anyway, glad you are happy with how things are.

 

[zzzippp]

Hello @Dayo - I am a mid 2010 Mac Pro 5,1 owner who has been booting into MacOS 'Mojave' via RefindPlus on it for many months now, and am now looking to start using MacOS 'Big Sur' for work-related application compatibility.

Since I am familiar and comfortable with rEFInd/RefindPlus, I have decided to try your comprehensive solution in order to chain load OpenCore to gain MacOS 'Big Sur' boot ability. I am using MyBootMgr 0.7.5b.

I first read through and understood all the information and instructions given in post 1 of this thread, to the best of my ability, and then at the end of Stage 2, Step 1, after providing all my responses in the ConfigFactory app, upon building it gave me a dialog with a build error at BuildStep: 52. I am wondering if you could graciously help me with this!

I am attaching the ConfigFactory DebugLog as instructed (with extension changed to ".txt" to allow uploading to the MacRumors Forums), and if it helps here is my log of all of my responses in the Config Factory app:

Spoiler: Log of ConfigFactory dialogs & responses

Yes <- Would you like to use ConfigFactory Defaults for your Mid 2010 Mac Pro where Possible?
No <- Are you running any 'DosDude' or similar patched Mac OS instances?
No <- Are you running any cards or modules providing WiFi functionality in your Mid 2010 Mac Pro?
No <- Are you running any FileVault encrypted Mac OS Volumes on your Mid 2010 Mac Pro?
No <- Are you running any Mac OS instances on your Mid 2010 Mac Pro from HFS+ format volumes?
Yes <- Are you running or intend to soon install Mac OS 'Big Sur' on your Mid 2010 Mac Pro?

Notes on Mac OS 11.x (and later) for your Mac:
• Potential delta and other update issues
- Use 'OpenCore (Updates)' instance for updates
• Potential boot issues with built-in USB ports.
- Consider USB 2.0 hub or PCIe USB controller

Yes <- Are you running or intend to soon install Mac OS 'Monterey' on your Mid 2010 Mac Pro?
Yes <- Are you running or intend to soon install any Linux flavour on your Mid 2010 Mac Pro?
Yes <- Are you running or intend to soon install Microsoft Windows on your Mid 2010 Mac Pro?
Yes <- Have you implemented or intend to implement UEFI Windows on your Mid 2010 Mac Pro?

CAUTION:
- UEFI Windows can damage your Legacy Mac
- Legacy Windows works best for Legacy Macs

No <- Are you using a 'Retina' or any other HiDPI Monitor for the boot screen on your Mid 2010 Mac Pro?
Yes <- Have you connected or intend to soon connect more than one monitor to your Mid 2010 Mac Pro?

Could not directly make drives connected to PCIe Slots in your Mid 2010 Mac Pro identify as internal.
No <- Would you like to use 'Innie' to make such drives identify as internal?
NOTE - The version of 'Innie' bundled with ConfigFactory may not function when running Mac OS 11.x (Big Sur) or newer.

Nvidia Kepler GPU support was dropped in Mac OS 12.x
- Consider switching to an AMD GPU model
- Consider applying Kepler BaseSystem Patches
* See MyBootMgr 'Docs' folder for details

No <- Would you like to enable Thunderbolt 3 support in OpenCore?
Yes <- Would you like to allow booting operating systems on external drives via OpenCore?
No <- Would you like to include external FireWire drives?
NB: This may compromise system integrity
Yes <- Would you like to always automatically run WrangleConfig after ConfigFactory?

SELECT FALLBACK Mac OS VOLUME
This should be a Mac OS volume that you will like to boot to if you need to reset things.
This information will be used by some of the bundled apps to locate the volume automatically.
You can override the detected disks or volumes the using MyBootMgr's Helper Tools.

<Selected working clone of bootable Mac OS Mojave system located on SATA SSD in Bay 2>

SELECT EITHER ONE OF:
• For HFS Type: The volume you wish to install to.
• For ESP Type: Any volume on a physical disk whose EFI System Partition (ESP) you wish to install to.
- For example, select any volume on the volume on the disk in Bay 3 to install on the ESP of that disk
This information will be used by some of the bundled apps to locate the disk automatically.
You can override the found disks or volumes when using the Helper Tools.
Select a HFS+ volume for full compatibility/automation as the ESP of disks containing HFS+ volumes can be detected reliably as opposed to APFS, RAID, or Fusion drives.

<Selected working bootable Mac OS Mojave system located on "external" NVMe SSD installed on PCIe host controller, where my working RefindPlus set up is installed on the ESP volume, named "EFI">

<Name of NVMe SSD> does not appear to be in HFS+ format
While RefindPlus and OpenCode will work as normal on any compatible volume format, HFS+ volumes allow for the full automation of various MyBootMgr apps.
No <- Would you like to select an HFS+ volume instead?

<ConfigFactory Specification Completed>

After building, I saw this dialog:

Build Error at BuildStep: 52
Please report this issue on the MyBootMgr Support Thread at www.MacRumors.com and attach a ConfigFactory debug log to your post
You will find the 'DebugLog_ConfigFactory.log' file for this run saved under /Users/Shared/MyBootMgr
NOTES
- The 'DebugLog_ConfigFactory.log' file will be deleted on subsequent runs

There is abbreviated information about my particular MacPro set up, but here is more detailed information that may help:

• The system is a mid-2010 Mac Pro 5,1 with dual quad-core Westmere E5620 processor
• I have replaced the stock ATI Radeon GPU with a non-Mac-flashed NVIDIA GTX 760 card, which is Kepler-based, and have RefindPlus configured so that I can see the RefindPlus boot-selection/utilities screen when I start/reboot my Mac Pro
• Up to now I have been dual-booting using RefindPlus into:
  • MacOS 10.14.6 'Mojave' and
  • Windows 10 - UEFI install (and yes, with very helpful information from you on another MacRumors thread elsewhere, I am well aware of the potential risks)
  • NOTE: The two systems are installed on separate NVMe SSD blades installed on a PCIe host controller that has given me zero issues.
• To prepare for using MyBootMgr to install and configure RefindPlus & OpenCore, I cloned my MacOS 'Mojave' boot volume to a SATA SSD which is installed internally in Bay 2 of my MacPro 5,1, to be used as my fallback system. I also backed up my RefindPlus set up by copying all the folders/files from the ESP volume on the APFS-formatted NVMe drive with the original MacOS 'Mojave' system. I am hoping to use that same ESP volume for the new RefindPlus/OpenCore set up, unless it makes more sense to set it up on the fallback system drive.

Please let me know if there's any other information that you require.

Thank you!

Edit: Added ConfigFactory debug log for completeness

 

[Dayo]

Thanks for the report.
Seems you missed out attaching the debug log file itself.
Perhaps you can edit your post to add it.

 

[Dayo]

Please let me know if there's any other information that you require.

None actually. I have cross referenced your issue with that from @Farravi and spotted the issue on build step 52.

Basically, it should work if you choose "NO" to the question on running WrangleConfig automatically.
Can you try this and confirm? Also, please attach the actual DebugLog File as this issue should not have been triggered in your case ... need to check to see why it did in case there is something else I need to consider.

Pending a fix, if you have added a script to WrangleConfig that you want to apply, drag the tool into Terminal and press 'Enter' to run such manually.

EDIT: There was something else, related to using an Nvidia GPU, to consider.

 

[Dayo]

Updated MyBootMgr to v075c
See change log in Post 1 for details

 

[zzzippp]

Basically, it should work if you choose "NO" to the question on running WrangleConfig automatically.
Can you try this and confirm? Also, please attach the actual DebugLog File as this issue should not have been triggered in your case ... need to check to see why it did in case there is something else I need to consider.

Thanks, @Dayo, for your help with this!

After updating MyBootManager to version 0.7.5c, I ran ConfigFactory again, and successfully completed the RefindPlus and OpenCore build and configuration.

I think I misunderstood the functionality of WrangleConfig. I mistakenly assumed it would walk the user through the process of how to implement post-installation changes/amendments, but after searching for information about the tool in this thread, I now see that the user needs to edit the WrangleConfig Bash script to add script(s) for any post-installation changes they would like to make. I have been using Refind with some menu customizations, but I now realize I should see what changes are needed after installing MyBootMgr for the first time, and then decide if I need to edit WrangleConfig to be automatically used in future updates.

Also on the topic of potential misunderstandings, with regards to ConfigFactory's first query that I saw, "Would you like to use ConfigFactory Defaults for your Mid 2010 Mac Pro where Possible?", I assumed there are very few cases in which a user would want to answer "No". However, I am unable to find any details or documentation regarding this both by searching on this MacRumors thread or using Google. So, what are the ConfigFactory defaults for a Mid 2010 Mac Pro affected by the answer to that query? Does that just set the highlighted default answer for each query in each ConfigFactory query dialog?

On this second run of ConfigFactory, I noticed it began with a new query asking if I would like to run it in debug mode. Perhaps I missed that the first time?

In addition to answering 'No' to the query asking whether I would like to always automatically run WrangleConfig after ConfigFactory, I changed some of my other responses, based on the fact that I have now formatted my fallback volume with my cloned backup of MacOS 'Mojave' as HFS+ (MacOS Extended). For the sake of completeness, here is a log of my responses to ConfigFactory's queries:

Spoiler: Log of ConfigFactory dialogs & responses

-----------------------
Second Install Attempt
-----------------------

Yes <- Would you like to run ConfigFactory in debug mode?
Yes <- Would you like to use ConfigFactory Defaults for your Mid 2010 Mac Pro where Possible?
No <- Are you running any 'DosDude' or similar patched Mac OS instances?
No <- Are you running any cards or modules providing WiFi functionality in your Mid 2010 Mac Pro?
No <- Are you running any FileVault encrypted Mac OS Volumes on your Mid 2010 Mac Pro?
Yes <- Are you running any Mac OS instances on your Mid 2010 Mac Pro from HFS+ format volumes?
Yes <- Are you running or intend to soon install Mac OS 'Big Sur' on your Mid 2010 Mac Pro?

Notes on Mac OS 11.x (and later) for your Mac:
• Potential delta and other update issues
- Use 'OpenCore (Updates)' instance for updates
• Potential boot issues with built-in USB ports.
- Consider USB 2.0 hub or PCIe USB controller

Yes <- Are you running or intend to soon install Mac OS 'Monterey' on your Mid 2010 Mac Pro?
Yes <- Are you running or intend to soon install any Linux flavour on your Mid 2010 Mac Pro?
Yes <- Are you running or intend to soon install Microsoft Windows on your Mid 2010 Mac Pro?
Yes <- Have you implemented or intend to implement UEFI Windows on your Mid 2010 Mac Pro?

CAUTION:
- UEFI Windows can damage your Legacy Mac
- Legacy Windows works best for Legacy Macs

No <- Are you using a 'Retina' or any other HiDPI Monitor for the boot screen on your Mid 2010 Mac Pro?
Yes <- Have you connected or intend to soon connect more than one monitor to your Mid 2010 Mac Pro?

Could not directly make drives connected to PCIe Slots in your Mid 2010 Mac Pro identify as internal.
No <- Would you like to use 'Innie' to make such drives identify as internal?
NOTE - The version of 'Innie' bundled with ConfigFactory may not function when running Mac OS 11.x (Big Sur) or newer.

Nvidia Kepler GPU support was dropped in Mac OS 12.x
- Consider switching to an AMD GPU model
- Consider applying Kepler BaseSystem Patches
* See MyBootMgr 'Docs' folder for details

No <- Would you like to enable Thunderbolt 3 support in OpenCore?
Yes <- Would you like to allow booting operating systems on external drives via OpenCore?
No <- Would you like to include external FireWire drives?
NB: This may compromise system integrity
No <- Would you like to always automatically run WrangleConfig after ConfigFactory?

SELECT FALLBACK Mac OS VOLUME
This should be a Mac OS volume that you will like to boot to if you need to reset things.
This information will be used by some of the bundled apps to locate the volume automatically.
You can override the detected disks or volumes the using MyBootMgr's Helper Tools.

<Selected working clone of bootable Mac OS Mojave system located on SATA SSD in Bay 2>

SELECT EITHER ONE OF:
• For HFS Type: The volume you wish to install to.
• For ESP Type: Any volume on a physical disk whose EFI System Partition (ESP) you wish to install to.
- For example, select any volume on the volume on the disk in Bay 3 to install on the ESP of that disk
This information will be used by some of the bundled apps to locate the disk automatically.
You can override the found disks or volumes when using the Helper Tools.
Select a HFS+ volume for full compatibility/automation as the ESP of disks containing HFS+ volumes can be detected reliably as opposed to APFS, RAID, or Fusion drives.

<Selected working clone of bootable Mac OS Mojave system located on SATA SSD in Bay 2>

ConfigFactory Specification Completed

However, on the next step, running the DeployConfig app, after selecting the ESP partition I would like to use, I am seeing the message:

Could not validate selected item

...and I would like to find out if this is any cause for concern. After that message, I see a dialog asking to "Select Desired EFI System Partition", and I am not sure why the partition I selected could not be validated.

Here is the output of diskutil list in Terminal:

Spoiler: List of disks / partitions:

/dev/disk0 (external):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                         1.0 TB     disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk2         1.0 TB     disk0s2

/dev/disk1 (external):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                         256.1 GB   disk1
   1:                        EFI                         104.8 MB   disk1s1
   2:       Microsoft Basic Data WinPro                  254.9 GB   disk1s2

/dev/disk2 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +1.0 TB     disk2
                                 Physical Store disk0s2
   1:                APFS Volume MacProSSD               321.4 GB   disk2s1
   2:                APFS Volume PreBoot                 23.1 MB    disk2s2
   3:                APFS Volume Recovery                507.6 MB   disk2s3
   4:                APFS Volume VM                      32.8 KB    disk2s4

/dev/disk3 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *2.0 TB     disk3
   1:                        EFI EFI                     209.7 MB   disk3s1
   2:                  Apple_HFS MaxiMacBackup           2.0 TB     disk3s2
   3:                  Apple_HFS eDrive                  19.2 GB    disk3s3

/dev/disk4 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk4
   1:                        EFI EFI                     209.7 MB   disk4s1
   2:                  Apple_HFS MacProMojave            999.2 GB   disk4s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk4s3

In the DeployConfig App, I selected ESP Type, and then selected disk4s1 from the diskutil list that DeployConfig presented. I know this ESP partition is valid and working, as I can mount it with the command sudo diskutil mount disk4s1, and observe that it has an Apple Firmware.scap file located in the directory EFI/APPLE/EXTENSIONS and in the Info for the volume it appears as MS-DOS (FAT32), exactly as the ESP partition where I have had RefindPlus installed and working fine on my main boot drive (the NVMe SSD blade previously mentioned).

So should the message about not being able to validate disk4s1 as the ESP on which to install RefindPlus and OpenCore be any cause for concern?

Edit: Reformatting for better legibility

 

[Dayo]

After updating MyBootManager to version 0.7.5c, I ran ConfigFactory again, and successfully completed the RefindPlus and OpenCore build and configuration.

Great.

I now realize I should see what changes are needed after installing MyBootMgr for the first time, and then decide if I need to edit WrangleConfig to be automatically used in future updates.

Correct. You can do set things up to automatically apply whatever changes you want. It is a blank slate for users to add any code they want to run on the output.

Most likely use I think will be to do things like add changes to the RefindPlus custom.conf file (different background, icons for obscure distros, change whole theme etc) but you can do things like amend the OC config file with PlistBuddy etc.

You can also set it up to add extra OC instances to the package by copying the folder in and amending the RefindPlus config file to display this etc. Whatever you can imagine really.

Does that just set the highlighted default answer?

Yes, it just picks the highlighted default answers. However, the highlighted defaults are not fixed and do change based on various factors, the main one being the model in use. Defaults can also change depending on whether the GPU is from Nvidia or from AMD or Mac versions previously indicated etc

The questions ConfigFactory asks are of two basic types. If a user does not know the answer, they should go with the highlighted default:

• About what you have in your Mac ... Do you have ABC?
  • Always displayed for user input if could not be detected automatically or detection was not attempted
    • For instance, you didn't get any questions about your GPU as all the info needed was found but some others might do.
  • The default is Cancel. Obviously not a good idea to proceed if not knowing what is in one's computer
• About options available ... Would you like XYZ?
  • Some are not shown if set to use defaults
  • The highlighted default button changes as explained (the questions themselves may also change to fit)

So, if you don't know the answer to a question, such as what WrangleConfig actually does for instance, you should click the highlighted "No" in that case. I will rephrase the question though, as it seems people can't resist clicking "Yes" to stuff that says "automatically do this?" even when "No" is suggested by highlighting.

On this second run of ConfigFactory, I noticed it began with a new query asking if I would like to run it in debug mode. Perhaps I missed that the first time?

It always runs in debug mode the first time it is run as that is when issues are most likely to crop up.

In addition to answering 'No' to the query asking whether I would like to always automatically run WrangleConfig after ConfigFactory, I changed some of my other responses

You will note that "No" is the default selection on that question.

I would like to find out if this is any cause for concern. After that message, I see a dialog asking to "Select Desired EFI System Partition", and I am not sure why the partition I selected could not be validated.

Not a cause for concern. Just that the tool could not determine some detail about your preferred target volume and needed that you select things manually. Was too lazy to write out anything more verbose.

To clarify further, you didn't select disk4s1 from the diskutil list here, but a whole line containing disk4s1:

I selected ESP Type, and then selected disk4s1 from the diskutil list that DeployConfig presented.

This line then needed to be parsed to extract "disk4s1". This parsing is what failed and the apps therefore degrade to offering a less convenient (for the user, who might need to run DiskUtil List in Terminal first) but reliable way to get the info. The parsing failure has been fixed for the next iteration.

* Edited for clarity

 

[zzzippp]

Thank you @Dayo, for all of the helpful answers!

Most likely use I think will be to do things like add changes to the RefindPlus custom.conf file (different background, icons for obscure distros, change whole theme etc)

Yes, this is what I imagine I may take advantage of WrangleConfig to help with. I just didn't do enough searching to learn its functionality to realize I should not choose to automatically execute it on my initial configuration and install.

Yes, it just picks the highlighted default answers. However, the highlighted defaults are not fixed and do change based on various factors, the main one being the model in use. Defaults can also change depending on whether the GPU is from Nvidia or from AMD or Mac versions previously indicated etc

The questions ConfigFactory asks are of two basic types. If a user does not know the answer, they should go with the highlighted default:

• About what you have in your Mac ... Do you have ABC?
  • Always displayed for user input if could not be detected automatically or detection was not attempted
    • For instance, you didn't get any questions about your GPU as all the info needed was found but some others might do.
  • The default is Cancel. Obviously not a good idea to proceed if not knowing what is in one's computer
• About options available ... Would you like XYZ?
  • Some are not shown if set to use defaults
  • The highlighted default button changes as explained (the questions themselves may also change to fit)

So, if you don't know the answer to a question, such as what WrangleConfig actually does for instance, you should click the highlighted "No" in that case. I will rephrase the question though, as it seems people can't resist clicking "Yes" to stuff that says "automatically do this?" even when "No" is suggested by highlighting.

This is very helpful to know! I did not realize answering "yes" to this would result in subsequent query dialogs having the default response highlighted. Perhaps an explanation in the "Would you like to use ConfigFactory Defaults for your <Mac Model> where Possible?" query dialog would help clarify?

To clarify further, you didn't select disk4s1 from the diskutil list here, but a whole line containing disk4s1:

This line then needed to be parsed to extract "disk4s1". This parsing is what failed and the apps therefore degrade to offering a less convenient (for the user, who might need to run DiskUtil List in Terminal first) but reliable way to get the info. The parsing failure has been fixed for the next iteration.

Yes, my apologies, my wording wasn't clear. I use diskutil in Terminal often enough to recognize that the list in the DeployConfig app's "Select Desired EFI System Partition" dialog appeared to be generated by the diskutil list command. And yes, I chose the line in that list containing the designation of the EFI partition (disk4s1) that I want to use for the ESP type RefindPlus and OpenCore deployment.

Now that I know the reason for the "Could not validate selected item" message, I used the fallback method offered in the subsequent dialog, and successfully deployed RefindPlus and OpenCore to my chosen EFI partition (and soft-blessed RefindPlus so that I may begin testing).

I do have a question, however, about the finalisation step. As I understand it with no blessed folder/volume set in my Mac Pro's NVRAM, it will boot using the first EFI partition instance containing a valid bootx64.efi file. So, since I already had RefindPlus deployed onto the EFI partition of the NVMe SSD drive on which I plan to install MacOS 'BigSur' courtesy of OpenCore, I should remove that original instance of RefindPlus so that it is not selected to load after I do the 4-chime NVRAM reset, correct?

 

[Dayo]

I did not realize answering "yes" to this would result in subsequent query dialogs having the default response highlighted.

Didn't say that and the default response is always highlighted on every dialogue box. That very one itself has a default/suggested selection, "Yes", highlighted.

What clicking "Yes" there does is to use the default for some questions without displaying those questions. You can re-run and click "No" to see these.

remove that original instance of RefindPlus

The guide is based on only having one active ESP present but I suppose it doesn't make a difference since whatever such RP/OC based ESP it selects after an NVRAM reset will allow you to boot into Mac OS without OpenCore to firm bless the instance you want to bless. Booting into Mac OS without OpenCore is the critical item in the process.

You can of course also disconnect that disk if you want.

 

[Dayo]

I just didn't do enough searching to learn its functionality to realize I should not choose to automatically execute it on my initial configuration and install.

You should not have selected "Yes" indeed but that is just as a matter of principle. That is, not selecting options to do "stuff" when you do not definitively know what that "stuff" is.

Most that run ConfigFactory in the mode that shows a query about activating RadeonBoost tend to select "Yes", despite "No" being highlighted, without knowing what RadeonBoost actually does and just assume this from the name .. will most likely remove it altogether.

Anyway, that the app failed for you on activating WrangleConfig is a separate matter from the principle and would have affected those that did legitimately need it, now fixed, as it should have just run the empty tool with nothing happening.

 

[JedNZ]

I have finally managed to upgrade with MyBootMgr 0.7.5b, but it meant I had to do quite a bit of reading up in order to identify and understand why – with versions of RefindPlus MyBootMgr upwards of 0.7.3a on my cMP – the logon screen would not show on Mojave and it lost GPU support (as per my sig, I have a Sapphire Pulse RX590), and why Big Sur would crash and stall. But alas I was able to work it out (and learned much more about OpenCore in the process - which I fear I'll forget too quickly), and now have a well behaving Mojave (NVMe) and Big Sur (SSD in SATA bay) using the OC instance of OpenCore created by ConfigFactory MyBootMgr. I was also able to upgrade Big Sur 11.5.2 to 11.6.1 using the OC_ALT instance of OpenCore (but use OC for everyday usage).

I realise this post might be specific to OpenCore, however I share it here for others who might also be having issues using the OC instance of OpenCore that is created by ConfigFactory MyBootMgr. If anyone knows how to achieve the changes below with choices I should be making in ConfigFactory then please let me know (I'd far prefer to use the stock output from ConfigFactory without having to go and make manual changes afterwards).

Changes I've made from the OC version of OpenCore created with RefindPlus MyBootMgr0.7.5b:

Under the Misc > Security section:
<key>SecureBootModel</key> <string>Default</string>
changed to:
<key>SecureBootModel</key> <string>Disabled</string>

Under the NVRAM > boot-args section:
<string>debug=0x144 keepsyms=1 -no_compat_check</string>
changed to:
<string>agdpmod=pikera shikigva=80 wegtree=1 unfairgva=1 debug=0x144 keepsyms=1 -no_compat_check</string>

Under the PlatformInfo > SMBIOS section:
<key>BoardProduct</key> <string>Mac-27AD2F918AE68F61</string>
changed to:
<key>BoardProduct</key> <string>Mac-7BA5B2D9E42DDD94</string>

These three things allow me to enjoy the best of my cMP - boot screens on 4K monitor, HWAccel, internal PCIe drives etc.

I have not had to make any changes to the OC_ALT instance - it seems to work fine for it's single purpose for me of updating macOS versions.

Updated: erroneous nomenclature corrected

 

[Dayo]

Haven't actually calculated it, but I am sure the permutations of setups that can come out are at least a hundred.

So, you need to attach the debug log from your run to allow a meaningful response.

BTW, on nomenclature, there is no such thing as RefindPlus 075b and RefindPlus does not create OpenCore config files.

RefindPlus is just a component, along with OpenCore, of a boot setup created by MyBootMgr. ConfigFactory is part of MyBootMgr which configures RefindPlus and OpenCore.

The misunderstanding of the process is not an issue in this case but is often the case.

Anyway, as said, you need to share the debug log from ConfigFactory.

 

[JedNZ]

Haven't actually calculated it, but I am sure the permutations of setups that can come out are at least a hundred.

So, you need to attach the debug log from your run to allow a meaningful response.

BTW, on nomenclature, there is no such thing as RefindPlus 075b and RefindPlus does not create OpenCore config files.

RefindPlus is just a component, along with OpenCore, of a boot setup created by MyBootMgr. ConfigFactory is part of MyBootMgr which configures RefindPlus and OpenCore.

The misunderstanding of the process is not an issue in this case but is often the case.

Anyway, as said, you need to share the debug log from ConfigFactory.

My apologies - I seem to do that a bit. I've edited my post to correct this.

Log attached. If I'm reading it correctly, it doesn't seem to recognise my GPU: using gfxutil, I think the PCie address is
GFX0@0 = PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0) if I'm reading it correctly. It's installed in PCIe slot 1. In About this Mac it's recognised as Radeon RX 590 8 GB.

 

[Dayo]

If I'm reading it correctly, it doesn't seem to recognise my GPU:

Correct. You somehow ended up in a state where it concluded you neither have an AMD nor Nvidia GPU as shown in Card_Nvidia=false ... Card_AMD=false. It should have asked for information about the GPU though. Are you saying this didn't happen?

Might be related to you not having Python 3 installed but there is a fallback and I seem to recollect previous instances with your GPU being recognised. Not sure why that hasn't happened here.

On the boot issues, there are multiple instances created by ConfigFactory and the default "OC_MAIN" instance is not created as a one-size-fits-all instance. I thought there is enough information given in RefindPlus on what each instance is focused on. The OC_LEG instance should boot Mojave and the "OC_MAIN" should boot Monterey.

You did indicate Monterey in ConfigFactory but if you are not literally about to install this in the next week or so, then best to answer "NO" to the query. Basically, ConfigFactory is not trying to create an OpenCore instance that handles everything from Mojave (Legacy Mac OS) to Monterey (Modern Mac OS) and there are instances to cover each separately.

I suppose overlaying all of that is the issue with your GPU not showing up which is likely adding another dimension to the setup issues. Either way, there is nothing wrong with editing the generated files to suit but regardless, the setup will always be finetuned further based on feedback and observations.

 

[JedNZ]

You somehow ended up in a state where it concluded you neither have an AMD nor Nvidia GPU as shown in Card_Nvidia=false ... Card_AMD=false. It should have asked for information about the GPU though. Are you saying this didn't happen?

Yes, there was no option about my GPU (I haven’t seen any questions in ConfigFactory to do with my GPU for quite some time - maybe back in version <0.6.x).

At which stage should options about my GPU come up? Do you think my RX590 isn’t expected or able to be recognised?

I’ll change the Card_AMD=false to true to see if that affects anything.

I’ll install Python 3 and rerun ConfigFactory but exclude Monterey as I don’t plan to install and experiment with it just yet.

 

[Dayo]

It should have asked for information about the GPU though. Are you saying this didn't happen?

I have done a review and the fallback does not cover some instances indeed.

I can't issue an update right now as the apps are in a state of flux following quite a lot of changes ahead of v076 and I don't have enough time to make sure there is no mix up. Best stick with your working amended setup.

PS: A debug log is a record of what has happened ... changing such doesn't affect anything.
Logs are output items, not input items.

Yes, there was no option about my GPU (I haven’t seen any questions in ConfigFactory to do with my GPU for quite some time - maybe back in version <0.6.x).

At which stage should options about my GPU come up? Do you think my RX590 isn’t expected or able to be recognised?

It only asks when it can't detect things but in your case, the fallback code where the question would have been asked on failure had a bug that caused it to be skipped for undetected AMD GPUs

 

[JedNZ]

You're amazing, and very patient with me – I really do appreciate that. No rush - my system is working so I'm happy.

I had issues installing Python 3 (3.9.9) so had to uninstall Brew and everything else, and then install it back again. All completely over my head, but Python 3 is installed and working now. And I ran ConfigFactory again, made a couple of tweaks (added the extra boot-args of agdpmod=pikera shikigva=80 wegtree=1 unfairgva=1, changed the BoardProduct to <string>Mac-7BA5B2D9E42DDD94</string>, didn't have to change the SecureBootModel because this time it was set on Disabled), and I then deployed it and it's working fine.

 

[Macschrauber]

Did I miss something or why is Monterand removed from MyBootMgr and CDF's variant?

No longer necessary?