MP 1,1-5,1 Activate AMD hardware acceleration

[star-affinity]

Updated to Big Sur - 11.6.3 with 0.76 without any issues.
Will be doing Monterey this evening.

Did it work to go to Monterey?
Did you do anything special?
I have trouble for some reason.

 

[eikic1]

Hello, i try to install OC v77 on my cMp
Doesn’t work

Blank screen and put login screen
I try to sellect bootable to mojave installer cant boot but put to mojave drive

How sollution

Thanks

 

[MoerBoer]

Did it work to go to Monterey?
Did you do anything special?
I have trouble for some reason.

Yup, see #3,248

 

[MoerBoer]

Just did a rom dump for fun the see if all is ok. Does the 6 bluetooth controller error have anything to do with this package I'm running? (0.76). I'm getting this unit next week to install, and I hope it will work out of the box? : https://www.ebay.com/itm/274475421781

Firmware 144.0.0.0 (latest)


14 Memory Configs (ok)


0 xml (ok)


2 iCloud Tokkens (ok)


0 Microsoft Certificates (ok)


6 BluetoothActiveControllerInfos (not ok)


2 BluetoothInternalControllerInfos (ok)


2 current-network (ok)


2 AAPL Path Properties (ok)


34432 Bytes free space of 65472

 

[star-affinity]

Yup, see #3,248

So you just changed the "Cpuid1Mask" (replaced that one A with a C), restarted and then ran the Monterey installer from within Big Sur?

I'm on the 0.7.7 OC package, not sure if that makes a difference perhaps.

That WiFi and Bluetooth kit you're getting should work fine I think.

 

[tsialex]

Just did a rom dump for fun the see if all is ok. Does the 6 bluetooth controller error have anything to do with this package I'm running? (0.76). I'm getting this unit next week to install, and I hope it will work out of the box? : https://www.ebay.com/itm/274475421781

Firmware 144.0.0.0 (latest)


14 Memory Configs (ok)


0 xml (ok)


2 iCloud Tokkens (ok)


0 Microsoft Certificates (ok)


6 BluetoothActiveControllerInfos (not ok)


2 BluetoothInternalControllerInfos (ok)


2 current-network (ok)


2 AAPL Path Properties (ok)


34432 Bytes free space of 65472

If you boot between Mojave and Catalina/BigSur/Monterey frequently this happens, Apple changed the syntax of bluetoothActiveControllerInfo and bluetoothInternalControllerInfo with Catalina.

If you don't boot between Mojave and newer releases, something is wrong with your circular log and you probably already have variable multiplication.

Btw, for some yet unknown motive this happens more with BCM946302 AirPortExtremes than with BCM94360 ones.

 

[MoerBoer]

So you just changed the "Cpuid1Mask" (replaced that one A with a C), restarted and then ran the Monterey installer from within Big Sur?

I'm on the 0.7.7 OC package, not sure if that makes a difference perhaps.

That WiFi and Bluetooth kit you're getting should work fine I think.

I did a clean install on another NVME blade, but yes, just did that

 

[MoerBoer]

If you boot between Mojave and Catalina/BigSur/Monterey frequently this happens, Apple changed the syntax of bluetoothActiveControllerInfo and bluetoothInternalControllerInfo with Catalina.

If you don't boot between Mojave and newer releases, something is wrong with your circular log and you probably already have variable multiplication.

Btw, for some yet unknown motive this happens more with BCM946302 AirPortExtremes than with BCM94360 ones.

Thanks for the reply.

Yes, I quad boot between High Sierra, Mojave, Big Sur and Monterey.

So it's "normal" if I read your message correctly?

 

[tsialex]

Thanks for the reply.

Yes, I quad boot between High Sierra, Mojave, Big Sur and Monterey.

So it's "normal" if I read your message correctly?

Not normal and can be a serious issue if you don't have enough VSS space, but it's expected to happen with people that boot between Mojave and newer macOS releases frequently.

Several people bricked in the past because of the variable multiplication/circular log not being garbage collected, usually happens when Apple releases a new software update and the several variables needed to bootstrap the update process fill the NVRAM. This is happening a lot more frequently nowadays with Apple rolling software updates.

The outdated and insufficient NVRAM design is now the Achilles heel of MacPro5,1.

 

[MoerBoer]

Not normal and can be a serious issue if you don't have enough VSS space, but it's expected to happen with people that boot between Mojave and newer macOS releases frequently.

Several people bricked in the past because of the variable multiplication/circular log not being garbage collected, usually happens when Apple releases a new software update and the several variables needed to bootstrap the update process fill the NVRAM. This is happening a lot more frequently nowadays with Apple rolling software updates.

The outdated and insufficient NVRAM design is now the Achilles heel of MacPro5,1.

Oh boy.

Is it also related due to Martin’s package residing on my High Sierra drive as the boot picker?

Is there any way of fixing it if I decide to only stay on Big Sur and Monterey?

 

[tsialex]

Oh boy.

Is it also related due to Martin’s package residing on my High Sierra drive as the boot picker?

Not really, this is more a NVRAM design issue than anything.

You need to remember that this a design from 2008, announced in January 2009 and released in March 2009. The early-2009 Mac Pro came with Leopard and at that time the NVRAM was used very sparingly, nowadays is used frequently for all sort of things.

Booting multiple macOS releases and having the hardware config maxed-out makes the NVRAM volume work with much more pressure than the design intended back in the day and things can and will go wrong…

Is there any way of fixing it if I decide to only stay on Big Sur and Monterey?

You can workaround these issues with a BootROM reconstruction service and flash the never booted BootROM image on a schedule, most people do it every 90 days.

 

[MoerBoer]

Not really, this is more a NVRAM design issue than anything.

You need to remember that this a design from 2008, announced in January 2009 and released in March 2009. The early-2009 Mac Pro came with Leopard and at that time the NVRAM was used very sparingly, nowadays is used frequently for all sort of things.

Booting multiple macOS releases and having the hardware config maxed-out makes the NVRAM volume work with much more pressure than the design intended back in the day and things can and will go wrong…


You can workaround these issues with a BootROM reconstruction service and flash the never booted BootROM image on a schedule, most people do it every 90 days.

Thanks , I suppose my mid 2010 is the same and the 2012 regarding nvram space.

I won’t say my machine is maxed, but I have 2 ssd’s, 2 spinners, 2 nvme’s, rx570 and usb 3.1 pcie card. 32gb ram and 2 x5680’s.

If I recall you render the service, no? Should I contact you via dm for pricing etc?

 

[tsialex]

Thanks , I suppose my mid 2010 is the same and the 2012 regarding nvram space.

Correct, it's exactly the same design from early-2009 to mid-2012.

If I recall you render the service, no? Should I contact you via dm for pricing etc?

I've sent you a PM with instructions/cost.

 

[AKB69]

I created a new "easy to install package" as per many requested (based on the official OpenCore). [The attached package updated to 0.7.7]

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:

1. Boot screen (via GOP for unflashed card, including some Nvidia card)
2. Firmware protection (to run Windows in EFI mode without risking the cMP bootROM)
3. HWAccel (H264 / HEVC hardware decode + encode in Mojave and newer macOS)
4. ability to watch DRM streaming content (Mojave and newer macOS)
5. 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)
6. NVMe and SATA drives on PCIe card show up as internal
7. Support for Apple USB SuperDrive
8. TRIM (regardless trimforce status)
9. Ability to run non-GUI 32bit software in Catalina
10. Ability to reset NVRAM in boot picker (disabled at this moment to align with the native Apple boot manager)
11. 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]
12. 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]
13. Sleep should work (tested on my cMP, but I can't guarantee it also work with your hardware)
14. Possible to run 8x32GB RAM in macOS (user need to mod the config.plist manually. Replace the false below CustomMemory to true)
15. Enable HDMI Audio for some graphic cards
16. 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

1. [Optional] 3x NVRAM reset to avoid some unknown issues.
2. Disable SIP (must do, especially if you performed step 1)
3. 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.)
4. Follow the steps in this video (please turn on and read the subtitle)
   
5. Spoiler: Multi monitors fix for Big Sur

   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.
   
6. 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: 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.

P.S. If you want to support my work, please donate via the following link. Million thanks in advance! https://www.paypal.com/paypalme/martinlo420

[Last update: 24 Jan 2022, OpenCore 0.7.7, Lilu 1.5.9, WhateverGreen 1.5.6, RadeonSensor 0.3.1, AppleALC 1.6.3, FeatureUnlock 1.0.5, SurPlus, MonteRand]

Thanks for this - used your 0.7.7 package and Monterey working fine on my 5,1 (32GB Ram, 3.33 6-core W3680 mac 7950). Just have a couple of questions if anyone can help:

1, I am moving my windows partition to a new HDD - do I need to move the OPenCore to that drive?

2, If so, is it easy to do and how do I 'unbless' the old open core and bless the new one?

 

[rudo.ba]

Hello martin,

last week i updated your OC from 0.7.6 to 0.7.7 (also BigSur from 11.6.2 to 11.6.3, ota) on single core MP 5,1 (32 GB RAM, sata 2 SSD in standard drive bay with system + sata 3 SSD as scratch disk in PCI, also have HDD with clean Mojave, RX 470 4GB, two displays over HDMI and DP).

Problems started with Photoshop - i could work for about hour or so, next it was no longer possible to save work. Save/export dialogs did not appear and cmd-s also did not work. Next, all running apps (Mail, Chrome, InDesign, Photoshop) terminated and i get clean desktop - with no top menu bar nor any items on desktop, just Dock on bottom. I could use power button to invoke dialog with Shut off/restart buttons, and i can successfully restart (with no warning screens), and work for another hour or so.

I tested over the weekend using just chrome and mail, and there were no problems.

I was not sure it was caused by macOS or OC update, so downgraded back to 0.7.6 (simply by overwriting folders in EFI partition as when upgrading, just now with older version 0.7.6). Now, today, i several hours use Photoshop without any issue again. Finally stability.

I'm attaching a few error messages from ethrecheck: looks like some problems with open/save panel service and many Photoshop and InDesign crashes over QuickLook?? (i did not notice any problem with InDesign, just Photoshop, both current and legal versions).

BigSur (11.6.1, next 11.6.2 and 11.6.3, ota) i installed over dosdude’s Catalina (Catalina over existing Mojave), using your OC 0.7.5, next 0.7.6 - both fine. Just now version 0.7.7 is kind of problematic. OK, my path to BigSur is not ideal, but i am lazy to do clean install (if not necessary). And now back with 0.7.6 have fine working system again.

Probably my wild system upgrades caused it, but if anyone else has similar problems with Adobe apps and OC 0.7.7, try downgrade to 0.7.6. (srry used google translate for this EN text).

Update: it happened again, problably for just not so intensive work today (and frequently saving), it last stable longer, look like i can not avoid clean reinstall... so ignore this.

 

[star-affinity]

Thanks for this - used your 0.7.7 package and Monterey working fine on my 5,1 (32GB Ram, 3.33 6-core W3680 mac 7950). Just have a couple of questions if anyone can help:

1, I am moving my windows partition to a new HDD - do I need to move the OPenCore to that drive?

2, If so, is it easy to do and how do I 'unbless' the old open core and bless the new one?

I think the answer to your question is here (on the previous page of this thread):

You can install multiple OpenCore copies on a single cMP. E.g. you can copy your existing OC folder to the Windows drive’s EFI partition, but not delete the old one.

Then you unmount all other EFI partition but only leave the Windows drive EFI partition still mounted, and run the bless tool. In this case, the bless tool will bless the OC that stores on the Windows drive, and disable the original copy (unless you remove the Windows drive, then the cMP should able to boot from the old copy).

The idea is simple, you can install many many copies of OC. But when you only mount one EFI partition and run bless tool, that OC copy will become the master.

 

[kkinto]

2, If so, is it easy to do and how do I 'unbless' the old open core and bless the new one?

I think you just mount the new one with SIP disabled and bless it. You don't have to 'unbless' the old one.

 

[star-affinity]

For some reason it seems I couldn't change the OC location even if I mounted the EFI partition I wanted to use (the one on my Windows 10 drive), copied the ”OC” and ”BOOT" folder from the 0.7.7 package and then ran the ”Bless OpenCore.app”, so I decided to delete OC from the EFI partition I first had it installed on and then run the ”Bless OpenCore.app” to not get any confusion. Bad idea…

I now only get a dark screen when attempting to boot – the OC boot picker won't come up comes up.

Any ideas?

Maybe drag out the drive I originally had OC on and put it back there via my work laptop. Sigh…

 

[prefuse07]

For some reason it seems I couldn't change the OC location even if I mounted the EFI partition I wanted to use (the one on my Windows 10 drive), copied the ”OC” and ”BOOT" folder from the 0.7.7 package and then ran the ”Bless OpenCore.app”, so I decided to delete OC from the EFI partition I first had it installed on and then run the ”Bless OpenCore.app” to not get any confusion. Bad idea…

I now only get a dark screen when attempting to boot – the OC boot picker won't come up comes up.

Any ideas?

Maybe drag out the drive I originally had OC on and put it back there via my work laptop. Sigh…

Try an NVRAM reset (P+R+Cmd+Option), and if 1 is not enough, then do 3 chimes -- it's worked for me in the past when i've encountered that, but YMMV.

 

[star-affinity]

Try an NVRAM reset (P+R+Cmd+Option), and if 1 is not enough, then do 3 chimes -- it's worked for me in the past when i've encountered that, but YMMV.

Thanks. But won't that turn SIP back on? Or not a problem anymore with newer OC versions?

 

[prefuse07]

Thanks. But won't that turn SIP back on? Or not a problem anymore with newer OC versions?

It will re-enable it -- Why do you keep SIP disabled?

 

[0134168]

Thanks. But won't that turn SIP back on? Or not a problem anymore with newer OC versions?

When I installed OCLP, I chose the option to disable SIP. So, though A Cmd+Alt+P+R, SIP stays disabled. Sure you can specify the same in the config into the package.

 

[agejon]

Martin, using your 0.7.7 OC version , I updated from Big Sur 11.6.2 to 11.6.3 and during the process probably the update overwrote my blessed EFI partition.

I needed to re-bless by booting with a rescue OC cdrom I have lying around for everything to work properly again!

PS: My EFI resides in an external usb stick!

 

[star-affinity]

It will re-enable it -- Why do you keep SIP disabled?

Think it was related to me switching to Windows boot with the tool Boot Champ (pre-OpenCore):

Download Bootchamp for Mac | MacUpdate

Download the latest version of Bootchamp for Mac for free. Read 2 user reviews and compare with similar apps on MacUpdate.

www.macupdate.com

Also in the instructions on page 53 when installing the OpenCore package:

1. [Optional] 3x NVRAM reset to avoid some unknown issues.
2. Disable SIP (must do, especially if you performed step 1)

Anyway, I managed to get OC working again by copying the 0.7.7 OC package back onto the EFI partition of the drive I originally had it on. Not sure why my computer doesn't seem to like using the OC 0.7.7 I have installed on the EFI of my Windows 10 drive. Any ideas?



I was also a bit surprised to again see that ”NO NAME” drive in the OC boot picker upon the first restart after getting OC working again. I accidentally started from ”Macintosh HD” instead of ”MacOS” which is my main install with Big Sur. I think the Macintosh HD partition was created by the Monterey installer and now when I accidentally tried to start from it it didn't work, presumably because CpuID” is incorrectly set in in the ”config.plist”.

After trying to boot from the ”Macintosh HD” it restarted after a minute and then the OC boot picker looked like this:



So for some reason the ”NO NAME” volume, one of the two ”Recovery 11.6.3 (dmg)” went away?

Does this makes sense to anyone?
How can I find out what that ”NO NAME” partition is about? ?

 

[prefuse07]

@star-affinity
FYI -- you only need SIP disabled for the initial bless.... After you've blessed, if you want to re-enable it, you can.