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

[Dayo]

Override is not created anywhere in v062d not sure why? Where would it be located?

It is in the "chainloader" folder as of the current version.

Also want to clarify something during the ConfigFactory there are a few questions regarding if I would like nvram reset reboot and shutdown which I answer yes to each one of those so is ConfigFactory suppose to make the change in OpenCore's config file and change HideAuxillary from Yes to No? It doesn't in v062d just want to make this clear.

The questions asked whether you want to allow reboot/shutdown functionality or not, and it does exactly this. When you select "Yes", the selected functionality is available, and when you select "No", the selected functionality is not available.

You have made an assumption that making these available means HideAuxiliary would automatically be set in line with those two but that, as said, is just an assumption on your part.

HideAuxiliary is a totally separate config token that is not tied to these two and ConfigFactory does not include anything that could be remotely interpreted as suggesting HideAuxiliary is being set.

BTW, HideAuxiliary has always been set to true in every single version of MyBootMgr released with those very same items switched on. There was no choice given on this before ... The config files came that way and if you wanted otherwise, you had to amend manually. Curious as to why this has only now become an issue.

Also not sure why you want HideAuxiliary off in the first place.
Why do you want your screen cluttered with items you will not be using on a day to day basis? What the big issue with pressing the space bar to access those items when you specifically need them?

In any case, I will add an option to switch this key in the next release

 

[osxfr33k]

It is in the "chainloader" folder as of the current version.


The questions asked whether you want to allow reboot/shutdown functionality or not, and it does exactly this. When you select "Yes", the selected functionality is available, and when you select "No", the selected functionality is not available.

You have made an assumption that making these available means HideAuxillary would automatically be set in line with those two but that, as said, is just an assumption on your part.

HideAuxillary is a totally separate config token that is not tied to these two and ConfigFactory does not include anything that could be remotely interpreted as suggesting HideAuxillary is being set.

BTW, HideAuxillary has always been set to true in every single version of MyBootMgr released with those very same items switched on. There was no choice given on this before ... The config files came it that way and if you wanted otherwise, you had to amend manually. Curious as to why this has only now become an issue.

Also not sure why you want HideAuxillary off in the first place.
Why do you want your screen cluttered with items you will not be using on a day to day basis? What the big issue with pressing the space bar to access those items when you specifically need them?

Thanks for clearing this up now back to why this is not come up as a problem you tell me I tried on two different machines the second machine does not get the message "Variable MacVols is not Defined" to make sure this is not the cause which it should not be since this message comes up after the build is complete. Neither folder on both machines has an override file inside the Chainloader folder, I only see PNG files in the Images folder and Override is not there either? Let me run this again leaving all defaults to what defaults are selected.

I have not tried any builds since MyBootMgr-060c, just FYI.

 

[osxfr33k]

@Dayo
Thanks for uploading V062e. I see an overrides instead of chainloader folder wanted to confirm this and what is the file called that has the changes that where made is it a conf file? I still do not see any conf file, just a folder called overrides with the images folder inside it, no conf file to be found.

Thanks for adding the new feature to enable or disable HideAuxillary, I also see now the choice to save the configuration but I don't see any conf file created as I have already said.

Want to check in before I try to boot this new release.

Thanks!

 

[Dayo]

You don't need to crosscheck things with a post and all check ins should be done by referring back to the guide. It is updated with pertinent information as things evolve so that any user can follow what it says to get things installed. This is of course as long as they do what it actually says and don't bring in stuff that is not explicitly stated.

I am actually actively trying to avoid the situation whereby people think they need to read the whole thread for nuggets of critical information. All the critical information is in the first post and that is actually the only post that needs to be read. If anything important crops up in a post, it is always reflected back there at the first opportunity. Those that have read it before just need to remember that they need to go back to it as needed.

As to some file or the other not showing up, All I can say is that everything works for me after running the steps outlined in the guide exactly as outlined. If you do the same without adding anything whatsoever to the process, there is no reason why it would not work on yours as well.

I believe the root cause of your issues is the same most have in that many cannot just take the guide at face value and implement it without second guessing it and injecting some twist of theirs into the process.

There is probably something that you think is important that is not mentioned in the guide and that you concluded must have been overlooked and so, implemented.

EDIT:
I suspect you disconnect drives when installing as you think this somehow "protects" your machine.
You should not be doing this, the "macVols variable" error you have been reporting is most likely caused by this, but regardless, I will build in some resilience on this aspect into another release.

As said though, the guide doesn't tell you to do this and you should not be, but will amend the code to live with this as there is a case to be made that some might actually operate their MacPros with only one disk.

 

[osxfr33k]

Yes I only have one disk so you can say this is the only part that I am doing that is outside the guide. Again that warning should not affect the build in the end or will it?

If something goes wrong I have my own easy way to boot back to the drive.

My other macpro has one drive I don’t get that message.

I only get this message from this macpro3,1 I cannot figure out why. Still get the message on the one MacPro but I ran it on the other MacPro and now I have the overrides.conf. I'll have to run it on the other machine going forward until I figure out why I get this message.

 

[Dayo]

v062f should work for you.

 

[osxfr33k]

@Dayo Thanks for your patience and creating the updated version 062f everything works perfect and I like the original rEFInd theme you put back. Also I want you to know I really do appreciate all the time and effort you have put into MyBootMgr which I consider perfection!!

 

[JedNZ]

Has anyone encountered an issue where, when you select OpenCore from the RefindPlus pick list, all you see in the OpenCore pick list is a Restart and a Shutdown option, and no boot disks are shown?

The second issue is, only seeing one boot drive - a HD in a direct connect bay – it doesn't show my PCIe NVMe SSD.

I have had this issue today when I removed OpenCore and installed RefindPlus/OpenCore. I followed the instructions for removing OpenCore, then installed RefindPlus using ConfigFactory. My primary boot is on a PCIe NVMe. I disabled SIP, reset SMC and NVRAM a few times, but the best I could get was my secondary boot drive (HDD in direct connect bay) showing up. I'm wondering if using my Time Machine EFI volume was the issue. I've now tried another drive with no OS on it and I get the same issue - my NVMe boot drive doesn't show up in the OpenCore pick list. It does show up in RefindPlus and I can boot to it direct instead of via OpenCore.

Anyone encounter this issue and have a fix for it?

 

[Dayo]

Has anyone encountered an issue where, when you select OpenCore from the RefindPlus pick list, all you see in the OpenCore pick list is a Restart and a Shutdown option, and no boot disks are shown?

The second issue is, only seeing one boot drive - a HD in a direct connect bay – it doesn't show my PCIe NVMe SSD.

I have had this issue today when I removed OpenCore and installed RefindPlus/OpenCore. I followed the instructions for removing OpenCore, then installed RefindPlus using ConfigFactory. My primary boot is on a PCIe NVMe. I disabled SIP, reset SMC and NVRAM a few times, but the best I could get was my secondary boot drive (HDD in direct connect bay) showing up. I'm wondering if using my Time Machine EFI volume was the issue. I've now tried another drive with no OS on it and I get the same issue - my NVMe boot drive doesn't show up in the OpenCore pick list. It does show up in RefindPlus and I can boot to it direct instead of via OpenCore.

Anyone encounter this issue and have a fix for it?

It might be an issue with the "scanpolicy" setting. Try setting this to "0" which removes all restrictions to see if this is the case. See OpenCore docs for details.

 

[JedNZ]

I assume I open up /EFI/EFI/OC/config.plist and change
<key>ScanPolicy</key> <integer>983299</integer>
to this

<key>ScanPolicy</key> <integer>0</integer>

Is this right?

 

[AlexSakha67]

Hi, my system is macPro 3.1
macOS Mojave Patcher - DosDude1and
macOS Catalina Patcher - DosDude1
10.15.7-10.14.6 (18G3020) 2 x 3.2 GHz Quad-Core Intel Xeon, Asus NVIDIA GeForce GT 640 2GB. Will MyBootMgr_062f install?
Thanks in advance.

 

