MP 1,1-5,1 RefindPlus|OpenCore by MyBootMgr

[Dayo]

Searched this thread and re-read the first post but didn't see much regarding Filevault activation post RP/OC install.

I don't use it and didn't have anything to say on the subject.
EDIT: Added an item to OTHER CONSIDERATIONS

I'd like to turn FV on in Mojave, and vaguely remember an option for FV being presented in MyBootMgr 066f.

Don't rely on vague recollections. It will take you all of two minutes to run it again and verify things.

I'm wondering if I need to rerun MyBootMgr from the start, or will the option to reuse existing settings provide the option to enable FV compatibility?

When you think about it properly, I am sure you will conclude that since you originally set things up for a certain setup and now want to make significant changes, it stands to reason that you will be best served to rerun the config setup to make sure what you now have is consistent with your new set up.

It's not as if running ConfigFactory is some major or time consuming undertaking and needs careful consideration before setting out to run it right?

Lastly, I assume MyBootMgr will modify OC's config file to add all necessary keys and NVRAM entries to allow FV's preboot loader to start?

RP should boot into FileVault without issue and I presume OC would as well but as said, I don't use this feature and have not tested it by myself. Feedback from others is that it works as expected.


Anyway, as with any such changes, you simply have to follow the basic rule of making changes:

• Prepare a recovery position
• Implement your changes
• Test your changes

If it's all ok, fine. If not, fall back on your recovery position and try to figure things out.

If it doesn't work, it might be that OC needs some specific setting which you will need to ask about in a more appropriate thread. You can tag me so that I can follow to see whether there is and adjust MyBootMgr accordingly.

 

[amstel78]

Hi @Dayo, quick question. I'm getting a weird error with TweakESP whenever a certain USB drive is plugged in.

Checking that drive via diskutil info/Volumes/"Drive Name", its volume and disk UUID are unique and don't match anything else. Unmounting the drive doesn't resolve the error. I have to physically unplug the unit from the Mac.

I've circled it in red below.

And here is the info on that specific drive:

 

[Dayo]

Does this only happen when you are trying to override your previously indicated volume?

 

[amstel78]

Does this only happen when you are trying to override your previously indicated volume?

No, this happens the moment I start the application with that particular USB HDD connected. I can't even get to the screen which provides the override button. TweakESP works normally the moment the external drive is physically disconnected. Unmounting doesn't solve it.

 

[Dayo]

I vaguely recollect some issue related to having more than 10 Disk IDs when first putting that app together.
Parked as not being critical since "no one was ever going to hit that limit" ... Will revisit this presently.

 

[amstel78]

I vaguely recollect some issue related to having more than 10 Disk IDs when first putting that app together.
Parked as not being critical since "no one was ever going to hit that limit" ... Will revisit this presently.

Thank you. I thought about that last night; wondering if there was a physical disc limit in place. That would explain why TweakESP would only work after physically disconnecting the drive.

 

[modiug]

Hi there, trying to install but DeployESP gives Fatal Error: PhysicalDiskCheck 01.
Mac Pro 5,1: High Sierra.
Any suggestion? Thank you

 

[Dayo]

Any suggestion?

Disconnect any external volumes not needed for setting things up until you are done.

 

[modiug]

Thank you, no external volumes, only system SSD and 1TB disk where I try deploy ESP

 

[Dayo]

I see.

Launch Terminal, run "diskutil list" (without quotes) and post a screenshot please.

 

[modiug]

Sorry for the screeshot quality. It is not 1 but 3Tb disk.

 

[Dayo]

Looks like a Fusion drive?

If so, then these are not currently supported.
Sorry that this is not explicitly set out anywhere (Configfactory only mentions RAID but this meant RAID and Fusion drives).
I will rectify this.

Try to find a regular HFS+ drive to use.

 

[modiug]

Thank you but is not a fusion drive, normal classic WD. It was used on a 3,1 catalina macpro and moved to my new 5,1.

 

[Dayo]

It is a fusion drive (Apple CoreStorage format).

 

[modiug]

I understand but is a normal WD caviar Green WD30EZRX. I can try to reformat? Thank you.

 

[Dayo]

You could still use it as is but will have to do everything manually in Terminal.

As long as it is a standard HFS+ drive, the apps will be fully automated and on standard APFS, semi-automated.
I will amend the apps to handle such drives and update the guide with the manual commands later.

 

[modiug]

Thank you again, awesome support.
Best regards.

 

[Macschrauber]

Searched this thread and re-read the first post but didn't see much regarding Filevault activation post RP/OC install.

I'd like to turn FV on in Mojave, and vaguely remember an option for FV being presented in MyBootMgr 066f.

I'm not in front of my Mac at the moment to check, so I'm wondering if I need to rerun MyBootMgr from the start, or will the option to reuse existing settings provide the option to enable FV compatibility?

Lastly, I assume MyBootMgr will modify OC's config file to add all necessary keys and NVRAM entries to allow FV's preboot loader to start?

I run FileVault on my MP3.1 and MP5.1 with RefindPlus. No Problems, regarding of what version of rp it shows Preboot for Mojave.

Those Options for FileVault on or off was a glitch with an addition what needed to be disabled when doing FV. This is obsolete and solved.

 

[nocomprendo]

@Dayo Many thanks for all the development work on MyBootMgr! Good job!

I had a previously installation of Big Sur and implemented your MyBootMgr because I like the graphical boot loader. It looks nice. Also, I was hopping that it would give me instant wifi compatability but it didn't. I found a workaround with AirPortAtheros40.kext because all other kexts included weren't working for me.

Right now, I'm still try to find a solution for:

1. Installing Windows 10 on a separate SSD.
   I'm not sure how to install Windows 10 on this setup. Initially I was looking at the original OpenCore on the Mac Pro which guided users on how to install it. But that involves installing a driver from OcBinaryData and I'm not sure if it will mess things up.
   I am sure that during the initial steps using ConfigFactory I chose that it was intended to install Windows on this machine, but not sure if it did anything that allows me to proceed with W10 install. How can I check it?

Any comments or advice from you or anyone regarding this?
I appreciate all help I can get.

Many many thanks in advance!!

 

[Dayo]

I found a workaround with AirPortAtheros40.kext because all other kexts included weren't working for me.

AirPortAtheros40 is already included in MyBootMgr setup but it isn't activated for MacPro4,1 as wasn't sure exactly what is in those. Either way, all you needed to do was to switch it on in the config.

Will set it to be switched on for these be default in the next version since it now seems clear they need this.

Installing Windows 10

If you read the guide in Post 1, you will find information regarding Windows.

 

[Dayo]

Updated MyBootMgr to v067
See changelog for details

This is a significant update.
Consider the changes to notes on upgrading from an earlier version.

 

[amstel78]

Updated MyBootMgr to v067
See changelog for details

This is a significant update.
Consider the changes to notes on upgrading from an earlier version.

v067 of MyBootMgr is still deploying RP v0.12.0.AQ and v0.6.6 of OC. Can you please check your distro?

Edit: just checked twice by reinstalling v067 release of MyBootMgr and deleting previously deployed EFI folder on EFI target drive.

 

[Dayo]

Might have mixed the packages up. Should be sorted now.

 

[amstel78]

Just downloaded v067 again and installed. Checked the deployed EFI folder and the same old structure from 066f is present. BOOTx64 also has older time stamps.

Oddly, even without a MyBootMgr_BAK folder present in the /Shared folder, ConfigFactory is asking if I want to use an existing configuration.

 

[Dayo]

My fault ... I uploaded to the wrong folder (you had the same package as before).
Should finally be sorted now.

PS: Re-using the previous settings is not based on the backup folder.