Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

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

Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
After having untold amounts of problems trying to install big sur using the micropatcher I gave up and installed OpenCore. After amending the config plist I was able to install big sur without any problems, unfortuantly no WiFi but no matter I’ll update the card at some point.
Beta 5 was working quite well when the update to beta 6 turned up, upon trying to update I found myself exactly where I was with the micropatcher.
stage 1 of the install would complete the it just went into a bootloop, I did some more browsing
around the forums and found this
This is a copy n paste
The trick is to un-enroll in the beta program and then re-enroll
Unroll:

sudo /System/Library/PrivateFrameworks/Seeding.framework/Versions/A/Resources/seedutil unenroll

Enroll:

sudo /System/Library/PrivateFrameworks/Seeding.framework/Versions/A/Resources/seedutil enroll DeveloperSeed

I was stuck on Beta 5 and nothing including re-downloading the entire process worked. This worked first time I ran this in terminal and installed beta 5 and then updated to beta 6 flawlessly

Copied from the opencore forum on Facebook
 

Attachments

  • 23CA7762-792D-4753-B5F8-7D4138CA81B0.jpeg
    23CA7762-792D-4753-B5F8-7D4138CA81B0.jpeg
    300.6 KB · Views: 447
  • 89EB0296-4139-4750-897C-441D49ACA694.jpeg
    89EB0296-4139-4750-897C-441D49ACA694.jpeg
    233.6 KB · Views: 383
  • 9CF52C5A-F51F-4CD2-B507-9182A0DD51DA.jpeg
    9CF52C5A-F51F-4CD2-B507-9182A0DD51DA.jpeg
    383.6 KB · Views: 357
  • F1F6CBD8-7604-4947-B25F-5DB0B87B6FD1.jpeg
    F1F6CBD8-7604-4947-B25F-5DB0B87B6FD1.jpeg
    329.7 KB · Views: 358
Eweie said:
View attachment 952152
Click to expand...

The below important part of the above list was left out, See below. The list was created for hackintoshes not Apple legacy Mac Pro, so the claim that the HD.7870 is not supported may be correct. However if Dortiana’s list is correct it may work if the proper kexts are used. I have no personal experience with this, just noted the omission. Your mileage may vary.
————————

Needed kexts

Extras:

  • radpg=15: Required for HD 7730/7750/7770/R7 250/R7 250X GPU initialization)
  • InjectAMD: While deprecated, some users require this for proper initialization, avoid unless absolutely necessary
 
dataid said:
The below important part of the above list was left out, See below. The list was created for hackintoshes not Apple legacy Mac Pro, so the claim that the HD.7870 is not supported may be correct. However if Dortiana’s list is correct it may work if the proper kexts are used. I have no personal experience with this, just noted the omission. Your mileage may vary.
————————

Needed kexts

Extras:

  • radpg=15: Required for HD 7730/7750/7770/R7 250/R7 250X GPU initialization)
  • InjectAMD: While deprecated, some users require this for proper initialization, avoid unless absolutely necessary
Click to expand...
This discussion about this graphic card goes too far, and not OpenCore related anymore. It’s better to discuss this matter in the GPU support thread.

The reason why it’s not OpenCore (on cMP) related is because this card doesn’t shipped with a UEFI GOP ROM. Which is required for displaying boot screen on cMP via OpenCore. (For Hackintosh, this doesn’t matter, the graphic card can provide basic display support once power up).

For kext editing, or adding support by WhateverGreen, etc, these are the GPU supporting (inside MacOS) issue, not quite OpenCore related.

Of course, we can patch the kext, or inject WhateverGreen via OpenCore, but clearly the discussion isn’t on that direction.

For flashing, this card works inside Mojave WITHOUT flashing the HD7950 Mac EFI UGA (this is NOT the UEFI GOO that OpenCore need), because it can use the RadeonFramebuffer.

But once you flashed it, this card will be assigned an incorrect Framebuffer, which seems make it incompatible to Mojave anymore.

If there is anything OpenCore can help, that will be manually inject (and override) the incorrect Framebuffer which comes from the Mac EFI UGA.

So that the 7870 can display boot screen via flashing, and may able to work in Mojave via OpenCore Framebuffer patching.
 
Last edited:
  • Like
Reactions: Kai.Def
I have a problem once I get to OpenCore boot picker (all is well including the MacPro 5.1 mid 2010 booting to the boot picker that displays the only available OS, which is a DosDude patched version of Catalina). I let OpenCore pick the OS, and after a couple of seconds, the text on the screen disappears briefly, to come back up to the boot options (just Catalina). At this point I can select it using the arrows and pressing enter, but the same thing happens.
So, it is the Catalina on my boot drive that just doesn't boot from OpenCore.
Does anyone know if this is a problem with me using Catalina instead of Mojave, or if it is because it is patched using DosDude patcher, or if there is anything else I am missing? I have gone over the instruction precisely a few times and I get the same result. Catalina refuses to boot, so I can't move to checking what has happened and installing Catalina on the drive I have selected to have OpenCore.
Any suggestion would be much appreciated.
 
giocar64 said:
the screen disappears briefly, to come back up to the boot options
Click to expand...
Sounds like a misconfigured config file and/or missing elements in your OpenCore package.

Run ocvalidate on your config file as first step:
- drag the ocvalidate into terminal, add a space, then drag your config file in and enter.

if that doesn't give you any clear pointers, run a debug version and check the output:
- Swap the files listed here to debug
 
  • Like
Reactions: JedNZ
Could be unrelated, but since updating to OC 0.6.1 my Windows 10 installation is having trouble booting. I'll select it from the OpenCanopy boot picker, then the Windows logo appears and hangs forever. No spinning loading dots. I shut down and repeat this twice. On the third attempt I get the automatic diagnosis window. Startup repair fails, but if I click Exit and Continue to Windows it boots just fine the third time.
 
I have [finally ...] installed Open Core successfully. cMP 4.1 >5.1 conversion.

One thing I'm still unclear about though, is are both disks (Disk A and Disk B required to stay in place or can I just leave the Mojave > Catalina drive in place and remove "Disk A" ?

Thanks!
 
hwojtek said:
Once you remove "Disk A", you remove OC from your computer, so you do the math...
Click to expand...

I thought that might be the case, but I don't see that explicitly stated. Can I use the rest of the 2 TB dive I allocated for Disk A or no?
 
No, you need to put your (working) OC installation verbatim to the "EFI" partition of your system disk.
Since messing with the EFI partition of a system disk is sort of a sketchy deal (it will render the computer unbootable if done wrong) the guide splits EFI and system disk to two separate drives, in order to have a bootable vanilla OS disk.
This said - there is nothing against putting a working OC installation into the EFI partition of the system disk. I assume hundreds of people have done it (yours truly included).
 
Last edited:
h9826790 said:
This discussion about this graphic card goes too far, and not OpenCore related anymore. It’s better to discuss this matter in the GPU support thread.

The reason why it’s not OpenCore (on cMP) related is because this card doesn’t shipped with a UEFI GOP ROM. Which is required for displaying boot screen on cMP via OpenCore. (For Hackintosh, this doesn’t matter, the graphic card can provide basic display support once power up).

For kext editing, or adding support by WhateverGreen, etc, these are the GPU supporting (inside MacOS) issue, not quite OpenCore related.

Of course, we can patch the kext, or inject WhateverGreen via OpenCore, but clearly the discussion isn’t on that direction.

For flashing, this card works inside Mojave WITHOUT flashing the HD7950 Mac EFI UGA (this is NOT the UEFI GOO that OpenCore need), because it can use the RadeonFramebuffer.

But once you flashed it, this card will be assigned an incorrect Framebuffer, which seems make it incompatible to Mojave anymore.

If there is anything OpenCore can help, that will be manually inject (and override) the incorrect Framebuffer which comes from the Mac EFI UGA.

So that the 7870 can display boot screen via flashing, and may able to work in Mojave via OpenCore Framebuffer patching.
Click to expand...
Sorry by continuing this totally off topic, but HD 7870 support issues are more complex since there are HD 7870 cards that are based on Tahiti and Pitcairn, examples:

AMD Radeon HD 7870 XT
AMD Radeon HD 7870 GHz Edition

The video cards that have the Tahiti GPU version still works perfectly with Mojave, while Pitcairn ones work up to High Sierra. Both GPU versions don't have GOP support, the cards were released more than a year before the UEFI 1.3b ratification.

One last interesting note, late-2013 Mac Pro D300 GPU is a Pitcairn derivative with different PCIeID and still work with Mojave and newer macOS releases, Apple removed support only for PC cards.
 
Nice work y'all. I'm planning on setting up OC at some point this fall when I can free up some time to devote to it. Maybe in conjunction with the Big Sur release (I skipped Catalina).

Pardon me if this has already been discussed (I tried searching first) but I wonder if anyone has tested whether emulating a newer Mac via OC allows WiFi calling to be turned on--assuming you have already upgraded the Airport card. This feature works via the FaceTime app and allows you to place or receive calls even if you don't have your iPhone nearby. Obviously it's a carrier-dependent feature--not sure how widespread it is globally but all the main carriers in the US have it.

Even though we've been able to achieve all the newer Continuity/Handoff features with a new card and terminal command, the cMP has (to my knowledge anyway) never been allowed to enable WiFi calling. Has anyone tried to get it working via OC? Not sure whether it's a platform check or a SN check.

You can tell if it's available by looking at what appears in FaceTime preferences on the Mac (after you've enabled it on your phone first). Normally the cMP shows this:
cMPNoWiFiCalling.jpg

If WiFi calling is available/enabled you'll see this instead (found this image on the web):

facetime-settings-phone.jpg

Here's Apple's Support article about how to turn it on and here's an older thread in this forum asking about whether it can work on the 2012 cMP.

Any input appreciated. Thanks!
 
bookemdano said:
Nice work y'all. I'm planning on setting up OC at some point this fall when I can free up some time to devote to it. Maybe in conjunction with the Big Sur release (I skipped Catalina).

Pardon me if this has already been discussed (I tried searching first) but I wonder if anyone has tested whether emulating a newer Mac via OC allows WiFi calling to be turned on--assuming you have already upgraded the Airport card. This feature works via the FaceTime app and allows you to place or receive calls even if you don't have your iPhone nearby. Obviously it's a carrier-dependent feature--not sure how widespread it is globally but all the main carriers in the US have it.

Even though we've been able to achieve all the newer Continuity/Handoff features with a new card and terminal command, the cMP has (to my knowledge anyway) never been allowed to enable WiFi calling. Has anyone tried to get it working via OC? Not sure whether it's a platform check or a SN check.

You can tell if it's available by looking at what appears in FaceTime preferences on the Mac (after you've enabled it on your phone first). Normally the cMP shows this:
View attachment 953011

If WiFi calling is available/enabled you'll see this instead (found this image on the web):

View attachment 953012

Here's Apple's Support article about how to turn it on and here's an older thread in this forum asking about whether it can work on the 2012 cMP.

Any input appreciated. Thanks!
Click to expand...
I just tested wifi calling from my cMP and it works. My phone line is on a 13.5 IOS device.
1600127252581.png

1600127213273.png
 
  • Like
Reactions: bookemdano
Quick question, If I'm only planing on only using Mojave, do I need to install OC to take advantage of Hardware Acceleration tweaks?
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back