Quote from: livada on December 24, 2018, 01:21:33 PM

Quote from: pbfarmer on December 20, 2018, 10:04:21 PM

Quote from: GordoLui on December 19, 2018, 11:47:49 PM

Just a small update on how my small farm is doing, I been running this miner for a week now pretty stable with almost no issues. Not sure how I can check for the percentage of rejected and accepted shares, but all the numbers seem to have evened out. All my miners have been running almost all the same across the board. Maybe a few points of difference between them but they can all hit at least 1900 sol/s for my vega 56's.

A few days ago I read a reddit post of a dude saying he was able to hit 2000 sol/s on his vega 56 with an extremely reduced power draw. He was using the recently released adrenalin drivers but didn't give out much more information. So far I have downloaded the second to latest drivers and have been able to closely replicate the results i had with using the soft powerplay table mod and using overdriveN tool. It does feel like there is room for fine tuning but i wouldn't know where to start. Ideally I would like to hit the 2000 sol/s using 115w on gpu-z. Maybe not that low but having a system total power draw of 500w or under for 3 vega 56 would be very nice.

Haha - "sol/s"... someone's been mining ZEC? Wink

I have mostly 64s, but my one 56 is running around 1950 H/s at sub-160W ATW. It doesn't seem to be the best asic quality, and is a bit old, so I would expect better from a larger sample set. I also flashed to 64 rom a while ago, which is useless for CNv2 (unless you don't care about power use,) so even lower power use should be expected on a stock rom given that 56 mem runs at a lower voltage, while it's tighter mem timings allow similar results at lower clocks.

For 2K H/s (and best efficiency,) I would suggest a voltage setting of around 840mv (or less if you can get away w/ it,) while targeting a 1400 effective core clock. I say effective, because the low voltage will almost certainly cause significant core clock throttling, so you will likely have to set your P7 clock much higher than 1400 to get to that level while under a mining load. For example, I run a 1450 @ 835mv P7 setting, and only get a ~1360 effective clock out of it. On some of my 64s, my clock setting ranges from 1430-1500 (@ 815-850mv) to get to ~1400 effective. As for mem clock, I believe you're looking for a ~950Mhz setting for a 56 - higher is obviously better, if possible.

Regarding the PPT, it really is only necessary for two reasons. The first is to lower your P0-5 power state voltages to allow undervolting P6/7 appropriately. This is necessary via PPT, because P0-5 can't be set w/ ODNT/Wattman/etc, but power state voltage settings must be in ascending order. In other words, w/o PPT, the floor for P6/7 voltage is whatever the stock P5 voltage is set to - around 1.1v iirc. With that in mind, I set my P0-P5 @ 800-805mv via PPT, then tune P7 (while miner is running) as appropriate via ODNT. 1450 @ 840mv is prob a good P7 starting point while tuning.

The second purpose of PPT is to lock in your final settings once you're done tuning, as it seems the drivers don't seem to always honor the ODNT voltage settings on load, but if those same settings are written to PPT, they 'stick'. This also technically removes the need for loading ODNT profiles at startup, though it doesn't hurt anything to continue to do so.

So in short, your steps are:

1. Create a first PPT simply to drop your voltage floor
2. Tune while miner is running to get to an appropriate/stable P7
3. Recreate PPT using final P6/7 values

A couple other notes:

- a cn_config setting (for trm) of 15+15 seems to be better than 16+14, at least for these lower clocks

- CNv2, esp w/ the TRM rocketship, is an unstable beast power wise. Settings which may seem stable at first (even for hours,) may lead to a crash at some point due to power starvation. Even once you think you've found the correct settings, expect to have to dial voltages up (or clocks down) by increments of 5-10 over time to get to a truly stable setup.

- You can create PPTs via ODNT, by running in admin mode, then clicking on the GPU icon (top left) and selecting 'PPTable Editor'.

- As a starting point, here is my ODNT profile for my 56, though every card, properly tuned, will have different P7 values (also note my mem clock setting is for a 64 bios):

Code:

[Profile_66]
Name=cn8-srvega56-s-r1-2
GPU_P0=852;800
GPU_P1=991;801
GPU_P2=1084;802
GPU_P3=1100;803
GPU_P4=1125;804
GPU_P5=1150;805
GPU_P6=1350;815
GPU_P7=1450;835
Mem_P0=167;800
Mem_P1=500;800
Mem_P2=800;802
Mem_P3=1107;830
Fan_Min=300
Fan_Max=4000
Fan_Target=50
Fan_Acoustic=0
Power_Temp=80
Power_Target=0

EDIT: I always run latest drivers - never had a problem w/ them other than when using stak/derivatives (TRM is an entirely separate codebase, so doesn't suffer from the same issues.) It should be noted that the latest Adrenaline drivers allow setting P0-5 now, which should remove the need for PPT. Sadly, based on my testing it would seem they forgot to extend this capability to the mem power states, which also act as voltage floors to the core.

NICE TUTORIAL.

i have vega 56 with 64 bios. Are you sure that V8 algo is better to return stock bios? i have referent vega 56 with samsung mem and now i u se 1095/1100 mhz mem

The main point of the 64 flash was to get 1150MHz+ mem speeds (which was consequential for CN/v1 while still maintaining efficiency.) For CNv2, core power consumption has increased significantly, so if you're not comfortable running ~210W+ per vega, you'll need to drop your mem speed to 1107 or below (which in effect drops your SOC clock) to get total power consumption down. Total throughput of 1107MHz @ 64 timings seems to be similar to 950MHz @ 56 timings based on other reported hashrates I've seen, which then means you're just burning extra power (though not much) for similar results.