I noticed some folks are installing OpenCore on their MacBook Pro's,
I have a 15" 2008 4,1 MacBook Pro and want to see if i can do a native install of Mojave on it,
rather than the patched install of Mojave currently installed.
What is the eariest model MBP that OpenCore will work with?
I noticed some folks are installing OpenCore on their MacBook Pro's,
I have a 15" 2008 4,1 MacBook Pro and want to see if i can do a native install of Mojave on it,
rather than the patched install of Mojave currently installed.
What is the eariest model MBP that OpenCore will work with?
Make sure that your wireless chipset is natively supported. Alternatively, there are kexts that you can use for enabling older cards. Also note that booting between different versions of macOS may require a reboot to get wireless to work.
As for deleting OpenCore, it is just a matter of deleting the files in your EFI partition and rebooting. Make sure not to have any disks with unsupported versions of macOS, because this can cause troubles booting.
Thanks. My Wi-Fi card is original Apple AirPort Extreme 802.11n and in the past was ok with OC and Catalina.
I don’t uderstand. Also reboot not solve my problem.
I have only ssd with OC and Catalina. If I prepar bootable usb with Mojave, Can I reboot and eresse all ssd for install Mojave via usb?
That would be the Broadcom BCM94322 chipset. Support for this card actually stops at Mojave. Moving forward, your best bet is to upgrade. In the interim, you may have some success with the IO80211Mojave.kext. A quick search should bring up instructions for using this kext.
I have only ssd with OC and Catalina. If I prepar bootable usb with Mojave, Can I reboot and eresse all ssd for install Mojave via usb?
This only applies if you have a standard graphics card (not flashed for Mac). Although the USB installer will provide the graphics drivers for the initial setup, once your Mac reboots to complete the installation, you will be in the dark for a while until Mojave starts.
This only applies if you have a standard graphics card (not flashed for Mac). Although the USB installer will provide the graphics drivers for the initial setup, once your Mac reboots to complete the installation, you will be in the dark for a while until Mojave starts.
Thx, I have a RX 580 8GB and it's not flashed for Mac. If the problem is only temporary, it's ok.
I'll try to put correct IO80211Mojave.kext in my configuration, if I'm not able todo this, I'll format ssd to put Mojave in.
Can I format directly SSD from usb bootable with Mojave? Or I have to put Mojave first in HDD and then, when Mac starts by HDD, I have to format SSD with Mojave also and delete HDD?
Can I format directly SSD from usb bootable with Mojave? Or I have to put Mojave first in HDD and then, when Mac starts by HDD, I have to format SSD with Mojave also and delete HDD?
I'm afraid that, once again, some users are going off topic. This thread is about OpenCore for Mac Pro. It is NOT about replacing obsolete hardware components. Those in need of information about newer BT/Wi-Fi modules should go to the relevant threads (not this one) or send a private message of a knowledgeable user. Please, don't derail this thread with irrelevant concerns.
Not sure why this response was warranted. This was truly not helpful. This was a question because there was a discussion about this previously and changes in the OC config that may make it work. But thanks for taking the time adding nothing to this.
Installed Monterey Beta 7 also this morning. One reboot produced the crossed out circle and one hung. But it installed and rebooted 2 more times with no problem.
Ahhh. Awesome. Good to hear. Seems like this is going to be similar to Catalina as @cdf mentioned. I don't mind that. In addition, once @Syncretic releases his race condition fix, we may have added more life to our Mac Pro for at least one more release.
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.
🚫 macOS Big Sur 11.3 and higher is currently not viable for the Mac Pro 5,1. A possible workaround is currently in testing.
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:
This guide (step-by-step hands-on instructions)
Martin's Package (very popular easy-to-install one-package-fits-all solution provided by @h9826790 with emphasis on hardware acceleration)
MyBootMgr (great multi-boot solution provided by @Dayo with a rich suite of helper apps for setting up and maintaining RefindPlus and OpenCore)
OC Plistlib Generator (diligent programmatic solution provided by @TECK for automating OpenCore updates)
Another great solution is the OpenCore Legacy Patcher (OCLP) provided by the Dortania team. This solution, which applies not only to the Mac Pro 5,1, probes your hardware to dynamically configure OpenCore for your Mac.
Requirements
This guide is aimed at systems with the following specifications:
Mac Pro model
Early 2009 with MacPro5,1 firmware,* Mid 2010 or Mid 2012
Processor architecture
Westmere (E56xx, L56xx, X56xx) / Gulftown (W36xx)
Boot ROM version
144.0.0.0.0
Graphics
EFI (flashed) or a standard UEFI card (PC GPU) supported in Catalina or Big Sur
Wireless
Chipset supported in Catalina or Big Sur (BCM943224, BCM9435x, BCM9436x)
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.
Is asking for a download link to 11.2.3 allowed on this forum? I missed the boat on upgrading my Mac Pro 5 1 and I'd like to update it to the last version before the issues started with 11.3. I've searched around on the internet looking for a legit link but only found shady torrents.
Great I'll take a look and post there if there are any questions. I was asking because my cMP is working perfectly with nothing "broken" but my software update is reminding me to update and I'm not sure I should or even need to. So I thought I'd see what experiences are out there to gauge the risk.
Is it currently possible to have conditional patches? In particular, if I have "Patch A" in one location and "Patch B" in another (non-adjacent) location, is there a way to set up the OpenCore patcher to say "only install Patches A & B if both succeed, otherwise don't install either one"? I have a two-part patch I'll be posting very soon, but if either part of the patch fails while the other succeeds, there will be a kernel panic. I'd like to bind them together so they install all-or-none style.
I didn't see anything in the docs suggesting that this is possible, but I figured it can't hurt to ask. Thanks in advance.
Perhaps bridge the gap by replicating the original item to make it one big patch?
I suppose that might introduce other issues or mean multiple versions if the gap varies in different releases.
Is it currently possible to have conditional patches? In particular, if I have "Patch A" in one location and "Patch B" in another (non-adjacent) location, is there a way to set up the OpenCore patcher to say "only install Patches A & B if both succeed, otherwise don't install either one"? I have a two-part patch I'll be posting very soon, but if either part of the patch fails while the other succeeds, there will be a kernel panic. I'd like to bind them together so they install all-or-none style.
I didn't see anything in the docs suggesting that this is possible, but I figured it can't hurt to ask. Thanks in advance.
