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
You dont have to install a multiboot linux version. Use a dedicated drive for linux only. Refindplus will let you load it. I use mint and also a grml boot stick.
before using bootloaders like opencore its recommended to make a firmware backup to flash back a known good rom.
I made a tool for dumping and basic analyzing: https://www.dropbox.com/s/jh4unzd7gd4n5me/Macschrauber's CMP Rom Dump.dmg?dl=0
@Dayo I'm getting a build error.
I run ConfigFactory 0.7.1d (currently on 0.7.0b) with manual options (and then later using the default config) and always get to 94% with Build error at Buildstep: 44
I have double checked that SIP is disabled (first time via RFP main screen, second time via booting into Recovery).
I run ConfigFactory 0.7.1d (currently on 0.7.0b) with manual options (and then later using the default config) and always get to 94% with Build error at Buildstep: 44
I have double checked that SIP is disabled (first time via RFP main screen, second time via booting into Recovery).
Attachments
Last edited:
If I add or replace one instance of OC with the OC folder of OCLP it kinda works. Some patches seems to be missing (like wifi).
so my conclusion: I need this boot.efi (/Volumes/EFI/System/Library/CoreServices/boot.efi) what olcp generates into root of the esp volume.
This overrides the boot process completely.
Is there a way to handle this?
edit: I was wrong, this boot.efi is just to load OC and contains no patches. So it can be removed and MyBootMgr can handle oclp instances correctly. This no wifi thing must have another reason.
I use this to run Big Sur on a Mac Pro 3,1 aside Linux, legacy Windows and Mojave.
that was described here by @khronokernel
macOS 11 Big Sur on Unsupported Macs Thread
The boot.efi you see is simply a bootstrap for EFI/OC/OpenCore.efi, this is done because on Macs there are 2 standard locations boot loaders are scanned at on OS start: - EFI/BOOT/BOOTx64.efi - System/Library/CoreServices/boot.efi The partition type does not matter whether FAT32 or HFS+...
forums.macrumors.com
Last edited:
You actually don't need SIP enabled to use ConfigFactory and if an issue is SIP related, only relevant to app such as BootBlesser, it will be mentioned.
Anyway, will post a fix for this issue shortly
You can replace the OC folder with any you want or add as many as you wish to what is there (just need to add to RefindPlus config)
Yes, did that with MartinLo‘s package and worked like a charm.
Just got confused by this boot.efi (what is just a bootstrap) and as I knew that from MP1,1 and 2,1 patches running El Capitan I combined false information
So, to second that: MyBootMgr can load an instance of OCLP fine to run Big Sur (for example) on unsupported Mac Pro 3,1.
Can you clarify where WIFI is missing?
Both OCLP created config and those created by MyBootMgr should have WIFI patches in place for supported units (MyBootMgr supports fewer units)
yes, I have stock Wifi for Mac Pro 3,1 (BCM94321mc)
in Big Sur 11.4 I get no Wifi with OCLP 0.14 (I need this version as latebloom boot logs work)
in Big Sur 11.4 I get Wifi with OCLP 0.23 (with this version latebloom boot logs are missing)
has nothing to do with RefindPlus, its the same when oclp instances gets booted directly.
It's just a side note, don't need Wifi at all. Maybe that 0.14 was not built for 3,1 as I had it on my Big Sur SSD what I made on a 5,1. I keep it as it is for those Latebloom Logs. (am working a little on a latebloom reporting tool).
I believe the only reason OpenCore can't be used alone is because of some rigid design choices that limits the kinds of stuff it can boot. Maybe OpenCore should have a plugin feature that can add other items to the boot picker.
I haven't used OpenCore much so I don't know what all the limits are. Does it know about legacy BIOS booting on old Macs? What's missing for being able to boot Linux? Does OpenCore support chain booting other boot loaders? Can it boot RefindPlus (the opposite order of MyBootMgr)?
One issue with OpenCore is that DSDT/SSDT changes are applied to all boot options so you have to make sure the changes are compatible with all the OSs you want to boot.
OpenCore can be used, and is used by the majority of users, alone. Perhaps you meant it can't be so used for multiple instances of OpenCore?
Anyway, the only restrictions on what it can boot are:
- It does not support booting legacy BIOS setups
- So, no legacy windows or similar
- There is an open item to add this on the tracker but is tagged as "Low Priority"
- It does not ordinarily allow booting another OpenCore Instance
- You can't chain-load another OpenCore instance unless you disable signing and build your own as documented in the OpenCore manual.
Legacy BIOS - See above
Missing for Booting Linux - Nothing. It boots Linux
Supports Chainloading - Yes, apart from other OpenCore instances. Every time an OS is booted, it is a bootloader being chain-loaded. The firmware does this, RefindPlus does this and so does OpenCore. That some other bootloader is actually there instead is not visible to what is calling it as long as it has the correct name from the UEFI specs. That's why the firmware will happily load RP or OC and same applies to those.
Boot RefindPlus - See above. Actually, this was the initial way to use Legacy Windows with OC. I just turned it on it's head in MyBootMgr as I also wanted to boot multiple OC instances. Initially to have instances with GPU Acceleration (Mojave) or without (HiSierra) but since moved on to other reasons and now keep four OpenCore Instances:
- OC - Current Version with GPU Acceleration
- OC_ALT - Current Version without GPU Acceleration
- OC_Dev - Builds of the GitHub Code for Testing
- Can easily misconfigure something here, in which case recovery means simply rebooting and selecting another instance.
- No need to pull disks, reset NVRAM etc
- OC_WRK - Some old known working implementation of OC (I think it is v0.5.9)
- Just because I sometimes lose discipline and develop in the three previous instances concurrently
- I can probably delete this since I can also get in with RefindPlus directly but just leave it there
For this, I use a
RP (Stable Version) -> OC -> RP (Dev Version) setup. If RP Dev blows out, it is simply reboot and carry on. Only restriction here is that another OC instance can't be added to that chain as mentioned earlier.Hey peeps,
I have a little problem:
The following kexts were found on your system: - Lilu.kext - WhateverGreen.kext Please uninstall these kexts to proceed Opencore will inject these as required instead
I deleted the Kext's in my OC config but they are still apparently installed.
Can you offer some advice to a noob like me ?
I have a little problem:
The following kexts were found on your system: - Lilu.kext - WhateverGreen.kext Please uninstall these kexts to proceed Opencore will inject these as required instead
I deleted the Kext's in my OC config but they are still apparently installed.
Can you offer some advice to a noob like me ?
You have installed Lilu and WhateverGreen on your system and now trying to set OpenCore up, which will also inject copies of those kexts, leading to conflicts in such a situation.
I'll have thought the message is clear that you need to uninstall them from your system to proceed with Configfactory so that OpenCore is left to inject them instead. At least if you want to use the ConfigFactory app, which will not run if either of those two kexts are detected as being already installed (to avoid the mentioned conflicts).
You will need to check for the kexts where you installed them to (most likely in your "Library/Extensions" or "System/Library/Extensions" folders).
Do a web search on how to uninstall kexts if not familiar with the procedure, although I presume you must be to have installed them originally.
I'll have thought the message is clear that you need to uninstall them from your system to proceed with Configfactory so that OpenCore is left to inject them instead. At least if you want to use the ConfigFactory app, which will not run if either of those two kexts are detected as being already installed (to avoid the mentioned conflicts).
You will need to check for the kexts where you installed them to (most likely in your "Library/Extensions" or "System/Library/Extensions" folders).
Do a web search on how to uninstall kexts if not familiar with the procedure, although I presume you must be to have installed them originally.
Last edited:
The message is extremely clear, the thing is I am somewhat sure I unloaded them, even force removed them via terminal to be sure.
Does the installer perhaps detect downloaded kext's that are not loaded? I do have copies of the kexts on my harddrive
Does the installer perhaps detect downloaded kext's that are not loaded? I do have copies of the kexts on my harddrive
Last edited:
No, it checks whether they are active/loaded by running "kextstat".
Kexts are loaded into the kernel at boot stage. Once boot is completed, the kext files in S/L/E and L/E are not used, but the instances added to the kernel. Simply deleting those files will not remove them from the kernel and you need to reboot without them so that they are not loaded into the kernel to start with.
You can check if they are loaded by running
kextstat | egrep -i 'lilu|whatevergreen'. If the kext is loaded, you will get an output string.
Last edited:
Just as an FYI: you can simplify that by using egrep -i:
kextstat | egrep -i 'lilu|whatevergreen' will display both with fewer commands, and using -i means the user won't be bothered with case-sensitivity (which some folks might overlook if they're not copy/pasting).Also, it's possible to avoid grep altogether:
kextstat -b 'as.vit9696.Lilu' && kextstat -b 'as.vit9696.WhateverGreen' will work nicely, too (case-sensitive, unfortunately).I am going to check it after work, found a nice little python script that checks loaded kexts and gives you path, to tell me what I might have missed: https://gist.github.com/erikng/d85b17e6e13fd8dcad7cf51d1c6b3a1c
Works well at work, so I will find the little trickster. I've played with my OC config so much that I have kind of forgotten everything I have done at this point and its possible I installed it somewhere else and forgot.
Edit: Remote Desktop'ed to my Mac at home, found the little bastards. Hopefully things can go smooth now
Works well at work, so I will find the little trickster. I've played with my OC config so much that I have kind of forgotten everything I have done at this point and its possible I installed it somewhere else and forgot.
Edit: Remote Desktop'ed to my Mac at home, found the little bastards. Hopefully things can go smooth now
Last edited:
So, this is weird, the kexts are shown as loaded on /Library/Extensions but the Kexts are most definitely not there. Is it possible they are loaded in the kernel cache and somehow the Kernel is not getting updated? (After restart ofc, but I got an idea what is up so gotta test it out)
Last edited:
You need to provide clearer information:
- Have you actually rebooted after deleting the kexts?
- What does the
If it is all getting too complex, just make sure you run things while on a natively supported Mac OS version that does not require potentially conflicting mods to function. You don't have a signature showing your details ... this would be helpful.
- Have you actually rebooted after deleting the kexts?
- What does the
kextstat | egrep -i 'lilu|whatevergreen' command show after a reboot?If it is all getting too complex, just make sure you run things while on a natively supported Mac OS version that does not require potentially conflicting mods to function. You don't have a signature showing your details ... this would be helpful.
It's all good, I will figure it out, I am pretty stubborn. Worst case is I will just do a clean install & fresh OC. I got my current OC config saved as it was dreadful to get TB3 running properly.
It's just a 2009 Mac Pro with a single socket tray 3.33 GHz 6 core Xeon, 64 GB of RAM, RX 580, TB3 Card.
Last edited: