Topic: SRBMiner-MULTI GPU & CPU Miner 0.9.4 - page 19. (Read 44491 times)
Mining Bamboo (https://bitcointalksearch.org/topic/m.60808933 , https://discord.gg/tNKcfjWttj ) on my RX5600 and it runs nice, but my Ryzen7 3800X is much better, so I think that CPU is for the time much better option. Thank you for your work
Is there any option to control power consumption on AMD cards in miner, without me having to resort to manual adjustment in Catalyst Driver or Bios Mod?
Mem clocks? Core Clocks? Power Limit?
Here, in my case, this is essential.
Tks...
Try OverdriveNTool. Mem clocks? Core Clocks? Power Limit?
Here, in my case, this is essential.
Tks...
V1.0.8
+ Added algorithm 'blake3_ironfish' (IRONFISH coin) for CPU/GPU mining, fee 0.85% *
+ Added ETHASH/ETCHASH + BLAKE3_IRONFISH dual mining mode
+ Added AUTOLYKOS2 + BLAKE3_IRONFISH dual mining mode
+ Added algorithm 'pufferfish2bmb' for RDNA cards [ 5xxx ]
+ Performance increase on 'autolykos2' algorithm for RX5700/XT GPU's
+ Small performance increase on 'kaspa' algorithm for RDNA cards [ 5xxx ]
+ Algorithm 'autolykos2' possible fix for situation when miner isn't creating dataset
+ Algorithm 'autolykos2' now uses 1 thread per GPU as default (was 2) - hashrate should be more stable
+ Possible fix for miner crashing when it's trying to reconnect to the pool
***
Algorithm 'blake3_ironfish' stratum implementation does not send back a message to the miner if share was accepted/rejected, so
you won't have statistics about this in the miner - only how many shares were sent to the pool.
Tested on zk.work pool.
Ironfish is at the moment running at an incentivized testnet.
+ Added algorithm 'blake3_ironfish' (IRONFISH coin) for CPU/GPU mining, fee 0.85% *
+ Added ETHASH/ETCHASH + BLAKE3_IRONFISH dual mining mode
+ Added AUTOLYKOS2 + BLAKE3_IRONFISH dual mining mode
+ Added algorithm 'pufferfish2bmb' for RDNA cards [ 5xxx ]
+ Performance increase on 'autolykos2' algorithm for RX5700/XT GPU's
+ Small performance increase on 'kaspa' algorithm for RDNA cards [ 5xxx ]
+ Algorithm 'autolykos2' possible fix for situation when miner isn't creating dataset
+ Algorithm 'autolykos2' now uses 1 thread per GPU as default (was 2) - hashrate should be more stable
+ Possible fix for miner crashing when it's trying to reconnect to the pool
***
Algorithm 'blake3_ironfish' stratum implementation does not send back a message to the miner if share was accepted/rejected, so
you won't have statistics about this in the miner - only how many shares were sent to the pool.
Tested on zk.work pool.
Ironfish is at the moment running at an incentivized testnet.
Thanks for your hard work guys.
Question: Today I downloaded the latest version and in the help.bat I don't see the commands for API statistics. In my bat from previous versions (0.8.0) the commands were --api-enable --api-port
What is the command for the new version of SRB?
Question: Today I downloaded the latest version and in the help.bat I don't see the commands for API statistics. In my bat from previous versions (0.8.0) the commands were --api-enable --api-port
What is the command for the new version of SRB?
Stil the same.
Run xmrig --help from terminal or command line.
Thanks for your hard work guys.
Question: Today I downloaded the latest version and in the help.bat I don't see the commands for API statistics. In my bat from previous versions (0.8.0) the commands were --api-enable --api-port
What is the command for the new version of SRB?
Question: Today I downloaded the latest version and in the help.bat I don't see the commands for API statistics. In my bat from previous versions (0.8.0) the commands were --api-enable --api-port
What is the command for the new version of SRB?
V1.0.7
+ Added algorithm 'pufferfish2bmb' (BMB - Bamboo) for GPU mining [ rdna2 only ], fee 1.00%
+ Small performance increase on 'pufferfish2bmb' algorithm for CPU's
+ Reduced devfee for 'autolykos2' (ERGO) to 1.00%
+ Possible fix for 'Can't switch to algorithm 1' issue when using --multi-algorithm-job-mode 3
+ Bug fixes
+ Added algorithm 'pufferfish2bmb' (BMB - Bamboo) for GPU mining [ rdna2 only ], fee 1.00%
+ Small performance increase on 'pufferfish2bmb' algorithm for CPU's
+ Reduced devfee for 'autolykos2' (ERGO) to 1.00%
+ Possible fix for 'Can't switch to algorithm 1' issue when using --multi-algorithm-job-mode 3
+ Bug fixes
i tried to mine kawpow algorithm from my r5 m330 but there is no support for my card. I have an old gpu and I would like to take advantage of it, could you help me?
I tried to mine bitcoin but I know it's crazy to do it from a graphics card. I don't understand why only r9 cards and not r5 I just want compatible software for my r5 gpu it would be something interesting.
I tried to mine bitcoin but I know it's crazy to do it from a graphics card. I don't understand why only r9 cards and not r5 I just want compatible software for my r5 gpu it would be something interesting.
Your laptop graphics card only has 2GB memory as stated on https://www.techpowerup.com/gpu-specs/radeon-r5-m330.c2681
Might be the reason.
i tried to mine kawpow algorithm from my r5 m330 but there is no support for my card. I have an old gpu and I would like to take advantage of it, could you help me?
I tried to mine bitcoin but I know it's crazy to do it from a graphics card. I don't understand why only r9 cards and not r5 I just want compatible software for my r5 gpu it would be something interesting.
I tried to mine bitcoin but I know it's crazy to do it from a graphics card. I don't understand why only r9 cards and not r5 I just want compatible software for my r5 gpu it would be something interesting.
Is there any option to control power consumption on AMD cards in miner, without me having to resort to manual adjustment in Catalyst Driver or Bios Mod?
Mem clocks? Core Clocks? Power Limit?
Here, in my case, this is essential.
Tks...
Mem clocks? Core Clocks? Power Limit?
Here, in my case, this is essential.
Tks...
I just started a cpu mining today and I'm currently mining Raptoreum using my Ryzen 5 3400GE, but I only got 76-170H/s is this hashrate is okay in my ryzen 5 or Am I missing something, by the way, I also currntly using cpu miner, and I want to try SRBminer and I just want to see the difference.
Have you optimize your RAM and setting the core speed? [1] this will increase and make your hashrate more stable, there's a lot gap betwee 76 to 170H/s even in this site [2] the hashrate is around 189H/s.You can try it, it doesn't difficult to set up SRBMiner since there's a tutorial on the main thread.
[1] https://www.nicehash.com/blog/post/how-to-optimize-cpu-mining-performance-for-monero-random-x
[2] https://www.hashrates.com/cpus/amd-ryzen-5-pro-3400ge-w-radeon-vega-graphics-8-3.30/
Thanks for answering my query, very long time since I stopped GPU mining, that's why I'm totally noob again and have no idea on the latest update on the mining tools that are using today. I will try to do that bro, again, Thanks.
I just started a cpu mining today and I'm currently mining Raptoreum using my Ryzen 5 3400GE, but I only got 76-170H/s is this hashrate is okay in my ryzen 5 or Am I missing something, by the way, I also currntly using cpu miner, and I want to try SRBminer and I just want to see the difference.
Have you optimize your RAM and setting the core speed? [1] this will increase and make your hashrate more stable, there's a lot gap betwee 76 to 170H/s even in this site [2] the hashrate is around 189H/s.You can try it, it doesn't difficult to set up SRBMiner since there's a tutorial on the main thread.
[1] https://www.nicehash.com/blog/post/how-to-optimize-cpu-mining-performance-for-monero-random-x
[2] https://www.hashrates.com/cpus/amd-ryzen-5-pro-3400ge-w-radeon-vega-graphics-8-3.30/
I just started a cpu mining today and I'm currently mining Raptoreum using my Ryzen 5 3400GE, but I only got 76-170H/s is this hashrate is okay in my ryzen 5 or Am I missing something, by the way, I also currntly using cpu miner, and I want to try SRBminer and I just want to see the difference.
V1.0.6
+ Added algorithm 'pufferfish2bmb' (BMB - Bamboo) for CPU mining, fee 1.00%*
+ Algorithm 'xdag' is now compatible with the new XDAGj network protocol
***
Algorithm 'pufferfish2bmb' stratum implementation supported only ( ffmpool.com )
+ Added algorithm 'pufferfish2bmb' (BMB - Bamboo) for CPU mining, fee 1.00%*
+ Algorithm 'xdag' is now compatible with the new XDAGj network protocol
***
Algorithm 'pufferfish2bmb' stratum implementation supported only ( ffmpool.com )
V1.0.5
+ Added algorithm 'sha512_256d_radiant' (RAD - Radiant Layer One) for CPU/GPU mining, fee 1.00%
+ Added ETHASH/ETCHASH + SHA512_256D_RADIANT dual mining mode
+ Added AUTOLYKOS2 + SHA512_256D_RADIANT dual mining mode
+ Fixed issue with dual mining ethash using nicehash mode
+ Added automatic caching of ZIL DAG in dual mining mode [ETH/ETC] (if GPU has enough VRAM to hold both DAG's)
+ Added parameter '--gpu-ethash-dag-cache' to set caching of specific ETH/ETC epoch in dual mining mode [ def. is epoch 0 - ZIL ]
+ Added algorithm 'sha512_256d_radiant' (RAD - Radiant Layer One) for CPU/GPU mining, fee 1.00%
+ Added ETHASH/ETCHASH + SHA512_256D_RADIANT dual mining mode
+ Added AUTOLYKOS2 + SHA512_256D_RADIANT dual mining mode
+ Fixed issue with dual mining ethash using nicehash mode
+ Added automatic caching of ZIL DAG in dual mining mode [ETH/ETC] (if GPU has enough VRAM to hold both DAG's)
+ Added parameter '--gpu-ethash-dag-cache' to set caching of specific ETH/ETC epoch in dual mining mode [ def. is epoch 0 - ZIL ]
104 version consumes one to two percent more power on RDN-RDN2 graphics cards than 103
Is there a possibility to add extra threads for dual mining algorithms?
I noticed it was limited to 1 thread per algo when dual-mining.
For example I want 2threads for ETH/ETC and then one thread for HEAVYHASH.
--gpu-intensity 20+20;10 for example ignored the second thread for ETC/ETH. Only used the first value per algo.
I noticed it was limited to 1 thread per algo when dual-mining.
For example I want 2threads for ETH/ETC and then one thread for HEAVYHASH.
--gpu-intensity 20+20;10 for example ignored the second thread for ETC/ETH. Only used the first value per algo.
That's not possible.
Is there a possibility to add extra threads for dual mining algorithms?
I noticed it was limited to 1 thread per algo when dual-mining.
For example I want 2threads for ETH/ETC and then one thread for HEAVYHASH.
--gpu-intensity 20+20;10 for example ignored the second thread for ETC/ETH. Only used the first value per algo.
I noticed it was limited to 1 thread per algo when dual-mining.
For example I want 2threads for ETH/ETC and then one thread for HEAVYHASH.
--gpu-intensity 20+20;10 for example ignored the second thread for ETC/ETH. Only used the first value per algo.
V1.0.4
+ Improved performance on all dual mineable algorithms for RDNA2 GPU's
+ Minor bug fixes
+ Improved performance on all dual mineable algorithms for RDNA2 GPU's
+ Minor bug fixes
What about KASPA solo mining ?
... solo+tcp://127.0.0.1 doesn't work on my node ..
... solo+tcp://127.0.0.1 doesn't work on my node ..
Same as for every other algorithm, stratum only.
V1.0.3
+ Added algorithm 'mike' (Vkax coin) for CPU mining, fee 0.85%
+ Significantly improved performance on 'curvehash' algorithm for GPU's
+ Reduced devfee for 'kaspa' and 'heavyhash' to 0.85%
+ Using any of the supported dual mining combinations, automatically enables auto tune
+ Added possibility to disable an algorithm in dual mining mode per GPU*
+ Default value for '--gpu-dual-max-loss' is lowered from 5% to 3%*
***
It is now possible to disable one of the algorithms in dual mining mode per GPU.
--gpu-id ETHASH_GPUS;KASPA_GPUS [separator between GPU's is !, as usual]
For example you have a 4 GPU rig and want to dual mine ETH+KAS on GPU's 0,1,3 and ETH only on GPU 2 (without KAS) :
--gpu-id 0!1!2!3;0!1!3
***
--gpu-dual-max-loss parameter should be used to set the ratio between the hashrates of the two algorithms in dual mining mode.
Lower value gives higher priority to the first algorithm (ETH/ETC/AUTOLYKOS2).
As always, GPU CORE clock affects the effectiveness of this parameter. Sometimes a slightly higher CORE clock can make a big difference.
+ Added algorithm 'mike' (Vkax coin) for CPU mining, fee 0.85%
+ Significantly improved performance on 'curvehash' algorithm for GPU's
+ Reduced devfee for 'kaspa' and 'heavyhash' to 0.85%
+ Using any of the supported dual mining combinations, automatically enables auto tune
+ Added possibility to disable an algorithm in dual mining mode per GPU*
+ Default value for '--gpu-dual-max-loss' is lowered from 5% to 3%*
***
It is now possible to disable one of the algorithms in dual mining mode per GPU.
--gpu-id ETHASH_GPUS;KASPA_GPUS [separator between GPU's is !, as usual]
For example you have a 4 GPU rig and want to dual mine ETH+KAS on GPU's 0,1,3 and ETH only on GPU 2 (without KAS) :
--gpu-id 0!1!2!3;0!1!3
***
--gpu-dual-max-loss parameter should be used to set the ratio between the hashrates of the two algorithms in dual mining mode.
Lower value gives higher priority to the first algorithm (ETH/ETC/AUTOLYKOS2).
As always, GPU CORE clock affects the effectiveness of this parameter. Sometimes a slightly higher CORE clock can make a big difference.
Jump to: