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

[papampi]

Point_2

No matter what; cc and mc are taken from INDIVIDUAL_CLOCKS  _0 values

Code:

INDIVIDUAL_CLOCKS="NO"      	# YES NO

# Set individual clocks here if INDIVIDUAL_CLOCKS="YES"
__CORE_OVERCLOCK_0=150
MEMORY_OVERCLOCK_0=100

Happened while mining SIGT with these options

Code:

COIN="SIGT"

Maxximus007_AUTO_TEMPERATURE_CONTROL="YES"

IAmNotAJeep_and_Maxximus007_WATCHDOG="YES"

# SET OC and POWERLIMIT by ALGO (see end of 1bash for ALGO OC settings)

damNmad_ALGO_SPECIFIC_OC="YES"

POWERLIMIT="YES"              	# YES NO
	
	POWERLIMIT_WATTS=76
	
__CORE_OVERCLOCK=150
MEMORY_OVERCLOCK=100

Code:

INDIVIDUAL_CLOCKS="NO"      	# YES NO

# Set individual clocks here if INDIVIDUAL_CLOCKS="YES"
__CORE_OVERCLOCK_0=150
MEMORY_OVERCLOCK_0=-1000

Code:

if [ $COIN == "SIGT" -o $COIN == "ZPOOL_SKUNK" ]
then
	POWERLIMIT_WATTS=80
__CORE_OVERCLOCK=150
MEMORY_OVERCLOCK=600
fi

Target Temperature also behaving same; getting value from TARGET_TEMP_0 and applying it on all GPU's (in AUTO_TEMP)

Code:

INDIVIDUAL_TARGET_TEMPS="NO"   	# YES NO

# Set individual target temps here if INDIVIDUAL_TARGET_TEMPS="YES"
TARGET_TEMP_0=60

Please let me know if I've missed or mistook something!!

I believe I have the same issue on Overclock and Power Limits
Power limit problem has been there since v0018, but overclock is new from v0019.1

[1713863156]

1713863156

[1713863156]

1713863156

[1713863156]

1713863156

[1713863156]

1713863156

[1713863156]

1713863156

[1713863156]

1713863156

[fullzero]

I could compile KTccminer on nv0019, but not on my other ubuntu
gave me some errors
just download the source
and run the commands with no args

Code:

./autogen.sh 
./configure.sh
./build.sh

it should be ok

remember to:

cd to the KTccminer directory first:

cd /home/m1/KTccminer

Klaust aswered under papami's Github ticket.
He said and/or write :

"I have a 1070 too, and under Windows it works.
Did you use the build.sh script to compile it?"

In my case, i just downloaded tar salfter's KTccminer and uncompressed in /home/m1.
But i saw the mph_switching_profit stop mining when Monero bécame most profitable to mine. The rig don't mine nothing before to toggle to anoter coin algorithm.

unfortunately if I have the skills to compile or mining, I do not have those to know how to code. I try to read your scripts, which I sometimes understand, but not always everything and not all the time ...

Thank you very much to you fullzero for this work and the great progress of nvOC.

I'm sure everything can still make great strides. Why not with a web interface for example?

Eventually I will implement all the requests.

[fullzero]

Set it to LOCAL in 1bash

found it, thank you.

So I made the change and reboot the system and for some reason, the GPUx id of my cards changed. I have 2 1080Ti mixed with the GTX-1070s so I had to manually changed the powerlimit for each cards and now one of the 1070 is set to 225 and a 1080Ti to 135watts.

Weird...

press F12 to open guake terminal, then press the button at the lower right corner to open new tab, then type

Code:

gedit .bashrc

add the following at the bottom:

Code:

export CUDA_DEVICE_ORDER=PCI_BUS_ID

save and restart.
The solution was posted by fullzero with credit given to car1999 about 10-11 pages back

Thank you !
I use the remote output now so I did it using nano in the terminal instead­.

EDIT: the ids are still wrong but I think my settings are fine, its just mixed up for some reason in the output.

try this instead, it will load it as permanent global variable for login and non-login, interactive and non-interactive shells:

Code:

sudo echo 'export CUDA_DEVICE_ORDER=PCI_BUS_ID' | sudo tee -a /etc/profile.d/cuda-device-order.sh

you need to logout and login again and restart the mining process for it to take effect (or just reboot).

Please post results.

it works, thank you very much !

Do you think this fix will be include in v0020 ?

added this fix to the -1 update

[fullzero]

Would there be any issues with running v0019 on the new Asus B250 Mining Expert motherboard?  (the one with 19 PCIe slots)

Will it support running, say 19x 1050Ti's for example?

Looking at the bash script, it looks like support only goes up to 14.  If I modify it to allow up to 19, will it work?

Yes it does, you need to edit 1bash, 3main, watchdog and auto temp scripts too, to accommodate 19 GPU.

Fullzero said that he is already working on it, we may see that in the upcoming update.

I tested this mobo; you need to change a bios setting to enable nvOC to boot:

select advanced mode in Bios then Boot tab; change Launch CSM to Enabled.  Save changes and reboot.

-1 update supports 19x GPUs but mobo will not post with 19x GPUs connected. 

It works well with 13x GPUs.  If anyone gets it to post with 19x let me know the CPU / ram / prior process you used.

[fullzero]

Papami, Leenoox and IAmNotAJeep :

What do you think about this other site that give some other comparisons ?
https://www.coinwarz.com/cryptocurrency

They don't give JSON but they give others résults and coins.

Would it be possible to request and extract data of the answer page that they give us ?

wget the url; then grep

[fullzero]

Just got my B250 19 GPU motherboard in hand. Will try to setup soon. Out of curiosity, why do you say it's unlikely we would get over 13 when there was a guy who already did all 19 successfully?

See:  https://bitcointalk.org/index.php?topic=1854250.msg22150526#msg22150526

Might be that I used a Skylake CPU; but I doubt it.

[fullzero]

v0019-1 update:

Lots of changes; please keep in mind this update is beta: it will most likely have some bugs, if you don't want to deal with any bugs you can wait until any issues have already been found and fixed by the community.

Before updating; please copy your 1bash (and any other files you have changed/customized) to a different directory (such as the desktop).

To update:

open 1bash with gedit and ensure:

Code:

AUTO_UPDATE="BETA" 

close any terminal currently open; then:

open a guake terminal ( press f12 ) and type the following, then press enter:

Code:

bash 4update

This will launch 4update which will update your 2unix file.  

When 4update is done; gnome-terminal will auto launch.  

The new 2unix will detect your v0019 is not -1 and launch the update.

The update will install all system updates including the newest Nvidia driver.  Then update nvOC files.

When it is done your rig will reboot automatically.  

Your 1bash will be copied to a file named: your_old_1bash as a new version is required for some of the updates.  

You can copy and paste your pools / addresses into the new 1bash.  ( I will eventually automate this)

v0019-1 can support up to 19x GPUs; however it is unlikely you will be able to get more than 13x GPUs to work correctly with the new Asus 19x mobo.

Edit Additional info:

Lots of new COIN selections from damNmad and some from papampi.  I will add a full change log to the OP later today.

Thank you so much fullZero for the major update

I've planned to add this in my next update, but you have done it already

Code:

HCD=/home/m1/eth/$CLAYMORE_VERSION/ethdcrminer64

Much needed and much better update in my opinion.

In future (hopefully) users need not to edit 1bash for every update; thanks again amigo

EDIT :

I will report all the bugs/issues noticed here

Point_1

I've noticed this file is missing from papampi version:

Code:

REBOOT_REQUIRED=$(/home/m1/reboot-required)

TELEGRAM throwing this warning or sort of:

Code:

m1@m1-desktop:~$ bash /home/m1/BaliMiner_TELEGRAM_ALERTS
/home/m1/telegram: line 40: /home/m1/reboot-required: No such file or directory

I guess its a simple fix from papampi; providing the code and save that code into a reboot-required file

&&

For people who don't want to skip that warning by just commenting out this line in /home/m1/telegram file

Code:

#REBOOT_REQUIRED=$(/home/m1/reboot-required)

If your telegram bot not working while selecting 'papampi'; change this:

Code:

APIKEY=$TELEGRAM_ALERT_APIKEY

to

Code:

APIKEY=$TELEGRAM_APIKEY

Point_2

No matter what; cc and mc are taken from INDIVIDUAL_CLOCKS  _0 values

Code:

INDIVIDUAL_CLOCKS="NO"      	# YES NO

# Set individual clocks here if INDIVIDUAL_CLOCKS="YES"
__CORE_OVERCLOCK_0=150
MEMORY_OVERCLOCK_0=100

Happened while mining SIGT with these options

Code:

COIN="SIGT"

Maxximus007_AUTO_TEMPERATURE_CONTROL="YES"

IAmNotAJeep_and_Maxximus007_WATCHDOG="YES"

# SET OC and POWERLIMIT by ALGO (see end of 1bash for ALGO OC settings)

damNmad_ALGO_SPECIFIC_OC="YES"

POWERLIMIT="YES"              	# YES NO
	
	POWERLIMIT_WATTS=76
	
__CORE_OVERCLOCK=150
MEMORY_OVERCLOCK=100

Code:

INDIVIDUAL_CLOCKS="NO"      	# YES NO

# Set individual clocks here if INDIVIDUAL_CLOCKS="YES"
__CORE_OVERCLOCK_0=150
MEMORY_OVERCLOCK_0=-1000

Code:

if [ $COIN == "SIGT" -o $COIN == "ZPOOL_SKUNK" ]
then
	POWERLIMIT_WATTS=80
__CORE_OVERCLOCK=150
MEMORY_OVERCLOCK=600
fi

Target Temperature also behaving same; getting value from TARGET_TEMP_0 and applying it on all GPU's (in AUTO_TEMP)

Code:

INDIVIDUAL_TARGET_TEMPS="NO"   	# YES NO

# Set individual target temps here if INDIVIDUAL_TARGET_TEMPS="YES"
TARGET_TEMP_0=60

Please let me know if I've missed or mistook something!!

For checking if reboot is required in telegram add a reboot-required file

Put these inside:

Code:

#!/bin/bash
if [ -f /var/run/reboot-required ]; then
  echo 'yes'
else 
echo 'No'
fi

make executable by running this command:

Code:

chmod +x reboot-required

Edit:
A better way is to open telegram file
in papampi section find this line :

Code:

REBOOT_REQUIRED=$(/home/m1/reboot-required)

and change it to :

Code:

REBOOT_REQUIRED=$([ -f /var/run/reboot-required ] && echo "Yes!!!" || echo "No")

It seems its left out in the message line as well, add it to MSG :

Code:

MSG=" Worker: $WORKERNAME
Reboot Required: $REBOOT_REQUIRED
... REST_of_The_Message
"

I think I fixed these in -1.1; let me know.

[fullzero]

ewbf 3_3 does not have the 2% fee

What makes 3_4 more effective? Anyone using 3_3 with the same performance as 3_4?

3_4 is about 2% better than 3_3 but has a 2% fee; so 3_4 is really only better if you use its api.  With -1 update you can also try the zm client.

[fullzero]

Fullzero and damNmad
I was setting up my 19.1 1bash and 3main, to get it ready for upgrade and thought there are many pools which requires registration and use our username
I thought it would be nice in next version we set variables for all the popular pools with pool address , port and usernames
So users just use the variables and lower the problems setting up pools and ports and ...

Code:

SUPRNOVA_USERNAME="papampi"
ZCL_SUPRNOVA_POOL="zcl.suprnova.cc"
ZCL_SUPRNOVA_PORT="4042"
KMD_SUPRNOVA_POOL="kmd.suprnova.cc"
KMD_SUPRNOVA_PORT="6250"
.
.
.

ZCL_WORKER=$WORKERNAME
ZCL_ADDRESS=$SUPRNOVA_USERNAME
ZCL_POOL=$ZCL_SUPRNOVA_POOL
ZCL_PORT=$ZCL_SUPRNOVA_PORT

KMD_WORKER=$WORKERNAME
KMD_ADDRESS=$SUPRNOVA_USERNAME
KMD_POOL=$KMD_SUPRNOVA_POOL
KMD_PORT=$KMD_SUPRNOVA_PORT
.
.
.

I already have a list of almost all popular pools and ports,
let me know and I will make it ready for next version and send it to you

This is a good idea.  Please send it to me.  Also remember pools have multiple servers for different geographical locations.

[fullzero]

ewbf 3_3 does not have the 2% fee

What makes 3_4 more effective? Anyone using 3_3 with the same performance as 3_4?

I use 3_3, it's 2% slower than 3_4.

So thats exactly the dev fee, have you tried dstm zminer ?
its available in v19.1
it also has 2% dev fee

I haven't

Does the version of claymore built in have the claymore zec miner?

I believe the Claymore Equihash client is AMD only.

[fullzero]

Same Problem with 2.04 version of Salfter :

Code:

./ccminer -o stratum+tcp://europe.cryptonight-hub.miningpoolhub.com:20580 -u Cryptatometrader44.ATOMICMINER44 -p xcd
    *** ccminer-cryptonight 2.04 (64 bit) for nVidia GPUs by tsiv and KlausT 
    *** Built with GCC 5.4 using the Nvidia CUDA Toolkit 8.0

 tsiv's BTC donation address:   1JHDKp59t1RhHFXsTw2UQpR3F9BBz3R3cs
 KlausT's BTC donation address: 1QHH2dibyYL5iyMDk3UN4PVvFVtrWD8QKp
 for more donation addresses please read the README.txt
-----------------------------------------------------------------
[2017-09-23 14:33:54] 2 miner threads started
[2017-09-23 14:33:54] Starting Stratum on stratum+tcp://europe.cryptonight-hub.miningpoolhub.com:20580
[2017-09-23 14:33:54] GPU #1: GeForce GTX 1070 (15 SMX), using 60 blocks of 32 threads
[2017-09-23 14:33:54] GPU #0: GeForce GTX 1070 (15 SMX), using 60 blocks of 32 threads
[2017-09-23 14:33:54] Pool set diff to 500054
[2017-09-23 14:33:54] Stratum detected new block
[2017-09-23 14:33:57] GPU #1: GeForce GTX 1070, 648.71 H/s (648.58 H/s avg)
[2017-09-23 14:33:57] GPU #0: GeForce GTX 1070, 623.38 H/s (623.22 H/s avg)
[2017-09-23 14:34:11] Stratum detected new block
[2017-09-23 14:34:13] GPU #1: GeForce GTX 1070, 721.66 H/s (710.22 H/s avg)
[2017-09-23 14:34:13] GPU #0: GeForce GTX 1070, 717.64 H/s (702.43 H/s avg)
[2017-09-23 14:35:06] Pool set diff to 350010
[2017-09-23 14:35:06] Stratum detected new block
[2017-09-23 14:35:06] GPU #1: GeForce GTX 1070, 721.36 H/s (718.44 H/s avg)
[2017-09-23 14:35:06] GPU #0: GeForce GTX 1070, 718.37 H/s (714.17 H/s avg)
[2017-09-23 14:35:11] GPU #1: GeForce GTX 1070, 710.39 H/s (717.88 H/s avg)
[2017-09-23 14:35:11] accepted: 1/1 (100.00%), 1428.76 H/s (yay!!!)
[2017-09-23 14:35:17] Stratum detected new block
[2017-09-23 14:35:17] GPU #0: GeForce GTX 1070, 715.12 H/s (714.29 H/s avg)
[2017-09-23 14:35:19] GPU #1: GeForce GTX 1070, 720.93 H/s (718.08 H/s avg)
[2017-09-23 14:35:57] Stratum detected new block
[2017-09-23 14:35:59] GPU #1: GeForce GTX 1070, 720.85 H/s (718.96 H/s avg)
[2017-09-23 14:36:00] GPU #0: GeForce GTX 1070, 717.43 H/s (715.36 H/s avg)
[2017-09-23 14:36:52] Pool set diff to 245007
[2017-09-23 14:36:52] Stratum detected new block
[2017-09-23 14:40:03] GPU #0: GeForce GTX 1070, 713.93 H/s (716.51 H/s avg)
[2017-09-23 14:40:04] GPU #1: GeForce GTX 1070, 720.59 H/s (719.81 H/s avg)
[2017-09-23 14:40:59] Pool set diff to 58824.7
[2017-09-23 14:40:59] Stratum detected new block
[2017-09-23 14:41:00] GPU #0: GeForce GTX 1070, 717.95 H/s (716.70 H/s avg)
[2017-09-23 14:41:00] GPU #1: GeForce GTX 1070, 720.57 H/s (719.91 H/s avg)
[2017-09-23 14:41:23] Stratum detected new block
[2017-09-23 14:41:24] GPU #0: GeForce GTX 1070, 716.59 H/s (716.69 H/s avg)
[2017-09-23 14:41:24] GPU #1: GeForce GTX 1070, 720.54 H/s (719.95 H/s avg)
[2017-09-23 14:42:04] Pool set diff to 50000.2
[2017-09-23 14:42:04] Stratum detected new block
[2017-09-23 14:42:04] GPU #1: GeForce GTX 1070, 720.56 H/s (720.00 H/s avg)
[2017-09-23 14:42:07] GPU #0: GeForce GTX 1070, 717.18 H/s (716.73 H/s avg)
[2017-09-23 14:42:07] GPU #1: result for nonce $008006C5 does not validate on CPU!
[2017-09-23 14:42:10] GPU #1: result for nonce $008006C5 does not validate on CPU!
[2017-09-23 14:42:13] GPU #1: result for nonce $008006C5 does not validate on CPU!
[2017-09-23 14:42:15] GPU #1: result for nonce $008006C5 does not validate on CPU!
[2017-09-23 14:42:18] GPU #1: result for nonce $008006C5 does not validate on CPU!
[2017-09-23 14:42:21] GPU #1: result for nonce $008006C5 does not validate on CPU!
[2017-09-23 14:42:24] GPU #1: result for nonce $008006C5 does not validate on CPU!
[2017-09-23 14:42:26] GPU #1: result for nonce $008006C5 does not validate on CPU!
[2017-09-23 14:42:29] GPU #1: result for nonce $008041DF does not validate on CPU!
[2017-09-23 14:42:32] GPU #1: result for nonce $008041DF does not validate on CPU!
[2017-09-23 14:42:34] GPU #1: result for nonce $008041DF does not validate on CPU!
[2017-09-23 14:42:37] GPU #1: result for nonce $008041DF does not validate on CPU!
[2017-09-23 14:42:40] GPU #1: result for nonce $008041DF does not validate on CPU!
[2017-09-23 14:42:43] GPU #1: result for nonce $008041DF does not validate on CPU!
[2017-09-23 14:42:45] GPU #1: result for nonce $008041DF does not validate on CPU!
[2017-09-23 14:42:48] GPU #1: result for nonce $008041DF does not validate on CPU!
[2017-09-23 14:42:51] GPU #1: result for nonce $008041DF does not validate on CPU!
[2017-09-23 14:42:54] GPU #1: result for nonce $008041DF does not validate on CPU!
[2017-09-23 14:42:56] GPU #1: result for nonce $008041DF does not validate on CPU!
[2017-09-23 14:42:59] GPU #1: result for nonce $008041DF does not validate on CPU!
[2017-09-23 14:42:59] Stratum detected new block
[2017-09-23 14:43:00] GPU #0: GeForce GTX 1070, 714.77 H/s (716.54 H/s avg)
[2017-09-23 14:43:02] GPU #1: result for nonce $008041DF does not validate on CPU!
[2017-09-23 14:43:02] GPU #1: GeForce GTX 1070, 700.57 H/s (717.96 H/s avg)
[2017-09-23 14:43:07] Stratum detected new block
[2017-09-23 14:43:08] GPU #0: GeForce GTX 1070, 714.21 H/s (716.51 H/s avg)
[2017-09-23 14:43:10] GPU #1: GeForce GTX 1070, 720.60 H/s (718.00 H/s avg)
[2017-09-23 14:43:24] Stratum detected new block
[2017-09-23 14:43:24] GPU #0: GeForce GTX 1070, 714.12 H/s (716.44 H/s avg)
[2017-09-23 14:43:26] GPU #1: GeForce GTX 1070, 720.54 H/s (718.07 H/s avg)
[2017-09-23 14:43:41] GPU #0: GeForce GTX 1070, 713.45 H/s (716.36 H/s avg)
[2017-09-23 14:43:41] accepted: 3/3 (100.00%), 1434.00 H/s (yay!!!)
[2017-09-23 14:44:19] Stratum detected new block
[2017-09-23 14:44:19] GPU #1: GeForce GTX 1070, 720.56 H/s (718.28 H/s avg)
[2017-09-23 14:44:21] GPU #0: GeForce GTX 1070, 715.85 H/s (716.32 H/s avg)
[2017-09-23 14:44:21] accepted: 4/4 (100.00%), 1436.40 H/s (yay!!!)
[2017-09-23 14:44:50] GPU #0: GeForce GTX 1070, 715.27 H/s (716.26 H/s avg)
[2017-09-23 14:44:51] accepted: 5/5 (100.00%), 1435.82 H/s (yay!!!)

[2017-09-23 14:56:06] GPU #1: result for nonce $00803485 does not validate on CPU!
[2017-09-23 14:56:09] GPU #1: result for nonce $00803485 does not validate on CPU!
[2017-09-23 14:56:12] GPU #1: result for nonce $00803485 does not validate on CPU!
[2017-09-23 14:56:15] GPU #1: result for nonce $00803485 does not validate on CPU!
[2017-09-23 14:56:17] GPU #1: result for nonce $00803485 does not validate on CPU!
[2017-09-23 14:56:20] GPU #1: result for nonce $00803485 does not validate on CPU!
[2017-09-23 14:56:23] GPU #1: result for nonce $00803485 does not validate on CPU!
[2017-09-23 14:56:26] GPU #1: result for nonce $00803485 does not validate on CPU!
[2017-09-23 14:56:28] GPU #1: result for nonce $00803485 does not validate on CPU!
[2017-09-23 14:56:31] GPU #0: GeForce GTX 1070, 716.64 H/s (715.82 H/s avg)
[2017-09-23 14:56:31] accepted: 16/16 (100.00%), 1437.12 H/s (yay!!!)
[2017-09-23 14:56:31] GPU #1: result for nonce $00803485 does not validate on CPU!
[2017-09-23 14:56:34] GPU #1: result for nonce $00803485 does not validate on CPU!
[2017-09-23 14:56:37] GPU #1: result for nonce $00803485 does not validate on CPU!
[2017-09-23 14:56:39] GPU #1: result for nonce $00803485 does not validate on CPU!
[2017-09-23 14:56:40] Stratum detected new block
[2017-09-23 14:56:42] GPU #0: GeForce GTX 1070, 717.12 H/s (715.82 H/s avg)
[2017-09-23 14:56:42] GPU #1: result for nonce $00803485 does not validate on CPU!
[2017-09-23 14:56:42] GPU #1: GeForce GTX 1070, 707.28 H/s (718.34 H/s avg)
[2017-09-23 14:56:58] GPU #0: GeForce GTX 1070, 715.65 H/s (715.82 H/s avg)
[2017-09-23 14:56:58] accepted: 17/17 (100.00%), 1422.93 H/s (yay!!!)
[2017-09-23 14:57:08] GPU #0: GeForce GTX 1070, 714.64 H/s (715.81 H/s avg)
[2017-09-23 14:57:09] accepted: 18/18 (100.00%), 1421.92 H/s (yay!!!)
[2017-09-23 14:57:35] Stratum detected new block
[2017-09-23 14:57:38] GPU #0: GeForce GTX 1070, 716.26 H/s (715.81 H/s avg)
[2017-09-23 14:57:38] GPU #1: GeForce GTX 1070, 720.31 H/s (718.42 H/s avg)
[2017-09-23 14:57:49] GPU #1: GeForce GTX 1070, 715.13 H/s (718.39 H/s avg)
[2017-09-23 14:57:49] accepted: 19/19 (100.00%), 1431.39 H/s (yay!!!)
[2017-09-23 14:58:31] Stratum detected new block
[2017-09-23 14:58:31] GPU #1: GeForce GTX 1070, 720.34 H/s (718.45 H/s avg)
[2017-09-23 14:58:32] GPU #0: GeForce GTX 1070, 715.34 H/s (715.79 H/s avg)
[2017-09-23 14:58:54] Stratum detected new block
[2017-09-23 14:58:55] GPU #1: GeForce GTX 1070, 720.51 H/s (718.48 H/s avg)
[2017-09-23 14:58:56] GPU #0: GeForce GTX 1070, 717.65 H/s (715.82 H/s avg)
[2017-09-23 14:59:18] Stratum detected new block

