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
I use wireless Apple keyboard and trackpad without any issue.
By the way, when I keep an usb gaming mouse plugged to the cMP, at every boot, the optical drivers opens its trays.
That is what it was. I plugged in a wired mouse and it worked fine. Is there any plans to make is selectible with keyboard? Even a wired keyboard doe not work.
I installed windows on a seperate drive and played some games yesterday and had a blast. Then when I booted back onto Catalina finder would freeze and just do the spinning wheel. I left it for an hour and it still was there. This went on till 5 this morning when I took out the windows drive and booted again. It still acted all wonky but when i let is chill for a minute things seems to work out. I dont trust the Macos right now. Has anyone else had these issues? I just went from 5.1 to 5.8 two days ago.
The plan is to release OpenCore 0.5.9 package with OpenCanopy, that may support your wireless mouse / keyboard better.
Catalina still just for testing for me at this moment. My daily use drive still Mojave.
Just updated to the latest 10.14.6 (18G5033), and 10.15.5 (19F96). HWAccel works as expected on both.
To update Catalina, please turn on VMM and turn off SMBIOS spoofing as per the following video.
(There is no need to turn on VMM for Mojave update. But as precaution, you can turn off SMBIOS spoofing)
And after update, please turn off VMM, and turn SMBIOS back on for HWAccel.
To update Catalina, please turn on VMM and turn off SMBIOS spoofing as per the following video.
And after update, please turn off VMM, and turn SMBIOS back on for HWAccel.
Last edited:
There is no need to touch the VMM flag for Mojave.
Turn off SMBIOS spoofing is more for precaution.
Anyway, post #1730 updated to avoid confusion.
From memory, someone tested, even with HEVC hardware encoding, still black screen only.
But I am not sure if there is any changes with the latest OS. Or if different SMBIOS spoofing in OpenCore can make any difference.
I tried Sidecar a few days ago (using freeSidecar) at a friends MacPro (essentially same configuration as mine) with OpenCore 5.7 and an iPad Pro and I only got a black screen. Turning hardware acceleration on or off made no difference. Even trying DuetDisplay resulted in a black screen with the MacPro interestingly, while working fine with my 2012 MacBook Pro.
Hi,
I have Radeon Vii and had problem with Lilu and Whatevergreen kext method unlocking the hardware acceleration under Mojave.
Sometimes, kinda often I got gui screen freezes with mouse working forcing me to hard shutdown (gpurestart fail in console). I could trigger it using Photos.app or changing wallpapers back and forth couple times.
I want to try OpenCore now, but I see it uses Lilu and Whatevergreen kext too, so could someone please check for me if changing wallpapers back and forth couple times will freeze the screen, force shutdown because of failed gpurestart?
I wonder, maybe I need a clean and full reinstall?
I have Radeon Vii and had problem with Lilu and Whatevergreen kext method unlocking the hardware acceleration under Mojave.
Sometimes, kinda often I got gui screen freezes with mouse working forcing me to hard shutdown (gpurestart fail in console). I could trigger it using Photos.app or changing wallpapers back and forth couple times.
I want to try OpenCore now, but I see it uses Lilu and Whatevergreen kext too, so could someone please check for me if changing wallpapers back and forth couple times will freeze the screen, force shutdown because of failed gpurestart?
I wonder, maybe I need a clean and full reinstall?
Yes sir, I'm on the newest version and I tried today the kext mod and the same happens.
I had this problem with earlier versions too.
If I disable the mod, everything is working great, no gpurestarts.
I wonder what I'm doing wrong
I had this problem with earlier versions too.
If I disable the mod, everything is working great, no gpurestarts.
I wonder what I'm doing wrong
It definitely not common for Radeon VII.Yes sir, I'm on the newest version and I tried today the kext mod and the same happens.
I had this problem with earlier versions too.
If I disable the mod, everything is working great, no gpurestarts.
I wonder what I'm doing wrong
The RX580 used to suffer from this problem, however, 10.14.6 seems fixed the issue. At least, I can't hit this bug anymore on my cMP no matter how hard I try (RX580).
For Radeon VII, I can't quite remember similar report, and my own Radeon VII perform really flawlessly in 10.14.6.
If possible, please find a spare drive and try clean installation.
Hi, as we agreed, fresh install did help, all is working great with the kext mod. No more GPUs restarts. Thanks for help!
I have this setup, with an Apple wireless BT keyboard and it works perfectly during the boot selector. Be it with OC or with the built-in Apple one (when I still had a GPU that would display it).
@h9826790 thank god I follow you on FB too, otherwise I would have missed the update to 0.5.9
How about updating post #1 instead? That would make it easier to track.
Anyway, great job as always. With OpenCanopy becoming the bootpicker, I have a couple of questions:
- can we reset nvram from the bootpicker like we could do before? and if so where is it in the plist file?
- where do you define the background color, I'd like mine to mimic the normal mode, not dark mode.
Thanks!
How about updating post #1 instead? That would make it easier to track.
Anyway, great job as always. With OpenCanopy becoming the bootpicker, I have a couple of questions:
- can we reset nvram from the bootpicker like we could do before? and if so where is it in the plist file?
- where do you define the background color, I'd like mine to mimic the normal mode, not dark mode.
Thanks!
I am too lazy to completely re-write post #1. But I will put a link / info at the top for existing OpenCore users.
Change this to "false" will put you back to the light grey background
We better discuss non HWAccel related settings in the OpenCore thread. Anyway, you can search "AllowNvramReset" in the config.plist
There are many words that can be used to describe your efforts here, and of other things I can be sure. But "lazy" isn't one of them!
Thanks for all you do!