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

[star-affinity]

Just went from 0.7.0 to 0.7.4 on my Big Sur 11.6 installation and Bluetooth (USB dingle) gets disabled when I do that change.

If no one has any ideas I’ll just stick with 0.7.0 for now. Or try and fiddle with the config.plist.

Edit:

Disabling ExtendBTFeatureFlags in the config.plist in the 0.7.4 package (and then restart the computer) worked for me – my Bluetooth USB dongle is now recognized.

 

[h9826790]

Just went from 0.7.0 to 0.7.4 on my Big Sur 11.6 installation and Bluetooth (USB dingle) gets disabled when I do that change.

If no one has any ideas I’ll just stick with 0.7.0 for now. Or try and fiddle with the config.plist.

You are not alone, this problem seems started from 0.7.3

 

[star-affinity]

You are not alone, this problem seems started from 0.7.3

Seems I just managed to solve it!

What I did was compare the config.plist in your 0.7.0 package with the config.plist in the 0.7.4 package in OpenCore Configurator. One difference was that in the Kernel section in 0.7.4 had ExtendBTFeatureFlags enabled, something that is disabled in 0.7.0. So I just disabled (unchecked) that and restarted my computer and now my Bluetooth USB module is recognized fine for me also when using the 0.7.4 package.

So at least this was the solution in my case.

 

[h9826790]

Thanks for providing the solution. I will update the 0.7.4 package to make that ExtendBTFeatureFlags disabled by default to improve compatibility.

 

[abaxworld]

So WIFI is working, just not BlueTooth?

I just have Bluetooth, my computer never had WIFI. But I have read others who have are experiencing the same issue.

 

[abaxworld]

Seems I just managed to solve it!

What I did was compare the config.plist in your 0.7.0 package with the config.plist in the 0.7.4 package in OpenCore Configurator. One difference was that in the Kernel section in 0.7.4 had ExtendBTFeatureFlags enabled, something that is disabled in 0.7.0. So I just disabled (unchecked) that and restarted my computer and now my Bluetooth USB module is recognized fine for me also when using the 0.7.4 package.

So at least this was the solution in my case.

Shame that doesn't work with the internal Bluetooth ( at least for me ). :'( I guess we need a new kext driver or something to reactivate it.

 

[kkinto]

Hi Martin - why was latebloom removed from this latest version?

 

[shadow_999]

Hi Martin - why was latebloom removed from this latest version?

It's using surplus which is a solution and not a workaround as latebloom was

 

[splifingate]

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

Thank you cdf

Considering that I have been using OCLP to slip-stream into this process with my 2012 MP5,1, I am very interested in learning more . . . where might I research, further?

Regards, splifingate

 

[cdf]

Thank you cdf

Considering that I have been using OCLP to slip-stream into this process with my 2012 MP5,1, I am very interested in learning more . . . where might I research, further?

Regards, splifingate

Happy to help!

If you're curious about the FirmwareFeatures, you can obtain the original values by booting Mojave natively (without OpenCore) and running dmidecode (for the SMBIOS values) and also entering the following Terminal commands (for the NVRAM values):

nvram -x 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeatures

nvram -x 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeaturesMask

To understand what the bits mean, you can take a look at

OpenCorePkg/Include/Apple/IndustryStandard/AppleFeatures.h at master · acidanthera/OpenCorePkg

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

github.com

You'll have to do the conversion between the various representations of the values (base64, hexadecimal, and binary) being mindful of the endianness.

If you want to learn more about OpenCore in general, the Dortania resources are fantastic:

Getting Started

And if you want to try setting up OpenCore on your Mac manually, make sure to take a look at our guide on this forum:

OpenCore on the Mac Pro

This guide explains how to use the excellent OpenCore boot loader to install, run, and update the latest version of macOS on the MacPro5,1, resulting in a clean, unaltered operating system just like on a supported Mac.

forums.macrumors.com

 

[kkinto]

It's using surplus which is a solution and not a workaround as latebloom was

Ah thanks. I didn't know about that - guess I got some reading to do!

 

[Run75]

Hello,
7.4 installed and works perfectly
1000 thanks

 

[joevt]

Happy to help!

If you're curious about the FirmwareFeatures, you can obtain the original values by booting Mojave natively (without OpenCore) and running dmidecode (for the SMBIOS values) and also entering the following Terminal commands (for the NVRAM values):

nvram -x 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeatures

nvram -x 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeaturesMask

To understand what the bits mean, you can take a look at

OpenCorePkg/Include/Apple/IndustryStandard/AppleFeatures.h at master · acidanthera/OpenCorePkg

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

github.com

You'll have to do the conversion between the various representations of the values (base64, hexadecimal, and binary) being mindful of the endianness.

If you want to learn more about OpenCore in general, the Dortania resources are fantastic:

Getting Started

And if you want to try setting up OpenCore on your Mac manually, make sure to take a look at our guide on this forum:

OpenCore on the Mac Pro

This guide explains how to use the excellent OpenCore boot loader to install, run, and update the latest version of macOS on the MacPro5,1, resulting in a clean, unaltered operating system just like on a supported Mac.

forums.macrumors.com

My gfxutil.sh script has a showfirmwarefeatures command. You still need to have proper access to nvram (no OpenCore nvram protection - same as your instructions).
https://gist.github.com/joevt/477fe842d16095c2bfd839e2ab4794ff

The script outputs both ExtendedFirmwareFeatures and FirmwareFeatures. It says which flags are set, not set, and unsupported (ignored).

 

[Sebisa]

Hello, I tried to upgrade my Mac Pro 5.1 from Catalina to Big Sur 11.6 with Open Core 0.7.3.1. I followed all steps one by one... but my Mac Pro turns in a loop at the boot picker... What's wrong here ? Please need your help, Thx

 

[splifingate]

Happy to help!

If you're curious about the FirmwareFeatures, you can obtain the original values by booting Mojave natively (without OpenCore) and running dmidecode (for the SMBIOS values) and also entering the following Terminal commands (for the NVRAM values):

nvram -x 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeatures

nvram -x 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeaturesMask

To understand what the bits mean, you can take a look at

OpenCorePkg/Include/Apple/IndustryStandard/AppleFeatures.h at master · acidanthera/OpenCorePkg

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

github.com

You'll have to do the conversion between the various representations of the values (base64, hexadecimal, and binary) being mindful of the endianness.

If you want to learn more about OpenCore in general, the Dortania resources are fantastic:

Getting Started

And if you want to try setting up OpenCore on your Mac manually, make sure to take a look at our guide on this forum:

OpenCore on the Mac Pro

This guide explains how to use the excellent OpenCore boot loader to install, run, and update the latest version of macOS on the MacPro5,1, resulting in a clean, unaltered operating system just like on a supported Mac.

forums.macrumors.com

You are very kind. Thank you.

I like easy, but you know that I'm not adverse to getting down:dirty

Currently, I'm immersed in an n-dimensional 'Adventure' "twisty-windy" singularity, and the Rabbit Hole constricts me.

I will research. thx

Regards, splifingate

 

[splifingate]

My gfxutil.sh script has a showfirmwarefeatures command. You still need to have proper access to nvram (no OpenCore nvram protection - same as your instructions).
https://gist.github.com/joevt/477fe842d16095c2bfd839e2ab4794ff

The script outputs both ExtendedFirmwareFeatures and FirmwareFeatures. It says which flags are set, not set, and unsupported (ignored).

Teh Rabbit Hole widens . . . excellent

Regards, splifingate

 

[Herbjul]

Macbook pro 13inch mid 2012 has Problems with sleep awake problems.

Macbook sometimes does not go into sleep mode either

OpenCore 0.7.4

Data Source: Stackshots
Shared Cache: 1FB62A50-25C7-3F72-8054-A70CD3CA5953 slid base address 0x7fff20096000, slide 0x96000

Event: Sleep Wake Failure
Duration: 0.00s
Steps: 1

Data Source: Stackshots
Shared Cache: 1FB62A50-25C7-3F72-8054-A70CD3CA5953 slid base address 0x7fff20096000, slide 0x96000

 

[Auggie]

Sorry I'm late to the game for the past couple months but it looks like the release of SurPlus has allowed us to continue into the latest builds of both Big Sur and Monterey.

I wish I checked in earlier before I bit the bullet and purchased a new Mac Pro 7,1. But I'd still like to keep at least one of my cMP's running the absolute latest, if possible.

My question as I've never updated since the initial install back in April, so it's on OC 0.7.0, and whatever method to get Big Sur up to 11.2.3 working.

What's the best procedure for upgrading to the latest package here with SurPlus?

I perused the first post and nothing was updated to indicate this process.

 

[offdwall]

Sorry I'm late to the game for the past couple months but it looks like the release of SurPlus has allowed us to continue into the latest builds of both Big Sur and Monterey.

I wish I checked in earlier before I bit the bullet and purchased a new Mac Pro 7,1. But I'd still like to keep at least one of my cMP's running the absolute latest, if possible.

My question as I've never updated since the initial install back in April, so it's on OC 0.7.0, and whatever method to get Big Sur up to 11.2.3 working.

What's the best procedure for upgrading to the latest package here with SurPlus?

I perused the first post and nothing was updated to indicate this process.

I’m no expert but just update OC to 0.7.3v2 or 0.7.4 from this thread. They both include Sur plus. Then just do an Apple software update to 11.6.

 

[Auggie]

I’m no expert but just update OC to 0.7.3v2 or 0.7.4 from this thread. They both include Sur plus. Then just do an Apple software update to 11.6.

Just copy over the contents of the installers over to the EFI partition, replacing what may come?

 

[benmuetsch]

Just updated to the latest package, works great on Catalina so far. Sidecar appears now in System Profiler, which is weird, as I don't even have a Polaris GPU, but an old GTX660.
Cannot try it though as I don't have an iPad. I assume it's just there and cannot work, or does it?

 

[G10]

Hello - I hope someone can help me out. I have an internal SATA SSD that I've been using as a time machine HD backup disk. It has been disconnecting after 2 minutes after the machine boots up. After it disconnects I can no longer see the disk under disk utility. I have to restart the machine to see the disk only to have it disconnected 2 minutes later. T

When I look at the logs I get


2021-10-13 19:44:26-04 USER-Mac-Pro storagekitd[451]: disk4s5s1 appears to be an APFS snapshot disk.
2021-10-13 19:44:29-04 USER-Mac-Pro storagekitd[451]: disk4s5s1 appears to be an APFS snapshot disk.
2021-10-13 19:45:28-04 USER-Mac-Pro storagekitd[451]: Removing client connection <SKDaemonConnection: 0x7f88f3c04290>
2021-10-13 19:45:28-04 USER-Mac-Pro storagekitd[451]: No more connections, storagekitd will exit...

I have a 2012 5.1 machine with Martin's package 0.7.4 OC with Big Sur 11.6
This wasn't a problem on 0.7.3 v2

 

[Pressure]

Whoops, wrong thread. Just delete

 

[G10]

Hello - I hope someone can help me out. I have an internal SATA SSD that I've been using as a time machine HD backup disk. It has been disconnecting after 2 minutes after the machine boots up. After it disconnects I can no longer see the disk under disk utility. I have to restart the machine to see the disk only to have it disconnected 2 minutes later. T

When I look at the logs I get


2021-10-13 19:44:26-04 USER-Mac-Pro storagekitd[451]: disk4s5s1 appears to be an APFS snapshot disk.
2021-10-13 19:44:29-04 USER-Mac-Pro storagekitd[451]: disk4s5s1 appears to be an APFS snapshot disk.
2021-10-13 19:45:28-04 USER-Mac-Pro storagekitd[451]: Removing client connection <SKDaemonConnection: 0x7f88f3c04290>
2021-10-13 19:45:28-04 USER-Mac-Pro storagekitd[451]: No more connections, storagekitd will exit...

I have a 2012 5.1 machine with Martin's package 0.7.4 OC with Big Sur 11.6
This wasn't a problem on 0.7.3 v2

I think this self fixed itself after a couple of reboots. I would delete my original posting but don't know how to.

 

[avro707]

Just copy over the contents of the installers over to the EFI partition, replacing what may come?

That’s what I did. I have 0.7.4 on the less powerful MP5,1 and it just worked.


Edit: Big Sur 11.6 now running on the single processor MP 5,1 now too. Just needed to do CMD+OPT+P+R trick as per my other MP5,1. Running with Samsung 870 EVO SSD 2TB in the #1 drive bay (with OWC SSD tray).

Now I just need to buy the WIFI upgrade card to get my WIFI working again. Happy. I see side car in the system settings too. Nice!