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

[Dewdman42]

Also, I tried both Radeonboost and no Radeonboost activated. Can't seem to tell a difference. Is it still needed with 10.14.6? I do confirm with either setting that VideoProc shows H264 and HEVC active whereas non-OC Mojave shows not active.

I think it depends on the card as to how much it improves anything. on the RadeonBoost thread on this forum you can see some tools you can download to run that will show whether you are technically getting any GPU improvement. I initially tried RadeonBoost, ran the tests, felt that improvements were minor and many people said on that other thread that for my card (RX580) that was to be expected. So then I turned off RadeonBoost. However later on I turned it back on and its been on ever since..I can't remember why I decided to keep it on...I think partly because that is the default of MyBootMgr and I felt like, "why not?".

 

[amstel78]

I had a similar problem when I upgraded to the most recent RefindPlus. In my case, I disabled an option in the override.conf file, which suddenly made all my volumes appear on the next boot. I do not know if the option itself was causing the problem, or somehow something need to flush some cache somewhere or something weird like that. I mentioned it in an earlier post, you can look for it.

But really to debug the problem you need to take a look at the conf files you are using for RefindPlus as first step prior to assuming its a bug. I do think there might be some kind of bug though based on my previous experience mentioned earlier on this thread a week or two ago.

Thanks for your feedback. I'm attempting to give @Dayo all the information he needs to help me solve this issue, but since I'm a total newb to all this, am unsure where to get the RefindPlus log files - or even how to enter debug mode. I'm searching the forums as well as this thread, and am having difficulty gleaning this information. Would you be so kind as to tell me where the log files are located?

EDIT: NVM. I used the FetchESP tool to get the logs from my EFI volume. Sorry guys.. I'm learning this as I go.

 

[Dewdman42]

As I said, you should start out by reading the post#1 on this thread completely and thoroughly, which is exactly what Dayo is going to tell you also. Try that and see if you get a working system. If so, then save and if you want to custom configure either RefindPlus or OpenCore on your own you can branch off and do that, but Dayo has worked out a lot of details and so first I recommend you follow the instructions exactly with MyBootMgr and see if you get a working system. If you are unable to get that working then its a good time to figure out why before trying to manually install RefindPlus and OpenCore. You might even just decide to use the MyBootMgr setup exactly as is..which is a very good configuration.

 

[amstel78]

As I said, you should start out by reading the post#1 on this thread completely and thoroughly, which is exactly what Dayo is going to tell you also. Try that and see if you get a working system. If so, then save and if you want to custom configure either RefindPlus or OpenCore on your own you can branch off and do that, but Dayo has worked out a lot of details and so first I recommend you follow the instructions exactly with MyBootMgr and see if you get a working system. If you are unable to get that working then its a good time to figure out why before trying to manually install RefindPlus and OpenCore. You might even just decide to use the MyBootMgr setup exactly as is..which is a very good configuration.

I've read post #1 about 50 times thoroughly over the past two weeks. I've followed Dayo's instructions to the letter. Everything works as far as seeing the RefindPlus bootpicker on my non-EFI Vega 64. I can also launch an OpenCore instance of Mojave and again, everything there runs fine. I just cannot see the native Mojave installation in the bootpicker, which according to Dayo, should have appeared automatically.

 

[amstel78]

Not sure what you changed on MyBootMgr 065a, I will check that out anyway. However I did seem to solve my problem by removing an old entry in the RefindPlus overrides.conf file, which was from a month ago when we were playing around with HiDPI stuff...when I remove the following option, suddenly scanning worked:

force_hidpi true

and of course the newer version of RefindPlus has other ways to handle HiDPI...so I'm happy with the results now..but anyway, not sure why that option would cause it to not scan my OS X volumes, but there it is.

Thanks for the followup.

I just read all of your posts related to my issue up to the one quoted above. I've tried configuring RefindPlus set to either hidpi or non-hidpi. Neither setting has resolved the issue.

MyBootManager was configured on a fresh Mojave install. Only thing I can think of is that non-OC Mojave sees it's boot drive as external since it's on an OWC 6g PCIe SSD instead of a drive installed in a sled. Perhaps that is why RefindPlus doesn't see the Mojave install within the picker?

BTW, where would the option to boot into the Mojave restore volume reside? Should it be listed as one of the boot options in the default OpenCore session? I don't see it in RefindPlus picker or OC hence my question. Selecting the default OC session only gives one option:

*1: Mac OS Mojave (or something to that effect)

 

[amstel78]

Ok, I don't know what I did because I'm exhausted. I changed some parameters in MyBootManager. Now I'm seeing the non-OC Mojave installation. I'll upload the config and logs tomorrow.

 

[amstel78]

Quick question - is AMFI disabled only at RefindPlus boot, but re-enabled on macOS startup? I was looking at some of the arguments listed in the config file and wasn't sure about this. I need AMFI enabled otherwise it breaks certain MS apps.

 

[Dayo]

That option sets a boot argument.
Boot arguments persist until they are specifically cleared.

 

[amstel78]

That option sets a boot argument.
Boot arguments persist until they are specifically cleared.

I see. I've just hard blessed my 5,1. All is working fine. Does AMFI need to be disabled via boot argument in order for RefindPlus and OpenCore to continue doing their thing, or can I re-enable it? If the latter, how can I do that?

 

[Dayo]

I don't understand the last query. Anyway. prefer to keep this thread as focused on MyBootMgr specific stuff as possible.

So please direct RefindPlus specific config queries to the new discussion facility activated on GitHub:

dakanji RefindPlus · Discussions

Explore the GitHub Discussions forum for dakanji RefindPlus. Discuss code, ask questions & collaborate with the developer community.

github.com

Pointed to the rEFInd forum in Post 1 but seems the rEFInd developer is currently not able to respond to queries and anyway, RefindPlus has diverged a lot more than it was when Post 1 was started so will update Post 1.

Thanks

 

[amstel78]

@Dayo, I forgot to use 'SwitchRunMode' before hard bless. Can I still use this tool to get out of debug mode? If so, do I just need to boot into non-OC Mojave, use tool, redeploy ESP then reboot? Or, can I switch modes within OC Mojave?

EDIT: nevermind. I booted into non-OC Mojave and ran the tool successfully. No more log files being generated in EFI.

 

[Dayo]

If there is a restriction in using any of the apps, it will tell you about it when you run it.

Please operate on the basis that if something is not mentioned in the guide, it is not relevant and you don't need to come back for reaffirmation.

Do I need to use tool, redeploy ESP then reboot?

The app works on your already deployed files and not the local files in your staging folder btw.
If you refer back to the guide, you will note that this is the case.

So it is simply, "Run the App". You can run it multiple times switching back and forth if you want.
When you next reboot, whatever mode you last selected will be used.

 

[amstel78]

Thanks Dayo for clarifying.

May I ask one last question if you don't mind, but is it possible with my current configuration to install Windows 10 via Bootcamp? If so, would you suggest that be done within OC or should I boot into native Mojave? Additionally, would RefindPlus bootpicker automatically pick up the Win10 installation, or would I need to tweak something in the config files?

 

[Dayo]

This is an OpenCore specific issue best directed to the main OpenCore thread. You can tag me in queries to threads linked in Post if you think I can contribute.

Anyway, I have never used Bootcamp and don't know anything about its intricacies.

The guide links to a recommended Windows implementation process. This is does not say that one way of booting Mac OS or another needs to be used and following the previous advice, such considerations are therefore not relevant to that process. You can ask follow on questions on the thread dealing with that implementation process.

The main OpenCore thread also has instructions on implementing Windows if you prefer that path btw.

 

[amstel78]

Hello @Dayo. I see RefindPlus has been updated to v0.12.0.AP to correct a bug we discussed in GitHub. I've just been reading the instructions in post 1 and am a little confused. Do I only need to update MyBootManager, or RefindPlus, or both? The instructions give details on updating MyBootManager but says RefindPlus shouldn't really be updated.

Since everything is working fine at the moment, nothing needs to change within the EFI folders, so can I just replace the applications?

Cheers,
James

 

[Dayo]

Updated MyBootMgr to v066

 

[amstel78]

Updated MyBootMgr to v066

Got this installing v066 today:

I take it WrangleConfig is a new tool for v066? I don't see it present in the v065 folder.

 

[Dayo]

Typo in the installation script.
Delete current, give it 15 mins and download again.

PS: Make sure you shut down your browser completely and reopen before attempting to download.
You can also use another browser or private browsing mode.

 

[amstel78]

Typo in the installation script.
Delete current, give it 15 mins and download again.

OK.

Also, I ran into this after running ConfigFactory then attempting to DeployESP:

Edit: good news is that it appears EFI folders were copied anyway. Seems like I was able to boot into OC v066 just fine.

 

[Dayo]

Trash any previous and download again.
I had forgot some issues with running from OpenCore dealt with now

 

[startergo]

When I try to open the image:

 

[Dayo]

Corrupted cache on my server after swapping the package .... issued a reboot to clear it.
Need to make a checklist to follow for various actions.

 

[amstel78]

@Dayo, discovered something else. However ConfigFactory configures Innie.kext in v066 seems a bit different then v0.65a. Or perhaps the way OC implements Innie is incorrect somehow. Using v066 and Innie.kext loaded, it showed one of my internal PCIe drives as external and the other internal. Previous version showed both correctly as internal and confirmed this by reverting EFI folders to the previous configuration.

That said, can I simply delete v066 folder and revert back to previous v065a by removing BAK from folder name, or, do I have to go through the uninstall process? I've reverted back to v065a for now.

EDIT: were you able to upload fixed v066 package?

 

[Dayo]

Issue with the new version of Innie perhaps. I don't use it myself. Please report on the innie thread. Just took a look and it seems a few are having issues with it.

PS: Innie is not the only way to get to were you want. So why roll back without trying the other options?

Fixed version of MyBootMgr uploaded.
You can revert by deleting current EFI folder and renaming previous one. Note that if you run v066 twice in a row, the efi bak folder will no longer be for v065a.

 

[amstel78]

Issue with the new version of Innie perhaps. I don't use it myself. Please report on the innie thread. Just took a look and it seems a few are having issues with it.

PS: Innie is not the only way to get to were you want. So why roll back without trying the other options?

Fixed version of MyBootMgr uploaded.
You can revert by deleting current EFI folder and renaming previous one. Note that if you run v066 twice in a row, the efi bak folder will no longer be for v065a.

I only reverted because against better judgement, this Mac is also my main work machine. Need to have it 100% reliable 24x7. I do have regular CCC backups just in case, but I'd rather avoid any potential issues to begin with. That said, I'll play around with v066 again and check out the Innie thread as suggested.

As for EFI folder backups, I've been making it a habit to keep separate backups of known good EFI configs. That way, if something goes bonkers, it's an easy fix.