Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

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

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.
Gustav Holdoff said:
I give increased speed to the both CPU in order to especially cool the northbridge
Moreover, I leaned the side panel as far as the expansion card for 4xNVME allowed.
Click to expand...
What you can do to help cool the Northbridge is to fit in a small fan powered from the optical drive bay to direct more air across the northbridge heatsink. Noctua fans are quiet running and they have a small one which will work. This is in addition to checking the thermal compound and the spring clips (which I did already).

My dual CPU 5,1 doesn't have any optical drives anymore (don't need them) so that works fine. Keeps the Northbridge around 55ºC, rather similar to the single CPU machine I also have. It also prevents the dual CPU machine sounding like a screaming banshee.
 
h9826790 said:
There are few possible reasons. But the 1st thing to make sure is that the package's integrity.

You may simply re-download the latest package, and replace your existing OpenCore, then see if Monterey can boot.

Since you can still boot that Monterey once VMM is enabled. So, the Monterey itself should be good. You may also try if can you boot VMM on + SMBIOS spoofing on. In this case, CPU turboboost will be disabled, but 5700XT's HWAccel should be enabled. It also allow us to know if it's the VMM flag make your Monterey unbootable, or the SMBIOS spoofing makes it unbootable.

Last but not least, please perform 4x NVRAM reset. More than one users believed that they have OpenCore / macOS issue, but end up is NVRAM issue.
Click to expand...
I've made the test, when I turn only the VMM flag ON and don't touch the updateSMBIOS, Monterey boot without problem, then my room is 9144.0.9.7.0, and I've full HWAccel.

When I restore VMM Flag to default and set updateSMBIOS ON (false), it don't boot. and of course restore the original config.plist, monterey don't boot, only Bigsur and Win10.

So the problem is with the VMM FLAG.
 
Hi Martin,
Thank you for your many years of support with this package. As Monterey is soon to be unsupported, I'm starting to plan my jump to OCLP to get the latest version of macOS. What would be the proper way to remove and then install OCLP without having to reinstall macOS? I've seen videos of people just running the OCLP installer over your already installed package but I assume that wouldn't be advised. Would we just have to mount the EFI partition and delete the OC and BOOT folders before running OCLP with macOS still booted?
 
14dcutaneo said:
Hi Martin,
Thank you for your many years of support with this package. As Monterey is soon to be unsupported, I'm starting to plan my jump to OCLP to get the latest version of macOS. What would be the proper way to remove and then install OCLP without having to reinstall macOS? I've seen videos of people just running the OCLP installer over your already installed package but I assume that wouldn't be advised. Would we just have to mount the EFI partition and delete the OC and BOOT folders before running OCLP with macOS still booted?
Click to expand...
You may manually remove the OC and BOOT folder, but that's not required. OCLP installer should replace all relevant files automatically.
 
  • Like
  • Love
Reactions: TheStork, crjackson2134 and 14dcutaneo
h9826790 said:
You may manually remove the OC and BOOT folder, but that's not required. OCLP installer should replace all relevant files automatically.
Click to expand...
Thanks for the clarification :). I'm holding on to Monterey as long as I can, but I know my days are numbered
 
basslik said:
So you all think Sonoma will never fly with these 5,1's
Click to expand...
Anything beyond Monterey will require root patching, which is fine but can cause some native features to act weird or not at all such as continuity camera or some DRM content on Safari. I have Sonoma on a second Mac Pro 5,1 and it runs just fine
 
I strictly use my 5,1 for recording bands with pro Tools. I never used for anything else, other than the browser for updates for my plugins. I might have to give it a try and see how Pro Tools run on Sonoma.

thanks
 
h9826790 said:
There are few possible reasons. But the 1st thing to make sure is that the package's integrity.

You may simply re-download the latest package, and replace your existing OpenCore, then see if Monterey can boot.

Since you can still boot that Monterey once VMM is enabled. So, the Monterey itself should be good. You may also try if can you boot VMM on + SMBIOS spoofing on. In this case, CPU turboboost will be disabled, but 5700XT's HWAccel should be enabled. It also allow us to know if it's the VMM flag make your Monterey unbootable, or the SMBIOS spoofing makes it unbootable.

Last but not least, please perform 4x NVRAM reset. More than one users believed that they have OpenCore / macOS issue, but end up is NVRAM issue.
Click to expand...
Hi martin,

I have another mac pro5.1, it belongs to my son and I installed BigSur on an SSD in PCIe 4 slot and two archive SATA drives, OC V0.9.7 is in one of them , Win10 is on another SSD on optical bay. Everything works well. the thing is that when I unplug my recent Monterey from my mac and install it on my son's mac in the 3 pcie slot, it works fine and the config.plist is in default mode, and I don't understand Why. I swapped his BigSur with mine just to be safe, and Monterey won't boot on my Mac Pro. so what? is it an error with the drive where OC is installed? if so, bigsur and win10 should not boot and the boot selection will not show! any idea ?
 

Attachments

  • 1706994269642.png
    1706994269642.png
    312 bytes · Views: 61
  • 1706994860017.png
    1706994860017.png
    312 bytes · Views: 58
mohnumber7 said:
Hi martin,

I have another mac pro5.1, it belongs to my son and I installed BigSur on an SSD in PCIe 4 slot and two archive SATA drives, OC V0.9.7 is in one of them , Win10 is on another SSD on optical bay. Everything works well. the thing is that when I unplug my recent Monterey from my mac and install it on my son's mac in the 3 pcie slot, it works fine and the config.plist is in default mode, and I don't understand Why. I swapped his BigSur with mine just to be safe, and Monterey won't boot on my Mac Pro. so what? is it an error with the drive where OC is installed? if so, bigsur and win10 should not boot and the boot selection will not show! any idea ?
Click to expand...
This beyond my understanding as well.

The Monterey works on another 5,1, which means the Monterey itself is good.

It means, your "can't boot Monterey with VMM off" issue is hardware issue. And VMM should only be only CPU related. However, as you said, your 5,1 can boot Big Sur flawlessly. It can also run Windows 10 without any trouble. So, doesn't feels like the CPU itself is faulty.

Anyway, did you try 4x NVRAM reset yet?
 
not yet, cause my gpu is 5700xt amd, I've mojave installed in an emergency drive but I guess it will not show anything! I must use a gpu supported by mojave if I want to see something. I should use the vega 64 of my son's mac pro.
 
mohnumber7 said:
not yet, cause my gpu is 5700xt amd, I've mojave installed in an emergency drive but I guess it will not show anything! I must use a gpu supported by mojave if I want to see something. I should use the vega 64 of my son's mac pro.
Click to expand...
I know it's quite a bit of work to do to swap GPU. However, from experience, 4x NVRAM reset is one of the possible solution. You have to try it at some stage.

If you haven't flash your 5,1 with EnableGop yet, you may also go for that way. So that your 5700XT will able to display boot screen natively on your 5,1. Which makes your life much easier (if 4x NVRAM reset disable OpenCore unintentionally).
 
  • Like
Reactions: mohnumber7
my mac pro is not flashed with EnableGop, I don't know this method and if it's safe to use it. I think I'll go with the 4X NVRAM, by this I must heard the chime sound 4 times include the first one?
 
h9826790 said:
I created a new "easy to install package" as per many requested (based on the official OpenCore). [The attached package updated to 0.9.8]

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 packages (0.9.4 and before) included Clover Configurator (for mounting the EFI partition only, please do NOT use it to edit the OpenCore config plist) 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). Since 0.9.5, the Clover Configurator (which we use it only mount the EFI partitions) is replaced by Macschrauber's Mount EFI script (the Bless OpenCore script is also credit to Macschrauber).

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. The auto detect HiDPI function may not work correctly for ultra wide screen. For those who are running ultra wide monitor, the Apple logo may be too large 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][AVXPel is also included. another credit to Syncretic][ASPP-Override is included for macOS 12.3, credit to dortania]
  13. Sleep should work (tested on my cMP, but I can't guarantee it also work with your setup)
  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)
  17. Possible to run AQC107S 10Gbps network in Monterey 12.3 and newer (credit to Jazzzy)
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". Or by Macschrauber's ROM dumper)
  • If you want to test run 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.
  • Also for RX580, users reported that they can't see the screen during macOS installation / update. Analysis shows that there is bug in macOS. When multiple monitors connected, the installation / update will process as expected, but all screens may remain black. Therefore, for RX580 (may be also applicable to other Polaris GPU), please only connect one monitor when you want to install / update macOS (if you prefer to able to see the progress).
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 (if the newer package has compatibility issue. You may download the older package, same installation procedures.)
  4. Follow the steps in this video (please turn on and read the subtitle) [N.B. some tools are updated, but they are very self explanatory. Therefore, I have no plan to create another video just to show how to use the new tools at this moment]
  5. 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: 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.

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:16 Feb 2024, OpenCore 0.9.8, Lilu 1.6.7, WhateverGreen 1.6.6, RadeonSensor 0.3.3, AppleALC 1.8.9, FeatureUnlock 1.1.5, SurPlus, AVXpel, ASPP-Override]
Click to expand...
Thats to

h9826790​

to all the effort work done to keep the updates I was waiting for this one. Confirm that HypeV and sanbox is working under Windows 10 22H2 Great job!!

​

 

Attachments

  • Screenshot 2024-02-14 225153.jpg
    Screenshot 2024-02-14 225153.jpg
    327.6 KB · Views: 89
  • Like
Reactions: h9826790
Hi

Im using Martin Lo Package on Monterey

I was wondering if i can i install the Geforce-Kepler-patcher over martin Lo Package to fix my issues with my NVIDIA Kepler Quadro K600 GPU as its not working properly

Thanks
 
IMG_5115.jpeg
I noticed I started having a series of hangs recently. I’m running the latest Monterey OS.

When I boot it into recovery disc, First Aid stated I need to run FSCK. When I booted into single user mode, I was not able to choose the correct disk.

Is there any other options to attempt to repair this hard drive?
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back