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

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...  

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.

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 )

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 ]

104 version consumes one to two percent more power on RDN-RDN2 graphics cards than 103

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.

V1.0.4
+ Improved performance on all dual mineable algorithms for RDNA2 GPU's
+ Minor bug fixes

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.

What about KASPA solo mining ?
... solo+tcp://127.0.0.1 doesn't work on my node ..

Devfee is mined on a different connection, not the same you are connected to the pool. Also you won't see any devfee shares sent on the screen/log - it's not displayed to the user.
What happened in your case that i don't know, but i am almost certain it's wasn't mining to my devfee wallet. There are also a few mechanisms that abort devfee mining if it might get stuck.

i think there is some bug in stbminer, that it forget to switch back to user pool and will be mining to developers wallet until miner is restarted. I have seen this problem a few times, 1-2 times every 1-2 months. Right now i have 21 cpus mining 2 different coins. Rigs are not local, some of them controlled with vnc. Two days ago one cpu worker dissappeared from pool, but i see that this rig is alive and gpus are online and working fine, just cpu worker is missing. Just got here and i see same problem as before - srbminer is running fine and shares sent all the time, but not to my wallet. Closed srbminer and run again - i see my worker on zergpool again as before. Version is 0.9.8, but i had same problem with previous versions.

Use lolminer if you want to mine KAS for example. But in my opinion it is not worth, if KAS not rise in price next time, i think it will die slowly. Profits so low

let's we give him one fury for tests...

 
Read the instructions, it is always added:

V1.0.0

+ Added ETHASH/ETCHASH + BLAKE3_ALEPHIUM dual mining mode
+ Added AUTOLYKOS2 + BLAKE3_ALEPHIUM dual mining mode
+ Fixed ETHASH/ETCHASH + KASPA mining on nicehash
+ Added parameter '--gpu-table-slow-build' which slows down DAG/Datatable creation for ETHASH/ETCHASH/UBQHASH/PROGPOW/AUTOLYKOS2 algorithms (might help in avoiding crash)
+ Parameter '--gpu-dual-mode' isn't needed anymore, miner will auto check if selected algorithms are eligible for dual mining
+ Fixed a few bugs related to dual mining mode

Dual mining tips:

Same as before, it is important to follow this simple rule:

If you increase CORE clock of the GPU because you want higher hashrate on A1 (KASPA/ALEPHIUM), you probably should also increase intensity of the SECOND algorithm too!
Not doing so might leave you on the same hashrate even if you increased the CORE clock!

Example:

Leave intensity of A0 on auto, and set intensity of A1 to 4 : --gpu-intensity 0 --gpu-intensity 4 , or --gpu-intensity 0;4

Dual ethereum/alephium example:

--disable-cpu --algorithm ethash --algorithm blake3_alephium --pool ethereum-pool-here --pool alephium-pool-here --wallet ethereum-wallet-here --wallet alephium-wallet-here

Dual ergo/alephium example:

--disable-cpu --algorithm autolykos2 --algorithm kaspa --pool ergo-pool-here --pool alephium-pool-here --wallet ergo-wallet-here --wallet alephium-wallet-here


Support for old gpu´s was dropped in version 0.9.5 (read the changes) because doktor has nothing for tests.

what a f..k man? Where are support for fiji? in many algos they still strong, one example its 23mh on kawpow and many other. many years we works with your miner

Hi.
Do you have plans to add 'ethash + blake3b' ?
Membercash, not a bad coin on blake3b https://bitcointalksearch.org/topic/--5399940