[ mining os ] nvoc - page 217. | Bitcointalksearch.org

Schleicher

hero member

Activity: 675

Merit: 514

Quote from: CryptAtomeTrader44 on September 23, 2017, 07:32:03 AM

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.

VoskCoin

sr. member

Activity: 1414

Merit: 487

YouTube.com/VoskCoin

Quote from: VoskCoin on September 19, 2017, 11:57:40 AM

Quote from: VoskCoin on September 19, 2017, 08:25:00 AM

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. .

VoskCoin

sr. member

Activity: 1414

Merit: 487

YouTube.com/VoskCoin

Quote from: papampi on September 23, 2017, 03:42:56 AM

Quote from: car1999 on September 23, 2017, 02:44:45 AM

Quote from: VoskCoin on September 23, 2017, 01:31:38 AM

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?

CryptAtomeTrader44

full member

Activity: 340

Merit: 103

It is easier to break an atom than partialities AE

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 ?

CryptAtomeTrader44

full member

Activity: 340

Merit: 103

It is easier to break an atom than partialities AE

Quote from: Schleicher on September 22, 2017, 01:12:19 AM

Quote from: CryptAtomeTrader44 on September 21, 2017, 05:54:08 PM

So my problem with Cryptonight hasher with the GPUs does not seem to be solved.

If you have an idea, I am taker, because I know how to apply some rules but I do not know how to program.

About 9 days ago there was a fix for the "illegal memory access" problem in ccminer-cryptonight.
Maybe your version is older than that.
The latest version is there:
https://github.com/KlausT/ccminer-cryptonight/releases

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.

I do the same test with that of Salfter
Log:

Code:

m1@MINER44:~/00.TESTS/ccminer-cryptonight-2.05$ ./ccminer -o stratum+tcp://europe.cryptonight-hub.miningpoolhub.com:20580 -u minerspeudo44.MINER44 -p x
    *** ccminer-cryptonight 2.05 (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 13:29:20] GPU #0: GeForce GTX 1070 (15 SMX), using 60 blocks of 32 threads
