Topic: SRBMiner-MULTI GPU & CPU Miner 0.9.4 - page 10. (Read 45053 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

Dynex is the only supported algo for VII on newer drivers. For other algorithms you must use old drivers. (20.40 on linux)

Hi Doc,

Some of my rigs in my small farm ran with 414 mallob error with full power over the night without restarting. Profitability's low and power aint cheap either, any way for us to reset the miner when 414 occur?

any chance for support on radeon pro vii.  the titan v works and does mine.. but the radeon cant seem to create dag for ReTHereum.  TIA

Output from 2.3.5 windows 11.  newest drivers on nvidia and amd

Detecting GPU devices...

GPU0 : nvidia_titan_v                        [unknown_nvidia][MEM: 12 GB][CU:   80][BUS: 01]
GPU1 : amd_radeon_pro_vii                    [gfx906        ][MEM: 16 GB][CU:   60][BUS: 04]

======================================================================
SRBMiner-MULTI 2.3.5

Press 's' to display stats
Press 'p' to switch to the next pool
Press 'o' to switch to the previous pool
Press 0-9 to disable/enable GPU 0-9, shift+0-9 for GPU 10-19
======================================================================

Algorithm/s         : ethashb3 [1.00% fee]
Gpu mining          : enabled
Cpu mining          : disabled
Watchdog            : enabled
Gpu tweaking        : disabled

[2023-08-27 18:02:56] Initializing GPU0
[2023-08-27 18:02:56] Initializing GPU1
[2023-08-27 18:02:56] GPU1 couldn't create program for ctx->algorithm
[2023-08-27 18:02:56] GPU0 |A0|ethashb3            |INTENSITY:         23|
[2023-08-27 18:02:59] Connected to us.vipor.net:5073 [ethashb3]
[2023-08-27 18:02:59] Epoch    : 11 [ethashb3]
[2023-08-27 18:03:01] GPU0 1111MB DAG created in 1121ms [ethashb3]
[2023-08-27 18:03:10] Job received [00001847           ] [ethashb3][0]

V2.3.5
+ Added support for dual mining ETHASHB3/BLAKE3_ALEPHIUM on NVIDIA and AMD RDNA1/2/3 GPUs
+ Minor performance improvement on algorithm 'ethashb3'
+ Minor performance improvement on algorithm 'dynex'
+ Lowered devfee for algorithm 'ethashb3' to 1%
+ Added field 'wallet' to API->algorithms->pool
+ Minor bug fixes

A huge request to change the output of the failed map not at the end of the entire log, but at the beginning of the failure. Or change the waiting time for the end of the log.

RTH+RADİANT+ZİL CONFİG windows

SRBMiner-MULTI.exe --disable-cpu   --algorithm ethashb3 --pool RTHPOOL --wallet RTHWALLET  --algorithm sha512_256d_radiant --pool RADİANTPOOL --wallet radiant-wallet  --zil-enable --zil-pool ZİLPOOL --zil-wallet ZİLWALLET
 
pause