Thanks. I tried a different usb, again as exfat and it doesn’t show up on boot screen. It is lit up while it start so it is clear the computer sees it is there.
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
Hello eveyrone, I am trying to understand is the opencore supported with my Early 2009 Mac Pro (2x 2,93 Nehalem cpus)? Thank you for all your support on this! If not, the only way to upgrade to Catalina is to upgrade to the Westemere cpu's? I'm not sure if, as of now, it is profitable for me to invest more on my Mac pro or decide that this machine is coming to an end. Upgrading to 2x cpu's, new ram and nvme will cost me 500$, is this the right solution or the time to buy a new system has come?
Nehalem CPUs never supported Apple Hypervisor, so you won't have VMM support/native updates.
You can workaround this limitation and use a Nehalem Xeon, it's basically the same recipe as a MP3,1 + OpenCore, but you will be plagued by the stuttering audio problem of the Nehalem dual CPUs, since you have a dual CPU Mac Pro. This is a maddening problem.
Most people here are trying to extend the MP5,1 useful life until the new Apple Silicon Mac Pros are released.
If you think that with some careful spending right now to keep your Mac Pro working fully supported for 2 or 3 years more and wait the transition time from Intel to Apple Silicon is valid to you, go for it.
For me, sure is.
Will give that look sometime tomorrow, work isn't giving me much playtime at the moment.
Thankyou for the pointer.
opencore 0.6.3 will work on your Mac Pro and allow you to do Catalina and Big Sur with native updates
here's the link
Activate AMD hardware acceleration
I created a new "easy to install package" as per many requested (based on the official OpenCore). [The attached package updated to 0.7.9] For those who only need HWAccel, post #594 has everything you need. This new package mainly offer HWAccel + boot screen. Also, this package should work in...
forums.macrumors.com
Attachments
No, it won't unless you spoof iMac Pro full time. Btw, @izapp Mac Pro is a dual CPU and will have the stuttering audio problem.opencore 0.6.3 will work on your Mac Pro and allow you to do Catalina and Big Sur with native updates
here's the link
Activate AMD hardware acceleration
I created a new "easy to install package" as per many requested (based on the official OpenCore). [The attached package updated to 0.7.9] For those who only need HWAccel, post #594 has everything you need. This new package mainly offer HWAccel + boot screen. Also, this package should work in...
And it's not good idea to spoof IDs on 0.6.3 to update Big Sur. 0.6.3 Will not block potential unwanted firmware updates.
If it is configured for that, OC 0.6.4 block for now firmware updates.
Anyway it's a good practice to have a backup of your bootrom, to flash it back in case of tragedy.
For blocking updates there is a new kext developed:
github.com
GitHub - acidanthera/RestrictEvents
Contribute to acidanthera/RestrictEvents development by creating an account on GitHub.
github.com
Yes, but it has to be saidFor blocking updates there is a new kext developed:
GitHub - acidanthera/RestrictEvents
Contribute to acidanthera/RestrictEvents development by creating an account on GitHub.
.Not only 'opencore 0.6.3 will work on your Mac Pro and allow you to do Catalina and Big Sur with native updates'
@paalb:
ok, as long as the efi volume is blessed you get the boot picker and you can boot into any volume.
this seems to stick even if you go to system preferences / startup disk and select a volume and restart.
so to go to normal "non-opencore" mode you would have to boot into recovery mode and bless a normal non-efi volume?
and the blessing does not work when booted normally, it must be done from a recovery boot?
and one more:
i have a sierra, a mojave and a catalina on my 5,1
while booting into mojave and catalina works fine, booting into sierra results in a long wait with then my RX580 fans spinning to the max where i made hard reset (getting back to the boot picker)
is it known that opencore (0.64) does not work with sierra?
Last edited:
I just modded the "standard" TB3 SSDT to fit my own card (a donated Gigabyte Alpine Ridge). So that, it will ident as Alpine Ridge, but not Titan Ridge.
There is nothing special, very cosmetic indeed. But if you have the Alpine Ridge, and you want macOS can ident it correctly, you may use the attached SSDT.
Anyway, found something interesting. If we connect a USB 2.0 HID device (e.g. the Apple Mighty Mouse) directly to the USB-C port (of course, need a Type C to A adaptor) without any hub in between. It can actually works flawlessly in Big Sur.
The infamous USB bug doesn't affect the USB 3.1 ports at all.
I am not sure if this is only true for some particular cards, or same for all USB-C cards. Anyway, apart from using hubs, one more possible solution if you need to connect a USB 2.0 HID device to the cMP in Big Sur.
There is nothing special, very cosmetic indeed. But if you have the Alpine Ridge, and you want macOS can ident it correctly, you may use the attached SSDT.
Anyway, found something interesting. If we connect a USB 2.0 HID device (e.g. the Apple Mighty Mouse) directly to the USB-C port (of course, need a Type C to A adaptor) without any hub in between. It can actually works flawlessly in Big Sur.
The infamous USB bug doesn't affect the USB 3.1 ports at all.
I am not sure if this is only true for some particular cards, or same for all USB-C cards. Anyway, apart from using hubs, one more possible solution if you need to connect a USB 2.0 HID device to the cMP in Big Sur.
Dortania Guide suggests this kernel patch:
XML:
<key>Patch</key>
<array>
<dict>
<key>Arch</key>
<string>x86_64</string>
<key>Base</key>
<string>_isSingleUser</string>
<key>Comment</key>
<string>Patch IOHIDFamily</string>
<key>Count</key>
<integer>1</integer>
<key>Enabled</key>
<true/>
<key>Find</key>
<data></data>
<key>Identifier</key>
<string>com.apple.iokit.IOHIDFamily</string>
<key>Limit</key>
<integer>0</integer>
<key>Mask</key>
<data></data>
<key>MaxKernel</key>
<string></string>
<key>MinKernel</key>
<string>20.0.0</string>
<key>Replace</key>
<data>uAEAAADD</data>
<key>ReplaceMask</key>
<data></data>
<key>Skip</key>
<integer>0</integer>
</dict>
</array>
The recommended way is to always keep a disk with Mojave. The way I have solved this is that I have an old small SSD in the free CD slot with an installation of Mojave. In Bay 1 I have an SSD disk with the EFI partition and my original pre Catalina Mojave. In Bay 2 I have Catalina. Bay 3 and 4 are Data disks. When I need to go “non-opencore” I just remove the disk in Bay 1. Then the blessing will be reset and the mac is back to normal.
Not sure about Sierra.
Seems they are still figuring things out themselves.
I noticed a few USB Mapping kexts which they are not activating anywhere as well.
I though it wasn't work on some USB 3.0 card, but most likely just my bad memory.
May be it only works with those USB kexts.
But I am too lazy to make a full port mapping for my cMP now. May be try this later.
This can help automate it:
dortania/Opencore-Legacy-Patcher
Contribute to dortania/Opencore-Legacy-Patcher development by creating an account on GitHub.
github.com
Could be ... seems they may be trying to map cMP to nMP and then fully spoof as nMP
Hello
I tried to update to 11.1 on my cMP with OC 0.6.4 but the system is stuck at preparing mac 11.1 update (download was OK). Anyone has an idea ?
(I'm using the OTA upgrade)
I tried to update to 11.1 on my cMP with OC 0.6.4 but the system is stuck at preparing mac 11.1 update (download was OK). Anyone has an idea ?
(I'm using the OTA upgrade)
How long you wait? It can prepare a long time. How you determine the cMP is stuck?
Just "accidentally" did it. Wanted to just download to have it ready and walked away from my computer. Seems okay. Two reboots, one with blank screens scared me. Just watched my NVMe blinking away so I left it and it eventually came up.
It says 15 minutes remaining and it didn't move for ages (at least 10 minutes) but now it seems to move a little bit (10 minutes remaining). So it may work, I'll wait a little bit more. It's my first OTA using opencore.