Sidebar Sidebar
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

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.
RicheeThree said:
I think I can do that, but I just want to make sure I have it straight, since the only way I can boot natively into Mojave is to remove all other drives from the system:
  1. Remove all other drives except Mojave from the machine
  2. Boot to Mojave
  3. Restart the machine and hold Command + Option + P + R > let Mojave boot
  4. Shut down the machine
  5. Insert Big Sur/OC drive
  6. Boot to recovery mode (or can I boot to Mojave again to bless the other drive?)
  7. Bless the EFI partition on the Big Sur drive
Click to expand...
See "Disabling OpenCore" and "Re-enabling OpenCore" in Part 3 of the guide. In recovery, before blessing OC, you can clear the NVRAM by entering nvram -c in terminal.
 
  • Like
Reactions: MacForumsUser
sfalatko said:
@cdf - take a look at my config.plist and screenshot. I'm using the config.plist from the first post with spoofing of the BoardID to enable continuity and updates (worked for 11.2.1 and 11.2.2) and VMM off - my processor is "Unknown"
Click to expand...
Thanks for the info. If you could open an issue on the Acidanthera bugtracker with the output of sysctl machdep.cpu and dmidecode that would be great. Reports like this will hopefully get all processors compatible with the classic Mac Pro to be detected automatically by OpenCore. In the interim, you can always manually set ProcessorType (see the cpu list).
 
nocomprendo said:
Hey. I'm on the same situation. Big Sur, no wifi... And wondering if it would work with Martin Lo's OC package.
Did you find a way to do this?
Click to expand...
Yes, I installed OC via MyBootMgr which also included all necessary kexts for legacy WiFi, BT, and audio. All of it works perfectly with my cMP5,1 and Big Sur.
 
  • Like
Reactions: Dayo and nocomprendo
I have a Mac Pro 2009（from 4,1 to 5,1）with my cpu Upgrade to Xeon W3690，GPU is RX 590，BOOTROM 144.0.0.0.0

when I install big sur，it allway get into bootloop，I have try micropatch and opencore。
At last I find this：

panic(cpu 0 caller 0xffffff800ae9092c): Sleep transition timed out after 180 seconds while entering darkwake on way to sleep. Suspected bundle: com.apple.iokit.IOUSBHostFamily. Thread 0x70fc.
Failure code:: 0xcb3cb8ca 00000031

Backtracing panicked thread because kernel_stack is NULL for specified thread
Backtrace (CPU 0), Frame : Return Address
0xffffff83b8193930 : 0xffffff800a71a65d
0xffffff83b8193980 : 0xffffff800a854a75
0xffffff83b81939c0 : 0xffffff800a8465fe
0xffffff83b8193a10 : 0xffffff800a6c0a40
0xffffff83b8193a30 : 0xffffff800a719d27
0xffffff83b8193b30 : 0xffffff800a71a117
0xffffff83b8193b80 : 0xffffff800aec1b6c
0xffffff83b8193bf0 : 0xffffff800ae9092c
0xffffff83b8193ea0 : 0xffffff800ae1343a
0xffffff83b8193ec0 : 0xffffff800a75c605
0xffffff83b8193f40 : 0xffffff800a75c131
0xffffff83b8193fa0 : 0xffffff800a6c013e

BSD process name corresponding to current thread: kernel_task
Boot args: -no_compat_check amfi_allow_any_signature=1

Mac OS version:
19H2

Kernel version:
Darwin Kernel Version 19.6.0: Mon Aug 31 22:12:52 PDT 2020; root:xnu-6153.141.2~1/RELEASE_X86_64
Kernel UUID: 05D51A3D-3A87-3FF0-98C3-9CF3827A3EDD
Kernel slide: 0x000000000a400000
Kernel text base: 0xffffff800a600000
__HIB text base: 0xffffff800a500000
System model name: MacPro5,1 (Mac-F221BEC8)
System shutdown begun: NO
Panic diags file available: YES (0x0)
 

Attachments

  • opencore-2021-02-25-160434.txt
    256 KB · Views: 81
Last edited:
sfalatko said:
It is not set so it is the failsafe 0.
Click to expand...
Not setting a key is not the same thing as setting the failsafe.
Explicitly specify the failsafe value to set it and see if that works.
 
Last edited:
Dayo said:
Not setting a key is not the same thing as setting the failsafe.
Explicitly specify the failsafe value to set it and see if that works.
Click to expand...
That sounds somewhat unlikely to me. Can you give us at least one example? For instance, if <key>Example</key> is an integer and its failsafe value is 1, what would OpenCore suppose its value to be if I don't include said key anywhere in my config.plist? 0?
 
PeterHolbrook said:
what would OpenCore suppose its value to be if I don't include said key anywhere in my config.plist?
Click to expand...
It can literally be anything.
Search for "Undefined Behaviour" in the OpenCore Manual ... It's somewhere near the beginning.

According to the OC Developer, missing keys fall into this category: https://github.com/acidanthera/bugtracker/issues/1122#issuecomment-680938158. This is mentioned somewhere in the manual as well.

I believe the upcoming config updates here will sort this out though.
 
Last edited:
  • Like
Reactions: PeterHolbrook
I don't know why would you attach this file, but perhaps you should have a look into what your log shows as a possible culprit:
Viki Yi said:
panic(cpu 0 caller 0xffffff800ae9092c): Sleep transition timed out after 180 seconds while entering darkwake on way to sleep. Suspected bundle: com.apple.iokit.IOUSBHostFamily. Thread 0x70fc.
Failure code:: 0xcb3cb8ca 00000031
Click to expand...

What are your connected USB devices? Any 3rd party USB card?
 
@cdf I got the 11.2.2 update this morning with VMM off by checking manually, but interestingly, I did not get an alert new software is released?

1614357997229.png
 
TECK said:
@cdf I got the 11.2.2 update this morning with VMM off by checking manually, but interestingly, I did not get an alert new software is released?

View attachment 1735715
Click to expand...
FWIW, with VMM on, the 11.2.2 update wasn't found. Installed it last night with VMM off with hybridization (iMac spoof). I did not change BIOSVersion to 9999.0.0.0.0 before doing it though (which was a bit of a risk) but it worked nonetheless.

Additionally, upon first reboot after initiating the 11.2.2 installer, the installer volume name was no longer called 'Mac OS Installer' or something to that effect, but rather 'Macintosh HD' which caused a bit of concern. Selecting it however allowed installation to continue. I was able to verify with others in the Big Sur unsupported Mac thread (https://forums.macrumors.com/thread....2242172/page-363?post=29638972#post-29638972) that this new naming scheme for the installer volume is indeed accurate and exists even in the 11.3 beta distro.

And no, I didn't get the notification either. Only found out about 11.2.2 update via another forum member.
 
I got the alert (VMM off) .... but for understanding...
what are the roles of VMM, hybridization and BIOSVersion in regard of updates and update safety?
(with 0.66 BigSur)

I kinda lost track of this since the update to BigSur
(is the part about VMM in #1 still valid here?)
 
zzzachi said:
I got the alert (VMM off) .... but for understanding...
what are the roles of VMM, hybridization and BIOSVersion in regard of updates and update safety?
(with 0.66 BigSur)

I kinda lost track of this since the update to BigSur
(is the part about VMM in #1 still valid here?)
Click to expand...
Based on my understanding from CDF's explanation here: https://forums.macrumors.com/threads/opencore-on-the-mac-pro.2207814/post-29636214

Hybridization occurs when using OC to spoof BoardProduct. Use BIOSVersion set to 9999.0.0.0.0 in addition to BoardProduct spoofing to ensure BS installs/updates can't update firmware. VMM is no longer needed with hybridization. HTH.

For context (cuz I asked the same question the other day): https://forums.macrumors.com/threads/opencore-on-the-mac-pro.2207814/post-29636056
 
Last edited:
  • Like
Reactions: zzzachi
Hey Guys. Can I get some help please. I have a MBP 2012 which is running BigSur 11.0 with the micro patcher. I have BS 11.2 installed on an external drive and tried booting from that drive to see if it works and it boots up. I also have Open Core( the untouched basic EFI Folder and config.plist) in there. I am trying to get my MBP to boot from OC so that I can do the updates normally.
 
Surenmunoo said:
Hey Guys. Can I get some help please. I have a MBP 2012 which is running BigSur 11.0 with the micro patcher. I have BS 11.2 installed on an external drive and tried booting from that drive to see if it works and it boots up. I also have Open Core( the untouched basic EFI Folder and config.plist) in there. I am trying to get my MBP to boot from OC so that I can do the updates normally.
Click to expand...
I think you really need to study the first message of this thread. Rightly configured, OpenCore will let you install and run Big Sur if your unsupported Mac has the right setup (like a Metal GPU, sufficient RAM, et cetera), but I don't know how it will behave if your Big Sur installation has been compromised by using third-party procedures, such as the so-called "micro patcher". In case you do manage to boot your current non-pristine Big Sur through OpenCore, perhaps you should download the latest untouched full installer of Big Sur 11.2.2 and then install that on top of your current Big Sur installation. Hopefully, that will get rid of your current patched, unsealed Big Sur and generate the correct, sealed APFS structure where an untouched system will behave as intended.
 
PeterHolbrook said:
I think you really need to study the first message of this thread. Rightly configured, OpenCore will let you install and run Big Sur if your unsupported Mac has the right setup (like a Metal GPU, sufficient RAM, et cetera), but I don't know how it will behave if your Big Sur installation has been compromised by using third-party procedures, such as the so-called "micro patcher". In case you do manage to boot your current non-pristine Big Sur through OpenCore, perhaps you should download the latest untouched full installer of Big Sur 11.2.2 and then install that on top of your current Big Sur installation. Hopefully, that will get rid of your current patched, unsealed Big Sur and generate the correct, sealed APFS structure where an untouched system will behave as intended.
Click to expand...
I read the 1st post numerous times and managed to get the MBP to boot from OC but lost the ability to get the wifi working. I had to revert back to the micro patcher and have BS reinstalled but would like it to work with OC. I tried numerous kexts to get the wifi up but eventually failed with it. any help with that will be appreciated or maybe a working config.plist will help
 
Surenmunoo said:
I read the 1st post numerous times and managed to get the MBP to boot from OC but lost the ability to get the wifi working. I had to revert back to the micro patcher and have BS reinstalled but would like it to work with OC. I tried numerous kexts to get the wifi up but eventually failed with it. any help with that will be appreciated or maybe a working config.plist will help
Click to expand...
 
  • Like
Reactions: Surenmunoo and Dayo
cdf said:
Thanks for the info. If you could open an issue on the Acidanthera bugtracker with the output of sysctl machdep.cpu and dmidecode that would be great. Reports like this will hopefully get all processors compatible with the classic Mac Pro to be detected automatically by OpenCore. In the interim, you can always manually set ProcessorType (see the cpu list).
Click to expand...
@cdf - issue posted on the bugtracker.
 
  • Like
Reactions: cdf
sfalatko said:
@cdf - issue posted on the bugtracker.
Click to expand...
Thanks! I suspected that you had a W3690 because the X5690 does get detected properly.

Note: Acidanthera may point out that the config is invalid (not passing ocvalidate); however, this is a specification vs implementation thing. Although it makes no difference functionally, the next update to the sample config here will adhere to the specification.
 
  • Like
Reactions: Dayo
Surenmunoo said:
I read the 1st post numerous times and managed to get the MBP to boot from OC but lost the ability to get the wifi working. I had to revert back to the micro patcher and have BS reinstalled but would like it to work with OC. I tried numerous kexts to get the wifi up but eventually failed with it. any help with that will be appreciated or maybe a working config.plist will help
Click to expand...
Did you use the a generic config file? I really would like to have the skills to generate a valid one for my Macbook Pro 17" 2011. I tried this page but simply, is beyond my skills.

 
  • Like
Reactions: innovaTutor
startergo said:
Try this:
github.com

GitHub - dortania/OpenCore-Legacy-Patcher: Experience macOS just like before

Experience macOS just like before. Contribute to dortania/OpenCore-Legacy-Patcher development by creating an account on GitHub.
github.com github.com
Click to expand...
Thank you so much. Looking in the web also I found this.

mackie100projects.altervista.org

Download OpenCore Configurator 2.77.1.0 | mackie100 projects

OpenCore Configurator will help you to fully configure your OpenCore bootloader.
mackie100projects.altervista.org mackie100projects.altervista.org

Do you know it?
 
******* said:
Did you use the a generic config file? I really would like to have the skills to generate a valid one for my Macbook Pro 17" 2011. I tried this page but simply, is beyond my skills.

Click to expand...
I use OC on my Asus Hackintosh so have a small idea on how to create the config. I tweaked the generic file bit to get the MBP to boot and the only thing left was wifi which @startergo gave the link for now- thank you @startergo
 
  • Like
Reactions: 0134168
  • Like
Reactions: 0134168
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back