[OS] nvOC easy-to-use Linux Nvidia Mining

[CWJ1007]

GPU 10, Target temp: 75, Current: 65, Diff: 10, Fan: 43, Power: 108.96

Fri Oct 13 05:33:08 MST 2017 - Adjusting Fan for gpu:10. Old: 43 New: 75 Temp: 65



ERROR: Error assigning value 75 to attribute 'GPUTargetFanSpeed' (m1-desktop:0[fan:10]) as specified in
       assignment '[fan:10]/GPUTargetFanSpeed=75' (Unknown Error).


GPU 11, Target temp: 75, Current: 66, Diff: 9, Fan: 43, Power: 117.42

Fri Oct 13 05:33:09 MST 2017 - Adjusting Fan for gpu:11. Old: 43 New: 75 Temp: 66



ERROR: Error assigning value 75 to attribute 'GPUTargetFanSpeed' (m1-desktop:0[fan:11]) as specified in
       assignment '[fan:11]/GPUTargetFanSpeed=75' (Unknown Error).


GPU 12, Target temp: 75, Current: 66, Diff: 9, Fan: 44, Power: 106.87

Fri Oct 13 05:33:11 MST 2017 - Adjusting Fan for gpu:12. Old: 44 New: 75 Temp: 66


I have 3 rigs... use v0019-1.3.
All rigs had above problems....plz help...

Hardware (3 rigs are same)
Intel G4400
Asus B250 Mining Expert
UMAX 4GB DDR4-2400 x 2
Asus dual-GTX1070-8G x 13
Leadex 850W x 3

Thank you.

[1714292471]

1714292471

[1714292471]

1714292471

[1714292471]

1714292471

[Temporel]

I built djm34's ccminer with Cuda9 and found that it was faster than tp ccminer on ZCOIN. If you can confirm that, use djm34's as default zcoin miner.

dont know about nvOC or Linux, but I used that combo on Windows 10 and it is 10-13 % faster than the previous ccminer I was using.

[kk003]

I found out that when I change in 1bash the value of var:

Code:

TELEGRAM_TIMEOUT_IN_MINUTES

the interval time a telegram is sent does not change.

Killed miner+temp (don't use any more functions of Nvoc) and then:

Code:

bash 3main

does not make any difference.

I had to restart the system for the new value to be used.

I am working on a telegram script that should allow the user choose at what times of day to send a telegram (not using cron) and I need to change this value for testing that functionality.
Is there any way to accomplish this without restart the system?

[hurvajs77]

Hi Fullzero,

I've a small improvment of MPH script. I live in EU, so for me are better pools in Europe. MPH salfter script don't check location by default, by API gets list of possible host. I measure ping with default host names from MPH API and there were little big latency against to Europe host. So, I modify switching script.

There is guideline:

1) modify 1bash script and add (in MPH settings - for example before PROFIT_CHECK_TIMEOUT):

2) modify 3main script and adjust structure for generation configuration file for MPH (mph_conf.json, find this: /home/m1/mph_conf.json):

3) modify mph_switch script:
3a) after line with min_profit=cfg["min_profit"] add:
That's all. Now MPH check region settings.

All these changes seem to be focusing on my miner right now.
Thanks to you.
Very good job as this regionnal choice. I had seen that the site proposed these three geographical areas, notably by copying the URL in the script, but I would not have been able to make myself modifications!
If my miner is more efficient and plants less thanks to your modifications, I will send you sure coins (I have a small miner then it will probably not coins of great value ... but it seems that it is The gesture which counts)

I will still continue on MPH while waiting for a full version nvOC 20. I want to see what it gives me over a month.

I read on another btalk post that compared Zpool, Nicehash and Miningpoolhub that MPH was better paying than Nicehash, and Zpool pays more than MPH who pays more than nicehash. I must point out that the guy was mining dash with three identical miners: baikals (https://bitcointalk.org/index.php?topic=2067256.0)

No, problem. I can help - I want to earn some money as all there ;-)

About swithing pools - I've good experiences with NiceHash. MPH is wrost - when I tried mine via MPH, I got approx. 1/2 amount BTC to NiceHash. I tried more times.

[hurvajs77]

Unfortunately I must write, that nvOS is really unstable with 11 GPUs in my case. I'm sad... :-( In this case, each miner crash a few minutes after mining for memory segmentation fault, in 70% of startups watchdog kill mining process for maybe 20x times. In general there are many epochs without mining - when nvOS set up GPUs, or restating whole mining process. After GPUs re-allocation there are great improvement in stability. So, someone who has in one rig more that 8 cards and succesfully OCed?

I'm solving miners crashing, OC all day. My conclusion is nvOS v0019 is unstable and I can't trust it - with 11x GPUs.

It's little strange that if rig has only 8 cards, so it's stable. So, I've two rigs now, with 8 gpus, and 3 gpus. Both use nvOS and works :-) I don't understand why both rigs can have different OC settings.

On rig with 8 gpus is this:

• power limit: 208W
• core: +85
• mem: +480
• Mobo: ASRock BTC Pro+
• PSU 1200W, 1700W
• 7x Gigabite AORUS 1080Ti Extreme Water
• 1x Zotac Extreme 1080Ti AMP
• i5-7600K
• used these risers, powered via SATA https://www.aliexpress.com/item/10pcs-TISHRIC-2018-VER008S-Molex-4PIN-15PIN-SATA-6PIN-3-in-1-PCIE-PCI-Express-Riser/32828808283.html?spm=a2g0s.9042311.0.0.szfVUP

On rig with 3 gpus is this:

• power limit: 225W
• core: +120
• mem: +900
• Mobo: ASUS Maximus Ranger IV
• PSU 1700W
• 3x Gigabite AORUS 1080Ti Extreme Water
• i7-4790K

both rigs use CPU mining too

Hash rates are for ZCash:

• with 8 gpus - about 5550 Sol/s
• with 3 gpus - about 2150 Sol/s

My guess is the problem is temperature related. 

in 1bash you can increase the target temp:

Code:

TARGET_TEMP=80

and increase the minimal fan speed:

Code:

MINIMAL_FAN_SPEED=75

  or higher depending on how hot your GPUs are tending.

IMO 1080tis should always have active cooling; also they do best when the fans are blowing into the GPUs from the front (they are rear + top ejecting (not front like you would expect))

thanks for answer Fullzero.

Ok, I'll try it. It's true that my setting are

Code:

TARGET_TEMP=62
MANUAL_FAN="NO"
MINIMAL_FAN_SPEED=30

Yes, I use extra fans blowing to radiators from the front (I've water cooled GPUs)

I post results later.

Do you think is normal lower OC with more GPUs?

IMO you can OC a single GPU system significantly higher than a multi GPU system; for example I had 1080ti FTW3s that we’re stable with +2000 mc 175 pl, producing 39.5 mh/s Ethash.  Take another and put them on the same rig and it can only OC ~+1600 mc; this trend continues as you add more GPUs.  With core intensive algos like Equihash; you have significantly less improvement when reducing the number of GPU’s.

Thanks for explain. I expected that. So, smaller rigs are better for hash rate, but more expensive for mobos etc.

[joshuajones02]

Where do I insert the password for suprnova login info in the miner blocks? I've tried everything I could possibly think of including using the password x for my miner login

anyone? trying to mine ZEN on suprnova

[Temporel]

Where do I insert the password for suprnova login info in the miner blocks? I've tried everything I could possibly think of including using the password x for my miner login

anyone? trying to mine ZEN on suprnova

yes and it works just fine.

[papampi]

Where do I insert the password for suprnova login info in the miner blocks? I've tried everything I could possibly think of including using the password x for my miner login

anyone? trying to mine ZEN on suprnova

You dont need suprnova password to mine

[Temporel]

Where do I insert the password for suprnova login info in the miner blocks? I've tried everything I could possibly think of including using the password x for my miner login

anyone? trying to mine ZEN on suprnova

You dont need suprnova password to mine

isnt the option available in 3main anyway ?

[joshuajones02]

Where do I insert the password for suprnova login info in the miner blocks? I've tried everything I could possibly think of including using the password x for my miner login

anyone? trying to mine ZEN on suprnova

You dont need suprnova password to mine

isnt the option available in 3main anyway ?

found it in 3main, pass is "z" not x... thanks

[hurvajs77]

Hi papampi,
I'm using your telegram messages. Excellent!

I've a small improvement for miner uptime (I got always empty), so I check command. There is used unknown option -p and failed

The universal solution is:

Code:

ps -eo comm,etime | grep -i miner | grep -vi cpu | awk '{print $2}'

Other infos are empty too, I check later

Thanks mate
I'm aware of some problems thats why we call beta version:)
Some info and hash rate on web has not completed yet , will try to add them all for next version.

you're welcome. Maybe better solution is:

Code:

ps -eo comm,etime | grep -vi cpu | grep -i miner | awk '{print $2}'

So, first time gets all processes without CPU miner, than we got correct info about GPUs miner... Sorry ;-)

But, I don't know how much from us use CPU mining...

[hurvajs77]

I am mining Mona with ASccminer and intensity 21 with no problem and great hash rate on suprnova
are you sure you made your worker in suprnova settings?
suprnova dont creat worker automatically , you should make them manually

Excellent! I switched now without any problems and hash rate encreased from 680MHz to 770 - same OC...

Thanks for notification papampi :-)

[hurvajs77]

Where do I insert the password for suprnova login info in the miner blocks? I've tried everything I could possibly think of including using the password x for my miner login

anyone? trying to mine ZEN on suprnova

You dont need suprnova password to mine

isnt the option available in 3main anyway ?

found it in 3main, pass is "z" not x... thanks

password isn't checked, so you can use z or modify 3main and fill correct password. Result is same :-)

[joshuajones02]

Where do I insert the password for suprnova login info in the miner blocks? I've tried everything I could possibly think of including using the password x for my miner login

anyone? trying to mine ZEN on suprnova

You dont need suprnova password to mine

isnt the option available in 3main anyway ?

found it in 3main, pass is "z" not x... thanks

password isn't checked, so you can use z or modify 3main and fill correct password. Result is same :-)

lol thanks, thats strange though.. I changed my pass in suprnova from x to z and rebooted and it worked fine, no issues. Every time I booted previously, it would show fan speed and then going in a loop to []Screen is terminating.. Oh well, working good now

[Temporel]

Where do I insert the password for suprnova login info in the miner blocks? I've tried everything I could possibly think of including using the password x for my miner login

anyone? trying to mine ZEN on suprnova

You dont need suprnova password to mine

isnt the option available in 3main anyway ?

found it in 3main, pass is "z" not x... thanks

password isn't checked, so you can use z or modify 3main and fill correct password. Result is same :-)

well I had to change my password on suprnova recently because I made a mistake when I created a worker, so yeah, it does matter

[jlbaseball11]

I built djm34's ccminer with Cuda9 and found that it was faster than tp ccminer on ZCOIN. If you can confirm that, use djm34's as default zcoin miner.

Would you be willing to share how you compiled?  I got a bunch of "BIGNUM" errors when I tried to use -make.
How do we upgrade to CUDA9?  The instructions on their website didn't work for me:
Installation Instructions:
`sudo dpkg -i cuda-repo-ubuntu1604_9.0.176-1_amd64.deb`
`sudo apt-key adv --fetch-keys http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64/7fa2af80.pub`
`sudo apt-get update`
`sudo apt-get install cuda`

Thanks for your help.

[Temporel]

I built djm34's ccminer with Cuda9 and found that it was faster than tp ccminer on ZCOIN. If you can confirm that, use djm34's as default zcoin miner.

Would you be willing to share how you compiled?  I got a bunch of "BIGNUM" errors when I tried to use -make.
How do we upgrade to CUDA9?  The instructions on their website didn't work for me:
Installation Instructions:
`sudo dpkg -i cuda-repo-ubuntu1604_9.0.176-1_amd64.deb`
`sudo apt-key adv --fetch-keys http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64/7fa2af80.pub`
`sudo apt-get update`
`sudo apt-get install cuda`

Thanks for your help.

download openssl v1.0.2f from the offical website (look archive)
then copy the file bn.h (from crypto directory) to /usr/local/include/openssl
then try your last command (make or build) again.

[123sss]

0d:00.0 VGA compatible controller: NVIDIA Corporation Device 1c02 (rev a1)
0e:00.0 VGA compatible controller: NVIDIA Corporation Device 1c02 (rev a1)
0f:00.0 VGA compatible controller: NVIDIA Corporation Device 1c02 (rev a1)


Fri Oct 13 14:02:57 2017       
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 384.90                 Driver Version: 384.90                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX 106...  Off  | 00000000:01:00.0  On |                  N/A |
| 25%   36C    P0    26W / 120W |    117MiB /  3009MiB |      7%      Default |
+-------------------------------+----------------------+----------------------+
|   1  GeForce GTX 106...  Off  | 00000000:02:00.0 Off |                  N/A |
| 25%   31C    P8     6W / 120W |      9MiB /  3013MiB |      2%      Default |
+-------------------------------+----------------------+----------------------+
|   2  GeForce GTX 106...  Off  | 00000000:03:00.0 Off |                  N/A |
| 25%   35C    P8     6W / 120W |      9MiB /  3013MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   3  GeForce GTX 106...  Off  | 00000000:04:00.0 Off |                  N/A |
| 25%   34C    P8     7W / 120W |      9MiB /  3013MiB |      4%      Default |
+-------------------------------+----------------------+----------------------+
|   4  GeForce GTX 106...  Off  | 00000000:05:00.0 Off |                  N/A |
| 25%   36C    P8     7W / 120W |      9MiB /  3013MiB |      4%      Default |
+-------------------------------+----------------------+----------------------+
|   5  GeForce GTX 106...  Off  | 00000000:06:00.0 Off |                  N/A |
| 25%   29C    P8     7W / 120W |      9MiB /  3013MiB |      4%      Default |
+-------------------------------+----------------------+----------------------+
|   6  GeForce GTX 106...  Off  | 00000000:09:00.0 Off |                  N/A |
| 25%   32C    P8     7W / 120W |      9MiB /  3013MiB |      3%      Default |
+-------------------------------+----------------------+----------------------+
|   7  GeForce GTX 106...  Off  | 00000000:0A:00.0 Off |                  N/A |
| 25%   32C    P8     7W / 120W |      9MiB /  3013MiB |      3%      Default |
+-------------------------------+----------------------+----------------------+
|   8  GeForce GTX 106...  Off  | 00000000:0B:00.0 Off |                  N/A |
| 25%   26C    P8     6W / 120W |      9MiB /  3013MiB |      3%      Default |
+-------------------------------+----------------------+----------------------+
|   9  GeForce GTX 106...  Off  | 00000000:0C:00.0 Off |                  N/A |
| 25%   31C    P8     7W / 120W |      9MiB /  3013MiB |      5%      Default |
+-------------------------------+----------------------+----------------------+
|  10  GeForce GTX 106...  Off  | 00000000:0D:00.0 Off |                  N/A |
| 25%   31C    P8     7W / 120W |      9MiB /  3013MiB |      2%      Default |
+-------------------------------+----------------------+----------------------+
|  11  GeForce GTX 106...  Off  | 00000000:0E:00.0 Off |                  N/A |
| 25%   33C    P8     6W / 120W |      9MiB /  3013MiB |      2%      Default |
+-------------------------------+----------------------+----------------------+
|  12  GeForce GTX 106...  Off  | 00000000:0F:00.0 Off |                  N/A |
| 25%   40C    P8     7W / 120W |      9MiB /  3013MiB |      3%      Default |
+-------------------------------+----------------------+----------------------+
                                                                               
+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|=============================================================================|
|    0      1111      G   /usr/lib/xorg/Xorg                            91MiB |
|    0      2202      G   compiz                                        28MiB |
|    1      1111      G   /usr/lib/xorg/Xorg                             7MiB |
|    2      1111      G   /usr/lib/xorg/Xorg                             7MiB |
|    3      1111      G   /usr/lib/xorg/Xorg                             7MiB |
|    4      1111      G   /usr/lib/xorg/Xorg                             7MiB |
|    5      1111      G   /usr/lib/xorg/Xorg                             7MiB |
|    6      1111      G   /usr/lib/xorg/Xorg                             7MiB |
|    7      1111      G   /usr/lib/xorg/Xorg                             7MiB |
|    8      1111      G   /usr/lib/xorg/Xorg                             7MiB |
|    9      1111      G   /usr/lib/xorg/Xorg                             7MiB |
|   10      1111      G   /usr/lib/xorg/Xorg                             7MiB |
|   11      1111      G   /usr/lib/xorg/Xorg                             7MiB |
|   12      1111      G   /usr/lib/xorg/Xorg                             7MiB |
+-----------------------------------------------------------------------------+

Power limit for GPU 00000000:01:00.0 was set to 100.00 W from 120.00 W.

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

Power limit for GPU 00000000:02:00.0 was set to 100.00 W from 120.00 W.

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

Power limit for GPU 00000000:03:00.0 was set to 100.00 W from 120.00 W.

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

Power limit for GPU 00000000:04:00.0 was set to 100.00 W from 120.00 W.

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

Power limit for GPU 00000000:05:00.0 was set to 100.00 W from 120.00 W.

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

Power limit for GPU 00000000:06:00.0 was set to 100.00 W from 120.00 W.

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

Power limit for GPU 00000000:09:00.0 was set to 100.00 W from 120.00 W.

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

Power limit for GPU 00000000:0A:00.0 was set to 100.00 W from 120.00 W.

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

Power limit for GPU 00000000:0B:00.0 was set to 100.00 W from 120.00 W.

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

Power limit for GPU 00000000:0C:00.0 was set to 100.00 W from 120.00 W.

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

Power limit for GPU 00000000:0D:00.0 was set to 100.00 W from 120.00 W.

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

Power limit for GPU 00000000:0E:00.0 was set to 100.00 W from 120.00 W.

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

Power limit for GPU 00000000:0F:00.0 was set to 100.00 W from 120.00 W.

Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.

All done.

LAUNCHING:  IAmNotAJeep_and_Maxximus007_WATCHDOG

process in guake terminal Tab (f12)


LAUNCHING:  Maxximus007_AUTO_TEMPERATURE_CONTROL

process in guake terminal Tab (f12)


  Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:0]) assigned value 100.


  Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:0]) assigned value 300.


  Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:1]) assigned value 100.


  Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:1]) assigned value 300.


  Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:2]) assigned value 100.


  Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:2]) assigned value 300.


  Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:3]) assigned value 100.


  Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:3]) assigned value 300.


  Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:4]) assigned value 100.


  Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:4]) assigned value 300.


  Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:5]) assigned value 100.


  Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:5]) assigned value 300.


  Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:6]) assigned value 100.


  Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:6]) assigned value 300.


  Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:7]) assigned value 100.


  Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:7]) assigned value 300.


  Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:8]) assigned value 100.


  Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:8]) assigned value 300.


  Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:9]) assigned value 100.


  Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:9]) assigned value 300.


  Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:10]) assigned value 100.


  Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:10]) assigned value 300.


  Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:11]) assigned value 100.


  Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:11]) assigned value 300.


  Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:12]) assigned value 100.


  Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:12]) assigned value 300.

[screen is terminating]


What a problem??? ver  v0019-1.3                 

[123sss]

miner not started

[123sss]

Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:12]) assigned value 300.

There is no screen to be resumed matching miner.