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.
Sorry I'm a newbie, not understanding what you mean by "fit your own number into that position."
You do realise that Terminal has the power to do a lot of harm to your OS if you type a command with a typo? Maybe start by watching some videos about Terminal 101
 
Thanks for helping me so far. Just one more thing. I have managed to bless and it didn’t give me any errors. I just see any errors SMC. I have the following error when trying to see the open core version.
image.jpg
 
Thanks for helping me so far. Just one more thing. I have managed to bless and it didn’t give me any errors. I just see any errors SMC. I have the following error when trying to see the open core version.
View attachment 964575
remove versionnvram and leave only nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:eek:pencore-version
 
@Mogale use this:


Code:
nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version

Copy and past that code into terminal.
 
Thanks for helping me so far. Just one more thing. I have managed to bless and it didn’t give me any errors. I just see any errors SMC. I have the following error when trying to see the open core version.
View attachment 964575
No offence, but since you can't quite follow the procedures. May I suggest you to halt at here.

May I know what's your reason to install OpenCore?

OpenCore is quite advance, and if you use it to run non natively supported OS. You may stuck at no boot condition if you keep making this kind of low level mistake.

I wish you only proceed if you can really follow the steps in post #1.

cdf makes everything very clear in post #1. All you need to do is just comprehend them, then follow the exact steps.

However, you failed to follow the step to get your disk ID in terminal.

And you failed to copy and paste a terminal command which is boxed.

This is a sign that you may make much more serious mistake if you continue.

Again, no offence, but you really should take a break, and think twice if you really want to continue.
 
Last edited:
No offence, but since you can't quite follow the procedures. May I suggest you to halt at here.

May I know what's your reason to install OpenCore?

OpenCore is quite advance, and if you use it to run non natively supported OS. You may stuck at no boot condition if you keep making this kind of low level mistake.

I wish you only proceed if you can really follow the steps in post #1.

cdf makes everything very clear in post #1. All you need to do is just comprehend them, then follow the exact steps.

However, you failed to follow the step to get your disk ID in terminal.

And you failed to copy and paste a terminal command which is boxed.

This is a sign that you may make much more serious mistake if you continue.

Again, no offence, but you really should take a break, and think twice if you really want to continue.

Thanks for the advice. Although I followed all the steps except step 1 because I already have catalina in disk01.
The main reason to install OC is to have my disk 01 the main as it still mounting as external.
 
Thanks for the advice. Although I followed all the steps except step 1 because I already have catalina in disk01.
The main reason to install OC is to have my disk 01 the main as it still mounting as external.
If it's already working for you, you better keep your current config.

For me, it looks like that you don't have enough knowledge to "jump steps" yet.

And you are trying to mod the procedures to make your existing Catalina boot via OpenCore.

Of course, you can do that, however, I must warn you that there is a high chance you will stuck at no boot condition (e.g. OpenCore isn't loaded, and your cMP can't boot the Catalina natively).

Please only proceed if you accept this risk, and know your recovery plan.

For "installing OpenCore with existing Catalina", you may consider to use my package. As long as SIP is disabled. All you need to do it just put the EFI folder into position, and run the bless tool.

 
@h9826790 sorry but i am not quite sure where and if I'm missing something.

If I set in the config.plist UpdateSMBIOS "false" I can boot both Catalina and BS beta9 with display port connection from my RX5600xt GFX but I have noticed that I lost HWA acceleration (according to Videoproc) on both the OS.

If I set UpdateSMBIOS to "true" I can boot Catalina with display port connection and have also HWA Acceleration but I can't pass the 2nd stage boot BigSur Beta9 and I have to connect the monitor to HDMI connection (with clearly Max resolution problem since I have a QuadHD capable display).

Attached config.plist

I don't remember to had these problems with the "old" rx590 gfx that I had until Big Sur beta2...
is it related to the fact that using hybridisation smbios I lost gfx connections other that HDMI on this specific graphic card?

as always thank you.

cheers
 

Attachments

  • config.plist.zip
    3 KB · Views: 74
@h9826790 sorry but i am not quite sure where and if I'm missing something.

If I set in the config.plist UpdateSMBIOS "false" I can boot both Catalina and BS beta9 with display port connection from my RX5600xt GFX but I have noticed that I lost HWA acceleration (according to Videoproc) on both the OS.

If I set UpdateSMBIOS to "true" I can boot Catalina with display port connection and have also HWA Acceleration but I can't pass the 2nd stage boot BigSur Beta9 and I have to connect the monitor to HDMI connection (with clearly Max resolution problem since I have a QuadHD capable display).

Attached config.plist

I don't remember to had these problems with the "old" rx590 gfx that I had until Big Sur beta2...
is it related to the fact that using hybridisation smbios I lost gfx connections other that HDMI on this specific graphic card?

as always thank you.

cheers
Are you using AGDPmod=Pikera?
 
Hello @vit9696 , sometimes when I rebuild a new kernelcollection (kmutil install --update-all ; kcditto) with patched kext, from opencore selecting the "BigSur Preboot" I get "exiting efiboot" with no boot neither single user mode (as if the BootKernelExtensions.kc is refused from opencore), while with the same BKE modified kernelcollection I can boot from apple startup manager or refind (without opencore) either with CMD+S and exit and normal booting.

Which main kernelcollection path opencore loads ?

/Volumes/Preboot/UUIDBigSur/boot/System/Library/KernelCollections/BootKernelExtensions.kc

only this or others too?

Then I have another question, would be possible to implement a kext injection (maybe on next opencore version) on these paths:

/Volumes/BigSurLabel/System/Library/KernelCollections/BootKernelExtensions.kc
/Volumes/BigSurLabel/System/Library/KernelCollections/SystemKernelExtensions.kc

I don't know how to extract the BootKernelExtensions.kc but I guess it contains the kernel and main kext required to make the "kernel cache".
 
Last edited:
One question, I have gotten ( donated ) 128 GB of DDR3 4x32GB organized in 1-3 - 5-7 pattern put it in the MacPro the machine chimes, no red light I get the boot screen, I can choose the disk to boot on, logo shows up, but no progress bar. apple logo stays on as long as it wants. ;)

Do I need to turn something on in the config.plist?

Thank you,
 
One question, I have gotten ( donated ) 128 GB of DDR3 4x32GB organized in 1-3 - 5-7 pattern put it in the MacPro the machine chimes, no red light I get the boot screen, I can choose the disk to boot on, logo shows up, but no progress bar. apple logo stays on as long as it wants. ;)

Do I need to turn something on in the config.plist?

Thank you,
I don't think the cMPs can use 32 GB
DIMMs
 
I'm trying to enable the graphical boot picker but can't find the ZIP. The link brings me to this page. Where can I find the the OcBinaryData ZIP to download?
Screen Shot 2020-10-09 at 4.39.37 PM.png
 
I'm trying to enable the graphical boot picker but can't find the ZIP. The link brings me to this page. Where can I find the the OcBinaryData ZIP to download?

Just click on the green button “code” then choose “download zip “ or something very similar

This is now clarified in the guide.
 
Last edited:
  • Like
Reactions: tomed and Stefano85
I don't think the cMPs can use 32 GB
DIMMs
It does actually, if you get 32GB module DDR3 LRDIMM it will work, I wanted to know if there was something that I could potentially turn on in the config.plist so that mine that was given to me for free ;) could be recognized. The machine boots but hang on the Apple logo...

I may by the LRDIMM instead the one I got was RDIMM only .. :(
 
This is now clarified in the guide.
IMO, might be useful to use the git clone command into guide, it will save a lot of confusion. Instead of downloading extracting etc. use one command to clone a specific OC tag (0.6.2 for example) and pull the same way the OCData. People will be able to copy/paste the 3 commands to assemble the directory easy. You saw how I do it into my plist generator. :)
 
The AppleMCEReporterDisabler.kext is in the kexts folder along with the other two kext files.

The path also seemed to match what I found.

Did you end up figuring this out? I'm not sure this is working on my machine either. Kextstat is showing com.apple.driver.AppleIntelMCEReporter listed. Not sure if this should or should not be there if AppleMCEReporterDisabler.kext is loaded and doing what it should be at startup? Can anyone clarify? Running Catalina 10.15.7.

cMP 5,1 dual X5690
 
Howdy folks! I really appreciate this thorough, well maintained, and detailed thread. The install process was effortless. I've been having a lot more kernel panics on my 12 core machine than I ought to be. Hoping for some suggestions for what to do next.

I have two Mac Pro 5,1 (one 6Core/64GB one 12Core/96GB, all x5690, both using PCIe NVMe boot) running Catalina via OpenCore 0.6.0. I updated both to OC 0.6.0 and 10.15.6 supplemental on the 16th of August and was on 0.5.9 and 10.15.5 and .6 before that.

Both are using the standard config from this thread save for the addition of the necessary kexts to enable graphical boot screen and hardware acceleration and the config tweaks required. The 12 core machine also has the kext and config tweak for AppleMCEReporterDisabler. I updated these kexts when I updated OC to 0.6.0

Both machines are crunching Handbrake jobs round the clock and using the latest release. Both have more kernel panics than I think they should, but the 12 core WAY more. Configs attached to this post - they pass the command line checker and I have no boot problems. I do not believe this to be a Catalina/Handbrake combination problem as I'm also crunching Handbrake round the clock on a 10 core 6,1 and do not get any panics.

The 6 core machine is far more stable - I started tracking panics at the end of July and it only had panics on 25JUL and 18AUG, but I had months of uptime on Mojave that was only interrupted by my installing patches.

The 12 core has panics every few days. It's really annoying when it happens right after bed because then it's just chillin' all night not doing any work. 05AUG, 12AUG, 14AUG, 15AUG, 21AUG, 23AUG, 26AUG (no more free PasteBin, but this one was also the Handbrake process; usb.IOUSBHostHIDDevice last loaded kext, timed out during locked wait on cpu13). I don't really see a pattern emerging here...

Things I've considered/tried:

Northbridge temp issues on the 12 core: Installed MacsFanControl. NB Diode was around 78 at the beginning of AUG (heatwave) but is now staying 70-74 just with default fans. I've added a box fan in front of the computers to help get cool air in and push the hot air out the back of the room. FYI- NB on the 6 core is around 58-60; I've read that you can expect the 12 core to be around 15C hotter.

CPU Temp issues: A runs around 87 on the diode and B around 81. Cooling seems to be adequate for processors constantly running at ~99%

Memory: Installed memtest, got bored after it ran for 12 hours without problems and quit. Starting to swap out modules one at a time with other matching 16GB modules to see if there's any impact. Too soon to tell.

Hardware Test: thought about running this but having trouble finding out how to enter this mode while using OC- DuckDuckGo has been less than helpful in this regard.

Searching key phrases from the panic reports: found lots of irrelevant things for other models, usually with problems at boot or with really random kernel extensions installed for problematic software, especially AV or management suites. My install is pretty much a base install.

Searching this thread: didn't find anything I thought matched my situation when I searched for kernel panic.


Do y'all see anything in the panic reports that's suspicious? Any ideas for things I could try or check? Any search terms I should have used or places I should be reading? I don't mind putting in the work- just need a push in the right direction.

Did you end up finding a solution to this RaoulDuke-Esq? I'm having the same issues since 10.15.6. System would run well for about a month on average between BSDs. Now, I'm not even getting a day of uptime between crashes. Very similar looking crash reports. Any help or suggestions would be much appreciated. My suspicions were parallels up to now. But it's even crashing without it running now.

Kernel Extensions in backtrace:
com.apple.driver.AppleIntelCPUPowerManagement(222.0)[0CDAF741-D451-3432-8313-555EBC9DDE2C]@0xffffff7f9c2cb000->0xffffff7f9c2f4fff

Same as mine and the others are similar as well. Is anyone else experiencing something similar?
 
Last edited:
Did you end up figuring this out? I'm not sure this is working on my machine either. Kextstat is showing com.apple.driver.AppleIntelMCEReporter listed. Not sure if this should or should not be there if AppleMCEReporterDisabler.kext is loaded and doing what it should be at startup? Can anyone clarify? Running Catalina 10.15.7.

cMP 5,1 dual X5690
I replaced my config.plist and OpenCore folder from 0.6.1 to 0.6.2. After that I followed the steps again and everything worked out well. I skipped Step 4 Install Catalina since I already had it installed.
 
Hi There,

First off I wanted to say a Huge Thank You to the OP and everyone involved in this guide and all the magic that allowed me to Install OpenCore and get Catalina on my 5,1. :)

It works and from a complete techno dunce like me being able to follow along and get this done is massive.

I am running into a few small aesthetic issues that if someone has a solution to resolve it would be awesome but if not then its an aesthetic issue so ill just deal with it.

I followed the basic installation parts 1 - 5 to the letter in post #1. and I also Enabled the Graphical Boot Picker in "Part II Advanced Configuration".

When I boot up the Mac the wild and negative colours appear on boot. Much like when I first installed OpenCore. I can make out that the Graphical Boot Picker is working but those pinks and yellows and rainbow spectrum colours don't look the greatest. Once I select the Boot Drive the Black screen with the white apple logo kicks in and everything is fine from there on.

I went and repeated all the Post Install actions again (made sure the changes were correct) I even re enabled some like HiDPI Display, GOP Renderer but reboots with those reverted were still the same.

Could someone let me know if the initial boot screen is supposed to be crazy colours and if not if you have any suggestions on what the issue might be that would be awesome.

End of day though is a small aesthetic issue when I first boot up so if that's just how it is I won't complain.

Awesome Job once again :D

Edit: Attached are photos of the screens I see in order, Ive seen this (Apart from the Graphic Icon of the Boot Drive) on boot up ever since going to Open Core (incase that in itself is unusual). a second after the last photo in the series it goes to the black apple boot screen for a second before logging into Catalina

Boot_1.jpg

Boot_2.jpg

Boot_3.jpg
Boot_4.jpg
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.