[2017-09-23 13:29:20] Starting Stratum on stratum+tcp://europe.cryptonight-hub.miningpoolhub.com:20580
[2017-09-23 13:29:20] 2 miner threads started
[2017-09-23 13:29:20] GPU #1: GeForce GTX 1070 (15 SMX), using 60 blocks of 32 threads
[2017-09-23 13:29:21] Pool set diff to 500054
[2017-09-23 13:29:21] Stratum detected new block
[2017-09-23 13:29:23] GPU #0: GeForce GTX 1070, 649.35 H/s (649.32 H/s avg)
[2017-09-23 13:29:23] GPU #1: GeForce GTX 1070, 633.48 H/s (633.42 H/s avg)
[2017-09-23 13:29:35] Stratum detected new block
[2017-09-23 13:29:36] GPU #0: GeForce GTX 1070, 718.36 H/s (705.85 H/s avg)
[2017-09-23 13:29:36] GPU #1: GeForce GTX 1070, 722.14 H/s (705.65 H/s avg)
[2017-09-23 13:29:52] GPU #0: GeForce GTX 1070, 716.28 H/s (711.03 H/s avg)
[2017-09-23 13:29:52] accepted: 1/1 (100.00%), 1438.42 H/s (yay!!!)
[2017-09-23 13:30:31] Stratum detected new block
[2017-09-23 13:39:46] GPU #1: GeForce GTX 1070, 720.81 H/s (720.33 H/s avg)
[2017-09-23 13:39:46] GPU #0: GeForce GTX 1070, 717.23 H/s (714.19 H/s avg)
[2017-09-23 13:39:53] Pool set diff to 50000.2
[2017-09-23 13:39:53] Stratum detected new block
[2017-09-23 13:39:54] GPU #1: GeForce GTX 1070, 721.05 H/s (720.34 H/s avg)
[2017-09-23 13:39:54] GPU #0: GeForce GTX 1070, 713.56 H/s (714.18 H/s avg)
[2017-09-23 13:39:57] GPU #0: GeForce GTX 1070, 695.57 H/s (714.10 H/s avg)
[2017-09-23 13:39:57] accepted: 10/10 (100.00%), 1416.63 H/s (yay!!!)
[2017-09-23 13:40:48] Stratum detected new block
[2017-09-23 13:40:48] GPU #0: GeForce GTX 1070, 715.50 H/s (714.19 H/s avg)
[2017-09-23 13:40:48] accepted: 11/11 (100.00%), 1436.55 H/s (yay!!!)
[2017-09-23 13:40:50] GPU #1: GeForce GTX 1070, 721.03 H/s (720.40 H/s avg)
[2017-09-23 13:40:55] Pool set diff to 75000.3
[2017-09-23 13:40:55] Stratum detected new block
[2017-09-23 13:40:55] GPU #1: GeForce GTX 1070, 721.07 H/s (720.40 H/s avg)
[2017-09-23 13:40:56] GPU #0: GeForce GTX 1070, 712.35 H/s (714.15 H/s avg)
[2017-09-23 13:41:10] GPU #0: GeForce GTX 1070, 713.88 H/s (714.14 H/s avg)
[2017-09-23 13:41:10] accepted: 12/12 (100.00%), 1434.94 H/s (yay!!!)
[2017-09-23 13:41:14] GPU #1: GeForce GTX 1070, 717.80 H/s (720.34 H/s avg)
[2017-09-23 13:41:14] accepted: 13/13 (100.00%), 1431.68 H/s (yay!!!)
[2017-09-23 13:41:17] GPU #1: GeForce GTX 1070, 698.25 H/s (720.25 H/s avg)
[2017-09-23 13:41:17] accepted: 14/14 (100.00%), 1412.13 H/s (yay!!!)
[2017-09-23 13:41:50] Stratum detected new block
[2017-09-23 13:41:50] GPU #0: GeForce GTX 1070, 716.57 H/s (714.26 H/s avg)
[2017-09-23 13:41:52] GPU #1: GeForce GTX 1070, 721.04 H/s (720.29 H/s avg)
[2017-09-23 13:42:29] Pool set diff to 52500.6
[2017-09-23 13:42:29] Stratum detected new block
[2017-09-23 13:42:29] GPU #1: GeForce GTX 1070, 721.07 H/s (720.32 H/s avg)
[2017-09-23 13:42:30] GPU #0: GeForce GTX 1070, 716.68 H/s (714.38 H/s avg)
[2017-09-23 13:43:24] Pool set diff to 50000.2
[2017-09-23 13:43:24] Stratum detected new block
[2017-09-23 13:43:25] GPU #1: GeForce GTX 1070, 721.01 H/s (720.37 H/s avg)
[2017-09-23 13:43:26] GPU #0: GeForce GTX 1070, 716.98 H/s (714.56 H/s avg)
[2017-09-23 13:43:27] GPU #1: GeForce GTX 1070, 698.73 H/s (720.30 H/s avg)
[2017-09-23 13:43:28] accepted: 15/15 (100.00%), 1415.71 H/s (yay!!!)
[2017-09-23 13:43:44] GPU #1: GeForce GTX 1070, 717.60 H/s (720.24 H/s avg)
[2017-09-23 13:43:44] accepted: 16/16 (100.00%), 1434.58 H/s (yay!!!)
[2017-09-23 13:43:50] GPU #0: GeForce GTX 1070, 713.75 H/s (714.53 H/s avg)
[2017-09-23 13:43:51] accepted: 17/17 (100.00%), 1431.35 H/s (yay!!!)
[2017-09-23 13:44:16] GPU #1: GeForce GTX 1070, 718.87 H/s (720.18 H/s avg)
[2017-09-23 13:44:16] accepted: 18/18 (100.00%), 1432.62 H/s (yay!!!)
[2017-09-23 13:44:19] Stratum detected new block
[2017-09-23 13:44:20] GPU #0: GeForce GTX 1070, 716.65 H/s (714.60 H/s avg)
[2017-09-23 13:44:21] GPU #1: GeForce GTX 1070, 721.15 H/s (720.19 H/s avg)
[2017-09-23 13:44:26] GPU #1: result for nonce $00800AD3 does not validate on CPU!
[2017-09-23 13:44:29] GPU #1: result for nonce $00800AD3 does not validate on CPU!
[2017-09-23 13:44:32] GPU #1: result for nonce $00800AD3 does not validate on CPU!
[2017-09-23 13:44:35] GPU #1: result for nonce $00800AD3 does not validate on CPU!
[2017-09-23 13:44:37] GPU #1: result for nonce $00800AD3 does not validate on CPU!
[2017-09-23 13:44:40] GPU #1: result for nonce $00800AD3 does not validate on CPU!
[2017-09-23 13:44:43] GPU #1: result for nonce $00800AD3 does not validate on CPU!
[2017-09-23 13:44:45] GPU #1: result for nonce $00800AD3 does not validate on CPU!
[2017-09-23 13:44:48] GPU #1: result for nonce $00800AD3 does not validate on CPU!
[2017-09-23 13:44:51] GPU #1: result for nonce $00800AD3 does not validate on CPU!
[2017-09-23 13:44:54] GPU #1: result for nonce $00800AD3 does not validate on CPU!
[2017-09-23 13:44:56] GPU #1: result for nonce $00800AD3 does not validate on CPU!
[2017-09-23 13:44:59] GPU #1: result for nonce $00800AD3 does not validate on CPU!
[2017-09-23 13:45:02] GPU #1: result for nonce $00800AD3 does not validate on CPU!
[2017-09-23 13:45:05] GPU #1: result for nonce $00800AD3 does not validate on CPU!
[2017-09-23 13:45:07] GPU #1: result for nonce $00800AD3 does not validate on CPU!
[2017-09-23 13:45:10] GPU #1: result for nonce $00800AD3 does not validate on CPU!
[2017-09-23 13:45:13] GPU #1: result for nonce $00800AD3 does not validate on CPU!
[2017-09-23 13:45:14] Stratum detected new block
[2017-09-23 13:45:16] GPU #1: result for nonce $00800AD3 does not validate on CPU!
[2017-09-23 13:45:16] GPU #1: GeForce GTX 1070, 702.95 H/s (719.20 H/s avg)
[2017-09-23 13:45:16] GPU #0: GeForce GTX 1070, 714.44 H/s (714.59 H/s avg)
[2017-09-23 13:45:18] Stratum detected new block
[2017-09-23 13:45:18] GPU #1: GeForce GTX 1070, 721.22 H/s (719.21 H/s avg)
[2017-09-23 13:45:19] GPU #0: GeForce GTX 1070, 712.47 H/s (714.59 H/s avg)
[2017-09-23 13:45:24] GPU #0: GeForce GTX 1070, 708.94 H/s (714.56 H/s avg)
[2017-09-23 13:45:25] accepted: 19/19 (100.00%), 1430.17 H/s (yay!!!)
[2017-09-23 13:45:38] Pool set diff to 75000.3
[2017-09-23 13:45:38] Stratum detected new block
[2017-09-23 13:45:38] GPU #0: GeForce GTX 1070, 714.98 H/s (714.55 H/s avg)
[2017-09-23 13:45:40] GPU #1: GeForce GTX 1070, 721.06 H/s (719.25 H/s avg)
[2017-09-23 13:46:33] Pool set diff to 52500.6
[2017-09-23 13:46:33] Stratum detected new block
[2017-09-23 13:46:33] GPU #1: GeForce GTX 1070, 721.01 H/s (719.34 H/s avg)
[2017-09-23 13:46:34] GPU #0: GeForce GTX 1070, 717.18 H/s (714.69 H/s avg)
[2017-09-23 13:46:51] Stratum detected new block
[2017-09-23 13:46:51] GPU #1: GeForce GTX 1070, 721.03 H/s (719.37 H/s avg)
[2017-09-23 13:46:53] GPU #0: GeForce GTX 1070, 716.33 H/s (714.72 H/s avg)
[2017-09-23 13:46:59] GPU #1: result for nonce $00801124 does not validate on CPU!
[2017-09-23 13:47:02] GPU #1: result for nonce $00801124 does not validate on CPU!
[2017-09-23 13:47:05] GPU #1: result for nonce $00801124 does not validate on CPU!
[2017-09-23 13:47:08] GPU #1: result for nonce $00801124 does not validate on CPU!
[2017-09-23 13:47:10] GPU #1: result for nonce $00801124 does not validate on CPU!
[2017-09-23 13:47:13] GPU #1: result for nonce $00801124 does not validate on CPU!
[2017-09-23 13:47:16] GPU #1: result for nonce $00801124 does not validate on CPU!
[2017-09-23 13:47:19] GPU #1: result for nonce $00801124 does not validate on CPU!
[2017-09-23 13:47:21] GPU #1: result for nonce $00801124 does not validate on CPU!
[2017-09-23 13:47:24] GPU #1: result for nonce $00801124 does not validate on CPU!
[2017-09-23 13:47:27] GPU #1: result for nonce $00801124 does not validate on CPU!
[2017-09-23 13:47:30] GPU #1: result for nonce $00801124 does not validate on CPU!
[2017-09-23 13:47:32] GPU #1: result for nonce $00801124 does not validate on CPU!
[2017-09-23 13:47:35] GPU #1: result for nonce $00801124 does not validate on CPU!
[2017-09-23 13:47:38] GPU #1: result for nonce $00801124 does not validate on CPU!
[2017-09-23 13:47:41] GPU #1: result for nonce $00801124 does not validate on CPU!
[2017-09-23 13:47:43] GPU #1: result for nonce $00801124 does not validate on CPU!
[2017-09-23 13:47:46] GPU #1: result for nonce $00801124 does not validate on CPU!
[2017-09-23 13:47:46] Pool set diff to 50000.2
[2017-09-23 13:47:46] Stratum detected new block
[2017-09-23 13:47:47] GPU #0: GeForce GTX 1070, 714.57 H/s (714.72 H/s avg)
[2017-09-23 13:47:49] GPU #1: result for nonce $00801124 does not validate on CPU!
[2017-09-23 13:47:49] GPU #1: GeForce GTX 1070, 703.51 H/s (718.55 H/s avg)
[2017-09-23 13:47:57] GPU #0: GeForce GTX 1070, 709.93 H/s (714.67 H/s avg)
[2017-09-23 13:47:58] accepted: 20/20 (100.00%), 1413.43 H/s (yay!!!)
[2017-09-23 13:48:42] Stratum detected new block
[2017-09-23 13:48:42] GPU #1: GeForce GTX 1070, 719.98 H/s (718.62 H/s avg)
[2017-09-23 13:48:42] accepted: 21/21 (100.00%), 1429.91 H/s (yay!!!)
[2017-09-23 13:48:43] GPU #0: GeForce GTX 1070, 714.48 H/s (714.65 H/s avg)
[2017-09-23 13:49:06] GPU #1: GeForce GTX 1070, 718.84 H/s (718.62 H/s avg)
[2017-09-23 13:49:06] accepted: 22/22 (100.00%), 1433.32 H/s (yay!!!)
[2017-09-23 13:49:15] Stratum detected new block
[2017-09-23 13:49:15] GPU #0: GeForce GTX 1070, 716.37 H/s (714.70 H/s avg)
[2017-09-23 13:49:17] GPU #1: GeForce GTX 1070, 720.94 H/s (718.63 H/s avg)
[2017-09-23 13:49:38] GPU #1: GeForce GTX 1070, 718.53 H/s (718.63 H/s avg)
[2017-09-23 13:49:38] accepted: 23/23 (100.00%), 1434.90 H/s (yay!!!)
[2017-09-23 13:49:44] GPU #1: result for nonce $00804923 does not validate on CPU!
[2017-09-23 13:49:46] GPU #1: result for nonce $00804923 does not validate on CPU!
[2017-09-23 13:49:49] GPU #1: result for nonce $00804923 does not validate on CPU!
[2017-09-23 13:49:52] GPU #1: result for nonce $00804923 does not validate on CPU!
[2017-09-23 13:49:55] GPU #1: result for nonce $00804923 does not validate on CPU!
[2017-09-23 13:49:57] GPU #1: result for nonce $00804923 does not validate on CPU!
[2017-09-23 13:50:00] GPU #1: result for nonce $00804923 does not validate on CPU!
[2017-09-23 13:50:03] GPU #1: result for nonce $00804923 does not validate on CPU!
[2017-09-23 13:50:05] GPU #1: result for nonce $00804923 does not validate on CPU!
[2017-09-23 13:50:07] Stratum detected new block
[2017-09-23 13:50:08] GPU #1: result for nonce $00804923 does not validate on CPU!
[2017-09-23 13:50:08] GPU #1: GeForce GTX 1070, 703.00 H/s (718.25 H/s avg)
[2017-09-23 13:50:09] GPU #0: GeForce GTX 1070, 715.61 H/s (714.74 H/s avg)
[2017-09-23 13:50:46] GPU #1: GeForce GTX 1070, 719.61 H/s (718.29 H/s avg)
[2017-09-23 13:50:46] accepted: 24/24 (100.00%), 1435.22 H/s (yay!!!)
[2017-09-23 13:51:03] Stratum detected new block
[2017-09-23 13:51:04] GPU #1: GeForce GTX 1070, 719.85 H/s (718.30 H/s avg)
[2017-09-23 13:51:05] GPU #0: GeForce GTX 1070, 716.97 H/s (714.84 H/s avg)
[2017-09-23 13:51:17] Stratum detected new block
[2017-09-23 13:51:18] GPU #1: GeForce GTX 1070, 721.02 H/s (718.33 H/s avg)
[2017-09-23 13:51:19] GPU #0: GeForce GTX 1070, 715.87 H/s (714.85 H/s avg)
[2017-09-23 13:51:35] GPU #0: GeForce GTX 1070, 714.53 H/s (714.84 H/s avg)
[2017-09-23 13:51:35] accepted: 25/25 (100.00%), 1435.56 H/s (yay!!!)
[2017-09-23 13:52:12] Stratum detected new block
[2017-09-23 13:52:12] GPU #0: GeForce GTX 1070, 716.60 H/s (714.89 H/s avg)
[2017-09-23 13:52:13] GPU #1: GeForce GTX 1070, 721.01 H/s (718.44 H/s avg)
[2017-09-23 13:52:22] GPU #1: GeForce GTX 1070, 714.50 H/s (718.42 H/s avg)
[2017-09-23 13:52:22] accepted: 26/26 (100.00%), 1431.10 H/s (yay!!!)
[2017-09-23 13:52:26] Stratum detected new block
[2017-09-23 13:52:27] GPU #1: GeForce GTX 1070, 721.01 H/s (718.43 H/s avg)
[2017-09-23 13:52:28] GPU #0: GeForce GTX 1070, 715.07 H/s (714.89 H/s avg)
[2017-09-23 13:52:50] GPU #0: GeForce GTX 1070, 715.37 H/s (714.90 H/s avg)
[2017-09-23 13:52:50] accepted: 27/27 (100.00%), 1436.37 H/s (yay!!!)
[2017-09-23 13:52:55] GPU #0: GeForce GTX 1070, 703.66 H/s (714.85 H/s avg)
[2017-09-23 13:52:56] accepted: 28/28 (100.00%), 1424.67 H/s (yay!!!)
[2017-09-23 13:52:56] GPU #1: GeForce GTX 1070, 719.12 H/s (718.44 H/s avg)
[2017-09-23 13:52:56] accepted: 29/29 (100.00%), 1422.78 H/s (yay!!!)
[2017-09-23 13:53:21] Stratum detected new block
[2017-09-23 13:53:22] GPU #0: GeForce GTX 1070, 716.01 H/s (714.86 H/s avg)
[2017-09-23 13:53:23] GPU #1: GeForce GTX 1070, 721.08 H/s (718.49 H/s avg)
[2017-09-23 13:54:16] Stratum detected new block
[2017-09-23 13:54:18] GPU #0: GeForce GTX 1070, 717.21 H/s (714.95 H/s avg)
[2017-09-23 13:54:19] GPU #1: GeForce GTX 1070, 721.03 H/s (718.58 H/s avg)
[2017-09-23 13:54:37] GPU #0: GeForce GTX 1070, 714.40 H/s (714.94 H/s avg)
[2017-09-23 13:54:37] accepted: 30/30 (100.00%), 1435.43 H/s (yay!!!)
[2017-09-23 13:54:43] GPU #1: GeForce GTX 1070, 718.61 H/s (718.59 H/s avg)
[2017-09-23 13:54:43] accepted: 31/31 (100.00%), 1433.01 H/s (yay!!!)
[2017-09-23 13:54:48] GPU #1: GeForce GTX 1070, 711.36 H/s (718.56 H/s avg)
[2017-09-23 13:54:48] accepted: 32/32 (100.00%), 1425.76 H/s (yay!!!)
[2017-09-23 13:55:12] Stratum detected new block
[2017-09-23 13:55:12] GPU #0: GeForce GTX 1070, 715.29 H/s (714.95 H/s avg)
[2017-09-23 13:55:12] GPU #1: GeForce GTX 1070, 720.77 H/s (718.59 H/s avg)
[2017-09-23 13:55:20] GPU #1: GeForce GTX 1070, 715.41 H/s (718.58 H/s avg)
[2017-09-23 13:55:21] accepted: 33/33 (100.00%), 1430.70 H/s (yay!!!)
[2017-09-23 13:56:08] Stratum detected new block
[2017-09-23 13:56:08] GPU #1: GeForce GTX 1070, 720.88 H/s (718.64 H/s avg)
[2017-09-23 13:56:08] GPU #0: GeForce GTX 1070, 716.81 H/s (715.01 H/s avg)
[2017-09-23 13:57:03] Stratum detected new block
[2017-09-23 13:57:04] GPU #1: GeForce GTX 1070, 720.96 H/s (718.72 H/s avg)
[2017-09-23 13:57:05] GPU #0: GeForce GTX 1070, 716.95 H/s (715.08 H/s avg)
[2017-09-23 13:57:13] Stratum detected new block
[2017-09-23 13:57:15] GPU #1: GeForce GTX 1070, 720.98 H/s (718.73 H/s avg)
[2017-09-23 13:57:15] GPU #0: GeForce GTX 1070, 714.29 H/s (715.07 H/s avg)
[2017-09-23 13:57:21] GPU #0: GeForce GTX 1070, 710.51 H/s (715.06 H/s avg)
[2017-09-23 13:57:21] accepted: 34/34 (100.00%), 1431.49 H/s (yay!!!)
[2017-09-23 13:57:37] Stratum detected new block
[2017-09-23 13:57:37] GPU #0: GeForce GTX 1070, 717.32 H/s (715.08 H/s avg)
[2017-09-23 13:57:39] GPU #1: GeForce GTX 1070, 721.05 H/s (718.77 H/s avg)
[2017-09-23 13:58:11] GPU #1: GeForce GTX 1070, 719.41 H/s (718.78 H/s avg)
[2017-09-23 13:58:11] accepted: 35/35 (100.00%), 1436.74 H/s (yay!!!)
[2017-09-23 13:58:28] GPU #0: GeForce GTX 1070, 716.78 H/s (715.13 H/s avg)
[2017-09-23 13:58:28] accepted: 36/36 (100.00%), 1436.19 H/s (yay!!!)
[2017-09-23 13:58:32] Stratum detected new block
[2017-09-23 13:58:32] GPU #1: GeForce GTX 1070, 721.10 H/s (718.81 H/s avg)
[2017-09-23 13:58:33] GPU #0: GeForce GTX 1070, 712.71 H/s (715.12 H/s avg)
[2017-09-23 13:58:46] GPU #0: GeForce GTX 1070, 715.22 H/s (715.12 H/s avg)
[2017-09-23 13:58:47] Stratum detected new block
[2017-09-23 13:58:47] accepted: 37/37 (100.00%), 1436.31 H/s (yay!!!)
[2017-09-23 13:58:48] GPU #1: GeForce GTX 1070, 720.99 H/s (718.83 H/s avg)
[2017-09-23 13:58:49] GPU #0: GeForce GTX 1070, 709.24 H/s (715.10 H/s avg)
[2017-09-23 13:59:11] GPU #0: GeForce GTX 1070, 716.11 H/s (715.12 H/s avg)
[2017-09-23 13:59:11] accepted: 38/38 (100.00%), 1437.11 H/s (yay!!!)
[2017-09-23 13:59:42] Stratum detected new block
[2017-09-23 13:59:43] GPU #0: GeForce GTX 1070, 716.03 H/s (715.13 H/s avg)
[2017-09-23 13:59:44] GPU #1: GeForce GTX 1070, 721.00 H/s (718.89 H/s avg)
[2017-09-23 14:00:40] Stratum detected new block
[2017-09-23 14:00:42] GPU #0: GeForce GTX 1070, 713.82 H/s (715.09 H/s avg)
[2017-09-23 14:00:43] GPU #1: GeForce GTX 1070, 721.03 H/s (718.96 H/s avg)
[2017-09-23 14:01:12] GPU #1: GeForce GTX 1070, 719.21 H/s (718.96 H/s avg)
[2017-09-23 14:01:12] accepted: 39/39 (100.00%), 1433.03 H/s (yay!!!)
[2017-09-23 14:01:17] GPU #0: GeForce GTX 1070, 715.91 H/s (715.10 H/s avg)
[2017-09-23 14:01:17] accepted: 40/40 (100.00%), 1435.12 H/s (yay!!!)
[2017-09-23 14:01:23] Stratum detected new block
[2017-09-23 14:01:23] GPU #1: GeForce GTX 1070, 721.00 H/s (718.97 H/s avg)
[2017-09-23 14:01:25] GPU #0: GeForce GTX 1070, 714.78 H/s (715.09 H/s avg)
[2017-09-23 14:01:41] Stratum detected new block
[2017-09-23 14:01:41] GPU #0: GeForce GTX 1070, 716.35 H/s (715.10 H/s avg)
[2017-09-23 14:01:41] GPU #1: GeForce GTX 1070, 720.79 H/s (718.99 H/s avg)
[2017-09-23 14:01:47] Stratum detected new block
[2017-09-23 14:01:49] GPU #0: GeForce GTX 1070, 714.25 H/s (715.10 H/s avg)
[2017-09-23 14:01:49] GPU #1: GeForce GTX 1070, 720.64 H/s (719.00 H/s avg)
[2017-09-23 14:02:40] GPU #0: GeForce GTX 1070, 716.96 H/s (715.15 H/s avg)
[2017-09-23 14:02:40] accepted: 41/41 (100.00%), 1437.60 H/s (yay!!!)
[2017-09-23 14:02:42] Stratum detected new block
[2017-09-23 14:02:42] GPU #1: GeForce GTX 1070, 720.79 H/s (719.04 H/s avg)
[2017-09-23 14:02:43] GPU #0: GeForce GTX 1070, 709.32 H/s (715.14 H/s avg)
[2017-09-23 14:02:58] Stratum detected new block
[2017-09-23 14:02:58] GPU #1: GeForce GTX 1070, 721.07 H/s (719.06 H/s avg)
[2017-09-23 14:02:59] GPU #0: GeForce GTX 1070, 715.92 H/s (715.14 H/s avg)
[2017-09-23 14:03:32] Stratum detected new block
[2017-09-23 14:03:33] GPU #1: GeForce GTX 1070, 721.01 H/s (719.09 H/s avg)
[2017-09-23 14:03:34] GPU #0: GeForce GTX 1070, 716.01 H/s (715.16 H/s avg)
[2017-09-23 14:03:49] GPU #1: GeForce GTX 1070, 717.91 H/s (719.08 H/s avg)
[2017-09-23 14:03:49] accepted: 42/42 (100.00%), 1433.91 H/s (yay!!!)
[2017-09-23 14:04:03] GPU #1: result for nonce $00804AFF does not validate on CPU!
[2017-09-23 14:04:05] GPU #1: result for nonce $00804AFF does not validate on CPU!
[2017-09-23 14:04:08] GPU #1: result for nonce $00804AFF does not validate on CPU!
[2017-09-23 14:04:11] GPU #1: result for nonce $00804AFF does not validate on CPU!
[2017-09-23 14:04:13] GPU #1: result for nonce $00804AFF does not validate on CPU!
[2017-09-23 14:04:16] GPU #1: result for nonce $00804AFF does not validate on CPU!
[2017-09-23 14:04:19] GPU #1: result for nonce $00804AFF does not validate on CPU!

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

Hashing time : 13:20 =>14:04 = 34 min

What means theses messages :

Code:

result for nonce $00804AFF does not validate on CPU!

Hardware :
Motherboard : TB250BTC PRO (12 PCIe)
Intel G34xx
4 Go RAM DDR4
USB Key 32Go
2 X GTX 1070 Asus Dual
nvOC V0019 (not upgraded yet)

How can i help you to improve debugging ?

papampi

full member

Activity: 686

Merit: 140

Linux FOREVER! Resistance is futile!!!

Made some new changes to use dropbox folder. So upPASTE dont need to copy the 1bash to temp1bash everytime it checks it and just check it in dropbox folder
Tested and working with no problems

Install dropbox

Code:

sudo apt install nautilus-dropbox

Sign in
Use selective sync,
Select the folder you want to sync
Dont forget to put your 1bash in the folder (and always keep an edited working 1bash in a safe place in case you make a mistake)

Edit 1bash :

Code:

_Parallax_MODE="YES"             # YES NO

        pasteBASH="/home/m1/Dropbox/YOUR_DROPBOX_SHARED_FOLDER/1bash" 
        upPASTE_TIMEOUT_IN_MINUTES=10  ##

Edit upPASTE:
first comment out all the lines from this section:

Code:

cd /tmp
wget https://pastebin.com/raw/$pasteBASH
sleep 2
cp $pasteBASH '/home/m1/temp1bash'
sleep 2
rm $pasteBASH
sleep 2
sudo dos2unix /home/m1/temp1bash
sleep 15

To :

Code:

#cd /tmp
#wget https://pastebin.com/raw/$pasteBASH
#sleep 2
#cp $pasteBASH '/home/m1/temp1bash'
#sleep 2
#rm $pasteBASH
#sleep 2
#sudo dos2unix /home/m1/temp1bash
#sleep 15

Then, find and change these 2 lines :

From :

Code:

old=$(md5sum '/home/m1/1bash' | sed 's/[^0-9]*//g')

Code:

new=$(md5sum '/home/m1/temp1bash' | sed 's/[^0-9]*//g')

To:

Code:

old=$(cat /home/m1/1bash | md5sum | sed 's/[^0-9]*//g')

Code:

new=$(cat $pasteBASH | md5sum | sed 's/[^0-9]*//g')

And a bit lower
From :

Code:

if [ $old != $new ]
then
change="YES"
cp '/home/m1/temp1bash' '/home/m1/1bash'
sleep 2
pkill -e gnome-terminal
pkill -f 3main
pkill -e screen
sleep 4
sudo dos2unix /home/m1/1bash

To:

Code:

if [ $old != $new ]
then
change="YES"
cp $pasteBASH '/home/m1/1bash'
sleep 2
pkill -e gnome-terminal
pkill -f 3main
pkill -e screen
sleep 4
#sudo dos2unix /home/m1/1bash

papampi

full member

Activity: 686

Merit: 140

Linux FOREVER! Resistance is futile!!!

Quote from: car1999 on September 23, 2017, 02:44:45 AM

Quote from: VoskCoin on September 23, 2017, 01:31:38 AM

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

papampi

full member

Activity: 686

Merit: 140

Linux FOREVER! Resistance is futile!!!

If any one wants to algo mine MPH_EQUIHASH
Please change the port in 1 bash from 20570 (zcash port) to 17023 (Equihash auto switch port)

Code:

#MPH_EQUIHASH
MPH_WORKER=$WORKERNAME
MPH_ADDRESS="username"
MPH_EQUIHASH_POOL="us-east.equihash-hub.miningpoolhub.com"
MPH_EQUIHASH_PORT="17023"

papampi

full member

Activity: 686

Merit: 140

Linux FOREVER! Resistance is futile!!!

Quote from: Razvan17 on September 23, 2017, 02:52:04 AM

Quote from: car1999 on September 23, 2017, 02:43:37 AM

Quote from: Razvan17 on September 23, 2017, 01:20:02 AM

Can someone explain me a lil what is

GPUPowerMizerMode_Adjust="NO"

# Set PowerMizerMode
GPUPowerMizerMode=1

How must i set it? Yes or No and what does it do?

Thx

don't know, but i've never changed them and my rigs work well.

Mine works great as well but i have notice when the terminal starts after reboot that warning appears with persistance mode disabled. I did read about it and I understood it is something related to drivers. Just hope someone can explain what it really means.

Thx!

Power Mizer mostly came out for notebooks and battery life as explained HERE
I believe its better to set it to no, as it locks GPU performance and cause some problems as explained HERE

papampi

full member

Activity: 686

Merit: 140

Linux FOREVER! Resistance is futile!!!

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

Razvan17

newbie

Activity: 18

Merit: 0

Quote from: car1999 on September 23, 2017, 02:43:37 AM

Quote from: Razvan17 on September 23, 2017, 01:20:02 AM

Can someone explain me a lil what is

GPUPowerMizerMode_Adjust="NO"

# Set PowerMizerMode
GPUPowerMizerMode=1

How must i set it? Yes or No and what does it do?

Thx

don't know, but i've never changed them and my rigs work well.

Mine works great as well but i have notice when the terminal starts after reboot that warning appears with persistance mode disabled. I did read about it and I understood it is something related to drivers. Just hope someone can explain what it really means.

Thx!

car1999

full member

Activity: 350

Merit: 100

Quote from: VoskCoin on September 23, 2017, 01:31:38 AM

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.

car1999

full member

Activity: 350

Merit: 100

Quote from: Razvan17 on September 23, 2017, 01:20:02 AM

Can someone explain me a lil what is

GPUPowerMizerMode_Adjust="NO"

# Set PowerMizerMode
GPUPowerMizerMode=1

How must i set it? Yes or No and what does it do?

Thx

don't know, but i've never changed them and my rigs work well.

car1999

full member

Activity: 350

Merit: 100

thanks fullzero, It's time to upgrade my v0017 rig Cheesy

VoskCoin

sr. member

Activity: 1414

Merit: 487

YouTube.com/VoskCoin

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?

Razvan17

newbie

Activity: 18

Merit: 0

Can someone explain me a lil what is

GPUPowerMizerMode_Adjust="NO"

# Set PowerMizerMode
GPUPowerMizerMode=1

How must i set it? Yes or No and what does it do?

Thx

papampi

full member

Activity: 686

Merit: 140

Linux FOREVER! Resistance is futile!!!

Quote from: damNmad on September 22, 2017, 04:14:05 PM

Quote from: ?? on ??

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 Cheesy

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
"

bwarbwar

newbie

Activity: 12

Merit: 0

I dropped about 15 sol / card on the new update. Anyone else seeing a reduction in performance?

damNmad

full member

Activity: 378

Merit: 104

nvOC forever

Quote from: korbi.bro on September 22, 2017, 01:55:02 PM

Quote from: damNmad on September 21, 2017, 10:50:38 AM

Quote from: Bigf00t on September 21, 2017, 10:25:57 AM

Quote from: korbi.bro on September 21, 2017, 10:14:52 AM

I try to connect to suprnova.

My Code:

COIN="UBQ"

UBQ_WORKER="#ubiq"
UBQ_ADDRESS="korbi.bro"
UBQ_POOL="stratum+tcp://ubiq.suprnova.cc:3030"
UBQ_EXTENSION_ARGUMENTS=""

@Bigf00t
i will try this. Thank you.

For suprnova you will need another settings. See https://ubiq.suprnova.cc/index.php?page=gettingstarted.

You have to look for UBQ in 3main and change it over there. Because of all this different pools it makes it difficult to make one system that works out of the box.

just try this, don't change anything in 3main:

Code:

UBQ_WORKER="yourSuprNovaWorkerName"
UBQ_ADDRESS="yourSuprNovaLoginName"
UBQ_POOL="ubiq.suprnova.cc:3030"

ethminer doesn't like the stratum (I will test the options available like SP1 and SP2 and push it my next update) but claymore is happy with them. Let me know if it works.

EDIT:

Sorry, I have overlooked about the suprnova settings; @Bigf00t is right, please make sure your 3main code looks like this.

Code:

screen -dmS miner $HCD -S $UBQ_POOL -O $UBQADDR:x -SP 1 -U

Finally it works. Big thanks to damNmad and Bigf00t

You are welcome korbi

damNmad

full member

Activity: 378

Merit: 104

nvOC forever

Quote from: ?? on ??

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 Cheesy

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)

papampi's solution for the above issue

Quote from: papampi on September 23, 2017, 01:19:03 AM

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

Code:

nano reboot-required

Code:

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

Code:

chmod +x reboot-required

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

Code:

#mod by papampi
if [ $TELEGRAM_TYPE == "papampi" ]
then
CHATID=$TELEGRAM_CHATID
APIKEY=$TELEGRAM_ALERT_APIKEY

to

Code:

#mod by papampi
if [ $TELEGRAM_TYPE == "papampi" ]
then
CHATID=$TELEGRAM_CHATID
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!!

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