Topic: SRBMiner-MULTI GPU & CPU Miner 0.9.4 - page 6. (Read 42257 times)

What's more profitable at the moment? Dynex+ dualmining or just dynex stand alone?

I get around 3.1kh per rx 470 right now on just dynex single mining.

V2.3.8
+ Added support for NVIDIA 'Volta' architecture - displayed as 'unknown_nvidia' but supported algorithms should work
+ Dynex bug fixes
+ Minor bug fixes

!MANDATORY UPGRADE FOR DYNEX MINING!

To be able to continue mining, users MUST upgrade to this version ( v 2.3.8 ) as soon as possible!
Older versions will stop working in a few days (i don't know the exact date - Dynex team will make that decision).

Hi.
Trying to mine DNX on 6x 5700XT for the first time.

Upgraded SRBMiner to 2.3.7 but its always stuck here

[2023-10-11 17:01:46] Job type: SAT
[2023-10-11 17:01:46] Chips needed: 900000000
[2023-10-11 17:01:46] Chips available: 2574
[2023-10-11 17:01:51] Mallob error: [Timeout was reached]
[2023-10-11 17:01:57] Updated capacity with mallob endpoint https://dnx.us.ekapool.com
[2023-10-11 17:01:57] Preparing data, please wait..
[2023-10-11 17:01:58] GPU0 allocating memory for 429 chips
[2023-10-11 17:01:58] GPU0 doing init - please wait
[2023-10-11 17:01:58] GPU0 init...
[2023-10-11 17:02:03] GPU1 allocating memory for 429 chips
[2023-10-11 17:02:03] GPU1 doing init - please wait
[2023-10-11 17:02:03] GPU1 init...
[2023-10-11 17:02:08] GPU2 allocating memory for 429 chips
[2023-10-11 17:02:08] GPU2 doing init - please wait
[2023-10-11 17:02:08] GPU2 init...

If I disable GPU2 then it stops at GPU1 or 3, never gets through initialization.

Whats wrong?

Hi Doc!
I used "Claymore's Ethereum Dual Miner Manager" Connector from https://bitcointalksearch.org/topic/clayconn-using-srbminer-rigs-with-claymores-manager-4324950 in 2018 (CN times) to monitor rigs running old SRBMiner. Now its not working(( Did you change API? Or may be other solutions to monitor SRBMinerMulti?

2023-10-10 00:00:12] GPU0 CC0: 1450MHZ
[2023-10-10 00:00:12] GPU0 MC0: [FAILED]
[2023-10-10 00:00:12] GPU1 CC0: 1450MHZ
[2023-10-10 00:00:12] GPU1 MC0: [FAILED]
[2023-10-10 00:00:12] GPU2 CC0: 1450MHZ
[2023-10-10 00:00:12] GPU2 MC0: [FAILED]
[2023-10-10 00:00:12] GPU3 CC0: 1450MHZ
[2023-10-10 00:00:12] GPU3 MC0: [FAILED]
[2023-10-10 00:00:12] GPU4 CC0: 1450MHZ
[2023-10-10 00:00:12] GPU4 MC0: [FAILED]
[2023-10-10 00:00:12] GPU5 CC0: 1450MHZ
[2023-10-10 00:00:12] GPU5 MC0: [FAILED]
[2023-10-10 00:00:12] GPU6 CC0: 1450MHZ
[2023-10-10 00:00:12] GPU6 MC0: [FAILED]
[2023-10-10 00:00:12] GPU7 CC0: 1450MHZ
[2023-10-10 00:00:12] GPU7 MC0: [FAILED]
[2023-10-10 00:00:12] GPU8 CC0: 1450MHZ
[2023-10-10 00:00:12] GPU8 MC0: [FAILED]
[2023-10-10 00:00:12] GPU9 CC0: 1450MHZ
[2023-10-10 00:00:12] GPU9 MC0: [FAILED]
[2023-10-10 00:00:12] GPU10 CC0: 1450MHZ
[2023-10-10 00:00:12] GPU10 MC0: [FAILED]
[2023-10-10 00:00:12] GPU11 CC0: 1450MHZ
[2023-10-10 00:00:12] GPU11 MC0: [FAILED]

--mallob-endpoint mallob-eu.dnx.k1pool.com:3691
,--mallob-endpoint mallob-us.dnx.k1pool.com:3691
--zil-enable
--zil-epoch 1
--zil-pool eu.zil.k1pool.com:1111
--zil-wallet Kravu6E5qkE5xpa7oDj88qV1MNPTVyTwszA.%WORKER_NAME%
--gpu-id 0,1,2,3,4,5,6,7,8,9,10,11
--gpu-cclock0 1450
--gpu-mclock0 8000,7800,7800,+2000,2000,1600,1600,2000,2000,2000,2000,1600
--zil-cclock 1100,900,900,900,900,1050,1050,950,900,900,1050,1050
--zil-mclock 3000,2000,2000,2000,2000,1600,1600,2000,2000,2000,2000,1600

what wrong in config ? hiveos


GPU0 ZIL CC: 1100MHZ
[2023-10-10 00:26:53] GPU0 ZIL MC: [FAILED]
[2023-10-10 00:26:53] GPU1 ZIL CC: 900MHZ
[2023-10-10 00:26:53] GPU1 ZIL MC: [FAILED]
[2023-10-10 00:26:53] GPU2 ZIL CC: 900MHZ
[2023-10-10 00:26:53] GPU2 ZIL MC: [FAILED]
[2023-10-10 00:26:53] GPU3 ZIL CC: 900MHZ
[2023-10-10 00:26:53] GPU3 ZIL MC: [FAILED]
[2023-10-10 00:26:53] GPU4 ZIL CC: 900MHZ
[2023-10-10 00:26:53] GPU4 ZIL MC: [FAILED]
[2023-10-10 00:26:53] GPU5 ZIL CC: 1050MHZ
[2023-10-10 00:26:53] GPU5 ZIL MC: [FAILED]
[2023-10-10 00:26:53] GPU6 ZIL CC: 1050MHZ
[2023-10-10 00:26:53] GPU6 ZIL MC: [FAILED]
[2023-10-10 00:26:53] GPU7 ZIL CC: 950MHZ
[2023-10-10 00:26:53] GPU7 ZIL MC: [FAILED]
[2023-10-10 00:26:53] GPU8 ZIL CC: 900MHZ
[2023-10-10 00:26:53] GPU8 ZIL MC: [FAILED]
[2023-10-10 00:26:53] GPU9 ZIL CC: 900MHZ
[2023-10-10 00:26:53] GPU9 ZIL MC: [FAILED]
[2023-10-10 00:26:53] GPU10 ZIL CC: 1050MHZ
[2023-10-10 00:26:53] GPU10 ZIL MC: [FAILED]
[2023-10-10 00:26:53] GPU11 ZIL CC: 1050MHZ
[2023-10-10 00:26:53] GPU11 ZIL MC: [FAILED]
[2023-10-10 00:26:56] ZIL mining starts [1]

More than 6 rejected shares for this pool connection, restarting miner [dynex]

please how can .off  this functhion


restart miner many times

tell me an example of a body file for Dynex + radiant under the windows

SRBMiner-MULTI.exe --disable-cpu --algorithm dynex;sha512_256d_radiant --gpu-dual-mode --pool de.dynex.herominers.com:1120;ua.vipor.net:5067 --wallet X......c;1.....BA --password A --ssl false --api-enable
pause
https://imgur.com/a/JcPKhsd

1. + Added support for algorithm 'dynex' on NVIDIA GPUs

How to use it?
______________________________________________________________________________
Detected GPU devices

GPU0  

• [3] [03:00.0] : amd_radeon_rx_6600_xt [gfx1032] [8176 MB] [CU: 32] [MaxBuf: 7920 MB]

GPU1  

• [07:00.0] : amd_radeon_rx_6600_xt [gfx1032] [8176 MB] [CU: 32] [MaxBuf: 7920 MB]

GPU2  

• [1] [0a:00.0] : amd_radeon_rx_6600_xt [gfx1032] [8176 MB] [CU: 32] [MaxBuf: 7920 MB]

GPU3  [1][0] [0b:00.0] : geforce_rtx_3090 [ampere] [24576 MB] [CU: 4294967378] [MaxBuf: 6144 MB]
GPU4  [1][1] [0e:00.0] : geforce_rtx_3090 [ampere] [24576 MB] [CU: 4294967378] [MaxBuf: 6144 MB]
GPU5  

• [2] [12:00.0] : amd_radeon_rx_6600_xt [gfx1032] [8176 MB] [CU: 32] [MaxBuf: 7920 MB]

_______________________________________________________________________________ _
but 3090 still need another miner
_______________________________________________________________________________ _

GPU0 : amd_radeon_rx_6600_xt                 [gfx1032       ][MEM:  8 GB][CU:   32][BUS: 03]
GPU1 : amd_radeon_rx_6600_xt                 [gfx1032       ][MEM:  8 GB][CU:   32][BUS: 07]
GPU2 : amd_radeon_rx_6600_xt                 [gfx1032       ][MEM:  8 GB][CU:   32][BUS: 0a]
GPU5 : amd_radeon_rx_6600_xt                 [gfx1032       ][MEM:  8 GB][CU:   32][BUS: 12]

===============================
SRBMiner-MULTI 2.3.7

Press z-v to disable/enable algorithm 0-3
Press 0-9 to disable/enable GPU 0-9, shift+0-9 for GPU 10-19
===============================
Algorithm/s         : dynex+zil [2.50% fee]+[0.00% fee]
Gpu mining          : enabled
Cpu mining          : disabled
Watchdog            : enabled
___________________________________________________________________________

FIXED!!! Nvidia drivers updated.

2. ------ZIL mining got stuck for more than 300 seconds! Disabled ZIL mining.--------
Each zil-round i have that.
May be could be better lower than 300? Idk, may be 80-100-120?
I'm using old rustpool.xyz.

3. On some rigs doesn't work with the only this:
[2023-10-04 13:42:14] NAUGHTY5
It's not about 2.3.7... something another...
FIXED by reboot.

Hey Doc,

pls add overclocking features to AMD gpus.For windows users overdriventool not working with new drivers.

but you didnt try adding --gpu-id 0,1,2,3,4,5,6

gpu-cclock0 - not working properly,it only takes first value and applies to all gpus

ex:
  config :

gives us:


and yes I've tried all kinds of separators.

V2.3.7
+ Performance improvement on algorithm 'dynex' on AMD and NVIDIA GPUs
+ Minor bug fixes

Hi

I updated Hiveos installation (New drivers) and got it to run (srbminer v.2.3.6).
Got an improvement of about 6%.

Thank's Ockie

Right now it only works on driver 23.x, ill fix that for next version it will work again on 22.x

I have same error with VII + 2.3.6, rolling back to 2.3.5

Hi

I'm having problem with the latest release (srbminer v.2.3.6) together with Radeon VII cards and Dynex. (SRB v.2.3.5 work's like a charm)

Error message:
GPU0 couldn't create program for ctx->algorithm

Are there a work around?

 Please help
Don't work
Dnx+zill on polaris amd 570 8gb..
Please Please add this videocard  on supports
hive os
first coin
--gpu-intensity 100
--disable-cpu
second coin
--disable-cpu
--zil-epoch 1
PU0 |A1|ethash              |INTENSITY:         19|
[2023-09-29 17:54:56] GPU0 |A0|dynex               |INTENSITY:        105|
[2023-09-29 17:54:57] GPU1 |A0|dynex               |INTENSITY:        105|
[2023-09-29 17:54:57] GPU1 |A1|ethash              |INTENSITY:         19|
[2023-09-29 17:54:57] GPU2 |A0|dynex               |INTENSITY:        105|
[2023-09-29 17:54:57] GPU2 |A1|ethash              |INTENSITY:         19|
[2023-09-29 17:54:57] GPU3 |A0|dynex               |INTENSITY:        105|
[2023-09-29 17:54:57] GPU3 |A1|ethash              |INTENSITY:         19|
[2023-09-29 17:54:57] GPU4 |A0|dynex               |INTENSITY:        105|
[2023-09-29 17:54:57] GPU4 |A1|ethash              |INTENSITY:         19|
[2023-09-29 17:54:57] GPU5 |A0|dynex               |INTENSITY:        105|
[2023-09-29 17:54:57] GPU5 |A1|ethash              |INTENSITY:         19|
[2023-09-29 17:54:57] GPU6 |A0|dynex               |INTENSITY:        105|
[2023-09-29 17:54:57] GPU6 |A1|ethash              |INTENSITY:         19|
[2023-09-29 17:54:57] GPU7 |A0|dynex               |INTENSITY:        105|
[2023-09-29 17:54:57] GPU7 |A1|ethash              |INTENSITY:         19|
[2023-09-29 17:54:57] GPU8 |A0|dynex               |INTENSITY:        105|
[2023-09-29 17:54:57] GPU8 |A1|ethash              |INTENSITY:         19|
[2023-09-29 17:54:57] GPU9 |A0|dynex               |INTENSITY:        105|
[2023-09-29 17:54:57] GPU9 |A1|ethash              |INTENSITY:         19|
[2023-09-29 17:54:57] GPU10|A1|ethash              |INTENSITY:         19|
[2023-09-29 17:54:57] GPU10|A0|dynex               |INTENSITY:        105|

V2.3.6
+ Added support for algorithm 'dynex' on NVIDIA GPUs
+ Performance improvement on algorithm 'dynex' on AMD GPUs
+ Removed Dynex optimised dual kernels
+ Lowered devfee for algorithm 'ethashb3' to standard 0.85%
+ Added parameter '--busy-wait-recheck' which sets the NVIDIA/INTEL GPUs OpenCL busy wait recheck value per algorithm

***
--busy-wait-recheck:

Nvidia's OpenCL implementation has a bug known for many years which manifests in the way of having higher CPU usage (LA - load average) than it should be.
This will probably never get fixed, and its present only in their OpenCL implementation, but not in CUDA.
SRBMiner uses OpenCL for NVIDIA, and a workaround for this bug is used since the addition of NVIDIA support, but doing so (lowering/fixing the CPU usage bug) comes with a penalty, which is lower hashrate in some cases.
Every rig behaves differently depending on the CPU and number of GPU's used on it.
Unfortunately lowering the CPU usage also might lower the hashrate too, so finding an optimal 'golden middle' is important.

--busy-wait-recheck accepts values from 0.01 to 0.99 -> lower the value, higher the CPU usage will be, which allows for higher hashrate

Default value of --busy-wait-recheck is 0.3, which might or might not be the best value for your rig.

As a first step, set '--busy-wait-recheck 0.01' to get the maximum hashrate, then increase the value of --busy-wait-recheck and do some tests.
Experiment and try out different values to find an acceptable hashrate / CPU LA ratio.

Thank you for clarifying that.   Appreciate it!

from https://github.com/doktor83/SRBMiner-Multi/blob/master/Parameters


choose one