Contribute
Register

[GUIDE] Injection of AMD Vega Power and Fan Control Properties

If the problem goes away you could try using a DP to HDMI adapter to drive the third monitor.
Or a DP to DVI adapter as i think this third monitor uses a DVI interface.
 
@jaymonkey
Removing the 3rd monitor has solved the problem! Can't attach it with a DP->DVI Adapter because my card only has 2 DP-Ports which are driving the other displays so i think i'll leave the monitor plugged out for the moment.
Thx for your support!
 
I didn't benchmark each macOS update, but here are my results:

Geekbench:
- macOS 10.4.3: 210857
- macOS 10.4.5 (with or w/o Power Table is about the same): 156916

LuxMark:
- macOS 10.4.5 with Power Table: 34311
- macOS 10.4.5 w/o Power Table: 30042


I hope that lower performances are only with Geekbench..
 
This question might have been posted earlier in this thread but it's like looking for a needle in... an ocean. Of needles.

Just finished my Asrock Phantom Gaming z390 mini ITX with a Power Color Vega 56 as my GPU. Put it in a Fractal Design Nano S case with a beQuiet CPU cooler. Installed 10.14.5 and everything runs smooth but still got a question regarding possible fan control issues.

According to HWMonitorSMC2 the temperatures for both the processor (i9 9900K) and graphics card are very stable in idle state and doesn't run very high under heavy load either.

However, I'm a little concerned regarding the values under the tab "Fans or Pumps", It gives a value of 6000 on all four motherboard fans. In my build, there's only the beQuiet CPU cooler and two fans in the case.

Also, each fan representation (0 through 4) is split into three rows. Could it be that the first row represents the actual fan speed, the second one the lowest value and the third one a max value? Thought I had everything on lock but I'm pretty clueless right now.

See attached image for reference. Temperatures during a 10 minute Media Encoder render.

411063
 
Could it be that the first row represents the actual fan speed, the second one the lowest value and the third one a max value?


@organ,

Yes .... you answered your own question correctly ;)

Cheers
Jay
 
@organ,

Yes .... you answered your own question correctly ;)

Cheers
Jay

Hooray! Then everything works OOTB, without VgTab or any other third party software! Thanks!
 
I'm jumping in here to request some help. I'm on 10.14.5, and suffering the slowdown with my Vega 64. I switched out a RX580 for the Vega, and -think- I did my config.plist properly. Taking the liberty of posting it here, hoping jaymonkey or other experienced person will take a quick look at it, and see if it looks basically correct?
Thanks in advance!
 

Attachments

  • config copy.plist.zip
    2.5 KB · Views: 73
I'm jumping in here to request some help. I'm on 10.14.5, and suffering the slowdown with my Vega 64. I switched out a RX580 for the Vega, and -think- I did my config.plist properly. Taking the liberty of posting it here, hoping jaymonkey or other experienced person will take a quick look at it, and see if it looks basically correct?


@kentval,

I cant see anything wrong with your config.plist, its pretty basic and straight forward, you are correctly setting the IGPU Device Properties for headless configuration using PlatformID 0x3E910003.

You should have Lilu + WhatEverGreen installed which will configure the Vega GPU with a framebuffer ... etc.

With regards to the mention of slowdown .... are you referring to a slower result running the OpenCL test in GeekBench 4 ? ... if so then I think that everyone is seeing this ..... if it's the FCPX BruceX export time of around 21 seconds ? ... then quite a few other users including myself are also experiencing this issue with the 10.14.5 update. It's also effecting some real Macs if you check the Apple forums.

No real reason why or how to fix at the moment, a few theories but nothing concrete.

Hopefully Apple will resolve the issue in 10.14.6 ....

Cheers
Jay
 
Last edited:
Thanks, Jay. After chasing this for a few days, it does indeed seem to be Apple's problem... or at least no one here can figure it out. (Just sorta disappointing since I was getting the same scores with my previous RX580, and I just spent $300 on the Vega. That's life, eh?)

One last thing that I discovered in my travels around this issue, and I think it's worth posting for "all to see" instead of buring it in a single thread. I'll mention it here, hoping you can forward it along to Stork, or whoever:

Clover does not, and likely never will, support hardware NVRAM on 390 boards. If you plan to use Clover and a 390 board, you must use emulated NVRAM.

That's straight from the horse's mouth, over on sourceForge:

Thanks for your help and courtesy, Jay.
 
Thanks, Jay. After chasing this for a few days, it does indeed seem to be Apple's problem... or at least no one here can figure it out. (Just sorta disappointing since I was getting the same scores with my previous RX580, and I just spent $300 on the Vega.


@kentval,

Lets hope that Apple resolve the issue in the next Mojave update (10.14.6).

One last thing that I discovered in my travels around this issue:-

Clover does not, and likely never will, support hardware NVRAM on 390 boards. If you plan to use Clover and a 390 board, you must use emulated NVRAM ... That's straight from the horse's mouth, over on sourceForge


Thanks for the confirmation of the issue with NVRAM on 390 Motherboards .... I have seen several posts on this and other forums indicating that native NVRAM on these boards is troublesome and that in most cases emulated NVRAM must be used.

Cheers
Jay
 
Back
Top