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

[tsialex]

Gtx680 has no original bios that supports UEFI
maybe flashing gtx 770 gives a chance.

EVGA GTX 770 VBIOS

2048 MB GDDR5, 1111 MHz GPU, 1753 MHz Memory

www.techpowerup.com

Dont know if this rom works.

Yes, it has. eVGA offered it for some time for anyone that asked via support.

 

[papadj3]

Expert-roobarb:
Is there a way to use the Windows Legacy Install with a 5,1 using Open Core, without losing Open Core during switching from Win 10 to Mac Catalina?? Would love to know a procedure!

 

[hknatm]

Yes, it has. eVGA offered it for some time for anyone that asked via support.

Now will try that, hope i wont get bricked gpu

 

[papadj3]

Expert roobarb! - Re- #1,303?
How do you use your attachment 2020-02-22_OC_REFIND_EFI.zip and can you describe the procedure? I can’t follow the “Clip” I am a REAL NEWBIE- Is there a way to use the Windows Legacy Install with Open Core(0.5.5 or 0.5.6??), without losing Open Core during switching from Win 10 to Mac Catalina??
Would love to know a procedure!
I have a Legacy Windows 10 on a Separate SSD-
Thanks- papadj3

 

[tsialex]

Expert roobarb! - Re- #1,303?
How do you use your attachment 2020-02-22_OC_REFIND_EFI.zip and can you describe the procedure? I can’t follow the “Clip” I am a REAL NEWBIE- Is there a way to use the Windows Legacy Install with Open Core(0.5.5 or 0.5.6??), without losing Open Core during switching from Win 10 to Mac Catalina??
Would love to know a procedure!
I have a Legacy Windows 10 on a Separate SSD-
Thanks- papadj3

Your idea is flawed from the start, OpenCore don't support booting CSM Windows at all.

 

[roobarb!]

Expert-roobarb:
Is there a way to use the Windows Legacy Install with a 5,1 using Open Core, without losing Open Core during switching from Win 10 to Mac Catalina?? Would love to know a procedure!

I do this all the time, I just don't use the boot pickers in macOS or Windows. Take a look back at this post; that's the version of OC I'm still using right now. For me it boots with the three options shown in the video (Mojave, Windows, Catalina). To set the default, when the OC boot picker appears just select the one you want as default and hit CTRL-RETURN. If you want to temporarily boot into one or the other, just choose it and hit RETURN as normal.

I usually leave it with Windows selected as default, so if that's the OS I'm using that day, when I walk away and it decides to randomly auto-update it's at least sat at the correct OS with the updates partially complete, rather than defaulting to Catalina, where I'd then have to reboot and wait for the Windows updates to finish.

And to be clear, it's rEFInd which is handling the boot of Windows in CSM mode - OC can't boot CSM Windows, but it can boot rEFInd, which in turn can boot CSM Windows. It's chainloading; not supported by OC IIRC, but it works perfectly for me.

Follow the instructions in #1 to drop the .zip file contents into an EFI partition and bless the partition. Reboot. It's really that easy.

 

[205Maxi]

OC developers are working on their own GUI Bootliquor.efi.
It is still in development and it is not in the manual from what I understand. Those of you who already tested NdkBootPicker.efi may test easily BootLiquor.efi. All you have to do is:

<key>UEFI</key>
    <dict>
        <key>ConnectDrivers</key>
        <true/>
        <key>Drivers</key>
        <array>
            <string>FwRuntimeServices.efi</string>
            <string>NTFS.efi</string>
            <string>#NdkBootPicker.efi</string>
            <string>BootLiquor.efi</string>

Of course you need to put BootLiquor.efi in the drivers folder and the "Resources" folder inside the OC folder. Generate the "Resources" folder with Pavo's OC builder
If you want to compile it from master you may need to issue this command (if you have errors compiling):

# Change the path if you installed Xcode somewhere else.
sudo xcode-select -s /Applications/Xcode.app/Contents/Developer

View attachment 899188
After pressing spacebar I got some icons getting out of the screen. There is no secondary raw like in NDK's bootlicker:
View attachment 899190

Hello I would love to set this up instead of NdkBootPicker.efi... Do you have an how to just to compile the Bootliquor.efi? I already have the resources files. I would really appreciate your help. Thank you.

 

[startergo]

Do you have an how to just to compile the Bootliquor.efi

GitHub - Pavo-IM/ocbuilder

Contribute to Pavo-IM/ocbuilder development by creating an account on GitHub.

github.com

It will generate the complete structure with or without the kexts. Bear in mind that FwRuntimeServices.efi is no more if you compile from the master branch (it is renamed). Just compare the sample.config generated there with yours and make the necessary adjustments. Also consult with the updated manual which will also be generated.

 

[Charmandrigo]

so I came back to this thread after the first time it was created and updated opencore to the latest release (I used this method with the old opencore 0.5.4 I believe)

By disabling only the VMM flag I understand Opencore is still booting on the Mac's bootscreen but I remember Opencore was not compatible with Windows installed on Legacy boot, is the newest version of opencore now compatible with windows installed on Legacy? because if that's not the case then I have to disable opencore completely and not just the VMM flag. How do I do that now? and let me boot Cataline just with the native method of sudo nvram boot-args="-no_compat_check"?

I should mention the Opencore bootscreen only shows my Mac drives and the recovery partition, but not my Windows drive

 

[papadj3]

tsialex - I don't even know how to word my request! Thanks for the real issue with Win10 Legacy install! *BUT ALSO*
*Thank-You roobarb!* for exactly what I was looking for! A way to boot Win10 Legacy while still using Open Core!!? Just to clarify for me, If I follow Post #1 and use the new 0.5.6 config and drop your zip into my EFI (adding rEFInd) will it work???

 

