Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Updated MyBootMgr to v100a
See change log in Post 1 for details
 
Hello!

I have troubles getting the ConfigFactory working.

Using a cMP Mid 2010 5.1 2 x CPU with 1x Metal GPU.
Tried it with a fresh install of Mojave and afterwards installed a fresh copy of High Sierra 10.13.6.

After selecting Solo Mode the App crashes straight away.
After selecting Dual Mode a Window pops up with no Text and OK and Cancel.
Pressing OK I get informed that my Mac is unknown - so partly supported.
If I proceed the App crashes (Command exited with a non-zero status)
I also tried to give the ConfigFactory Permissions in the Privacy Settings. Always same issue.

Thanks for your help!!
 
Last edited:
I have troubles getting the ConfigFactory working.
Thanks for the report. Should be fixed.
Try downloading the package again.
Make sure you have completely shut your browser down at least once since the previous download
 
  • Like
Reactions: DieBartDie
Hi Dayo,

On my cMP 5,1 I have been trying to set up Monterey as the main OS with Mojave as an emergency boot drive, and Windows for other things. I've gone through the entire setup on p. 1 and got RefindPlus working great - but not OC.

I originally installed Monterey using OCLP, which I understand MyBootMgr is supposed to work with. Was having issues with SIP being on, so I disabled NVRAM again in Recovery, removed RFP and OC and reinstalled them, but when booting into RFP and selecting Monterey, all I get is a prohibitory sign. Probably missed a step, but I just don’t know where it is.

I’m confused about something in the dual install: It gives you disk options for the RFP setup, but not for OC. I thought that had to be installed on an ESP on the Monterey drive. Sorry if I’m really out in left field here, but my brain has turned to mush on this. As always, any help is appreciated.
 
Probably missed a step ... my brain has turned to mush
Get some sleep and take a look with a clear head after.

In the meantime, share logs.
Remember to never report an issue anywhere without adding log files if available. ConfigFactory always generates a log file when run. It also sets RefindPlus and OpenCore up in debug mode initially so that they generate log files when run.

Having said all that, it is best for most to decide on a preferred method of setting OpenCore up and to stick with this. If you like the OCLP, ignoring that it is not needed (some would say not desirable) for Monterey on a cMP unless using an otherwise unsupported GPU, then stick with this and do what you want within that context.
 
Last edited:
Thanks much for your response. Enclosed are the ConfigFactory and OC logs. Please let me know if I missed any others.
 
I thought you just had to click Attach Files below. I stuck the actual files on there, but they looked as if I had copy/pasted them. I'll try attaching a zip file.
 

Attachments

  • RFP OC Logs.zip
    3.2 KB · Views: 27
Rerun
I'll try attaching a zip file.
You can incoporate OCLP Monterey into a MyBootMgr setup but as mentioned before, the OCLP is not needed to run Monterey on a cMP when using a supported GPU as in your case with an RX 580.

While it is possible for both to coexist, you need to decide whether you want to use a MyBootMgr setup or an OCLP one when not going beyond Monterey. How to incorporate Ventura/Newer, which require the OCLP, is explained in Post 1. This does not apply to you (as yet).

If you want to use a MyBootMgr setup with what you have...
  • Remove any OCLP system patches added to Monterey
    • Should not be any for RX580 but in case there was
  • Follow the steps set out in Post 1 verbatim
    • Includes running ConfigFactory
      • The "DosDude" item you set will no longer be applicable.
    • Do not disconnect drives while running ConfigFactory as you appear to have done
      • This is contrary to what Post 1 states
      • Unless you know what you are doing, do not decide to do X when it says to do Y
Otherwise, stick with the OCLP and configure things as it requires.
You should find help either on the OCLP support channel or somewhere like the "Monterey on Unsupported Macs" thread.

Good luck!
 
Thanks. I do try not to skip things, but sometimes I get lost in the instructions. I'll give this a shot.
 
Ok, I got as far as:
2. Test OpenCore if "Dual Mode" was used
Boot Mac OS via an appropriate OpenCore instance in RefindPlus

I assume this means boot Monterey - I clicked the icon and got a prohibitory sign. Followed everything else correctly unless there was something I didn't understand. I had set RFP to be installed on my HFS+ FILES disk, and soft-blessed it. At one point I did soft-bless OC (even though it said "Are you sure? Normally you should bless RefindPlus". It restarted, and it gave me a text choice of which instance to open. I selected Monterey and got a huge verbose text stream that said Trying To Restart at the bottom. It never did, so I had to do it manually and go back into Mojave. Enclosed is the latest RFP log.
 

Attachments

  • DebugLog_ConfigFactory.log.zip
    2 KB · Views: 42
A few things.
  1. The file you attached is not a RefindPlus log. It is a ConfigFactory log ... as the filename says it is.
  2. I assume you are selecting the correct OpenCore instances in RefindPlus for what you want to ultimately boot.
  3. To get RefindPlus logs, you need to mount the ESP using the "TweakESP" app where you will find them with a "*.log" format. OpenCore logs will also be on the ESP and have a "*.txt" format
Leaving those aside...
Check whether you are able to boot into Mojave both via RefindPlus (first) and then the "OC_LEG" OpenCore instance in RefindPlus. Leave Monterey alone for now as not sure of the provenance of that installation and doubt you completed the Monterey installation process with the OCLP.

Report back if unable to.

If able to, complete the rest of the Post 1 steps and then, from Mojave, create a new Monterey installer with this script:

Instructions are at the top of the file.

Connect the USB Installer, restart into RefindPlus, select the "OC_VMM" OpenCore instance, run the macOS Installer (which would be presented as an option) and overwrite the existing Monterey instance to get rid of any funnies there.

