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

[Farravi]

OK so i managed to get OC working i think but now RP doesn't load and before you ask I did bless RP and OC.

Anywho, this was my last attempt. For what it is worth, it managed to load onto the target disk Storage A this time, I have compressed the file and attached it below.

I have also got 4 files which i believe to be some sort of Log file for OC which I have also included.

 

[Dayo]

but now RP doesn't load and before you ask I did bless RP and OC.

Two queries:

1. What do you mean by RP doesn't load?
   • Clarify ... How did you get to OC if not via RP?
2. What do you mean by blessing RP and OC?
   • There is nothing in the Post 1 instructions about blessing both

 

[Farravi]

Two queries:

1. What do you mean by RP doesn't load?
   • Clarify ... How did you get to OC if not via RP?

When i start the computer and even restart no matter how many times, I get this :

Opencore Boot Screen
* 1. Macintosh HD
Choose the Operating System

1. What do you mean by blessing RP and OC?
   • There is nothing in the Post 1 instructions about blessing both

I could have sworn I read it in the instructions, not once many times. Must be where I am going wrong. Intrestingly, I do get the option to Bless OC and RP in Bootblesser so maybe that's where I may have got confused. I don't know.

 

[Dayo]

I could have sworn I read it in the instructions, not once many times.

Seemed obvious you were not actually following what was written. I believe the same applied to other methods you have tried and is why I suggested getting someone else to have a go instead.

 

[Farravi]

Eureka!

I followed the process and took the additional steps of deleting the EFI folder from Storage A, CPU cable disconnect, then connect, then connected the keyboard to the CPU USB port and did the 4 x Chime restart holding Cmnd + Option + P + R keys.

Revisited the instructions as per post 1 and all working. Booted into RP And then choose the OC instance (1) and pressed spacebar when the option for OC appeared on the top right and it changed from 1. Macintosh HD to 'show auxillary' and gave me a whole menu, the same with OC instance (2) in RP and again pressed spacebar twice and it gave me a lot of options. Checked the bootroom everytime to check whether I am *spoofed* I believe is the correct terminology?! If it's showing 999.99.9.9.9 then it's not native and if it shows 144.0.0.0.0 then I am booted into the Native MacOS.

That has been quite the journey and again i thank you for your help and appreciate all the advise from you and @tsialex and @Macschrauber

Now for the next bit. Installing Legacy windows and possibly Monterey. Any tips?

 

[Dayo]

Installing Legacy windows and possibly Monterey. Any tips?

OS installation is out of scope for this thread but there is a link to a thread on how to install Windows in Post 1.
Try the Monterey thread for guidance on that OS version.

 

[Dayo]

Updated MyBootMgr to v076b
See change log in Post 1 for details

 

[Dayo]

Updated MyBootMgr to v076c
See change log in Post 1 for details

 

[Dayo]

Updated MyBootMgr to v076d
See change log in Post 1 for details

 

[amstel78]

Hello @Dayo. It's been a while since I fired up my MP5,1. I'm skimming through the posts here but wanted to confirm if the latest release of RFP integrates the necessary OC workarounds to allow updating of BigSur past 11.2.3. Anyway, I'll keep reading in the interim. Happy New Year to you and yours, and as usual, thanks for all the hard work you do.

 

[amstel78]

@Dayo v076d results in the following when presented with Innie choices and selecting 'YES':

Going back and selecting 'NO' will permit ConfigFactory to continue without error. That said, only some internal PCIe drives are showing as external and the rest are internal, internal PCIe drives still show as external. Going back to AHCI method should resolve.

 

[Dayo]

Hi ... will look at the error for the next release due next week.
Might have been left as an oversight as Innie is now an absolute last resort option (development appears to have ceased).

 

[amstel78]

FWIW, up until v070c, I never used Innie. There was always a problem with it and recognizing PCIe drives under Big Sur. Instead, I always used the alternate AHCI solution which no longer appears to be an option in ConfigFactory. Is there a possibility to bring that back?

 

[amstel78]

Hi ... will look at the error for the next release due next week.
Might have been left as an oversight as Innie is now an absolute last resort option (development appears to have ceased).

Thanks. If you bring back AHCI option in ConfigFactory, that should solve the issue. Please bring that back with the next release. Thank you.

 

[amstel78]

Welp, color me impressed. Didn't have to do too much going from v070c to v076d to get Big Sur updated to 11.6.2. So far, Wifi works along with all other peripherals. Internal PCIe drives are still being reported as external drives, but I chalk that up to AHCI not being configured correctly. @Dayo, let me know once you get ConfigFactory fixed to allow AHCI and I'll retest. Thank you.

 

[amstel78]

Ok, so discovered a few more issues.

1. Boot OC (default - post Mojave): will not actually boot Mojave. Selecting that option results in a system reboot and return back to boot picker;

2. Boot OC (alternate - Pre Monterey): selecting this will force a reboot into recovery mode.

3. Boot OC (Pre Monterey): error 'load error when loading OpenCore.efi

4. Boot OC (Post Mojave): same error message as above

I can only boot native Mojave by selecting the vanilla option in boot picker.

Selecting option one and choosing BS will load Big Sur 11.2.6. Choosing Mojave will result in a reboot back to the picker screen.

NVRAM cleared 3x and result is the same as described above.

 

[Dayo]

1. Boot OC (default - post Mojave): will not actually boot Mojave.

Bear in mind that "Post Mojave" means "After Mojave" and therefore excludes Mojave.
That is, it is to be used for Big Sur Catalina and later.
I suppose many might get muddled up on that and will consider a rename.

