Topic: [ mining os ] nvoc - page 231. (Read 418546 times)

anyone has an answer to this?

Then may be some things wrong with the image/OS
Some times starting from scratch is easier than trying to solve the problem.

P.S. is GPU Power Mizer Mode set in 1bash?

Is it possible to cpu mine Zcoin and gpu mine simultaneously on nvoc?

Thank you for your answer !

Yes, the problem persists even if i set higher fan values or 100%...

In the Thermal Settings in the nvidia x settings utility only gpu0 has fan control option enabled, the other gpu's are missing this feature.

I've seen issue with WATCHDOG while using keccak algo (for MAX COIN) on MPH; the GPU utilization for this coin is algo is always around 90 and WATCHDOG always restarts the mining eventually the whole RIG based on that usage!

I remember one of the user complained about keccak; asked about how to disable it (thinking its probably because of this utilization low issue).

I noticed that xmr-stack takes a while to load up all the gpu's with work - on 13 card systems this can take up to 3-4 minutes (it also depends on the thread/block count in xmr-stak config.txt - the settings from fullzero load under 2G of data, but you can tweak those numbers higher getting, resulting higher hash rates, but also increasing the initialization time).
Once stak loads all the cards, and assuming your OC settings are stable - it will behave itself for days. I meant to modify watchdog to recognize stak is running and increase the initialization time appropriately, but I still need to migrate to v0019. for now if you want to run watchdog, change the initial timeout to 360 seconds it should do the trick.
Once all the cards are loaded stak will spit out a bunch of submits to the pool in one shot.

Unfortunately we dont have KTccminer, we have KX for skunk-krnlx  and TP for tpruvot 2.2 and AS for alexis78
Can you please give it a shot?
Hash rate difference is around 20% with 1070
1000+ on windows with klaust ccminer and 800 with SP and KX ccminer on nvoc

I finally got around to upgrading to v19 from v17.  I'd had some trouble with v18 and went back to v17, but v19's being much better behaved.  I put my config in (configured to use my MiningPoolHub switcher and Maxximus007's fan-control code) and let her rip.

There is one issue I ran across: no Cryptonight miner.  I noticed it when my mining rig's fans all slowed down.  To get things running again in a hurry, I copied the mining software from my v17 setup.  It's in this tarball:

https://alfter.us/wp/wp-content/uploads/2017/09/KTccminer-cryptonight.tar.xz

Unpack to ~m1. It'll unpack to a Git repo into which you can pull updates (I last updated it just a few days ago) that has already been configured and built.  I might've built it for Pascal (GeForce 10-series) GPUs only; I don't recall for sure if I did, so if you're using older GPUs and it doesn't work for you, you might need to rebuild it.

There was also an upstream change in this miner that requires a change in 3main.  The "-a cryptonight" option is no longer accepted, so load 3main into the editor of your choice, search for "KTccminer-cryptonight" (it's near the beginning of the heredoc that gets written to mph_conf.json), and delete "-a cryptonight" from that line.

Beyond that, the only other changes I made were to set the hostname equal to the worker name (changes in /etc/hostname and /etc/hosts), change the timezone from Eastern to Pacific, and to revise the speed and power figures in the mph_conf.json heredoc with my current configuration (up from 3 GPUs to 4).  As I write this, I'm imaging my v19 setup so I can copy it over to the (physically smaller) stick with v17.

Does the error happens if you set speed to higher values like 60-65 too ?
I think I had the same problem on low values

I will look into a watchdog conflict with multiple gpus while using xmr-stak.

Hi guys, can someone give some hints or explain what is wrong with my rigs since only the gpu0 can have can receive/execute the fan speed as being set ? Below is the error i see all the time when any other than gpu0 fan gets set:

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

I am currently using rigs with 3 x 1080 Ti and 3 x 1070's and having the first release of v019 installed on SSD.
Tried manually to do:

nvidia-xconfig --enable-all-gpus
nvidia-xconfig --cool-bits=4
nvidia-settings -a [gpu:1]/GPUFanControlState=1
nvidia-settings -a [fan:1]/GPUTargetFanSpeed=50

but the error is the same.
Other than being unable to set the fan speeds, the rigs are chugging along, however, the speed of the fans for the cards other than gpu0 is the factory default as neither the minimum fan speed set in 1bash gets applied, with or without the automated fan control feature.

Edit: in the nvidia x server settings i can see the Enable fan control feature for the gpu0 but it is missing for the other gpu's.

Unfortunately we dont have KTccminer, we have KX for skunk-krnlx  and TP for tpruvot 2.2 and AS for alexis78
Can you please give it a shot?
Hash rate difference is around 20% with 1070
1000+ on windows with klaust ccminer and 800 with SP and KX ccminer on nvoc

I finally got around to upgrading to v19 from v17.  I'd had some trouble with v18 and went back to v17, but v19's being much better behaved.  I put my config in (configured to use my MiningPoolHub switcher and Maxximus007's fan-control code) and let her rip.

There is one issue I ran across: no Cryptonight miner.  I noticed it when my mining rig's fans all slowed down.  To get things running again in a hurry, I copied the mining software from my v17 setup.  It's in this tarball:

https://alfter.us/wp/wp-content/uploads/2017/09/KTccminer-cryptonight.tar.xz

Unpack to ~m1. It'll unpack to a Git repo into which you can pull updates (I last updated it just a few days ago) that has already been configured and built.  I might've built it for Pascal (GeForce 10-series) GPUs only; I don't recall for sure if I did, so if you're using older GPUs and it doesn't work for you, you might need to rebuild it.

There was also an upstream change in this miner that requires a change in 3main.  The "-a cryptonight" option is no longer accepted, so load 3main into the editor of your choice, search for "KTccminer-cryptonight" (it's near the beginning of the heredoc that gets written to mph_conf.json), and delete "-a cryptonight" from that line.

Beyond that, the only other changes I made were to set the hostname equal to the worker name (changes in /etc/hostname and /etc/hosts), change the timezone from Eastern to Pacific, and to revise the speed and power figures in the mph_conf.json heredoc with my current configuration (up from 3 GPUs to 4).  As I write this, I'm imaging my v19 setup so I can copy it over to the (physically smaller) stick with v17.

I believe I compiled this miner for v0019; it should be under the directory KTminer.  Might be a different version.