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

Actually if he was talking about StakeCube coin (don't know he never gives any information except 'not working'), then he was right, it's not working cause they dont use FIROPOW parameters , their period is different. I got that info from zpool admin. So i dont know why they say they use FIROPOW when .. its not.

It cant connect because you are trying to connect to a non existent host:port.
It's pool.xdag.org:13656 or 116.202.3.220:13656 you could at least spend 15 sec and check that on their page : https://xdag.org/setup?pool_id=2

Problem not in extra params, problem is what miner can't connect to pool. And we use different pools.

Tested on serveral GPU´s - mostly polaris pendants from the smallest to the biggest.



Why you don´t set a worker for epic mining? " ;R2700Pro"

this is my commandline for testing xdag

SRBMiner-MULTI.exe --disable-gpu --algorithm xdag --pool xdagmine.com:13654 --wallet ****************** --worker srbminer --cpu-threads 2

why so much extra arguments? You really need them? I don´t think so. Keep the commandline easier. If it works, then you can start to add some extra arguments.

What GPU you use?

1.0.9 - Xdag. 1.1.1 not work for me also. Can you provide your command line for Xdag.

Mine is:
SRBMiner-MULTI.exe --multi-algorithm-job-mode 3 --disable-gpu --algorithm randomepic;xdag --pool 51pool.online:4416;xdag.org:13656 --wallet ************;ZgSUDwUv0V2YpWIrbM69q58iZRDg7gLH --cpu-threads 8;8 --password *******;x --worker ;R2700Pro --keepalive true;false --retry-time 5 --max-no-share-sent 1600

And what miner version you are using for Xdag? Really hard to help you with zero information.
My first test on xdag = it is working = i will test it deeper but i am sure all is fine.
Second i tested yescryptR16 on a GPU = success shares found and all working flawless.

Tested with 1.1.3

aunt edit says:

XDAG mining work flawless - the failure by BoozyTalking is a wrong wallet - a wrong wallet results in the reconnecting failure after every sent job to the pool.

If i have more time later, i will look into the Firo failure - but i think it is also an failure by BoozyTalking

GPU is working, stats show hashrate, but no shares is found (tested about 30 minits),
with same difficulty (0.2) even celeron J1900 (which hashrate is less about 10 times)
can found 10-20 shares.

About Xdag - that miner version i use at that moment not work.

last time you also said xdag not working but there was no issue with it at least for other people who were/are mining it.

can you describe 'not working' please ?

Hi, Doktro83. Yescryptr16 algo not work on RX580 gpu, please fix it.

V1.1.3
+ Fixed miner crashing on ETHASH/ETCHASH + KASPA/HEAVYHASH dual mining options that appeared in previous version [ 1.1.2 ]
+ Added parameters '--a0-start-script' and '--a1-start-script' which run a user defined script every time algorithm 0 or 1 become active*
+ Added parameter '--start-script-delay' which delays mining for x seconds after a0 or a1 startup script was executed

***
Apply different OC settings every time an algorithm switch happens!

--a0-start-script and --a1-start-script is only for GPU's, and ONLY if using --multi-algorithm-job-mode 3 (which is automatically used when mining ZIL)
--start-script-delay can be used to define a delay (in seconds) that is applied after the script was run, but before mining resumes

Thanks for the videos, appreciate it!

RX 5700 XT - Kaspa Hashrate & Profit (Dual Ergo+KAS) - https://www.youtube.com/watch?v=xirEDGJ0gHg
RX 5700 XT - Vertcoin Hashrate & Profit - https://www.youtube.com/watch?v=d6SA7_LcJWU
My tests - RX 5700 XT with SRBMiner.

RX 570 8GB - Kaspa Hashrate & Profit (Dual Ergo+KAS) - https://www.youtube.com/watch?v=dom6KjmPoxk
My tests - RX 570 8GB with SRBMiner.

V1.1.2
+ Added algorithm 'sha256dt' (NOVO coin) for CPU/GPU mining, fee 0.85%
+ Added ETHASH/ETCHASH + SHA256DT dual mining mode
+ Added AUTOLYKOS2 + SHA256DT dual mining mode
+ Lowered devfee for 'sha512_256d_radiant' algorithm to 0.85% (CPU/GPU)
+ Reworked auto-tune procedure for GPU's
+ Added parameter '--gpu-disable-interleaving' which disables interleaving of threads (only when same GPU runs 2+ threads) - might get better hashrate in some cases
+ --gpu-buffer-mode 1 should work more stable on 4GB GPU's now
+ Bug fixes & minor improvements

V1.1.1
+ Added algorithm 'evrprogpow' (EVRMORE coin) for CPU/GPU mining, fee 0.85%
+ Performance increase on 'cryptonight_gpu' algorithm for RDNA/RDNA2 GPU's
+ Performance increase on 'sha512_256d_radiant' algorithm for RDNA2 GPU's
+ Performance increase on 'lyra2v2_webchain' algorithm for GPU's
+ Progpow algorithms bugfixes [kawpow, firopow, epic, sero, veil, veriblock, zano]
+ Added parameter '--force-msr-tweaks' which forces usage of MSR tweaks for CPU mined algorithm/s *
+ Added support for gfx1036
+ Fixed detection of RX550 GPU's on newer AMD drivers

***
MSR tweaking was enabled by default for every algorithm on previous miner versions if miner had admin/root privileges.
Not every CPU mineable algorithm benefits from this, so from this version it will be automatically enabled only to algorithms that are known to benefit from it.
If one wants to force enable MSR tweaking it can be done adding '--force-msr-tweaks' parameter

XDAG mining not work.


Also FiroPow not work with coins which use FiroPow (except Firo coin).

I like SrbMiner but for Monero mining Xmrig works better than SrbMiner every time I try.
I would use Xmrig for Monero mining

Your mining command line for miner is brainless, why you set 4 algos for mining?

Hey guys,

I need your help. I user an older version of SRBMiner some months ago and now I always got the same errors. Do you have any Idea for a good fix?

First I will show you the Mining log:

CPU0 : AMD EPYC 7702P 64-Core Processor [L3:  16384 KB][L2:  2048 KB][L1:  256 KB][PU:   4]

======================================================================
SRBMiner-MULTI 1.1.0

Press 's' to display stats
Press 'h' to display hashrate
Press z-v to disable/enable algorithm 0-3
======================================================================

Algorithm/s         : randomx+randomx+randomx+randomx [0.85% fee]+[0.85% fee]+[0.85% fee]+[0.85% fee]
Gpu mining          : disabled
Cpu mining          : enabled
Watchdog            : enabled
Huge-pages          : available
HW-Aes              : available

[2022-10-16 22:15:00] MSR tweaking enabled
[2022-10-16 22:15:00] If miner crashes try setting --msr-use-preset parameter manually
[2022-10-16 22:15:00] Algorithm 0 available values for --cpu-threads-intensity : 1
[2022-10-16 22:15:00] Algorithm 1 available values for --cpu-threads-intensity : 1
[2022-10-16 22:15:00] Algorithm 2 available values for --cpu-threads-intensity : 1
[2022-10-16 22:15:00] Algorithm 3 available values for --cpu-threads-intensity : 1
[2022-10-16 22:15:01] 4 CPU core/s - 4 thread/s detected
[2022-10-16 22:15:01] Using 1|1|1|1 thread/s for CPU mining
[2022-10-16 22:15:02] SSL/TLS connection established with randomxmonero.auto.nicehash.com:443 [TLS_AES_256_GCM_SHA384]
[2022-10-16 22:15:02] Connected to randomxmonero.auto.nicehash.com:443 [randomx]
[2022-10-16 22:15:02] Difficulty 173576.0000000000 [randomx][0]
[2022-10-16 22:15:05] Connected to randomxmonero.auto.nicehash.com:9200 [randomx]
[2022-10-16 22:15:05] Difficulty 173576.0000000000 [randomx][1]
[2022-10-16 22:15:08] SSL/TLS connection established with randomxmonero.auto.nicehash.com:443 [TLS_AES_256_GCM_SHA384]
[2022-10-16 22:15:08] Connected to randomxmonero.auto.nicehash.com:443 [randomx]
[2022-10-16 22:15:08] Difficulty 173576.0000000000 [randomx][2]
[2022-10-16 22:15:11] Connected to randomxmonero.auto.nicehash.com:9200 [randomx]
[2022-10-16 22:15:11] Difficulty 173576.0000000000 [randomx][3]
[2022-10-16 22:15:11] Job received [00000000d95efca0] block height 2734985 [randomx][3]
[2022-10-16 22:15:14] RX Cache   initialized on node 0 [  ] [randomx]
[2022-10-16 22:15:14] RX Dataset initialized on node 0 [  ] [randomx]
[2022-10-16 22:15:14] RX Initialization time on node 0 : 12148 ms [randomx]
[2022-10-16 22:15:18] Job received [0000000056a8c973] block height 2734986 [randomx][0]
[2022-10-16 22:15:29] RX Cache   initialized on node 0 [  ] [randomx]
[2022-10-16 22:15:29] RX Dataset initialized on node 0 [  ] [randomx]
[2022-10-16 22:15:29] RX Initialization time on node 0 : 15181 ms [randomx]
[2022-10-16 22:15:29] Job received [000000002f09c1ae] block height 2734986 [randomx][1]
[2022-10-16 22:15:48] RX Cache   initialized on node 0 [  ] [randomx]
[2022-10-16 22:15:48] RX Dataset initialized on node 0 [  ] [randomx]
[2022-10-16 22:15:48] RX Initialization time on node 0 : 18996 ms [randomx]
[2022-10-16 22:15:48] Not enough free memory available to allocate dataset on node 0 [randomx]
[2022-10-16 22:15:48] Worker thread 1 stopped
[2022-10-16 22:15:48] Worker thread 0 stopped
[2022-10-16 22:15:48] Dataset 0 released
[2022-10-16 22:15:48] Cache 0 released
[2022-10-16 22:15:48] Dataset 0 released
[2022-10-16 22:15:48] Cache 0 released
[2022-10-16 22:15:48] Dataset 0 released
[2022-10-16 22:15:48] Cache 0 released


I always get the memory error. I would like to fix it. Any idea? The error always comes on the same line. I tried to reduce cpu-threads. That didn't worked because I would like to use 4 times Connection to the mining pool. I used two times startum+tcp and two times stratum+ssl. I used the guided-setup.sh for configuration. Before that I did it on another way. Please help me.

Best regards

What is the reason for such algo? All these shit-algos are scam. It is already mined with fpga or even some private asics.
I try to mine it with 6 gpus for more then 24 hours. Block difficulty is about 10Phash, maximal share difficulty generated
by my gpus was about 3T, so you need about 300-500 RTX3090 to find blocks. Electricity cost is too high to spend it for that algo.