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

[DigitaLife]

The USB drive originally contained the folder called efi, which made the drive bootable. During the installation, we backed up that folder and replace it with another one that we generated for your Windows drive. This folder contained the Microsoft folder that we needed. After copying the Microsoft folder, we restore the USB drive to its original state in case we want to use it again.



Windows probably activated itself automatically when you connected to the internet. If you've ever had Windows activated on your machine, Microsoft knows it.

I can't find the right words to thank you enough!
Your explanations have been truly exhaustive!
Thank you so much for your competence, kindness and availability!

 

[computerwiz222]

The installinstallmacos.py script location changed on github. Here is the updated command:

curl -O -L https://raw.githubusercontent.com/munki/macadmin-scripts/main/installinstallmacos.py && sudo python installinstallmacos.py

Also, I had to install xattr:

sudo pip install xattr

Hope it helps.

 

[cdf]

The installinstallmacos.py script location changed on github.

Wiki updated. Thanks!

 

[ECJ]

I've upgraded from 0.5.8 to 0.5.9, but I am having a weird issue. I can add all the tweaks and Catalina works great. Once I add the DeviceProperties for my highpoint 7101a PCI card to have the external drives shown as internal drives, the installation fails to boot and I get the circle with the line through it. If I remove the entries, everything runs normally. I have noticed that my PCI path is much longer than the example. Any idea of how I alter the entries?

<key>Add</key>
<dict>

<key>PciRoot(0x0)/Pci(0x7,0x0)/Pci(0x0,0x0)/Pci(0x8,0x0)/Pci(0x0,0x0)</key>
<dict>
<key>built-in</key>
<data>AA==</data>
</dict>

</dict>
<key>PciRoot(0x0)/Pci(0x7,0x0)/Pci(0x0,0x0)/Pci(0x9,0x0)/Pci(0x0,0x0)</key>
<dict>
<key>built-in</key>
<data>AA==</data>
</dict>

</dict>
<key>PciRoot(0x0)/Pci(0x7,0x0)/Pci(0x0,0x0)/Pci(0x10,0x0)/Pci(0x0,0x0)</key>
<dict>
<key>built-in</key>
<data>AA==</data>
</dict>

</dict>
<key>PciRoot(0x0)/Pci(0x7,0x0)/Pci(0x0,0x0)/Pci(0x11,0x0)/Pci(0x0,0x0)</key>
<dict>
<key>built-in</key>
<data>AA==</data>
</dict>

</dict>

 

[cdf]

I have noticed that my PCI path is much longer than the example. Any idea of how I alter the entries?

The paths can be longer. The problem is your config: remove the extra </dict> above the key entries.

 

[joevt]

I've upgraded from 0.5.8 to 0.5.9, but I am having a weird issue. I can add all the tweaks and Catalina works great. Once I add the DeviceProperties for my highpoint 7101a PCI card to have the external drives shown as internal drives, the installation fails to boot and I get the circle with the line through it. If I remove the entries, everything runs normally. I have noticed that my PCI path is much longer than the example. Any idea of how I alter the entries?

Use plutil to verify the format of a plist file (it should show "OK"). You can also use "plutil -p" to show a more easily readable version. Use gfxutil to list the paths of all your devices. https://github.com/acidanthera/gfxutil

 

[ECJ]

The paths can be longer. The problem is your config: remove the extra </dict> above the key entries.

Thanks for the correction. I removed the extra </dict> and now it boots properly into Catalina, but the drives are still displayed as external. Below is the output I'm receiving using gfxutil.
08:00.0 126f:2262 /PCI0@0/IOU1@7/PXS2@0/pci-bridge@8/pci126f,2262@0 = PciRoot(0x0)/Pci(0x7,0x0)/Pci(0x0,0x0)/Pci(0x8,0x0)/Pci(0x0,0x0) 09:00.0 126f:2262 /PCI0@0/IOU1@7/PXS2@0/pci-bridge@9/pci126f,2262@0 = PciRoot(0x0)/Pci(0x7,0x0)/Pci(0x0,0x0)/Pci(0x9,0x0)/Pci(0x0,0x0) 0a:00.0 1987:5012 /PCI0@0/IOU1@7/PXS2@0/pci-bridge@10/pci1987,5012@0 = PciRoot(0x0)/Pci(0x7,0x0)/Pci(0x0,0x0)/Pci(0x10,0x0)/Pci(0x0,0x0) 0b:00.0 1987:5012 /PCI0@0/IOU1@7/PXS2@0/pci-bridge@11/pci1987,5012@0 = PciRoot(0x0)/Pci(0x7,0x0)/Pci(0x0,0x0)/Pci(0x11,0x0)/Pci(0x0,0x0)

Use plutil to verify the format of a plist file (it should show "OK"). You can also use "plutil -p" to show a more easily readable version. Use gfxutil to list the paths of all your devices. https://github.com/acidanthera/gfxutil

Thanks for the tip about "plutil -p". The config.plist is "OK" and I'm using the output from gfxutil.

 

[Tiem]

Well I was finally able to spoof it has a MacPro7,1 on Dual CPU Tray. There is only one thing that you do not see here if you paid attention to...

You mean the lack of a memory tab? Try: https://github.com/IOIIIO/MacProMemoryNotificationDisabler
[automerge]1593415579[/automerge]

The EFI volume of the Windows drive is empty. That's OK. In that volume, create a folder called EFI. Now look at the contents of your USB drive. You should see a folder called EFI and a folder called efi.bak. If you open the folder called EFI, you should see a folder called Microsoft. Copy that folder into the EFI folder you just created. Finally delete the EFI folder in the USB drive and rename efi.bak to efi. Don't forget to remove the USB drive before proceeding. When you reboot you should see Windows (not external) in the boot picker.

You really shouldn't be doing this way. Use the command

bcdboot

from the Windows installer command prompt. Creating a new EFI (or repairing an existing one) is the following:

bcdboot C:\windows /s S:

Copying folders does not work well in Windows as it usually does more than just shift files. Good way to just up and corrupt your install.

 

[205Maxi]

You mean the lack of a memory tab? Try: https://github.com/IOIIIO/MacProMemoryNotificationDisabler
[automerge]1593415579[/automerge]

Well true! It was not showing first, but I got it to work now, might have been some bug because of macOS Big Sur. But a 16" model has no memory tab ( see attached ). But I think that during the presentation of macOS if I recall well when Craig. F showed the MacMini with ARM12Z I did not see the Memory tab (Not sure about). Also it will look weird without the info of a graphics as well.

Now I was always interested to get the memory tab showing properly with the MP7,1 Spoof and I never really found anything about to get it showing properly I am pretty sure there is a way but did not find it.

Does this MacProMemoryNotificationDisable will disable the popup in the right upper corner that you get each time you restart the machine? Or is it a fix for the tab showing the memory correctly? (Attention more than maximum supported etc etc etc)

Thank you for the link I will take a look at...

***** Though, there isn't any explanations on how and where to put it. **** Would appreciate if there was explanations. Thanks again.

You really shouldn't be doing this way. Use the command

bcdboot

from the Windows installer command prompt. Creating a new EFI (or repairing an existing one) is the following:

bcdboot C:\windows /s S:

Copying folders does not work well in Windows as it usually does more than just shift files. Good way to just up and corrupt your install.

 

[startergo]

Thanks for the correction. I removed the extra </dict> and now it boots properly into Catalina, but the drives are still displayed as external. Below is the output I'm receiving using gfxutil.
08:00.0 126f:2262 /PCI0@0/IOU1@7/PXS2@0/pci-bridge@8/pci126f,2262@0 = PciRoot(0x0)/Pci(0x7,0x0)/Pci(0x0,0x0)/Pci(0x8,0x0)/Pci(0x0,0x0) 09:00.0 126f:2262 /PCI0@0/IOU1@7/PXS2@0/pci-bridge@9/pci126f,2262@0 = PciRoot(0x0)/Pci(0x7,0x0)/Pci(0x0,0x0)/Pci(0x9,0x0)/Pci(0x0,0x0) 0a:00.0 1987:5012 /PCI0@0/IOU1@7/PXS2@0/pci-bridge@10/pci1987,5012@0 = PciRoot(0x0)/Pci(0x7,0x0)/Pci(0x0,0x0)/Pci(0x10,0x0)/Pci(0x0,0x0) 0b:00.0 1987:5012 /PCI0@0/IOU1@7/PXS2@0/pci-bridge@11/pci1987,5012@0 = PciRoot(0x0)/Pci(0x7,0x0)/Pci(0x0,0x0)/Pci(0x11,0x0)/Pci(0x0,0x0)


Thanks for the tip about "plutil -p". The config.plist is "OK" and I'm using the output from gfxutil.

Did you add them to the delete key as well? If there is any existing property you override you should add it to the delete key.

 

[cdf]

Did you add them to the delete key as well? If there is any existing property you override you should add it to the delete key.

True in general, but if the "built-in" property was already there, then the disks would already be internal, and there would be no need for this in the first place.

 

[startergo]

By the way DarwinDumper has a new version as of 2020/06/11 (the last one was from 2017). There is a section for prelinked kexts and details for troubleshooting BigSur.

 

[205Maxi]

Tried with the complied MacProMemoryNotificationDisabler and still the notification comes on.. ( It says that's only working with the latest Lilu.kext ) and I did put the 1.4.5 one..

Here maybe I have done something wrong. If someone can chime in ... I would really appreciate. Thanks to all.

<dict>
<key>BundlePath</key>
<string>MacProMemoryNotificationDisabler.kext</string>
<key>Comment</key>
<string>MacProMemoryNotificationDisabler</string>
<key>Enabled</key>
<true/>
<key>ExecutablePath</key>
<string>Contents/MacOS/MacProMemoryNotificationDisabler</string>
<key>MaxKernel</key>
<string></string>
<key>MinKernel</key>
<string></string>
<key>PlistPath</key>
<string>Contents/Info.plist</string>
</dict>



Well answering to myself, corrected, I leave it here is someone wants to use it...


<dict>
<key>Comment</key>
<string></string>
<key>MaxKernel</key>
<string></string>
<key>PlistPath</key>
<string>Contents/Info.plist</string>
<key>Enabled</key>
<true/>
<key>MinKernel</key>
<string></string>
<key>ExecutablePath</key>
<string>Contents/MacOS/MacProMemoryNotificationDisabler</string>
<key>BundlePath</key>
<string>MacProMemoryNotificationDisabler.kext</string>
</dict>

 

[startergo]

Tried with the complied MacProMemoryNotificationDisabler and still the notification comes on.. ( It says that's only working with the latest Lilu.kext ) and I did put the 1.4.5 one..

Here maybe I have done something wrong. If someone can chime in ... I would really appreciate. Thanks to all.

<dict>
<key>BundlePath</key>
<string>MacProMemoryNotificationDisabler.kext</string>
<key>Comment</key>
<string>MacProMemoryNotificationDisabler</string>
<key>Enabled</key>
<true/>
<key>ExecutablePath</key>
<string>Contents/MacOS/MacProMemoryNotificationDisabler</string>
<key>MaxKernel</key>
<string></string>
<key>MinKernel</key>
<string></string>
<key>PlistPath</key>
<string>Contents/Info.plist</string>
</dict>

Latest LILU with BigSur support is 1.4.6. You need to compile it from the master branch or use corpnewt's compiler

 

[205Maxi]

Latest LILU with BigSur support is 1.4.6. You need to compile it from the master branch or use corpnewt's compiler

I shouted to fast after putting the kext and correcting the config.plist.. the Notification is still there, now I am confused, is the first bundle path correct? or The second one?

 

[h9826790]

I shouted to fast after putting the kext and correcting the config.plist.. the Notification is still there, now I am confused, is the first bundle path correct? or The second one?

At this stage, you better put the kext in Library/Extensions. This is way easier to see if the kext is loaded, and if the system react to the kext properly (if that's loaded).

Once everything work, then you can move the kext to OC. It's really at the very very early stage about "using OC / Lilu / other kexts in Big Sur". You better start with something that's "easy to observe / verify"

 

[TC!!]

Wanted to ask what's my best option to upgrade? I'm on a 2010 Mac Pro 5,1 with processor card upgraded to give me 3.46GHz 6-Core Intel Xeon, with an RX 580 and NVMe boot drive.
Not being able to upgrade Xcode is now starting to cause me problems for an iPhone App I develop.

This Mac is my main work computer so I can't **** it up. I would like to upgrade to BCM94360 at some point to at least get a couple more years out of this machine until Apple's Mac Pros use their new processors.

 

[h9826790]

Wanted to ask what's my best option to upgrade? I'm on a 2010 Mac Pro 5,1 with processor card upgraded to give me 3.46GHz 6-Core Intel Xeon, with an RX 580 and NVMe boot drive.
Not being able to upgrade Xcode is now starting to cause me problems for an iPhone App I develop.

This Mac is my main work computer so I can't **** it up. I would like to upgrade to BCM94360 at some point to at least get a couple more years out of this machine until Apple's Mac Pros use their new processors.

You mean upgrade to Big Sur?

 

[tsialex]

You mean upgrade to Big Sur?

Xcode since 11.4 requires Catalina and 11.3.1 was the last version of Xcode that runs with Mojave.

Xcode will take around a little less than a year to require Big Sur.

 

[TC!!]

You mean upgrade to Big Sur?

Sorry, I missed that part, I'm currently on Mojave. I was thinking that if I'm going to have to jump through hoops to get up to Catalina I may as well go right up to Big Sur, unless it's much more difficult.

 

[tsialex]

Sorry, I missed that part, I'm currently on Mojave. I was thinking that if I'm going to have to jump through hoops to get up to Catalina I may as well go right up to Big Sur, unless it's much more difficult.

Big Sur is on beta1, a lot of things will change between now and the GM around late September/October, besides that, you can't submit apps with Xcode betas.

Install Catalina and have Xcode working.

 

[TC!!]

Big Sur is on beta1, a lot of things will change between now and the GM around late September/October, besides that, you can't submit apps with Xcode betas.

Install Catalina and have Xcode working.

Thanks for the reply. With my setup running a 'supported' RX580 what's the safest solution opencore, dosdude? I have a macbook pro running Catalina if that can help.

 

[tsialex]

Thanks for the reply. With my setup running a 'supported' RX580 what's the safest solution opencore, dosdude? I have a macbook pro running Catalina if that can help.

Depends if you have a fully compatible config or not, see the first post. If you have, you can make a completely vanilla install of Catalina with OpenCore.

I don't recommend patched installs at all, but people that don't want to learn how to use OpenCore go for it.

 

[205Maxi]

At this stage, you better put the kext in Library/Extensions. This is way easier to see if the kext is loaded, and if the system react to the kext properly (if that's loaded).
View attachment 929057

Once everything work, then you can move the kext to OC. It's really at the very very early stage about "using OC / Lilu / other kexts in Big Sur". You better start with something that's "easy to observe / verify"

I was able to load ( see attached ) that ver1.0 of MacProMemoryNotificationDisabler still does not work despite the fact it is loaded. I will try ver1.1 and report.

Hopefully the 1.1 will make the difference but really not sure about it.

Radeon does not load but when I go to Graphics Tab, VBIOS Says RadeonBoost ( That might be because OC is loading it since I put it in the Kext folder and enabled it ).

Again not really sure about it but easily checkable.

 

[jvlfilms]

I used Martin Lo's package and everything is running smoothly!! I use rEFInd on a USB to navigate to my Win 10 legacy install and that seems to be the best way of doing it for now. Thanks for the help everyone!