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
No problems to report with 068a. FWIW though, the Acidanthera patches didn't have any negative effects in Mojave; just Big Sur.
P.S. Still having issues with physical drive limits in TweakESP. Was wondering if you'd made any leeway in resolving that?
Last edited:
No ... not looked at.
Once an issue that I don't face goes back a page or so, it's gone for good if it was not immediately sorted I'm afraid.
Might create a bugtracker on GitHub for MyBootMgr but major changes should be slowing down so doesn't seem really needed.
It's not really an issue per se; one just has to physically disconnect a drive once the limit is reached. If no major changes to RP/OC are in the pipeline, I can leave well enough alone.
Dayo, wanted to follow up and let you know the MyBootMgr update to v068 did indeed fix my GXT 680/RefindPlus issue. I'm now booting just fine with RefindPlus blessed and everything seems to be working just as expected. Thanks!
I do have one small suggestion. When ConfigFactory is asking if you'll be booting other OS's the No response is always on the right until you get to Windows. I personally never plan to run Windows on my cMP but have accidentally responded Yes a number of times by assuming the No option would remain consistent. Not a big deal but thought I'd pass it along.
Something odd happened with 068b. Rebooted after deploying and lost one of my vanilla MacOS options. Decided to run CleanNvram option from RP and the computer just froze. Had to hard reboot then triple clean NVRAM. Just wanted to let you know. Last entry in the log for v0.13.2.AC:
Other than that, seems to be working well on my cMP5,1. Haven't had the opportunity to test with the new audio fixes on the cMP3,1. Hopefully soon.
Looked at this some more as I have been getting similar and it appears the issue is that due to recent memory management optimisations, RefindPlus, especially the RELEASE build, is now significantly faster and some disk volumes may not be fully initialised when RP is checking volumes. It either doesn't see them to start with, or cannot access the filesystem and they appear to it as not bootable. The upshot is that they get skipped on the main screen either way.
Added a note to POST 1 => OTHER CONSIDERATIONS on what to do on this.
Interestng observations, Dayo.
Another thing I've noticed is that RP now displays 2 vanilla options for Big Sur, whereas previous versions showed just one. Not sure if RP is picking up both data partitions at boot. How can I reconfigure RP to just show one?
Another thing I've noticed is that RP now displays 2 vanilla options for Big Sur, whereas previous versions showed just one. Not sure if RP is picking up both data partitions at boot. How can I reconfigure RP to just show one?
Two questions:
- Can anyone confirm if it’s safe to apply the Mojave 10.14 Security Update 2021-003 using RefindPlus/OC Chainloader?
- Any problems upgrading to Big Sur 11.3 using RefindPlus/OC Chainloader, and if so are they the same problems as plain OpenCore users are experiencing with hangs, freezes and KPs , and possible issues with NVMe or SSD in PCIe adapters as discussed here?
1. It should work fine.
2. I wouldn't attempt it. Even if you don't have a PCIe NVME or SSD, alterations to the way PCI devices are handled by 11.3 is questionable. This includes USB3 PCIe cards, network cards, etc. If you're on a cMP5,1, then 11.2.3 is the last stable release for the time being.
Edit: just ran the latest Mojave 2021-003 sec. update via RefindPlus/OC v069. No problems whatsoever.
Last edited:
ConfigFactory gets information by automated hardware probing supplemented by asking users questions about their Mac. The automated hardware probing is currently fairly basic but the next version will have this enhanced significantly.
The current level of hardware probing allows ConfigFactory to setup WIFI up for orthodox stock setups but the next release will cover other setups such as requested above along with a lot of other things.
This enhanced hardware probing will leverage snippets of code from the OCLP amended to allow generating config files consistent with the "minimal" principles of the main OC thread on this forum. It does however require that Python 3.8+ is available on the host Mac.
If Python 3 is not available, ConfigFactory will still continue and transparently provide a working config as before. The difference will be that some of the additional items will not be there or more kexts used (kexts such as Innie will not be needed if Python 3 is available but will be used if not) or more questions asked (some things asked before can now be detected automatically).
Installation is not required as ConfigFactory will use previously installed instances of Python 3, if available, or a bundled instance otherwise. Either way, Python 3 will always be available.
Last edited:
found a glitch in config factory of v070, started from scratch, as always
this is the 1st message I got
this is the 1st message I got
That is an debug setup I use that was not defined properly before checking ... Fixed and re-uploaded. Thanks.
Btw, if "from scratch" means deleting previous preferences in Application Support and such, note that this action is only useful for a feel good factor as it has no bearing on your outcome. Best to leave such alone.
superb,
yes, I move away the prefs file in Application Support plus the Mybootmgr files in shared.
As a good tester I act like a new user and wipe the old installation
yes, I move away the prefs file in Application Support plus the Mybootmgr files in shared.
As a good tester I act like a new user and wipe the old installation
As said, it makes no difference and actually, a good tester should leave alone since the tool should take care of this as needed. But if it makes you feel better, then continue by all means. Just irrelevant to any report.
Last edited:
I'd like to get Boot Icons for the Recovery Partitions what I can set human names to (like Mojave Recovery).
adding apple_recovery to showtools
gives a list "Recovery HD, Recovery, Recovery" for different MacOs Versions I have on my disks.
I'd prefer Boot Icons like I have for Linux, Windows, MacOs
can this be configured?
adding apple_recovery to showtools
gives a list "Recovery HD, Recovery, Recovery" for different MacOs Versions I have on my disks.
I'd prefer Boot Icons like I have for Linux, Windows, MacOs
can this be configured?
I suppose it would be useful for RefindPlus to scan for a version.plist file (or whatever it's called in each situation) and display that version number next to each macOS and recovery option that is found (as long as that version number is not already included in the volume name - don't want the text to be redundant). If the recovery partition has an icon (it usually doesn't), then it might be useful to show that as well - perhaps with an optional recovery badge icon.
Currently not. Recovery is handled by a tool which always has a fixed name.
The suggestion by @joevt is a possibility but would think that would probably be something that should be done upstream in rEFInd itself instead.
EDIT:
I see that OC adds the OS version to the name. That might be worth trying to replicate.
Last edited: