MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro

[Situationen]

Dual-processor machines need AppleMCEReporterDisabler.

That did it (not boot looping that is). Still no OTA update, but now I can start figuring that out.

Your patience (and that of all the other bright minds in here) must be immense with people like me doing the same mistakes over and over again.

You have my sincere thanks!

 

[jackfennimore]

This is just for creating Windows PE bootable USB so you can manipulate files on the Windows partition. I believe you can do that with a Linux live USB. The benefit of using Ventoy is that you don"t have to expand the ISO just drop it inside.

APFSStart:1555: Mounting with apfs_efi_osx-945.275.7
efi_fusion_pairing:668: Container 80bbf6d4-e74f-add9-5ee015f9fb48
efi_fusion_pairing:673: fusion uuid: 00000000-0000-0000-0000-000000000000
efi_container_create:972: Volume attached is internal
nx_kernel_mount:1473: : checkpoint search: largest xid 26846, best xid 26846 @ 119
er_state_obj_get_for_recovery:4214: No ER state object for volume Preboot - rolling is not happening, nothing to recover.
er_state_obj_get_for_recovery:4214: No ER state object for volume Recovery - rolling is not happening, nothing to recover.
er_state_obj_get_for_recovery:4214: No ER state object for volume VM - rolling is not happening, nothing to recover.

 

[amstel78]

You may add that it works in RefindPlus.

Thanks. Just updated the issue on GitHub to reflect.

 

[jackfennimore]

when i boot Strelec's WinPE image from my Ventoy USB on cMP i get no picture.

 

[startergo]

when i boot Strelec's WinPE image from my Ventoy USB on cMP i get no picture.

There are several boot loaders and only one worked. I think it was the Fallback EFI loader

 

[jackfennimore]

You need to find a way to replace the driver with the attached. It is found in 2 places:

/Volumes/<VolumeName>/Windows/System32/drivers/BCMWL63a.SYS
/Volumes/<VolumeName>/Windows/WinSxS/amd64_dual_netbc64.inf_31bf3856ad364e35_10.0.21301.1000_none_d5966702e569443d/BCMWL63a.SYS

ok i successfully swapped that driver out in both locations for the one you attached.

once booted into windows it gave me the option to "continue to Windows 10". so i did, it was spinning on the win10 boot screen for about 12 minutes before bluescreening to the same stopcode and the same "what failed: bcmwl63a.sys"

 

[startergo]

ok i successfully swapped that driver out in both locations for the one you attached.

once booted into windows it gave me the option to "continue to Windows 10". so i did, it was spinning on the win10 boot screen for about 12 minutes before bluescreening to the same stopcode and the same "what failed: bcmwl63a.sys"

Do the same thing again apparently it reinstalled them.

 

[jackfennimore]

Do the same thing again apparently it reinstalled them.

did the same thing again. same result.

 

[startergo]

did the same thing again. same result.

What model is your WiFi card?

 

[jackfennimore]

What model is your WiFi card?

good question. Fenvi T919

 

[startergo]

good question. Fenvi T919

Delete those drivers at all or better why don't you disconnect it until you install Windows? Is your original wifi card still inside or you took it out?

 

[jackfennimore]

Delete those drivers at all or better why don't you disconnect it until you install Windows? Is your original wifi card still inside or you took it out?

the stock wireless card is still in the system (whatevers in the 5,1). i'll try this, thanks

EDIT: this was it. up and running Windows 10 (installing wireless drivers). thanks again @startergo !

 

[0134168]

Helio everybody. Long time following this thread.Though a bit intimidating, finally I have started to handle OpenCore in my Mac Pro 4,1-->5.1. Started with Mojave, then updated to Catalina. Everything works like a charm. Even unlock from sleep with Apple Watch, that I never got work properly. Now I can see the Big Sur in Updates. Excuse me, but after reading a lot the thread is not stll clear for me. Does Big Sur work properly? Maybe with micropatcher? Thank you.

 

[TECK]

Does Big Sur work properly?

I did a clean install of Big Sur with the first post advances settings, no issues. I did not wanted to upgrade from Catalina because Big Sur is a major OS change and wanted everything clean. Beside the Bluetooth dual reboot bug, everything works as it should on a supported Mac.

 

[TECK]

Sadly, those are not available anymore.

What version you had prior when everything was working? OTA updates are working fine with latest OC 0.6.6, these are the settings I use now (identical to OP settings). I was able to update to 11.2.1 without issues. Make sure your config.plist has these settings. If you're not sure about the unhexlify values, use Hackintool to convert Hex to Base64 and see the end result.

 

[TECK]

Is anyone running Windows 10 on NVMe drives with an Sapphire Pulse RX 580 GPU? I want to know if you have any freezing problems, thank you. I'm constantly plagued by Windows Logo freezes or freezes during Windows normal use.

Edit: I created a thread

 

[nobullone1964]