2. Boot OC (alternate - Pre Monterey): selecting this will force a reboot into recovery mode.

Not clear on what you mean. Do you get the reboot on selecting the option in RP as stated or on selecting something in OpenCore? If the later, what was selected?

Hopefully not Monterey since "Pre" means "Before"

3. Boot OC (Pre Monterey): error 'load error when loading OpenCore.efi

Ditto

4. Boot OC (Post Mojave): same error message as above

As Item 1

I can only boot native Mojave by selecting the vanilla option in boot picker.

Do you actually have Monterey installed? If not, do not say so in ConfigFactory.

 

[amstel78]

Not clear on what you mean. Do you get the reboot on selecting the option in RP as stated or on selecting something in OpenCore? If the later, what was selected?

System would reboot the moment that option was selected in RP. I did not get the usual OC selection of operating systems.

Do you actually have Monterey installed? If not, do not say so in ConfigFactory.

I do not have Monterey although cannot remember if I selected yes in ConfigFactory in the last build (I believe I said no). I will go through the process again and revert.

Bear in mind that "Post Mojave" means "After Mojave" and therefore excludes Mojave.
That is, it is to be used for Big Sur Catalina and later.
I suppose many might get muddled up on that and will consider a rename.

In previous iterations, would use the default OC to also boot Mojave in order to take advantage of certain OC functionality such as extended GPU support as well as showing PCIe drives as internal. If the default can no longer be used to boot the native OS, what option would?

Edit: Clear NVRAM from RP doesn't seem to function. Selecting that option does nothing.

Edit 2: my fault. Ran ConfigFactory again and problem solved as far as default OC and Mojave. I guess I had inadvertently selected Monterey as a build choice last night. FWIW, clear NVRAM still doesn't seem to do anything from RP.

 

[Dayo]

Previously, a single OpenCore setup could easily boot any available Mac OS version but with Monterey, there is a break in Mac OS versions, tied to APFS, as follows (My Naming):

• Non APFS : HiSierra (HFS+) and Older
• Proto APFS : HiSierra (APFS) and Mojave
• Transitional APFS : Catalina and Big Sur
• Actual APFS : Monterey and Newer (Expected)

The "Default" OC Instance was never said to be linked to a "Native Mac OS", it was simply capable of booting any Mac OS version present ... before Monterey was released.

With Monterey, you cannot readily have a single OpenCore setup that spans all four categories but a setup targeted at one category can generally also boot adjacent categories.

The setups created by ConfigFactory are of two types:

• Proto APFS : Boots "Non APFS", "Proto APFS" and "Transitional APFS" ... Current Label = "Pre Monterey"
• Actual APFS : Boots "Transitional APFS" and "Actual APFS" ... Current Label = "Post Mojave"

Therefore, as to your query, you simply need to look at what the label says it is for.

Configfactory creates multiple instances to cover the full spectrum of Mac OS types based on what the user indicates and you wouldn't have had four instances if you didn't indicate that you had Monterey or that this was immiment. (Would be a bug if so) ... You can always share/check the ConfigFactory debug log.

If you had indicated Big Sur as the newest, it would have just created two Proto APFS instances that would look like the previous iterations since there would have been no need to try to cover Actual APFS.

 

[amstel78]

Thanks, Dayo. Yes, it was a configuration fault on my end. Deselecting Montery in ConfigFactory now provides with me two options, default and alternate which both appear to work fine, including booting Mojave.

Only remaining issues (at least for me):

1. No AHCI configuration option to force PCIe drives to show as internal;
2. Clear NVRAM option in RP doesn't seem to do anything.

 

[Dayo]

System would reboot the moment that option was selected in RP. I did not get the usual OC selection of operating systems.

Should not happen and failures should be after OpenCore has loaded and an unsupported Mac OS for that OpenCore Instance selected.

Can you recreate the previous setup, retry your failed attempts and share the debug logs from ConfigFactory, OpenCore and RefindPlus?

Thanks.

 

[amstel78]

Was not able to recreate the issue again. Likely due to something that resolved itself after an NVRAM purge. If I notice the problem again, I'll go back to debug and send you the logs.

 

[Dayo]

Updated MyBootMgr to v077
See change log in Post 1 for details

 

[freqrider]

Updated MyBootMgr to v077
See change log in Post 1 for details

Hi Dayo! I noticed a few things I thought to mention to you. 1: Switch Run Mode has not been working for me in Monterey/BigSur. Works fine in Mojave? Also, 2: The cpuid flag AAAAAAAAJCAAAAAA crashes my 3,1. I’m assuming this is the SSE4.2 spoof flag? Shame because I want to run latest PShop in Monterey! Is this a known issue with the 3,1? Anyone else have this problem? Also, 3: No H264 accel in Monterey, only HevC ? Works in Mojave. Could be a VideoProc bug? (Latest version)?

 

[joevt]

Hi Dayo! I noticed a few things I thought to mention to you. 1: Switch Run Mode has not been working for me in Monterey/BigSur. Works fine in Mojave? Also, 2: The cpuid flag AAAAAAAAJCAAAAAA crashes my 3,1. I’m assuming this is the SSE4.2 spoof flag? Shame because I want to run latest PShop in Monterey! Is this a known issue with the 3,1? Anyone else have this problem? Also, 3: No H264 accel in Monterey, only HevC ? Works in Mojave. Could be a VideoProc bug? (Latest version)?

Has spoofing SSE4.2 when you don't have SSE4.2 worked for anyone? Seems likely to cause a crash.

Does Intel SDE work? https://forums.macrumors.com/thread...unsupported-macs-thread.2299557/post-30740707