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

Did you get it to run in a terminal with the suggestions?

Try different sleep settings to see if it works. It also depends what cpu/mem you have in other words the faster your system is the longer sleep you might need.

I already do a sleep 1.  Do I need 2 seconds?

Try command line/Terminal first. Go back to basic

./SRBMiner-MULTI --disable-gpu --algorithm scryptn2 --pool stratum+tcp://scryptn2.na.mine.zpool.ca:4339 --wallet xxxx --password myrigname

If that is working try:

./SRBMiner-MULTI --disable-gpu --cpu-threads 8 --give-up-limit 0 --algorithm scryptn2 --pool stratum+tcp://scryptn2.na.mine.zpool.ca:4339 --wallet xxxx --password myrigname

Do note some options require root.

When using it in a script try

sleep 2
./SRBMiner-MULTI --disable-gpu --cpu-threads 8 --give-up-limit 0 --algorithm scryptn2 --pool stratum+tcp://scryptn2.na.mine.zpool.ca:4339 --wallet xxxx --password myrigname
sleep 2

Seems when using a (bash)script sometimes you have to add a sleep to give it time to be handled properly.

Probably tries to restart itself, and not quit ?
A log would be more useful than just guessing here 

Thanks, that worked!

Although on one machine (Core i5 1135G7), it would look like it would start mining then it just says Killed and then exits.

It seems to only happens to that one CPU.  Any ideas?

EDIT:
Noticed it's quiting and not allowing my script to continue.

"Too many job errors for this pool connection, reconnecting [scryptn2]"

My script goes to the next miner to mine another pool/coin, but SRBMiner just quits and not let me bash script continue.  What is going on?

Change your command to ./SRBMiner-MULTI --give-up-limit 0 --disable-gpu --algorithm scryptn2 --pool stratum+tcp://scryptn2.na.mine.zpool.ca:4339 --wallet xxxx --password myrigname --cpu-threads 8

Anything enabling or disabling cpus/gpus goes in front of --algorithm.

I cannot get SRBMiner-Multi to work on zpool mining with scryptn2.

 ./SRBMiner-MULTI --give-up-limit 0 --algorithm scryptn2 --pool stratum+tcp://scryptn2.na.mine.zpool.ca:4339 --disable-gpu --wallet xxxx --password myrigname --cpu-threads 8

I get this:
Devfee pool/s not reachable - please check your firewall/antivirus is not blocking outgoing connections


Mining with another miner with the same info works fine.  Right now I'm using this one, but wanted to try SRBM because it seems to work in the Windows version and the hashrate seems higher with SRBM than cpuminer.

https://github.com/fireworm71/veriumMiner

V0.7.9
+ Added algorithm 'cosa' (COSA - Cosanta coin) for CPU mining, fee 2.0%
+ Fixed hashrate regression on 'heavyhash' algorithm for Navi cards

New video tutorial:

How to change memory timings in real time

you should manually set difficulty much higher ( --password d=5 ) for example

---------------------
Pool:
Workers: 2
NAME   DIFF   HASHRATE (NOW/AVG)
018   0.128   474.75/354.28 MH/s
060   0.128   392.19/433.56 MH/s
--------------------------------------------
Real:
018 RIG - 2 cards RX470-580 x ~650Mh = ~1.3Gh
060 RIG - 4 cards RX470-580 x ~650Mh = ~2.6Gh

Pool = 787Mh
Real = 3.9Gh

Hi
2021-07-24 20:42:55] GPU1[t0] result rejected [job not found] [circcash][0]
[2021-07-24 20:42:55] GPU5[t0] result rejected [job not found] [circcash][0]
[2021-07-24 20:42:55] GPU0[t0] result rejected [job not found] [circcash][0]
[2021-07-24 20:42:55] GPU4[t0] result rejected [job not found] [circcash][0]
[2021-07-24 20:42:55] GPU4[t0] result rejected [job not found] [circcash][0]
[2021-07-24 20:42:55] GPU1[t0] result rejected [job not found] [circcash][0]
[2021-07-24 20:42:55] GPU8[t0] result rejected [job not found] [circcash][0]
[2021-07-24 20:42:55] GPU7[t0] result rejected [job not found] [circcash][0]
[2021-07-24 20:42:55] GPU7[t0] result rejected [job not found] [circcash][0]
[2021-07-24 20:42:55] GPU8[t0] result rejected [job not found] [circcash][0]
[2021-07-24 20:42:55] GPU6[t0] result rejected [job not found] [circcash][0]
[2021-07-24 20:42:55] GPU7[t0] result rejected [job not found] [circcash][0]
[2021-07-24 20:42:55] Socket error : 104 [circcash]
[2021-07-24 20:42:55] Reconnecting to stratum-ru.rplant.xyz:17050 in 3 seconds [circcash]
[2021-07-24 20:42:58] Pool unexpectedly closed the connection [circcash]
[2021-07-24 20:42:58] Reconnecting to stratum-ru.rplant.xyz:17050 in 3 seconds [circcash]

I think this for a rig with a large number of GPUs works fine for 4 cards for sure.

V0.7.8
+ Added algorithm 'circcash' for GPU mining, fee 0.85%
+ Performance increase on 'heavyhash' algorithm on GPU's (~15-25%)
+ Performance increase on 'verushash' algorithm on CPU's supporting SSE4.2 and AES (~4%)
+ Added parameter '--gpu-manual-tuning' for real time editing of memory timings (check Help\Gpu_Manual_Tuning.txt)
+ Added parameter '--log-file-mode' (check Help\Cmd_Common_Parameters.txt)
+ Fixed auto setup on Ethash algorithm for Navi/Navi2 cards that broke in previous version
+ Removed devfee for 'randomwow' algorithm
+ Removed devfee for 'bl2bsha3' algorithm
+ Removed devfee for 'eaglesong' algorithm
+ Removed devfee for 'k12' algorithm
+ Removed devfee for 'kadena' algorithm
+ Removed devfee for 'minotaur' algorithm
+ Minor bug fixes

You can now set/change memory timings in real time! For details refer to Help\Gpu_Manual_Tuning.txt

Have you tried switching to the other compute drivers? I have no idea about RaveOS but on Hive there is a specific driver version the kicks it back up again.

Hi,
I have some issues when using for xhv coin under linux ( RaveOS) comparing with windows.
Under linux my baffin cards like RX 550 2Gb, RX 560 2Gb works only 300 h/s. But it will get 500 h/s more in windows, with same core, mem, and voltage.
Let me know the problem and how to solve it.
Thank you.

Hi,
whats your ETH hashrate/wattage on RX6700xt/6800/6800xt?

Use gpu's 0,1,2

is there a config to select a gpu to mine but not all? example: only 1 of 2 gpus will mine.

Pretty much to keep it from being easily optimized and maintain the reasonably large instruction set. That goes a long way towards making certain types of development a lot harder to do.

You are from the Raptoreum team right? I must ask why not making all CN algos use same scratchpad size? That way there would be no such big HR fluctuations + the num of used cpu cache could be known and so num of worker threads could be chosen much more efficiently. Right now the other miner choses to use ALL threads which might be efficient only when mining the small scratchpad CN algos, but not when doing the 2MB ones.
This is why my miner doesnt use all the threads but let's say it selects num of threads based on an avg. of all scratchpad sizes and available L3, L2 caches.
There is no efficient way of doing this because of the different memory requirements for CN algos..