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.

Bmju

macrumors 6502a
Dec 16, 2013
702
768
It was working fine in high sierra i.e. before I upgraded to Big Sur using OCLP. This is why I suspect that there must be a setting in opencore that is causing this.
Hmm. Starting to wonder whether this is a misconfiguration in your OpenCore, after all. Maybe this? (You might be able to search your config.plist file for the incorrect setting, rather than searching the entire IO Registry.)
 
  • Like
Reactions: TimothyR734

smartin80

macrumors member
Jun 5, 2020
40
23
Newb here...:)

I'm in the middle of trying to clean up the mess I made of my Opencore Lecacy Patcher upgrade from Catalina to Big Sur...

This is my setup:
Mac Pro Late 2010, 5,1, 6 core, 3.33mhz (?)
Samsung 860 Evo SSD as my boot drive
Radeon RX 580 sapphire graphics card

This box has been running Catalina very happily for a long while, curtesy of Dosdude's patcher but as I'm a few security updates behind, I figured it would be just as easy to jump to an OCLP install of Big Sur...

Not so...! :)

The Radeon card has never shown the Boot picker. This hasn't been an issue for me.

I built OCLP with the Radeon installed in the hope that the Boot picker might appear, as indicated by this post <https://forums.macrumors.com/thread...efi-for-rx580-reference.2286955/post-29656023>

The Boot picker did not appear so I reinstalled the stock graphics card which did allow me to choose the EFI disk from OCLP. The installation took me to the regular Big Sur installation screen but things started looping with endles restarts and I eventually pulled the plug and am now in the painful process of restoring from my CCC backup, which is taking forever ...

Was my mistake to not rebuild OCLP with the stock graphics card installed?

Is there any other reason why my install process should bork so badly?

Will I really see a Boot picker when using the Radeon RX 580 once I have found a way to complete this install...?

Thanks for your patience!

(PS... I did a practice run on my old Macbook which was running High Sierra and that went ok. No real issues.)

S
 
  • Like
Reactions: TimothyR734

Ausdauersportler

macrumors 603
Nov 25, 2019
5,007
5,826
Newb here...:)

I'm in the middle of trying to clean up the mess I made of my Opencore Lecacy Patcher upgrade from Catalina to Big Sur...

This is my setup:
Mac Pro Late 2010, 5,1, 6 core, 3.33mhz (?)
Samsung 860 Evo SSD as my boot drive
Radeon RX 580 sapphire graphics card

This box has been running Catalina very happily for a long while, curtesy of Dosdude's patcher but as I'm a few security updates behind, I figured it would be just as easy to jump to an OCLP install of Big Sur...

Not so...! :)

The Radeon card has never shown the Boot picker. This hasn't been an issue for me.

I built OCLP with the Radeon installed in the hope that the Boot picker might appear, as indicated by this post <https://forums.macrumors.com/thread...efi-for-rx580-reference.2286955/post-29656023>

The Boot picker did not appear so I reinstalled the stock graphics card which did allow me to choose the EFI disk from OCLP. The installation took me to the regular Big Sur installation screen but things started looping with endles restarts and I eventually pulled the plug and am now in the painful process of restoring from my CCC backup, which is taking forever ...

Was my mistake to not rebuild OCLP with the stock graphics card installed?

Is there any other reason why my install process should bork so badly?

Will I really see a Boot picker when using the Radeon RX 580 once I have found a way to complete this install...?

Thanks for your patience!

(PS... I did a practice run on my old Macbook which was running High Sierra and that went ok. No real issues.)

S
Your main mistake was trying an upgrade instead of a doing clean new installation. You need to have the RX580 installed when running OCLP because if analyses the hardware and creates a fitting tailored configuration. Any changes of the hardware later on may render the system unbootable. So if you change hardware rerun OCLP and reinstall OpenCore, again. Most importantly format your target disk using the Monterey disk utility from the installer/recovery dialogue.

Your best starting point would be Mojave (supported macOS on your system) to run OCLP and honestly the patcher you had with Catalina was the worst choice you could have made. It does not support your fancy GPU, does not enable video toolbox acceleration and the worst of all, it patches most likely the macOS Catalina, a thing we try to avoid at all cost with a modular system using OpenCore.

The GPU should have a GOP BIOS installed, search the web for details. Without GOP no OpenCore boot picker at all. You will like the OpenCore boot picker.

Do not install both graphics cards, will not work.

On Macrumors there are at least three different threads (including this one) describing in great detail how to manage OpenCore on your MacPro5,1, do not mix and match, each group likes to stay separated and you may end up with "off topic" replies when asking basic questions. Nevertheless each of this thread is a great resource to information if you are willing to spend your time on reading the first post or the main documentation provided/linked there. It is not so much a help desk.

P.S.:
You could have used Catalina unpatched with OpenCore on your Mac for years...
You may think about updating the (stock) existing BT/WiFi module with a PCI based BCM94360CD to get most features of Big Sur or Monterey running. Like adding a GPU some developments cannot by just patched out of the reality and need hardware changes.
 
Last edited:

smartin80

macrumors member
Jun 5, 2020
40
23
Your main mistake was trying an upgrade instead of a doing clean new installation.
That didn't seem to be an option... You mean to format the drive and then do the install...? It might come to that if this try doesn't work...
You need to have the RX580 installed when running OCLP because if analyses the hardware and creates a fitting tailored configuration. Any changes of the hardware later on may render the system unbootable. So if you change hardware rerun OCLP and reinstall OpenCore, again.
That's my new plan. I was going to re-try the install with the stock card installed. Install Opencore to the boot drive, re-fit the RX 580 and re-run Opencore and install to the boot drive again. Not workable?
Most importantly format your target disk using the Monterey disk utility from the installer/recovery dialogue.
I'm trying to install Big Sur... I should reformat using the installer?
Your best starting point would be Mojave (supported macOS on your system) to run OCLP and honestly the patcher you had with Catalina was the worst choice you could have made. It does not support your fancy GPU, does not enable video toolbox acceleration and the worst of all, it patches most likely the macOS Catalina, a thing we try to avoid at all cost with a modular system using OpenCore.
We are where we are... :)
The GPU should have a GOP BIOS installed, search the web for details. Without GOP no OpenCore boot picker at all. You will like the OpenCore boot picker.

Do not install both graphics cards, will not work.

On Macrumors there are at least three different threads (including this one) describing in great detail how to manage OpenCore on your MacPro5,1, do not mix and match, each group likes to stay separated and you may end up with "off topic" replies when asking basic questions. Nevertheless each of this thread is a great resource to information if you are willing to spend your time on reading the first post or the main documentation provided/linked there. It is not so much a help desk.
Believe me, I've been trying to read up but some of these threads run to nearly 500 pages. It's not easy to absorb.

Thanks for your comments though :)
S
P.S.:
You could have used Catalina unpatched with OpenCore on your Mac for years...
You may think about updating the (stock) existing BT/WiFi module with a PCI based BCM94360CD to get most features of Big Sur or Monterey running. Like adding a GPU some developments cannot by just patched out of the reality and need hardware changes.
 
  • Like
Reactions: TimothyR734

Ausdauersportler

macrumors 603
Nov 25, 2019
5,007
5,826
That didn't seem to be an option... You mean to format the drive and then do the install...? It might come to that if this try doesn't work...

That's my new plan. I was going to re-try the install with the stock card installed. Install Opencore to the boot drive, re-fit the RX 580 and re-run Opencore and install to the boot drive again. Not workable?

I'm trying to install Big Sur... I should reformat using the installer?

We are where we are... :)

Believe me, I've been trying to read up but some of these threads run to nearly 500 pages. It's not easy to absorb.

Thanks for your comments though :)
S
Each of the three threads has either a documentation at GitHub (this one), on the first post or somewhere in the middle.

Each post has an introduction on the very first post. Do not miss it.

Nobody would try to read a complete thread if there is already a comprehensive summary…
 

smartin80

macrumors member
Jun 5, 2020
40
23
Newb here...:)

I'm in the middle of trying to clean up the mess I made of my Opencore Lecacy Patcher upgrade from Catalina to Big Sur...

This is my setup:
Mac Pro Late 2010, 5,1, 6 core, 3.33mhz (?)
Samsung 860 Evo SSD as my boot drive
Radeon RX 580 sapphire graphics card

This box has been running Catalina very happily for a long while, curtesy of Dosdude's patcher but as I'm a few security updates behind, I figured it would be just as easy to jump to an OCLP install of Big Sur...

Not so...! :)

The Radeon card has never shown the Boot picker. This hasn't been an issue for me.

I built OCLP with the Radeon installed in the hope that the Boot picker might appear, as indicated by this post <https://forums.macrumors.com/thread...efi-for-rx580-reference.2286955/post-29656023>

The Boot picker did not appear so I reinstalled the stock graphics card which did allow me to choose the EFI disk from OCLP. The installation took me to the regular Big Sur installation screen but things started looping with endles restarts and I eventually pulled the plug and am now in the painful process of restoring from my CCC backup, which is taking forever ...

Was my mistake to not rebuild OCLP with the stock graphics card installed?

Is there any other reason why my install process should bork so badly?

Will I really see a Boot picker when using the Radeon RX 580 once I have found a way to complete this install...?

Thanks for your patience!

(PS... I did a practice run on my old Macbook which was running High Sierra and that went ok. No real issues.)

S
In case it helps another Nervous Newb...

It's only been running for an hour but I've now got Big Sur running on my machine, with my Radeon RX 580 fitted.

Photoshop CC 2022 runs which is my main concern :) I'm even being offered the Monteray upgrade through Software update, which I'm not doing...

I followed the OCLP instructions here: https://dortania.github.io/OpenCore-Legacy-Patcher/START.html each of three times I tried the install but with some differences..

The first time (Which crashed and burned...): I had my RX 580 card fitted when I built OCLP and did the installation. This card has never shown a Boot Picker but I was hoping it might show up. It didn't seem to. I just got a black screen. I gave up and force-quit the box by holding the power button down until it shut down.

The second time (Which was also a disaster): I re-fitted the stock graphics card. Then I used exactly the same installer that I had built previously, using the "Offline" GUI version of the patcher. Had I been more patient things might have worked out but I was perturbed about the multiple soft restarts (without the chime) and the time it was taking. I also interrupted the process by holding down the alt/option key during one of the restarts and chose the EFI disk again to boot from. Things borked so badly that I had to restore from my backup...

The third time: With the stock graphics card fitted I built the OCLP using the smaller "Online" GUI tool. Then I just walked away and let things take their course. When I got back, about 30mins later, I was at the login screen and logged in successfully.

I then built and ran the patcher again but this time installed it on my boot drive. I had removed the USB drive for the previous install first. I then rebooted with the Option key down and came up against the Boot picker again. I selected the EFI partition, held down the Control key to make this choice persistent and hit the enter key. The machine rebooted and I logged in again.

Then I rebooted again without any keys down to test the reboot. It rebooted fine without a problem.

I then refitted my RX 580 Sapphire card. and rebooted/Logged in again.

Then I rebuilt OCLP again and installed it to my boot drive again. I also did the Post installation patches but there were none to install.

I used the default settings in OCLP throughout.

The thing runs well and reboots without any intervention or USB sticks hooked up. Mind you it's early days yet...

In a nutshell... Leave the installation well alone for some considerable time. Hopefully it will complete.

S
 

Ausdauersportler

macrumors 603
Nov 25, 2019
5,007
5,826
I followed the OCLP instructions here: https://dortania.github.io/OpenCore-Legacy-Patcher/START.html each of three times I tried the install but with some differences..



I then refitted my RX 580 Sapphire card. and rebooted/Logged in again.

Then I rebuilt OCLP again and installed it to my boot drive again. I also did the Post installation patches but there were none to install.

I used the default settings in OCLP throughout.

The thing runs well and reboots without any intervention or USB sticks hooked up. Mind you it's early days yet...

In a nutshell... Leave the installation well alone for some considerable time. Hopefully it will complete.

S
Do you have an OpenCore boot picker on boot?

Great idea to run the post install patches at the very end after installation of the RX580, doing it with the GT120 installed would have ruined the installation and your day :)
 
  • Like
Reactions: TimothyR734

smartin80

macrumors member
Jun 5, 2020
40
23
Do you have an OpenCore boot picker on boot?

Great idea to run the post install patches at the very end after installation of the RX580, doing it with the GT120 installed would have ruined the installation and your day :)
I'll let you know about the Boot Picker tomorrow! My nerves are shot. Can't take any more tonight ;-)

S
 
  • Like
Reactions: TimothyR734

madvinegar

macrumors regular
Feb 23, 2022
192
100
Hmm. Starting to wonder whether this is a misconfiguration in your OpenCore, after all. Maybe this? (You might be able to search your config.plist file for the incorrect setting, rather than searching the entire IO Registry.)
You may be on to something...

I checked my config.plist and the IoregistryExplorer. See the screenshot. Whilst the config.plist states the IOName value as "string", the IoregistryExplorer states the value as "data". i.e. exactly what the post you linked states as problem.

However, I have three questions.

1. How do I fix this? The post says "Find what sets that wrong type and change it to the correct type, or disable that patch". Could it be that "display" has the "#" sign in front of it? Should I delete it altogether? How do I find what sets that wrong type?

2. Is it like this on purpose by OCLP and so if I make any changes to that value I may face a problem booting etc?

3. What happens if I mess with my EFI? How can I make corrections to it? Will I be able to boot without the EFI folder so as to mount the EFI partition and fix it?


Many thanks my friend either way!
 

Attachments

  • Στιγμιότυπο 2022-04-14, 9.35.50 μμ.png
    Στιγμιότυπο 2022-04-14, 9.35.50 μμ.png
    1.2 MB · Views: 96
  • Like
Reactions: TimothyR734

jgleigh

macrumors regular
Apr 30, 2009
177
232
Newb here...:)

I'm in the middle of trying to clean up the mess I made of my Opencore Lecacy Patcher upgrade from Catalina to Big Sur...

This is my setup:
Mac Pro Late 2010, 5,1, 6 core, 3.33mhz (?)
Samsung 860 Evo SSD as my boot drive
Radeon RX 580 sapphire graphics card

This box has been running Catalina very happily for a long while, curtesy of Dosdude's patcher but as I'm a few security updates behind, I figured it would be just as easy to jump to an OCLP install of Big Sur...

Not so...! :)

The Radeon card has never shown the Boot picker. This hasn't been an issue for me.

I built OCLP with the Radeon installed in the hope that the Boot picker might appear, as indicated by this post <https://forums.macrumors.com/thread...efi-for-rx580-reference.2286955/post-29656023>

The Boot picker did not appear so I reinstalled the stock graphics card which did allow me to choose the EFI disk from OCLP. The installation took me to the regular Big Sur installation screen but things started looping with endles restarts and I eventually pulled the plug and am now in the painful process of restoring from my CCC backup, which is taking forever ...

Was my mistake to not rebuild OCLP with the stock graphics card installed?

Is there any other reason why my install process should bork so badly?

Will I really see a Boot picker when using the Radeon RX 580 once I have found a way to complete this install...?

Thanks for your patience!

(PS... I did a practice run on my old Macbook which was running High Sierra and that went ok. No real issues.)

S

This is also useful for GPUs that don't support the Mac boot screen.

 
  • Like
Reactions: TimothyR734

Ausdauersportler

macrumors 603
Nov 25, 2019
5,007
5,826
You may be on to something...

I checked my config.plist and the IoregistryExplorer. See the screenshot. Whilst the config.plist states the IOName value as "string", the IoregistryExplorer states the value as "data". i.e. exactly what the post you linked states as problem.

However, I have three questions.

1. How do I fix this? The post says "Find what sets that wrong type and change it to the correct type, or disable that patch". Could it be that "display" has the "#" sign in front of it? Should I delete it altogether? How do I find what sets that wrong type?

2. Is it like this on purpose by OCLP and so if I make any changes to that value I may face a problem booting etc?

3. What happens if I mess with my EFI? How can I make corrections to it? Will I be able to boot without the EFI folder so as to mount the EFI partition and fix it?


Many thanks my friend either way!
Please leave this untouched, it just disables the iGPU of your SandyBridge CPU which would not work anyway with Big Sur and later.

But enabling it would crash the system on wake (it breaks simply the sleep/wake ability of your iMac).

And it is most likely interfering with the Intel Power Gadget (because it does not run on my similar equipped OCLP/Monterey iMac 2011).
 

Bmju

