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.
sofyan said:
Mac Pro 4.1->5.1 user here, with OpenCore 0.63 and the latest Catalina, My Home is working here with Hue smart lamps.
Click to expand...
Thanks for the +ve report, I wonder what is different on my setup. Just tried it again with a warm reboot and I have five houses now. I can edit these new ones which appear on my iPad immediately, but something has to be a bit off for it to be happening in the first place. I'm just digging out my vanilla MacBook Pro to test on there.
 
roobarb! said:
Thanks for the +ve report, I wonder what is different on my setup. Just tried it again with a warm reboot and I have five houses now. I can edit these new ones which appear on my iPad immediately, but something has to be a bit off for it to be happening in the first place. I'm just digging out my vanilla MacBook Pro to test on there.
Click to expand...
I uploaded a picture. Perhaps login out of iCloud could fix/reset the settings on the mac pro?
 
  • Like
Reactions: roobarb!
roobarb! said:
Is anyone else here using HomeKit on a Mac Pro with OpenCore? If you are, is it working for you? Because it's not here.

I've done this a few times now and here's how it goes. I delete all homes until I'm left with one which is seen by both the Mac Pro and my iPad. I set up that home. Everything is fine. I reboot the Mac Pro and relaunch the Home app. The home app doesn't see the home I've just created, but the iPad does. The Home app on macOS appears to create a new "My Home" which appears on the iPad as an additional home. It's usually around this point that the configured and working home gets "No Response" on all accessories and is effectively dead.

View attachment 1698898View attachment 1698900

I can rinse and repeat this as many times as I like. Every time the Home app on macOS is launched after a reboot a new "My Home" is created and it can no longer see the original, or any of the others it has created.

I'm posting here because OpenCore and macOS Catalina are the only 'odd' things about this system that I can think of that would possibly affect an iCloud service in this way, though I have no idea by what means. Does anybody have some insight? I'm on OpenCore 0.6.4 and my config is here.
Click to expand...
I don't think this is OC related, more like macOS bug.

Anyway, I am use OC 0.6.4 with Big Sur. Home apps works fine. I can also use Siri (on my cMP, iPhone, and iPad) to control all the lights (Hue). And all automations also work as expected.
 
  • Like
Reactions: Eschers and roobarb!
h9826790 said:
I don't think this is OC related, more like macOS bug.

Anyway, I am use OC 0.6.4 with Big Sur. Home apps works fine. I can also use Siri (on my cMP, iPhone, and iPad) to control all the lights (Hue). And all automations also work as expected.
Click to expand...
Well, how embarrasing. I've tried the old sign-out, sign-in to iCloud and it now seems to work. I swear I had no luck with this last night! Sorry folks, false alarm. :)

EDIT: ARGH! It's doing it again! It's unlikely to be OpenCore related if you folk are having success. I will go and take a stern look at my setup.

EDIT2: This machine was in need of a shake-down, so I've reinstalled. Less hassle than chasing this around the houses. The issue appears to be gone.
 
Last edited:
  • Like
Reactions: h9826790
Eschers said:
is it dangerous to pop in a SSD with GPT Windows 10 installed and then select in the bootpicker
Click to expand...
As long as you boot it through OC it is ok (providing you use the config file in the first post as a base and ProtectSecureBoot is enabled). If I were you I would also remove the BOOTx64.efi file from the ESP partition of the SSD drive. OC does not need it for booting. You can zip it if you need it later. Also after every update/upgrade Windows may recreate that file.
 
  • Like
Reactions: Eschers and Macschrauber
So I was playing with the USB3 ports in Big Sur. I have an Asmedia3142 controller PCIE card and I am now able to provide these properties when my iPad is connected:
1608589970616.png

1608589543064.png
 

Attachments

  • USBMap.kext.zip
    2.1 KB · Views: 96
  • SSDT-EC-USBX.aml.zip
    364 bytes · Views: 83
  • SSDT-RHUB-Reset.zip
    685 bytes · Views: 76
Last edited:
  • Like
Reactions: Eschers, h9826790, TECK and 1 other person
bookemdano said:
Then you more than anyone should know that it really sucks to put a lot of time and work into something for the sole purpose of helping people and then be criticized by the same people you were attempting to help. Think about your words before uttering them.
Click to expand...
I don't intend to become a part of the ongoing feud in this thread, so just to be brief, yeah, it probably sucks.

