With my little understanding of what these brilliant minds came up with - and actually I don't really even understand if their solution applies to my problem - I added syncretic's AVWpel patch to my oc config file. The Mac rebooted with the modifyed config.plist so at least I didn't break anything as far as I can tell.
But unfortunately it didn't resolve my issue with the AVX error that pops up right at the beginning of the software installation I wanted to do. Maybe I did something wrong, for now I am still looking for a solution.
With my little understanding of what these brilliant minds came up with - and actually I don't really even understand if their solution applies to my problem - I added syncretic's AVWpel patch to my oc config file. The Mac rebooted with the modifyed config.plist so at least I didn't break anything as far as I can tell.
But unfortunately it didn't resolve my issue with the AVX error that pops up right at the beginning of the software installation I wanted to do. Maybe I did something wrong, for now I am still looking for a solution.
may be C4D not compatible with old cMP? i use blender 3.1, UE5 and Twinmotion- everything seems to work no worse than the MAC Studio. As I understand there is other solution- try noAVX kext (try to follow instruction post#1)
Having a black-screen/reboot issue on a fresh full install of Monterey 12.4 on an NVMe (Sabrent Rocket). This is on a true MacPro5,1 2010, w/ OC 0.8.0 on a SATA SSD w/ a fresh full install of Mojave 10.14.6, and a fresh full install of Windows 10 using OC w/ UEFI & GPT on a Samsung AHCI.
If I run Mojave or Windows 10, then choose Monterey during next OC boot, it will successfully load to the desktop, but will black-screen a couple of minutes in (regardless whether I interact with Monterey or not after loading into the desktop), then restart into OC. The Mac Pro does not power cycle, as it remains on and running the whole time. Unless I reset NVRAM, it will continuously do this every time I select Monterey.
Note, I can select Windows 10 or Mojave on OC after the black-screen/reboot from Monterey, without resetting NVRAM, and both OS’ will run without issue, so seems Monterey specifically is not liking something…… After an NVRAM reset and selecting Monterey first, it will run (and even restart back into itself) without issue, so long as I do not run Mojave or Windows 10 again.
Maybe others have had a similar issue, but not seeing anything recent, considering 12.4’s recent release. I can confirm all set-up steps were followed correctly, and the whole system was built clean, from scratch in the last few days. And suggestions where to start?
[Side note, I always need to sleep cycle on Monterey after booting to get the stock Sapphire Pulse 580 8GB Dual Bios (switched to Gaming) to perform at its full tilt when running Geekbench, which is not a problem in Mojave or Windows 10, where it will run full-tilt from boot. Not sure if anyone has seen/knows a solution, as I’ve had no luck.]
may be C4D not compatible with old cMP? i use blender 3.1, UE5 and Twinmotion- everything seems to work no worse than the MAC Studio. As I understand there is other solution- try noAVX kext (try to follow instruction post#1)
That's interesting info, thanks for sharing. What gpu are you using if I may ask, are you rendering on it?
And thanks for pointing out khronokernel's noavx kext and cdf's instructions in the 1st post, slipped my eye, it's deep down inside of the "complete your setup" block (click to expand ...) - for everybody who is wanting to look into this matter.
Will give it a shot soon eventhough the post claims that the avx problems this kext aims at is "starting with 12.4".
I am too curious if this might be the end of my c4d update path on cMP. The machine still is incredible (2010 5,1 - 2 x 3,46 6-core - 128GB - 8GB RX 580 - big sur on nvme).
That's interesting info, thanks for sharing. What gpu are you using if I may ask, are you rendering on it?
And thanks for pointing out khronokernel's noavx kext and cdf's instructions in the 1st post, slipped my eye, it's deep down inside of the "complete your setup" block (click to expand ...) - for everybody who is wanting to look into this matter.
Will give it a shot soon eventhough the post claims that the avx problems this kext aims at is "starting with 12.4".
I am too curious if this might be the end of my c4d update path on cMP. The machine still is incredible (2010 5,1 - 2 x 3,46 6-core - 128GB - 8GB RX 580 - big sur on nvme).
Now Blender 3.1 with MacOs 12.3.1-12.4 supports GPU rendering in circles, My GPU RadeonPro W5700
on other cMP i use RadeonPro W5500-
it's more better then RX580- because I can simultaneously work in ArchiСad or even in UE while rendering Twinmotion,
But with rx580, while rendering, I have to leave for lunch
My current OC 0.8.0 with edited cdf config +TBOLT3+radeonsensor+syncretyc patch My CMP 4.1/5.1 dual cpu xeon 5680, 96gb RAM, radeonpro w5700, nvme crucial 2tb, evo plus 1tb, TB3 alpine ridge, oc 0.8.0, mac os 12.4
I installed everything and it worked great. The only issues now is that none of my front usb ports work correctly on my (2009 mac pro, flashed 4,1 to 5,1, raddeon 580 8gb, 32 ram.) But the most annoying issue, is that in the past i had NTFS for mac installed, about 2 OSs back. I've uninstalled and gone through all of the ~/library/ hidden compartments to get rid of the all components of that app. Now i keep getting this "Paragon Updater cannot be opened..." the only way to get rid of it, is by opening "activity Monitor" and searching for UserNotificationCenter and quitting it. Is there any way i can remove that notification from "UserNotificationCenter"? Sorry if this was for another thread.
I installed everything and it worked great. The only issues now is that none of my front usb ports work correctly on my (2009 mac pro, flashed 4,1 to 5,1, raddeon 580 8gb, 32 ram.) But the most annoying issue, is that in the past i had NTFS for mac installed, about 2 OSs back. I've uninstalled and gone through all of the ~/library/ hidden compartments to get rid of the all components of that app. Now i keep getting this "Paragon Updater cannot be opened..." the only way to get rid of it, is by opening "activity Monitor" and searching for UserNotificationCenter and quitting it. Is there any way i can remove that notification from "UserNotificationCenter"? Sorry if this was for another thread.
The front ports should works. If you have issue about USB 1.1 HID doesn't work, then try connect them via a hub. It's the OS issue, not really OC's problem.
Again I got a problem installing third party audio drivers with OC 0.8.0
Monterey 12.4
UAD driver update version 10.1
after restart the Uad drivers extension won't load even if have authorised in file vault
The only only solution i have found was the same used for installing Motu firewire drivers
using OCLP EFI in my magic USB pendrive
here is my previous post
Hi @h9826790. I've been using your package for a while, and recently checked the speeds of my Samsung 960EVO NVMe drive. Read speeds are about 1350MB/s, but write speeds are very low - about 200MB/s. During my investigations, I found that your package disables TRIM at boot. Could this be the cause of the low write speeds? If so, what would I change to resolve this?
Hi @h9826790. I've been using your package for a while, and recently checked the speeds of my Samsung 960EVO NVMe drive. Read speeds are about 1350MB/s, but write speeds are very low - about 200MB/s. During my investigations, I found that your package disables TRIM at boot. Could this be the cause of the low write speeds? If so, what would I change to resolve this?
Thanks @h9826790. I set the Trim Timeout to the value above and rebooted. It took a few minutes to boot up, but I'm now back to 1400MB/s for both read and write.
I rarely reboot, so no big deal if it takes a couple of minutes to trim at startup. The SSD must have had a lot of untrimmed blocks to have such low write performance. Hopefully on future reboots only light trimming will be necessary anyway.
I created a new "easy to install package" as per many requested (based on the official OpenCore). [The attached package updated to 0.8.0]
For those who only need HWAccel, post #594 has everything you need. This new package mainly offer HWAccel + boot screen. Also, this package should work in Catalina and newer macOS for dual processor cMP.
I don't mind you guys discuss anything about this package, but I have no plan to provide any explanation about OpenCore at here. If you want to know more, please join cdf's OpenCore thread. For new joiners, please make sure read through the FAQ in post #1 before you ask anything.
The attached packaged included Clover Configurator and a complete preconfigured OpenCore. All credits goes to the developer teams. If you want to show your support, please give them donation (declaration of interest： I am NOT in any of their developer teams)
For Clover Configurator and OpenCore developers teams, please let me know if you want me to remove the associated software inside my attachment in this post.
This is a "one package fit all" solution. So, it's designed to fit as much setup as possible, which may not be optimized for your setup (e.g. I haven't provide HiDPI boot screen, for those who are running 4K screen, the Apple logo may be quite small during boot). You have to do the optimization by yourself (details in the OpenCore manual, some info also available in cdf's OpenCore thread).
Anyway, for those who have RX 460 or newer AMD GPU, this package should gives you:
Boot screen (via GOP for unflashed card, including some Nvidia card)
Firmware protection (to run Windows in EFI mode without risking the cMP bootROM)
HWAccel (H264 / HEVC hardware decode + encode in Mojave and newer macOS)
ability to watch DRM streaming content (Mojave and newer macOS)
Boot picker (only support EFI systems, tested with Apple wired keyboard, Magic Mouse, and Magic Keyboard, 10s timeout. If you can't see this. Just don't touch the keyboard, and your cMP should continue to boot to desktop)
NVMe and SATA drives on PCIe card show up as internal
Support for Apple USB SuperDrive
TRIM (regardless trimforce status)
Ability to run non-GUI 32bit software in Catalina
Ability to reset NVRAM in boot picker (disabled at this moment to align with the native Apple boot manager)
Ability to run any natively supported ancient OSX with modern graphic card e.g. Radeon VII in 10.6.8 (only can display, no acceleration) [Update 5th May 2020: Sierra and High Sierra may not fully supported yet. Thanks for pierrox's report]
Ability to boot Catalina / Big Sur / Monterey and the associated Recovery Partition [SurPlus (credit to Syncretic) is included and enabled by default to fix the racing condition in macOS 11.3 or later][MonteRand is also included. another credit to Syncretic][ASPP-Override is included for macOS 12.3, credit to dortania]
Sleep should work (tested on my cMP, but I can't guarantee it also work with your hardware)
Possible to run 8x32GB RAM in macOS (user need to mod the config.plist manually. Replace the false below CustomMemory to true)
Enable HDMI Audio for some graphic cards
Ability to monitor modern AMD GPU's temperature (by using the attached RadeonGadget. Credit to Aluveitie)
It's impossible for me (and other voluntary helpers) to test every single function in all situations. So, as usual, use at your own risk. But you are welcome to report back if there is any problem / error.
Pre-installation:
Recommend to backup your BootROM between step 1 and 2 (e.g. by using ROMTool, credit to Dosdude, password "rom")
If you want to test OpenCore, you can install this package onto a bootable USB thumb drive.
Quite a few users reported that can't boot OpenCore from NVMe, analysis shows that depends on hard drives config. It's hard to explain which exact scenario may hit this bug. So, please avoid to install this package on NVMe. You can install this package on ANY SATA drive with virtually no performance lost, not necessary your boot drive.
If you want to remove OpenCore, please mount the EFI partition by using Clover Configurator, then remove BOOT and OC folders inside the EFI folder on EFI partition.
If your cMP stuck at boot. After shutdown, please pull out the hard drive that contain OpenCore, then perform NVRAM reset. If still doesn't work, then please install your emergency graphic card that has boot screen. Hold Option to boot, then select your backup boot drive. This should disable OpenCore.
For those who want to report issue / error. Please provide details (e.g. which graphic card, OpenCore installed on NVMe / SATA drive, the issue's details, etc) otherwise it will be extremely hard (or even impossible) for me to work out what's wrong.
If you installed Lilu for whatever reason (e.g. because of innie), or applied my previous non-OpenCore HWAccel mod, please remove them or revert them. For Lilu + WEG, that means delete Lilu.kext in /Library/Extensions/ and reboot (caution: these kexts may be installed in System/Library/Extensions/ as well). For hex edit method, that means delete AppleGVA.framework in /System/Library/PrivateFrameworks/ and rename AppleGVA.framework.bak to AppleGVA.framework. Warning: My packages already have Lilu and WEG included, "double installation" of these kexts will cause macOS boot failure.
For PULSE RX580, users reported that only can see boot screen when boot from gaming mode. There may be no UEFI GOP in the compute mode's ROM.
I tried to make the installation as simple as possible. However, I still demand you to learn some very basic skills. Those skills are very useful in the recovery process if something goes wrong. Anyway, here is what you need to do
[Optional] 3x NVRAM reset to avoid some unknown issues.
Disable SIP (must do, especially if you performed step 1)
Download the attachment in this post (Some users reported 0.6.1 package has compatibility issue. You may download the 0.5.9 package if you prefer that, same installation procedures.)
Follow the steps in this video (please turn on and read the subtitle)
For Big Sur and Monterey, if some ports on your graphic card are disabled, please follow the steps in this video to re-enable them.
Reboot
For existing OpenCore users, you may follow the step in this video to update OpenCore [For those who installed OC onto the Windows drive, please make sure you only replace the OC files, but not the whole EFI folder]
Additional option 1: If you have 4K screen, and you want to have "Retina" boot screen. You may do this. [Depreciated in 0.7.6, which Retina should be enabled automatically on 4K monitor]
Additional option 2: If you have a flashed Thunderbolt 3 card, you can install that in slot 4, then enable Thunderbolt 3 support by doing this.
Additional option 3: If you want to enable the ability to install / update Catalina, Big Sur and Monterey, please follow the steps in this video. [N.B. you should revert the changes after macOS installation completed. This special setting is not designed for daily use]
Additional option 4: If you have legacy wifi card, you may try the follow steps to re-activate the old wifi card in Big Sur (only avail in my 0.6.4 package or above)
Additional option 5: To enable legacy BT support in the latest unsupported OS, you may turn on both BlueToolFixUp and BlueTooth-Spoof kext.
Additional option 6: Since 0.6.3, I allow OC to take over SIP control. There are various reasons, but anyway, that's defaulted to be disabled. If you want to re-enable SIP, please follow the steps in this video. (please turn on the English subtitle when you watch this video, some useful info at there)
For FCP(X) users, if you want to export HEVC video by using HWAccel, you will need Compressor.
[N.B. The setting MUST identical to the one that I show in the video. Otherwise, HEVC hardware encoding may not work]
If you want to completely uninstall my OpenCore package, please follow the steps in this video.
N.B. Unflashed graphic card means "the ROM is never modified". For those who bought used card, and can't see the boot screen, most likely the last user flashed the card with modified ROM (e.g. downvolt for mining). In this case, you can go to TechPowerUp to find a ROM that fit your own card, and flash it.
Hi @h9826790. First, thanks for your great work! It really saved me after my Nvidia driver stopped working like many others a few days ago. Now I´m running a Sapphire Pulse on my 5.1 Mac with 10.13.6 and I´m trying to install Monterey, but I keep getting the firmware update error message (because of a 3rd party SSD). Did I miss anything or does your 0.8.0 package not solve that problem and I need to get an original Apple SSD? I could not find another possibility on the forum so far. Thanks for a reply and maybe a solution!
Hi @h9826790. First, thanks for your great work! It really saved me after my Nvidia driver stopped working like many others a few days ago. Now I´m running a Sapphire Pulse on my 5.1 Mac with 10.13.6 and I´m trying to install Monterey, but I keep getting the firmware update error message (because of a 3rd party SSD). Did I miss anything or does your 0.8.0 package not solve that problem and I need to get an original Apple SSD? I could not find another possibility on the forum so far. Thanks for a reply and maybe a solution!
Thanks for your reply.
Of course, I watched your video before, but strangely, my Mac allows the installer to run right away – even bevor changing the settings in your config (I downloaded the InstallAssistant.pkg). I do not get warnings like in your video. All my disks are immediately ready for installing, no matter whether SSD or others. But after the installer runs for a while and then restarts my mac, I get the firmware update message. I expect, formatting the SSD to AFPS was correct? Or do I have the wrong installer? Downloading the one from the Appstore was not possible. Sorry to bother you again.
Eventually, I've made my Bluetooth and Wifi worked in Monterey. It didn't work due to I installed the Opencore into the EFI partition of my original Mojave drive which I should install it into the target-installation-drive for the new macOS. In h982790's video. There's no subtitle mentioned about the which drive's EFI partition should be used. So I did it incorrectly.
Yeah, I've got OC on my Windows drive in SATA bay 1. That way a) my UEFI Windows can't boot without OC running (which could cause corruption to NVRAM) and b) OC will always run and self-bless following an NVRAM reset, as in my particular machine, bay 1 is first in the boot order.
Additional option 3: If you want to enable the ability to install / update Catalina, Big Sur and Monterey, please follow the steps in this video. [N.B. you should revert the changes after macOS installation completed. This special setting is not designed for daily use]
I installed Martin's OC 0.8.0 in order to update from Mojave to Big Sur soon. Then I read this warning. Why is Big Sur striked in the above comment? And what is the method to in stall Big Sur then?
I installed Martin's OC 0.8.0 in order to update from Mojave to Big Sur soon. Then I read this warning. Why is Big Sur striked in the above comment? And what is the method to in stall Big Sur then?
Yes, I was able to install Big Sur not changing the config without any issues on my 5.1 Mac (since my attempts to install Monterey always got me the firmware update error (after modifying the config as shown in h9826790´s video). I'm fine with Big Sur though.
BUT: My mouse often keeps freezing for short moments and even jumps from one place to another on my screen when moving it. Sometimes it gets really bad an requires a restart. Does anyone have a solution for that?
Yes, I was able to install Big Sur not changing the config without any issues on my 5.1 Mac (since my attempts to install Monterey always got me the firmware update error (after modifying the config as shown in h9826790´s video). I'm fine with Big Sur though.
BUT: My mouse often keeps freezing for short moments and even jumps from one place to another on my screen when moving it. Sometimes it gets really bad an requires a restart. Does anyone have a solution for that?
for me sometimes i had issue with radeon RX580 due to
<key>DirectGopRendering</key>
<true/>
when I set it to "false" I got the solution
if this does not solve the problem, return to "true" and look for another reason
I just wanted to upgrade my 1tb nvme to a 2tb nvme on my cMP4.1 patched to 5.1. I used Martin Lo's Open Core 8.0 with plist for Monterey 12.4 since this is the only version I can download. I have a Samsung 970 Evo Plus from 2022 so the Firmware should be up to date.
I did detached everything beside my SSD on wich OC is installed and a RX 580, mouse and keyboard and was able to beginn the installation process. Everything went perfectly fine until the first restart where a window appeared which says something like "necessary firmware update couldn't be loaded" (freely translated from German) and I cloudn't do anything from this point on. I was asked if I want to go to HDD mode or shut down but nothing happens in HDD mode. Does anyone know what went wrong? Help is highly appreciated!
for me sometimes i had issue with radeon RX580 due to
<key>DirectGopRendering</key>
<true/>
when I set it to "false" I got the solution
if this does not solve the problem, return to "true" and look for another reason
Hi Gustav, thanks for the tip – but it made no difference, unfortunately. Restarting the finder seems to make things better, but that's, of course, no permanent solution. Does anyone else have a suggestion?
