Sidebar Sidebar
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

BTW, the next version will have a FileVault related option in ConfigFactory but I don't expect this will solve your issue.
You could still give it a shot though

EDIT:
Macschrauber said:
it just resets hard the Mac if chainloaded via RefindPlus.
Click to expand...
Out of interest, when you run OpenCore directly, do you use the BootBlesser to bless or do you bless directly and if directly, which file do you bless?
 
Last edited:
I copied the standard config.plist from the opencore thread. No big difference.

also I tried to boot my usb backup clone what is also filevault formatted With standard settings. Almost same Reset.

{almost} explained: with Dayo Setting the boot chime is 100% Audio Volume
the boot chime audio volume stored in my nvram is about 20% Audio Volume

so theres an audible difference in restarting thru standard and thru Dayo settings.

still thinking about an issue with FileVault. Dont have a regular Mojave installation here, its my home machine and I am limited. Much more stuff in the workshop to test but that will happen next week.

a Partition with the DosDude Mojave Installer and a Partition with El Capitan both boot just fine with chainloaded OpenCore and standard settings.
 
I see.

I was thinking about the issue and could only think of two situations where chainloading from RefindPlus would result in a different outcome to running directly. Not saying there aren't others but just what I could think of:
  1. RefindPlus uses the Bootstrap efi as entry point and it could be that some bug in OpenCore leads to a crash with this when Filevault is active.
  2. RefindPlus is loading some driver that causes FileVault to choke and crashes OpenCore.
As you are using the BootBlesser when going direct and it is working, the first is not the case.
So, try running RefindPlus without any drivers (rename the drivers folder) and see what happens.
 
Dayo said:
I see.

I was thinking about the issue and could only think of two situations where chainloading from RefindPlus would result in a different outcome to running directly. Not saying there aren't others but just what I could think of:
  1. RefindPlus uses the Bootstrap efi as entry point and it could be that some bug in OpenCore leads to a crash with this when Filevault is active.
  2. RefindPlus is loading some driver that causes FileVault to choke and crashes OpenCore.
As you are using the BootBlesser when going direct and it is working, the first is not the case.
So, try running RefindPlus without any drivers (rename the drivers folder) and see what happens.
Click to expand...


Bingo! I renamed the RefindPlus Drivers Folder and now chainloaded OpenCore boots my FileVault Mojave Partition.

OpenCore is active

Code: 
mp31sins:~ admin$ opencoreversion
4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version    DBG-062-2020-10-05

there's just one file in the drivers_x64 folder: x64_OsxAptioFix3Drv.efi
 
  • Like
Reactions: JedNZ and Dayo
Great. I have filed a bug report on the OpenCore Project.
Update: It got closed abruptly!
 
Last edited:
I have found something else:

If I allow reFindplus to scan "PreBoot" and if I disable the x64_OsxAptioFix3Drv.efi driver

I can use reFindplus to boot directly into my FileVault Mojave. I have to select "PreBoot" as expected.

Have DosDude's APFS Patch in my Mac Pro 3,1 Firmware if that counts.

btw: What is the purpose for 64_OsxAptioFix3Drv.efi?

as for first quick glance ReFind works as expected (or better if I count FileVault)
 
Hi,

I have a 3,1 Mac Pro, with a new (to me) Kepler GTX780Ti. Mojave on a HFS+ partition on a AHCI PCIe SSD, El Capitan and Snow Leopard on a separate HDD, and legacy Windows 10 on another HDD.

I ran through the installation steps as indicated on the first page, and installation seemed to work well (I chose to install on the EFI partition of the El Cap/Snow Leopard HDD). I softblessed RefindPlus, but I just reboot into a black screen. Same thing happens when I softbless Opencore. If I just press enter at the black screen, system reboots and I go straight back into Mojave as expected (since it was a softbless).

Can anyone point out where I've gone wrong here? I suspect somewhere in the Config settings?

Thanks a lot!
 
r6mile said:
Can anyone point out where I've gone wrong here?
Click to expand...
See the requirements in the guide: (OUTDATED ... REFER TO CURRENT VERSION IN POST 1)

Screen Shot 2020-10-31 at 15.58.30.jpg
 
Last edited:
r6mile said:
But I was under the impression that the whole point of using this method is to enable a boot screen for cards that can't natively show it?
Click to expand...
It is a work in progress for Kepler GPU's. We need testers. If you want to contribute let @Dayo know.
 
startergo said:
It is a work in progress for Kepler GPU's. We need testers. If you want to contribute let @Dayo know.
Click to expand...

Ok thank you. It sounds then like perhaps I didn't make the best choice of graphics card - I chose a Kepler card because those have Metal but also work under El Capitan, which I want to keep as a back-up as it's officially supported; I know that modern AMD cards can't do El Capitan. I believed that I could still get a boot screen through OpenCore/Refind through.
Perhaps I should have stuck to getting a GTX680 and flash it...
 
Refindplus / OpenCore has advantages even with a UGA BootScreen GPU. Like selecting different instances of openCore, Booting Linux etc etc.

After some trouble with FileVault I may let it active even if I have a Kepler GPU with bootscreen.
 
r6mile said:
Hi,

I have a 3,1 Mac Pro, with a new (to me) Kepler GTX780Ti. Mojave on a HFS+ partition on a AHCI PCIe SSD, El Capitan and Snow Leopard on a separate HDD, and legacy Windows 10 on another HDD.

I ran through the installation steps as indicated on the first page, and installation seemed to work well (I chose to install on the EFI partition of the El Cap/Snow Leopard HDD). I softblessed RefindPlus, but I just reboot into a black screen. Same thing happens when I softbless Opencore. If I just press enter at the black screen, system reboots and I go straight back into Mojave as expected (since it was a softbless).

Can anyone point out where I've gone wrong here? I suspect somewhere in the Config settings?

Thanks a lot!
Click to expand...
Did you test booting from all the ports of the GPU? Maybe one of the ports works.
 
I'm totally thrilled how RefindPlus works :)

have a 4.1 with 5.1 Firmware, RX580 with GOP

and RefindPlus / OpenCore setup with bootscreen.

now I flashed (for test sake) another Mac Efi Firmware (with a different serial number). The Firmware was rebuilt with a complete empty nvram.

I had sworn (as the blessing is in nvram) that RefindPlus does not show up, but it started like nothing happened.

How on earth it has survived even a Firmware Change of the Mac Pro?

In other words It should be possible to throw the ssd just in another Mac Pro (with correct firmware) and RefindPlus is running?

Was on a AHCI Apple SSD Blade if that counts.
 
Macschrauber said:
How on earth it has survived even a Firmware Change of the Mac Pro?
Click to expand...
A fallback efi file (BOOTx64.efi) placed in the correct location ("EFI/BOOT" folder of an EFI Partition) will be loaded if there is no boot file designated in the NVRAM.

For MyBootMgr, you should go in and run the "Finalise Installation" steps.
 
Last edited:
  • Like
Reactions: JedNZ and Macschrauber
Dayo said:
A fallback efi file (BOOTx64.efi) placed in the correct location ("EFI/BOOT" folder of an EFI Partition) will be loaded if there is no boot file designated in the NVRAM.

For MyBootMgr, you should go in and run the "Finalise Installation" steps.
Click to expand...

is this the 1st Disk the firmware finds? Bay1 of internal sata?

Or in other words, where should one install RefindPlus to survive a nvram reset?
 
Macschrauber said:
where should one install RefindPlus to survive a nvram reset?
Click to expand...
Where the guide in Post 1 recommends that you should install to ... any EFI partition.

That's why my previous writes about "EFI/BOOT" folder of an EFI Partition and not "EFI/BOOT" folder of the EFI Partition of Bay/Disk XYZ.

This of course assumes that you don't have multiple fallback efi files in multiple EFI Partitions.
 
Last edited:
Macschrauber said:
is this the 1st Disk the firmware finds? Bay1 of internal sata?

Or in other words, where should one install RefindPlus to survive a nvram reset?
Click to expand...
Test this and tell us the result.
Put a RefindPlus in each EFI Partition, each with a refind.conf with a unique manual stanza that indicates which bay it is installed to.
Reboot the computer, zap the pram twice, then see what gets booted.
 
joevt said:
Test this and tell us the result.
Put a RefindPlus in each EFI Partition, each with a refind.conf with a unique manual stanza that indicates which bay it is installed to.
Reboot the computer, zap the pram twice, then see what gets booted.
Click to expand...
This is what I wanted to do.

I often have to setup a Mac for non-tech-save-people.

They read somewhere that zapping nvram could solve a problem and do it.

next day they call me to fix, so better it is bullet proof.
 
After deep nvram reset:

To my surprise the BOOTx64.efi was chosen what was in the last bay (4) located in EFI/Boot of the disk in Bay 4

it was on old OC Verision 0.59 I almost forgot I had on it.

I make Icons in the EFI Partitions to distinguish them

IMG_2024.JPG
 
Hi, Big fan of this effort so far! However, need help with .63 and Big Sur RC1


CMP 2009 5,1 2x6 core 3.5GHz and 96GB RAM. Booting of SSD and also have an NVME. I can install Big Sur without refindplus with an OC setup I already have working, but want to get refind plus working if possible to do the same. with both old and re-attempt with .63 version, I can install my EFI, but can’t get big sur to continue installation after setup (reboots to apple with no progress bar).

It seems like the .63 installer is building corrupted utility apps. My old refindplus apps work fine… I can’t get through step 2 of the install setup…

1) Download .63 refind plus from davo site
2) open MyBootMgrSetup from .dmg
3) click notice that says to finalize and you go into circular setup of install, click notice, re-install
4) don’t click notice
5) Run ConfigFactory Tool. Specify the name of volume (I do want it installed on my boot volume so chose it.. “Mojave 840”)
6) Since I had previously disabled SIP in refindplus from prior install, so I skipped this step of booting to recovery
7) Run DeployEFI Tool with right-click/open and result is “The command exited with a non-zero status.” If I click Edit I get “”DeployEFI” can’t be opened because it is from an unidentified developer”
8) checked csrutil status and it is not 100% disabled. “BaseSystem Verification” is enabled and a warning about an unsupported configuration.
9) Reboot to attempt recovery mode with command-R. unless reboot chime cycle
10) let it boot to prior refind/OC setup, hit space for auxiliary, booted to recovery, disable sip, reboot back to OS and continue refindplus install
11) Run DeployEFI Tool with right-click/open and result is “The command exited with a non-zero status.” Tweak EFI does the same.. Only ConfigFactory seems to work.
12) verified csrutil stats is ‘disabled’
13) removed old EFI folder from EFI partition and rebooted into Mojave “stock setup”
14) Run DeployEFI Tool with right-click/open and result is “The command exited with a non-zero status.”

Other Questions:
-How does one disable debug log mode as I’m afraid the EFI volume will fill up and run out of capacity at some point in the future?
-Why is SIP not totally disabled with refindplus SIP toggle? What should be entry in config file for full disable in Big Sur?

Thanks!
 
johnwillsey said:
-How does one disable debug log mode as I’m afraid the EFI volume will fill up and run out of capacity at some point in the future?
-Why is SIP not totally disabled with refindplus SIP toggle? What should be entry in config file for full disable in Big Sur?
Click to expand...
Before dealing with top level issues, you need to sort out some basic ones resulting in issues with the Helper Tools.
Wipe things out and start over while adhering to this:
Screen Shot 2020-11-08 at 20.13.54.jpg

if you do have issues after strictly following this, then such can be resolved.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back