macrumors 6502a
Dec 16, 2013
702
768
You may be on to something...

I checked my config.plist and the IoregistryExplorer. See the screenshot. Whilst the config.plist states the IOName value as "string", the IoregistryExplorer states the value as "data". i.e. exactly what the post you linked states as problem.

However, I have three questions.

1. How do I fix this? The post says "Find what sets that wrong type and change it to the correct type, or disable that patch". Could it be that "display" has the "#" sign in front of it? Should I delete it altogether? How do I find what sets that wrong type?

2. Is it like this on purpose by OCLP and so if I make any changes to that value I may face a problem booting etc?

3. What happens if I mess with my EFI? How can I make corrections to it? Will I be able to boot without the EFI folder so as to mount the EFI partition and fix it?


Many thanks my friend either way!
To boot without OC you need to boot into Recovery, run sudo nvram boot-args="-no_compat_check" from the Terminal, then reboot your Mac, hold down ALT during boot to get the native Apple bootpicker, and select macOS directly. This will boot into macOS without OC, to let you check the theory.
Hmm. Your computer should start without OC. Why don't you test that first, as above?

You can also use https://github.com/mikebeaton/BootHelperPkg/releases to toggle -no_compat_check much more quickly than by booting into Recovery mode, you need to put the EFI folder for that program somewhere so that you can select it from the Apple boot menu, e.g. on a USB drive.

(Basically, without -no-compat-check you expect to see a 'No Entry' sign if you attempt to boot Big Sur without OC; but with it set, it should boot.)
 
Last edited:
  • Like
Reactions: TimothyR734

Bmju

macrumors 6502a
Dec 16, 2013
702
768
In an iMac 2011 I updated the Cpu to i7-2600s and the Gpu to Nvidia K2100m.
Then used OCLP to update the system to Big Sur.

I install intel power gadget, it installs fine but when I open it, the terminal opens instead, showing an error.

Does this have anything to do that I updated the cpu to i7 2600s?
Or that I updated the gpu to k2100m?
Or is there any setting in opencore that I should change...?

I've been assuming (wrongly?) that you upgraded to a graphics card which is natively supported in macOS? If it needs loads of patching then not so sure! Would you even have the native macOS boot menu with this card? (I guess @Ausdauersportler would know!)
 
  • Like
Reactions: TimothyR734

madvinegar

macrumors regular
Feb 23, 2022
192
100
@Bmju you assumed correctly. I replaced the oem AMD HD6770m GPU to a metal supported one (Nvidia K2100M) so as to have native gpu acceleration in Macos Big Sur. I also flashed the K2100m with a new apple supported bios (Nick[D]Vb bios). See the screenshot.

If @Ausdauersportler is certain that any change to this setting will break the sleep/wake functionality, I will not mess with it.

I could experiment (I mean delete the setting, see if there is any problem and if there is, re-apply the patch in config.plist) but I wanted to make sure that I could boot back to the desktop to fix things if I mess with the config.plist.
 

Attachments

  • Στιγμιότυπο 2022-03-20, 12.57.56 μμ.png
    Στιγμιότυπο 2022-03-20, 12.57.56 μμ.png
    2.4 MB · Views: 109
  • Like
Reactions: TimothyR734

smartin80

macrumors member
Jun 5, 2020
40
23
Do you have an OpenCore boot picker on boot?

Great idea to run the post install patches at the very end after installation of the RX580, doing it with the GT120 installed would have ruined the installation and your day :)
No, Doesn't seem to want to boot at all with the Option key down. Just a black screen.

S
 
  • Like
Reactions: TimothyR734

smartin80

macrumors member
Jun 5, 2020
40
23
Just to add that in case you have installed OpenCore Legacy Patcher you need to hold down the Escape key to see the OpenCore boot picker.
Just so I understand... I did use OCLP for my install. If I hold down the Escape key instead of the Option key, I will see the Boot picker...?
 
  • Like
Reactions: TimothyR734

smartin80

macrumors member
Jun 5, 2020
40
23
The opencore bootpicker, yes.
Ok, thanks :)

Hope you don't mind another Newb question...I habitually have a TimeMachine backup and a Carbon Copy Cloner backup to a different drive. This CCC copy will also be bootable. When I restart, will the system know which disk to boot from? It would be a drag if it booted from the copy rather than the main drive...

If I hold down Escape during the boot, will I be able to tell which EFI volume to choose for the boot drive? Will it be distinct from the Copy drive?

S
 
  • Like
Reactions: TimothyR734

makra

macrumors 6502
Dec 29, 2020
370
385
Northern Germany
Updated MB5,1 to Big Sur - using 0.4.4N because of the 1200s-issue. Worked well, but got this alert on startup (which doesn't appear on my 2009-2011 Macs). I'd seen, that 0.4.4N has different default SIP-settings. I remembered this: #5,411 and altered the SIP-settings to 0.4.3 default settings. Now the alert doesn't appear anymore. :) Thanks again for the great work.
 

Attachments

  • Bildschirmfoto 2022-04-15 um 10.33.35.png
    Bildschirmfoto 2022-04-15 um 10.33.35.png
    62 KB · Views: 75
Last edited:

Bmju

macrumors 6502a
Dec 16, 2013
702
768
@Bmju you assumed correctly. I replaced the oem AMD HD6770m GPU to a metal supported one (Nvidia K2100M) so as to have native gpu acceleration in Macos Big Sur. I also flashed the K2100m with a new apple supported bios (Nick[D]Vb bios). See the screenshot.

If @Ausdauersportler is certain that any change to this setting will break the sleep/wake functionality, I will not mess with it.

I could experiment (I mean delete the setting, see if there is any problem and if there is, re-apply the patch in config.plist) but I wanted to make sure that I could boot back to the desktop to fix things if I mess with the config.plist.
I'm giving you instructions as to how to boot into macOS without OpenCore - why don't you try them? If you can boot into your macOS without OpenCore, then ofc you can use that to fix any problems you might make in your OpenCore config.

I do this all the time on my MBP10,2 which - I think like yours - can boot without OpenCore, as long as boot-args="-no_compat_check" has been set, by one method or another (which just tells macOS to not bother checking whethe it 'thinks' it is compatible, and to try starting anyway).
 
  • Like
Reactions: TimothyR734

madvinegar

macrumors regular
Feb 23, 2022
192
100
I'm giving you instructions as to how to boot into macOS without OpenCore - why don't you try them? If you can boot into your macOS without OpenCore, then ofc you can use that to fix any problems you might make in your OpenCore config.

I do this all the time on my MBP10,2 which - I think like yours - can boot without OpenCore, as long as boot-args="-no_compat_check" has been set, by one method or another (which just tells macOS to not bother checking whethe it 'thinks' it is compatible, and to try starting anyway).

I will try this and report back.
However I would like to apply a proper solution to this problem rather than just deleting the patch (which is there for a reason).
I understand the problem is that in the config.plist the IOName is stated as "string" but when it is injected it changes to "Data". And from what I understand, I need to create a DSDT to fix this and keep it to string even after been injected.

Do you have any guide in creating Dsdts?
 
  • Like
Reactions: TimothyR734

madvinegar

macrumors regular
Feb 23, 2022
192
100
I'm giving you instructions as to how to boot into macOS without OpenCore - why don't you try them? If you can boot into your macOS without OpenCore, then ofc you can use that to fix any problems you might make in your OpenCore config.

I do this all the time on my MBP10,2 which - I think like yours - can boot without OpenCore, as long as boot-args="-no_compat_check" has been set, by one method or another (which just tells macOS to not bother checking whethe it 'thinks' it is compatible, and to try starting anyway).
So, I installed the OCLP EFI to an empty USB. I opened config.plist and deleted the IOName patch. Saved it and then restarted and booted off this modified USB EFI.

Intel Power Gadget installs and works fine. Also I checked the IORegistryExplorer and now the IOName entry is correctly shown as "string".

I tested sleep/wake and it is working. However, I believe that maybe Deep sleep is not working. This is because when I wake up the iMac, it wakes up very fast whilst I remember it used to delay a little... Is there a way to check if deep sleep is actually working?
 

Attachments

  • Στιγμιότυπο 2022-04-15, 3.19.11 μμ.png
    Στιγμιότυπο 2022-04-15, 3.19.11 μμ.png
    1.6 MB · Views: 171
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.