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
Easy.
The reason is because VideoProc NOT aways shows the GPU that provide HWAccel in that Hardware Info page. It simply detect whatever the first GPU detected in the system. In this case, the Titan.
The HWAccel is actually provided by the AMD GPU, but just VideoProc shows the Nvidia GPU's name.
I have this on my own Hackintosh indeed.
The Intel iGPU doing the HWAccel, but VideoProc shows the 1080Ti's name.
Until Nvidia provide driver for macOS again, it's impossible for us to have any Nvidia NVENC / NVDEC function in macOS. NVDEC / NVENC is owned by Nvidia. The associated driver can only be provided by Nvidia. And they never ever release any driver / software to enable Nvidia HWAccel in any OSX / macOS.
It is not only Videoproc which is fooled. Activity monitor is too.
Look at the VTDecoderXPCService:
But VTDecoderXPCService still under RX480.
Utilisation rate is another matter of course.
Wondering if someone can help me. Not sure where to post this really..
I am running OC 0.6.2, runs great, quick to load boot picker.
But then when I log into my Mojave SSD running off the NVME, it takes at least 8-10 minutes for the system to completely load up after I log in. I don't have much on this particular drive as it's my nearly clean boot drive - only have macs fanc control, a couple of media apps (VLC, plex), and my VPN on it. It would also stop loading up any of my apps I want to start until it finishes.....just the bouncing icon on the dock.
I literally cannot touch the mac until its done loading up whatever it is in the background. I might as well brew a tea after starting it up!
I've tried CCC onto a SATA SSD and then wiping and cloning back to the NVME but still have the same problem. Windows 10 however, runs fine so I am inclined to believe its something to do with the macos side of the installation.
OC itself running off a blank SSD. Before I installed opencore, mojave ran great off the SATA SSD.
ANOTHER issue I found was I could not use recovery to reinstall macos, not sure if thats a problem with my OC install. I also am unable to install Catalina as it thinks I need a firmware update but I am not worrying about that for now.
Been pulling my hair out on this. Any advice would be appricated!
Specs;
4,1 -> 5,1
X5680*2
PCIE slots;
Vega 56
NVME drive
SATA PCIE card
USB 3.0 card.
HDD:
1x SSD + 1x HDD in optical drive bay
3x HDD in normal drive bays
1x NVME in PCIE slot 2.
I am running OC 0.6.2, runs great, quick to load boot picker.
But then when I log into my Mojave SSD running off the NVME, it takes at least 8-10 minutes for the system to completely load up after I log in. I don't have much on this particular drive as it's my nearly clean boot drive - only have macs fanc control, a couple of media apps (VLC, plex), and my VPN on it. It would also stop loading up any of my apps I want to start until it finishes.....just the bouncing icon on the dock.
I literally cannot touch the mac until its done loading up whatever it is in the background. I might as well brew a tea after starting it up!
I've tried CCC onto a SATA SSD and then wiping and cloning back to the NVME but still have the same problem. Windows 10 however, runs fine so I am inclined to believe its something to do with the macos side of the installation.
OC itself running off a blank SSD. Before I installed opencore, mojave ran great off the SATA SSD.
ANOTHER issue I found was I could not use recovery to reinstall macos, not sure if thats a problem with my OC install. I also am unable to install Catalina as it thinks I need a firmware update but I am not worrying about that for now.
Been pulling my hair out on this. Any advice would be appricated!
Specs;
4,1 -> 5,1
X5680*2
PCIE slots;
Vega 56
NVME drive
SATA PCIE card
USB 3.0 card.
HDD:
1x SSD + 1x HDD in optical drive bay
3x HDD in normal drive bays
1x NVME in PCIE slot 2.
AFAIK, CCC won’t clone the recovery partition automatically. But they provide you an option to fix that manually (select the hard drive at the bottom left corner, then you should able to create a recovery partition on the MVMe).
Which NVMe you are using right now?
If the same OS works fine in a SATA SSD, but not MVMe, then I can only expect that’s the NVMe’s problem.
The NVME is a PNY XLR8 running off a Sabrent adapter with heatsink. I'm pretty sure is compatible as the blade uses an E12 controller (I went through the NVME thread before buying). REALLY strange thing is, once the NVME does start up after log in (waiting 10 mins!) everything runs great for the most part, and I get 1200/1400MB/s read/write on blackmagic speed test......
One of my troubleshooting steps from a few nights ago was booting off the SATA SSD, and trying to fresh Mojave install onto the NVME and I can't even do that as the install is blocked....something about needing a firmware update?! Would it be worth removing all my HDD and opencore SSDs, leaving only the NVME and my Mojave SATA SSD, boot up that SSD -without- OC, try a Mojave install to NVME -without- OC, then install my OC SSD again as this seems to be blocking my OS install?
Hi,
Thanks for the package.
I've an issue with Big Sur, when trying to boot from the USB installer I get the round with a bar sign. If I try to launch the installer from Catalina, it told me I've to upgrade my rom to install on APFS disks.
My config:
- cMP 5,1
- RX580 (flashed)
- opencore 0.6.3 (from this thread)
- catalina (dosdude version) 10.15.7 (supplemental update 2 installed)
- bootrom 144.0.0.0.0
TIA
Thanks for the package.
I've an issue with Big Sur, when trying to boot from the USB installer I get the round with a bar sign. If I try to launch the installer from Catalina, it told me I've to upgrade my rom to install on APFS disks.
My config:
- cMP 5,1
- RX580 (flashed)
- opencore 0.6.3 (from this thread)
- catalina (dosdude version) 10.15.7 (supplemental update 2 installed)
- bootrom 144.0.0.0.0
TIA
There is a board ID injection to activate HWAccel if you are using my OC package. This may trigger that firmware update issue for some MacOS installer.
You may disable SMBIOS spoofing or even temporarily remove OC for installing Mojave onto your NVMe. (The associated video tutorial in post #1314. The tutorial for enable Catalina installation can also fix that firmware update issue)
But TBH, if you can boot fine with the SATA SSD, why not simply leave the OS at there, and use the NVMe as project drive? There is little to no difference on performance or system responsiveness for most normal daily use anyway.
I have had this setup and it works perfect, i have catalina (nvme) and windows 10 (ssd sata). i think i have open core 0.5.8. now the new os big sur shows up as an update, i want to upgrade but i dont wanna mess up anything.
what do i need to enable or disable to make the upgrade?
You are amazing thanks so much for giving life to this old machines!
You can simply update to 0.6.3, then install / run Big Sur.
I will add a video about how to update OC in post #1314
Last edited:
Im extremely happy to report back, it 100% worked perfect, just as you said.
I followed your video of how to upgrade my opencore to 0.6.3, then i install the final release of big sur and installed it, i did an upgrade from catalina.
thats it. i only changed the plist to make my 4k monitor look right on the boot picker.
is there another configuration i should make?
also my original wifi card still doesn't work on big sur.
does anyone know how to make it work?
it does work perfectly on my windows 10 installation.
Thanks Martin! you are amazing! thanks!!
If anyone knows how to make the original Wificard work on 5,1 and Big Sur that would be great. even windows 10 recognizes it just fine. this will help many people that have not upgraded to a different wifi card. thanks so much!
Take a look here perhaps:
OpenCore on the Mac Pro
Another huge step in getting BCM4322 to work in Catalina and Big Sur https://github.com/khronokernel/IO80211-Patches Stock IO80211Family kext from Mojave already works in Catalina, but there were kernel panics when entering recovery because of collission with Catalina's version. Big Sur did...
forums.macrumors.com
Check this thread and this post and use on of the patchers. These address your problem. It is a little bit bold to try an installer on an unsupported machine expecting everything will be working as normal.... at least the micro patcher does the trick.
Thanks so much!Take a look here perhaps:
OpenCore on the Mac Pro
Another huge step in getting BCM4322 to work in Catalina and Big Sur https://github.com/khronokernel/IO80211-Patches Stock IO80211Family kext from Mojave already works in Catalina, but there were kernel panics when entering recovery because of collission with Catalina's version. Big Sur did...
has anyone tried that patch?
i have a perfect setup, little worried to messed up
I'm going to give it a try on a 2012 Mac mini that I use to do Zoom calls from my couch. I took the recommended config for 0.6.3, I added the Mojave kexts into the OC kext file and the recommended entries for the config.plist (I've just made them non-function for the time being). I got OC installed on a USB EFI and it is downloading and installing Big Sur as I write. Once it completes installing, I'll made the entries functional in the plist and see what we get. Will report back later tonight.Take a look here perhaps:
OpenCore on the Mac Pro
Another huge step in getting BCM4322 to work in Catalina and Big Sur https://github.com/khronokernel/IO80211-Patches Stock IO80211Family kext from Mojave already works in Catalina, but there were kernel panics when entering recovery because of collission with Catalina's version. Big Sur did...
I can report that it works on a 2012 Mac mini built-in BT/WiFi. I took the default config from the recommended 0.6.3 OpenCore, added the patched Mojave kext to the kext folder, and the recommended code to the config.plist. I removed the MCEReporter entry and disabled the Mojave WiFi entries (at least for the install phase). I put OC on the EFI of a USB drive, disabled SIP, blessed and rebooted. Software Update recognized the 'need' for Big Sur so I went through the install and when complete went back into the config and enabled the WiFi entries, rebooted and there it was - old 802.11n WiFi and Big Sur running on an unsupported mini.Take a look here perhaps:
OpenCore on the Mac Pro
Another huge step in getting BCM4322 to work in Catalina and Big Sur https://github.com/khronokernel/IO80211-Patches Stock IO80211Family kext from Mojave already works in Catalina, but there were kernel panics when entering recovery because of collission with Catalina's version. Big Sur did...
This is pretty awesome!!
Do you have a written guide? Or some screen shots? Bit new to the OC game here.
Hi, I spent the last two days modding my Mac 5.1. Now everything is fine but the HW acceleration doesn't work. I have a Sapphire RX580 8GB. I did the last OC installer and tried even the suggest way using the Whatevergreen in the Lilo-Container.
But when I enter the: "sudo nvram boot-args="shikigva=96 shiki-id=Mac-7BA5B2D9E42DDD94"" I get the error: "nvram: Error setting variable - 'boot-args': (iokit/common) general error". SIP is disabled. Can anyone help me?
best regards
Lukas
But when I enter the: "sudo nvram boot-args="shikigva=96 shiki-id=Mac-7BA5B2D9E42DDD94"" I get the error: "nvram: Error setting variable - 'boot-args': (iokit/common) general error". SIP is disabled. Can anyone help me?
best regards
Lukas
Do not mix use different methods.
If you installed my OC package, do NOT install WhateverGreen etc, or do that boot argument in terminal. OC has all of them included.
I have dual E5520 2.26 Ghz xeons in my 4,1->5,1 Mac Pro, I want to install Opencore but not Catalina or Big Sur, still on 10.14.3 because sound stuttering.
Will I have problems if I install Opencore?
Will I have problems if I install Opencore?
Should work, however, HWAccel may not able to work reliably.
From experiences, before 10.14.5 HWAccel may cause GPURestart fault (mainly occur with RX580) occationally.
But more fair, by that time, we didn't use OpenCore yet. So, can't achieve fully functional HWAccel. May be OpenCore can actually make HWAccel work stably in 10.14.3.
Anyway, it's relatively safe to try. If system freeze due to that GPURestart fault. You can always remove OpenCore (GPURestart usually only trigger when the user stress the video engine. It won't stop the user to boot to desktop).
But the CPU is so cheap now. Why not just get a new one? E.g. something like X5677 is extremely cheap, but almost 50% faster than yours.
Hi, thanks for the reply. I don't really get it. I used the complete way from this thread (https://forums.macrumors.com/threads/opencore-on-the-mac-pro.2207814/), and HW acceleration dint work. Than I tried the one you suggest in the very first post but you yourself tell to download whatevergreen and to do this argument or am I missing something? Sorry I'm absolutely new to this topic. best regards
