Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
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.
Please excuse my ignorance, but can I use Preferences > Startup Disk to reboot my cMP into Windows 10? Will it cause any irreversible damage to OC or the BootROM?
You can, but it will make Windows the default startup. If you have Bootcamp on the Windows side you can use that to boot back to macOS. Otherwise, you'll have to press"ESC" at boot to choose macOS again.
 
So I have updated to macOS 11.3 (20E5186d). But when I tried to update through OC id did not work. It crashed at the NVME drivers. So I continued installation from the Apple boot picker selecting BS directly. Then it went through.
 
you have to set the layout-id and create a dev entry for your audio device. reading the alcid from the boot-args and setting the alc-layout-id is broken
Did that. No joy. This is ALC889A, device path 0x1b, layout-id 0c000000/12/DAAAAA==
Tried both 1.5.8 and 1.5.9 versions of AppleALC kext.
 
Did that. No joy. This is ALC889A, device path 0x1b, layout-id 0c000000/12/DAAAAA==
Tried both 1.5.8 and 1.5.9 versions of AppleALC kext.
Yes, it is still broken. For me and my iMac12,2 and 11,3 it is showing at least the hardware and the microphone jack is working with my older iPhone 3.5mm chinch in (microphone) and out (headset). Internal speakers remain unusable. It is under development....
 
  • Like
Reactions: Jonathan50
So I have updated to macOS 11.3 (20E5186d). But when I tried to update through OC id did not work. It crashed at the NVME drivers. So I continued installation from the Apple boot picker selecting BS directly. Then it went through.
Wait, do Big Sur beta updates boot directly from Apple boot picker?
 
As long as -no_compat_check is set it just operates as a supported OS on cMP5,1 ( Minus the update initiation).
OK, as I understand it the -no_compat_check is recommended to be disabled as per post #1 though?

Clean up the NVRAM​

Find NVRAM and delete
XML:
<key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
<dict>
<key>boot-args</key>
<string>-no_compat_check</string>
</dict>
 
[EDIT: solved] I solved the problem by:
1. setting the VMM flags in config.plist and rebooting
2. redownloading the update

So - at least for me on a genuine 5.1 with two X5690, if it makes any difference - the hybridization alone, WITHOUT VMM flags set to ON does not allow for seamless updating.
There must be something incorrectly configured as I was able to update to 11.2.3 seamlessly and without issue using just hybridization. I too have a genuine cMP5,1 with two X5690s. I detailed my experience here.
 
  • Like
Reactions: hwojtek
OK, as I understand it the -no_compat_check is recommended to be disabled
@cdf I believe we can safely remove the 7C436110-AB2A-4BBB-A880-FE41995C9F82 Apple GUID, from OC NVRAM. @hwojtek the boot-args values are passed to NVRAM, when you boot your Mac.
 
Last edited:
  • Like
Reactions: hwojtek
Info reported. Thanks! (Actually, the recent fix for the X5690 should work with this as well.)
It is fixed now:
Code:
00:097 00:014 OCCPU: Timer address is 408 from LPC
00:212 00:115 OCCPU: Intel TSC:  3458000129Hz,  3458MHz; FSB:   133000004Hz,   133MHz; MaxBusRatio: 26
02:578 00:019 OC: OcLoadPlatformSupport...
02:596 00:018 OCSMB: SmbiosLookupHost failed to lookup SMBIOSv3 - Not Found
02:611 00:014 OCSMB: Found DMI Anchor 773E2000 v2.4 Table Address 773DF000 Length 2452
02:628 00:017 OCSMB: Current SMBIOS MacPro5,1 (Mac-F221BEC8 made by Apple Inc.)
02:650 00:021 OC: PlatformInfo auto 0 OEM SN 0 OEM UUID 0 OEM MLB 0 OEM ROM 0 - Success
02:665 00:014 OCSMB: Post-override BIOS vendor Apple Inc. 1
02:681 00:015 OCSMB: CPU display frequency is 3460MHz
 
Last edited:
The easiest way is to use Hackintool to install the kext. Remember BS system is sealed it will only load the kext after a reboot.

System extensions should be and with Hackintool will be added to "library\extensions". Use Hackintool as suggested. If you need help using get back at me. Keep SIP disabled.

Thanks both, I have no idea about Hackintool but downloading and looking into it now. Appreciate any tips you can give on getting it working with Big Sur!

I don't mind a reboot every morning as I tend to turn the machine on in the morning and then off at the end of the day, so it's not a big deal if it buys me an extra 12-18 months with the machine!

There's no guarantee the PCIe sound card drivers/kext will even work in Big Sur, so it's a long shot anyway. If it doesn't, I'll wipe the drive and install Catalina and see if that works.

I also want to be able to get Logic X and FCPX updates in the future, but they are Catalina upwards.
 
OK, I have Hackintool and by default it wants to put the kext in the following location:

1) Macintosh SSD / Library / Extensions

However in Mojave the Kext is actually in:

2) Mac SSD / System / Library / Extensions

Is it okay to change the path to 2), or do you leave it at path 1) and then have to restart on each fresh boot of the machine?

Apologies if my understanding is a bit off!
 
Normally third party extensions go in /L/E it will only ask you to reboot once after the installation.
 
That wasn't the case with my audio interface (which previously required SIP to be disabled for many generations of OSX).

I'll try with Library / Extensions and if that doesn't work, investigate further!
 
That wasn't the case with my audio interface (which previously required SIP to be disabled for many generations of OSX).

I'll try with Library / Extensions and if that doesn't work, investigate further!
Sip has to be disabled if the extension is unsigned.
 
  • Like
Reactions: Sharky II
Hi - so far so good (with the kext in Library / Extensions).

The machine restarted and then cut off mid way through another restart - and then turned back on again - quite possessed.

Then, it worked!

I have lost the preference pane (it's there in System Prefs but doesn't seem to detect the PCIe card) but can adjust the settings in Audio/MIDI controls.

I haven't tried another reboot or cold start yet!
 
So I have updated to macOS 11.3 (20E5186d). But when I tried to update through OC id did not work. It crashed at the NVME drivers. So I continued installation from the Apple boot picker selecting BS directly. Then it went through.
Have you tried the latest build(20E5196f)?
 
Have you tried the latest build(20E5196f)?
I tried installing it, but it did not go. It crashed at NVME controllers (My BS is on an NVME drive). Never had that issue before. I could only continue by selecting the BS option in the bootpicker not the newly created Macintosh HD. It "appeared" it was upgrading BS, but after booting I realized it did not go through.
1615405891809.png
 
Last edited:
  • Like
Reactions: TECK and VitaminK
looking for some answers and help please. Today I decided to remove my open core SSD from my system and prep it for sale. I simply removed the SSD containing open core, my Vega VII, and all my other drives. Installed my efi flashed 280x and did a few NVRAM resets.

threw in a small Apple Blade in an Apple PCIe adapter and installed Mojave via USB.

Once done, I ran updates then proceeded to take some screen shots and I noticed now my ram is no longer showing 1333 but now showing 1066Mhz I decided to blast away a few more NVRAM resets and reboot, but then it lost the Disk and wouldn't boot so I fired up my usb installed and used the select startup disk from there and was able to get it booted back up. but ram still showing 1066Mhz

is it possibly a corrupt BootRom is causing this? if so what is the best way to check? Im not sure how to use RomTool but I downloaded it and when I attempt to extract the zip it is asking me to type in a password for info.plist.

If anyone else has anything else they want me to check please let me know, I just want to make sure this machine is functioning well before I sell it.
 
@wickerstick I don't see any relation to OpenCore in your post. You could get better visibility by posting a new thread and troubleshoot your issues there?
 
OpenCore on Legacy Apple Hardware

This guide explains how to use the excellent OpenCore bootloader on a Mac Pro 5,1 to install, run and update macOS Catalina and macOS Big Sur, resulting in a clean, unpatched operating system no different than on a supported Mac.

Why OpenCore?

There are several advantages to using OpenCore on a classic Mac Pro:

Boot picker screen (even with a standard graphics card)
View attachment 1723702
Software Update (just like on a supported Mac)
View attachment 1723703
Hardware acceleration (and DRM for Netflix on Safari)View attachment 1723704
Another approach to installing and running macOS on unsupported Macs consist of applying a series of rigid patches. Although effective, this strategy may be considered undesirable, because it alters system files—a potential problem for updates. With OpenCore, macOS remains entirely untouched. Necessary modifications take place cleanly in memory.

Why this Guide?

The purpose of this guide is to provide step-by-step hands-on instructions to using OpenCore on the Mac Pro 5,1. Included with the instructions is a basic sample configuration to get you started. Guidelines for creating a more advanced configuration customized to your machine are also detailed.

👍 The included sample configuration is about as minimal of a configuration as possible for using OpenCore on a Mac.​

Additional Resources

Since this guide appeared, other solutions to OpenCore on Apple hardware have been proposed. Here on MacRumors, you have a few options:
  1. This guide (step-by-step hands-on instructions)
  2. Martin's Package (very popular easy-to-install one-package-fits-all solution provided by @h9826790 with emphasis on hardware acceleration)
  3. MyBootMgr (great multi-boot solution provided by @Dayo with a rich suite of helper apps for setting up and maintaining RefindPlus and OpenCore)
  4. OC Plistlib Generator (diligent programmatic solution provided by @TECK for automating OpenCore updates)
Requirements

This guide is aimed at systems with the following specifications:

Mac Pro modelEarly 2009 with MacPro5,1 firmware,* Mid 2010 or Mid 2012
Processor architectureWestmere (E56xx, L56xx, X56xx) / Gulftown (W36xx)
Boot ROM version144.0.0.0.0
GraphicsEFI (flashed) or a standard UEFI card (PC GPU) supported in Catalina or Big Sur
WirelessChipset supported in Catalina or Big Sur (BCM943224, BCM9435x, BCM9436x)

Need to upgrade your boot ROM? See the upgrade instructions.

Regarding Graphics: Several GPUs supported in macOS High Sierra are not supported in macOS Mojave or later. This includes all non-Kepler generation NVIDIA GPUs as well as AMD GPUs earlier than HD 7950. Several HD 78xx GPUs (Pitcairn) were rebadged as R9 2xx and are not supported in macOS Mojave or later. All classic Mac Pro factory GPUs had support removed with Mojave.

Acknowledgements

A big thank you to @vit9696 and the other talented developers of Acidanthera for making all of this possible. Special gratitude goes to @h9826790 for spearheading the hardware acceleration study and @startergo for the relentless testing that led to boot screen support. And thanks to all those that have contributed to this thread!


PART I
Basic Installation




PART II
Advanced Configuration





PART III
Maintenance





PART IV
Installing and Updating macOS




APPENDIX
Installing Windows and Linux
Hello good nigth

I want start with this tutorial, and like to create a video to how do this step by step too.
To start i want to understand what this part means:
see
Captura de pantalla 2021-03-10 a las 23.32.18.png


before do all this step, i want understand all that i will do.
My mac pro 5.1 hasta catalina installed, but not opencore, and i want to do a clean install , erase all and follow this steps.

Can somebody help me?

Regards

Julio
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.