Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
That s what i get i think that opencore is guilty
 

Attachments

  • 9029B8FF-E96D-48BF-A567-EF9B73A779CF.jpeg
    9029B8FF-E96D-48BF-A567-EF9B73A779CF.jpeg
    299.3 KB · Views: 249
  • Haha
Reactions: JohnD
That s what i get i think that opencore is guilty
"A prohibitory symbol, which looks like a circle with a line or slash through it, means that your startup disk contains a Mac operating system, but it's not a version or build of macOS that your Mac can use. "
 
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.
I don't have neither PCIe nor NVMe and I got the issue.
 
I may or may be wrong but in my case, my keyboard has a usb hub where I connect a tablet and a camera, I kept getting 🚫 on boot until I unplugged those two usb devices
 
Glad I checked in here before the end of day....
Wanted to run this past everyone to see if there is anything additional I need to be aware of and/or take action on?

BTW: I am on opencore v6.7 right now. Been running stable since I upgraded to BS and reflashed my unbooted bootrom. I also dual boot (per signature) to BS on PCIe NVMe and Windows10 on PCIe NVMe.... both of these are living on a dual slot card.


my cMP is telling me it's gonna reboot for updates later today
1619559424150.png


Unchecked the Auto update box (above screenshot)
Then clicked "Turn Off Automatic Updates", entered password prompt
1619559452720.png


When I click the Advanced it shows these options
(I unchecked the "Install system data files and security updates")
1619559487090.png


That puts me at this screen:
Notice it no longer says it will update/reboot later tonight.
1619559554658.png
 
I managed to successfully toast my Mac 5,1 yesterday afternoon :eek:. Interestingly all attempts to reinstall over my trashed boot drive were thwarted with my 'incompatible' version of Mac OS. I did test the upgrade out on another Mojave installation and experienced the same crossed circle message though I was able to downgrade this back to Mojave so the 'incompatibility' issue may be related to my multiple attempts at recovering the system. Mojave kindly enabled SIP adding to the recovery process with a GPU swap for the necessary Mac EFI support.

The good news is I have my home directory located on a separate drive to avoid such eventualities and Time Machine enabled which I used to recover my apps and config using the migration assistant tool after booting a fresh copy of 11.2.3 I was able to thankfully locate and download.

Needless to say automatic updates have now been disabled.
 
I just installed OpenCore and upgraded from Mojave to Big Sur 11.2.3, and now it no longer recognizes my iOS devices (iPhone 12 Pro and iPad Pro) to sync (not listed under "Locations" in Sidebar). I'm using two different third-party Lightning cables which works fine under Mojave, and on my 2015 MBP "natively" running Big Sur.

All other USB devices and drives work and mount just fine, so this is specific to iOS.

Is anyone else experiencing this issue?
 
I managed to successfully toast my Mac 5,1 yesterday afternoon :eek:. Interestingly all attempts to reinstall over my trashed boot drive were thwarted with my 'incompatible' version of Mac OS. I did test the upgrade out on another Mojave installation and experienced the same crossed circle message though I was able to downgrade this back to Mojave so the 'incompatibility' issue may be related to my multiple attempts at recovering the system. Mojave kindly enabled SIP adding to the recovery process with a GPU swap for the necessary Mac EFI support.

The good news is I have my home directory located on a separate drive to avoid such eventualities and Time Machine enabled which I used to recover my apps and config using the migration assistant tool after booting a fresh copy of 11.2.3 I was able to thankfully locate and download.

Needless to say automatic updates have now been disabled.
I can't recall exactly, but you may need to re-enable the `VMM` flag for installation.
 
Hey Folks,

Before I go back to the Apple Store and buy a 2019 I thought I would ask if anyone has gotten OpenCore to work on a flashed to 5,1 2009 Cheesegrater with Nehalem dual CPU.

Thanks,
Robert
 
Not so. VMM is required for Catalina software updates and dual Nehalem Xeon have stuttering audio after 10.14.3.
I did read about that with Mojave, but did not know if it applied to Catalina and Big Sur.

Decided not to spend the money on Westmere's and to order a refurb 7,1 from Apple. May do the Westmere's at some point as Max3(my Cheesegrater) is on old friend at this point. He has a 1080Ti, SSD boot drive, and 8TB RAID 0. Hopefully my RAID card will run in the new one. Awaiting Areca to tell me it will.

Thanks for all the answers,
Robert
 
  • Like
Reactions: hwojtek
So what's the verdict regarding updating to Big Sur 11.3 for a 2012 5,1 Mac Pro with OpenCore 0.6.8?
 
MacPro boot rom was automatically change to open core version 9144.0.6.8.0 ,is this will create any issue for the feature use, reset Nvram also shows same result.
bootrom opencore.jpeg
 
MacPro boot rom was automatically change to open core version 9144.0.6.8.0 ,is this will create any issue for the feature use, reset Nvram also shows same result.
This is the intended version number set by Martin's package. Part 2 of the guide explains how to set this value. You want a high version number to prevent unwanted firmware updates.

Note that resetting the NVRAM without properly reblessing OpenCore is problematic. There are several comments about this in the last few pages of this thread.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.