I think Alex's only meant to inform you nehalem has stutter issue with macOS so you have better information before using nehalem for your mac, of course you're free to do what you want.
Got a tip for us?
Let us know
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
- Thread starter cdf
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
I’m on X5690, thank you. And this is still irrelevant as MacOS was not the point, OC was. But enough with this, 11.3 compatibility is now the real issue, let’s get on with that.
no, that's just spoofing. Even when I dump the rom / nvram I get the correct readings in this situation.
The real value can cause unwanted firmware updates, so I strongly recommend keeping the value as it is now. (Note that if you absolutely want to use the real value, you can also just leave the string empty.)
The guide has been updated to OpenCore version 0.6.9.
For this update, there are only minor updates to the sample configuration file. See Part 3 of the guide.
While updating OC is always recommended, updating to macOS ≥11.3 is currently not recommended on the Mac Pro 5,1, and it is not known at this time whether this will change.
For this update, there are only minor updates to the sample configuration file. See Part 3 of the guide.
While updating OC is always recommended, updating to macOS ≥11.3 is currently not recommended on the Mac Pro 5,1, and it is not known at this time whether this will change.
Not to my knowledge. In fact, nothing has shown any definitive impact towards resolving the problems we now face.
My machine behaves exactly as you described in #300. It is a clean install with 11.3 and OC 0.6.8.
Why did you do a refresh with a reconstructed BootROM? Does that help in any way?
If you like waiting hours for a time machine backup to restore instead of immediately booting into a working drive right away go ahead. I don't have time for that.
I use carbon copy cloner. it automatically copies my ssd to another ssd of the same size every night.
Glad you had a positive outcome like myself, many others don't. Please share your exact hardware and install steps as reply to #300 post, so people know you had the same result. cc @cdf
See #4,574, technically many people have no idea they can end-up with a bricked Mac, out of nowhere. I hired @tsialex to build me a cleaned ROM, which I flash every 3 months.
Last edited:
You can set the value into your OC configuration file, as detailed into first post. I personally use the Plistlib Generator setup.py example:
New here - I built an Open Core hackintosh for my brother last month. That went so smoothly I decided to upgrade my Mac Pro 5,1 (with RX580) from DosDude's Catalina to Open Core & Big Sur. After following page 1's instructions (which didn't warn me about 11.3 not working yet), I got stalled because the macOS 11.3 installer said "This update cannot be installed on this computer" (when selecting my OC-volume), even though I had booted via OC. I don't know if that's related to the compatibility issue so I downloaded 11.2.2, hoping that works, but it gave me the same error. In the page 1 guide, I didn't see a troubleshooting guide about this issue.
[Edit: aha - I need to update my Boot ROM - that's scary..proceeding slowly]
Edit2: I have upgraded my firmware to 144.0.0.0.0 (yay, thanks Mojave installer!), and am still getting the same "This update cannot be installed on this computer" error when trying to install either Big Sur or Catalina after booting from the OC to the createinstallmedia drive.
Edit 3: decided not to install Big Sur yet, due to the PCIe bus issues. Since Catalina needs `Cpuid1Data` & mask set, fixed those and tried again, Success! The latest and greatest May 4th Security update installed without a hitch, so I'm really pleased. Thanks, all.
[Edit: aha - I need to update my Boot ROM - that's scary..proceeding slowly]
Edit2: I have upgraded my firmware to 144.0.0.0.0 (yay, thanks Mojave installer!), and am still getting the same "This update cannot be installed on this computer" error when trying to install either Big Sur or Catalina after booting from the OC to the createinstallmedia drive.
Edit 3: decided not to install Big Sur yet, due to the PCIe bus issues. Since Catalina needs `Cpuid1Data` & mask set, fixed those and tried again, Success! The latest and greatest May 4th Security update installed without a hitch, so I'm really pleased. Thanks, all.
Last edited:
Plistlib Generator 1.1.1 was released with support for OC 0.6.9 (see notable changes), you will need to perform one minor change to your current setup.py file, prior executing the usual upgrade process.
I installed Mojave on a SSD in bay 1. Then I pulled all HDD sleds except for bay 1. Then I downloaded Martin's Package and installed it by the book on the EFI partition of the Mojave drive. Boot picker worked. After that I put the sled for bay 2 with another SSD back in. Then I downloaded Big Sur 11.3 and started the installer from Mojave an installed on the bay 2 SSD.
The install hung once with a progress bar freeze. After a forced shut down it ran through.
Then I moved OC to the Big Sur drives EFI partition. Everything works. The only problems I have are the warm boot issues, the messages that I did not shut down the machine correctly and mysterious recovered files in the trash.
Attachments
Can you please post these details as reply to #300 post hardware related thread? This is an OC related thread.
I remembered this question as I had been looking for a boot solution myself. And since yesterday, after upgrading to the latest OpenCore Legacy Patcher (0.1.2), I've got an OpenCore boot screen om my MacPro5,1 with GT-710. Unexpected, but very welcome.
The fix in RefindPlus that gave bootscreen for Nvidia GPUs was ported to OpenCore v0.6.9.
It is now also available in OpenCore, with or without OCLP, as long as running v0.6.9 and the relevant settings are activated