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

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.

Why not? The more algos then more dev fee =)

No, im not interested in adding any of those. Eventually i will look into peach, i never heard about it before.

Hi, Dok! How about to add cockutoo/cuckaroo, peach and equihash 150,5, lyra2z330 algos for cpu and gpu?

Coin devs are working on fixing the duplicate share issue.

Yeah the pool issue is now fixed in 0.9.1 

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.

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)

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

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.

Yesterday updated from 0.8.9 to 0.9.0 and already had same problem twise in 12h. Did not had any problems with any previous versions:

[2022-02-09 22:38:44] Job received [e1ed] [verushash][0]
[2022-02-09 22:38:59] CPU result accepted      [  236ms] [verushash][0]
[2022-02-09 22:39:29] CPU result accepted      [  219ms] [verushash][0]
[2022-02-09 22:40:05] Job received [e1ee] [verushash][0]
[2022-02-09 22:40:36] ==========================================================
[2022-02-09 22:40:36] Not connected to a pool ?
[2022-02-09 22:40:36] ==========================================================
[2022-02-09 22:44:28] ==========================================================
[2022-02-09 22:44:28] Not connected to a pool ?
[2022-02-09 22:44:28] ==========================================================
[2022-02-09 22:48:07] ==========================================================
[2022-02-09 22:48:07] Not connected to a pool ?
[2022-02-09 22:48:07] ==========================================================
[2022-02-09 22:50:30] ==========================================================
[2022-02-09 22:50:30] Not connected to a pool ?
[2022-02-09 22:50:30] ==========================================================
[2022-02-09 22:53:17] ==========================================================
[2022-02-09 22:53:17] Not connected to a pool ?
[2022-02-09 22:53:17] ==========================================================
[2022-02-09 22:55:22] ==========================================================
[2022-02-09 22:55:22] Not connected to a pool ?
[2022-02-09 22:55:22] ==========================================================
[2022-02-09 22:57:40] ==========================================================
[2022-02-09 22:57:40] Not connected to a pool ?
[2022-02-09 22:57:40] ==========================================================
[2022-02-09 23:00:07] ==========================================================
[2022-02-09 23:00:07] Not connected to a pool ?
[2022-02-09 23:00:07] ==========================================================
[2022-02-09 23:00:14] Internal error: 0x2003

Restarting miner...

Win10, amd 3900x.
T-rex is running 24h on same rig and it did not see any problems with internet, same with other rigs with 0.8.9 still working fine (same pool). Going to downgrade to previous version.

You can come to my discord channel if you need support.
Miner shows a similar message when it isn't connected to the pool it's trying to switch to.
And don't always worry about the devfee pools, if miner can't connect to them you will get notified.

Not only me. After some time miner start to show message about it can't switch to second algo pool and work only on 1-st algo.
0.8.9 works fine. Maybe miner cant connect to some dev fee pools.

i can't because you gave 0 hints about the issue you are having

Hi, Doktor. Looks like last version dual mining or dev mining switch is broken. Please check it.

V0.9.0
+ Added algorithm 'blake3_alephium' (ALPH - Alephium coin) for CPU/GPU mining, fee 1.00%
+ Added algorithm 'xdag' (XDAG - Dagger coin) for CPU mining, fee 1.00%
+ Fixed broken 'yespower' algorithms (broke in previous 0.8.9 version)
+ Rewrote miner restarting mechanism on Windows
+ Removed algorithm 'rx2'
+ Bug fixes

***
You can use --worker parameter to set worker name when mining 'xdag' algorithm

***
Because Alephium doesn't have a unified stratum implementation, pools created their own implementations.
I added Herominers and WoolyPooly's implementation, other pools are not guaranteed to work as expected.
Herominers should be preferred because it uses the least network traffic between pool-miner.

You can 'dual' mine 'blake3_alephium' with any other algorithm you like.
Good combinations are : ethash + alph or etchash + alph.
You will need to adapt --gpu-intensity values manually for best results.

hello doctor83.
this cosanta thing is very interesting
i have intel cpu (about 40 haswel xeons) and amd cpu (eight ryzens like 3600, 3900 and 3950).
im not getting any hashrate boost on amd cpu with msr on cosanta
i try msr preset and msr tweak separate and together

i think this is because your software auto load best amd ryzen msr settings.
so there is nothing i can do with amd to increase hash (these cpus already hot and sweaty like a gym person)

so for amd i need faster clock ? yes?
the sweaty smell is too much though i need a bigger gym with more windows or close the gym and buy
big meat freezer. ah yes cold and no sweaties.
thank you from manchester where we mine like sweaty gymsters

---

not a newbie.had this conversation before.  manage a crap ton of rigs (60 plus now??)
£30,000 of crypto nicked - could put that story on youtube
this place would still say im a newbie
when the crypto is nicked - you grow up.

srb with cosanta looks INTERESTING

hello doctor83
thank you doctor - your software rocks- its not messing with the ethereum minings

Hi, doktor83! Can you please add zhash algos (125/144/192)?

With latest release, I don't get MSR tweaking on 5800x. On 5900x & 6700k it is activated. Normal or bug?

V0.8.9
+ Added algorithm 'randoml' (LOZZ - Lozzax coin) for CPU mining, fee 0.85%
+ Performance increase on 'ghostrider' algorithm with dynamic thread management
+ Performance increase on 'verushash' algorithm for CPU's with AES
+ Performance increase on 'scryptn2' algorithm
+ MSR tweaks are now allowed for every CPU mineable algorithm
+ Dataset for 'autolykos2' algorithm is now created differently, so hopefully video driver won't time-out on slower gpu's
+ Added file Help\Tdr_Fix\tdr_fix.reg for Windows, to increase driver time-out value (helps with DAG/dataset creation)
+ Removed algorithm 'eaglesong'
+ Removed algorithm 'kadena'
+ Removed algorithm 'bl2bsha3'
+ Removed algorithm 'phi5'
+ Removed algorithm 'cryptonight_cache'
+ Removed algorithm 'cryptonight_heavyx'
+ Minor bug fixes


***
Dynamic thread management for 'ghostrider' algorithm works only if you leave it on auto setup (don't set --cpu-threads or --cpu-threads-intensity parameter)

***
'scryptn2' added values 4, 8, 12, 16 for --cpu-threads-intensity. This parameter sets how many hashes to do per worker thread.
--cpu-threads-intensity parameter can accept values per thread if needed, so you can set different number of hashes per thread for every worker thread!
This can further increase the hashrate, if you find the right settings for your system.

Examples:
--cpu-threads 16 --cpu-threads-intensity 16 (uses 16 CPU threads, every thread does 16 hashes)
--cpu-threads 16 --cpu-threads-intensity 8!8!8!8!8!8!8!8!12!12!12!12!12!12!12!12 (uses 16 CPU threads, threads 0..7 do 8 hashes per thread, threads 8..15 do 12 hashes per thread)

It's harder to troubleshoot when using Hive.
Miner probably restarts because those GPU's are dead / didn't start working, so it triggers restart procedure.
Are all 12 gpu's same ? (5700xt)
Screenshot of miner shows GPU0,1,2,3 are the ones that didn't create a DAG.