So what do you think about WattMan in Crimson ReLive edition?

[gupsterg]

Crimson ReLive edition has WattMan for R9 Fury Series, R9 390 Series, R9 380 Series, R9 290 Series, R9 285 Series, R9 260 Series, R7 360 Series and R7 260 Series.

IMO one of the biggest things this gives users is VID per DPM control plus GPU clock per DPM.

VID is the voltage the GPU is requesting. Simply put VDDC can be lower depending on LLC / what applications is loading GPU, even when GPU is in same DPM state.

Currently all monitoring applications show VDDC and not VID. AIDA64 through a registers dump can give users VID per DPM. WattMan also shows VID per DPM when a user wishes to edit voltage.

Why is editing VID per DPM better than voltage offsets we have used in MSI AB or Sapphire TriXX? A voltage offset increases VDDC for all DPM states, but we are usually only after VDDC increase on highest state of GPU as we aim to OC that.

The other plus I see with VID per DPM being exposed, is users can now compare voltage better with one another. For so long all I've seen is I gain x clock of GPU with x offset, which is pretty much useless as every GPU will have varying VID per DPM.

Next WattMan allows Advanced fan profile modification on Polaris, it does not on Fiji, I plan to see what it does on Hawaii. Advanced fan profile uses "Fuzzy Logic" based on some settable parameters to adjust fan profile "on the fly" based on GPU temperature/power usage. MSI AB or Sapphire TriXX allow custom fan profiles, these profiles are like if ROM was using Lookup table fan profile (ie do x for x temp).

WattMan on Polaris shows a memory clock editing section which shows multi states, it still only allows editing of highest state of RAM clock. I plan to test if on Fiji and Hawaii where I modify ROM to have more states than stock versions do we see the facility to modify more states. The memory voltage control in WattMan does not modify RAM voltage on Polaris, from data where owners have used a multimeter to check a view has been formed it is changing memory controller voltage. On stock Fiji ROM there is no memory voltage section in WattMan. Hawaii does not have a voltage control chip with data interface to allow software to change RAM voltage. Only Asus Matrix and MSI Lightning cards do, so I don't expect it to be there. If it is there I would assume it will change memory controller voltage, like Aux voltage editing in MSI AB or Sapphire TriXX does.

Another plus of WattMan is within gaming profiles you can set an OC per game.

Due to some gripes with what WattMan is allowing on Fiji compared with Polaris I will still opt for bios mod as I prefer that. This is a shame as Tonga, Fiji and Polaris share the same revision of PowerPlay in ROM. I do like the features within WattMan as they give access to some settings which MSI AB or Sapphire TriXX does not (currently ) .

 

[Solaris17]

DPM being exposed is users can now compare voltage better with one another.

I agree! I also agree with this statement. The only issue. is that they would also need to make sure the testing settings were 100% identical. You would not be able to compare for example the VID of someone running a game on medium vs high. It would be important during comparisons to make sure to mention this.

 

[gupsterg]

Yes indeed .

It took me a while to get to grips with what occurs with voltage as often it is not discussed in the manner it should be. Hopefully it will be now.

Voltage is complicated by PowerTune, which is something I like TBH. Viewing launch reviews and the publicly available AMD PDFs on PowerTune helps some what, but they lack depth IMO that I'm after.

For example it is easy to think there are only 8 DPM states from viewing ROM/WattMan but there are more.

PowerTune is also highly granular in terms of its ability to manage clocks. While previous GPUs had only 3 or 4 power states (idle/low, medium, and peak), a GPU with PowerTune contains hundreds of intermediate states in between the primary power states to maximize performance within the TDP constraint.

Quote from, page 6, paragraph 2.

 

[AsRock]

Nope not yet waiting on possible issue's pop up befor i try them, as a gamer as long as the fps is about 35+fps i cut the speed and power usage though afterburner, although if Wattman can give me the options as Afterburner can i may try it.

 

[gupsterg]

@AsRock

Even in your scenario still WattMan maybe beneficial to you compared with VDDC offset that MSI AB or TriXX does.

For example on Hawaii the GPU can become unstable if it's voltage is too low when RAM spikes up a state when GPU state is low = low VID/VDDC.

You will have noticed on your 290X when at desktop the GPU clock can bounce up and RAM can also from the 150MHz idle to 1250MHz (or higher depending on card). Usually when this bounce occurs the GPU will not climb to highest state = lower VID/VDDC. The VDDC offset in MSI AB or TriXX reduces all states VDDC and as lower states are lower voltage than higher states you could get instability due to the RAM state bounce as well.

So with WattMan you can tune lower states to a level where when the RAM clock bounce occurs and GPU clock is say DPM 0, 1, 2 or 3 it does not become unstable. Then for higher states where VID/VDDC is higher you can do a different level of tuning of VID/VDDC.

Here is an example of VID per DPM for a 290X I owned.

------[ GPU PStates List ]------

DPM0: GPUClock = 300 MHz, VID = 0.96800 V
DPM1: GPUClock = 516 MHz, VID = 1.05000 V
DPM2: GPUClock = 748 MHz, VID = 1.05600 V
DPM3: GPUClock = 865 MHz, VID = 1.08700 V
DPM4: GPUClock = 916 MHz, VID = 1.11800 V
DPM5: GPUClock = 964 MHz, VID = 1.16200 V
DPM6: GPUClock = 1006 MHz, VID = 1.20600 V
DPM7: GPUClock = 1030 MHz, VID = 1.24300 V

Now when you set an offset all the VIDs have been reduced by that offset. With WattMan you could reduce DPM 0 to 3 with -25mV VID reduction and higher states with differing reduction. Depending on your silicon it may overall be a improved reduction of power with improved stability.

How to test a DPM?

i) Using MSI AB or TriXX set GPU clock as a DPM you wish to tune, for example DPM 2 is 748MHz on above card.
ii) Set an offset you wish to test.
iii) Run an application on the GPU like 3DM FS and card will only go to 748MHz and use the corresponding VID with offset you applied.
iv) After you have assessed what offset works for that DPM, open MSI AB or TriXX and reset card to defaults.
v) Reduce the VID in WattMan for the DPM you tested with the amount of offset you used in MSI AB or TriXX allowing you to tune it .

 

[Ebo]

None of the choices above.

the reason for that is simply that the way I see it, theres too many unknowns.

1. your PSU and it preform
2. your MB(depending on bios and stability)
3. how far is your system pushed overall ?.

 

[gupsterg]

@Ebo

WattMan is restricted more for voltage adjustment range than MSI AB or TriXX.

Stock ROMs profile the ASIC on PCB to set VID per DPM. This way a manufacturer is not tailoring ROM per GPU on PCB for model of card. The ROM has values on what the VID can be based on LeakageID, GPU clock etc. One of these values is the max VID a GPU can be under profiling, basically this sets the limit of VID in WattMan in a way.

For example my Fury X has DPM 7 as 1.212V, so in WattMan I can only go upto 1.250V. Only if I modify my ROM will WattMan allow extra VID above 1.250V, but the driver still has 1.300V limit on Fiji and only way around that is VDDC offset which it can't detect.

Now IIRC MSI AB allows +100mV and TriXX +200mV. So my stock ROM of Fury X profiles DPM 7 as 1.212V, with a VDDC offset it resulting in VID of 1.312V or 1.512V. But also the voltage control chip IR3567B has a VMAX limit of 1.48125V (again can be edited), regardless of if you use a VID and/or VDDC offset it will not allow more voltage than VMAX.

As stated in OP due to GPU properties even the same model of GPU will have a different VID on stock ROM, so each card will have differing headroom for positive increase of VID in WattMan.

 

[AsRock]

@AsRock

Even in your scenario still WattMan maybe beneficial to you compared with VDDC offset that MSI AB or TriXX does.

For example on Hawaii the GPU can become unstable if it's voltage is too low when RAM spikes up a state when GPU state is low = low VID/VDDC.

You will have noticed on your 290X when at desktop the GPU clock can bounce up and RAM can also from the 150MHz idle to 1250MHz (or higher depending on card). Usually when this bounce occurs the GPU will not climb to highest state = lower VID/VDDC. The VDDC offset in MSI AB or TriXX reduces all states VDDC and as lower states are lower voltage than higher states you could get instability due to the RAM state bounce as well.

So with WattMan you can tune lower states to a level where when the RAM clock bounce occurs and GPU clock is say DPM 0, 1, 2 or 3 it does not become unstable. Then for higher states where VID/VDDC is higher you can do a different level of tuning of VID/VDDC.

Here is an example of VID per DPM for a 290X I owned.

------[ GPU PStates List ]------

DPM0: GPUClock = 300 MHz, VID = 0.96800 V
DPM1: GPUClock = 516 MHz, VID = 1.05000 V
DPM2: GPUClock = 748 MHz, VID = 1.05600 V
DPM3: GPUClock = 865 MHz, VID = 1.08700 V
DPM4: GPUClock = 916 MHz, VID = 1.11800 V
DPM5: GPUClock = 964 MHz, VID = 1.16200 V
DPM6: GPUClock = 1006 MHz, VID = 1.20600 V
DPM7: GPUClock = 1030 MHz, VID = 1.24300 V

Now when you set an offset all the VIDs have been reduced by that offset. With WattMan you could reduce DPM 0 to 3 with -25mV VID reduction and higher states with differing reduction. Depending on your silicon it may overall be a improved reduction of power with improved stability.

How to test a DPM?

i) Using MSI AB or TriXX set GPU clock as a DPM you wish to tune, for example DPM 2 is 748MHz on above card.
ii) Set an offset you wish to test.
iii) Run an application on the GPU like 3DM FS and card will only go to 748MHz and use the corresponding VID with offset you applied.
iv) After you have assessed what offset works for that DPM, open MSI AB or TriXX and reset card to defaults.
v) Reduce the VID in WattMan for the DPM you tested with the amount of offset you used in MSI AB or TriXX allowing you to tune it .

With some game run fps around 35-60fps and run the gpu @ 800MHz cannot remember how much lower the gpu voltage was off hand but a saving of 100w in power usage.

It just depends on the game, now if Wattman can allow many profiles which it sounds like it does then i will try it soon.

Like any thing done right takes time, although i don't know whats available in wattman i may have a look at it in a minute and just see what it offers.

 

[gupsterg]

@AsRock

Yes, per game over/under, clock/voltage, works I have tried a few on Fiji card , will be trying on my Hawaii soon . This adds a further dimension to SW manipulation of GPU than MSI AB or TriXX .

 

[Ungari]

I have already noticed improvement with the driver, but as to Wattman, I'm still learning it's features.
As to whether Wattman will obviate the need for BIOS Mods, I'm not sure as I have Dual BIOS chips so I'm inclined to do so if it's easier.

 

[biffzinker]

Looks like I'll have to wait on the poll/reply until I can get my hands on the XFX Radeon RS RX 480 on Christmas.

This is all get for a R9 280.

 

[AlienIsGOD]

i love wattman even tho im not o/c ing at all. i use custom fan speed and custom target temp for my 480. Keeps it at around 68C - 74C reference version as well

 

[INSTG8R]

Disappointed. Went back to Trixx. I'm just running a 50hz OC to get my card to Fury X Specs. Target Temp still makes it throttle as soon as it gets close(set for 70 it throttles at 69 without fail)instead of spinning up the fans. This also makes even that small OC unstable. Trixx I can set my own fan curve(Wattman can't)it's rather aggressive so card doesn't even see 60C anymore let alone 70 and the OC is rock solid in everything. I'd hoped for more control.

 

[gupsterg]

Looks like I'll have to wait on the poll/reply until I can get my hands on the XFX Radeon RS RX 480 on Christmas.

This is all get for a R9 280.
View attachment 81819

You basically have OverDrive in WattMan skin , I think I'm gonna get the same on my Hawaii card .

i love wattman even tho im not o/c ing at all. i use custom fan speed and custom target temp for my 480. Keeps it at around 68C - 74C reference version as well

View attachment 81820

Yeah Polaris gets a fuller feature set compared with Fiji and Tonga in WattMan, even though they use same PowerPlay in ROM. You will see in this section of Linux driver basically translation of PowerPlay, only certain sections are tailored to each GPU but they share same structure/parameters with only few differences.

Disappointed. Went back to Trixx. I'm just running a 50hz OC to get my card to Fury X Specs. Target Temp still makes it throttle as soon as it gets close(set for 70 it throttles at 69 without fail)instead of spinning up the fans. This also makes even that small OC unstable. Trixx I can set my own fan curve(Wattman can't)it's rather aggressive so card doesn't even see 60C anymore let alone 70 and the OC is rock solid in everything. I'd hoped for more control.

Yes, Advance fan profile modification is missing for Fiji , due to these gripes I will still bios mod Fiji.

 

[INSTG8R]

Yes, Advance fan profile modification is missing for Fiji , due to these gripes I will still bios mod Fiji.

Yeah somewhere in the later drivers they've forced it to throttle the clocks over spinning up the fans. My 70 Target was fine until lately so I gave up and tried using Trixx, I already had it installed to check it out when they recently updated it. As I said my fan curve is pretty aggressive(and loud) but it's certainly not throttling Don't really care about noise, my casefans are doing 2K at anything over 35C case temps so they win for noise anyway.

 

[Ungari]

The Default Fan Curve for my Factory OC still has the fans off under 60C.
I have a Custom Curve for Manual OC Profiles that is absolutely necessary to maintain the Boost.

 

[Kofoed]

i love wattman even tho im not o/c ing at all. i use custom fan speed and custom target temp for my 480. Keeps it at around 68C - 74C reference version as well

View attachment 81820

Question:

Have you had problems with the fan not spinning after a restart? I've had my fans on my Sapphire 390 being completely turned off and resulting in a system crash a few times now..
For me I need to leave it on auto or it won't work after a reboot :s

 

[eidairaman1]

Disappointed. Went back to Trixx. I'm just running a 50hz OC to get my card to Fury X Specs. Target Temp still makes it throttle as soon as it gets close(set for 70 it throttles at 69 without fail)instead of spinning up the fans. This also makes even that small OC unstable. Trixx I can set my own fan curve(Wattman can't)it's rather aggressive so card doesn't even see 60C anymore let alone 70 and the OC is rock solid in everything. I'd hoped for more control.

Ive never like variable clockspeed on any card no matter green or red, either force it to run at max performance in games or lower performance for less demanding tasks.

Question:


Have you had problems with the fan not spinning after a restart? I've had my fans on my Sapphire 390 being completely turned off and resulting in a system crash a few times now..

For me I need to leave it on auto or it won't work after a reboot :s

go to AMD forums and ask the question. Talk to Sapphire support too.

 

[AlienIsGOD]

Question:

Have you had problems with the fan not spinning after a restart? I've had my fans on my Sapphire 390 being completely turned off and resulting in a system crash a few times now..
For me I need to leave it on auto or it won't work after a reboot :s

no i havent, mine restarts fine

 

[Kofoed]

Alright thanks. Must just be my card that is acting weird then.. :/

 

[Ungari]

Disappointed. Went back to Trixx. I'm just running a 50hz OC to get my card to Fury X Specs. Target Temp still makes it throttle as soon as it gets close(set for 70 it throttles at 69 without fail)instead of spinning up the fans. This also makes even that small OC unstable. Trixx I can set my own fan curve(Wattman can't)it's rather aggressive so card doesn't even see 60C anymore let alone 70 and the OC is rock solid in everything. I'd hoped for more control.

With Trixx I had saved the profile but the Voltage bumps keep getting reset to Zero offset.

 

[Caring1]

The Poll doesn't make sense, most of the choices are questions that require a yes or no answer.

 

[Octopuss]

Functionality-wise the program is ok.
However the interface is a little annoying, and it's pain in the ass to click through to.

 

[gupsterg]

The Poll doesn't make sense, most of the choices are questions that require a yes or no answer.

Hmmm, the poll is relevant IMO to OP title . The 1st set of questions indicate to a viewer quickly how many think it is a positive or negative to drivers, so basically what someone thinks of WattMan in concise manner. 2nd set of questions is basically to see how many intend to use it or not and 3rd set is to deem if having access to WattMan has given users what they need not to choose bios modding.

 

[chuck216]

Frankly I think it sucks... not the overclocking tools, but the fan controls. Or rather lack of fan controls. With my R9 390 I am unable to manually set a fan profile or even set it to a set speed. And If I try to set one with the Asus GPU tweaker it crashes the Video driver. So I'm stuck with the default fan profile on my 390 Strix which doesn't even turn the damn fans on until it hits 65c. That's way too hot in my opinion. That's what I want at full load, not with mild use.