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

[sfalatko]

Indeed, legacy booting with OC requires the addition of a driver, but I've left this out of the guide for now. The reason is that the same functionality should already be available natively with EnableGop. I may add some details later once more testing gets done.

Got it. As I noted in my testing I get two Legacy Windows entries in the OC boot menu so it is confusing. Also, as I boot OC from a USB stick with EnableGop and can boot Legacy Windows from the Apple Boot Menu I most likely won't use the capability.

 

[Gustav Holdoff]

I decided to include both bootkicker and openlegacyboot for testing, and I also have an enableGop.
there are probably so many duplicate drivers conflicting
I had a syspolicyd process at 40-90%, I waited about half an hour it did not stop, I couldn’t wait - I killed it
After that, I rebooted several more times and checked - mds and mds_stores processes worked for a very long time, and 90% of the syspolicyd appeared again. I realized that these additional functions only harm me - I erased all traces of bootkicker and openlegacy in EFI and config
without them my system works fine - syspolicyd does not appear
EDITED
I worked all day yesterday normally - no unnecessary processes were observed
This morning I turned on the computer - syspolicyd daemon appeared at 45-90% and it additionally caused an endless jumping process MDS at 50-400%
theoretically 40% with unloaded CPU's is nothing, but CPU A heats up about 10 degrees more than when there are no 40% of these constant processes
It was not possible to kill syspolicyd - it appeared again
Reset nvram and smc did not help
then I just returned opencore 0.9.4 - the daemon was gone
I’ll probably hold off on version 0.9.5 for now - I’ll wait for fixes in version 0.9.6

 

[sfalatko]

Updated OC to 0.9.5 and then updated Monterey to 12.6.9. Both went fine.

 

[hwojtek]

On my heavily upgraded 5,1 with an almost vanilla (as per post #1) config modded only for GPU and NVMe, 12.6.9 was only successful in VMM mode. Obviously, your mileage may vary.

Feels snappier, tho.

 

[ZNDK]

I updated from OC 0.9.4 to 0.9.5 and the volume name in BootPicker is in arabic typeface and when I proceed from there, it won't go to the next step and won't boot.
I verified with ocvalidate and the config.plist is correct. is there anything I need to change from 0.9.4 to 0.9.5?

 

[sfalatko]

I updated from OC 0.9.4 to 0.9.5 and the volume name in BootPicker is in arabic typeface and when I proceed from there, it won't go to the next step and won't boot.
I verified with ocvalidate and the config.plist is correct. is there anything I need to change from 0.9.4 to 0.9.5?

Did you follow the instructions in Post #1 under the "Updating OpenCore" section in Maintenance?

 

[ZNDK]

I have added the ShimRetainProtocol in the correct location and the BootKicker.efi entry as well.
I have attached two images. The first image is when the Mac is booted normally and the second is when it is booted via GOP.

 

[Gustav Holdoff]

I have added the ShimRetainProtocol in the correct location and the BootKicker.efi entry as well.
I have attached two images. The first image is when the Mac is booted normally and the second is when it is booted via GOP.

maybe you forgot to copy all the necessary files to the resources folder?
Each new version of opencore comes with empty folders and you need to remember to insert the files manually
check post#1
please note: in the font folder there should be not 4 files (as written by cdf) but 6

➍ Verify that your ESP contains the following files and folders:

ESP ("EFI" in Finder)
└── EFI
⠀⠀ ⠀├── BOOT
⠀⠀ ⠀│⠀ ⠀└── BOOTx64.efi
⠀⠀ ⠀└── OC
⠀⠀⠀⠀ ⠀ ⠀├── ACPI
⠀⠀⠀⠀ ⠀ ⠀├── config.plist
⠀⠀⠀⠀ ⠀ ⠀├── Drivers
⠀⠀⠀⠀ ⠀ ⠀│⠀ ⠀├── OpenCanopy.efi
⠀⠀⠀⠀ ⠀ ⠀│⠀ ⠀└── OpenRuntime.efi
⠀⠀⠀⠀ ⠀ ⠀├── Kexts
⠀⠀⠀⠀ ⠀ ⠀├── OpenCore.efi
⠀⠀⠀⠀ ⠀ ⠀├── Resources
⠀⠀⠀⠀ ⠀ ⠀│⠀ ⠀├── Audio
⠀⠀⠀⠀ ⠀ ⠀│⠀ ⠀├── Font (4 files)
⠀⠀⠀⠀ ⠀ ⠀│⠀ ⠀├── Image
⠀⠀⠀⠀ ⠀ ⠀│⠀ ⠀│⠀ ⠀└── Acidanthera
⠀⠀⠀⠀ ⠀ ⠀│⠀ ⠀│⠀⠀⠀ ⠀ ⠀└── GoldenGate (22 files)
⠀⠀⠀⠀ ⠀ ⠀│⠀ ⠀└── Label (22 files)
⠀⠀⠀⠀ ⠀ ⠀└── Tools

To keep things nice and tidy, the following files and folders can be deleted:

• all files in the folders "Audio" and "Tools"
• all files in the folder "Drivers", except for the files "OpenCanopy.efi" and "OpenRuntime.efi"
• all folders in the folder "Acidanthera", except for the folder "GoldenGate"

🎉 Congratulations! You now have a basic OpenCore setup and are ready for the first boot.

 

[ZNDK]

Thank you. I was able to solve the problem. I reconfigured OC from the beginning and was able to start with 0.9.5.

 

[eVasilis]

Hi all

For sometime now I've been experiencing problems with my wired Logitech mouse whic stops responding (it is not the mouse at fault). I have it plugged in a usb 3 hub which connects onto a usb 3 pcie card. When it freezes, I have to unplug and re-plug the hub's power cord. I tried plugging the hub into one of my macpro's usb 2 ports but the problem remains. I am running Monterey 12.6.7 via opencore (0.9.3.0) on a 5,1 macpro. Any tips?

Thanks

 

[h9826790]

Hi all

For sometime now I've been experiencing problems with my wired Logitech mouse whic stops responding (it is not the mouse at fault). I have it plugged in a usb 3 hub which connects onto a usb 3 pcie card. When it freezes, I have to unplug and re-plug the hub's power cord. I tried plugging the hub into one of my macpro's usb 2 ports but the problem remains. I am running Monterey 12.6.7 via opencore (0.9.3.0) on a 5,1 macpro. Any tips?

Thanks

If you must re-plug the hub's power cord, but not the hub's USB cable. Then I suspect it's the hub's issue. The controller inside the hub may occasionally freeze, therefore, you can clear it by "rebooting" the hub.

 

[eVasilis]

If you must re-plug the hub's power cord, but not the hub's USB cable. Then I suspect it's the hub's issue. The controller inside the hub may occasionally freeze, therefore, you can clear it by "rebooting" the hub.

Thanks for your reply. It is happening way too often and with different hubs. It i either Monterey or my 5,1 is ready to move onto green pastures. As I am writing this it froze twice...

 

[bookemdano]

...it is not the mouse at fault...

How do you know this? Have you tried another wired mouse on your Mac Pro and experienced the same freezes? What about other USB peripherals plugged into your Mac Pro (keyboard, webcam, whatever)--are they performing consistently or do they freeze up as well?

To eliminate variables, you should plug your mouse directly into one of the built-in USB 2.0 ports on your Mac Pro. Eliminate any and all hubs for now.

 

[Madr]

Yes, not all outputs work in all situations. If I remember correctly, the DisplayPort output is the most reliable.

I bought an Mini DP adapter to hdmi but it didn't work. I tried it with Mojave and there it worked fine. So i don't think Monterey only works on DP but not 100% sure yet.

Yes, it has two PCIe power outputs 75W each on the mainboard. But the adapter I linked allows you to power a PCIe card separately from empty SATA power ports. So you can hook up both motherboard ports to the 7950 and power your 5770 from SATA.
If you want to go for a reflash (the Hackintosh may come in handy), I believe all the files needed, including a readme, are in the ZIP attached below. I believe your card has dual EPROM, so make sure you don't play with the switch while installing and flash Mac-friendly firmware with the switch in one position, so you can recover from a borked reflash with the the switch in position 2. It may be, that the card has a standard (BIOS) firmware in position 1 and PC EFI firmware in position 2. Some cards have regular firmware in position 1 and overclocked firmware in position 2. You may find it helpful if you gave us the exact details of the card.

Bought this also. Sorry for the late reply but i didn't have time to test. Anyway this adapter works if you cut off the part on the right side. Otherwise it won't fit. It's a bit loose but for only getting the 7950 to work shouldn't be a problem.

Anyway Monterey booted up with both cards inside and connected to the 5770 for screen. Thing is: when i look at the 7950 in profiler it says 8950 instead of 7950 and no kext loaded.

But it wouldn't boot Montherey with only the 7950 installed. Even if i wait 5 minutes and in that time Mojave showed screen and was on a normal HD not a SSD like Montherey install

It's been a time i did this install but i think i used the 5770 mostly for the Monterey install although not 100% sure. And that is the reason why it didn't load the 7950 standard drivers.

Or there is a way to get the 7950 to work now because i have visual what is going on. Anyway i forgot if this option is viable. It's most easy one because i don't have to go through setup again.

Any tips?

I'll go through all the topics i have written about this online ( those are mostly for me to look back later if i have to do it again) But maybe i haven't documented the Monterey steps.

Thank you!

 

[MikeymikeT5]

Good evening from Japan...

The last major update I carried out to my 5,1, was stepping up to Mojave, which has worked flawlessly thanks to Martin, Tsialex, and one or two others on here. My machine is upgraded to dual 6 core 3.46 processors, NVME 2TB boot, and Crucial 2TB. I then have a HDD for movie storage. I'm also running 96GB of ram, and Radeon VII 16Gb graphics. I've been using the machine mainly for FCP, though also downloaded Davinci Resolve last week for doing simple video work using clips from a Canon C200 shot in RAW. Both of the movie software packages need updated OS system software in order to run the later versions of the movie software. Is the general consensus on here to update directly to Monterey, or is one of the previous versions a better bet for any reason? I ask, as the update process seems somewhat daunting, and the latest Davinci Resolve is supposedly ok with Big Sur 😅

 

[mertisrules]

Good evening from Japan...

The last major update I carried out to my 5,1, was stepping up to Mojave, which has worked flawlessly thanks to Martin, Tsialex, and one or two others on here. My machine is upgraded to dual 6 core 3.46 processors, NVME 2TB boot, and Crucial 2TB. I then have a HDD for movie storage. I'm also running 96GB of ram, and Radeon VII 16Gb graphics. I've been using the machine mainly for FCP, though also downloaded Davinci Resolve last week for doing simple video work using clips from a Canon C200 shot in RAW. Both of the movie software packages need updated OS system software in order to run the later versions of the movie software. Is the general consensus on here to update directly to Monterey, or is one of the previous versions a better bet for any reason? I ask, as the update process seems somewhat daunting, and the latest Davinci Resolve is supposedly ok with Big Sur 😅

yeah, good job! very similar to mine. Although I don't use it everyday BM hardware and Resolve work well for me in both Big Sur and latest Monterey. so maybe it's just preference...

 

[flaubert]

Good evening from Japan...

The last major update I carried out to my 5,1, was stepping up to Mojave, which has worked flawlessly thanks to Martin, Tsialex, and one or two others on here. My machine is upgraded to dual 6 core 3.46 processors, NVME 2TB boot, and Crucial 2TB. I then have a HDD for movie storage. I'm also running 96GB of ram, and Radeon VII 16Gb graphics. I've been using the machine mainly for FCP, though also downloaded Davinci Resolve last week for doing simple video work using clips from a Canon C200 shot in RAW. Both of the movie software packages need updated OS system software in order to run the later versions of the movie software. Is the general consensus on here to update directly to Monterey, or is one of the previous versions a better bet for any reason? I ask, as the update process seems somewhat daunting, and the latest Davinci Resolve is supposedly ok with Big Sur 😅

You might as well just get out in front of the problem, and set it up with Monterey, in my opinion.

 

[MikeymikeT5]

Thank you for the opinions on this, I'm reading and re-reading everything, to brace myself for the ordeal ahead... 😅

As an aside, my Bluetooth/Wireless card is the following, does anyone know if its compatible?...

Card Type: AirPort Extreme (0x14E4, 0x16D)
Firmware Version: Broadcom BCM43xx 1.0 (7.77.61.3 AirPortDriverBrcmNIC-1305.12)

 

[hwojtek]

https://forums.macrumors.com/threads/seeking-opencore-for-5-1-guidance-please.2353891/?post=31709584#post-31709584

 

[Bmju]

https://forums.macrumors.com/threads/seeking-opencore-for-5-1-guidance-please.2353891/?post=31709584#post-31709584

Of course emulated NVRAM (OpenVariableRuntimeDxe.efi) is available, which can pretty much knock problems like this on the head. But it doesn't seem to have caught on! 😭

 

[hwojtek]

Does NVRAM emulated with this kext isolate the OS from hardware NVRAM completely?

 

[Bmju]

In-OS, yes.

EDIT: To add a little more detail, it won't block DirectHW.kext for example - but that really is direct writing to the NVRAM (or even to the BIOS itself, if the machine is in the right state with long press on power button). That's not relevant to normal drivers writing normally (i.e. using UEFI runtime services), to normal NVRAM variables - OpenVariableRuntimeDxe isolates all of those normal updates, to a RAM-based alternative store.

 

[Ivan Shpak]

I think you'll be better with a Virtual Machine. Snow Leopard is pretty light and fast to run in VM. Officially you'l need a SL server, but there's a trick to spoof SnowLeopard Client installer in Server version

I work with hardware and software via SCSI and Fire Wire. Proprietary software that only works in 32-bit mode, I was tired of booting through ALT and I thought maybe in the config I could set the inclusion of 32-bit mode only for Snow Leopard

 

[startergo]

I work with hardware and software via SCSI and Fire Wire. Proprietary software that only works in 32-bit mode, I was tired of booting through ALT and I thought maybe in the config I could set the inclusion of 32-bit mode only for Snow Leopard

32 bit libraries are still in Mojave. Plus you have AMD hardware acceleration. There is an NVRAM variable to enable 32 bit support.

To re-enable 32-bit processing from the kernel, just disable Apple's disabling function by adding no32exec=0 to your boot-args (sudo nvram boot-args="no32exec=0 $(nvram boot-args 2>/dev/null | cut -f 2-)" if SIP is disabled, if not run the same command from Recovery mode without sudo).

 

[Ivan Shpak]

32 bit libraries are still in Mojave. Plus you have AMD hardware acceleration. There is an NVRAM variable to enable 32 bit support.

I wrote about Snow Leopard because to work in my hardware (Creo/Kodak iQsmart3) software (Kodak oXYgen) environment I need the Rosetta module (PowerPC)