In this case, better boot to High Sierra, format the Mojave SSD, and install a clean Mojave onto in.
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 Activate AMD hardware acceleration
- Thread starter h9826790
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
I tried to install Mojave from high sierra , after selecting Mojave SSD for installation then restart, opencore boot selector came , I selected macOS installer from it. After that was apple logo and progress bar for 10 seconds then black screen for 30 minutes , I tried to restart and do the same process even load mojave installer from bootable flash drive that I’ve created before , but no difference, black screen after apple logo with progress bar,
I didn’t have this problem when I Installed catalina from High sierra.
Is it possible that opencore doesn’t allow installation of os older than Catalina?
I waited even 45 minutes then Installation log error came
I clicked restart to start installing macOS again but same happened.
My OC package should allow Mojave installation. But if encounter error, you may remove OC first. You don’t need it to boot High Sierra, and Mojave anyway.
Then re-install OC after Mojave installation completed.
Or you may try some older package. e.g. 0.7 etc and see if that make any difference.
Then re-install OC after Mojave installation completed.
Or you may try some older package. e.g. 0.7 etc and see if that make any difference.
I finally did it with removing all drives then clean install Mojave then I used your older method with Opencore 0.5.5 you‘ve just posted in 16 Feb 2020 in post #594
now I have everything working ; simple Boot Selector
( not a fancy one like opencore 0.9.0 ) but it works and fully functional HW acceleration H264 and HVEC
thanks to you 🙏🙏🙏
I like this one better because it gives me Mojave Updates not Catalina which I don’t need and I can’t use because it lacks 32bit support that I need for my sound card and midi keyboard to work
finally I have a question is it safe to install macOS security updated or other updates that come in software update window ? Or I should Avoid it
I will post more results when I installed Premier pro , … and other video related software
There is no more security update for Mojave, no need to worry about that.
And this lastest one is safe to apply.
And about newer open core like 0.7 version you just mentioned , is there a difference between version 0.5.5 and 0.7 in performance and features in Mojave , should I give version 0.7 a try?
I've been reading all the comments for 8 hours and I understand absolutely nothing. LOL.
it all seems very confusing, 1) which post should i follow? the #1 post where I have to type a lot of commands or #1314? which is just copy and paste new boot files?.
i have a mac pro 4.1 which i have already updated to 5.1 mojave i have rx570.
it all seems very confusing, 1) which post should i follow? the #1 post where I have to type a lot of commands or #1314? which is just copy and paste new boot files?.
i have a mac pro 4.1 which i have already updated to 5.1 mojave i have rx570.
@h9826790 I'm with @ufolouco! I saw your latest 0.9.1 post on fb and this stuff is making my head spin! I am hoping to get Monterey running on my 4,1 -> 5,1, but it seems like you're saying that attempting with 0.9.1 is not a good idea. Is that an accurate understanding? If so, what would be the best release for doing this? And is it still recommended to install on SATA rather than NVMe SSD? Finally, I have a USB3 card and latest WiFi/Bt that I would like to work if at all possible. Or maybe it's not? I appreciate your incredible efforts and plan on contributing to the dev fund!
0.9.1 is fine. You can follow the steps in post #1314 to install 0.9.1
Then follow the video in that post (additional option 3) to mod the config.
Once you finish these two steps, you can install the latest Monterey natively.
After that, undo the changes in additional option 3 (or simply replace the config.plist by the default one), and reboot. Then everything is done.
Yes, leave OpenCore on any SATA drive is usually more stable. NVMe is fine, however, for some setup, NVRAM reset will disable OpenCore. By considering there is no practical performance benefit to install OpenCore onto NVMe, I personally recommend install OpenCore onto SATA drive. But this is not mandatory.
A proper USB 3 card and Wifi ac / BT 4 card should be natively supported by Monterey.
Yeah, this thread was originally to activate H264 / HEVC HWAccel. But slowly deviate to OpenCore support. So, it's a kind of messy, a bit hard to follow.
But the idea is simple. If you only want something tailor make for cMP. And most likely can work without too many user input, this package is for you.
It isn't completely effortless for the user, I demand the user to learn some very basic stuff like how to mount the EFI partition. IMO, this is the basics that a user should know. Otherwise, on the day that something goes wrong, can be too hard to recover.
If you want something even more user friendly, may be OCLP is a better choice for you. However, if anything goes wrong, that can be very painful to recover if you don't know the basics.
cdf provided a very detail guide on how to make your own OpenCore EFI folder for cMP. If you have time, you better read that though.
A million thanks in advance!
well thank you for your thorough response! after reading I have a quick followup question - kind a two parter, and then one other if you don't mind.
I got the NVMe SSD setup under the impression that the newer OS's ran far better on SSDs. I guess it's just more curiosity as to why you recommend installing on SATA. Is it simply the NVRAM reset issue? EDIT - and mOS,E,J, not APFS?
Lance @macsoundsolutions said you likely won't be supporting Ventura. I was originally attempting to go with OCLP because there seemed to be a roadmap for Ventura but hit a mysterious roadblock so now I'm looking at your "MLOC". Is there a technical reason you won't be pursuing Ventura?
Thanks again for you time & expertise!
Last edited:
Monterey 12.6.5 update successfully (as usual, with VMM on, SMBIOS spoofing off). HWAccel still works as expected. It seems a very normal security update this time. Safe to apply.
+1
I am also curious if Martin Lo will be working on Ventura compatibility, or is Monterey the "end-of-the-line" for his package? Thx for any info.
I also managed to install Monterey and it has graphics acceleration working 100%. But my bluetooth nor Wifi is working.
Well, it sounds like Open Core and OCLP are working it out for the 5,1 machines, albeit with a patch.
I guess I was wondering if this progress might trickle down to Martin Lo's package. But I guess not? Regardless, I sincerely appreciate Martin Lo's efforts thus far.
I recommend SATA SSD, but not SATA HDD. SATA SSD is still a low latency storage.
Under most situation, the system responsiveness is very similar between running OS from SATA SSD and NVMe. NVMe has much higher sequential speed than SATA SSD, but not necessary better 4K random read QD1 (most of them are, but just not necessary).
I recommend SATA SSD mostly because it has better compatibility on the cMP. And less unexpected issues for far. For most normal users, there is little to no real world performance difference of running OS from SATA SSD
But I want to make it more clear, I recommend people install my package (the OpenCore part) onto a SATA drive (SSD or HDD doesn't really matter), but macOS (or any other OS) onto SSD (SATA of PCIe / NVMe doesn't really matter). And they are completely seperated. You can install OpenCore onto a SATA HDD, but install Monterey on a NVMe. However, if put both thing together, the best solution will be a single SATA SSD which contain both OpenCore and the OS.
There were few reports about OpenCore was disabled when performing NVRAM reset. So, I recommend people install OpenCore onto a SATA device (if that exist). OpenCore is just a very small piece of software, even may cost 1-2 more seconds to load from HDD, but this minor performance impact only happen during the very early boot stage.
By considering most people aren't using their cMP to run OpenCore boot test, this minor performance is very acceptable if can further increase stability. Especially before EnableGop(Direct) exist, most uprgaded cMP has no native boot screen support. It can be quite hard for some user to recover from that situation. cdf provided a very bullet proof recovery solution, an OpenCore CD. But it seems not many people aware that they should create such an emergency CD (especially for those who has a GPU that's not supported before Catalina).
Anyway, if there is only NVMe in your cMP. Or you installed everything onto a NVMe, but only use SATA drives for data storage, and never have any issue. Then I will say you better keep your existing setup. As general rule, don't fix anything which aren't broken.
As the others pointed out. Ventura need AVX2 for many basic functions.
And there is no way for the cMP to get real AVX2 (we simply can't upgrade the CPU to that generation).
So, to run Ventura on cMP, we either patch (lots of) system files, or there is a AVX 2 emulator that allow the cMP to boot Ventura (but not just running software after boot to desktop).
For system files patching, OCLP is already doing that.
For AVX2 emulator, I still have a hope that will come. If that happen, I will see if that's good enough to allow me to create a pre-configured OpenCore package for 5,1 to run Ventura. But so far, it seems not that straight forward.
Also, even we have AVX2 emulation to fix most of the core issues, but something like lack of USB 1.1 support still there. Therefore, even we can run unpatched Ventura on cMP, most likely some other work around still be required to alleviate such hardware issue.
Thanks for the info. 👍 I understand there isn't a simple, nor immediate solution available. And perhaps there may never be... But it's nice to hear you have hope that this might be doable some day.
If there are stable workarounds, I don't think folks will mind so much. Currently, on Monterey I needed to bring in another USB 3 hub so my 1.1 devices (a number keypad and a couple of USB MIDI controllers) could be recognized by my 5,1. I don't believe this is an unrealistic workaround for a 13 year-old machine.
I doubt Ventura brings enough new features to the Mac Pro 5,1 to make it a compelling upgrade really. I'd prefer to stick to a stable solution, though it's great that people are trying to figure out AVX2 support. If there's a breakthrough, I may give it a go. Monterey will be widely supported for the next few years though, and I don't intend to still be using a cheesegrater as my primary machine at that point.
There are a couple of features from Ventura I miss on my cMP (running Monterey)--the ability to edit iMessages (to correct spelling, etc.) is pretty handy. I also like the native weather app, even though it's been a big buggy lately.
But more than anything about Ventura itself, there are a few iCloud-related things people are interested in that require Ventura+ on every Mac you use:
1. Advanced Data Protection for your iCloud account requires macOS 13.1 or later on all Macs you sign into with your Apple ID.
2. Security Keys for Two-factor authentication on your iCloud account requires macOS 13.1 or later on all Macs you sign into with your Apple ID.
3. HomeKit's new architecture requires macOS 13.2+ on any Mac on which you want to use the Home app
#1 and #2 are completely out of the question for you if you want to use your cMP running Monterey or earlier with your Apple ID. #3 is not a problem if you are willing to not use the Home app on your cMP. But for people with HomeKit devices set up that's a bit of a pain. Honestly, I am surprised and annoyed that Apple didn't make the new HomeKit architecture backwards compatible with Monterey since they orphaned a lot of Macs with the Ventura update and presumably they want more people using HomeKit. I'm sure a lot of people updated their HomeKit architecture without realizing they were going to lose access on their pre-Ventura Macs--and once you convert you cannot revert to the older architecture.
So there are really valid reasons for wanting Ventura compatibility on as many Mac models as possible, including the MacPro5,1.
Fall of next year, when macOS 15(?) comes out. So it's basically a year and a half away.
But the point is taken. I also wonder if the OC/OCLP devs will lose interest in Ventura once macOS 14(?) is released this Fall. Sounds like OCLP is doable for Ventura as long as you're willing to forego USB1.1 or USB 3.0. But unless Syncretic can get AVX emulation working I can imagine that future macOS releases are going to become nearly impossible to get running on our old Westmeres.
It's still a hell of a run for these venerable old machines.