Pages:
Author

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

hero member
Activity: 2548
Merit: 626
June 02, 2022, 08:54:24 AM
V0.9.6
+ Added algorithm 'kaspa' (KAS - Kaspa coin) for CPU/GPU mining, fee 1.00%
+ Small performance increase on 'heavyhash' algorithm for RDNA2 GPU's
+ Lower power consumption on 'heavyhash' algorithm for RDNA2 GPU's
+ Minor bug fixes
newbie
Activity: 44
Merit: 0
V0.9.5
Why was support for older cards removed?

Although those cards are really old, the real reason for removing support for Pitcairn, Tahiti, Hawaii, Fiji and Tonga is that i don't own any of these GPU's, meaning i can't test / optimise any code for them.

Oh, no!! Not the Fiji, they are good and have RAM speed (HBM1).

Can you reactivate the the Fiji ? I ask for a good friend.

Thanks.  
hero member
Activity: 2548
Merit: 626
V0.9.5
+ Added algorithm 'yescryptr8' for GPU mining, fee 0.85%
+ Added algorithm 'yescryptr16' for GPU mining, fee 0.85%
+ Added algorithm 'yescryptr32' for GPU mining, fee 0.85%
+ Added algorithm 'frkhash' (Expanse's next algorithm) for CPU/GPU mining, fee 0.85%
+ Lowered devfee for 'autolykos2' algorithm to 1.5%
+ Lowered devfee for 'blake3_alephium' algorithm to 0.85% (CPU/GPU)
+ Small performance increase on 'autolykos2' algorithm for RDNA2 GPU's
+ Small performance increase on 'dynamo' algorithm for GPU's
+ A little bit faster dataset creation on 'autolykos2' algorithm for some GPU's
+ A little bit lower power consumption on 'autolykos2' algorithm for Ellesmere GPU's
+ A little bit lower power consumption on 'ethash' algorithm for RDNA2 GPU's
+ A little bit lower power consumption on 'etchash' algorithm for RDNA2 GPU's
+ If using --cpu-threads parameter, affinity is now auto set for CPU's with 64+ threads too
+ Added parameter '--set-console-title' (Windows only) [set custom title to miner console window]
+ Added parameter aliases for --algorithm, --cpu-threads, --password, --pool, --wallet ( -a, -t, -p, -o, -u )
+ Parameter '--diff-factor' now accepts values in decimal format too
+ Removed support for older GPU's (pitcairn, tahiti, hawaii, fiji, tonga)
+ Minor bug fixes

Why was support for older cards removed?

Although those cards are really old, the real reason for removing support for Pitcairn, Tahiti, Hawaii, Fiji and Tonga is that i don't own any of these GPU's, meaning i can't test / optimise any code for them.
jr. member
Activity: 238
Merit: 3
April 11, 2022, 10:18:16 AM
well, it is possible but version 0.6.0.
I copied miner ID from version 3.0.7.0 and I made new folder in 3.0.7.2 with name of that ID. I copy/paste Srbminer.dll to this new folder and after restart of NH miner was downloaded, but yes, the old version.

EDIT: Afterthat you can extract new version to that folder... I just found a video on YT for adding back Trex minner, it is the same procedure.
hero member
Activity: 2548
Merit: 626
April 10, 2022, 12:41:49 AM
does anyone have an idea how to add srbminer back to Nicehash?
I followed this guide https://github.com/nicehash/NiceHashMiner/tree/master/doc/UserPlugins
but it doeasnt start the miner, neither the benchmark. my guess is algorithm_command_line is wrong or smth...

They removed SRBMiner cause i / a lot of other mining software don't comply to their new policy. So my guess is you won't make it work cause they don't want you to run it.
jr. member
Activity: 238
Merit: 3
April 09, 2022, 03:33:02 PM
does anyone have an idea how to add srbminer back to Nicehash?
I followed this guide https://github.com/nicehash/NiceHashMiner/tree/master/doc/UserPlugins
but it doeasnt start the miner, neither the benchmark. my guess is algorithm_command_line is wrong or smth...
hero member
Activity: 2548
Merit: 626
April 05, 2022, 07:28:51 AM
V0.9.4

+ Added algorithm 'sha3d' (Bsha3, Kylacoin, Yilacoin) for CPU/GPU mining, fee 0.85%
+ Added algorithm '0x10' (CHOX - ChainOX) for CPU/GPU mining, fee 0.85%
+ Performance increase on 'curvehash' algorithm (Pulsar coin) ( ~25% )
+ Removed 'astrobwt' algorithm
+ Removed parameter '--gpu-cn-mode'
+ Fixed issue [ https://github.com/doktor83/SRBMiner-Multi/issues/100 ]
hero member
Activity: 2548
Merit: 626
March 12, 2022, 01:11:10 AM
V0.9.3
+ Performance increase on 'curvehash' algorithm (Pulsar coin) (up to ~40% on some CPU's)
+ Removed algorithm 'argon2id_ninja'
+ Minor bug fixes
hero member
Activity: 2548
Merit: 626
February 27, 2022, 01:43:45 AM
Hi doktor83,

do you have a link for checking the mining on pool1.dynamocoin.org? My console summary is 11 MH/s (all GPUs) with your new version 0.9.2 but i will see it in real !!!!!

Thanks.

I just found out there is this : http://pool1.dynamocoin.org:8086/main.html

You should go into dynamo discord and ask there if you have further questions regarding this pool.
newbie
Activity: 44
Merit: 0
February 26, 2022, 01:45:32 PM
Hi doktor83,

do you have a link for checking the mining on pool1.dynamocoin.org? My console summary is 11 MH/s (all GPUs) with your new version 0.9.2 but i will see it in real !!!!!

Thanks.
hero member
Activity: 2548
Merit: 626
February 26, 2022, 11:13:45 AM
V0.9.2
+ Added algorithm 'dynamo' (DYNAMO - Dynamo coin) for GPU mining
+ Algorithm 'dynamo' supports only 'pool' mode (yiimp stratum compatibility removed)
+ Lowered devfee for 'dynamo' algorithm to 1% (CPU/GPU)
+ Added parameters '--gpu-progpow-safe' and '--gpu-dynamo-experimental'

***
Some drivers can create invalid programs for some periods on 'progpow' algorithms (you will notice by getting all rejected shares).
In that case try using '--gpu-progpow-safe' parameter

***
Dynamo uses algorithms which change on predefined block heights.
Using '--gpu-dynamo-experimental' parameter can make some of these algorithms hash faster, while on others it can decrease hashrate.
If you experience driver crashes with auto setup, try setting a lower intensity value manually ( --gpu-intensity parameter )

Only known public pool that uses 'pool' mode at the moment is : pool1.dynamocoin.org:4567
hero member
Activity: 2548
Merit: 626
February 23, 2022, 01:41:40 PM
All config same
all work nice on Nanopool , 2Miners, Herominers
stale shares %2-3
but when on binance pool stale shares %12-15
how can i fix this

Stales might be because the pool is too far from you (high latency), or if that's not the case then set intensity manually (--gpu-intensity parameter) to a lower value.

Which should I choose

" --gpu-intensity 21"
 or
"--gpu-raw-intensity 36xxyyzz"

autotune process return every time 36xxyyzz

Choose the one that gives you higher hashrate. After that play with alephium intensity. For example :

Code:
--disable-cpu --algorithm ethash;blake3_alephium --gpu-intensity 21;try-various-intensities-here-for-alephium .......

Or just try

Code:
--disable-cpu --algorithm ethash;blake3_alephium --gpu-auto-tune 3 .......
hero member
Activity: 2548
Merit: 626
February 23, 2022, 08:45:37 AM
All config same
all work nice on Nanopool , 2Miners, Herominers
stale shares %2-3
but when on binance pool stale shares %12-15
how can i fix this

Stales might be because the pool is too far from you (high latency), or if that's not the case then set intensity manually (--gpu-intensity parameter) to a lower value.
newbie
Activity: 315
Merit: 0
February 19, 2022, 02:40:06 AM
Why not? The more algos then more dev fee =)
hero member
Activity: 2548
Merit: 626
February 18, 2022, 11:48:23 PM
Hi, Dok! How about to add cockutoo/cuckaroo, peach and equihash 150,5, lyra2z330 algos for cpu and gpu?

No, im not interested in adding any of those. Eventually i will look into peach, i never heard about it before.
newbie
Activity: 315
Merit: 0
February 18, 2022, 02:42:20 PM
Hi, Dok! How about to add cockutoo/cuckaroo, peach and equihash 150,5, lyra2z330 algos for cpu and gpu?
hero member
Activity: 2548
Merit: 626
February 18, 2022, 10:37:20 AM
Yeah the pool issue is now fixed in 0.9.1  Grin

On the other hand I tried out DYNAMO.

You are good if you get 10% of the stated hashrate poolside because of the "duplicate shares" thing with this algo. You get good shares the first couple hours but then it falls of a cliff with only duplicate shares netting you a average 10% shares of the total stated that you should be getting because of all the rejects.

A little disappointing in the end it works like that.

Maybe do a calculation to remove all the rejects to see the "actual" hashrate you get of accepted shares?
Just a improvement suggestion.

Coin devs are working on fixing the duplicate share issue.
jr. member
Activity: 133
Merit: 5
February 18, 2022, 08:47:43 AM
Yeah the pool issue is now fixed in 0.9.1  Grin

On the other hand I tried out DYNAMO.

You are good if you get 10% of the stated hashrate poolside because of the "duplicate shares" thing with this algo. You get good shares the first couple hours but then it falls of a cliff with only duplicate shares netting you a average 10% shares of the total stated that you should be getting because of all the rejects.

A little disappointing in the end it works like that.

Maybe do a calculation to remove all the rejects to see the "actual" hashrate you get of accepted shares?
Just a improvement suggestion.
hero member
Activity: 2548
Merit: 626
February 13, 2022, 12:15:49 AM
V0.9.1
+ Added algorithm 'dynamo' (DYNAMO - Dynamo coin) for CPU mining, fee 3.00% (~ 20x-24x (+2000%) faster than the available public miner)
+ Small performance increase on 'blake3_alephium' algorithm for CPU's with AVX2
+ Added '--gpu-auto-tune 3' mode (auto tuning goes through every algorithm, but tuning one at a time - not all simultaneously)
+ If creating DAG/Dataset but mining multiple algorithms, miner now pauses work on other algorithms while the DAG/Dataset is created
+ Possible fix for 'not connected to pool' bug that appeared in previous version (0.9.0)
+ Better auto setup values for eth/etc + alph 'dual' mining
+ Added a workaround for 'blake3_alephium' algorithm pools that send both set_difficulty and set target in job
+ Minor bug fixes

***
'--gpu-auto-tune 3' might help in finding good '--gpu-intensity' values when doing 'dual' mining.
Set your prioritized algorithm to algorithm 0 (ex. ETH + ALPH, not ALPH + ETH)

***
'dynamo' will have a lot of rejected shares with the message 'duplicate share'. That is because everyone is working on the same job. It's not a miner issue.

(note: 'dynamo' might be the most profitable thing to mine now on CPU)
hero member
Activity: 2548
Merit: 626
February 11, 2022, 08:06:23 AM
I can concur the "Not connected to a pool?" issue with the 0.9.0 where it never was a issue in previous versions.

It's kinda random, you need to restart the miner to fix it.

Other miners or instances might be fully functional while this new 0.9.0 build gives this message.

Yeah, i got a few reports. Already prepared a fix, it's under testing currently.
Pages:
Jump to: