• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

The RX Vega 64 Owners Thread

Doogles said:
Yeah I've been keeping an eye out for them but I haven't seen any news, you'd think AIB would have been out much earlier considering the biggest downfall of Vega is that reference cooler, Volta will soon be here to wipe the floor but AMD still haven't cashed in!
Click to expand...

Oh jeez, what's this Volta now? I'm currently debating between a 1070Ti and Vega. You may have seen my thread: https://forums.overclockers.co.uk/threads/1070ti-or-wait-for-custom-vega-64-cards.18798269/
 
r22snapper said:
It definitely does. I have the same monitor and kept my 1080 for about 2 weeks, not worth losing freesync on that screen IMO, performance will be better than a 1080 and it's £50 cheaper. Win win.
Click to expand...

I think I had my 1080 for about 6 weeks, At first I didn't notice not having Freesync but I found that with more demanding titles the difference was there, Initially I built my new PC in the my old case so the 1080 could be used and I wouldn't have to rush into buying another gpu but it didn't work out like that.
 
MrDavies said:
Would you advise waiting?
Click to expand...
Waiting can end up a game in itself. At some point jump in and try what you want. Volta rd1 may not have HBM for the gaming cards. Likely to be GDDR6 with the lower end cards possibly getting GDDR5X. It's likely an architecture update too going by how the current compute card is designed.

Personally I'm interested in the performance of Volta, but not looking to upgrade until Vega 2 is out.
 
gupsterg said:
NP :) , nice to make your acquaintance as well :) . Yes, FreeSync was biggest factor, then I hated the nVidia driver panel as well.

I hope you can see the MSI GTX 1080 EK X was no way stock concerning clocks/vbios besides cooling. So I have merely made VEGA similar with tweaks :) .
Click to expand...

Yeah looking back as long as people buying the reference cooler are aware that you've still had to tweak the hbm2 clock, power limit and voltages for Vega then I don't think there's a problem. On the other side though the 1080 was at a similar advantage, (like you say) from the water cooling helping it boost higher, just without memory oc. In essence both gcards have more to untap, but the Vega I don't doubt has to more to tweak and more to unleash at the cost of heat/power draw but heyho, even from your current 1610-/+ clock it'd be nice to plot frequency gain vs fps scaling say if you're lucky to get 1750-1800 mhz. Then we could put the difference in ref vs custom cooling in perspective of value.
Hwbot shows a greater range of 1080's at firestrike 1080p scaling from 23k- 25k+. But regardless I have just stumbled onto your vega bios thread and that's going to keep me reading for a while :)



gupsterg said:
I have no idea fully yet how VEGA is concerning VID/VDDC, but it is not definitely not fixed or as we see when we change to manual voltage in Wattman. I believe VEGA is employing the most advanced "tuning" techniques AMD have at their disposal.

AFAIK V56/V64 when we change to manual mode DPM7 1200mV is pulled from PowerPlay (ATOM_Vega10_Voltage_Lookup_Table).

Code: 
7A 00 (0x7Ah)       USHORT usVddcLookupTableOffset;            /* points to ATOM_Vega10_Voltage_Lookup_Table */

typedef struct _ATOM_Vega10_Voltage_Lookup_Table {
01   UCHAR ucRevId;
08   UCHAR ucNumEntries;                                          /* Number of entries */
   ATOM_Vega10_Voltage_Lookup_Record entries[1];             /* Dynamically allocate entries */
} ATOM_Vega10_Voltage_Lookup_Table;

typedef struct _ATOM_Vega10_Voltage_Lookup_Record {
20 03 (800mV)   USHORT usVdd;                                               /* Base voltage */
} ATOM_Vega10_Voltage_Lookup_Record;

typedef struct _ATOM_Vega10_Voltage_Lookup_Record {
84 03 (900mV)   USHORT usVdd;                                               /* Base voltage */
} ATOM_Vega10_Voltage_Lookup_Record;

typedef struct _ATOM_Vega10_Voltage_Lookup_Record {
B6 03   USHORT usVdd;                                               /* Base voltage */
} ATOM_Vega10_Voltage_Lookup_Record;

typedef struct _ATOM_Vega10_Voltage_Lookup_Record {
E8 03 (1000mV)   USHORT usVdd;                                               /* Base voltage */
} ATOM_Vega10_Voltage_Lookup_Record;

typedef struct _ATOM_Vega10_Voltage_Lookup_Record {
1A 04 (1050mV)   USHORT usVdd;                                               /* Base voltage */
} ATOM_Vega10_Voltage_Lookup_Record;

typedef struct _ATOM_Vega10_Voltage_Lookup_Record {
4C 04 (1100mV)   USHORT usVdd;                                               /* Base voltage */
} ATOM_Vega10_Voltage_Lookup_Record;

typedef struct _ATOM_Vega10_Voltage_Lookup_Record {
7E 04 (1150mV)   USHORT usVdd;                                               /* Base voltage */
} ATOM_Vega10_Voltage_Lookup_Record;

typedef struct _ATOM_Vega10_Voltage_Lookup_Record {
B0 04 (1200mV)   USHORT usVdd;                                               /* Base voltage */
} ATOM_Vega10_Voltage_Lookup_Record;

EgvJiHD.jpg

Asder00 of Guru3D, famed for providing AMD drivers in the past before release and has helped in Hawaii bios mod (has some tools which can't share ;) ) posted this from VEGA, link.

So I believe AVFS is active. Besides Platform_Caps in powerPlay, marketing slides, etc, I see the case from monitoring data. I do believe there are "states" of GPU clock which we are unaware of and SW is not showing.

Let's roll back to Hawaii for a moment. Hawaii used EVV, in VBIOS where there were 8 DPM states, did PowerTune have only 8?



From page 8 of this basic whitepaper.

Even when we set manual VID for a DPM the voltage was never fixed. The GPU would have clocks/voltages between each DPM, etc. This perplexed some owners.

Now how did we know what EVV/ASIC Profiling determined as VID per DPM? First tool we had was shared by The Stilt. His own tool made for his own "work". This only showed DPM 7, you can find the posts in a thread on Guru3D from 2015. Next we found AIDA64 allowed dumping of GPU registers and translated VID per DPM, also worked on GPUs upto Polaris. It does not for VEGA yet, but I do believe it may not. Why I say this is AMD have locked down VEGA hard compared with past cards. AIDA64 register dump is so small on VEGA vs past cards.

I2C comms has been disabled to voltage control chip. Originally VEGA FE VBIOS showed The Stilt it was disabled via registers set. RX VEGA does not have those registers set. So it is believed now the driver is blocking access or another strategy has been employed. TBH even the voltage control chip does not have full control, it is a slave to the SMU. Scanning i2c on Fiji was slow, as SMU kept the line busy. This is why GPU-Z didn't have as many monitoring values for it as Hawaii. HWINFO author also had issues using i2c then reverted to AMD ADL. MSI AB employs "messaging" SMU via driver to do changes on Fiji onwards, previously voltage control on Hawaii was i2c in MSI AB via voltage control chip. I believe MSI AB on VEGA will be using "messaging", it has command line messaging capability as will (some messages can be found in Linux driver).

I believe VEGA is using SMU far more than Fiji and implemented heavier than it. Also I believe VEGA has/is SOC GPU (see VEGA whitepaper before linked).

VEGA also has on die hardware to check VBIOS is correct for ASIC. You can crossflash V56/V64 as they use same device ID, but you can not crossflash VEGA FE. Last I read recently even VEGA FE owners can not use later RX VEGA drivers/path. I was going to suggest to a member on OCN to edit inf, but I believe it may pick up "fused ASIC ID". An example of this was Hawaii flashed to Grenada still showed as Hawaii as driver picked up "fused ASIC ID".

Sorry for mega post :o .
Click to expand...

Great info there thanks, I've followed the stilt for years in his examination of Kaveri and then Godaveri/ Carrizo etc. How different or advanced is Vega over Polaris in the registers and powerplay tables?
For example Polaris looks like this but with Avfs/ temperature, current load etc the voltage and frequency tables obviously ride as close to the p-state.
Here's two examples of my rx470, 0% power limit and 15% power limit at auto voltage and auto clocks,
38tU5ue.jpg
hfqlEES.jpg
 
Last edited:
TrixX said:
Indeed they will, though my point on the cards performance still holds. The issue is that Nvidia has a drop in solution vs the tweaking required to get the best out of Vega. In that way Nvidia have managed to corner the market nicely as it's easy to get 100% performance out of their cards due to their boost implementation. Something Vega has tried to copy and gotten it backwards.

I guess my card is one of the luckier cards about, massive OC headroom and great undervolting (down to 900mv) though I've see a few of the guys mining hitting 800mv with some tweaking down. Though I wouldn't say it's far fetched for V56/64 to beat 1080's quite handily in games that support DX12's feature sets. In fact the more DX12 features used/supported seems to correlate with how much a Vega beats the 1080. The recent releases of Destiny 2, Forza 7 and TW Warhammer 2. Admittedly DX11 is not Vega's strong suit but it's definitely no slouch there either.
Click to expand...

900mv is nice to get to what clocks does that hold?, I run my rx470 at 1150mhz at 1.0v and this is a sweetspot. I agree Nvidia has them hard against the wall now. I don't dispute that you are others can get v56/64 upto and close to and beyond the 1080, especially in dx12 titles as you say. I noticed during the early days of Fiji that AMD had a scheduling problem in dx11 in particular at 1080p.
 
1Q0FVfkpkSyYa5KCwcf8h-FywZML5e4oeVJ5GR1uB1Q
 
Davedree said:
900mv is nice to get to what clocks does that hold?, I run my rx470 at 1150mhz at 1.0v and this is a sweetspot. I agree Nvidia has them hard against the wall now. I don't dispute that you are others can get v56/64 upto and close to and beyond the 1080, especially in dx12 titles as you say. I noticed during the early days of Fiji that AMD had a scheduling problem in dx11 in particular at 1080p.
Click to expand...
Well I use the voltage to create a stable clock instead of allowing ACG to cause all sorts of havoc when testing :D

900mv is around the ~1389MHz (+/-4fps) range with my P7 set to 1752MHz and min/max locked for testing. Oddly I found I couldn't do low mv with 950MHz HBM, though with 1050MHz HBM I was able to reach 900mv no worries using Superposition to test. Here's a range of tests I just performed over the last 40mins.

900mv- ~1388MHz Actual @ 99% GPU load
17.10.31-10.15amSuperpositionExt1752p7900mv1050m900mv.png
910mv
17.10.31-10.11amSuperpositionExt1752p7910mv1050m900mv.png
920mv
17.10.31-10.07amSuperpositionExt1752p7920mv1050m900mv.png
930mv
17.10.31-10.03amSuperpositionExt1752p7930mv1050m900mv.png
950mv
17.10.31-9.55amSuperpositionExt1752p7950mv1050m900mv.png
970mv - ~1588MHz Actual @ 99% GPU load
17.10.31-9.47amSuperpositionExt1752p7970mv1050m900mv.png

890mv However this one doesn't show any significant difference to the 900mv so I have to conclude the 890mv didn't apply and it was actually 900mv.
17.10.31-10.15amSuperpositionExt1752p7890mv1050m890mv.png

All the above were tested with HBCC on (minimum memory used on slider) and the below settings only adjusting the mv for P7 between runs:
OCUK_UV_test.PNG
 
Last edited:
HBM Overclocking up to 1200Mhz is now possible. Tested and i see a performance boost up to 1175Mhz. 1200Mhz crashed instantly.

Safe to say Vega overclocks pretty damn well and you can increase performance nicely with tuning.
2qv.png
 
You must log in or register to reply here.
Back
Top Bottom