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

[tsialex]

Actually, both Big Sur, and Mojave boot up just fine... I'm not sure if I have MacPro7,1 spoofing... how to tell?

You can check your config.plist <key>BoardProduct</key>, but if you are booting Mojave or you have iMacPro1,1 spoofing or -no_compat_check already added, since MacPro7,1 can't boot Mojave.

• iMacPro1,1 = Mac-7BA5B2D9E42DDD94
• MacPro7,1 = Mac-27AD2F918AE68F61

 

[Andreaux]

You can check your config.plist <key>BoardProduct</key>, but if you are booting Mojave or you have iMacPro1,1 spoofing or -no_compat_check already added, since MacPro7,1 can't boot Mojave.

• iMacPro1,1 = Mac-7BA5B2D9E42DDD94
• MacPro7,1 = Mac-27AD2F918AE68F61

I have <string>Mac-7BA5B2D9E42DDD94</string> there.

Should I move to the other one? What's the benefit? (sorry for the dumb noob questions )

 

[jggorman]

Anyone have any luck getting firewire audio to work on Martin Lo's config? I have an Apogee Duet Firewire I would like to get working. I have a cMP 4,1>5,1 where it is working with Martin Lo's config and Mojave. I have another machine running OCLP with Monterey and it is working there. I have not been able to get the Apogee Duet Firewire recognized on Monterey in my cMP.

 

[serdar13]

I have recently installed Monterey 12.6.6 and Post installs run in OCLP on my Mac Pro 5.1 but seems my hardware acceleration is not active. Can someone point me where I need to go and do to activate it. I was using manual Lilu and WhateverGreen method under Mojave 10.14. Could I use this method too in Monterey or will this cause problems?

 

[h9826790]

I was using manual Lilu and WhateverGreen method under Mojave 10.14. Could I use this method too in Monterey or will this cause problems?

No, don't do this in Monterey with OCLP.

Lily and WEG should be included in the OCLP EFI folder. If you double install that, your cMP will crash during boot.

I am not very sure what OCLP actually patch in your OS. If HWAccel doesn't work after root patching, you better contact the OCLP developers. So that they know this issue, and able to fix it.

 

[dreadedhamish]

I'm having some trouble booting and I'm wondering about enabling logging. I can see options in the clover configurator, but how do I enable it if I'm using the method from this thread? And where would I then find the logs?
(5,1, X5675, RX 590, running Mojave without issue, but getting restarts when the progress bar is at about 75% with the modified EFI files)

 

[serdar13]

No, don't do this in Monterey with OCLP.

Lily and WEG should be included in the OCLP EFI folder. If you double install that, your cMP will crash during boot.

I am not very sure what OCLP to to patch your OS. If HWAccel doesn't work after root patching, you better contact the OCLP developers. So that they know this issue, and able to fix it.

I followed Martin Lo's instructions regarding Hardware acceleration and after adding the files to EFI mount and rebooted, all is working and hardware acceleration is working

 

[h9826790]

I'm having some trouble booting and I'm wondering about enabling logging. I can see options in the clover configurator, but how do I enable it if I'm using the method from this thread? And where would I then gind the logs?
(5,1, X5675, RX 590, running Mojave without issue, but getting restarts when the progress bar is at about 75% with the modified EFI files)

1) You need to install the OpenCore DEBUG, but not the normal OpenCore RELEASE (the one that in my package is OpenCore RELEASE).

2) Then you better study the manual and set the Debug Target and DisplayLevel to what you really want / need. e.g.

<key>Debug</key>
        <dict>
            <key>AppleDebug</key>
            <true/>
            <key>ApplePanic</key>
            <false/>
            <key>DisableWatchDog</key>
            <true/>
            <key>DisplayDelay</key>
            <integer>0</integer>
            <key>DisplayLevel</key>
            <integer>2151678018</integer>
            <key>LogModules</key>
            <string>*</string>
            <key>SysReport</key>
            <true/>
            <key>Target</key>
            <integer>65</integer>
        </dict>

3) Once you finish you test, you should able to get the log from your EFI partition.

 

[dreadedhamish]

1) You need to install the OpenCore DEBUG, but not the normal OpenCore RELEASE (the one that in my package is OpenCore RELEASE).

2) Then you better study the manual and set the Debug Target and DisplayLevel to what you really want / need. e.g.

<key>Debug</key>
        <dict>
            <key>AppleDebug</key>
            <true/>
            <key>ApplePanic</key>
            <false/>
            <key>DisableWatchDog</key>
            <true/>
            <key>DisplayDelay</key>
            <integer>0</integer>
            <key>DisplayLevel</key>
            <integer>2151678018</integer>
            <key>LogModules</key>
            <string>*</string>
            <key>SysReport</key>
            <true/>
            <key>Target</key>
            <integer>65</integer>
        </dict>

3) Once you finish you test, you should able to get the log from your EFI partition.

Is this the correct next step for me?
I've followed all the instructions, moved my drive to a SATA port (from a OCW PCIe card), removed all other cards, done a plethora or NVRAM and SMC resets... i don't have another GPU to test with but my RX 590 is working with stock Mojave.

 

[h9826790]

Is this the correct next step for me?
I've followed all the instructions, moved my drive to a SATA port (from a OCW PCIe card), removed all other cards, done a plethora or NVRAM and SMC resets... i don't have another GPU to test with but my RX 590 is working with stock Mojave.

TBH, for Mojave, if that's my own cMP. I will simply boot to unpatched clean Mojave first.

Then if can boot to desktop, I will simply use the OC package in post #1314 to activate HWAccel.

That's it, no other diagnosis needed.

 

[dreadedhamish]

TBH, for Mojave, if that's my own cMP. I will simply boot to unpatched clean Mojave first.

Then if can boot to desktop, I will simply use the OC package in post #1314 to activate HWAccel.

That's it, no other diagnosis needed.

Thanks. clean Mojave is working fine - I'm typing from it now. When adding the package from post #1314 I can get the boot picker screen, then the progress bar to 75%, then it blacks out and restarts. Then clearing out the EFI files using Recovery gets me back to a functioning Majave install.

 

[h9826790]

Thanks. clean Mojave is working fine - I'm typing from it now. When adding the package from post #1314 I can get the boot picker screen, then the progress bar to 75%, then it blacks out and restarts. Then clearing out the EFI files using Recovery gets me back to a functioning Majave install.

I see.

That's strange. From memory, every single package was tested with Mojave. Should able to boot a clean Mojave.

Just to confirm the Mojave is 100% clean, no other self injected kext, right?

Also, when you install the OC package from post #1314. You copy both the OC and BOOT folder into position without any modification. Is that correct?

 

[dreadedhamish]

I see.

That's strange. From memory, every single package was tested with Mojave. Should able to boot a clean Mojave.

Just to confirm the Mojave is 100% clean, no other self injected kext, right?

Also, when you install the OC package from post #1314. You copy both the OC and BOOT folder into position without any modification. Is that correct?

To the best of my knowedge there was no modifications to mojave, and I copied across both OC and BOOT. Just to be sure I'm doing a clean install of Mojave on another drive.

 

[Macschrauber]

To the best of my knowedge there was no modifications to mojave, and I copied across both OC and BOOT. Just to be sure I'm doing a clean install of Mojave on another drive.

For Mojave I use the old method from post 1 with adding the two kexts not using OpenCore. Is still working.

 

[dreadedhamish]

For Mojave I use the old method from post 1 with adding the two kexts not using OpenCore. Is still working.

Thanks for your help. I want to also install Monterey on a new drive, but also keep my Mojave install.

 

[dreadedhamish]

I see.

That's strange. From memory, every single package was tested with Mojave. Should able to boot a clean Mojave.

Just to confirm the Mojave is 100% clean, no other self injected kext, right?

Also, when you install the OC package from post #1314. You copy both the OC and BOOT folder into position without any modification. Is that correct?

I did a fresh install of Mojave and it crashes at the same point. Once I removed the EFI files and booted into the new install (without OpenCore) I received a crash report, which I assume is from the unsuccessful boot using OpenCore - I've pasted the whole crash report here: https://pastebin.com/jyNvneux
It looks to be a GPU issue? Would it be strange for a GPU to crash using OpenCore while operating perfectly without?

 

[Macschrauber]

Thanks for your help. I want to also install Monterey on a new drive, but also keep my Mojave install.

so you can boot one System natively and one with OpenCore. So I do.

Either with Bootscreen GPU (if you have none you may check out the EnableGop project) - or with RefindPlus/MyBootMgr what loads systems natively and by OpenCore.

 

[dreadedhamish]

so you can boot one System natively and one with OpenCore. So I do.

Either with Bootscreen GPU (if you have none you may check out the EnableGop project) - or with RefindPlus/MyBootMgr what loads systems natively and by OpenCore.

I assumed if I was having trouble with OpenCore on Mojave then I'd have issues on Monterey?
I have a post in "moderation" because I attached a pastebin link to it - it's got a crash report from the a clean Mojave install attached - the I think it narrows it down to the GPU.

 

[dreadedhamish]

I successfully did a clean install of Monterey on a new drive. Apart from switching to the (unused) HDMI port during initial install it was all good.
Unless anyone has hints for getting my existing Mojave install working aswell with OpenCore, then I'll either resort to manually pulling the Monterey drive when I want to boot Mojave, or investigate RefindPlus/MyBootMgr.

 

[h9826790]

I successfully did a clean install of Monterey on a new drive. Apart from switching to the (unused) HDMI port during initial install it was all good.
Unless anyone has hints for getting my existing Mojave install working aswell with OpenCore, then I'll either resort to manually pulling the Monterey drive when I want to boot Mojave, or investigate RefindPlus/MyBootMgr.

You may disable all GPU related kext for Mojave only in OpenCore config by setting the min Kernel.

However, if that's too complicated. I think you better go for RefindPlus. So that you always default boot to RefindPlus, then you can select native Mojave, or OpenCore to further bridge boot Monterey.

Or you can simply flash you cMP

https://forums.macrumors.com/threads/pre-opencore-gop-support-for-efi-era-imacs-and-mac-pros.2378942/page-17?post=32137842#post-32137842

Therefore, your cMP default to boot OpenCore + Monterey. And you can simply hold Option key to boot native Mojave on the day you need it.

 

[joeldasso]

Hello again!First, BIG tanks for @h9826790 for all the support you are giving us!
I'm using your pack, and did the things you advice me to get the most of my Radeon VII. Its flawless.

But today I encountered this, when tried to open Apple Compressor:

I'm on macOS Monterey 12.6.6 using the last released @h9826790 OC pack

how can I solve it?

Since i'm not planning to leave Monterey, should I stay with an older version of OC?

 

[h9826790]

Hello again!First, BIG tanks for @h9826790 for all the support you are giving us!
I'm using your pack, and did the things you advice me to get the most of my Radeon VII. Its flawless.

But today I encountered this, when tried to open Apple Compressor:
View attachment 2221029

I'm on macOS Monterey 12.6.6 using the last released @h9826790 OC pack

how can I solve it?

Since i'm not planning to leave Monterey, should I stay with an older version of OC?

Please try Compressor Repair.

Compressor Repair - Digital Rebellion

Resets and repairs Apple Compressor

www.digitalrebellion.com

If doesn't work, may need to downgrade to 4.6.3

 

[donzubeck]

that same thing happened to me with compressor 4.6.4. try turning updates off in the config.plist. 4.6.3 works with updates on or off apple must have changed something in their code for compressor.

 

[joeldasso]

Please try Compressor Repair.

Compressor Repair - Digital Rebellion

Resets and repairs Apple Compressor

www.digitalrebellion.com

If doesn't work, may need to downgrade to 4.6.3

Tried the Compressor Repair and didn't work.
Also tried to find how to downgrade Compressor but didn't find how as well.
I have the original license for Compressor but didn't find where to download official Compressor 4.6.3.

Is there an other way to solve it?

 

[h9826790]

Tried the Compressor Repair and didn't work.
Also tried to find how to downgrade Compressor but didn't find how as well.
I have the original license for Compressor but didn't find where to download official Compressor 4.6.3.

Is there an other way to solve it?

May I know if the VMM flag is ON in your OpenCore config?

It should be OFF for daily use, which looks like this