Quote from: Ursul0 on November 24, 2019, 08:05:15 AM

Quote from: pbfarmer on November 24, 2019, 05:26:05 AM

Quote from: sudhsrx on November 22, 2019, 10:13:59 PM

Quote from: pbfarmer on November 19, 2019, 08:28:57 AM

Quote from: KolordZ on November 09, 2019, 11:10:29 AM

Quote from: pbfarmer on November 08, 2019, 11:13:57 PM

Quote from: KolordZ on November 08, 2019, 01:44:48 PM

Hello guys !

I've got 6 Sapphire RX Vega 64 Nitro+ and I would like to knows if someone had test wich parameters is good for this card.

I'm using Claymore V15 for mining Ethereum (ETH) only

I've already test BuriedONE parameter in his video but I've got overclocking errors

Thanks !

Nico

I use the following for ETH on my Nitro 64s - maybe not ultra best, but close enough:

Code:

--RAS 28 --RCDRD 12 --RCDWR 5 --RC 44 --RP 12 --RRDS 3 --RRDL 3 --REF 15600 --RFC 248 --FAW 14

for a couple cards w/ weaker mem chips/controller, i use a slightly less aggressive profile:

Code:

--RAS 32 --RCDRD 14 --RCDWR 6 --RC 44 --RP 12 --REF 15600

Hello pbfarmer !

Thanks for your reply !

What kind of profil do you use in Wattman ?

Nico

I don't use Wattman (or even Windows, honestly,) but basically I lock my core state to p0 (850Mhz) by disabling all states above that, while setting my mem clock to 1107 (p3). Then set your mem p3 voltage to whatever is required for your card - should be somewhere between 800-850mv.

This should get you to ~50MH/s for a Vega64.

hello pbfarmer ...do u meant u r using hive os or some other linux based system.
can u just post a screenshot of your overclock settings.your explanation just went over my head.
please post if u don't mind.

I've built my own linux system, and it's kind of hard to screenshot the settings, as it's mostly done in text file full of hexidecimal values (called a ppt file).

Here's the general idea though, illustrated in a windows tool called OverdriveNTool which many people use instead of wattman. Ignore that it says it's a RX 590 - the idea is the same for a vega. Also note, that every clock/voltage pair are disabled except the first GPU setting (P0) and last memory setting (P2 here, but a vega would be P3).

why do you think that you are changing the voltage of the memory on vega?
it's 1.25V on vega56 and 1.356V on vega64 - actually the reason to flash v56 with v64 bios is to update the mem voltage to 1.356

P.S. also in my experience setting proper phases make GPUs more stable (maybe it has to do with actual electricity supply and/or smoother silicon performance)

Not sure who said anything about changing mem package voltage.

I said to set the 'mem P3 voltage' - which of course actually controls the core/soc line if it's higher than the current core states voltage setting (and it likely will be w/ core p0 at 800mv.) Since the mem (and thus soc) speed is what is really controlling the voltage needs, given that the core clock is so low in this scenario, to me it makes sense to make the appropriate setting there, rather than at the core clock parameter.

And you could likely use mem P0 instead, or rewrite your core states to have 850/800 at p7, but i've found it unnecessary - no stability problems in my experience.