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.
In case this can help, I don't need to create an OpenCore boot CD, because I have a Mac-flashed EFI GPU, so I can easily boot using a GPT USB thumb drive. OpenCore 0.7.8 boots without any issues off that thumb drive.
Peter, that is how I used to boot OpenCore with a flashed GTX680 - using a USB drive.

When I switched to a RX560 (when Monterey dropped Nvidia drivers) I switched to using a rescueCD to boot since there is no way to force booting from a USB like a CD.

I'll test some later and perhaps @cdf can confirm the rescue CD root still works and I need to redo my 0.7.8 rescueCD or OpenCore needs to be "fixed" to boot from CD again.
 
Almost there, Big Sur and W10 have installed, no blue tooth in either atm, I have already done the bt/Wi-Fi adapter to BCM943602CDP. I have seen 3 random restarts in BS thou, screen flickers and restarts? However I'm seeing the same screen flicker in W10 also, but not causing a restart, not rx580 again hmm.
@cdf Is there something that requires changing in the config.plist to enable blue tooth, Ive installed drivers from bootcamp into windows, BT is working now, BT is working in Mojave.

Update: now its working in Big Sur, I remember I read somewhere else BT if you boot into BS from windows, but not Mojave.
 
Last edited:
Peter, that is how I used to boot OpenCore with a flashed GTX680 - using a USB drive.

When I switched to a RX560 (when Monterey dropped Nvidia drivers) I switched to using a rescueCD to boot since there is no way to force booting from a USB like a CD.

I'll test some later and perhaps @cdf can confirm the rescue CD root still works and I need to redo my 0.7.8 rescueCD or OpenCore needs to be "fixed" to boot from CD again.
@cdf - I just tested for the third time - created a new EFI folder from 0.7.8 files and followed post #1 to add the OcBinaryData files, clean up the folder per the instructions, add the three kexts I use and copy over my config.plist (this time copying it from my working boot rescueCD) and burned the disk.

Didn't work. On my machine I cannot boot from the rescueCD built with 0.7.8.

Another thing that is very odd is that when it doesn't boot from the rescueCD (holding down "C") it boots from my Catalina install though I had set my startup disk to Mojave. When I swapped back my 0.7.7 rescueCD and booted into Monterey my startup disk was still set to Mojave.

I'm looking forward to see what your experience is.

Regards,
sfalatko
 
@cdf - I just tested for the third time - created a new EFI folder from 0.7.8 files and followed post #1 to add the OcBinaryData files, clean up the folder per the instructions, add the three kexts I use and copy over my config.plist (this time copying it from my working boot rescueCD) and burned the disk.

Didn't work. On my machine I cannot boot from the rescueCD built with 0.7.8.

I'm looking forward to see what your experience is.

Regards,
sfalatko
I just updated my CD to 0.7.8, and it works. Note that for simplicity, my CD does not have OpenCanopy enabled (so the menu is text-based)...
 
@cdf Is there something that requires changing in the config.plist to enable blue tooth, Ive installed drivers from bootcamp into windows, BT is working now, BT is working in Mojave.

Update: now its working in Big Sur, I remember I read somewhere else BT if you boot into BS from windows, but not Mojave.
If your module is supported, then you shouldn't have to change anything. However, booting between different versions of macOS can cause issues (usually resolved after a few reboots).
 
Anybody who has done the upgrade from Big Sur to Monterey, how's the performance? I find Big Sur to be slower than Mojave was, but Windows 10 absolutely flies. Biggest slowdown was in games (which is apparently common). My settings for Borderlands 2 for example that worked flawlessly in Mojave now provide very poor performance with Big Sur. Was curious whether this was resolved with Monterey or not.
 
  • Like
Reactions: Cfreak
I just updated my CD to 0.7.8, and it works. Note that for simplicity, my CD does not have OpenCanopy enabled (so the menu is text-based)...
I will try the burn again and provide an update. Thanks for confirming it works for you.
 
Anybody who has done the upgrade from Big Sur to Monterey, how's the performance? I find Big Sur to be slower than Mojave was, but Windows 10 absolutely flies. Biggest slowdown was in games (which is apparently common). My settings for Borderlands 2 for example that worked flawlessly in Mojave now provide very poor performance with Big Sur. Was curious whether this was resolved with Monterey or not.

Monterey is faster. See below.

cMP4.1/5.1 dual xeon5680, evo plus 1TB, Crusial NVME P2 2TB, UCB3 pci card, RadeonPro W5700. I have been using OC for almost a year and a half, starting with version 0.5.8. my experience shows that the best CPU performance was on Mojave without open core, the weakest operating system was Catalina - and the CPU and GPU worked worse than on Mojave, although Catalina allowed to use Radeon Navi, but starting with version 0.7.0 and BigSur update The CPU began to work much better, almost like in Mojave, but the GPUs began to show significant performance gains. Gikbench5 Metal score on Catalina for the Radeon Pro W5700 was 60,000-61000, when switching to Big Sur Metal score became 63000, and with version 0.7.2 and BigSur 11.3, the drivers for Navi improved and the score became 64000, but with upgrade to Monterey with OC version 7.5 or 7.6 the score became 65000, today I update OC 7.7 and the geekbench5 metal score became 68000. BlackmagicRAW in BigSur 11.2 was 980, in BigSur 11.6 was 2000, for Monterey with OC 0.7.7 2032. But LuxMark BigSur and Monterey are about the same 2880 and 2910. Heaven benchmark with ultra settings for RadeonProW5700 -2205- for Monterey+OC 0.7.7, -2009 for OC 0.7.6 for BigSur score was about 1900, and i have comparison of Monterey and Catalina for radeon RX580 (sapphire dual bios)- high settings: for Mojave -1978, but for Catalina only -1740. As to real rendering with Twinmotion and UE4.7 or UE5 FPS performance increases with monterey significantly (about 15% compared to BigSur). some pictures attached.View attachment 1942514View attachment 1942515)View attachment 1942501View attachment 1942503 Luxmark as to real work in Twinmotion

@Gustav Holdoff I was wondering if you might have some scores for Mojave?
 
  • Like
Reactions: OVERKILL338LM
Wondering if anyone has experienced this and can help me out.

I was running Catalina on my Mac Pro 5,1 and Opencore 0.7.0

A few days ago I upgraded Opencore to 0.77 using the Wiki. Everything worked (DRM, TV app etc).

Last night I upgraded my OS to Monterey 12.2 and now my TV app is not playing any content so it seems my DRM settings have changed.

I looked through the wiki but can’t find a solution. Any ideas?
 
Lost usb keyboard/mouse in bootpicker

I've just completed installing Monterey 12.2 onto a new HD. To do so I followed Martin Lo's VMM / updateSMBIOS switches - the install completed just fine and when I was done setting up I changed them back and restarted.

On the subsequent boot I tried to switch back to my usual startup drive but the keyboard and mouse (logitech with usb dongle in keyboard) didn't work. Obviously the mouse depends on the keyboard but other than those two lines in config (checked for spelling etc) I changed nothing. Just the OS install and then restarting.

The keyboard is a wired aluminium apple extended and connected via a simple cheap (bus powered) USB dongle to the rear of the Mac.

Not sure if this is OC related but everything was fine until those config changes. A couple more restarts tried and the problem persists.

Any ideas? TIA
 
Using Martin Los' bundle i made it into Big Sur with MP5,1. Then i installed Monterey from within Big Sur onto the same drive partitioned into 2. Monterey install completed without any changes needed to the config file to allow install onto the new drive, and attempting to boot into it results in a restart loop just before the loading bar loads. All i see is the Apple logo and restart loop.
I'm pretty sure both installs are using the same config file being on the same drive. Is there something i can adjust to make this setup work!?
Check post #1 for the recommended settings for Monterey. You can also use the sample config to establish a working baseline.

The keyboard is a wired aluminium apple extended and connected via a simple cheap (bus powered) USB dongle to the rear of the Mac.
As a test, try connecting the keyboard directly on its own (no dongle, no mouse). This keyboard is the gold standard and should work perfectly with OC.
 
  • Like
Reactions: kkinto
Wondering if anyone has experienced this and can help me out.

I was running Catalina on my Mac Pro 5,1 and Opencore 0.7.0

A few days ago I upgraded Opencore to 0.77 using the Wiki. Everything worked (DRM, TV app etc).

Last night I upgraded my OS to Monterey 12.2 and now my TV app is not playing any content so it seems my DRM settings have changed.

I looked through the wiki but can’t find a solution. Any ideas?
Seems OK on my end (trailers at least). Are other streaming services (such as Netflix) also not working in Safari?
 
I will try the burn again and provide an update. Thanks for confirming it works for you.
@cdf - I am completely stumped.
I will try the burn again and provide an update. Thanks for confirming it works for you.
@cdf - well I am stumped. I tried burning a new CDRW with 0.7.8 in Catalina (I had been using Monterey) and it wouldn't boot. I then went back to Monterey and created another CDRW with my 0.7.7 files and it wouldn't boot either.

I am not sure what is going on - I can read the files on the burned CD's but the CD isn't booting though my original 0.7.7 CDRW is booting.

If you have any suggestions I can try let me know.
 
@cdf - I am completely stumped.

@cdf - well I am stumped. I tried burning a new CDRW with 0.7.8 in Catalina (I had been using Monterey) and it wouldn't boot. I then went back to Monterey and created another CDRW with my 0.7.7 files and it wouldn't boot either.

I am not sure what is going on - I can read the files on the burned CD's but the CD isn't booting though my original 0.7.7 CDRW is booting.

If you have any suggestions I can try let me know.

It's not the ScanPolicy settings is it? Check this very handy website app here to see if your current ScanPolicy includes booting off CD/DVDs.
 
@cdf - well I am stumped. I tried burning a new CDRW with 0.7.8 in Catalina (I had been using Monterey) and it wouldn't boot. I then went back to Monterey and created another CDRW with my 0.7.7 files and it wouldn't boot either.

I am not sure what is going on - I can read the files on the burned CD's but the CD isn't booting though my original 0.7.7 CDRW is booting.

If you have any suggestions I can try let me know.
The fact that 0.7.7 isn't booting either now indicates that the problem probably isn't with 0.7.8. Make sure to double check the directory structure: OC-CD/EFI/... You can also try the earlier set of instructions provided in post #8,637. Another option would be to use a Mac EFI graphics card to see if the CD appears in the native boot menu.

It's not the ScanPolicy settings is it? Check this very handy website app here to see if your current ScanPolicy includes booting off CD/DVDs.
These settings apply to what OC can boot. However, the problem here is with Mac (native firmware) not booting the CD.
 
  • Like
Reactions: JedNZ
It's not the ScanPolicy settings is it? Check this very handy website app here to see if your current ScanPolicy includes booting off CD/DVDs.
I don't think so - I burned my working EFI folder to a new CD and that won't boot either. I will take @cdf suggestion to reinstall my EFI flashed graphics card and see if I see the CD in the boot menu.
 
The fact that 0.7.7 isn't booting either now indicates that the problem probably isn't with 0.7.8. Make sure to double check the directory structure: OC-CD/EFI/... You can also try the earlier set of instructions provided in post #8,637. Another option would be to use a Mac EFI graphics card to see if the CD appears in the native boot menu.


These settings apply to what OC can boot. However, the problem here is with Mac (native firmware) not booting the CD.
I'll check later with my EFI flashed graphics card - it kind of seems that something is wrong with my CDRW burning even though I can read the files in macOS.
 
Sorry if this is not entirely apposite to this thread. After several failed attempts to install an XFX Radeon RX 580 8GB GPU on my cMP 5,1 back in Catalina and Big Sur times, I've tried once again with Monterey. This is odd, because the instability problems seem limited to all versions of macOS after Mojave. I haven't detected any issues in Mojave (native boot) or UEFI Windows 11 (via OpenCore).

The relevant "DeviceProperties" portion of my config.plist is as follows:

Code:
    <key>PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)</key>
    <dict>
    <key>@0,name</key>
    <data>QVRZLE9yaW5vY28=</data>
    <key>agdpmod</key>
    <data>cGlrZXJhAA==</data>
    <key>model</key>
    <string>Radeon RX 580</string>
    <key>rebuild-device-tree</key>
    <data>AA==</data>
    <key>shikigva</key>
    <data>UA==</data>
    <key>unfairgva</key>
    <data>AQAAAA==</data>

I'm not completely certain about the data values. Perhaps they are entirely wrong for this particular GPU? In addition, I've noticed that the "model" key does nothing, because the "Radeon RX 580" name doesn't stick; for instance, VideoPro Converter doesn't recognize the GPU. I wonder if the "rebuild-device-tree" key shouldn't have a different value. Can anyone comment? I haven't done the Pixlas mod yet.
 
Last edited:
Let's address this one first.

Unfortunately, you seem to be dealing with one of the exceptional cases where your GPU lacks the necessary acpi-path property for adding other properties. The quickest solution for now is just to use boot-args. In your config, remove

XML:
<key>PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)</key>
<dict>
<key>rebuild-device-tree</key>
<integer>0</integer>
<key>unfairgva</key>
<integer>1</integer>
<key>shikigva</key>
<integer>80</integer>
</dict>

and replace

XML:
<string>-no_compat_check</string>

by

XML:
<string>-no_compat_check wegtree=1 unfairgva=1 shikigva=80</string>

Now with these changes, check that DRM works.
Apparently I am also the lucky bastard that owns a GPU that lacks the necessary acpi-path property for adding other properties. Is there a list which GPU's are lacking this? The above solution works for me, so that's nice:)

FWIW my GPU is an AMD Radeon RX5700 reference card.

Cheers Jay
 
Sorry if this is not entirely apposite to this thread. After several failed attempts to install an XFX Radeon RX 580 8GB GPU on my cMP 5,1 back in Catalina and Big Sur times, I've tried once again with Monterey. This is odd, because the instability problems seem limited to all versions of macOS after Mojave. I haven't detected any issues in Mojave (native boot) or UEFI Windows 11 (via OpenCore).

The relevant "DeviceProperties" portion of my config.plist is as follows:

Code:
    <key>PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)</key>
    <dict>
    <key>@0,name</key>
    <data>QVRZLE9yaW5vY28=</data>
    <key>agdpmod</key>
    <data>cGlrZXJhAA==</data>
    <key>model</key>
    <string>Radeon RX 580</string>
    <key>rebuild-device-tree</key>
    <data>AA==</data>
    <key>shikigva</key>
    <data>UA==</data>
    <key>unfairgva</key>
    <data>AQAAAA==</data>

I'm not completely certain about the data values. Perhaps they are entirely wrong for this particular GPU? In addition, I've noticed that the "model" key does nothing, because the "Radeon RX 580" name doesn't stick; for instance, VideoPro Converter doesn't recognize the GPU. I wonder if the "rebuild-device-tree" key shouldn't have a different value. Can anyone comment? I haven't done the Pixlas mod yet.
Peter - take a look at this post earlier in the thread - #9617
 
Where's the new updated 0.7.8 bundle?
Curious if that'll fix my dual booting issue.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.