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

[amstel78]

OK, downloaded again.

Certainly different this time (did not ask to reuse previously saved choices). However, received the following during config:

P.S. all testing is being done on my MP3,1 running patched Catalina.

P.S.S. where does MyBootMgr store previous config choices?

 

[Dayo]

However, received the following:

Should be fixed.

P.S.S. where does MyBootMgr store previous config choices?

In the system folder for 3rd party application settings ... "/Library/Application Support"

 

[amstel78]

Dayo, getting a 404 when trying to download...

 

[Dayo]

Dayo, getting a 404 when trying to download...

Probably just a glitch but hang on a while as I need to update things.
Just spotted a problem with how APFS Containers are being handled.
Done: Kept the same release number although the RP version was changed.

The saving location was added to my previous.

 

[amstel78]

Specifying ESP drive label results in the following error:

It results in a script loop regardless of volume name given.

 

[Dayo]

Doesn't for me.

What kind of disk are you trying to use?
Is it a regular HFS+ format disk or is it part of a RAID partition?

 

[amstel78]

Regular HFS+ partition and is the ESP partition used previously.

 

[Dayo]

I see the issue. Does the volume have a space in the name?

 

[amstel78]

Yes.

 

[Dayo]

OK. Strange that it it worked before.
Will fix now.

EDIT: Done

 

[amstel78]

Looks good now Dayo. Glad to see the UGA/GOP issue was parsed into OC master v067 final also.

Thanks for the hard work! 👍

 

[amstel78]

@Dayo - as mentioned in PM, having trouble booting vanilla El Capitan (10.11) under OC. Selecting El Capitan immediately shows a gray "no access" circle follwed by a kernel panic and a hard reboot. Checking EFI/OC/Drivers, I note there's no HfsPlus.efi driver file present. I did specify 'YES' to the option for HFS+ in ConfigFactory, but it appears not to have worked. Could you please check?

P.S. Only drivers installed were DBG-OpenRuntime.efi and OpenRuntime.efi.

 

[Dayo]

I note there's no HfsPlus.efi driver file present.

Legacy Macs do not require HFS drivers as HFS is their native filesystem.

If you have read about such drivers somewhere, bear in mind that most online stuff about OC outside this forum is written from a hackintosh perspective.

I did specify 'YES' to the option for HFS+ in ConfigFactory, but it appears not to have worked.

That is not related to drivers. It is just to know whether to look for such volumes to show as options (ScanPolicy value).

 

[amstel78]

Thanks for the explanation above. Much appreciated.

Another question: what exactly does the option pertaining to 'DosDude patched operating systems' in ConfigFactory do as far as OC configuration? I ask because I've discovered the following (since I'm running a patched version of Catalina):

1. When setting that option to YES, Mojave kernel panics and hard reboots immediately after selecting it in OC.
2. With that option set to NO, Mojave boots to desktop without issue (minus audio support).

 

[Dayo]

It mainly stops some kexts from being added since these are already in DosDude.
Some other stuff that I can't recollect. You can access the main script and have a look.

As for KP, not sure why that might be as I use this setup myself without issue. Maybe something else is in conflict in your setup.

Issues are actually expected when you set to NO and actually have this and not the other way round.

 

[amstel78]

It mainly stops some kexts from being added since these are already in DosDude.
Some other stuff that I can't recollect. You can access the main script and have a look.

As for KP, not sure why that might be as I use this setup myself without issue. Maybe something else is in conflict in your setup.

Issues are actually expected when you set to NO and actually have this and not the other way round.

It's certainly odd. Behavior remains consistent even after deep cleaning NVRAM and re-blessing. What I haven't tried is starting patched Catalina with the DosDude option turned off via ConfigFactory.

On a side note - have you considered developing some sort of MyBootManager application that can automate or at least assist in the installation of 3rd party kexts? Something similar to what Clover does? It'd certainly help the IT-challenged folks such as myself.

EDIT: booted into patched Catalina with DosDude option set to NO in ConfigFactory. Everything works; audio, wifi, BT. Even OTA updates work as I just tried the Big Sur update option in System Update and it started. So, not sure how relevant that option in ConfigFactory is now with v0.6.7.

 

[Dayo]

Try a web search ... There are several tools that do this.

Everything works

More important is whether it fails to work when you select YES.

Advice on the OC Thread is not to run DosDude with OC. Doesn't mean it will fail but that it can as you potentially have two different procesess injecting and modifying stuff.

ConfigFactory tries to sort out the potential conflict points. Ultimately up to you what you want to do.

Recommendation in Post 1 is to overwrite DosDude with vanilla versions so that only one process, OC, is modifying things.

The question in ConfigFactory is mainly targeted to those that need to set things up the first time after which they should overwrite. You can ignore this recommendation if you want. Everything is at your discretion.

 

[amstel78]

Try a web search ... There are several tools that do this.

I'll search again; been looking for a few hours without much success.

Can I ask -you said you didn't experience KP's with a similar config. Are you booting successfully into Mojave with your MP3,1 with DosDude option set to YES, and still have full HW functionality?

Also, and FWIW - attempting to install BS with 067 is only partially succesful. I can initiate the first stage of installation from within an older OS, but the second stage (after first reboot) results in a KP and hard reboot. No problems on an MP5,1 but major issues still with an MP3,1.

 

[Dayo]

I'll search again; been looking for a few hours without much success.

I used one called KextBeast before. Hackintool also works and several others I can't recollect the names.

Are you booting successfully into Mojave with your MP3,1 with DosDude option set to YES, and still have full HW functionality?

Everyday.

No problems on an MP5,1 but major issues still with an MP3,1.

@freqrider was apparently able to install on his 3,1 a while ago.

 

[amstel78]

I used one called KextBeast before. Hackintool also works and several others I can't recollect the names.


Everyday.


@freqrider was apparently able to install on his 3,1 a while ago.

Thanks for your reply. Not sure what could be causing my particular anomaly then as far as DosDude implementation and Mojave goes. I'm not using NVME storage nor have any additional expansion devices save for a 3rd party USB3 card. Our biggest difference would be the video cards; yours has native GOP support whereas mine doesn't.

Would you be willing to share your RP and OC config files with me so I can do a compare and contrast? Perhaps I can narrow things down that way.

BTW, as you're able to boot into Mojave just fine; I'm assuming system audio is functional as well. Did you have to use a 3rd party audio kext in addition to whatever ConfigFactory installs to get that to work?

Edit: spoke to freqrider some time back. He needed to implement several different patches and workarounds to get BS loading on an MP3,1. I was kinda hoping the latest iteration of OC would have sorted that out. Guess not.

 

[JedNZ]

After updating to RFP 0.6.7 I found my reboots are noticeably faster (on warm reboots - haven't tried a cold start yet), and only one black/grey flash before the OC pick-list screen appears – I used to get a number of flashes of grey then black then grey after the RFP screen. First time after upgrading to RFP 0.6.7 it flashed some text very quickly after selecting OC but before the OC pick-list screen appears - will try and capture this next time I reboot.

 

[amstel78]

@Dayo I totally wiped the drive, keeping only High Sierra installed in a separate HFS+ partition. Reinstalled Mojave. Still no audio output devices. There's nothing related to DosDude left on the system.

I'm a bit stumped.

Edit: Found some remnants (another BOOTx64.efi file) from DosDude hidden in another EFI partition... Will experiment further.

Edit 2: Tried booting Mojave with setup generated by MyBootMgr v066 - same outcome. Reinstalled Mojave - same outcome. No audio output devices. Only thing I can think of is that legacy audio kexts (like ones used by DosDude) aren't being installed by MyBootManger in either v066 or v067.

Further, Dortania's guide to OC on legacy Macs states the following:

So not sure how you were able to get audio working on your end unless you manually patched it?

 

[amstel78]

On a secondary note, I updated MyBootMgr to v067 on my MP5,1. All is well there, however the syntax formerly used in WrangleConfig for overriding the stock banner seems to have changed. What is the new syntax?

 

[Dayo]

it flashed some text very quickly after selecting OC

This is feature of OC 0.6.7. Log items generated before the log file is ready to be used are sent to the screen.

I'm a bit stumped.

Nothing has changed from what has been told before:

OpenCore on the Mac Pro

Setup doesn't do anything specific on the audio side as personally didn't need such and didn't know enough on the subject. You will have to investigate what kexts are needed and inject. OCLP adds VoodooHDA for cMP3,1. You can start by looking at that. Give feedback on what works.

forums.macrumors.com

Please look for help on such intricacies of configuring OpenCore on that thread.

What is the new syntax?

The syntax of bash scripting has not changed and WrangleConfig is a bash script delivered to you empty, into which you enter whatever you want into. ConfigFactory's role is simply to trigger the script file if you set it to do so, as you can run it manually if you want (as with any other bash script file). It is just an optional vehicle provided for those that might want to use this and the validity of what they put in is up to them.

I don't want to take on the maintenance burden of such but it is most likely that you failed to update the paths to reflect the changed folder structure which was advised in the changelog.

You need to do some basic debugging of such issues as you ultimately own anything you enter into WrangleConfig. It's your baby basically.

 

[amstel78]

This is what I have in WrangleConfig. I did ensure to update the paths after the update. Everything is copied correctly, including the entry into custom.conf but the banner does not show:

###
## Set Custom Bootpicker Image START
###

echo "banner overrides/icons/Banner.png" >> "/Users/Shared/MyBootMgr/EFI/BOOT/custom.conf"
cp /Users/jamessarte/Pictures/RefindPlus_Customizations/Banner.png  /Users/Shared/MyBootMgr/EFI/BOOT/icons

###
## Set Custom Bootpicker Image End
###

So what I meant by syntax, is banner overrides still correct?