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

[Cracticus]

Fixed!

So as I had no EFI folder after mounting the EFI volume - I had then originally "made one" - but this was the problem ; When I checked the directory with "ls" in Terminal, and could see this path /Volumes/EFI/EFI/EFI/OC/OpenCore.efi - so for me the instruction to make an additional EFI folder was not applicable. After deleting the EFI folder, the blessing worked fine; restart; In videoProc I got h264 and h265 on my ASUS RX580! Thanks peeps.

 

[h9826790]

Fixed!

So as I had no EFI folder after mounting the EFI volume - I had then originally "made one" - but this was the problem ; When I checked the directory with "ls" in Terminal, and could see this path /Volumes/EFI/EFI/EFI/OC/OpenCore.efi - so for me the instruction to make an additional EFI folder was not applicable. After deleting the EFI folder, the blessing worked fine; restart; In videoProc I got h264 and h265 on my ASUS RX580! Thanks peeps.

Thanks, I rewrite the step 9 and 10 a bit to avoid confusion.

That "create EFI folder" just added few days ago because someone can't see it and don't know how to do. But obvious, that create more unnecessary confusion. Thanks for the report.

 

[Cracticus]

cool - just so happy it's possible with your thread info ! - yeah I am also enjoying much faster Affinity Photo RAW HDR Metal processing via the Asus RX580 which i never expected. Main goal was for FCPX, but photo processing is a big bonus too...

 

[MacManu77]

guys ask you again for help please.
I installed 2 Samsung 970 pro in the IoCrest card.
one from 512gb for boot with Mojave 10.14.6 and one from 1tb that I would use with fcpx.
everything ok with .h264 and hevc full acceleration with the universal file.
in slot 4 I have a 512gb ahci.
the problem is when I go to reposition the 4 normal hdd, restarting no longer boot me in Mojave, feel the Boing but then black screen.
Possible solution?
Thanks. ?

 

[MacManu77]

Update: I managed to start Mojave.
I basically have egg change the sequence where the hdds were located in their Bay.
Can someone tell me why?

 

[roobarb!]

I'm having some fun with this at the moment.

One quick question; if I remove the drive containing OpenCore and modify config.plist on another system, there's nothing special I need to do to have the Mac Pro boot using that new configuration?

Because I'm finding myself in a situation where the machine starts boot-looping after a change to the config.plist and there's no way to recover (including replacing the config.plist with the previously working version) other than a complete NVRAM zap, so I thought I might be missing something.

 

[startergo]

One quick question; if I remove the drive containing OpenCore and modify config.plist on another system, there's nothing special I need to do to have the Mac Pro boot using that new configuration?

That is correct. Try the EFI folder I posted here
#1,154

 

[roobarb!]

That is correct. Try the EFI folder I posted here
#1,154

Thanks - amusingly, the system boot-looped five times while I was typing that message, then successfully booted with additional no user interaction. Weird. I shall try a reboot in just a second.



In your EFI folder I see AppleMCEReporterDisabler.kext and HibernationFixup.kext. What is the purpose of these two and why does HibernationFixup appear twice in the config.plist? Is it supposed to?

 

[startergo]

In your EFI folder I see AppleMCEReporterDisabler.kext and HibernationFixup.kext. What is the purpose of these two and why does HibernationFixup appear twice in the config.plist? Is it supposed to?

Good Catch. HibernationFixup.kext only has to be loaded once (my mistake) it is for fixing Hibernation/sleep issues I had. It is optional if you have issues waking from sleep.
AppleMCEReporterDisabler.kext is a must for dual Xeons in Catalina. That is why minimum OS flag is set.

 

[roobarb!]

AppleMCEReporterDisabler.kext is a must for dual Xeons in Catalina. That is why minimum OS flag is set.

Could not having that be the cause of the odd boot loops I've been seeing?

 

[startergo]

Could not having that be the cause of the odd boot loops I've been seeing?

Indeed it could be. One of the options in the config file stops the process from reboot loop and you can see the kernel extension in back trace, and this kext disables the offending original kext (from creating kernel panic). Also I have fixed the config file.

 

[roobarb!]

Great stuff, I shall roll this in to my folder and give it a try.

Oh, also, if I'm injecting Lilu with OC, if I want to use a Lilu plugin (such as Innie) would I be better doing that with a second copy of Lilu in /Library/Extensions as before, or can I throw it into the copy injected by OC?

 

[startergo]

would I be better doing that with a second copy of Lilu in /Library/Extensions as before, or can I throw it into the copy injected by OC?

Don't mix the 2. Use one or the other. Preferred way to do it in OC is in the kext folder.

 

[roobarb!]

Don't mix the 2. Use one or the other. Preferred way to do it in OC is in the kext folder.

Ah, sadly including Innie.kext as a Plugin within Lilu in OC doesn't appear to work. NVME drives are still being shown as external. Reboots are going well, though!

Update: To confirm, I've now been able to set and remove and set VMM spoofing with AppleMCEReporterDisabler.kext injected with no reboot issues at all.

 

[cdf]

Ah, sadly including Innie.kext as a Plugin within Lilu in OC doesn't appear to work.

Double check your config. It should work.

 

[roobarb!]

Double check your config. It should work.

Does Innie within Lilu need to be specifically injected from the config.plist as well? Or should Innie be kept outside of Lilu and called just like any other kext?

 

[startergo]

Does Innie within Lilu need to be specifically injected from the config.plist as well? Or should Innie be kept outside of Lilu and called just like any other kext?

Put it outside just like the other kexts.

 

[cdf]

Does Innie within Lilu need to be specifically injected from the config.plist as well?

Yes. Make sure to use the right executable path.

 

[roobarb!]

It's only gone and worked.

This is all pretty remarkable; boot screens, working hardware encoding and decoding, plus native software updates. All in an evening's tinkering. Thanks for your help!

Even HEVC encoding is working in Handbrake - it's chewing through 4K footage at 170 fps right now, instead of 2 or 3 fps previously. Absolutely stunning.

I'll be keeping a close eye on this thread for future updates. The only thing that seems odd on this system now is the 3.46 GHz showing up as 3.5 GHz, but I've seen that mentioned in passing previously.

Awesome stuff!

 

[startergo]

3.46 GHz showing up as 3.5 GHz, but I've seen that mentioned in passing previously.

Yes that is the only cosmetic difference.

 

[Ludacrisvp]

It's only gone and worked.

This is all pretty remarkable; boot screens, working hardware encoding and decoding, plus native software updates. All in an evening's tinkering. Thanks for your help!

Even HEVC encoding is working in Handbrake - it's chewing through 4K footage at 170 fps right now, instead of 2 or 3 fps previously. Absolutely stunning.

I'll be keeping a close eye on this thread for future updates. The only thing that seems odd on this system now is the 3.46 GHz showing up as 3.5 GHz, but I've seen that mentioned in passing previously.

Awesome stuff!

I’m curious which GPU and what settings you are using for that kind of speed.

 

[roobarb!]

I’m curious which GPU and what settings you are using for that kind of speed.

Radeon VII and the default settings for Apple 2160p60 4K HEVC Surround but with the video engine switched to H.265 (VideoToolbox) and an average bitrate at 12000. It's animated content though, so YMMV with more realistic stuff. Plenty of flat blocks of colour here.

I'll be having a play with some film content today to see how that performs. Oh, and the Radeon VII is running at 1890 MHz @ 970 mV with 1111 MHz clock on the HBM2 memory.

 

[Macprouser2012]

Hey, this is great news! I have one question about first screenshot. How did you get that information, in which software?

Hello see >>> https://www.videoproc.com/video-process/full-gpu-acceleration-benefits-4k-video.htm

 

[h9826790]

Radeon VII and the default settings for Apple 2160p60 4K HEVC Surround but with the video engine switched to H.265 (VideoToolbox) and an average bitrate at 12000. It's animated content though, so YMMV with more realistic stuff. Plenty of flat blocks of colour here.

I'll be having a play with some film content today to see how that performs. Oh, and the Radeon VII is running at 1890 MHz @ 970 mV with 1111 MHz clock on the HBM2 memory.

1890MHz @970mV, you are lucky, that's a good chip.

 

[Eschers]

I did everything as described, it then worked as well as described.

But when I went to activate SIP except for kexts ( csrutil enable --without kext) the mod becomes non usable anymore.

Any idea how to solve this?

ps: while cheking csrutil staus it says "Apple Internal : disabled" as well despite only having added kext arguments.