Do you see nothing or a text menu as a picker? If it is the last one, please check your settings at PickerVariant and set it to `auto` or `Acidanthera\GoldenGate`.
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
if this gpu has a physical firmware switch it must be set to gaming.
computing has a modified bios and gop is lost.
Using OC 0.7.1 with the VMM flag set. I am trying to update Catalina with Security Update 2021-0004.
Software Update is unable ti Check for Updates and notes that Updates for this Mac are managed externally.
Clicking details I restored defaults but keep ending up with the same result.
SOLVED: signed into another account on the system and all was well from there. My account was fine after the update.
Software Update is unable ti Check for Updates and notes that Updates for this Mac are managed externally.
Clicking details I restored defaults but keep ending up with the same result.
SOLVED: signed into another account on the system and all was well from there. My account was fine after the update.
Last edited:
I'm loosing really a lot of time on this, but I can't permit now. Trying to adjust boot picker, I broke boot at all. With some setting picker appeared, but booting the cMP with Mojave went mostly in a prohibition sign (and sometimes even Catalina got stuck until hardware reset).
At the end, I did a nvram reset and started over OC install. Now I've installed manually OC and then I've overwritten with Martin's Package, and again, cMP boots without showing the picker, and with long boot times. Now I can't spend much time again on this... really I've to much important thing to finish. In the meantime, I can say that this is my graphic card: https://www.sapphiretech.com/en/consumer/nitro-rx-580-8g-g5
P.S.: another strange (for me) behavior I discovered, is that trying to install Catalina, installer application hangs on startup, either by starting the installation from the boot disk (disk A), or by starting the installation from Mojave (disk B).
Last edited:
Ok, question time.
First the background:
I've got a 5.1 Dual proc 3.46 Hex core westimer with 96 GB Ram, 2 internal SSD's on a sonnet card. Have a Radeon 580 installed and have been running Mojave for a long time without any problems.
Back in December, I tracked an album for a band in Logic. I've been a Logic user since it was owned by Emagic, but hadn't used it in some time prior to this album. At the time I tracked the album in December, I downloaded the trial version of the then 13.2 version of Logic Pro just to get the tracks laid down done, figuring I'd buy the upgrade by the time it came to mix it. Band leaves, goes and tracks the rest of the vocals in a different studio and with different software and such for the album and now it's mix time, and I have all the instrument solos still in Logic here.
I fire up Logic, fully expecting the Trial Expired dialog and romped the buy button which took me to the Apple store. Apple store informs me I can't install the *now* current version of Logic (previous install was last December which ran fine on Mojave) unless I have big Sur, and furthermore I can't even BUY it without Big Sur.
Did a bit of research and according to a 2018 Apple Post and if I can buy Logic on ANY box that can run the current OS, then I can cancel the install, go back to the Mojave box, return to the apple store and download the last previous version of Logic which will run on Mojave, which would be fine to finish the album.
However, I don't have ANY Apple hardware that'll run Big Sur.
So I headed here, read the guide, tried the less complicated OpenCore patcher, downloaded 16.7.2 and built the USB Stick and never got the OC BootPicker to show up, just a black screen.
Fixed that by doing the guide here, step by step, and installing that to the EFI Partition on the 2nd SSD which was where I was going to land big sur just to get to the apple store to be able to buy logic, and it gave me grief that there wasn't a hardware partition on the SSD and as a result the installer could not run.
OK fine, so I copied the now WORKING OC install back onto the flash drive I'd originally prepped the 16.7.2 installer that OpenCore Patcher had created and booted off that. That worked fine, boot picker came up and allowed me to run the installer. However the installer got to a reboot, and then rebooted and nothing came back up, and in fact the box shut itself off. Restarts resulted in the same thing.
Ok Fine again, pulled the USB Stick, did a command option PR to reset the Pram, rebooted back into Mojave which is where I'm at now.
I'm guessing its this whole version > 11.2.3 thing I've been reading here (as the OpenCore Patcher pulled down Big Sur 11.5.2 (16.7.2 Installer Version). Further I'm guessing that if I pull down the 11.2.3 thing, rebuild the installer flash drive with the 11.2.3 installer, then recopy my existing OC Install back onto that, that I should be able to at least get 11.2.3 to install.
So here's the questions:
1: Do I need to roll back farther to installer V. 16.4.07 (Big Sur 11.2.2) or are the problems just AFTER 11.2.3, or will 11.2.3 be ok?
2: Will I need to redo my config.plist just because the installer went from 16.7.02 down to 16.4.08?
3. What will I need to do to shut off auto updates to preclude the issue?
Bear in mind I don't need to even RUN big Sur once I get into the App Store to BUY the logic upgrade, I just need to be able to buy it and I HAVE to be running SOME version of Big Sur to do so. After that I can go back to my Mojave boot volume, and go back to the app store to download the last version of Logic that will run on Mojave (if the Apple Tech Tip from 2018 is still correct). I've blown an entire day on this so far and the clock is ticking. None of this would even have been necessary if Apple wouldn't force you to have the latest OS just to buy the damn thing. I don't need the latest and greatest, I just need logic to open the damn projects up and export the regions as Wave files to send them to the mix engineer, and I could care less what version of logic it is, but my older purchased install can't open these because they were tracked in a later version. I hope to hell this isn't too confusing,
Thanks in advance.
First the background:
I've got a 5.1 Dual proc 3.46 Hex core westimer with 96 GB Ram, 2 internal SSD's on a sonnet card. Have a Radeon 580 installed and have been running Mojave for a long time without any problems.
Back in December, I tracked an album for a band in Logic. I've been a Logic user since it was owned by Emagic, but hadn't used it in some time prior to this album. At the time I tracked the album in December, I downloaded the trial version of the then 13.2 version of Logic Pro just to get the tracks laid down done, figuring I'd buy the upgrade by the time it came to mix it. Band leaves, goes and tracks the rest of the vocals in a different studio and with different software and such for the album and now it's mix time, and I have all the instrument solos still in Logic here.
I fire up Logic, fully expecting the Trial Expired dialog and romped the buy button which took me to the Apple store. Apple store informs me I can't install the *now* current version of Logic (previous install was last December which ran fine on Mojave) unless I have big Sur, and furthermore I can't even BUY it without Big Sur.
Did a bit of research and according to a 2018 Apple Post and if I can buy Logic on ANY box that can run the current OS, then I can cancel the install, go back to the Mojave box, return to the apple store and download the last previous version of Logic which will run on Mojave, which would be fine to finish the album.
However, I don't have ANY Apple hardware that'll run Big Sur.
So I headed here, read the guide, tried the less complicated OpenCore patcher, downloaded 16.7.2 and built the USB Stick and never got the OC BootPicker to show up, just a black screen.
Fixed that by doing the guide here, step by step, and installing that to the EFI Partition on the 2nd SSD which was where I was going to land big sur just to get to the apple store to be able to buy logic, and it gave me grief that there wasn't a hardware partition on the SSD and as a result the installer could not run.
OK fine, so I copied the now WORKING OC install back onto the flash drive I'd originally prepped the 16.7.2 installer that OpenCore Patcher had created and booted off that. That worked fine, boot picker came up and allowed me to run the installer. However the installer got to a reboot, and then rebooted and nothing came back up, and in fact the box shut itself off. Restarts resulted in the same thing.
Ok Fine again, pulled the USB Stick, did a command option PR to reset the Pram, rebooted back into Mojave which is where I'm at now.
I'm guessing its this whole version > 11.2.3 thing I've been reading here (as the OpenCore Patcher pulled down Big Sur 11.5.2 (16.7.2 Installer Version). Further I'm guessing that if I pull down the 11.2.3 thing, rebuild the installer flash drive with the 11.2.3 installer, then recopy my existing OC Install back onto that, that I should be able to at least get 11.2.3 to install.
So here's the questions:
1: Do I need to roll back farther to installer V. 16.4.07 (Big Sur 11.2.2) or are the problems just AFTER 11.2.3, or will 11.2.3 be ok?
2: Will I need to redo my config.plist just because the installer went from 16.7.02 down to 16.4.08?
3. What will I need to do to shut off auto updates to preclude the issue?
Bear in mind I don't need to even RUN big Sur once I get into the App Store to BUY the logic upgrade, I just need to be able to buy it and I HAVE to be running SOME version of Big Sur to do so. After that I can go back to my Mojave boot volume, and go back to the app store to download the last version of Logic that will run on Mojave (if the Apple Tech Tip from 2018 is still correct). I've blown an entire day on this so far and the clock is ticking. None of this would even have been necessary if Apple wouldn't force you to have the latest OS just to buy the damn thing. I don't need the latest and greatest, I just need logic to open the damn projects up and export the regions as Wave files to send them to the mix engineer, and I could care less what version of logic it is, but my older purchased install can't open these because they were tracked in a later version. I hope to hell this isn't too confusing,
Thanks in advance.
Logic files can be copied and can be opened in a newer version of Logic Pro.
If all you need is to export them to WAV, perhaps i could help you.
I'm running Logic Pro 10.5.1 (latest Mojave version).
If you made the files with the same version or older , sent me a PM if you want.
Last edited:
Hi everybody,
Here's my problem .. I have a working legacy windows 10 on a SSD in the CD bay, Big Sur 11.2.3 on nvme and opencore 0.6.3 and RX580, but ;
-With GT120 I get bootscreen and Windows working, but Big Sur hangs at startup
-Without GT120 I can't boot Windows (Startup disk utility SDErrorDomain error 104)
I remember trying windows 10 UEFI without success, and I also tried bootchamp, bootmanager, quickboot etc ... no way
Is there a way to repair something to make the startup disk utility work ? (Should it work ??)
Or is there a easy way to get windows in the opencore menu ? (Legacy to UEFI didn't do the trick for me)
Thanks in advance.
Here's my problem .. I have a working legacy windows 10 on a SSD in the CD bay, Big Sur 11.2.3 on nvme and opencore 0.6.3 and RX580, but ;
-With GT120 I get bootscreen and Windows working, but Big Sur hangs at startup
-Without GT120 I can't boot Windows (Startup disk utility SDErrorDomain error 104)
I remember trying windows 10 UEFI without success, and I also tried bootchamp, bootmanager, quickboot etc ... no way
Is there a way to repair something to make the startup disk utility work ? (Should it work ??)
Or is there a easy way to get windows in the opencore menu ? (Legacy to UEFI didn't do the trick for me)
Thanks in advance.
Hi, maybe the answer is here somewhere in this thread but I can't seem to find anything related - is there some issue with Opencore and BigSur 11.5 on 5,1 that would prevent me from syncing my iphone? Cannot seem to be able to mount it in Finder using front USB ports. IPad pro mounts OK and appears in Finder. iPhone auto launches Photos app as usual but doesnt mount in Finder (appears in USB section of System info as iphone). Was working fine with 11.2.3
11.2.3 is the last version without issues with a MacPro5,1.
No. Config.plist changes when OpenCore releases a new version, not when Apple release an updated Big Sur release.
You can use latebloom to minimize 11.3+ kernel panics at boot, but since you don't need Big Sur…
You can still download older versions of apps that you previously bought that are compatible with the macOS release that you are running, I do it all the time with Apple's RemoteDesktop and HighSierra/Mojave.
First, remove the GT120 GPU, since Mojave Apple removed support for using multiple GPUs that are dissimilar, this now causes all sort of issues. Worst yet, you are using a supported and an unsupported one.
Use MyBootMgr to have BootCamp working with OpenCore:
MyBootMgr: RefindPlus&OpenCore
I see you use a RX580 Nitro. OpenCore is sensitive to the ROM you use. I remember on my RX580 I had a dual ROM switch, by default set to Performance mode. I was not able to see also the bootpicker, until I switched to Quiet mode. See #1 and #10 thread posts.
If you don't have a dual ROM card, is very easy to fix the issue by flashing a recommended ROM, as I explained into #1 post.
Last edited:
Have you actually confirmed this on a MyBootMgr setup?
I actually think (not confirmed) that GOP is always present but that the variant in one mode just can't be used on a cMP for the same reason the GOP on modern Nvidia GPUs can't be used and that if you use the
reload_gop feature in RefindPlus, which is always switched on by MyBootMgr, it will load. OpenCore now also has an equivalent setting (well, two settings that combine to give the same outcome).Not confirmed as said since I don't have such a GPU, but fairly certain that is what is the case. Basically, both modes should load on a MyBootMgr setup. It might be the case that it is better to use one or the other mode in running things in the OS, but the bootscreen should always show up.
EDIT:
I think the issue with the mode switching is likely to essentially be the same as this:
Activate AMD hardware acceleration
Actually, it turns out that when a GOP driver, a UEFI 2.x driver, is implemented according to the associated UEFI 2.x Specs, it does not work on Classic MacPros and that what works for us is what is actually the "Broken" UEFI GOP. Basically, one of the first items in the UEFI 2.x Specs for a...
forums.macrumors.com
Last edited:
Even there's a hole with an inscription, I can't see any switch:
I tried to flash the card, with one of the firmware downloaded from techpowerup.com, but went in panic because after reboot I didn't have any signal from card, and I thought I broke it for good. Then, fortunately, using the GT120, I was able to reload the original firmware. Desperate case, or is there a chance to find a firmware that works?
However, I also want to reiterate that in the various experiments, I was able to bring up a sort of picker. It was after installing OpenCore Legacy Patcher provided by the Dortania, only that with that configuration, the MacPro crashed booting macOS (even with Mojave on disk B).
Last edited:
I've *finally* found the time to start playing with OpenCore Legacy Patcher on a number of different systems / models.
A question I've immediately run into, and which has probably been answered elsewhere in this thread (but it's now 343 pages long, so I have zero hope of finding it).
On my MacPro systems; these are 4,1's flashed to 5,1's and all are upgraded to *at least* dual X5660 processors and AMD RX 560 graphics cards. The OpenCore Legacy Patcher is detecting that these are supported MacPro 5,1 systems.
Should I build and install as if they are 5,1 machines? Or should I change the target model to 4,1 machines?
A question I've immediately run into, and which has probably been answered elsewhere in this thread (but it's now 343 pages long, so I have zero hope of finding it).
On my MacPro systems; these are 4,1's flashed to 5,1's and all are upgraded to *at least* dual X5660 processors and AMD RX 560 graphics cards. The OpenCore Legacy Patcher is detecting that these are supported MacPro 5,1 systems.
Should I build and install as if they are 5,1 machines? Or should I change the target model to 4,1 machines?
Only use MP4,1 with early-2009s still with a MP4,1 series firmware.
Where you see "bios switch" there's a tiny slide switch inside , visible with a torch/light of your cellphone.
Managed to get it solved.
HUGE thanks to @tsialex, his patient assistance, education and what ultimately led to an emergency rebuild of my bootRom may very well have saved me from a bricked box, but also allowed me to get OC to actually work and be able to install Big Sur.
Was able to get into the App Store and buy Logic, (finally) and am just waiting for the ginormous Big Sur install to finish downloading, then will roll back to a new (safe) Mojave install and reload the older version from the App Store for it.
Learned a bunch of things along the way…
I was planning on putting a new 1TB Samsung Evo on the 2nd slot of the Sonnet card, and as it turns out the Sonnet Card and OC don’t get along spectularly well, so I ended up robbing a SATA carrier from another CMP and putting the Big Sur SSD on that, as well as taking out the old Mojave SSD and putting it on a carrier. It’s not currently installed as if I boot from it, I get a massive drop in VSS store free space requiring a reflash of the bootRom under a clean Mojave install on yet another SSD to fix.
Game plan is to get through the whole album export thing, then manually migrate the stuff off the old Mojave SSD to the “clean” one, and once that’s done reformat the old Mojave SSD and rebuild that as the new “safe” Mojave build in case either the OC install has issues or i have problems with the now “working” Mojave SSD install.
I’d tried using a 4tb spinner that was an installed spare before I upgraded my NAS Raid 10’s from 4 to 8tb as the “Safe“ Mojave install but the first install didn’t go well at all (lotta black screens and continuous reboots) and the 2nd I’m just not 100% sure of and just don’t want to risk it. I’ve got a couple more Sata carriers. and a 250gb Evo on order to be the final safe Mojave backup in case OC tanks.
What I haven’t tried yet (and will hold until I get this album export stuff done) is connecting the other 2 4K displays to the RX 580. I did the hybridization thing in OC to not have to screw with the VMM thing, but now it thinks it’s an Imac and I dont’ know how it’ll respond when I jack the other 2 LG’s in. Interestingly the display DOES report as the correct LG model, so maybe I’ll get lucky on that front. Will see.
However, I just want to thank Alex again (and @KeesMacPro for his kind offer to use his logic to get the exports out if everything else failed) and the entire community here for the massive testing, research and work that has gone into keeping these old boxes up and running.
I’ve upgraded 3 of these CMPS with dual hex core Xeon’s (and delidded all 6 of em), dumped a ton of ram into em at a fraction of what apple charges for new machines, thrown SSD’s into all of em and have managed to get all manner of utterly unsupported GPU’s to run for years with you folks help. Being a Covid Layoff with not a lot of recovery in my industry in site, these things are particularly helpful when one doesn’t just have 8-10K to toss at a new desktop. You folks are beyond awesome.
Thanks,
Mark
Opppsss... seeing nothing, I assumed that the hole on the casing was standard for cards with or without the swich. I'll look better tomorrow.
If your config is correct, then there should be no ill effects to using hybridization, and except for a possible macOS notification about your "new iMac Pro", there should be no outward indication of the spoofing.
Do I need a version of Catalina other than the latest 10.15.7? I've already gone through an OpenCore install on an iMac 14,1 -> Big Sur 11.5.1 with zero issues. A breeze!
I expected a few more problems with my old MacPro beasts of course, but was able to create the OpenCore installation drive without issue; just going for Catalina for now.
The good: I am greeted with a boot screen! Amazing!
The bad: Choosing "EFI" as the Boot drive, as docs tell me to do, results in about 3 minutes of black screen followed by a restart right back to the boot screen. Choosing the "Install macOS Catalina" instead I do get the Catalina installer, but when I try to install I receive the message "This version of macOS 10.15.7 cannot be installed on this computer."
Thinking back on that, I'm pretty sure this also occurs if I try to build DosDude patched installers for these MacPros and 10.15.7, so I'm thinking that I need to start with an older version and update once that's in place?
(Alternatively, since this OpenCore USB installer has theoretically be configured properly for a MacPro 5,1 I could easily yank the destination SSD from the Pro and simply perform the install on a different piece of equipment, then reinstall the SSD. I'm going to give that a whirl now.)
I expected a few more problems with my old MacPro beasts of course, but was able to create the OpenCore installation drive without issue; just going for Catalina for now.
The good: I am greeted with a boot screen! Amazing!
The bad: Choosing "EFI" as the Boot drive, as docs tell me to do, results in about 3 minutes of black screen followed by a restart right back to the boot screen. Choosing the "Install macOS Catalina" instead I do get the Catalina installer, but when I try to install I receive the message "This version of macOS 10.15.7 cannot be installed on this computer."
Thinking back on that, I'm pretty sure this also occurs if I try to build DosDude patched installers for these MacPros and 10.15.7, so I'm thinking that I need to start with an older version and update once that's in place?
(Alternatively, since this OpenCore USB installer has theoretically be configured properly for a MacPro 5,1 I could easily yank the destination SSD from the Pro and simply perform the install on a different piece of equipment, then reinstall the SSD. I'm going to give that a whirl now.)
Appears to be so. Had no issues hooking up all 3 4K displays to the 580 outside of Big Sur's stupid change from specific resolutions to "big Text More Text Less Text" and whatnot in the displays section, as the left LG didn't like either the stock 1080 or the alternatives. I've had to switch it to 1080p in the past then bump to 2580x1440 or whatever after doing that. Fixed that by swapping the HDMI for a DisplayPort cable and it seems to boot fine.
Had no issues getting either the new Mojave or Big Sur boots to log onto newly created Time Machine shares of the NAS and both backed up without issue. No video glitches. Aperture runs fine to a Nap mounted library (course it did that before). Logic runs fine on both mounts, and the App Store "the latest version of logic won't run under this oS (Mojave) would you like the latest compatible which turns out to be 10.5.1. Album was tracked in 10.3.2, and once logic was reinstalled the folders changed back to project files and opened without incident.
Last things to check are Fusion360 and Rhino in Big Sur. The Prusa Slicer works fine in both. Biggest PITA will be the reinstallation of pretty much everything on both Mojave and Big Sur as my old Mojave bootable was playing havoc with the NVRAM utilization. I'll mount it to get the files and app settings PLISTS off but won't boot from it. Got a lot of settings to redo and files to manually copy over as I don't trust the migration assistant to no bugger up my now clean boot rom that Alex so carefully reconstructed for me.
OK, at last a found the switch and turned the card to "the other mode" (is there a way to know which mode I get?). But nothing changed for boot picker... I can't see any.
And looking the GPU-Z information, the ROM seems exactly the same with 1340/2000MHz default clock (I don't insert both screenshots, because they have exactly the same data):
.
But the firmware that ati-atiflash utility said it's the same as the one loaded on card before any modify, was the one compiled on 2018-07-19 01:39:00, with 1411/2000 clock frequencies. And the one that ati-atiflash utility accepted to load on card (an with which card seemed to be broken), was the one compiled on 2017-10-19 06:35:00, always with 1411/2000, instead ati-atiflash utility won't install the firmware with 1340/2000MHz.
Last edited:
The ROM size will always be the same, as your dump is a binary image of the physical EPROM, either 128 or 256 kbytes.
The version reported may be the same.
Compare the two files and report back.