h9826790

macrumors P6
Original poster
Apr 3, 2014
15,276
7,572
Hong Kong
1.) What exactly is the difference between your kext from post #21 and the kext from post #35? I understand the one from #35, the VII will work using both 6-pin power. (to clarify, 6-pin to 8-pin).

Kext in post #21 - 240W max power draw

Kext in post #35 - 204W max power draw

In fact, I believe both kext will allow the Radeon VII to be powered by the mini 6pins only. However, the kext in post #35 is created particularly for that purpose, and fully tested with just powered by the mini 6pins. So, it's safer for those who don't want any power mod.

2.) What would you say is more "stable": using the kext from post #35, or nothing and powering the VII with a secondary PSU?

Assume your Radeon VII has normal silicon quality, the kext from post #35 should be the more stable option. (So far, I receive no complain about 981mV cause instability for their Radeon VII).

Without this kext, the Radeon VII will draw too much power, which cause the clock speed fluctuate a lot to avoid overheat. Of course, this will make the card run warmer, which may decrease stability (even though should be no difference as long as your cMP can provide proper cooling for the PCIe compartment).

Introduce a 2nd PSU also means create more "points of failure" (PSU, cable, connectors). So, I personally believe without the 2nd PSU should be a better choice.

3.) In post #21, you say "PRAM reset won't break the GPU driver. In fact, we can simply reset PRAM to disable the PP table (good for trouble shooting)." So basically, a PRAM reset will remove the kext? And to put it back, just repeat the steps of Post #21?

NVRAM reset will re-enable SIP, which stop the kext to load, but the kext will still stay at the installed position. Therefore, if you want to re-activate the kext, all you need to do is just disable SIP.
 
  • Like
Reactions: i make movies

i make movies

macrumors regular
Aug 9, 2007
172
13
Awesome, thank you for such a quick reply! I have 2 quick follow up questions:

1.) To get started, I just put the card in with the 6-pin power and go?

2.) So, in order for this to work you've got to run it with SIP disabled...which is fine since I use this for work only and its not connected to the internet. But for maintenance and installing new apps/drivers, I would like to enable SIP. Can I power the VII with just the 6-pin power if I'm not doing any heavy lifting? Or will even that cause random shutdowns or instability?
 

h9826790

macrumors P6
Original poster
Apr 3, 2014
15,276
7,572
Hong Kong
1.) To get started, I just put the card in with the 6-pin power and go?

Can.

However, my recommendation is balancing the demand between the mini 6pins. If you re-read my post #35 again, you should able the see that the power draw via each mini 6pin is very balanced.

The reason is because I use a cable combination to balance the demand.

"DUAL mini 6pin -> Single 6pin" + "Single 6pin FEMALE -> DUAL 6+2 pin"
Dual mini 6pin Radeon VII_filtered.jpg


I use a standard 6pin as the "bridge". In general, it's easier to acquire the cables that use 8pin as the bridge.
 
Last edited:

ExperimentalExpressinLab

macrumors newbie
Oct 27, 2019
8
2
Hi =)

I am a Hackintosh user(10.15.1 beta3), I have Radeon VII and Vega 64. When I play the powerplaytable with clover(Device Properties) didn't work for me. But thanks to the CustomPowerPlay.kext, now my Radeon VII can OC. However the kext patched only Radeon VII. How can i use the kext for Vega 64 at the same time ?
 

h9826790

macrumors P6
Original poster
Apr 3, 2014
15,276
7,572
Hong Kong
Hi =)

I am a Hackintosh user(10.15.1 beta3), I have Radeon VII and Vega 64. When I play the powerplaytable with clover(Device Properties) didn't work for me. But thanks to the CustomPowerPlay.kext, now my Radeon VII can OC. However the kext patched only Radeon VII. How can i use the kext for Vega 64 at the same time ?

VGTab doesn't work for your Vega?

 

ExperimentalExpressinLab

macrumors newbie
Oct 27, 2019
8
2
VGTab doesn't work for your Vega?



When I use the VGTab.kext with CostumPowerPlay.kext , AMD10000Controller created powerplaytable only for Vega64 =/
 

h9826790

macrumors P6
Original poster
Apr 3, 2014
15,276
7,572
Hong Kong
When I use the VGTab.kext with CostumPowerPlay.kext , AMD10000Controller created powerplaytable only for Vega64 =/

If you open up the PowerPlay kext, you should see the target Device ID.

My PowerPlay kext was developed base on the original AMD10000Controller. Minimum change on those parameter to avoid unnecessary trouble. But in your case, which will means "Apply that PowerPlay table to ALL matched device".

Since my PowerPlay kext ONLY developed for the Radeon VII, and I expect the users only use Radeon VII with this kext. I didn't specifically remove all unrelated device ID. Therefore, all those parameters are wrong for your Vega64, you should NOT use this kext with Vega 64.

If you want a system that can downvolt BOTH Vega 64 and Radeon VII. My suggestion is to install two separated dedicated kext.

1) open up the PowerPlay kext for Radeon VII, remove all unrelated device ID but only keep 0x66AF1002.

2) create another VegaPowerPlay kext, which only contain the Vega64 device ID, and a CORRECT power play table that's generated for the Vega64. (the required code can be generated by the Excel file that created by CMMChris)

3) Remove all previously installed PowerPlay kext, and then install these two kexts.

N.B. I expect VGTab's kext will also work if you remove all unrelated device ID.
 

Attachments

  • pptable_vega64.xlsx.zip
    36.1 KB · Views: 89
  • Like
Reactions: zoltm

ExperimentalExpressinLab

macrumors newbie
Oct 27, 2019
8
2
If you open up the PowerPlay kext, you should see the target Device ID.

My PowerPlay kext was developed base on the original AMD10000Controller. Minimum change on those parameter to avoid unnecessary trouble. But in your case, which will means "Apply that PowerPlay table to ALL matched device".

Since my PowerPlay kext ONLY developed for the Radeon VII, and I expect the users only use Radeon VII with this kext. I didn't specifically remove all unrelated device ID. Therefore, all those parameters are wrong for your Vega64, you should NOT use this kext with Vega 64.

If you want a system that can downvolt BOTH Vega 64 and Radeon VII. My suggestion is to install two separated dedicated kext.

1) open up the PowerPlay kext for Radeon VII, remove all unrelated device ID but only keep 0x66AF1002.

2) create another VegaPowerPlay kext, which only contain the Vega64 device ID, and a CORRECT power play table that's generated for the Vega64. (the required code can be generated by the Excel file that created by CMMChris)

3) Remove all previously installed PowerPlay kext, and then install these two kexts.

N.B. I expect VGTab's kext will also work if you remove all unrelated device ID.


Thanks a lot for your effort.

I tried but same result =/ the kexts only patched for Vega64 powerplaytable.(checked with IORegistryExplorer)

I have to edit your kext because of WhateverGreen.kext(1.3.4) I have black screen If I use your kext directly. I attached two separated kext.
 

Attachments

  • kexts.zip
    8.2 KB · Views: 76

h9826790

macrumors P6
Original poster
Apr 3, 2014
15,276
7,572
Hong Kong
Thanks a lot for your effort.

I tried but same result =/ the kexts only patched for Vega64 powerplaytable.(checked with IORegistryExplorer)

I have to edit your kext because of WhateverGreen.kext(1.3.4) I have black screen If I use your kext directly. I attached two separated kext.

There should be no compatibility issue between my Kext and WhateverGreen (1.3.2). I am running these two kexts together now.
Screenshot 2019-10-27 at 9.18.31 PM.png
 

ExperimentalExpressinLab

macrumors newbie
Oct 27, 2019
8
2
There should be no compatibility issue between my Kext and WhateverGreen (1.3.2). I am running these two kexts together now.
View attachment 872734


which version OS ? Because Whatevergreen kext has black screen issue until 10.15.1 (only work with not released version 1.3.4)

Btw, I just deleted some framebuffer sections on your kext. If I use your kext directly without Weg I lost all graphic acceleration. (10.15.1 beta3)
 

h9826790

macrumors P6
Original poster
Apr 3, 2014
15,276
7,572
Hong Kong
which version OS ? Because Whatevergreen kext has black screen issue until 10.15.1 (only work with not released version 1.3.4)

Btw, I just deleted some framebuffer sections on your kext. If I use your kext directly without Weg I lost all graphic acceleration. (10.15.1 beta3)

Mojave.

My kext was developed by modding the AMD10000 Controller kext plist file. I don't expect it compatible with Catalina.
 
  • Like
Reactions: zoltm

AlexMaximus

macrumors 65816
Aug 15, 2006
1,014
381
A400M Base
Mojave.

My kext was developed by modding the AMD10000 Controller kext plist file. I don't expect it compatible with Catalina.

Hello h98,

thank you so much for your important post here. I am a little bit worried to mess up some software stuff, so I have not tried yet to modify kext scripts and such, I am more of a hardware guy. But since it's about heat development and cooling down the Vega VII, I had some ideas to further enhance the cooling and I would like to hear your thought about it.
I just recently moved my Vega VII up two slots to have faster SSD speeds on my I/O Crest card. I lost a valuable slot, but the Vega get some more cooling on the backplate this way. I also found some long lost tech treasures, such as various alu cooling heat sinks and a PCI bracket with lots of holes form the G4 MDD period. I also found a never used Ram cooler fan from Corsair that I would love to use for this final upgrade. Do you have an idea how I can get this powerd up?

The idea with the alu heat sink is to mount it on the Vega VII backplate (using a drill and precision screws and some Arctic 7 heat compound as a heat-interface)

VegaVII_Cooling_Mod_2.jpg


To power this ram cooler up, I have found something like this, but I would need to sacrifice a HDD slot power for this. Would this work?

Screenshot 2019-10-27 at 18.48.01.png
 
  • Like
Reactions: zoltm

vikikang

macrumors newbie
Sep 16, 2019
6
5
which version OS ? Because Whatevergreen kext has black screen issue until 10.15.1 (only work with not released version 1.3.4)

Btw, I just deleted some framebuffer sections on your kext. If I use your kext directly without Weg I lost all graphic acceleration. (10.15.1 beta3)
Hello. Could you explain more about how to modify the PPT kext to make it compatible with WEG1.3.4 and Catalina 10.15.1 beta3. Thanks very much! BTW, I'm using Radeon VII.
 
  • Like
Reactions: zoltm

h9826790

macrumors P6
Original poster
Apr 3, 2014
15,276
7,572
Hong Kong
Hello h98,

thank you so much for your important post here. I am a little bit worried to mess up some software stuff, so I have not tried yet to modify kext scripts and such, I am more of a hardware guy. But since it's about heat development and cooling down the Vega VII, I had some ideas to further enhance the cooling and I would like to hear your thought about it.
I just recently moved my Vega VII up two slots to have faster SSD speeds on my I/O Crest card. I lost a valuable slot, but the Vega get some more cooling on the backplate this way. I also found some long lost tech treasures, such as various alu cooling heat sinks and a PCI bracket with lots of holes form the G4 MDD period. I also found a never used Ram cooler fan from Corsair that I would love to use for this final upgrade. Do you have an idea how I can get this powerd up?

The idea with the alu heat sink is to mount it on the Vega VII backplate (using a drill and precision screws and some Arctic 7 heat compound as a heat-interface)

View attachment 872779

To power this ram cooler up, I have found something like this, but I would need to sacrifice a HDD slot power for this. Would this work?

View attachment 872782

I have no idea about the hardware cooling mod for Radeon VII.

After downvolt the card, it's cool and quiet, therefore, I never look into hardware mod. In fact, even the usual poor factory thermal paste also replaced by the much higher quality graphite pad. I don't even need to apply the liquid metal cooling to this card. (I did this to my 1080Ti and RX580, works extremely well).
 
  • Like
Reactions: zoltm

ExperimentalExpressinLab

macrumors newbie
Oct 27, 2019
8
2
Hello. Could you explain more about how to modify the PPT kext to make it compatible with WEG1.3.4 and Catalina 10.15.1 beta3. Thanks very much! BTW, I'm using Radeon VII.

Hi,

The PPT kext has some Framebuffer patch, these are not compatible with WEG(1.3.4) "for me". I have an old RadeonVegaLowFansSpeed.kext and it is working with WEG(1.3.4). I just customise the RadeonVegaLowFansSpeed.kext with the PPT kext data and that's it.
 
  • Like
Reactions: vikikang

CMMChris

macrumors 6502a
Oct 28, 2019
525
410
@ExperimentalExpressinLab I am the creator of the Radeon VII PPT generator shared here.
On a Hackintosh there is absolutely no need to fumble with codeless kexts for PowerPlay Table injection. Use clover device properties for it. You just need to do it the right way and it will work. Use Hackintool to get the correct PCI path for your graphics card.
Those codeless kexts can get you into trouble especially if they override the entire info.plist of AMD10000Controller. This for example applies to the Kext generated by VGTab.

Also: Don't use VGTab for Vega 64 or Vega 56 if you use a custom card (for reference cards the PPTs generated by VGTab are fine). Reason is "MinimumPWMLimit" which is different on the custom card models. This is kind of a fan calibration value and important for correct fan speeds. So in case you use a custom card please use my Excel PPT Generator for Vega 56/64 and change the MinimumPWMLimit to match your card. You can extract the correct value from the PowerPlay Table inside the VBIOS of your card.

And bear in mind that undervolting Vega 56 / 64 on macOS isn't possible. The driver ignores the voltages set inside the PPT.
 

vikikang

macrumors newbie
Sep 16, 2019
6
5
@ExperimentalExpressinLab I am the creator of the Radeon VII PPT generator shared here.
On a Hackintosh there is absolutely no need to fumble with codeless kexts for PowerPlay Table injection. Use clover device properties for it. You just need to do it the right way and it will work. Use Hackintool to get the correct PCI path for your graphics card.
Those codeless kexts can get you into trouble especially if they override the entire info.plist of AMD10000Controller. This for example applies to the Kext generated by VGTab.

Also: Don't use VGTab for Vega 64 or Vega 56 if you use a custom card (for reference cards the PPTs generated by VGTab are fine). Reason is "MinimumPWMLimit" which is different on the custom card models. This is kind of a fan calibration value and important for correct fan speeds. So in case you use a custom card please use my Excel PPT Generator for Vega 56/64 and change the MinimumPWMLimit to match your card. You can extract the correct value from the PowerPlay Table inside the VBIOS of your card.

And bear in mind that undervolting Vega 56 / 64 on macOS isn't possible. The driver ignores the voltages set inside the PPT.
With my great respect for your gorgeous work on PPT generator. You have helped me a lot, Sir. ^_^
Could you plz do some further instructions about how to implement PPT in Clover. (As showed in my screenshot)
Very urge to hear from you. Thank you sir!
[automerge]1572316883[/automerge]
Hi,

The PPT kext has some Framebuffer patch, these are not compatible with WEG(1.3.4) "for me". I have an old RadeonVegaLowFansSpeed.kext and it is working with WEG(1.3.4). I just customise the RadeonVegaLowFansSpeed.kext with the PPT kext data and that's it.
Thanks for your explanations.
Can I use your Radeon VII kext directly?
 

Attachments

  • Screen Shot 2019-10-29 at 10.36.33 AM.png
    Screen Shot 2019-10-29 at 10.36.33 AM.png
    165.8 KB · Views: 114
  • Screen Shot 2019-10-29 at 10.36.23 AM.png
    Screen Shot 2019-10-29 at 10.36.23 AM.png
    35.7 KB · Views: 119

CMMChris

macrumors 6502a
Oct 28, 2019
525
410
Check /Devices/Properties in Clover Configurator. There are two fields, one for devices and one for the properties that belong to them. The devices box contains PCI paths. So simply add your Radeon VII PCI path in there. You can obtain the path using the PCI list inside Hackintool for example.

After adding the PCI path in Clover Configurator you can assign properties to it in the second box. For the PowerPlay Table we need to add "PP_PhmSoftPowerPlay Table". The type needs to be "Data". Then you simply paste the Clover Output of my PPT generator as the value of this property.

Your second screenshot doesn't show your GPU highlighted.
 
  • Like
Reactions: zoltm and h9826790

ExperimentalExpressinLab

macrumors newbie
Oct 27, 2019
8
2
@ExperimentalExpressinLab I am the creator of the Radeon VII PPT generator shared here.
On a Hackintosh there is absolutely no need to fumble with codeless kexts for PowerPlay Table injection. Use clover device properties for it. You just need to do it the right way and it will work. Use Hackintool to get the correct PCI path for your graphics card.
Those codeless kexts can get you into trouble especially if they override the entire info.plist of AMD10000Controller. This for example applies to the Kext generated by VGTab.

Also: Don't use VGTab for Vega 64 or Vega 56 if you use a custom card (for reference cards the PPTs generated by VGTab are fine). Reason is "MinimumPWMLimit" which is different on the custom card models. This is kind of a fan calibration value and important for correct fan speeds. So in case you use a custom card please use my Excel PPT Generator for Vega 56/64 and change the MinimumPWMLimit to match your card. You can extract the correct value from the PowerPlay Table inside the VBIOS of your card.

And bear in mind that undervolting Vega 56 / 64 on macOS isn't possible. The driver ignores the voltages set inside the PPT.

Thanks a lot for your information. I already tried with clover method for Radeon VII and Vega 64. I used Hackintool to get the correct PCI patch and I can see the powerplaytable on the IORegistryExplorer. However, when I try to benchmark with Luxmark, didn't effective =(

Btw, I checked your thread for Radeon VII on hackintosh-forum.de and I found a ssdt from apfelnico:

I copied the powerplaytable data to my SSDT and it is work !

I want to use SSDT method on Vega 64. As you said "Auch der Inject per SSDT ist möglich, dafür muss dann jedoch das Format umgewandelt"

Could you please explain how can i convert your Excel PPT Generator result to SSDT format ?
 

CMMChris

macrumors 6502a
Oct 28, 2019
525
410
Well, if it didn't work you did something wrong. Clover device properties always work if done right. But if you don't provide any more information except for "it doesn't work" it will be hard to track down where your mistake is.
In general there is no need to fumble with SSDTs. I personally don't know how to conveniently convert the data for an SSDT. Ask Apfelnico.
 

vikikang

macrumors newbie
Sep 16, 2019
6
5
Thanks a lot for your information. I already tried with clover method for Radeon VII and Vega 64. I used Hackintool to get the correct PCI patch and I can see the powerplaytable on the IORegistryExplorer. However, when I try to benchmark with Luxmark, didn't effective =(

Btw, I checked your thread for Radeon VII on hackintosh-forum.de and I found a ssdt from apfelnico:

I copied the powerplaytable data to my SSDT and it is work !

I want to use SSDT method on Vega 64. As you said "Auch der Inject per SSDT ist möglich, dafür muss dann jedoch das Format umgewandelt"

Could you please explain how can i convert your Excel PPT Generator result to SSDT format ?
Just copy data from excel and go to https://cryptii.com, then click "text" in first column and change to byte, then paste the data, change the "byte" to any other type and change back to "byte". You will get a formal format HEX data with "space" between every two bytes.
Second step, go to AML editor create a new file , paste those you get from cryptic.com, then select all, and use "Edit -- find and replace" function to insert "," between every two bytes.
Last step, replace apfelnico's PPT with your own, you are good to go.
 

Attachments

  • Screen Shot 2019-10-31 at 11.19.11 AM.png
    Screen Shot 2019-10-31 at 11.19.11 AM.png
    72.5 KB · Views: 101
  • Screen Shot 2019-10-31 at 11.19.43 AM.png
    Screen Shot 2019-10-31 at 11.19.43 AM.png
    80.5 KB · Views: 112
  • Screen Shot 2019-10-31 at 11.21.53 AM.png
    Screen Shot 2019-10-31 at 11.21.53 AM.png
    82.5 KB · Views: 98
Last edited:

ExperimentalExpressinLab

macrumors newbie
Oct 27, 2019
8
2
Just copy data from excel and go to https://cryptii.com, then click "text" in first column and change to byte, then paste the data, change the "byte" to any other type and change back to "byte". You will get a formal format HEX data with "space" between every two bytes.
Last step, go to AML editor create a new file , paste those you get from cryptic.com, then select all, and use "Edit -- find and replace" function to insert "," between every two bytes.
Last step, replace apfelnico's PPT with your own, you are good to go.


Thanks a lot =)
 

vikikang

macrumors newbie
Sep 16, 2019
6
5
I'm wondering whether this PPT can work as well in Hackintosh with new Mac Pro SMBIOS that will be available in a short time.
 

h9826790

macrumors P6
Original poster
Apr 3, 2014
15,276
7,572
Hong Kong
I'm wondering whether this PPT can work as well in Hackintosh with new Mac Pro SMBIOS that will be available in a short time.

The PPT table itself should work. But the kext won’t.

However, that’s nothing about 5,1 or 7,1. It’s just because 7,1 only has proper support in Catalina, and my kext won’t work in Catalina. Therefore, they can’t work together yet.

If you use 7,1 SMBIOS in Mojave, that PPT kext will still work, but just no point to do so.
 
  • Like
Reactions: vikikang
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.