You will be able to boot Monterey via the labelled OpenCore instance for this in RefindPlus after the suggested steps.
 
Last edited:
I can restart Mojave from RFP but I don't get any EFI instance to do it from OC. RFP shows the 3 OSes I plan to use, and 3 OC "stanzas", for a 7,1 login to Monterey, installing / updating Monterey, and (I think) a login for an older iMac.

Was only able to find RFP logs. The only .txt files were License.txt.
 

Attachments

  • ReFindPlus Logs.zip
    12.4 KB · Views: 25
Check whether you are able to boot into Mojave both via RefindPlus (first) and then the "OC_LEG" OpenCore instance in RefindPlus.
The instruction above was to load a specific Mac OS version, Mojave, from a specific OpenCore instance, the "OC_LEG" instance.

Your logs show that you have booted into the OC_AAA instance instead and tried to boot SOMETHING ELSE.

You may have done the correct thing first and then tried this later but the logs need to reflect this.

Repeated:
  • Try to boot into Mojave via the OC_LEG instance
    • Report back if it fails.
      • Do not report back about what happens with booting into anything else
      • Do not report back about what happens when you use a different OpenCore instance
    • If it does not fail, proceed with the instructions to install Monterey
      • Follow actual instructions written for that
 
I was looking at experimenting with Sequoia on a test drive, and also updating my production cMP from 14.6.6 to 14.6.7, so I downloaded MyBootMgr 1.0.1 and ran ConfigFactory but got an unexpected result - hardly any of the Kext files were copied across on the build. Here's a screenshot of the difference (left is my current working OC_EXT Kext folder, and the new one built with 1.0.1 on the right).

@Dayo I've included my log file. Are you able to confirm if there's an issue with ConfigFactory build, or something I've done wrong? I use the manual option to select the options, and believe I've selected all the options I made in the previous build I did using MyBootMgr 1.0.

Screen Shot 2024-09-18 at 17.02.39.png

Also attached are the config/plist files for comparison - look quite different, but don't know if part/all of that is because of the differences between MyBootMgr 1.0 and 1.0.1.
 

Attachments

  • DebugLog_ConfigFactory.log.zip
    2 KB · Views: 23
  • 1.0 config.plist.zip
    10.5 KB · Views: 21
  • 1.0.1 config.plist.zip
    4.3 KB · Views: 21
@JedNZ ... Not sure I fully understand the issue. Is the problem that the kexts in your existing OC_EXT folder was not propagated between the two runs?

Note that you are supposed to overwrite the OC_EXT folder created by ConfigFactory with the contents of the OC folder created by the OCLP. You presumably did this for your existing instance and are positioned to do the same now again or am I missing something?

BTW, "OC_EXT" will be changed to "OC_X**" as of the next version of MyBootMgr with "OC_X01" being for Ventura/Sonoma and "OC_X02" being for Sequoia/Newer.

This is to allow seamless multiboot of Sequoia and Ventura/Sonoma via the OCLP. Such is already an issue on MP31 where an undesirable-if-avoidable "cpus=4" boot arg is needed for Sequoia. I expect more of such to crop up with time across the board.
 
The screenshot above is what the two versions of MyBootMgr > ConfigFactor created - v1.0.0 (on the left) vs 1.0.1 (on the right). The one on the left is my currently deployed and working version - i.e. that's what is on the ESP.

When MyBootMgr 1.0.1 > ConfigFactory builds the OC_EXT there are a whole stack of Kexts missing, and the config.plist also looks screwed up compared to the previous working version I created using MyBootMgr 1.0.0. Are there any clues for you looking at the two config.plist files I uploaded above? I did run ConfigFactor twice and I got the exact same result both times, hence why I posted. Note: I do all of this running a native macOS Mojave boot drive.

Great to hear you're still working and developing MyBootMgr :) - I look forward to future updates.

I'll stick with my current version of OC_EXT until I hear from you. Let me know if you need anything further from me to help problem solve this one, but I will try again tomorrow just to see if I get a better result.
 
The 1.0 Config Plist was not generated by ConfigFactory but by the OCLP. It is in your existing OC_EXT folder because you copied in an OCLP generated OC folder (kexts, config file and all) to completely replace what ConfigFactory generates as the process requires. I think forgetting you need to do this might be your sticking point.

I'll refer you to the guide on incorporating OCLP instances into MyBootMgr setups that *YOU* wrote:

Follow it and you would be good.
I might amend ConfigFactory to create an empty OC_EXT folder to reinforce that it needs to be populated separately
 
  • Like
Reactions: JedNZ
Updated MyBootMgr to v102
See change log in Post 1 for details
 
Dayo,

I've been booting into and running macOS Monterey on my MacPro5,1 for some years now thanks to RefindPlus & OpenCore, as configured by MyBootMgr's ConfigFactory. The last version I used to update RefindPlus / OpenCore was MyBootMgr v088. I am planning to try installing macOS Ventura, so I've downloaded and installed MyBootMgr v102's apps with the goal of making sure macOS Monterey boots and runs without issue with the latest versions of RefindPlus / OpenCore and their respective configurations, before I attempt installing macOS Ventura.

After reviewing post 1, while booted natively into macOS Mojave I ran ConfigFactory, made all my selections, and then started the build. However, ConfigFactory stopped with a fatal error on BuildStep 15. Are you able to look at the attached ConfigFactory log to help diagnose what may be causing the issue?

If you need any more information on my MacPro5,1 or steps I took before running ConfigFactory, please let me know, thank you!
 

Attachments

  • DebugLog_ConfigFactory_log.zip
    1.9 KB · Views: 20
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.