My miner show constant hashrate about 1kH/s, but on miner statistics average hashrate is 20% lower:
Current Hash Rate: 883.00 H/sec
Average 1 Hour Hash Rate: 832.80 H/s
Average 6 Hour Hash Rate: 855.33 H/s
Average 24 Hour Hash Rate: 814.48 H/s
Why?
Topic: SRBMiner-MULTI GPU & CPU Miner 0.9.4 - page 36. (Read 44491 times)
issue with Ergo auto difficulty adjuster.
Join Ergo discord to learn more.
Things should get better soon when their diff . adjusting starts working.
and yet - how to make "max difficulty" work? can an example? Join Ergo discord to learn more.
Things should get better soon when their diff . adjusting starts working.
Hi, Doktor, looks like srbminer can't mine Ergo anymore after difficulty adjusted.
It's your GPU's that are slow to create dataset in time + issue with Ergo auto difficulty adjuster.
Join Ergo discord to learn more.
Things should get better soon when their diff . adjusting starts working.
Hi, Doktor, looks like srbminer can't mine Ergo anymore after difficulty adjusted.
yap, i have a same problem.srb and nanominer cant mine ergo after diff adjust.
Hi, Doktor, looks like srbminer can't mine Ergo anymore after difficulty adjusted.
V0.6.7
+ Performance increase on 'autolykos2' algorithm on GPU's
+ Devfee increased on 'autolykos2' algorithm from 1.25% to 2.00%
+ Ethash - added 1 or 2 buffer mode for DAG (manually set with --gpu-ethash-mode, check Help\Cmd_Gpu_Parameters.txt)
+ Minor bug fixes
- Changed the way how --gpu-ethash-mode parameter works : on newer video drivers 20.4.x+, DAG can be allocated in one buffer, this can lower your power consumption a little bit.
Miner detects if allocation of big buffer is possible, but if you want to set it manually use --gpu-ethash-mode 1 ( 1 buffer for DAG ), or --gpu-ethash-mode 2 ( 2 buffers for DAG )
+ Performance increase on 'autolykos2' algorithm on GPU's
+ Devfee increased on 'autolykos2' algorithm from 1.25% to 2.00%
+ Ethash - added 1 or 2 buffer mode for DAG (manually set with --gpu-ethash-mode, check Help\Cmd_Gpu_Parameters.txt)
+ Minor bug fixes
- Changed the way how --gpu-ethash-mode parameter works : on newer video drivers 20.4.x+, DAG can be allocated in one buffer, this can lower your power consumption a little bit.
Miner detects if allocation of big buffer is possible, but if you want to set it manually use --gpu-ethash-mode 1 ( 1 buffer for DAG ), or --gpu-ethash-mode 2 ( 2 buffers for DAG )
Hi, @Doktor83. Is it possible to add Verthash for GPU and CPU mining?
Possible it is, but i not sure i am going to, depends on my free time.
Hi, @Doktor83. Is it possible to add Verthash for GPU and CPU mining?
Hi doctor83.
i have problem to mine ERGO (srb version 0.6.6) with 2 VEGA-64-LC (8 GB). It is not possible to mine more than 18 hours. After this time the cards need an reboot, because they can't reinit with a new instance -> mining stops.
Can you look. i know such problems when using timer (seconds clock) with only 16 bit resolution -> 16,8 hours -> overflow.
My driver version is 20.10.35.02 with HBCC ON (max) -> 2x230 Watt -> 225 MH (woolypool).
Thanks.
i have problem to mine ERGO (srb version 0.6.6) with 2 VEGA-64-LC (8 GB). It is not possible to mine more than 18 hours. After this time the cards need an reboot, because they can't reinit with a new instance -> mining stops.
Can you look. i know such problems when using timer (seconds clock) with only 16 bit resolution -> 16,8 hours -> overflow.
My driver version is 20.10.35.02 with HBCC ON (max) -> 2x230 Watt -> 225 MH (woolypool).
Thanks.
There is no problem with any timer or anything like that, i have uptimes of 40+ days
0.6.6 version has 2 threads / gpu for default, maybe that's what your vegas dont like, try --gpu-intensity 24, it's running 1 thread only.
Hi doktor83,
Found an issue: Incorrect count of avg hashrate.
On my rig (6*rx480) example:
2 cards are died for some reason:
actual hashrate:
[2021-02-12 19:27:44] GPU0: 60.58 MH/s
[2021-02-12 19:27:44] GPU1: 63.86 MH/s
[2021-02-12 19:27:44] GPU2: 62.44 MH/s
[2021-02-12 19:27:44] GPU5: 69.83 MH/s
[2021-02-12 19:27:44] Total: 256.71 MH/s
But:
[2021-02-12 19:27:49] Avg. 1 min. : 379.61 MH/s
[2021-02-12 19:27:49] Avg. 5 min. : 374.77 MH/s
[2021-02-12 19:27:49] Avg. 15 min. : 375.71 MH/s
10 min later:
[2021-02-12 19:37:25] Avg. 1 min. : 376.24 MH/s
[2021-02-12 19:37:25] Avg. 5 min. : 374.24 MH/s
[2021-02-12 19:37:25] Avg. 15 min. : 374.30 MH/s
Thanks
Found an issue: Incorrect count of avg hashrate.
On my rig (6*rx480) example:
2 cards are died for some reason:
actual hashrate:
[2021-02-12 19:27:44] GPU0: 60.58 MH/s
[2021-02-12 19:27:44] GPU1: 63.86 MH/s
[2021-02-12 19:27:44] GPU2: 62.44 MH/s
[2021-02-12 19:27:44] GPU5: 69.83 MH/s
[2021-02-12 19:27:44] Total: 256.71 MH/s
But:
[2021-02-12 19:27:49] Avg. 1 min. : 379.61 MH/s
[2021-02-12 19:27:49] Avg. 5 min. : 374.77 MH/s
[2021-02-12 19:27:49] Avg. 15 min. : 375.71 MH/s
10 min later:
[2021-02-12 19:37:25] Avg. 1 min. : 376.24 MH/s
[2021-02-12 19:37:25] Avg. 5 min. : 374.24 MH/s
[2021-02-12 19:37:25] Avg. 15 min. : 374.30 MH/s
Thanks
Thanks for reporting, going to check it out
Hi doctor83.
i have problem to mine ERGO (srb version 0.6.6) with 2 VEGA-64-LC (8 GB). It is not possible to mine more than 18 hours. After this time the cards need an reboot, because they can't reinit with a new instance -> mining stops.
Can you look. i know such problems when using timer (seconds clock) with only 16 bit resolution -> 16,8 hours -> overflow.
My driver version is 20.10.35.02 with HBCC ON (max) -> 2x230 Watt -> 225 MH (woolypool).
Thanks.
i have problem to mine ERGO (srb version 0.6.6) with 2 VEGA-64-LC (8 GB). It is not possible to mine more than 18 hours. After this time the cards need an reboot, because they can't reinit with a new instance -> mining stops.
Can you look. i know such problems when using timer (seconds clock) with only 16 bit resolution -> 16,8 hours -> overflow.
My driver version is 20.10.35.02 with HBCC ON (max) -> 2x230 Watt -> 225 MH (woolypool).
Thanks.
Hi doktor83,
Found an issue: Incorrect count of avg hashrate.
On my rig (6*rx480) example:
2 cards are died for some reason:
actual hashrate:
[2021-02-12 19:27:44] GPU0: 60.58 MH/s
[2021-02-12 19:27:44] GPU1: 63.86 MH/s
[2021-02-12 19:27:44] GPU2: 62.44 MH/s
[2021-02-12 19:27:44] GPU5: 69.83 MH/s
[2021-02-12 19:27:44] Total: 256.71 MH/s
But:
[2021-02-12 19:27:49] Avg. 1 min. : 379.61 MH/s
[2021-02-12 19:27:49] Avg. 5 min. : 374.77 MH/s
[2021-02-12 19:27:49] Avg. 15 min. : 375.71 MH/s
10 min later:
[2021-02-12 19:37:25] Avg. 1 min. : 376.24 MH/s
[2021-02-12 19:37:25] Avg. 5 min. : 374.24 MH/s
[2021-02-12 19:37:25] Avg. 15 min. : 374.30 MH/s
Thanks
Found an issue: Incorrect count of avg hashrate.
On my rig (6*rx480) example:
2 cards are died for some reason:
actual hashrate:
[2021-02-12 19:27:44] GPU0: 60.58 MH/s
[2021-02-12 19:27:44] GPU1: 63.86 MH/s
[2021-02-12 19:27:44] GPU2: 62.44 MH/s
[2021-02-12 19:27:44] GPU5: 69.83 MH/s
[2021-02-12 19:27:44] Total: 256.71 MH/s
But:
[2021-02-12 19:27:49] Avg. 1 min. : 379.61 MH/s
[2021-02-12 19:27:49] Avg. 5 min. : 374.77 MH/s
[2021-02-12 19:27:49] Avg. 15 min. : 375.71 MH/s
10 min later:
[2021-02-12 19:37:25] Avg. 1 min. : 376.24 MH/s
[2021-02-12 19:37:25] Avg. 5 min. : 374.24 MH/s
[2021-02-12 19:37:25] Avg. 15 min. : 374.30 MH/s
Thanks
Please help,
I use SRBMiner-Multi 0.6.5 for mining Haven (XHV) coin on haven.herominers.com.
After some time an error occurred: "couldn't connect to a devfee pool for a long time ... pause mining"
After that I have to restart the miner to continue working.
I use SRBMiner-Multi 0.6.5 for mining Haven (XHV) coin on haven.herominers.com.
After some time an error occurred: "couldn't connect to a devfee pool for a long time ... pause mining"
After that I have to restart the miner to continue working.
Your firewall/antivirus is blockin miner from accessing the devfee pool probably
When the miner connects to devfee pool and what is its address?
The firewall/antivirus should not be a problem because it leaks properly haven.herominers.com.
V0.6.5
+ Huge performance increase on 'autolykos2' algorithm on GPU's (up to ~600%)
+ Huge performance increase on 'autolykos2' algorithm on CPU's with AVX2 (up to ~500%)
+ Added abort mechanism for 'autolykos2' dataset creation on CPU
+ Huge performance increase on 'autolykos2' algorithm on GPU's (up to ~600%)
+ Huge performance increase on 'autolykos2' algorithm on CPU's with AVX2 (up to ~500%)
+ Added abort mechanism for 'autolykos2' dataset creation on CPU
Hey Doc! Hugs you man and tnx a lot for such good work!
Have two qestions:
1. i test two days - MULTI vs 1.9.4 on Haven on four rigs(8 cards RX470).
For MULTI i try some gpu tweak profiles and boost ...(boost 15, tweak 3 is better ... BUT --->>> Still 1.9.4 on custom GPU config works better. (faster, get more shares in short time)
Can you approve this?
2. Is there any command in 1.9.4 miner to start numbering GPU from 1 (not 0)?
Thank you.
1. I think at poolside MULTI should show a little bit better results if you find all the tweaks/boosts and make GPU's work stable
2. Nope
Please help,
I use SRBMiner-Multi 0.6.5 for mining Haven (XHV) coin on haven.herominers.com.
After some time an error occurred: "couldn't connect to a devfee pool for a long time ... pause mining"
After that I have to restart the miner to continue working.
I use SRBMiner-Multi 0.6.5 for mining Haven (XHV) coin on haven.herominers.com.
After some time an error occurred: "couldn't connect to a devfee pool for a long time ... pause mining"
After that I have to restart the miner to continue working.
Your firewall/antivirus is blockin miner from accessing the devfee pool probably
i'm using a few different cpus so i figured it out something to do with us.fastpool.xyz:3338 it gives me rejected shares (incorrect extranounce2 size) or doesn't find shares but if i connect to just fastpool.xyz it works fine, but your version 6.2 works with us.fastpool.xyz super strange
could you test us.fastpool.xyz:3338 and see if you get rejected shares... and curious part is if i use 6.2 it works with us.fastpool.xyz:3338
could you test us.fastpool.xyz:3338 and see if you get rejected shares... and curious part is if i use 6.2 it works with us.fastpool.xyz:3338
All good on latest version at us.fastpool.xyz:3338
V0.6.5
+ Huge performance increase on 'autolykos2' algorithm on GPU's (up to ~600%)
+ Huge performance increase on 'autolykos2' algorithm on CPU's with AVX2 (up to ~500%)
+ Added abort mechanism for 'autolykos2' dataset creation on CPU
+ Huge performance increase on 'autolykos2' algorithm on GPU's (up to ~600%)
+ Huge performance increase on 'autolykos2' algorithm on CPU's with AVX2 (up to ~500%)
+ Added abort mechanism for 'autolykos2' dataset creation on CPU
Hey Doc! Hugs you man and tnx a lot for such good work!
Have two qestions:
1. i test two days - MULTI vs 1.9.4 on Haven on four rigs(8 cards RX470).
For MULTI i try some gpu tweak profiles and boost ...(boost 15, tweak 3 is better ... BUT --->>> Still 1.9.4 on custom GPU config works better. (faster, get more shares in short time)
Can you approve this?
2. Is there any command in 1.9.4 miner to start numbering GPU from 1 (not 0)?
Thank you.
066 ergo coin
windows 20.11.2
rate 50%/ miner restart not restore rate/ only rig reboot
windows 20.11.2
rate 50%/ miner restart not restore rate/ only rig reboot
Please help,
I use SRBMiner-Multi 0.6.5 for mining Haven (XHV) coin on haven.herominers.com.
After some time an error occurred: "couldn't connect to a devfee pool for a long time ... pause mining"
After that I have to restart the miner to continue working.
I use SRBMiner-Multi 0.6.5 for mining Haven (XHV) coin on haven.herominers.com.
After some time an error occurred: "couldn't connect to a devfee pool for a long time ... pause mining"
After that I have to restart the miner to continue working.
i'm using a few different cpus so i figured it out something to do with us.fastpool.xyz:3338 it gives me rejected shares (incorrect extranounce2 size) or doesn't find shares but if i connect to just fastpool.xyz it works fine, but your version 6.2 works with us.fastpool.xyz super strange
could you test us.fastpool.xyz:3338 and see if you get rejected shares... and curious part is if i use 6.2 it works with us.fastpool.xyz:3338
could you test us.fastpool.xyz:3338 and see if you get rejected shares... and curious part is if i use 6.2 it works with us.fastpool.xyz:3338
Jump to: