Thank you VERY much for this advice, h9826790! I will give this a go and let you know how it all shakes out. I'm looking forward to seeing the results of working with your MLOCP. I appreciate the quick reply and sharing your time with me! All the best to you and yours! 🤞🏼 ~ EMJWAYLZ
Got a tip for us?
Let us know
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
- Thread starter h9826790
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Hello guys,
I have a MacPro 2012 upgraded to dual 3.33Ghz/48Gb/Radeon RX6800 XT and booting BigSur 11.6.4 / Monterey 12.0.1 / WindowsPro 10 from OC installed a NVME blade on a PCI-E card (the one with BigSur installed on it).
I was wondering if it is safe to install OC 0.9.2 and upgrade BigSur to 11.7.7 and Monterey to 12.6.6 ?
I am pushing my MacPro to the limit until Apple Silicon can run natively Unreal Engine 5.x and support all the features available only on Windows unfortunately at the moment.
Thank you for your help keeping that amazing hardware alive !
I have a MacPro 2012 upgraded to dual 3.33Ghz/48Gb/Radeon RX6800 XT and booting BigSur 11.6.4 / Monterey 12.0.1 / WindowsPro 10 from OC installed a NVME blade on a PCI-E card (the one with BigSur installed on it).
I was wondering if it is safe to install OC 0.9.2 and upgrade BigSur to 11.7.7 and Monterey to 12.6.6 ?
I am pushing my MacPro to the limit until Apple Silicon can run natively Unreal Engine 5.x and support all the features available only on Windows unfortunately at the moment.
Thank you for your help keeping that amazing hardware alive !
Should be safe.
You can upgrade to 0.9.2 first. Then you can safely upgrade Big Sur and Monterey.
Is there a way to set the maximum OS to be at 12? I'm missing security updates as it's only promoting me to upgrade to 13 and I have to download updates like 12.6.6 manually. I saw on the OC site that it might be possible by manually configuring bits in SIP.
Is this even possible? Am I barking up the totally wrong tree?
Thank you so so sosososoooo much for all you do! Your work has kept me daily driving my cMP for years.
Is this even possible? Am I barking up the totally wrong tree?
Thank you so so sosososoooo much for all you do! Your work has kept me daily driving my cMP for years.
Last edited:
Thanks for the reply! Actually I already have Monterey installed. What I'd like it to do is to stop prompting me to update to Ventura, and instead supply only Monterey Updates like what a mp6,1 with stock boot would since Monterey is the newest officially supported OS for that Machine.
Last edited:
Unfortunately Option 4 is not working for me on Monterey 12.6.6.
My wifi card is a BCM4322.
Does this work only up to Big Sur?
Option 5 is working great!
Others reports also only work up to Big Sur. Monterey seems need system files patching. Which OCLP will do.
That prompt for Ventura will be there.
For future Monterey update, you have to follow that video's step to make it appear.
But if you don't want to see the red dot (which should be for Ventura in normal config), you may use the termial command to make it disappear
Code:
defaults write com.apple.systempreferences AttentionPrefBundleIDs 0 && killall DockThank you.
I updated to 0.9.2 first. Rebooted everything was fine.
I updated both BigSur (to 11.7.7) and Monterey (to 12.6.6) and bluetooth is now not working.
<dict>
<key>Arch</key>
<string>x86_64</string>
<key>BundlePath</key>
<string>Bluetooth-Spoof.kext</string>
<key>Comment</key>
<string>Bluetooth Patch for BRCM2046 and BRCM2070</string>
<key>Enabled</key>
<false/>
<key>ExecutablePath</key>
<string></string>
<key>MaxKernel</key>
<string>21.99.99</string>
<key>MinKernel</key>
<string>21.0.0</string>
<key>PlistPath</key>
<string>Contents/Info.plist</string>
</dict>
<dict>
<key>Arch</key>
<string>x86_64</string>
<key>BundlePath</key>
<string>BlueToolFixup.kext</string>
<key>Comment</key>
<string>Fix Legacy Bluetooth</string>
<key>Enabled</key>
<false/>
<key>ExecutablePath</key>
<string>Contents/MacOS/BlueToolFixup</string>
<key>MaxKernel</key>
<string>21.99.99</string>
<key>MinKernel</key>
<string>21.0.0</string>
<key>PlistPath</key>
<string>Contents/Info.plist</string>
</dict>
<dict>
<key>Arch</key>
<string>x86_64</string>
<key>BundlePath</key>
<string>BlueToolFixup.kext</string>
<key>Comment</key>
<string>Fix Legacy Bluetooth</string>
<key>Enabled</key>
<false/>
<key>ExecutablePath</key>
<string>Contents/MacOS/BlueToolFixup</string>
<key>MaxKernel</key>
<string>21.99.99</string>
<key>MinKernel</key>
<string>21.0.0</string>
<key>PlistPath</key>
<string>Contents/Info.plist</string>
</dict>
Any idea of what I should do ?
Thank you for your help !
Thanks, I'll look into it!
Maybe I can "merge" the two?
By finding out what OCLP does that makes wifi works so I can keep it in your version.
Has a way been found yet to enable hardware acceleration in 2010 and 2011 "silverback" iMacs (or other Macs) with their original video cards? (It is irksome to be able to run Mojave flawlessly on 2009 C2D "blackback" iMacs and laptops, but not the '10-'11 series.)
First, how to enable something that is not present in the hardware? Apple VideoToolbox API requires ASICs (UVD/VCE) from GCN4 generation (the Polaris GPUs / RX 460/560/480/580) and newer AMD GPUs.
Second, AMD hardware acceleration is not for the UI, it's for enabling hardware assistance of video decompression/compression/colour grading/pixel moving with the specialised ASICs present in the AMD Polaris and newer AMD GPUs.
What precludes a patch from kiting the toolbox functionality from High Sierra? (What you're basically telling me is that Apple planned-obsolesced 2010 and 2011 iMacs with stock-Mojave, but their widget requiring "newer" GPUs somehow forgot about the even older ones in 2009 iMacs.)
You are mixing different things.
It's a missing hardware requirement - earlier GPUs than GCN4.0 generation do not have the required dedicated ASICs or have previous ASICs version that do not have the basic funcionality to be compatible with Apple VideoToolBox API, nothing to do with Mojave or High Sierra, Metal or OpenGL support.
Mojave moved the UI engine from OpenGL (Quartz Extreme/Core Image) to METAL, the change is unrelated to the VideoToolbox API that here in this thread is called AMD Hardware Acceleration.
METAL is supported with AMD GPUs since the AMD GCN3.0 generation of GPUs, so, AMD Radeon 7xxx GPUs and newer.
Last edited:
Alright then, what precludes a (hypothetical dosdude1 or OCL or ???) patch from kiting whatever functionality was previously employed by High Sierra?
(Given that High Sierra and Mojave are the last versions of the MacOS to support 32bit apps and HFS+, I'm rather surprised that an OS hard-fork project isn't already underway somewhere.)
Last edited:
Didude patcher and OCLP added the necessary OpenGL support years ago, there is nothing to about the poor performance of GCN2 GPUs with the heavier METAL UI of Mojave and newer macOS releases. Read bout the non-METAL GPU support and OCLP to know more.
Hi all,
I have successfully moved to Big Sur 11.7.7 with my Mac Pro 5,1 using the OC package distributed here and USB ceased to be hot plug. If for any reason I'd unplug my mouse (to reset the profile used for example or whatever other reason), when I plug it back, it wouldn't get power and wouldn't get recognized.
Is there a fix to this? Has anybody else seen anything similar?
I have successfully moved to Big Sur 11.7.7 with my Mac Pro 5,1 using the OC package distributed here and USB ceased to be hot plug. If for any reason I'd unplug my mouse (to reset the profile used for example or whatever other reason), when I plug it back, it wouldn't get power and wouldn't get recognized.
Is there a fix to this? Has anybody else seen anything similar?
I think your issue is that these keys should be enabled and as you see they are all "false".
That's how they should look like I guess
<key>Enabled</key>
<true/>
At least that's how I made my WiFi working here...
Hope this helps
Older Intel southbridges like the X58 ICH10R Apple used with the 2009 to 2012 Mac Pros have two different USB controllers, OHCI for USB v1.0/1.1 connections and EHCI for anything USB v2.0.
Apple removed support for OHCI controllers after Catalina, so, you only have hot-plug for the still supported EHCI devices, anything that is OHCI, like HUD devices (keyboard, mice and etc), stops working if you reconnect after power on - this is the expected USB functionality with Big Sur and it's even worse with Monterey.
To workaround the removal of OHCI controller support, install a USB v2.0 or v3.0 hub between your OHCI devices and the Mac Pro USB port, this forces an EHCI connection even for USB v1.0 or v1.1 devices and will give back hot-plugging.
Thanks for the explanation...
Isn't there a way to plug back an older driver like for Airport/Bluetooth?
Thanks for the explanation...
Isn't there a way to plug back an older driver like for Airport/Bluetooth?
Nothing that really works since Apple removed it macOS wise, the USB v2.0 or v3.0 hub solves it cheaply, transparently and definitively.
Do not forget that it's even worse with Monterey, so, buy a hub.
Myeah, I have one, I'll be testing this. Thanks a million!
In the meantime, I'm trying to assess the pros and cons and see if I like the upgrade after all
Although the OS feels nicer, I lost 32 bit AU compatibility with Logic even through 32 lives, a whole bunch of Apps and now this
Feels a bit sour...
Myeah, I have one, I'll be testing this. Thanks a million!
In the meantime, I'm trying to assess the pros and cons and see if I like the upgrade after all
Although the OS feels nicer, I lost 32 bit AU compatibility with Logic even through 32 lives, a whole bunch of Apps and now this
Feels a bit sour...
Just use a different disk for Mojave and boot it when you have to run 32bit apps. Add -no_compat_check to your boot-args to boot Mojave with the MacPro7,1 spoofing.
Actually, both Big Sur, and Mojave boot up just fine... I'm not sure if I have MacPro7,1 spoofing... how to tell?