GPU 1: an illegal memory access was encountered
cryptonight/cuda_cryptonight_core.cu line 255

hashing time :
14:33 => 14h59 ==> 26 min

What miner for cryptonight should I use while waiting for a solution ?

Should I continue with that of Salfter or that of Klaust even if they bug within 30 minutes both ?

Hi try xmr-stak-nvidia, it should be in the xmr/stakGPU/bin folder, you'll need to edit the config.txt file to account for the number of GPU's, there is a post explaining how to make the changes about 10-20 pages back.

3main does the config automatically for multiple gpus after the -1 update

[fullzero]

I just compiled from the downloaded sources on your link and I 've already got this error after a few minutes.
By the way, I did not find a build.sh, so I made a make

Therefore, the memory access pb is not resolved.

The first bug was fixed, but it looks like there's another one.
Fixing errors that I don't see on my system is not easy so it will take some time.

Please let me know when the new version is done; and I will add it to the next update.

[fullzero]

Point_2

No matter what; cc and mc are taken from INDIVIDUAL_CLOCKS  _0 values

Code:

INDIVIDUAL_CLOCKS="NO"      	# YES NO

# Set individual clocks here if INDIVIDUAL_CLOCKS="YES"
__CORE_OVERCLOCK_0=150
MEMORY_OVERCLOCK_0=100

Happened while mining SIGT with these options

Code:

COIN="SIGT"

Maxximus007_AUTO_TEMPERATURE_CONTROL="YES"

IAmNotAJeep_and_Maxximus007_WATCHDOG="YES"

# SET OC and POWERLIMIT by ALGO (see end of 1bash for ALGO OC settings)

damNmad_ALGO_SPECIFIC_OC="YES"

POWERLIMIT="YES"              	# YES NO
	
	POWERLIMIT_WATTS=76
	
__CORE_OVERCLOCK=150
MEMORY_OVERCLOCK=100

Code:

INDIVIDUAL_CLOCKS="NO"      	# YES NO

# Set individual clocks here if INDIVIDUAL_CLOCKS="YES"
__CORE_OVERCLOCK_0=150
MEMORY_OVERCLOCK_0=-1000

Code:

if [ $COIN == "SIGT" -o $COIN == "ZPOOL_SKUNK" ]
then
	POWERLIMIT_WATTS=80
__CORE_OVERCLOCK=150
MEMORY_OVERCLOCK=600
fi

Target Temperature also behaving same; getting value from TARGET_TEMP_0 and applying it on all GPU's (in AUTO_TEMP)

Code:

INDIVIDUAL_TARGET_TEMPS="NO"   	# YES NO

# Set individual target temps here if INDIVIDUAL_TARGET_TEMPS="YES"
TARGET_TEMP_0=60

Please let me know if I've missed or mistook something!!

I believe I have the same issue on Overclock and Power Limits
Power limit problem has been there since v0018, but overclock is new from v0019.1

I think these are fixed with 1-1 please let me know if they aren't.

[fullzero]

This is slightly off topic, but I'm guessing  you were able to login to SSH. Can anyone share the default root password for SSH?

I tried the one listed of 'miner1' but I'm not able to gain access. Version I just installed is v0019-1.

Thank you!

to ssh into a rig from a *nix system use:

ssh m1@IPADDRESSHERE

then miner1 is the password

watch the end of the v0019 demo video for a visual example.

[fullzero]

So I had a three card riser-less build (well actually one was on a riser since the AORUS are huge, no issues with this setup)

1080 ti / 1080 ti / 1070  mini

I moved to a 6 card riser build and now I have this issue . . any ideas?
(1070 mini 1070 mini 1080 TI 1080 TI 1070 mini 1070 mini
software or hardware and then what?

This should be a 3k average sols rig

Added more details below ////




2x 1080 TI + 1070 earning the same as 2x 1080 TI 4x 1070

(1.8k sol rig avg)


3k sol rig, avg 2.6k due to error, but its as if all 3 of the 1070s on the second PSU (connected add2psu PSU1 to mobo/cpu/all risers +pata to Add2psu / PSU2 mobo to add2psu+3x 1070 mini


nvOC_19 on both . .


@crazydane On average I get the best daily returns from suprnova/luck/zhash roughly maybe in that order? if my miner finds a block on luck it obviously comes out ahead. I'm using luck because it's easy to look at basic stats individually



Also in other news . . that's actually good news. .  my bitmain antminer d3 has arrived and is hashing away 2 gh/s higher than advertised from 15.5 to 17.5 iirc




When is antOC_19 coming out fullzero? xD

Hey guys still dealing with this issue . . . can anyone lend me a hand here at a bit of a loss

https://luckpool.org/workers/znVUjim9waxP73P5jQ76ezdMpvgTYVnPp3r

It's averaged out to be a bout correct but a couple times a day its still completely dropping. .

It looks like your client is softcrashing and watchdog is restarting it.  If you are using a mixed rig the most likely reason is the GPU index is counter intutive ( I have had this problem many times with mixed rigs)  try using the cmd:

Code:

sudo echo 'export CUDA_DEVICE_ORDER=PCI_BUS_ID' | sudo tee -a /etc/profile.d/cuda-device-order.sh

in the guake terminal then reboot and ensure your GPUs are OCed / PLed in the same index as the system recognizes them.

If it works Thank:  car1999 + leenoox

I added this to the -1 update.

Let me know if this works.

[papampi]

So I had a three card riser-less build (well actually one was on a riser since the AORUS are huge, no issues with this setup)

1080 ti / 1080 ti / 1070  mini

I moved to a 6 card riser build and now I have this issue . . any ideas?
(1070 mini 1070 mini 1080 TI 1080 TI 1070 mini 1070 mini
software or hardware and then what?

This should be a 3k average sols rig

Added more details below ////




2x 1080 TI + 1070 earning the same as 2x 1080 TI 4x 1070

(1.8k sol rig avg)


3k sol rig, avg 2.6k due to error, but its as if all 3 of the 1070s on the second PSU (connected add2psu PSU1 to mobo/cpu/all risers +pata to Add2psu / PSU2 mobo to add2psu+3x 1070 mini


nvOC_19 on both . .


@crazydane On average I get the best daily returns from suprnova/luck/zhash roughly maybe in that order? if my miner finds a block on luck it obviously comes out ahead. I'm using luck because it's easy to look at basic stats individually



Also in other news . . that's actually good news. .  my bitmain antminer d3 has arrived and is hashing away 2 gh/s higher than advertised from 15.5 to 17.5 iirc




When is antOC_19 coming out fullzero? xD

Hey guys still dealing with this issue . . . can anyone lend me a hand here at a bit of a loss

https://luckpool.org/workers/znVUjim9waxP73P5jQ76ezdMpvgTYVnPp3r

It's averaged out to be a bout correct but a couple times a day its still completely dropping. .

It looks like your client is softcrashing and watchdog is restarting it.  If you are using a mixed rig the most likely reason is the GPU index is counter intutive ( I have had this problem many times with mixed rigs)  try using the cmd:

Code:

sudo echo 'export CUDA_DEVICE_ORDER=PCI_BUS_ID' | sudo tee -a /etc/profile.d/cuda-device-order.sh

in the guake terminal then reboot and ensure your GPUs are OCed / PLed in the same index as the system recognizes them.

If it works Thank:  car1999 + leenoox

I added this to the -1 update.

Let me know if this works.

You can also enable the telegram, to let you know whats goin on
I will post a new one tomorrow.

[damNmad]

v0019-1 update:

Lots of changes; please keep in mind this update is beta: it will most likely have some bugs, if you don't want to deal with any bugs you can wait until any issues have already been found and fixed by the community.

Before updating; please copy your 1bash (and any other files you have changed/customized) to a different directory (such as the desktop).

To update:

open 1bash with gedit and ensure:

Code:

AUTO_UPDATE="BETA" 

close any terminal currently open; then:

open a guake terminal ( press f12 ) and type the following, then press enter:

Code:

bash 4update

This will launch 4update which will update your 2unix file.  

When 4update is done; gnome-terminal will auto launch.  

The new 2unix will detect your v0019 is not -1 and launch the update.

The update will install all system updates including the newest Nvidia driver.  Then update nvOC files.

When it is done your rig will reboot automatically.  

Your 1bash will be copied to a file named: your_old_1bash as a new version is required for some of the updates.  

You can copy and paste your pools / addresses into the new 1bash.  ( I will eventually automate this)

v0019-1 can support up to 19x GPUs; however it is unlikely you will be able to get more than 13x GPUs to work correctly with the new Asus 19x mobo.

Edit Additional info:

Lots of new COIN selections from damNmad and some from papampi.  I will add a full change log to the OP later today.

Thank you so much fullZero for the major update

I've planned to add this in my next update, but you have done it already

Code:

HCD=/home/m1/eth/$CLAYMORE_VERSION/ethdcrminer64

Much needed and much better update in my opinion.

In future (hopefully) users need not to edit 1bash for every update; thanks again amigo

EDIT :

I will report all the bugs/issues noticed here

Point_1

I've noticed this file is missing from papampi version:

Code:

REBOOT_REQUIRED=$(/home/m1/reboot-required)

TELEGRAM throwing this warning or sort of:

Code:

m1@m1-desktop:~$ bash /home/m1/BaliMiner_TELEGRAM_ALERTS
/home/m1/telegram: line 40: /home/m1/reboot-required: No such file or directory

I guess its a simple fix from papampi; providing the code and save that code into a reboot-required file

&&

For people who don't want to skip that warning by just commenting out this line in /home/m1/telegram file

Code:

#REBOOT_REQUIRED=$(/home/m1/reboot-required)

If your telegram bot not working while selecting 'papampi'; change this:

Code:

APIKEY=$TELEGRAM_ALERT_APIKEY

to

Code:

APIKEY=$TELEGRAM_APIKEY

Point_2

No matter what; cc and mc are taken from INDIVIDUAL_CLOCKS  _0 values

Code:

INDIVIDUAL_CLOCKS="NO"      	# YES NO

# Set individual clocks here if INDIVIDUAL_CLOCKS="YES"
__CORE_OVERCLOCK_0=150
MEMORY_OVERCLOCK_0=100

Happened while mining SIGT with these options

Code:

COIN="SIGT"

Maxximus007_AUTO_TEMPERATURE_CONTROL="YES"

IAmNotAJeep_and_Maxximus007_WATCHDOG="YES"

# SET OC and POWERLIMIT by ALGO (see end of 1bash for ALGO OC settings)

damNmad_ALGO_SPECIFIC_OC="YES"

POWERLIMIT="YES"              	# YES NO
	
	POWERLIMIT_WATTS=76
	
__CORE_OVERCLOCK=150
MEMORY_OVERCLOCK=100

Code:

INDIVIDUAL_CLOCKS="NO"      	# YES NO

# Set individual clocks here if INDIVIDUAL_CLOCKS="YES"
__CORE_OVERCLOCK_0=150
MEMORY_OVERCLOCK_0=-1000

Code:

if [ $COIN == "SIGT" -o $COIN == "ZPOOL_SKUNK" ]
then
	POWERLIMIT_WATTS=80
__CORE_OVERCLOCK=150
MEMORY_OVERCLOCK=600
fi

Target Temperature also behaving same; getting value from TARGET_TEMP_0 and applying it on all GPU's (in AUTO_TEMP)

Code:

INDIVIDUAL_TARGET_TEMPS="NO"   	# YES NO

# Set individual target temps here if INDIVIDUAL_TARGET_TEMPS="YES"
TARGET_TEMP_0=60

Please let me know if I've missed or mistook something!!

For checking if reboot is required in telegram add a reboot-required file

Put these inside:

Code:

#!/bin/bash
if [ -f /var/run/reboot-required ]; then
  echo 'yes'
else 
echo 'No'
fi

make executable by running this command:

Code:

chmod +x reboot-required

Edit:
A better way is to open telegram file
in papampi section find this line :

Code:

REBOOT_REQUIRED=$(/home/m1/reboot-required)

and change it to :

Code:

REBOOT_REQUIRED=$([ -f /var/run/reboot-required ] && echo "Yes!!!" || echo "No")

It seems its left out in the message line as well, add it to MSG :

Code:

MSG=" Worker: $WORKERNAME
Reboot Required: $REBOOT_REQUIRED
... REST_of_The_Message
"

I think I fixed these in -1.1; let me know.

Yeah, the 2nd issue has been fixed for good, I haven't tested 'papampi' telegram version (issue_1) in this update, but can see the telegram api variable has been changed in this update. Thanks for the prompt and quick update fullzero

[CryptAtomeTrader44]

hashing time :
14:33 => 14h59 ==> 26 min

What miner for cryptonight should I use while waiting for a solution ?

Should I continue with that of Salfter or that of Klaust even if they bug within 30 minutes both ?

Hi try xmr-stak-nvidia, it should be in the xmr/stakGPU/bin folder, you'll need to edit the config.txt file to account for the number of GPU's, there is a post explaining how to make the changes about 10-20 pages back.


I've been looking for, but I'm not sure I've found it, and besides, I'm not sure it's possible to use it with the MPH-switching-profit of salfter at the same time as the more CPU mining.

[IAmNotAJeep]

hashing time :
14:33 => 14h59 ==> 26 min

What miner for cryptonight should I use while waiting for a solution ?

Should I continue with that of Salfter or that of Klaust even if they bug within 30 minutes both ?

Hi try xmr-stak-nvidia, it should be in the xmr/stakGPU/bin folder, you'll need to edit the config.txt file to account for the number of GPU's, there is a post explaining how to make the changes about 10-20 pages back.


I've been looking for, but I'm not sure I've found it, and besides, I'm not sure it's possible to use it with the MPH-switching-profit of salfter at the same time as the more CPU mining.

you can simultaneously cpu mine with another miner while mining xmr-stak-nvidia. I can't speak for the MPH-profit-switching, but I don't see why not.

[leenoox]

This is slightly off topic, but I'm guessing  you were able to login to SSH. Can anyone share the default root password for SSH?

I tried the one listed of 'miner1' but I'm not able to gain access. Version I just installed is v0019-1.

Thank you!

to ssh into a rig from a *nix system use:

ssh m1@IPADDRESSHERE

then miner1 is the password

watch the end of the v0019 demo video for a visual example.

Just to clarify this a bit...
You can't login as "root" user trough ssh. Login as "m1" (pass: miner1) then type: su to switch to root user (same pass), or just use sudo to execute a single command as root while logged in as m1