Is anyone running Windows 10 on NVMe drives with an Sapphire Pulse RX 580 GPU? I want to know if you have any freezing problems, thank you. I'm constantly plagued by Windows Logo freezes or freezes during Windows normal use.

Edit: I created a thread

I run it. All works smoothly.

 

[eVasilis]

Hi all

I recently installed BS via OC 0.6.6 on my 5,1 Mac Pro. Everything runs beautifully with the exception of wifi (5,1 original card). I did install the relevant kexts (I think they are relevant) and modify config.plist but no joy. here are the entries in config.plist. Any Ideas?

Thanks

Edit: I figured it out. I removed AirportBrcmFixup.kext and the relevant config.plist entries. See below.

<dict>
<key>Arch</key>
<string>x86_64</string>
<key>BundlePath</key>
<string>AirportBrcmFixup.kext</string>
<key>Comment</key>
<string>4331 Wifi Patch</string>
<key>Enabled</key>
<true/>
<key>ExecutablePath</key>
<string>Contents/MacOS/AirportBrcmFixup</string>
<key>MaxKernel</key>
<string></string>
<key>MinKernel</key>
<string>20.0.0</string>
<key>PlistPath</key>
<string>Contents/Info.plist</string>
</dict>
<dict>
<key>Arch</key>
<string>x86_64</string>
<key>BundlePath</key>
<string>AirportBrcmFixup.kext/Contents/PlugIns/AirPortBrcmNIC_Injector.kext</string>
<key>Comment</key>
<string>4331 Wifi Patch</string>
<key>Enabled</key>
<true/>
<key>ExecutablePath</key>
<string></string>
<key>MaxKernel</key>
<string></string>
<key>MinKernel</key>
<string>20.0.0</string>
<key>PlistPath</key>
<string>Contents/Info.plist</string>
</dict>
<dict>
<key>Arch</key>
<string>x86_64</string>
<key>BundlePath</key>
<string>IO80211Mojave.kext</string>
<key>Comment</key>
<string>Broadcom Wifi Patch</string>
<key>Enabled</key>
<true/>
<key>ExecutablePath</key>
<string>Contents/MacOS/IO80211Mojave</string>
<key>MaxKernel</key>
<string></string>
<key>MinKernel</key>
<string>19.0.0</string>
<key>PlistPath</key>
<string>Contents/Info.plist</string>
</dict>

 

[0134168]

I did a clean install of Big Sur with the first post advances settings, no issues. I did not wanted to upgrade from Catalina because Big Sur is a major OS change and wanted everything clean. Beside the Bluetooth dual reboot bug, everything works as it should on a supported Mac.

Thank you so much, sir. Just one question, may be you can help me. I make regular backups using Carbon Copy Cloner. As this app doesn´t copy the EFI partition, I suppose that all I have to do is make an standard backup and then copy manual the EFI contents. Right?

 

[Dayo]

I suppose that all I have to do is make an standard backup and then copy manual the EFI contents.

Yes. You can also use this in CCC: https://github.com/wombat94/EFIClone

 

[0134168]

Yes. You can also use this in CCC: https://github.com/wombat94/EFIClone

Didn´t know this script. Great. Thank you so much.

 

[mrt209]

Hello, after trying to boot into recovery mode using sudo nvram "recovery-boot-mode=unused" && sudo reboot recovery my Mac Pro won’t boot, get no screen, then after a few minutes it reboots again... I had an old version of OC and updated it to the latest version. Any ideas? Thanks

Edit: Accidentally deleted the config file when I replaced the old OC files with the new ones, fixed by adding it again.

 

[Paolo-Sp]

For a few months now, this warning has appeared on my Mac Pro 5.1 with Big Sur that I don't know how to remove. The copparse coincided with the various spoffing tests by inserting the data of the Mac Pro 7.1 and related error in the RAM.

 

[TECK]

I suppose that all I have to do is make an standard backup and then copy manual the EFI contents. Right?

Yes. I don't bother with backups because I can generate a fresh EFI and reboot in 30 seconds.

 

[Dayo]

You may add that it works in RefindPlus.

Thanks. Just updated the issue on GitHub to reflect.

Took a look at this and there is a specific fix for this issue in RefindPlus which is why it works there.

Basically adapts some OC code from ProvideConsoleGOP which will run on a MacPro5,1 and fix the loading screen but will not run on a MacPro3,1 even when that flag is on. This is because the active function implementing ProvideConsoleGOP in OC returns early on MacPro3,1 as it does not have the Console GOP issue that the MacPro5,1 has.

The RefindPlus fix does not propagate to OC when chain-loading as all System Table changes done in RefindPlus are reverted (the original is stashed before any changes are made) before handing off to other loaders.

Basically, the fix is undone when you decide to load OpenCore or any other loader. Just out of caution so that loaders receive original System Tables without RefindPlus changes.

Updated your OC issue to point them at the fix.