[08380728]

wow, you guys kick ass...

Is there a downloadable zipfile of a working EFI OpenCore folder for a MacPro 4,1 flashed to 5,1 with a Radeon RX 580?

Will it finally give us boot screen?

 

[cdf]

wow, you guys kick ass...

Is there a downloadable zipfile of a working EFI OpenCore folder for a MacPro 4,1 flashed to 5,1 with a Radeon RX 580?

Will it finally give us boot screen?

You will get a basic boot screen. I recommend that you follow the guide in the first post.

 

[safari70]

Hi,

I’ve been running Catalina 10.15.3 For a while on Mac Pro 5.1 after following thread #1.

Yesterday I enabled VMM and upgraded to 10.15.4, after the reboot I could see OC boot list, I chose Catalina, and it continued booting up for a bit but then went into a reboot cycle without successfully booting up 10.15.4.

On the 3rd reboot I chose my Mojave drive and it booted up fine...

I disabled VMM from Mojave them rebooted it into 10.15.4 without issues.

Anyone seeing something similar?

Thanks!

 

[cdf]

Anyone seeing something similar?

Yes. I saw this after updating to the last beta of 10.15.4. It was fine after a reboot.

 

[safari70]

Yes. I saw this after updating to the last beta of 10.15.4. It was fine after a reboot.

I let it reboot two times but it never finished booting up into 10.15.4, just keeps on stalling and rebooting... I am attaching my config file (changed it to .txt), if you have time to take a look for any obvious misconfigs I'd appreciate it...

Thanks.

 

[cdf]

I am attaching my config file (changed it to .txt), if you have time to take a look for any obvious misconfigs I'd appreciate it...

There are three formatting differences between your config and the one from the guide, but the content is the same. Perhaps you could try the one from the guide.

 

[startergo]

There are three formatting differences between your config and the one from the guide, but the content is the same. Perhaps you could try the one from the guide.

I still can't update either. When it asks to reboot to update it just gets stuck in the beginning of the progress bar with the apple logo. This is not the cold reboot but the "update reboot" phase. There might be some setting in the config file which is messing it up.
[automerge]1585157292[/automerge]
Otherwise I successfully updated my VMware cat 10.15.2 to 10.15.4. That one runs perfect even with the iMessage and FaceTime.

 

[cdf]

I still can't update either. When it asks to reboot to update it just gets stuck in the beginning of the progress bar with the apple logo. This is not the cold reboot but the "update reboot" phase. There might be some setting in the config file which is messing it up.

Strange. Did you check your debug log? Was your previous installation a patched one?

 

[MoerBoer]

When I did my update to 10.15.4, I re-enabled the VMM flag, rebooted and then started the update.

When it rebooted, on the bootpicker it was on "Install OSx" or something like that. Select that one ( It should be on it ) and it will do the final part of the update.

After that it set the boot sequence back to normal on the bootpicker and on next reboot the "Install OSX" was gone and everything was back to normal.

I then undid the VMM flag, last reboot and all is well.

 

[startergo]

Strange. Did you check your debug log? Was your previous installation a patched one?

As I said it is not a cold reboot so OC debug log would not be triggered anyway ( I use Release). It was a patched (dosdude's) installation correct. I wonder if there is any way to remove the patches (make it vanilla except the -no_compat_check argument) without starting from scratch.

 

[safari70]

There are three formatting differences between your config and the one from the guide, but the content is the same. Perhaps you could try the one from the guide.

so I used the original config file from 1st post with similar results - I reinstalled 10.15.4 (from full installer) but still seeing same issue.

Actually I found that if I let it reboot 3 times (without VMM) it will eventually boot up 10.15.4 but it's very sluggish with some visual artifacts (no problem at all when VMM is enabled).

When it eventually boots up, I get a message that the "system was shutdown during boot up" (or similar) and it asks if I want to send the panic report to apple (attached here). I'd appreciate any help with this.

Thanks!

 

[w1z]

I’ve had the same smooth experience @cdf had when updating to 10.15.4

What I did:

1. Enabled VMM flag
2. Removed SystemBoard and set its corresponding flag to false
3. Rebooted then updated to 10.15.4
4. Once the update completed, I disabled the VMM flag and added the SystemBoard entry back and set its corresponding flag back to true

Running latest OC compiled from master release branch.

 

[cdf]

so I used the original config file from 1st post with similar results - I reinstalled 10.15.4 (from full installer) but still seeing same issue.

Actually I found that if I let it reboot 3 times (without VMM) it will eventually boot up 10.15.4 but it's very sluggish with some visual artifacts (no problem at all when VMM is enabled).

When it eventually boots up, I get a message that the "system was shutdown during boot up" (or similar) and it asks if I want to send the panic report to apple (attached here). I'd appreciate any help with this.

Thanks!

Perhaps you could rule out OpenCore by booting without it (make sure to manually add -no_compat_check in recovery before).

 

[08380728]

Can I propose a request, the original poster or someone with his consent, to deploy the OpenCore for MacPro project to GitHub. It would allow people to identify issues, suggest potential solutions and bring people together in a centralised, shared efforts approach.



Not only would it reduce replicated/duplicated efforts of people working in isolation, it would help order and standardise information.



Having this thread with everyone asking loads of different questions all of over the place is making it all much harder for each and everyone of us for no good reason.



The OpenCore for MacPro could have different branches, on for Mojave, Catalina etc.

 

[startergo]

Perhaps you could rule out OpenCore by booting without it (make sure to manually add -no_compat_check in recovery before).

Ok I finally upgraded. I did some changes in the config file although I don't know which one was holding up the upgrade. Configs are attached.