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

[0134168]

internal SATA = Mac Pro drive bay? Aren't drive bays set to IDE when booted using Boot Camp legacy BIOS boot?

Mac Pro can't boot ESATA unless you're doing UEFI boot. UEFI boot sets internal drive bays to AHCI.

Nope. Legacy installation.

 

[star-affinity]

@h9826790

Your 0.7.3 OpenCore package on page 53 of this thread disables my Bluetooth USB dongle. 0.7.2 works fine. Any ideas?

Thankful for your efforts on those packages!
(I have sent a donation in the past)

 

[h9826790]

@h9826790

Your 0.7.3 OpenCore package on page 53 of this thread disables my Bluetooth USB dongle. 0.7.2 works fine. Any ideas?

Thankful for your efforts on those packages!
(I have sent a donation in the past)

May I know which OS?

Also, can you try 3xNVRAM reset? (Caution, depends on your hard drives config, NVRAM reset may lead the cMP boot into another non OC drive. If you want to play safe, remove all Windows drive. Or even just leave the OC + macOS drive installed to perform NVRAM reset.)

 

[h9826790]

I am running latest Mojave on an m.2 PCIE drive. I have a 5 drive RAID5 in the SATA ports using SoftRAID that I have disconnected just in case. The system was running fine prior to this. I upgraded to Mojave using the instructions in #1314.

May I know if you installed OC onto the Mojave drive?

Do you have any other boot drive?

You can't get into safe mode, but can boot to recovery partition, correct?

Do you still have the original graphic card (or have any flashed graphic card)?

 

[star-affinity]

May I know which OS?

Also, can you try 3xNVRAM reset? (Caution, depends on your hard drives config, NVRAM reset may lead the cMP boot into another non OC drive. If you want to play safe, remove all Windows drive. Or even just leave the OC + macOS drive installed to perform NVRAM reset.)

Big Sur 11.5.2.

I just feels it's something with OC or its congfig, since Bluetooth definitely comes back on if I go back to the 0.7.2 package.

@h9826790
Sorry, Bluetooth comes back on if I go back to the 0.7.0 package. Every version of the packages after that (0.7.1 to 0.7.3) disables my USB Bluetooth dongle.

Do you still think NVRAM resets could help? I mean if it works with 0.7.0 can it be an NVRAM problem? 🤔

But I'll see if I can try NVRAM reset x3 if you think it helps.

 

[gherebean]

May I know if you installed OC onto the Mojave drive?

Do you have any other boot drive?

You can't get into safe mode, but can boot to recovery partition, correct?

Do you still have the original graphic card (or have any flashed graphic card)?

So I ended up just intsalling a fresh copy of Mojave before you responded to this message and the system is now up and running but with no boot screen or HWA. I downloaded the 0.7.3 and tried to run the Bless Opencore but got an error. I didn't reset NVRAM or anything because I wasn't sure if I needed to just go through the process as if I were updating from High Sierra all over. I didn't want to brick the system again.

I do not have another boot drive currently.

I have an RX580 install and it is not flashed.

I would like to update to Big Sur and have OpenCore and HWA running correctly if at all possible. When I try to update to Big Sur, the Mac Update tells me that OS is not available.

 

[h9826790]

So I ended up just intsalling a fresh copy of Mojave before you responded to this message and the system is now up and running but with no boot screen or HWA. I downloaded the 0.7.3 and tried to run the Bless Opencore but got an error. I didn't reset NVRAM or anything because I wasn't sure if I needed to just go through the process as if I were updating from High Sierra all over. I didn't want to brick the system again.

I do not have another boot drive currently.

I have an RX580 install and it is not flashed.

I would like to update to Big Sur and have OpenCore and HWA running correctly if at all possible. When I try to update to Big Sur, the Mac Update tells me that OS is not available.

You have to mount the EFI partition that contain OC before you run the Bless tool, otherwise, it won't work.

Also, SIP must be still disabled. If not sure, please double check this as well.

 

[kings79]

So I ended up just intsalling a fresh copy of Mojave before you responded to this message and the system is now up and running but with no boot screen or HWA. I downloaded the 0.7.3 and tried to run the Bless Opencore but got an error. I didn't reset NVRAM or anything because I wasn't sure if I needed to just go through the process as if I were updating from High Sierra all over. I didn't want to brick the system again.

I do not have another boot drive currently.

I have an RX580 install and it is not flashed.

I would like to update to Big Sur and have OpenCore and HWA running correctly if at all possible. When I try to update to Big Sur, the Mac Update tells me that OS is not available.

Can you still see the Big Sur update option in system preferences?

This is the problem I had. I followed the same instructions the first time with Mojave and could see the OC boot screen. Now the second copy of Mojave I have I can't see the boot screen. I followed the same procedure on Martin's YouTube video.

 

[quadra605]

I created a new "easy to install package" as per many requested (based on the official OpenCore). [The attached package already updated to 0.7.3]

For those who only need HWAccel, post #594 has everything you need. This new package mainly offer HWAccel + boot screen. Also, this package should work in Catalina for dual processor cMP.

I installed OpenCore using the method in #1314, but scrolling through the thread I'm unclear about whether or not to re-enable SIP after the installation is complete. I went ahead and re-enabled it and checked the status in Recovery mode, and then in my home directory after I booted up. Does this all look good to everyone? Should I go back and disable it again in Recovery mode?

FYI: did this on my test machine cMP 4,1>5,1 in preparation for installing OpenCore on my main cMP5,1.

 

[h9826790]

I installed OpenCore using the method in #1314, but scrolling through the thread I'm unclear about whether or not to re-enable SIP after the installation is complete. I went ahead and re-enabled it and checked the status in Recovery mode, and then in my home directory after I booted up. Does this all look good to everyone? Should I go back and disable it again in Recovery mode?

FYI: did this on my test machine cMP 4,1>5,1 in preparation for installing OpenCore on my main cMP5,1.

View attachment 1834496

There is no need to re-enable SIP. It' just your choice.

And that customised SIP status is intentional.

 

[0134168]

@h9826790 I can see that in 0.7.3 Latebloom is enabled by default. Right?

 

[h9826790]

@h9826790 I can see that in 0.7.3 Latebloom is enabled by default. Right?

Correct, and it's programmed to only works in macOS 11.3 or later. Therefore, should be no harm for those using older OS.

 

[0134168]

Using it in 11.5.2. Works like a charm. Gonna try to update , previous backup, of course, to 11.6

 

[quadra605]

There is no need to re-enable SIP. It' just your choice.

And that customised SIP status is intentional.

Thank you. If I'm understanding you correctly, re-enabling SIP will NOT cause any problems, so I can leave my system with SIP enabled (as shown in my photos)

 

[iChan]

I changed the UIScale flag from AQ== to Ag== and all I got was large text as a bootpicker.

Also giant Apple logo and progress bar.

I'm outputting to LG CX 4K OLED over HDMI. GPU is RX 580. AQ== works as expected.

 

[abaxworld]

Anybody here experiencing the "An Error Occurred While Verifying Firmware" trying to upgrade to the latest macOS Monterrey Public Beta 7 using Martin Lo's OpenCore 0.7.2? Seems that for some reason this new beta is asking for a new firmware or something similar...

 

[Ausdauersportler]

Anybody here experiencing the "An Error Occurred While Verifying Firmware" trying to upgrade to the latest macOS Monterrey Public Beta 7 using Martin Lo's OpenCore 0.7.2? Seems that for some reason this new beta is asking for a new firmware or something similar...

Take a look at the Monterey thread, it is not an issue of a specific OC distribution.

 

[abaxworld]

Take a look at the Monterey thread, it is not an issue of a specific OC distribution.

The solution you propose there doesn't solve this issue. I tried to do both methods you propose and none of them prevents the Firmware error. So I'm asking if others with OpenCore have this problem here.

 

[flygbuss]

Short question: Will I be able to use a MvC flashed WX7100 with OC and Mojave for hardware acceleration (Compressor) in a cMP 5,1?
I know I wouldn’t need a flashed card for boot screen with OC, but would it work with the flashed ROM?
Thanks a lot in advance!

 

[KeesMacPro]

Short question: Will I be able to use a MvC flashed WX7100 with OC and Mojave for hardware acceleration (Compressor) in a cMP 5,1?
I know I wouldn’t need a flashed card for boot screen with OC, but would it work with the flashed ROM?
Thanks a lot in advance!

I suppose you're referring to an OpenCore install with Martin's package (since you posted it here). TBH I cant tell you from personal experience but I did install and test OC with different MVC flashed cards following the OpenCore procedure by CDF and it works perfectly (also with Mojave).

 

[Macschrauber]

I guess if Windows Uefi needs a valid GOP Boot screen it would not work.

We know this behaviour from GPUs with GTX680 Mac Edition Rom.

 

[abaxworld]

The solution you propose there doesn't solve this issue. I tried to do both methods you propose and none of them prevents the Firmware error. So I'm asking if others with OpenCore have this problem here.

I haven't said anything. We always post the wrong questions in the wrong threads. Better never ask.

 

[tsialex]

The Firmware spoofing in my MacPro is 9144.0.7.3.0 now ( OpenCore 0.7.3 ). I have tried to install macOS Monterey Beta 7 with this latest OC and firmware spoof version and the "An Error Occurred While Verifying Firmware" message appears again. So, Yes, it seems is something related to OpenCore Firmware Spoofing. I have seen other MacPro 4.1->5.1 users with OCLP are able to install macOS Monterey Beta 7, so I'm wondering if a new firmware version should be injected in OpenCore to allow the installer to recognize these computers using OC from Martin Lo.

Monterey beta 6 and 7 delta updates problems are not related to the firmware version number in any way, but to the iMac Pro/Mac Pro spoofing and it's a T2 related issue. Also Apple did some weird things with beta 7 delta that even some supported Macs are having issues and several Mac admins reported it since the release.

OCLP developers seem to have found a way to workaround the issue with 0.2.5, see this week commits on GitHub. If you want to upgrade to Monterey beta 7 right now, try to use the OCLP 0.2.5, maybe it will work for you.

P.S.:

I don't think that Monterrey beta support is the focus of @h9826790 right now and wouldn't be mine either since it's a moving target.

 

[cdf]

Anybody here experiencing the "An Error Occurred While Verifying Firmware" trying to upgrade to the latest macOS Monterrey Public Beta 7 using Martin Lo's OpenCore 0.7.2? Seems that for some reason this new beta is asking for a new firmware or something similar...

OCLP developers seem to have found a way to workaround the issue with 0.2.5, see this week commits on GitHub.

The best reference for this is directly at the OC source:

OcMainLib: Add large basesystem support to `AdviseFeatures` · acidanthera/OpenCorePkg@1cb8490

OpenCore bootloader. Contribute to acidanthera/OpenCorePkg development by creating an account on GitHub.

github.com

Explicitly: bit 35 (FW_FEATURE_SUPPORTS_LARGE_BASESYSTEM) of FirmwareFeatures is required for the update. The minimal approach is to preserve the original FirmwareFeatures and flip only that bit. These are the new values for PlatformInfo>SMBIOS:

<key>FirmwareFeatures</key>
<data>AxQMwAgAAAA=</data>
<key>FirmwareFeaturesMask</key>
<data>P/8f/wgAAAA=</data>

You might also need to add them in PlatformInfo>NVRAM PlatformNVRAM. In this case, these are the new values:

<key>FirmwareFeatures</key>
<data>A1QMwAgAAAA=</data>
<key>FirmwareFeaturesMask</key>
<data>P/8f/wgAAAA=</data>

Note that the Acidanthera firmware database (which OCLP has casually adopted) does not have the correct original values for the FirmwareFeatures of the Mac Pro 5,1.

Off topic: @tsialex, regarding the original FirmwareFeatures, there is a mismatch of one bit (bit 14 = FW_FEATURE_SUPPORTS_HIGH_SPEED_USB) between the values in the SMBIOS and the NVRAM. This seems like an Apple bug, but I wonder if it could not actually be an artifact of cross flashing. Do you have any insights on this?

 

[KeesMacPro]

I guess if Windows Uefi needs a valid GOP Boot screen it would not work.

We know this behaviour from GPUs with GTX680 Mac Edition Rom.

Not sure if you referred to my post # 2870 or another post...(?)

Anyway I got an OpenCore setup with a MVC flashed RX 580 Pulse , and a UEFI Windows 10 running fine.
Boot screen and boot picker both showing.
OpenCore as in the OC thread.