Sidebar Sidebar
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

Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Hi guys,

I slowly progress in installing different versions of macOS in my cMP 5.1 :

Bay n°1 > Mojave 10.14.6 (up to date) with OpenCore 0.7.6 (in EFI Boot)
Bay n°2 : empty
Bay n°3 : empty
Bay n°4 : empty
PCIe (top slot : x4/RAID) : NVMe SSD Samung 980 1TB

Note : I have already installed the BT 4.0/WiFi module BCM94360CD.

I dowloaded macOS Big Sur 11.6.5 installer and simply ran it from Mojave 10.14.6 to do a clean install of Big Sur 11.6.5 on my NVMe SSD Samung 980 1TB with easy success.

Now, my question is : can I directly update Big Sur to Monterey by updating the system in System Preferences ?

Thank you for your precious answers ??

Capture d’écran 2022-03-20 à 16.41.02.png
 
Last edited:
@h9826790, in the 0.7.9 release you added the 'enable-gva-support' argument under <key>boot-args</key> because of changes in latest WhateverGreen. My question is what does it do and who does it affect? Does it make any difference for HWAccel on my Radeon RX 560 or could I omit/ignore it?

If I need it could I move it to <key>DeviceProperties</key> like I did with some of your other <key>boot-args</key>?

<key>PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)</key>
<dict><key>agdpmod</key>
<data>cGlrZXJhAA==</data>
<key>model</key>
<string>AMD Radeon RX 560</string>
<key>rebuild-device-tree</key>
<data>AA==</data>
<key>shikigva</key>
<data>UA==</data>
<key>unfairgva</key>
<data>AQAAAA==</data>
</dict>

Another thing I noticed is that it seems by the size of ASPP-Override.kext that you are using v1.0.0 of it, there is a newer smaller v1.0.1 to be found here. It probably make no big difference, but...

And under <key>boot-args</key> you are are using arguments '-lilubetaall -wegbeta', do we need it anymore?

I am running Monterey 12.3 and all good. But beaware the BootROM! I think I was on the edge bricking my Mac Pro, but luckily after update I was able to restore a 1 year old BootROM backup I had, and my Mac Pro now seems to behave very well again.

Thank you for your great work!
 
Mic-M4c said:
Hi guys,

I slowly progress in installing different versions of macOS in my cMP 5.1 :

Bay n°1 > Mojave 10.14.6 (up to date) with OpenCore 0.7.6 (in EFI Boot)
Bay n°2 : empty
Bay n°3 : empty
Bay n°4 : empty
PCIe (top slot : x4/RAID) : NVMe SSD Samung 980 1TB

Note : I have already installed the BT 4.0/WiFi module BCM94360CD.

I dowloaded macOS Big Sur 11.6.5 installer and simply ran it from Mojave 10.14.6 to do a clean install of Big Sur 11.6.5 on my NVMe SSD Samung 980 1TB with easy success.

Now, my question is : can I directly update Big Sur to Monterey by updating the system in System Preferences ?

Thank you for your precious answers 🙏🏻

View attachment 1977163
Click to expand...

I recommend a Monterey clean install, and use the Migration Assistant at the end of the installation. That´s the only way it worked for me.
 
Mic-M4c said:
OK so I have to run OCLP from Big Sur and patch the official Monterey installer and make a bootable patched installer.
Then boot on it with OpenCore.
Right ?
Click to expand...
That´s right. Patch the USB Monterey Install USB that you have created clean. Boot from it and install. Caution if you have any drive with OCLP already installed in EFI. You have to boot from the USB installer EFI. Don´t choose any other one for boot.

I have just remebered, maybe it´s relevant, maybe not. I always adjust the installation of the OCLP to run with SIP disabled.
 
******* said:
That´s right. Patch the USB Monterey Install USB that you have created clean. Boot from it and install. Caution if you have any drive with OCLP already installed in EFI. You have to boot from the USB installer EFI. Don´t choose any other one for boot.
Click to expand...
Sure : boot from the USB installer displayed on the black screen (=OpenCore boot screen) and not on the grey screen (=Apple boot screen)
 
Mic-M4c said:
Sure : boot from the USB installer displayed on the black screen (=OpenCore boot screen) and not on the grey screen (=Apple boot screen)
Click to expand...
I say again, jut be sure it´s the OCLP EFI from the USB installer, not another OCLP EFI you can have in any other drive.
 
Mic-M4c said:
Yes ok understood.
Click to expand...
Nice. Read also what i said about SIP. Maybe it´s not important, but that´s how I did it.

"I have just remebered, maybe it´s relevant, maybe not. I always adjust the installation of the OCLP to run with SIP disabled."
 
4-> 2 -> 1 -> 3-> and type 0xFEF
 

Attachments

  • Captura de Pantalla 2022-03-20 a las 18.18.58.png
    Captura de Pantalla 2022-03-20 a las 18.18.58.png
    34.7 KB · Views: 88
Last edited:
Ok so I'm still failing here to install 12.3 or any Monterey on my cMP 5,1. I have 11.6.5 working no problem. I did have 12.2.1 working but ever since the OTA update I can't seem to make the upgrade work.

After a few boots, normal instal, it gets to a reboot then loads and fails with a pop up that says from the macOS update assistant, A required firmware could not be installed. Once you click ok, the computer hangs or reboots which you'd have to boot from another drive then I get the crash report.

Never seen that error report. Also interesting it says the OS is not set.

To get here, I tried a few things all lead to the same. The most recent was a new clean sata drive for the destination, then had a 16gb thumb drive and used the open core patcher gui app (v.0.4.3) downloaded and created the install disk, opened the EFI with clover configurator and dropped in the 0.79 open core package found here: https://forums.macrumors.com/thread...n.2180095/page-53?post=28255048#post-28255048

I'm just wondering, is there something I'm missing or there's something up with my cMP hardware?
Any help or insight would be greatly appreciated.

Crash Report:

panic(cpu 0 caller 0xffffff8015426fa2): "Rooting from the live fs of a sealed volume is not allowed on a RELEASE build\n"@/System/Volumes/Data/SWE/macOS/BuildRoots/a0c6c82cc8/Library/Caches/com.apple.xbs/Sources/apfs/apfs-1677.141.3/kext/apfs_vfsops.c:2047


Backtrace (CPU 0), Frame : Return Address


0xffffffa054192ec0 : 0xffffff801228b26d


0xffffffa054192f10 : 0xffffff80123d2993


0xffffffa054192f50 : 0xffffff80123c2f8a


0xffffffa054192fa0 : 0xffffff801222fa2f


0xffffffa054192fc0 : 0xffffff801228aa8d


0xffffffa0541930e0 : 0xffffff801228ad83


0xffffffa054193150 : 0xffffff8012a9c5aa


0xffffffa0541931c0 : 0xffffff8015426fa2


0xffffffa0541939b0 : 0xffffff8015430353


0xffffffa0541939e0 : 0xffffff80125178cc


0xffffffa054193b60 : 0xffffff80127d3d53


0xffffffa054193e80 : 0xffffff80122b9897


0xffffffa054193fa0 : 0xffffff801222f13e


Kernel Extensions in backtrace:


com.apple.filesystems.apfs(1677.141.3)[45812160-E4A7-307A-B604-91D6A782126B]@0xffffff80153aa000->0xffffff8015519fff


dependency: com.apple.driver.AppleEFINVRAM(2.1)[A506788E-BC7C-3C87-BD70-376984C225D3]@0xffffff80136fe000->0xffffff8013707fff


dependency: com.apple.driver.AppleEffaceableStorage(1.0)[F1C24692-B3A0-3F31-A777-CA17069CD3DD]@0xffffff8013711000->0xffffff8013716fff


dependency: com.apple.iokit.CoreAnalyticsFamily(1)[E6C5D15B-3934-3236-932A-1EEF294F5E2B]@0xffffff8013b6d000->0xffffff8013b73fff


dependency: com.apple.iokit.IOStorageFamily(2.1)[FFF27081-0E9D-3E7F-8807-C018C8E46A09]@0xffffff8014e6e000->0xffffff8014e7ffff


dependency: com.apple.kec.corecrypto(11.1)[17F7A252-0406-3D10-90BD-A51F4394481D]@0xffffff8015547000->0xffffff80155d8fff


dependency: com.apple.security.AppleImage4(3.0.0)[BE766F1D-D061-3436-98BA-AF65AD47F2EF]@0xffffff801377d000->0xffffff801378dfff





Process name corresponding to current thread: kernel_task


Boot args: -lilubetaall -wegbeta agdpmod=pikera enable-gva-support shikigva=80 unfairgva=1 mbasd=1 -wegtree -no_compat_check no32exec=0





Mac OS version:


Not yet set





Kernel version:


Darwin Kernel Version 20.6.0: Tue Feb 22 21:10:41 PST 2022; root:xnu-7195.141.26~1/RELEASE_X86_64


Kernel UUID: 40A47F9A-078F-3F9B-B353-53A194CC6F1D


KernelCache slide: 0x0000000012000000


KernelCache base: 0xffffff8012200000


Kernel slide: 0x0000000012010000


Kernel text base: 0xffffff8012210000


__HIB text base: 0xffffff8012100000


System model name: MacPro5,1 (Mac-7BA5B2D9E42DDD94)


System shutdown begun: NO


Panic diags file unavailable, panic occurred prior to initialization


Hibernation exit count: 0





System uptime in nanoseconds: 2494066769


Last Sleep: absolute base_tsc base_nano


Uptime : 0x0000000094a878f8


Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000


Wake : 0x0000000000000000 0x00000014b036b3f0 0x0000000000000000
 

Attachments

  • popup.jpg
    popup.jpg
    521.5 KB · Views: 94
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back