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.
I didn't finish the install and kept getting kernel panics trying to get the kexts to work. I'm on stuck on the step of Enabling Hardware Acceleration so I thought a new install from the beginning might provide better results.
For what it's worth, I've just upgraded to OC 0.6.2 by replacing the OpenCore binaries themselves plus the Lilu, WhateverGreen and AppleALC kexts, without altering my config.plist in the least and everything just works. My previous installed version was OC 0.6.1.
 
For what it's worth, I've just upgraded to OC 0.6.2 by replacing the OpenCore binaries themselves plus the Lilu, WhateverGreen and AppleALC kexts, without altering my config.plist in the least and everything just works. My previous installed version was OC 0.6.1.
It can work usually, but not properly.

Your config now miss some items, and OC apply the fail safe settings to them automatically. Also, some items aren't exist anymore, just luckily OC able to ignore them.

In some cases, the same item may have different meaning in the newer OC, this can cause more serious issue.

If you use your own config, you should at least study the "differences" document, and mod your config accordingly.
 
It can work usually, but not properly.

Your config now miss some items, and OC apply the fail safe settings to them automatically. Also, some items aren't exist anymore, just luckily OC able to ignore them.

In some cases, the same item may have different meaning in the newer OC, this can cause more serious issue.

If you use your own config, you should at least study the "differences" document, and mod your config accordingly.
Thanks. I'll look into it and see if I can make some improvements, although I don't see how I'll verify the situation is any better, since it's already working well.
 
Last edited:
It can work usually, but not properly.

Your config now miss some items, and OC apply the fail safe settings to them automatically. Also, some items aren't exist anymore, just luckily OC able to ignore them.

In some cases, the same item may have different meaning in the newer OC, this can cause more serious issue.

If you use your own config, you should at least study the "differences" document, and mod your config accordingly.

We are still not getting HWACLL working with OC6.2 correct?
 
For what it's worth, I've just upgraded to OC 0.6.2 by replacing the OpenCore binaries themselves plus the Lilu, WhateverGreen and AppleALC kexts, without altering my config.plist in the least and everything just works. My previous installed version was OC 0.6.1.
Hello did you try to see if you have full acceleration with VideoProc? Just curious, when I see you said everything works. Thank you.
 
Hello did you try to see if you have full acceleration with VideoProc? Just curious, when I see you said everything works. Thank you.
My GPU is a humble AMD Radeon HD 7970 3 GB. There's nothing to accelerate there. I've ordered an RX 580 which should arrive some time next week. We'll see then.
 
  • Like
Reactions: 205Maxi
We are still not getting HWACLL working with OC6.2 correct?
HWAccel works fine in 0.6.2
screenshot-2020-10-06-at-00-52-54-png.963185
 
  • Like
Reactions: 205Maxi
I'm still running 0.5.7 and everything has been working great (h/w acceleration, internal pcie SSD, TB3, etc.) - is there any benefit to upgrading to 0.6.2? and is config.plist in initial post updated for 0.6.2 in case I want to use it as a reference?

Thanks.


No need to uninstall when updating. If you already have OpenCore working, just carefully replace the files on the EFI volume and reboot.
 
Luckily it seems replacing the config file and switching to OpenCore 0.6.2 worked. I couldn't find the ZIP file for OcBinaryData am I at the wrong page?
Screen Shot 2020-10-06 at 3.46.34 PM.png
 
Last edited:
Here's what I get on Big Sur Beta 9.

View attachment 963668
Same here .. I was told it is a bug that was mistakenly introduced. But if that was the case then it would be the same for the entire line of product \s running that same beta 9 no? Since I have upgrade to beta 9 I do not have that HWACCL anymore..
 
The guide has been updated to OpenCore version 0.6.2.
@cdf OC 0.6.2 changed the directory structure inside, I don't see any reference to X64 directory into guide? This is how I fixed tree.py on line 92:

I updated the plist generator to 0.6.2, see configuration changes.
 
Last edited:
What causes this error when I run my version on terminal.

nvram: Error getting variable - '4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:eek:pencore-version': (iokit/common) data was not found

I can't seem to get open core to work on my MP 5,1
 
What causes this error when I run my version on terminal.

nvram: Error getting variable - '4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:eek:pencore-version': (iokit/common) data was not found

I can't seem to get open core to work on my MP 5,1
Did you follow the instructions on the first page? They are pretty self explanatory.
 
  • Like
Reactions: 6DecadesLater
Was talking under macOS Big Sur...

It worked for me on a 6c Mac Pro 5.1 that I sold now. I think it was on beta 6 or 7 when I sold it.
Sorry, should have done a screenshot. It had a Vega RX 64
I am using the stock config from h9826790
Only removed the entry for the multi cpu in that specific mac pro.

Not upgrading my 12c MP4.1 with the RX5700 XT just yet. Big Sur is too unstable for my daily work.
 
Same here .. I was told it is a bug that was mistakenly introduced. But if that was the case then it would be the same for the entire line of product \s running that same beta 9 no? Since I have upgrade to beta 9 I do not have that HWACCL anymore..
the same, now it's waiting for the new update ...
 
  • Like
Reactions: 205Maxi
Sorry I'm a newbie, not understanding what you mean by "fit your own number into that position."

Do you mean I should use a disk that I see on my terminal ?

You are skipping part of the instructions: Use diskutil list to find the value for A. Note that this step should always be carried out, because the actual value may change from one boot to the next.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.