Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MP 1,1-5,1 RefindPlus|OpenCore by MyBootMgr
- Thread starter Dayo
- Start date
-
- Tags
- multi boot opencore refindplus
- Sort by reaction score
It only asks about Nvidia GPUs when it has failed to determine the GPU vendor. It asking before was due to issues. Now that aspect has been fixed, Nvidia GPU users may just notice it only offers DRM Streaming and not GPU Acceleration. When the vendor is determined to be AMD, it offers DRM Streaming and GPU Acceleration.
It asks about the model when it determines there is only one AMD GPU model present. That is, only one AMD GPU Model ID or multiple GPU Model IDs of the same AMD model. Hardware probing supplies GPU Model IDs for this comparison but ConfigFactory does not include a database of GPU Model ID to GPU Model Name. If there is a mix and match, it doesn't bother to ask as the information will not be used.
As for everything else, you can share your OpenCore config file for a look.
It asks about the model when it determines there is only one AMD GPU model present. That is, only one AMD GPU Model ID or multiple GPU Model IDs of the same AMD model. Hardware probing supplies GPU Model IDs for this comparison but ConfigFactory does not include a database of GPU Model ID to GPU Model Name. If there is a mix and match, it doesn't bother to ask as the information will not be used.
As for everything else, you can share your OpenCore config file for a look.
Last edited:
Thanks for the clarification and your help. I am very happy with my current setup. I don't really need WIFI and I can live with only HDMI output - even though it's only 30 Hertz. Since the Display Port did not work with Martin's Package either, I don't think it's a MyBootMgr issue.
Anyway, here is my config.
Anyway, here is my config.
My Mac OS drive is setup as APFS, the last time i tried to use refindplus it complained about the APFS format,
has this been addressed yet ? I.E has APFS drive format support been added to the configs factory?
has this been addressed yet ? I.E has APFS drive format support been added to the configs factory?
It has always been there as there would be little point otherwise.
You need to read any messages displayed properly.
Either way, whatever blocking issue you may have faced with respect to APFS volumes is certainly no longer present.
Last edited:
I tried it again yesterday and got the same error, some thing like "you partition is not HFS blah Blah blah,
and it a fresh install of Mojave, not to worry i have gone with OpenCore and that is working perfectly.
Lost as to how you have interpreted this as representing an error message:
It simply informs you that you there is some functionality within ConfigFactorythat is only available when an HFS+ volume is selected. It gives an option to change your selection to such a drive or to just confirm the APFS volume choice and continue.
The limited functionality is with Configfactory and not with the final setup btw ... Could be that this was what you didn't get. I could add some more verbiage but not quite sure of the merits of writing an epistle in every dialogue box.
Seems like the best outcome was reached in the end all said and done.
EDIT: Rephrased sentence about 'comprehension'
It simply informs you that you there is some functionality within ConfigFactorythat is only available when an HFS+ volume is selected. It gives an option to change your selection to such a drive or to just confirm the APFS volume choice and continue.
The limited functionality is with Configfactory and not with the final setup btw ... Could be that this was what you didn't get. I could add some more verbiage but not quite sure of the merits of writing an epistle in every dialogue box.
Seems like the best outcome was reached in the end all said and done.
EDIT: Rephrased sentence about 'comprehension'
Last edited:
1) it still had issues with my APFS install, even after selecting "no" from that prompt.
2)"could be that bit was what you couldn't quite comprehend." Rude much ??
Like i already stated i have gone with OpenCore and it is giving me no issues at all.
Case closed !!
Should have used different wording ... Will change that.
This is what I use myself and has zero implication apart from some options not showing up in some other tools later ... Bizarre.
Would have been useful if you had articulated the issues as the "blah blah blah" notice is not an error message as pointed out. Anyway, the main thing is that you are up and running and happy with a setup. Not important how this was done.
EDIT: Changed the prompt message a bit (for next release) to make clear that the limitation is with MyBootMgr tools.
Last edited:
Rectified mix up in uploaded package which has now been replaced.
Needs to be downloaded again if done before this message.
EDIT:
Flawed version may have persisted on the server cache which has just been cleared.
If you see stuff about ConfigFactory when running MyBootMgrSetup, then that package needs to be discarded
Needs to be downloaded again if done before this message.
EDIT:
Flawed version may have persisted on the server cache which has just been cleared.
If you see stuff about ConfigFactory when running MyBootMgrSetup, then that package needs to be discarded
Last edited:
Not sure if I’m best to post My questions here or on the LateBloom thread as they are specific to RFP.
I’m trying to find a workflow for those of us using RefindPlus to upgrade/install 11.5.2 and using LateBloom.
My main system is using Mojave (see my sig). I have Catalina 10.15.7 and Big Sur 11.2 installed separately each on their own SSDs and located in direct connect SATA bays.
I have the latest version of RFP - 0.7.2a - which includes LateBloom. I can see the LB settings in my
Questions:
1a. When I installed Big Sur, would it have formatted the SSD with the latest version of APFS or the older version that Mojave and earlier use?
1b. If so, does that mean I can just install 11.5.2 (using a USB stick) over the top of 11.2, or is there a better method, or do I need to reformat my Big Sur volume using the Catalina version of Disk Utility or from the Big Sur USB stick (either way I would nuke my current Big Sur 11.2 installation)?
1c. Regardless, when I come to upgrading (from 11.2) or fresh installing Big Sur 11.5.2 do I boot into my
Q2a. Also, with my Mojave installation, should I reformat this using Catalina or Big Sur so it’s using the latest version of APFS?
Q2b. I’m wanting to upgrade my main Mojave drive to Catalina (I’m not going to use my existing drive that already has Catalina on it as it’s too small fir my everyday needs). Should I upgrade Catalina over the top of Mojave, or am I better to install it on a new NVMe and use migration tool to pull all my apps across from my Mojave drive so that I still have a backup Mojave drive if I need it?
Q3. Should/must I remove all my other drives when upgrading/installing a fresh copy of Big Sur? People have reported data corruption but on volumes formatted using the earlier versions of APFS?
Updated: typos and less ambiguous.
I’m trying to find a workflow for those of us using RefindPlus to upgrade/install 11.5.2 and using LateBloom.
My main system is using Mojave (see my sig). I have Catalina 10.15.7 and Big Sur 11.2 installed separately each on their own SSDs and located in direct connect SATA bays.
I have the latest version of RFP - 0.7.2a - which includes LateBloom. I can see the LB settings in my
OC config.plist file, which I guess I can manually configure. But I’ve also downloaded the OpenCore Legacy Patcher GUI and TUI files.Questions:
1a. When I installed Big Sur, would it have formatted the SSD with the latest version of APFS or the older version that Mojave and earlier use?
1b. If so, does that mean I can just install 11.5.2 (using a USB stick) over the top of 11.2, or is there a better method, or do I need to reformat my Big Sur volume using the Catalina version of Disk Utility or from the Big Sur USB stick (either way I would nuke my current Big Sur 11.2 installation)?
1c. Regardless, when I come to upgrading (from 11.2) or fresh installing Big Sur 11.5.2 do I boot into my
OC_ALT instance of RFP (which has VMM activated) or try to upgrade to 11.5.2 via the normal OC?Q2a. Also, with my Mojave installation, should I reformat this using Catalina or Big Sur so it’s using the latest version of APFS?
Q2b. I’m wanting to upgrade my main Mojave drive to Catalina (I’m not going to use my existing drive that already has Catalina on it as it’s too small fir my everyday needs). Should I upgrade Catalina over the top of Mojave, or am I better to install it on a new NVMe and use migration tool to pull all my apps across from my Mojave drive so that I still have a backup Mojave drive if I need it?
Q3. Should/must I remove all my other drives when upgrading/installing a fresh copy of Big Sur? People have reported data corruption but on volumes formatted using the earlier versions of APFS?
Updated: typos and less ambiguous.
Last edited:
Not familiar with the "RFP" abbreviation but it seems to be meant to refer to the setup created by MyBootMgr ... RefindPlus (RP) and OpenCore (OC). It is close to "RefindPlus" but none of the queries are related to that utility. Assuming you mean OpenCore as set up by MyBootMgr.
From reading your queries, you might be best served asking them on the main OpenCore thread (not the LateBloom thread btw, as that is for reporting tests of that utility) as they seem to be all to do with upgrading Mac OS on OpenCore instances.
The vehicle used to set your OpenCore instances up is not significant. Q1c does require some consideration of the two OpenCore instances MyBootMgr sets up but this is a minor item and Q1c can be rephrased along the lines of "Is VMM on or off in OpenCore relevant to the upgrade process?".
I could have had a stab at the queries regardless but I am not up to speed on the intricacies of upgrading Big Sur and you will get more knowledgeable eyes and better input on the main OpenCore thread. Just rephrase Q1c so as not to confuse the audience there.
Just sharing my experience using MyBootMgr (072a) and successfully upgrading from Big Sur 11.2.1 to 11.5.2 almost entirely without incident (just a hang halfway through the first progress bar - forced a reboot and it went on to do its thing). I didn't make any changes to the default Latebloom settings in MyBootMgr. Although I've only rebooted it twice so far, it seems very stable and lightening fast/responsive. VideoProc confirms HWAccel. (also posted in the Latebloom thread)
@Dayo I'm having problems with 073a, which are also showing up now with 073 also.
When booting into main boot drive via
Update: Just to confirm, I have tested this using both the default settings for my cMP 5,1, plus also choosing all the options manually in ConfigFactory.
I have reverted back to 072a - no problems at all.
When booting into main boot drive via
OC, I get the Apple logo and the progress bar moves across as normal, then the screen always goes blank before the login screen shows. However, with 073a, and now with 073 (didn't happen with 073 the two previous times I booted before installing 073a), after the screen goes blank for a moment after the Apple logo progress screen, I lose graphical output. I can remote in and can see the login screen but it's resolution 1024x768, and in System Preferences > Displays it also shows one resolution - 1024x768 - no other resolutions (I have a 4K screen).Update: Just to confirm, I have tested this using both the default settings for my cMP 5,1, plus also choosing all the options manually in ConfigFactory.
I have reverted back to 072a - no problems at all.
Filtering your message, what you appear to be saying is that after running OpenCore 0.7.3 that comes with MyBootMgr 073a, it appears to have triggered some issue which affected the OpenCore 0.7.3 that came with MyBootMgr 073 which had previously been OK. Upon reverting to OpenCore 0.7.2 that came with MyBootMgr 072a, everything seems to be fine again.
Well, I have no idea what the issue may be and perhaps we will see other reports.
What I do know is:
My bet is on some other change. Maybe different connection etc.
You can try the file again and perhaps there was a temporary glitch that has now been cleared. You can also directly download the OpenCore files from the repo on GitHub and swap these in if you think it might make a difference.
Well, I have no idea what the issue may be and perhaps we will see other reports.
What I do know is:
- Anything done by an OpenCore instance is in the RAM only and does not persist between boots. that is, the OpenCore 0.7.3 that comes with MyBootMgr 073a cannot change anything that will affect any subsequent boot.
- In any case, the OpenCore 0.7.3 files in MyBootMgr 073 and MyBootMgr 073a are exactly the same. The change between the MyBootMgr versions was in the ConfigFactory script which did not correctly create a folder. So when you booted the different times, it was the same file being used.
My bet is on some other change. Maybe different connection etc.
You can try the file again and perhaps there was a temporary glitch that has now been cleared. You can also directly download the OpenCore files from the repo on GitHub and swap these in if you think it might make a difference.
Maybe the issue is that since OpenCore 073
/Volumes/EFI/EFI/OC/Drivers/OpenLinuxBoot.efi
/Volumes/EFI/EFI/OC_ALT/Drivers/OpenLinuxBoot.efi
/Volumes/EFI/EFI/OC_UPD/Drivers/OpenLinuxBoot.efi
are missing.
you can add them from the package at
OpenCore-0.7.3-RELEASE.zip
/Volumes/EFI/EFI/OC/Drivers/OpenLinuxBoot.efi
/Volumes/EFI/EFI/OC_ALT/Drivers/OpenLinuxBoot.efi
/Volumes/EFI/EFI/OC_UPD/Drivers/OpenLinuxBoot.efi
are missing.
you can add them from the package at
OpenCore-0.7.3-RELEASE.zip
Not likely since that would have led to a halt when loading OC when Linux is indicated.
OC apparently loaded each time which suggests Linux and the associated file are not in play.
Thanks guys.
You're right @Dayo . The issue was not at the RefindPlus stage, it was post that, so when I booted via OC. It's definitely something to do with OC because nothing else was changed. I'll check the OC thread to see if anyone else has some ideas.
@Macschrauber thanks for replying, however I don't use Linux, so the absence of the OpenLinuxBoot.efi won't be the issue (also I didn't choose to add Linux support in MyBootMgr).
You're right @Dayo . The issue was not at the RefindPlus stage, it was post that, so when I booted via OC. It's definitely something to do with OC because nothing else was changed. I'll check the OC thread to see if anyone else has some ideas.
@Macschrauber thanks for replying, however I don't use Linux, so the absence of the OpenLinuxBoot.efi won't be the issue (also I didn't choose to add Linux support in MyBootMgr).
Best way to narrow things down would be to first try the package again.
If the issue is still present, try OC v0.7.3 from another source. Just rename the OC folder in your ESP and put another one there.
EDIT:
Perhaps try a triple NVRAM Reset (until you hear the fourth chime) in case something in the NVRAM need to be discarded.
If the issue is still present, try OC v0.7.3 from another source. Just rename the OC folder in your ESP and put another one there.
EDIT:
Perhaps try a triple NVRAM Reset (until you hear the fourth chime) in case something in the NVRAM need to be discarded.
Last edited:
yes, that's the difference. Even if I have no Linux Disk in my setup at the moment (I put one in from time to time) I told ConfigFactory I have Linux. So it setup to add the driver to OC.
But this issue is fixed now, thanks at @Dayo