What words exactly?
 
After perusing this thread for a few weeks I finally mustered up the nerve to install OC (0.6.4)...AND...all went well. I had a spare drive so I didn't bother with the 2 drive method in the instructions. I removed my original boot drive and all other drives. I did a fresh Mojave install to the spare drive and then copied OC files straight to the spare drive's EFI partition. Upon completion of the copying and the PLIST editing and the doling out of blessings, I booted back into Mojave with intentions to install Catalina.

With the VMM switch still set from the initial setup, software update presented me with the Big Sur 11.1 update. Being how this was a test drive, I accepted it. BS installation ran through to a successful completion and so far everything seems to be working fine.

Some notables:

The AMD drivers (I'm running a Gigabyte RX 560) must've been changed since High Sierra (the OS on my original boot drive) because I got screen flickering in both Mojave and BS on first boot up. This issue did not exist under HS. So far the only way to correct it is toggle in and out of Sleep after boot or reboot. Does anyone have experience with this?

I'd like to install Windows but noticed the recommended Windows install PLIST file at the bottom of APPENDIX appears to be identical to the PLIST at the start of the instructions in PART 1, yet claims to have modifications "to protect the Mac Pro from potential damage caused by UEFI Windows". Does anyone have any insight into this? Is the PLIST from PART 1 just written to default now to protecting the firmware from Windows UEFI writes?

What is the hardware acceleration for? I've seen this asked before but no straight answer was given. Are the GPUs drivers in the newer macOS's not running accelerated under OC without the steps in Part III? I haven't tried gaming but the OS is running well without having done those steps yet.

Hardware: Mac Pro 2012, 6-core, 32GB RAM, Gigbyte RX 560 4GB, BT 4.0, WiFi.ac, OWC SATA3 card with 840 EVO, USB 3.0. After I feel this out and get comfy with it on this machine I intend to install OC and Big Sur on my 12-core with Macvid RX 580 and NVME boot drive.

And a big THANKS to all involved in OC and the terrific information in this thread!
 
  • Like
Reactions: Eschers
marzer said:
I'd like to install Windows but noticed the recommended Windows install PLIST file at the bottom of APPENDIX appears to be identical to the PLIST at the start of the instructions in PART 1, yet claims to have modifications "to protect the Mac Pro from potential damage caused by UEFI Windows". Does anyone have any insight into this? Is the PLIST from PART 1 just written to default now to protecting the firmware from Windows UEFI writes?
Click to expand...
The parameter "ProtectSecureBoot" is set to "true" by default as far as I have understood, so once GPT Win10 is configured no stuff will be written in your Bootrom after windows updates etc. when using this standard config..
 
  • Like
Reactions: startergo
Eschers said:
The parameter "ProtectSecureBoot" is set to "true" by default as far as I have understood, so once GPT Win10 is configured no stuff will be written in your Bootrom after windows updates etc. when using this standard config..
Click to expand...
No certificates will be written to the NVRAM at Windows boot. Not related to updates/upgrades.
 
  • Like
Reactions: Eschers
Hello, i have installed Big Sur with opencore and it work fine. I have 2 problem now :
1. My 10Gb Solo card Ethernet card is down
2. For material accelleration, i dont unterstand how find the graphic card path, because, when i exectute the gfxutil, i have about 50 lines with Pci root... :

00:00.0 8086:3405 /PCI0@0/ESI@0 = PciRoot(0x0)/Pci(0x0,0x0)
00:01.0 8086:3408 /PCI0@0/IOU2@1 = PciRoot(0x0)/Pci(0x1,0x0)
00:03.0 8086:340a /PCI0@0/IOU0@3 = PciRoot(0x0)/Pci(0x3,0x0)
00:07.0 8086:340e /PCI0@0/IOU1@7 = PciRoot(0x0)/Pci(0x7,0x0)
00:0d.0 8086:343a /PCI0@0/pci8086,343a@D = PciRoot(0x0)/Pci(0xD,0x0)
00:0d.1 8086:343b /PCI0@0/pci8086,343b@D,1 = PciRoot(0x0)/Pci(0xD,0x1)
00:0d.2 8086:343c /PCI0@0/pci8086,343c@D,2 = PciRoot(0x0)/Pci(0xD,0x2)
00:0d.3 8086:343d /PCI0@0/pci8086,343d@D,3 = PciRoot(0x0)/Pci(0xD,0x3)
00:0d.4 8086:3418 /PCI0@0/pci8086,3418@D,4 = PciRoot(0x0)/Pci(0xD,0x4)
00:0d.6 8086:341a /PCI0@0/pci8086,341a@D,6 = PciRoot(0x0)/Pci(0xD,0x6)
0f:00.0 111d:8061 /PCI0@0/IOU2@1/I2PS@0 = PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)
00:0d.5 8086:3419 /PCI0@0/pci8086,3419@D,5 = PciRoot(0x0)/Pci(0xD,0x5)
00:0d.7 8086:341b /PCI0@0/pci8086,341b@D,7 = PciRoot(0x0)/Pci(0xD,0x7)
00:0e.0 8086:341c /PCI0@0/pci8086,341c@E = PciRoot(0x0)/Pci(0xE,0x0)
00:0e.1 8086:341d /PCI0@0/pci8086,341d@E,1 = PciRoot(0x0)/Pci(0xE,0x1)
05:00.0 1002:67df /PCI0@0/IOU0@3/GFX0@0 = PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)
00:0e.2 8086:341e /PCI0@0/pci8086,341e@E,2 = PciRoot(0x0)/Pci(0xE,0x2)
00:0e.3 8086:341f /PCI0@0/pci8086,341f@E,3 = PciRoot(0x0)/Pci(0xE,0x3)
00:0e.4 8086:3439 /PCI0@0/pci8086,3439@E,4 = PciRoot(0x0)/Pci(0xE,0x4)
05:00.1 1002:aaf0 /PCI0@0/IOU0@3/PXS1@0,1 = PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x1)
00:0f.0 8086:3424 /PCI0@0/pci8086,3424@F = PciRoot(0x0)/Pci(0xF,0x0)
00:10.0 8086:3425 /PCI0@0/pci8086,3425@10 = PciRoot(0x0)/Pci(0x10,0x0)
00:10.1 8086:3426 /PCI0@0/pci8086,3426@10,1 = PciRoot(0x0)/Pci(0x10,0x1)
00:11.0 8086:3427 /PCI0@0/pci8086,3427@11 = PciRoot(0x0)/Pci(0x11,0x0)
00:11.1 8086:3428 /PCI0@0/pci8086,3428@11,1 = PciRoot(0x0)/Pci(0x11,0x1)
00:13.0 8086:342d /PCI0@0/pci8086,342d@13 = PciRoot(0x0)/Pci(0x13,0x0)
00:14.0 8086:342e /PCI0@0/pci8086,342e@14 = PciRoot(0x0)/Pci(0x14,0x0)
00:14.1 8086:3422 /PCI0@0/pci8086,3422@14,1 = PciRoot(0x0)/Pci(0x14,0x1)
00:14.2 8086:3423 /PCI0@0/pci8086,3423@14,2 = PciRoot(0x0)/Pci(0x14,0x2)
00:14.3 8086:3438 /PCI0@0/pci8086,3438@14,3 = PciRoot(0x0)/Pci(0x14,0x3)
00:15.0 8086:342f /PCI0@0/pci8086,342f@15 = PciRoot(0x0)/Pci(0x15,0x0)
00:16.0 8086:3430 /PCI0@0/pci8086,3430@16 = PciRoot(0x0)/Pci(0x16,0x0)
00:16.1 8086:3431 /PCI0@0/pci8086,3431@16,1 = PciRoot(0x0)/Pci(0x16,0x1)
00:16.2 8086:3432 /PCI0@0/pci8086,3432@16,2 = PciRoot(0x0)/Pci(0x16,0x2)
00:16.3 8086:3433 /PCI0@0/pci8086,3433@16,3 = PciRoot(0x0)/Pci(0x16,0x3)
00:16.4 8086:3429 /PCI0@0/pci8086,3429@16,4 = PciRoot(0x0)/Pci(0x16,0x4)
00:16.5 8086:342a /PCI0@0/pci8086,342a@16,5 = PciRoot(0x0)/Pci(0x16,0x5)
00:16.6 8086:342b /PCI0@0/pci8086,342b@16,6 = PciRoot(0x0)/Pci(0x16,0x6)
00:16.7 8086:342c /PCI0@0/pci8086,342c@16,7 = PciRoot(0x0)/Pci(0x16,0x7)
00:1a.0 8086:3a37 /PCI0@0/UHC4@1A = PciRoot(0x0)/Pci(0x1A,0x0)
00:1a.1 8086:3a38 /PCI0@0/UHC5@1A,1 = PciRoot(0x0)/Pci(0x1A,0x1)
10:02.0 111d:8061 /PCI0@0/IOU2@1/I2PS@0/PPB2@2 = PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x2,0x0)
00:1a.2 8086:3a39 /PCI0@0/UHC6@1A,2 = PciRoot(0x0)/Pci(0x1A,0x2)
10:04.0 111d:8061 /PCI0@0/IOU2@1/I2PS@0/PPB4@4 = PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x4,0x0)
00:1a.7 8086:3a3c /PCI0@0/EHC2@1A,7 = PciRoot(0x0)/Pci(0x1A,0x7)
00:1b.0 8086:3a3e /PCI0@0/HDEF@1B = PciRoot(0x0)/Pci(0x1B,0x0)
00:1c.0 8086:3a40 /PCI0@0/pci-bridge@1C = PciRoot(0x0)/Pci(0x1C,0x0)
00:1c.1 8086:3a42 /PCI0@0/pci-bridge@1C,1 = PciRoot(0x0)/Pci(0x1C,0x1)
00:1c.2 8086:3a44 /PCI0@0/RP03@1C,2 = PciRoot(0x0)/Pci(0x1C,0x2)
00:1c.4 8086:3a48 /PCI0@0/RP05@1C,4 = PciRoot(0x0)/Pci(0x1C,0x4)
00:1c.3 8086:3a46 /PCI0@0/RP04@1C,3 = PciRoot(0x0)/Pci(0x1C,0x3)
00:1c.5 8086:3a4a /PCI0@0/RP06@1C,5 = PciRoot(0x0)/Pci(0x1C,0x5)
11:00.0 1b21:1242 /PCI0@0/IOU2@1/I2PS@0/PPB2@2/PXS3@0 = PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x2,0x0)/Pci(0x0,0x0)
00:1d.0 8086:3a34 /PCI0@0/UHC1@1D = PciRoot(0x0)/Pci(0x1D,0x0)
12:00.0 1d6a:87b1 /PCI0@0/IOU2@1/I2PS@0/PPB4@4/PXS4@0 = PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x4,0x0)/Pci(0x0,0x0)
00:1d.1 8086:3a35 /PCI0@0/UHC2@1D,1 = PciRoot(0x0)/Pci(0x1D,0x1)
09:00.0 8086:10f6 /PCI0@0/RP03@1C,2/ETH0@0 = PciRoot(0x0)/Pci(0x1C,0x2)/Pci(0x0,0x0)
00:1d.7 8086:3a3a /PCI0@0/EHC1@1D,7 = PciRoot(0x0)/Pci(0x1D,0x7)
00:1e.0 8086:244e /PCI0@0/pci-bridge@1E = PciRoot(0x0)/Pci(0x1E,0x0)
00:1d.2 8086:3a36 /PCI0@0/UHC3@1D,2 = PciRoot(0x0)/Pci(0x1D,0x2)
00:1f.0 8086:3a18 /PCI0@0/LPCB@1F = PciRoot(0x0)/Pci(0x1F,0x0)
00:1f.2 8086:3a22 /PCI0@0/SATA@1F,2 = PciRoot(0x0)/Pci(0x1F,0x2)
00:1f.3 8086:3a30 /PCI0@0/SBUS@1F,3 = PciRoot(0x0)/Pci(0x1F,0x3)
0b:00.0 104c:823e /PCI0@0/RP05@1C,4/FWBR@0 = PciRoot(0x0)/Pci(0x1C,0x4)/Pci(0x0,0x0)
0a:00.0 8086:10f6 /PCI0@0/RP04@1C,3/ETH1@0 = PciRoot(0x0)/Pci(0x1C,0x3)/Pci(0x0,0x0)
0c:00.0 104c:823f /PCI0@0/RP05@1C,4/FWBR@0/FRWR@0 = PciRoot(0x0)/Pci(0x1C,0x4)/Pci(0x0,0x0)/Pci(0x0,0x0)

If you can help me on theses problems...
 
thefbi said:
2. For material accelleration, i dont unterstand how find the graphic card path, because, when i exectute the gfxutil, i have about 50 lines with Pci root... :
Click to expand...
Maybe look at the parts of the lines that don't say Pci root...
The first part is the PCI bus:device:function
The second part is vendor:product IDs
The third part is the ioreg path /PCI0/...
The last part is the EFI path PciRoot(0x0)/...

Looks like you have a Radeon at 05:00.0 (vendor ID 1002 = AMD). https://pci-ids.ucw.cz/read/PC/1002/67df
05:00.1 is the corresponding display audio device. https://pci-ids.ucw.cz/read/PC/1002/aaf0
 
thefbi said:
2. For material accelleration, i dont unterstand how find the graphic card path, because, when i exectute the gfxutil, i have about 50 lines with Pci root... :
Click to expand...
As described in the guide, you should to run gfxutil -f display, and according to what you posted above, you should see

05:00.0 1002:67df /PCI0@0/IOU0@3/GFX0@0 = PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)
 
  • Like
Reactions: IceHouse and startergo
marzer said:
When you said “Not related to updates/upgrades“, I mistakingly assumed the protectsecureboot plist setting did not apply to updates/upgrades.
Click to expand...
That parameter is related to the certificates writes to the NVRAM. Again not sure what else is bothering you. What damages do updates/upgrades? I know only that they recreate the BOOTx64.efi. That is not a damage, if OC resides in the same EFI folder as the Windows boot file, Windows will overwrite the OC BOOTx64.efi. The solution for such an issue is described by @cdf above.
 
  • Like
Reactions: marzer
Eschers said:
The parameter "ProtectSecureBoot" is set to "true" by default as far as I have understood, so once GPT Win10 is configured no stuff will be written in your Bootrom after windows updates etc. when using this standard config..
Click to expand...
Thanks. Is this from experience? Do you have Windows loaded using Boot Camp? The OC manual says a Boot Camp install SHOULD work but its not supported. Even post #1 seems out of date given the discrepancy I noted in the two PLIST's not being different.

My biggest concern is having my firmware corrupted. I searched the nearly 6000! posts (LOL) and couldn't find an understandable means to foolproof against firmware corruption. I also noticed that with OC loaded I can no longer perform a legacy Windows install. This is very confusing. <derp!> :D
 
  • Like
Reactions: Eschers
startergo said:
That parameter is related to the certificates writes to the NVRAM. Again not sure what else is bothering you. What damages do updates/upgrades? I know only that they recreate the BOOTx64.efi. That is not a damage, if OC resides in the same EFI folder as the Windows boot file, Windows will overwrite the OC BOOTx64.efi. The solution for such an issue is described by @cdf above.
Click to expand...
Thanks. Apparently I have a lot more to learn about the workings of EFI before I can install Windows without corrupting the firmware. There are so many warnings about it throughout this forum that I take it very seriously. I just haven't found any information on fool proofing the firmware or how to recover corrupted firmware. At least not anything a layman like myself can understand. I will look at cdf's post as recommended. Thank again!
 
marzer said:
Even post #1 seems out of date given the discrepancy I noted in the two PLIST's not being different.
Click to expand...
It is not out of date. There is only one config (the link in Part 1 points to the attached file). As described in the guide, the config already has the protection for UEFI Windows.
 
  • Like
Reactions: marzer
cdf said:
It is not out of date. There is only one config (the link in Part 1 points to the attached file). As described in the guide, the config already has the protection for UEFI Windows.
Click to expand...
I see now. Thanks I didn't get that from reading through the guide. So with that plist configuration my firmware should be fine if I install and operate uefi windows?
 
marzer said:
before I can install Windows without corrupting the firmware.
Click to expand...
What corrupts the firmware are the multiple certificates written to the NVRAM, which "ProtectSecureBoot" is protecting from. Nothing else corrupts the firmware. It is the booting process, during which the certificate are written. Even a USB Windows installer that installs in UEFI mode writes certificates.
 
  • Like
Reactions: Eschers and marzer
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