[Dayo]

Will MyBootMgr_062f install?

As the guide in Post 1 says, you can operate DosDude Installations with OpenCore (that's the only way to run newer Mac OS versions on a 3,1) so no issues on that front. DosDude patching is not needed on 5,1 so you can overwrite your Mac OS with a vanilla version after installing MyBootMgr if using such cMP (You will no longer be able to boot in directly from RefindPlus).

As for your GPU, it is impossible to list out what specific GPU model might work, or might not work, out of the dozens of models out there except that Nvidia GPUs are less likely to work.

There is a general categorisation in that your GPU should fall into one of the following categories:

1. Fully Compatible Mac GPUs
   1. These are GPUs that can load Mac OS and show the Mac Pre-Boot Screen
      1. This ability to show the Pre-Boot Screen can be either from the factory or flashed afterwards
2. Semi Compatible Mac GPUs
   1. These are GPUs that can load Mac OS but cannot show the Mac Pre-Boot Screen
   2. Additionally for this category, the GPU must have "Valid" Usable or FixableGOP.
      1. This "Valid GOP" requirement is where most Nvidia cards that meet the first sub criteria fail as it is an internal GOP categorisation that many Nvidia cards do not meet. That is to say that while they may have GOP, for RefindPlus/OpenCore, the GOP they have is not "Valid" as it cannot be used by those tools to show their bootpickers as it is. (OUTDATED ... REFER TO POST 1)

The MyBootMgr process is however one where you can try things and if it doesn't work, remove it without negative impacts. So you can give it a shot and report back.

I can see that this information is incomplete and somewhat scattered in the guide. I will pull together into one piece.

 

[AlexSakha67]

As the guide in Post 1 says, you can operate DosDude Installations with OpenCore (that's the only way to run newer Mac OS versions on a 3,1) so no issues on that front. DosDude patching is not needed on 5,1 so you can overwrite your Mac OS with a vanilla version after installing MyBootMgr if using such cMP (You will no longer be able to boot in directly from RefindPlus).

As for your GPU, it is impossible to list out what specific GPU model might work, or might not work, out of the dozens of models out there except that Nvidia GPUs are less likely to work.

There is a general categorisation in that your GPU should fall into one of the following categories:

1. Fully Compatible Mac GPUs
   1. These are GPUs that can load Mac OS and show the Mac Pre-Boot Screen
      1. This ability to show the Pre-Boot Screen can be either from the factory or flashed afterwards
2. Semi Compatible Mac GPUs
   1. These are GPUs that can load Mac OS but cannot show the Mac Pre-Boot Screen
   2. Additionally for this category, the GPU must have "Valid GOP".
      1. This "Valid GOP" requirement is where most Nvidia cards that meet the first sub criteria fail as it is an internal GOP categorisation that many Nvidia cards do not meet. That is to say that while they may have GOP, for RefindPlus/OpenCore, the GOP they have is not "Valid" as it cannot be used by those tools to show their bootpickers as it is.

The MyBootMgr process is however one where you can try things and if it doesn't work, remove it without negative impacts. So you can give it a shot and report back.

I can see that this information is incomplete and somewhat scattered in the guide. I will pull together into one piece.

Thank you

 

[JedNZ]

I assume I open up /EFI/EFI/OC/config.plist and change
<key>ScanPolicy</key> <integer>983299</integer>
to this

<key>ScanPolicy</key> <integer>0</integer>

Is this right?

Worked! Now I just need to work out the number setting I’ll use to suppress seeing the unwanted volumes (like 2 EFI presentations etc). The guide is quite technical to this regard so I haven’t been able to work out how this bit works.

 

[Dayo]

Try these in turn and me know how you fare:

1. 983811
2. 17760515
3. 17761027

 

[JedNZ]

I have read the ScanPolicy information here.

The original OpenCore value was 983299 (0xF0103 which is all of these added together:
0x00000001 (bit 0) – OC_SCAN_FILE_SYSTEM_LOCK
0x00000002 (bit 1) – OC_SCAN_DEVICE_LOCK
0x00000100 (bit 8) – OC_SCAN_ALLOW_FS_APFS
0x00010000 (bit 16) – OC_SCAN_ALLOW_DEVICE_SATA
0x00020000 (bit 17) – OC_SCAN_ALLOW_DEVICE_SASEX
0x00040000 (bit 18) – OC_SCAN_ALLOW_DEVICE_SCSI
0x00080000 (bit 19) – OC_SCAN_ALLOW_DEVICE_NVME

But this didn't work – it didn't list my NVMe PCIe blade.

Should I instead go for the default value of 0x10F0103 (17,760,515) which is a combination of the following?:
OC_SCAN_FILE_SYSTEM_LOCK
OC_SCAN_DEVICE_LOCK
OC_SCAN_ALLOW_FS_APFS
OC_SCAN_ALLOW_DEVICE_SATA
OC_SCAN_ALLOW_DEVICE_SASEX
OC_SCAN_ALLOW_DEVICE_SCSI
OC_SCAN_ALLOW_DEVICE_NVME
OC_SCAN_ALLOW_DEVICE_PCI

Or is there a better combination I should calculate from the available list below?:
0x00000001 (bit 0) – OC_SCAN_FILE_SYSTEM_LOCK
0x00000002 (bit 1) – OC_SCAN_DEVICE_LOCK
0x00000100 (bit 8) – OC_SCAN_ALLOW_FS_APFS
0x00000200 (bit 9) – OC_SCAN_ALLOW_FS_HFS
0x00000400 (bit 10) – OC_SCAN_ALLOW_FS_ESP
0x00010000 (bit 16) – OC_SCAN_ALLOW_DEVICE_SATA
0x00020000 (bit 17) – OC_SCAN_ALLOW_DEVICE_SASEX
0x00040000 (bit 18) – OC_SCAN_ALLOW_DEVICE_SCSI
0x00080000 (bit 19) – OC_SCAN_ALLOW_DEVICE_NVME
0x00100000 (bit 20) – OC_SCAN_ALLOW_DEVICE_ATAPI
0x00200000 (bit 21) – OC_SCAN_ALLOW_DEVICE_USB
0x00400000 (bit 22) – OC_SCAN_ALLOW_DEVICE_FIREWIRE
0x00800000 (bit 23) – OC_SCAN_ALLOW_DEVICE_SDCARD
0x01000000 (bit 24) – OC_SCAN_ALLOW_DEVICE_PCI

Fairly sure I'll never use Firewire, but I may have reason to boot from a USB stick/drive at some stage so should that be included?
Would I need to include SCSI if I'm using HDD, SSD in PCIe adapters and NVMe in PCIe adapters? Are any of them still legacy SCSI devices?

Suggestions sought.

UPDATED: Thanks @Dayo . Only just saw your post after I posted my long winded version. I'll try option 2: 17760515 first and report back tomorrow.
PS: I just did my very first hexadecimal conversion trying to work this all out!! Old dogs can learn new tricks.

 

[Dayo]

I'll try option 2: 17760515 first and report back tomorrow.

Please report on the 3 options if it's not too much trouble.

 

[JedNZ]

Please report on the 3 options if it's not too much trouble.

I have tried all 3 options and none of them display my NVMe PCIe blade. I do see my SSD in a Accelsior S SATA III PCIe adapter with Catalina on it, and a HDD in a direct connect bay with a Mojave, however the other displayed options vary with each of the different options you provided (e.g. I see another HDD with Install High Sierra on it etc).

I'll go back to using 0 in the meantime until give a few other things a try out tomorrow.

Just one quick question: Am I doing the changes correctly?
I mount the EFI, and drag the config.plist file to my desktop from the /EFI/EFI/OC folder. I change the value, save it, then copy the file back.

Am I supposed to do any other magic (repair permissions etc)? Or reset NVRAM/SMC?

UPDATED:
Back on ScanPolicy 0 and my NVMe blade is showing and I can boot successfully into it.

 

[Dayo]

Back on ScanPolicy 0 and my NVMe blade is showing and I can boot successfully into it.

This was a bug in OpenCore which has now been fixed and will appear in the next release.
So use zero for now.

 

[Macschrauber]

I have found a little bug in 062f inside the BootBlesser Script.

If someone is using an USB Stick it would not find the RefindPlus file and it would not get blessed.

Have found the culprit, corrected and posted it to @Dayo.

View attachment 976427

View attachment 976429

 

[Dayo]

I have found a little bug in 062f inside the BootBlesser Script.

If someone is using an USB Stick it would not find the RefindPlus file and it would not get blessed.

Have found the culprit, corrected and posted it to @Dayo.

Thanks. Fix will appear in next version due after the weekend.

 

[Macschrauber]

ok, I have some issues:

MP3,1, Kepler GPU with UGA Bootscreen



when I boot RefindPlus Debug Version via bless

sudo bless  --folder /Volumes/BlackStick/EFI/BOOT/ --file /Volumes/BlackStick/EFI/BOOT/BOOTx64.efi --setBoot --nextonly

I get this error (plus a 3rd line saying HiddenTools maybe, its just too quick)

OpenRefind shows up, just with two OpenCore instances to select

if I bless the non debug version I dont have those lines, but same behaviour


Next step is selecting OpenCore, got my Mojave Disk to select, then the Mac is kinda resetting (screen gets black, loud chime, dvd drive is making positioning sounds) and rebooting into my startup disk.

If I bless without nextonly I am again in RefindPlus and so I'm lost


Now...

If I select the RefindPlus thumb drive with the BootPicker (have a bootscreen GPU) Refind plus shows up with all my drives. (but not my Mojave one)

But selecting OpenCore will hard reset again.


have FileVault active on Mojave Disk if that counts.


"native" OpenCore 0.62 works without chainloading from RefindPlus

 

[joevt]

ok, I have some issues:

MP3,1, Kepler GPU with UGA Bootscreen



when I boot RefindPlus Debug Version via bless

sudo bless  --folder /Volumes/BlackStick/EFI/BOOT/ --file /Volumes/BlackStick/EFI/BOOT/BOOTx64.efi --setBoot --nextonly

I get this error (plus a 3rd line saying HiddenTools maybe, its just too quick)


View attachment 976463

OpenRefind shows up, just with two OpenCore instances to select

if I bless the non debug version I dont have those lines, but same behaviour


Next step is selecting OpenCore, got my Mojave Disk to select, then the Mac is kinda resetting (screen gets black, loud chime, dvd drive is making positioning sounds) and rebooting into my startup disk.

If I bless without nextonly I am again in RefindPlus and so I'm lost


Now...

If I select the RefindPlus thumb drive with the BootPicker (have a bootscreen GPU) Refind plus shows up with all my drives. (but not my Mojave one)

But selecting OpenCore will hard reset again.


have FileVault active on Mojave Disk if that counts.


"native" OpenCore 0.62 works without chainloading from RefindPlus

For EFI partition blessing, I think the mount command is more appropriate:

sudo bless  --mount /Volumes/BlackStick --file /Volumes/BlackStick/EFI/BOOT/BOOTx64.efi --setBoot --nextonly

but I don't know if that will fix your problem.
My script at https://gist.github.com/joevt/477fe842d16095c2bfd839e2ab4794ff can show what the boot vars look like after the bless command (just use the dumpallbootvars function) so you'll be able to see the difference between each bless command.

 

[Dayo]

For EFI partition blessing, I think the mount command is more appropriate:

He is on a USB Volume ... That's the one that you have to choose to ignore recommendations against usage in this setup!

 

[Macschrauber]

will try, thanks

but anyway, this is what the BootBlesser Script of @Dayo does. There was the bug so I extracted it from the script.

if this helps, this happens when I bless OpenCore with the BootBlesser script: