Yup, it mentioned before,
Thanks any way.

It will be fixed in next release.

Hi papampi,

This issue was with a mix of cards like the P106 and 1070 in a frame setting the OC speeds requires that the nvidia command to set the GPU or memory OC needs to be the [2] for some and [3] for others.  The loop looks like it was designed to try both [2] [3] if NORMAL=YES above, for each gpu but the gpu variable was incremented in the inner loop so you would get [2] on gpu[0] then [3] on gpu[1],  [2] on gpu [2] and so on. By moving the gpu increment out of the for loop it and into the outer while loop I believe it works as intended.  I added the two echo's in here to show the behavior. 

Original loop:


TI is 2 3, J is 2 and GPU is 0
nvidia-settings -a [gpu:0]/GPUGraphicsClockOffset[2]=-200
nvidia-settings -a [gpu:0]/GPUMemoryTransferRateOffset[2]=1500

  Attribute 'GPUGraphicsClockOffset' (19_1_4:0[gpu:0]) assigned value -200.


  Attribute 'GPUMemoryTransferRateOffset' (19_1_4:0[gpu:0]) assigned value 1500.

TI is 2 3, J is 3 and GPU is 1
nvidia-settings -a [gpu:1]/GPUGraphicsClockOffset[3]=-200
nvidia-settings -a [gpu:1]/GPUMemoryTransferRateOffset[3]=1300




TI is 2 3, J is 2 and GPU is 2
nvidia-settings -a [gpu:2]/GPUGraphicsClockOffset[2]=-200
nvidia-settings -a [gpu:2]/GPUMemoryTransferRateOffset[2]=1500

  Attribute 'GPUGraphicsClockOffset' (19_1_4:0[gpu:2]) assigned value -200.


  Attribute 'GPUMemoryTransferRateOffset' (19_1_4:0[gpu:2]) assigned value 1500.

TI is 2 3, J is 3 and GPU is 3
nvidia-settings -a [gpu:3]/GPUGraphicsClockOffset[3]=-200
nvidia-settings -a [gpu:3]/GPUMemoryTransferRateOffset[3]=1500

  Attribute 'GPUGraphicsClockOffset' (19_1_4:0[gpu:3]) assigned value -200.


  Attribute 'GPUMemoryTransferRateOffset' (19_1_4:0[gpu:3]) assigned value 1500.

TI is 2 3, J is 2 and GPU is 4
nvidia-settings -a [gpu:4]/GPUGraphicsClockOffset[2]=-200
nvidia-settings -a [gpu:4]/GPUMemoryTransferRateOffset[2]=1300

  Attribute 'GPUGraphicsClockOffset' (19_1_4:0[gpu:4]) assigned value -200.


  Attribute 'GPUMemoryTransferRateOffset' (19_1_4:0[gpu:4]) assigned value 1300.

TI is 2 3, J is 3 and GPU is 5
nvidia-settings -a [gpu:5]/GPUGraphicsClockOffset[3]=-200
nvidia-settings -a [gpu:5]/GPUMemoryTransferRateOffset[3]=1300


===============================================================
By moving the gpu increment to the while loop the execution looks like:


TI is 2 3, J is 2 and GPU is 0
nvidia-settings -a [gpu:0]/GPUGraphicsClockOffset[2]=-200
nvidia-settings -a [gpu:0]/GPUMemoryTransferRateOffset[2]=1500

  Attribute 'GPUGraphicsClockOffset' (19_1_4:0[gpu:0]) assigned value -200.


  Attribute 'GPUMemoryTransferRateOffset' (19_1_4:0[gpu:0]) assigned value 1500.

TI is 2 3, J is 3 and GPU is 0
nvidia-settings -a [gpu:0]/GPUGraphicsClockOffset[3]=-200
nvidia-settings -a [gpu:0]/GPUMemoryTransferRateOffset[3]=1500

  Attribute 'GPUGraphicsClockOffset' (19_1_4:0[gpu:0]) assigned value -200.


  Attribute 'GPUMemoryTransferRateOffset' (19_1_4:0[gpu:0]) assigned value 1500.

TI is 2 3, J is 2 and GPU is 1
nvidia-settings -a [gpu:1]/GPUGraphicsClockOffset[2]=-200
nvidia-settings -a [gpu:1]/GPUMemoryTransferRateOffset[2]=1300

  Attribute 'GPUGraphicsClockOffset' (19_1_4:0[gpu:1]) assigned value -200.


  Attribute 'GPUMemoryTransferRateOffset' (19_1_4:0[gpu:1]) assigned value 1300.

TI is 2 3, J is 3 and GPU is 1
nvidia-settings -a [gpu:1]/GPUGraphicsClockOffset[3]=-200
nvidia-settings -a [gpu:1]/GPUMemoryTransferRateOffset[3]=1300




TI is 2 3, J is 2 and GPU is 2
nvidia-settings -a [gpu:2]/GPUGraphicsClockOffset[2]=-200
nvidia-settings -a [gpu:2]/GPUMemoryTransferRateOffset[2]=1500

  Attribute 'GPUGraphicsClockOffset' (19_1_4:0[gpu:2]) assigned value -200.


  Attribute 'GPUMemoryTransferRateOffset' (19_1_4:0[gpu:2]) assigned value 1500.

TI is 2 3, J is 3 and GPU is 2
nvidia-settings -a [gpu:2]/GPUGraphicsClockOffset[3]=-200
nvidia-settings -a [gpu:2]/GPUMemoryTransferRateOffset[3]=1500

  Attribute 'GPUGraphicsClockOffset' (19_1_4:0[gpu:2]) assigned value -200.


  Attribute 'GPUMemoryTransferRateOffset' (19_1_4:0[gpu:2]) assigned value 1500.







if [ $P106_100_FULL_HEADLESS_MODE == "NO" ]
then

gpu=0
while [ $gpu -lt $GPUS ]
do
for j in $TI
do
CORE=${__CORE_OVERCLOCK[${gpu}]}
MEM=${MEMORY_OVERCLOCK[${gpu}]}
echo "TI is $TI, J is $j and GPU is $gpu"
echo "${NVD} -a [gpu:$gpu]/GPUGraphicsClockOffset[${j}]=$CORE"
echo "${NVD} -a [gpu:$gpu]/GPUMemoryTransferRateOffset[${j}]=$MEM"
${NVD} -a [gpu:$gpu]/GPUGraphicsClockOffset[${j}]=$CORE
${NVD} -a [gpu:$gpu]/GPUMemoryTransferRateOffset[${j}]=$MEM
done
gpu=$(($gpu+1))
done

Would this be why my 2 1050 Ti's show as ERR! in the power chart when it first loads and ewbf reports them as 0 Hash/watt?  They're running alongside 6 1060 6GB cards and they all seem to be working correctly (appropriate hash rates per card).  Just the error bothered me was all. Thanks!

I need help. I imaged 19-1.4 to an SSD but when I boot the 1bash file inmedia/ isn't there. And when I edit the one inhome/ with my changes they get overwritten when I launch bash. Otherwise, Ubuntu is booting and running just fine. Thanks!

Unfortunately, the 1bash inmedia does not work. What I do with a fresh 19-1.4 image is this sequence of steps:

1) Boot for first time and wait on first reboot. Then you should see that it comes up and starts mining on ZEC (although I don't know for who) on attached display.
2) Fix the issue with hostname being 19_1_4 by editingetc/hostname (e.g., sudo vimetc/hostname, change 19_1_4 to m1-desktop).
3) Deploy edited 1bash via WinSCP or edit existing locally to make changes for my coin, pools, etc. Reboot.

This is the minimal that I do with new rigs to get them up and running.

Hope this helps.

I'm not sure if i doing it right but the fastest way i know is just close the console and start a new one. Not the green Guake terminal. The black standard terminal. It kills the miner and restarts mining.

is CTRL-C in the remote screen that bad ?

I do ctrl-C in the miner screen all of the time to restart it. I said kill the miner in my previous post, I just didn't say how. Either way, the watchdog detects low utilization and restarts 3main eventually.

Thanks for great miner   
*********************

ZM 0.5.4 in nvOC

13x Asus Strix 1070
The rig is with AsRock H110 PRO BTC+ & Intel Pentim G4400 & 4GB RAM
Pulling 2080W from wall. With 2x 1200W ATX PSU
OS with 16GB class6 microSD card in USB adapter <--- some might say unrealiable but I have them plenty and ready provisioned for swap if fail. Done +2months no fail.

**********************

Fans at 50%

ZEC

   POWERLIMIT_WATTS=140
   
__CORE_OVERCLOCK=80
MEMORY_OVERCLOCK=1000

**********************

   GPU0 57C  Sol/s: 464.9  Sol/W: 3.36  Avg: 468.4  I/s: 250.1  Sh/s: 0.043  +
   GPU1 55C  Sol/s: 470.0  Sol/W: 3.38  Avg: 471.6  I/s: 251.5  Sh/s: 0.014
   GPU2 63C  Sol/s: 462.5  Sol/W: 3.33  Avg: 464.8  I/s: 246.8  Sh/s: 0.000
   GPU3 63C  Sol/s: 468.4  Sol/W: 3.32  Avg: 464.3  I/s: 246.7  Sh/s: 0.029
   GPU4 58C  Sol/s: 457.9  Sol/W: 3.35  Avg: 466.9  I/s: 249.4  Sh/s: 0.014
   GPU5 53C  Sol/s: 460.0  Sol/W: 3.30  Avg: 460.9  I/s: 247.7  Sh/s: 0.014
   GPU6 57C  Sol/s: 463.2  Sol/W: 3.31  Avg: 462.3  I/s: 248.2  Sh/s: 0.014
   GPU7 51C  Sol/s: 469.5  Sol/W: 3.35  Avg: 467.1  I/s: 249.1  Sh/s: 0.057
   GPU8 47C  Sol/s: 474.4  Sol/W: 3.43  Avg: 478.1  I/s: 254.1  Sh/s: 0.014
   GPU9 63C  Sol/s: 465.1  Sol/W: 3.30  Avg: 460.4  I/s: 245.4  Sh/s: 0.014
   GPU10 63C  Sol/s: 451.8  Sol/W: 3.26  Avg: 454.5  I/s: 244.7  Sh/s: 0.071  +
   GPU11 56C  Sol/s: 461.3  Sol/W: 3.34  Avg: 465.7  I/s: 249.0  Sh/s: 0.029  +
   GPU12 53C  Sol/s: 478.5  Sol/W: 3.37  Avg: 470.5  I/s: 251.5  Sh/s: 0.014
   ========= Sol/s: 6047.6 Sol/W: 3.34  Avg: 6055.5 I/s: 3234.3 Sh/s: 0.329

If I drop the powerlimit to 130W I get aroud 3.7 Sol/W ~5800sols with same OC settings, but I like 6000 sol more round number.


**********************

ZM 0.5.4 in nvOC

4x Asus Strix A 1070 TI
   
    POWERLIMIT_WATTS=130
   
__CORE_OVERCLOCK=120
MEMORY_OVERCLOCK=1200


   GPU0 62C  Sol/s: 501.2  Sol/W: 3.92  Avg: 508.6  I/s: 270.8  Sh/s: 0.030
   GPU1 58C  Sol/s: 503.2  Sol/W: 3.95  Avg: 511.4  I/s: 272.8  Sh/s: 0.090  +
   GPU2 56C  Sol/s: 508.3  Sol/W: 3.93  Avg: 509.5  I/s: 272.3  Sh/s: 0.050  +
   GPU3 53C  Sol/s: 505.1  Sol/W: 3.93  Avg: 509.5  I/s: 271.6  Sh/s: 0.040
   ========= Sol/s: 2017.8 Sol/W: 3.93  Avg: 2039.0 I/s: 1087.4 Sh/s: 0.210


The Asus "binned" TI GPU stand more OC and hashes ok with 130W too. Will make 13x TI rig next. Same powerdraw more sols per W. Should be ~6600 sols with 2kw.