Contribute
Register

[TOOL] VGTab: Control your Vega in macOS without flashing the vBios

As I said, you need to remove the GPUSensors Kext for iStat to work properly. You also might need to completely(!) uninstall iStat and re-install it again for it to display the correct values.

istat worked but I do not like anything graphic environment I like much more HwMonitor xD. Is there currently no version compatible with HwMonitor with Vega64 and mojave? thanks!!
 
istat worked but I do not like anything graphic environment I like much more HwMonitor xD. Is there currently no version compatible with HwMonitor with Vega64 and mojave? thanks!!
I have it working in iStat and HWMonitor. I'm attaching my FakeSMC for you. You don't need anything else and make sure not to update it. Everything will say it's out of date, but the new one doesn't work.

Screen Shot 2019-07-14 at 10.28.30 PM.png

Screen Shot 2019-07-14 at 10.29.53 PM.png
 

Attachments

  • FakeSMC.kext.zip
    147.6 KB · Views: 89
istat worked but I do not like anything graphic environment I like much more HwMonitor xD. Is there currently no version compatible with HwMonitor with Vega64 and mojave? thanks!!


@FernandoCoverdale,

The only other hardware monitor that works well with Vega is HWMonitorSMC2, it hooks into the MacOS IOAccelerator task to display the dGPU sensor values, rather than reading them directly from the card.

For more info see the following Guide :-


Move down to the section titled "Monitoring of VEGA GPU Sensors" which is towards the bottom of the guide. It's still a work in progress but shows good potential.

Cheers
Jay
 
I have it working in iStat and HWMonitor. I'm attaching my FakeSMC for you. You don't need anything else and make sure not to update it. Everything will say it's out of date, but the new one doesn't work.

View attachment 416409
View attachment 416410
@FernandoCoverdale,

The only other hardware monitor that works well with Vega is HWMonitorSMC2, it hooks into the MacOS IOAccelerator task to display the dGPU sensor values, rather than reading them directly from the card.

For more info see the following Guide :-


Move down to the section titled "Monitoring of VEGA GPU Sensors" which is towards the bottom of the guide. It's still a work in progress but shows good potential.

Cheers
Jay


Thank you very much everyone. I am going to perform tests with all the information you have given me.
:headbang:
 
I have it working in iStat and HWMonitor. I'm attaching my FakeSMC for you. You don't need anything else and make sure not to update it. Everything will say it's out of date, but the new one doesn't work.

View attachment 416409
View attachment 416410

WOoooo Work!!!!
Thank you so much

Versión instaled= 3.5.1
Versión in a server = 1800

Is this the latest version that works?
 
WOoooo Work!!!!
Thank you so much

Versión instaled= 3.5.1
Versión in a server = 1800

Is this the latest version that works?
Yes. The newer versions changed how they handle plugins and I've yet to see any of them work. This is one of those, if it ain't broke don't fix it situations, lol.
 
VGTab is not necessary anymore. Everything works out of the box. You only need to use a PowerPlay Table if you want to overclock the card now.
Hi, forgive the n00b question, I'm new to Vega tweaking. I've just ordered a Vega 56 (MSI Air Boost OC) to use with 10.14.5. If my goal is to achieve the lowest possible power usage, could I do that with either VGTab or the PowerPlay Table Excel sheet? For the Excel method would I just enter a desired value in the cell Power Limit (W) and/or Current Limit (A)?

My goal is to get power consumption <200W under load, similar to the "Power Save" BIOS 2 profile available in Windows WattMan, or even better the "Power Limit -25%" BIOS 2 profile shown in this Tom's Hardware article. I'd like to use the 10.14.5 native drivers with as few tweaks as possible to reduce power consumption, with a kext.

Thanks for any advice!
 
You can limit consumption with Power Limit W in my Excel sheet but this will also limit the clock speed your card is able to reach which doesn't make that much sense. You should have opted for an RX580 or RX590 if you don't want to use your Vega 56 to its fullest potential.
 
You can limit consumption with Power Limit W in my Excel sheet but this will also limit the clock speed your card is able to reach which doesn't make that much sense. You should have opted for an RX580 or RX590 if you don't want to use your Vega 56 to its fullest potential.
Yeah, I had been looking at the RX580, but when I saw the Vega 56 on sale for $229 I couldn't pass it up.

Tom's found the Vega 56's power / performance "sweet spot" to be about 190W TBP, with diminishing performance returns with any additional power. My system is a bit power limited so I'm interested in getting as much Vega performance as I can within a safe amount of power consumption, if possible. Will experiment with the Excel sheet, thanks!

aHR0cDovL21lZGlhLmJlc3RvZm1pY3JvLmNvbS9CL1IvNzA2NzQzL29yaWdpbmFsLzEzLVN3ZWV0LVNwb3QucG5n
 
What temperatures does your vega reach? mine at rest is usually over 49 ° C
If you passed a performance test with the Heaven program, putting maximum performance "ultra" reaches temperatures of about 90 ° C Is this normal? I think it's too much :(
Sapphire Nitro Vega 64
 
Back
Top