Thanks for the brain dump of some extra info! I haven't had a chance to compile a test version of the driver and see if I can find out where it hangs and why.
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
Well after all the going back and forth with my MacPro5,1 realizing the HD booted MacOS either Mojave or Catalina does not cooperate well with a MAcOS SSD I kept getting messages of incompatibility thinking it was just the MacOS on the HD drive. I sorted that out now I have Catalina on SSD with Dosdude patcher and no Opencore in the EFI. On the other SSD I have Monterey with Refind chainloading OCLP. I was able to bless the Monterey EFI partition from the Catalina drive no issues. The boot sequence goes well Refind screen is there and it starts up Monterey but then the Kernel boot sequence stops at the last EB pre kernel message and never continues booting the kernel. If I hold down the option key during boot then choose EFI then Monterey the booting sequence is perfect boots right into Monterey. I have logs I can share but from what I see I don't see any error in them. Is it possible OCLP isn't no playing well with Refind? I have zipped up 3 logs. This is not the DBG version running for refind but rather the release version. Thanks for all the help and sorry about all the PM's I know it was too many, just couldn't get past the one drive recognizing the other and both drives were formatted correctly as APFS.
I always get the question about whether OpenCore is not working because of the fact that it is chain-loaded and I suppose I need to add something to Post 1 so I can just point people to this.
Short answer is that what happens in OpenCore basically has nothing to do with it being loaded by RefindPlus and anyone can check this by simply blessing OpenCore itself and letting the firmware load it instead of RefindPlus.
Short answer is that what happens in OpenCore basically has nothing to do with it being loaded by RefindPlus and anyone can check this by simply blessing OpenCore itself and letting the firmware load it instead of RefindPlus.
Last edited:
Seems you suggest you have basically done this and it works but it doesn't from RefindPlus.
That is definitely strange. Unfortunately, I can't look at this. AFAIK, there should be no difference.
You can PM Macschrauber who runs multiple OCLP via RefindPlus for advice.
I may have worded that wrong Opencore does load from refindplus it’s the pre kernel boot that gets stuck and never continues loading the kernel when chainloading.
I’ll see if Macschrauber is loading Monterey. Thanks.
BTW, since you seem to have a GPU that can show the bootscreen, I am not sure whether you know that there is a setting you can use that will always show this without needing the CMD + R keypress if you prefer? I don't know it off the top of my head but you can try a search.
Basically means you can remove RefindPlus from your boot chain but still have multiple OC instances (if you want) and be able to boot into Legacy Windows etc.
Basically means you can remove RefindPlus from your boot chain but still have multiple OC instances (if you want) and be able to boot into Legacy Windows etc.
Booting to the bootpicker menu (with supported graphics):
Code:
sudo nvram manufacturing-enter-picker=true && sudo rebootJust pulling my hair out again all day/evening, lol trying to figure out what is going on here. I have successfully been running "Macschrauber" DBG version AN. He didn't have the REL version handy so I figured out which version he is running, v0.3.13.2 AN, I don't want logs in the EFI accumulating.
If I swap out DBG for REL version there is no RP GUI goes straight to Opencore. Decided to try the latest release AP same issue as AN only the DBG version of AP is loading GOP and not the REL version.
The only way to prove its not me and some major brain freeze on my part is to to see if Macschrauber can try the REL version of AN.
The graphics card working perfectly in the DBG version is the EVGA GT740 4GB also the EVGA GT710 gets to the RP GUI but gets to a dark screen with mouse pointer at the desktop, I'll have to see if I need some flag in the Nvram/add for that part.
The MSI Aero ITX RX560 does not get to the RP Gui yet it does on the MacPro3,1 with an older REL version v0.12.0.L
If I swap out DBG for REL version there is no RP GUI goes straight to Opencore. Decided to try the latest release AP same issue as AN only the DBG version of AP is loading GOP and not the REL version.
The only way to prove its not me and some major brain freeze on my part is to to see if Macschrauber can try the REL version of AN.
The graphics card working perfectly in the DBG version is the EVGA GT740 4GB also the EVGA GT710 gets to the RP GUI but gets to a dark screen with mouse pointer at the desktop, I'll have to see if I need some flag in the Nvram/add for that part.
The MSI Aero ITX RX560 does not get to the RP Gui yet it does on the MacPro3,1 with an older REL version v0.12.0.L
Last edited:
Please raise an issue on GitHub for such RefindPlus specific items.
EDIT
In the meantime, use the SwitchRunMode app to switch OpenCore to REL and leave RefindPlus as DBG. It will take scores of boots into RP for the log files to pile up to a stage where they become an issue; even if you never clear them out at intervals.
EDIT
In the meantime, use the SwitchRunMode app to switch OpenCore to REL and leave RefindPlus as DBG. It will take scores of boots into RP for the log files to pile up to a stage where they become an issue; even if you never clear them out at intervals.
Last edited:
The primary purpose of a debug file is to produce logs for debugging and it does this unconditionally.
I don't think you would run the OpenCore DBG file for day to day use as an example.
You should therefore similarly run the REL version for day to day use.
I don't think you would run the OpenCore DBG file for day to day use as an example.
You should therefore similarly run the REL version for day to day use.
hello,
i've been successfully running a MyBootMgr v067a / Mojave setup on my 3,1 for the past year. thank you very much @Dayo for putting together and maintaining this utility!
i have some minor issues though, such as occasional graphical glitches in Final Cut Pro, and i am hoping to update MyBootMgr to see if that helps. since it's been a year, the setup process is not exactly fresh in my memory anymore so i have some questions...
in trying to follow the update instructions very literally, i've done the following:
1. step 2 of STAGE 1 - PRE INSTALLATION: downloaded the new version and run MyBootMgrSetup (since only step 2 was mentioned, i'm assuming for the update i don't need the natively booted macOS and can do this from within my OpenCore Mojave - is that correct?)
2. run FetchSetup to back up my existing setup
but the following steps seem to assume i now have a /Users/Shared/MyBootMgr/EFI folder, which i don't. am i meant to run the new ConfigFactory first?
i've been successfully running a MyBootMgr v067a / Mojave setup on my 3,1 for the past year. thank you very much @Dayo for putting together and maintaining this utility!
i have some minor issues though, such as occasional graphical glitches in Final Cut Pro, and i am hoping to update MyBootMgr to see if that helps. since it's been a year, the setup process is not exactly fresh in my memory anymore so i have some questions...
in trying to follow the update instructions very literally, i've done the following:
1. step 2 of STAGE 1 - PRE INSTALLATION: downloaded the new version and run MyBootMgrSetup (since only step 2 was mentioned, i'm assuming for the update i don't need the natively booted macOS and can do this from within my OpenCore Mojave - is that correct?)
2. run FetchSetup to back up my existing setup
but the following steps seem to assume i now have a /Users/Shared/MyBootMgr/EFI folder, which i don't. am i meant to run the new ConfigFactory first?
Correct. Updates can be done while booted via OpenCore but if you haven't updated since 067 however, the current version will most likely insist you run while natively booted and suggest that you reset your NVRAM.
Correct. Will add this to the instructions.
Hi Dayo,
I updated to v080a because I sometimes had USB und Bluetooth glitches in v075d. After starting OC (default instance) the system freezes. The last two messages are
OC: Watchdog status is 1
Halting on critical error
Running the Mojave instance via RefindPlus does not work either. I have to reset NVRAM to boot into Mojave.
I updated to v080a because I sometimes had USB und Bluetooth glitches in v075d. After starting OC (default instance) the system freezes. The last two messages are
OC: Watchdog status is 1
Halting on critical error
Running the Mojave instance via RefindPlus does not work either. I have to reset NVRAM to boot into Mojave.
It is impossible to figure stuff out without logs.
In any case, the next version is due after the weekend so, perhaps roll back to what you had before and try the next version at that time. If you have issues then, report this and include the log files needed to understand the issue.
ConfigFactory, RefindPlus and OpenCore are all set to debug mode by default and generate log files.
In any case, the next version is due after the weekend so, perhaps roll back to what you had before and try the next version at that time. If you have issues then, report this and include the log files needed to understand the issue.
ConfigFactory, RefindPlus and OpenCore are all set to debug mode by default and generate log files.
As @Dayo said, check your logs. Most of the time when I get that issue it’s because of a missing kext file. But the logs will set you free.
MyBootMgr does not and cannot boot anything. It is simply a process of setting up two boot managers, RefindPlus and OpenCore, so that they work together.
RefindPlus and OpenCore can boot stuff (that's what they do) and I assume you meant that you have tried to boot with one or the other of them. Which one of the two was it?
I suspect OpenCore given the mention of text output on the screen. Well, OpenCore does not support Legacy Windows. If it was RefindPlus however, then that is an issue. Please go to GitHub and raise this there. The link is in Post 1 under support options or at least post the logs here to start with. It is not possible to proceed without logs.
EDIT: On second thoughts, it can't be OpenCore since it probably would not display Legacy Windows.
Btw, if you are running in debug mode, there will always be logs unless you are using the Not-Recommended HFS Type implementation. You need to mount the ESP and look there.
RefindPlus and OpenCore can boot stuff (that's what they do) and I assume you meant that you have tried to boot with one or the other of them. Which one of the two was it?
I suspect OpenCore given the mention of text output on the screen. Well, OpenCore does not support Legacy Windows. If it was RefindPlus however, then that is an issue. Please go to GitHub and raise this there. The link is in Post 1 under support options or at least post the logs here to start with. It is not possible to proceed without logs.
EDIT: On second thoughts, it can't be OpenCore since it probably would not display Legacy Windows.
Btw, if you are running in debug mode, there will always be logs unless you are using the Not-Recommended HFS Type implementation. You need to mount the ESP and look there.
Last edited: