It will happen if OC is properly installed and boots first but its configuration is botched.
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
Hi,
I do own a Alpine Ridge Card, and I use it without Problems on my cMP 4.1->5.1 as an USB3 Controller. The Card is flashed, I got an working SSDT forme a "macuser"...
The reboot "problem" with Thunderbolt3 devices preisists. I have to to a warm boot to use my DSLR with the "BlackMagic Ultra Studio Mini Recorder" The Blackmagic device is recognized in the System Profiler, as TB dev. at first boot, but not working (BM Software could not see it) aufter a worm boot it ist working perfectly. Even the older TB2 version with the Apple TB2<->TB3 adaptor... (the BM Recorder does not have a separate power supply(!))...
Is there anything i can do? Flash an other Firmware, try a different SSDT, change the OpenCore config, etc?!
My Problem is when I get an invitation to an teams call unexpectetly, I have to do a reboot... which is having an impact to my workflow... (it takes endless seconts until the memory controller has allocated the 96GB of ram... especially when sobody ist wating for you
- you know that)
I do own a Alpine Ridge Card, and I use it without Problems on my cMP 4.1->5.1 as an USB3 Controller. The Card is flashed, I got an working SSDT forme a "macuser"...
The reboot "problem" with Thunderbolt3 devices preisists. I have to to a warm boot to use my DSLR with the "BlackMagic Ultra Studio Mini Recorder" The Blackmagic device is recognized in the System Profiler, as TB dev. at first boot, but not working (BM Software could not see it) aufter a worm boot it ist working perfectly. Even the older TB2 version with the Apple TB2<->TB3 adaptor... (the BM Recorder does not have a separate power supply(!))...
Is there anything i can do? Flash an other Firmware, try a different SSDT, change the OpenCore config, etc?!
My Problem is when I get an invitation to an teams call unexpectetly, I have to do a reboot... which is having an impact to my workflow... (it takes endless seconts until the memory controller has allocated the 96GB of ram... especially when sobody ist wating for you
- you know that)
Are you sure? I recall when testing this myself that e.g. NVRAM
boot-args = "-no_compat_check" is required to boot Big Sur outside of OC (e.g. on an MBP where Big Sur can in fact run it outside of OC), but is not required to run it inside of OC. I was under the impression that it is the Apple bootloader specifically which is doing a compat check and showing that 'no entry' screen, whereas the OC bootloader is doing no such check, is starting the OS independently of any Apple bootloader code, and would never show that screen?
Apologies, I double-checked again more carefully, you are right @hwojtek - thanks for setting me straight!
It's been well documented that 11.3 beta's 1 & 2 were fine, but Apple made updates as of beta 3 that persisted in beta's 3/4/5/6/7/8/RC/GM that are not compatible with the 5,1 Mac Pro. We haven't found the direct cause yet, so don't know if there will be a solution. Big Sur 11.2.3 is the last stable OS for the cMP.
Wasn't able to install BS 11.3. Running OC 0.68 with boardid spoofing on cMP 5,1. Software update downloads and starts the install. However, it got stuck for a long time. Restarted and went back to 11.2.3 and reran the update. The install got stuck again. I had to resume the install using a supported Macbook Pro. That completed successfully and booted on cMP.
You will have problems booting about 50% of the time, and you will eventually corrupt the OS to the point it will no longer boot. Best to roll back to 11.2.3 while you still can. This is a PCIe data issue that affects any storage attached to PCIe (NVMe, USB3, Thunderbolt, etc.).
5 is too small of a number, IMHO. With my testing of each beta release, I performed at least 20x-30x reboots (reboot button from the login screen, or power cycle after a fail). It once took me 11x reboots before I got a fail, then I got a lot of fails from that point on. But, most likely will experience at least one fail within the first 5 attempts...
The booting problems are not only related to PCIE devices. As I said it needs to be rebooted 5-10 times for conclusion.
I don't know if this can help but I was also stuck on 11.3 install until I unplug the Inateck USB3 card, after that the installer went smooth until the end of update process. After a couple of reboot, just to be sure everything was OK, I reinstalled the USB3 card and it was recognized again.
My actual PCIe setup is configured as follow:
Slot 4 : Inateck 4004 USB3 card (unplug for 11.3 install)
Slot 3 : 1 Tb NVMe Samsung 970EVO in Kryo M2 enclosure (great to have activity leds onboard...)
Slot 2 : Empty
Slot 1 : Sapphire Radeon RX580 8Gb (factory BIOS, Orinoco framebuffer)
At present I am still on OpenCore 0.6.7 and I have the Innie and GPU acceleration enabled.
My actual PCIe setup is configured as follow:
Slot 4 : Inateck 4004 USB3 card (unplug for 11.3 install)
Slot 3 : 1 Tb NVMe Samsung 970EVO in Kryo M2 enclosure (great to have activity leds onboard...)
Slot 2 : Empty
Slot 1 : Sapphire Radeon RX580 8Gb (factory BIOS, Orinoco framebuffer)
At present I am still on OpenCore 0.6.7 and I have the Innie and GPU acceleration enabled.
I got the mentioned issue, I had to reboot at least 2 times before the update resumed, didn't do any power cycle, first time I got the "🚫", second restart the update resumed (showed the big sur boot screen, it actually looks different if you're still on the gray boot bg), it restarted as part of the update, got stuck again, then it finally booted Big Sur. My issue was actually being caused by a 3rd 4k monitor I had plugged, after unplugging it completely the update finished
Attachments
You are right. Cmd-v shows inconsistent locations of where it hangs. I managed to get the system back up after reseting NVRAM and SMC, and re-blessing OC. I am not going to restart unless I have to. Hoping this problem will be figured out with the next oc release.
I never updated Big Sur to 11.2.3, I'm still at 11.1, where can I download the latest updated (except 11.3 since there are issues)?
OpenCore on the Mac Pro
BTW - avoid Big Sur 11.3 (soon to be released). Both 11.3 and 11.4 beta versions are currently not working on cMP, and very likely the final 11.3 release won't work either on cMP. But don't despair! The cMP gurus of this sub-forum are hard at work to fix that and more! 😀 Big Sur 11.2.3 works...
forums.macrumors.com
So, what I understand as a user, I shouldn't try to update from BS 11.2.3 to 11.3 considering I boot from my NVMe in a PCIe adaptor.
OPTIONS:
1.- I Stay in 11.2.3 and wait for a Opencore update (considering that new features in 11.3 are not important, in my case).
2.- Change My Booting Opencore disk to a SATA bay cloning my NVMe with Opencore and BS to a SSD, because there are not SATA to NVMe adaptors in the market (¿?)
In case I decide option 2: Could I use my NVMe (with PCIe adaptor) as a data hard disk with no problems in BS 11.3 (and in the very close future 11.4 and so on) or My NVMe from PCIe won´t work even without a OS?
If I am not wrong, most of the focus with regard to the issues that arose with 11.3 and the installation thereof on cMPs, has been on changes in PCI. Well, since PCI is inherently connected to processor architecture, could it be that the incompatibility lies within our out-of-date processors?
Unlikely since the cMP3,1 does not appear to have these issues despite having an even older processor.
I m trying to install a fresh Full Big Sur 11.3 on a HDD SATA in the bay of my Mac Pro with Big Sur installer under Mojave and Opencore 068 it seems to be ok the process is in progress (I have unplug all PCI EXPRESS CARDS and SSD SATA in bay )
I don't think this is the underlying issue. Regardless where you place your bootloader, you will have issues with PCIe/NVMe disks, please correct me if I'm wrong. I'm one of very few who don't have issues, see #300.
Last edited: