|
BIG UPDATE!
V0.8.1
+ Added algorithm 'firopow' (FIRO - Firo coin) for CPU/GPU mining, fee 0.85%
+ Added algorithm 'kawpow' (RVN - Raven coin) for CPU/GPU mining, fee 0.85%
+ Added algorithm 'progpow_sero' (SERO - Super Zero coin) for CPU/GPU mining, fee 0.85%
+ Added algorithm 'progpow_veil' (VEIL - Veil coin) for CPU/GPU mining, fee 0.85%
+ Added algorithm 'progpow_zano' (ZANO - Zano coin) for CPU/GPU mining, fee 0.85%
+ Added algorithm 'progpow_veriblock' (VBK- Veriblock coin) for CPU/GPU mining, fee 0.85%
+ Added algorithm 'progpow_epic' (EPIC - EpicCash coin) for CPU/GPU mining, fee 0.85%
+ Added algorithm 'astrobwt' (DERO - Dero coin) for CPU mining, fee 0.85%
+ Added algorithm 'minotaurx' (LCC - LiteCoin Cash coin) for CPU mining, fee 0.85%
+ Lowered devfee for 'lyra2v2_webchain' algorithm to 0.85%
+ Small improvements on 'autolykos2' algorithm for RX550 & RX560 GPU's
+ Added shares statistics per GPU ( accepted | rejected | gpu validation errors )
+ Added watchdog for CPU workers (detect if a cpu thread stops hashing)
+ Added parameter '--gpu-progpow-mode' (which progpow program to use)
+ Added parameter '--gpu-progpow-preload' (how many periods to pre-create)
+ Fixed crashing on Ryzen 3000 series CPU's on 'autolykos2' algorithm
+ Fixed compatibility with p2p-spb.xyz P2P pools
+ Fixed 'Internet not found' issue on some linux distributions
+ Changed default value for '--max-no-submit-responses' parameter from 0 to 5
+ Renamed parameter '--disable-gpu-watchdog' to '--disable-worker-watchdog'
+ Reduced miner binary size (Windows)
+ To fix miner disconnects on 'autolykos2' with 'WoolyPooly' pool, try --keepalive true
+ Minor bug fixes
- Progpow algos are using single DAG allocation (no split DAG), so you need a driver that allows allocation of large buffers.
- 'Dual' mine EpicCash Progpow with any other algorithm (ETHASH, ETCHASH, AUTOLYKOS2 ...)
- --gpu-progpow-mode is auto selected, but you can test manually, maybe you find a mode that works better for your GPU
|
|
|
|
|
Also has MinotaurX algorithm which is atm cpu only. Im going to add it soon to SRBMiner.
|
|
|
|
Hi, no 11MH + 11MH, 22 for both cards. Buuut, after many experiments with different drivers i found one which is the best - old Crimson Live Beta Blockchain drivers. Now i have - Srbmner: [2021-10-10 11:08:48] Difficulty 1.373976 [etchash][0]
[2021-10-10 11:08:48] Job received [0x297c4870f4602b224dcd31705fefc5] block height 13696949 [etchash][0]
[2021-10-10 11:08:48] Job received [0x297c4870f4602b224dcd31705fefc5] block height 13696949 [etchash][0]
[2021-10-10 11:08:48] [a0] [GPU0][t0] Auto tune started
[2021-10-10 11:08:48] [a0] [GPU1][t0] Auto tune started
[2021-10-10 11:09:00] GPU1 [BUS:03] 2847MB DAG created in 11980ms [etchash]
[2021-10-10 11:09:00] [GPU1][a0] Auto tune current hashrate thread0 : 10.49 MH/s
[2021-10-10 11:09:01] GPU0 [BUS:01] 2847MB DAG created in 12771ms [etchash]
[2021-10-10 11:09:01] [GPU0][a0] Auto tune current hashrate thread0 : 8694.08 kH/s
[2021-10-10 11:09:02] [GPU1][a0] Auto tune current hashrate thread0 : 13.48 MH/s
[2021-10-10 11:09:03] [GPU0][a0] Auto tune current hashrate thread0 : 10.26 MH/s
[2021-10-10 11:09:05] Applied boost value 8 to GPU worker 0 [BUS:01]
[2021-10-10 11:09:05] Applied boost value 8 to GPU worker 1 [BUS:03]
[2021-10-10 11:09:06] [a0] GPU0 auto tune result : --gpu-intensity 3899392
[2021-10-10 11:09:07] [GPU1][a0] Auto tune current hashrate thread0 : 14.08 MH/s
[2021-10-10 11:09:08] [a0] GPU1 auto tune result : --gpu-intensity 4937088
[2021-10-10 11:09:09] Job received [0x55b1b6b663aef071944a7ca7da69de] block height 13696950 [etchash][0]
[2021-10-10 11:09:25] ==========================================================
[2021-10-10 11:09:25] [0] [etchash]
[2021-10-10 11:09:25] GPU0 : 10.52 MH/s
[2021-10-10 11:09:25] GPU1 : 14.19 MH/s
[2021-10-10 11:09:25] Total: 24.72 MH/s Teamredminer: [2021-10-10 11:15:14] Mining ethash with 2 GPU workers
[2021-10-10 11:15:14] GPU PCIe CUs CoreMHz SocMHz MemMHz TEdge TJct TMem FanPct FanRpm VDDC Power ETH Cfg
[2021-10-10 11:15:14] 0 01:00.0 8 1070 0 1900 53C 0C 0C 35.00% 1692 0 mV 27 W A4294967264
[2021-10-10 11:15:14] 1 03:00.0 16 1083 0 1900 53C 0C 0C 40.00% 62 0 mV 36 W A138
[2021-10-10 11:15:14]
[2021-10-10 11:15:14] Stats Uptime: 0 days, 00:01:31
[2021-10-10 11:15:14] ----------------------------------------- GPU Status -------------------------------------------
[2021-10-10 11:15:14] GPU 0 [53C, fan 35%] ethash: 13.01Mh/s, avg 7.803Mh/s, pool 0.000 h/s a:0 r:0 hw:0
[2021-10-10 11:15:14] GPU 1 [53C, fan 40%] ethash: 13.42Mh/s, avg 9.792Mh/s, pool 44.47Mh/s a:1 r:0 hw:0
[2021-10-10 11:15:14] Total ethash: 26.44Mh/s, avg 17.60Mh/s, pool 44.47Mh/s a:1 r:0 hw:0
[2021-10-10 11:15:14] ----------------------------------------- Pool Status ------------------------------------------
[2021-10-10 11:15:14] eu1-etc.ethermine.org ethash: 25.68Mh/s, avg 17.14Mh/s, pool 44.37Mh/s a:1 r:0
[2021-10-10 11:15:14] ------------------------------------------------------------------------------------------------ Try without auto-tune, it can sometimes return much lower intensity than gpu could run fine with. |
|
|
|
Ok, looks like I fixed it - I install older drivers version - 21.5.1.
Now it works fine. But hashrate is very low - with latest driver i can make it work with Gminer
and it gives me 22 MH, now with 21.5.1 driver it gives me only 15 MH and 16 MH with srbminer.
22mhs with a rx560 ?  Try 18.6.1 driver, you got old cards, dont need to use latest drivers, you wont have any benefit. |
|
|
|
Example, with my 4 gb amd gpu mine Ergo, but it would be nice to mine ergo by default and when epic progpow time coming mine epic then back to ergo.
Coming soon  |
|
|
|
[2021-09-30 21:10:34] Found NUMA node id : 0
[2021-09-30 21:10:34] Miner version: 0.8.0
[2021-09-30 21:10:34] OS: windows
[2021-09-30 21:10:34] Windows version: 6.1 build 7601
[2021-09-30 21:10:34] Video driver version: 26.20.15029.27017
[2021-09-30 21:10:35] Found 1 OpenCL platform/s
[2021-09-30 21:10:35] Platform 0: Advanced Micro Devices, Inc.
[2021-09-30 21:10:35] Default OpenCL platform set to 0
[2021-09-30 21:10:35] Found 2 GPU device/s on platform 0
[2021-09-30 21:10:35] WMI API method failed
[2021-09-30 21:10:35] WMIC method failed
[2021-09-30 21:10:35] Gpu tweaking disabled
[2021-09-30 21:10:35] GPU0: radeon_rx550_550_series [gfx804 ][ 4096 MB][CU: 8][BUS: 01]
[2021-09-30 21:10:35] GPU1: radeon_rx_560_series [baffin ][ 4096 MB][CU: 16][BUS: 03]
[2021-09-30 21:10:35] ADL: enabled
[2021-09-30 21:10:35] Algorithm/s: verthash [1.00% fee]
[2021-09-30 21:10:35] Gpu mining: enabled
[2021-09-30 21:10:35] Cpu mining: disabled
[2021-09-30 21:10:35] Gpu tweaking: disabled
[2021-09-30 21:10:35] Gpu watchdog: enabled
[2021-09-30 21:10:36] Starting init of worker threads
[2021-09-30 21:10:36] A0|GPU0 | [BUS:01] [I: 65632]
[2021-09-30 21:10:36] A0|GPU1 | [BUS:03] [I: 65632]
[2021-09-30 21:10:36] Worker thread0 : GPU
[2021-09-30 21:10:36] Worker thread1 : GPU
[2021-09-30 21:10:36] AMD ADL initialised successfully! [2 devices]
[2021-09-30 21:10:36] Finished init of worker threads
[2021-09-30 21:10:36] HTTP API disabled
[2021-09-30 21:10:37] json_send[0][72]: {"id":1, "method":"mining.subscribe", "params":["SRBMiner-MULTI/0.8.0"]}
[2021-09-30 21:10:37] json_receive[0][161]: {"id":1,"result":[[["mining.set_difficulty","deadbeefcafebabef416000000000000"],["mining.notify","deadbeefcafebabef416000000000000"]],"27ffe98b",4],"error":null}
[2021-09-30 21:10:37] json_send[0][90]: {"id":2,"jsonrpc":"2.0","method":"mining.authorize","params":["********","******"]}
[2021-09-30 21:10:37] json_receive[0][59]: {"id":null,"method":"mining.set_difficulty","params":[0.1]}
[2021-09-30 21:10:37] Pool sent difficulty: 0.100000 [verthash]
[2021-09-30 21:10:37] json_receive[0][681]: {"id":null,"method":"mining.notify","params":["30ff","82bf590136b30bf233ccf4a1b378d08863275b4556c09cae8c6813548c17d731","01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff2003c207190492fd556108","0d2f6e6f64655374726174756d2f00000000020000000000000000266a24aa21a9ed5ceab4d1b09df6b3c329f7a2dc012045927420be975e7e27c0db81711ab3aeaceb7d2095000000001976a914e8bc1e74c9bd6dc0e70c3a983e63116fa627900288ac00000000",["a0a5ef6792c0cd9b974ca6a28bf862321fe0d53e3e05ead5785052ae9789cce1","940e83eb75a3fa5b4716fef8b40382937ae47d30eaff375bf0c453bc44a51aef","02adccfe8d727a4e35e3d03c57208ffda7b7f79a39d07e82d6cf1ab2aea6c9f1"],"20000000","1c024cc7","6155fd92",false]}
[2021-09-30 21:10:37] Difficulty 0.100000 [0]
[2021-09-30 21:10:37] Job received [30ff] block height 1640386 [0]
[2021-09-30 21:10:37] Allocated [1224 MB]
[2021-09-30 21:10:38] json_receive[0][35]: {"id":2,"result":true,"error":null}
[2021-09-30 21:10:38] Sent mining.extranonce.subscribe to pool [id:3] [verthash]
[2021-09-30 21:10:38] Connected to vtc.suprnova.cc:1775 [0]
[2021-09-30 21:10:39] Difficulty 0.100000 [0]
[2021-09-30 21:10:39] Job received [30ff] block height 1640386 [0]
[2021-09-30 21:10:44] E[2]
[2021-09-30 21:10:44] Worker thread 1 stopped
[2021-09-30 21:10:44] Worker thread 0 stopped
[2021-09-30 21:10:35] WMIC method failedIs that win7 home? I think home doesn't have WMI by default. |
|
|
|
@Doktor83, another one question - why tweaking not work for RX550/560 on windows 7? GPU0 : radeon_rx550_550_series [gfx804 ][MEM: 4096 MB][CU: 8][BUS: 01]
GPU1 : radeon_rx_560_series [baffin ][MEM: 4096 MB][CU: 16][BUS: 03]
======================================================================
SRBMiner-MULTI 0.8.0
Press 's' to display stats
Press 'h' to display hashrate
Press 'p' to switch to the next pool
Press 'o' to switch to the previous pool
Press 0-9 to disable/enable GPU 0-9, shift+0-9 for GPU 10-19
======================================================================
Algorithm/s : etchash [0.65% fee]
Gpu mining : enabled
Cpu mining : disabled
Gpu tweaking : disabled
Gpu watchdog : enabled
[2021-09-29 16:22:38] Gpu tweaking disabled Might be that winio driver can't be loaded. Enable log & --extended-log maybe it will tell more info about why tweaking got disabled |
|
|
|
If I run the miner in admin for msr_tweaks I started getting "NAUGHTY3" as response. What is this?
It means opencl.dll is in miner's run path, and it shouldn't be there. So if you have an opencl.dll in miner folder, delete it. Might be also that when you run it as admin the default run path is windows/system32, where this file normally resides. wasn't in miner directory but opencl.dll is present in wndows/system32. I thought this was a normal case? IT's normal that the file is there, but it's not normal that when you run an app as admin it uses windows/system32 as runpath, and not the app's folder. Maybe it depends on how you run it as admin, i never had this issue when testing on various machines, but someone reported and this is how we figured out the system32 thing. Try changing dir (cd) in .bat to miner folder before it invokes the .exe I will see if i can do something to fix this behaviour though. |
|
|
|
I have noticed a problem with version 0.8.0. I am getting a lot of LAG if I am browsing when mining, especialy if I watch any YT at the time. With version 0.7.3 it is fine.
You forgot to tell which GPU and which algorithm ? |
|
|
|
If I run the miner in admin for msr_tweaks I started getting "NAUGHTY3" as response. What is this?
It means opencl.dll is in miner's run path, and it shouldn't be there. So if you have an opencl.dll in miner folder, delete it. Might be also that when you run it as admin the default run path is windows/system32, where this file normally resides. |
|
|
|
Is SRBMiner-MULTI latest version supposed to be working on good old R9 280x cards? I see they are in the supported devices list, however any attempt to mine 'autolycos2' crashes the system badly, sometimes to the point where only hardware reset helps.
Tried to run it on HiveOS, both on a single card, and a bunch of them - no way, the miner works for some time, with extremely low hashrate on some cards, and with zero hash on others, then system freezes. The 'lolminer' works however (more or less stably), so its not rig issue... I just read somewhere SRBMiner should be better for those older cards, especially given the fact they are in supported device list...
Have you tried to manually tune the --gpu-intensity parameter? Or anything else beside just starting the miner with the default settings? Yep, sure, I did. Tried to run it with "--gpu-intensity 0", "--gpu-intensity 10", "--gpu-intensity 5", "--gpu-auto-tune 0", "--gpu-auto-tune 1"... No luck. First of all, it doesn't seem to pick up the intensity value I give it, while also doesn't completely ignore the parameter: if I don't set --gpu-intensity, the log shows intensity value of 32 takes effect; while when I set "--gpu-intensity 0", instead of 0 some other (higher than zero) parameter is used; when I set it to 5, I can see it is actually set as 17. Weird. As to "--gpu-auto-tune", it looks like when normal tuning procedure is started, it never ends - it works for some minutes, until GPU freezes. Though I did make some experiments, but didn't do too much of them (probably up to 10-15 attempts with different parameter combinations), because the rigs are remote, almost every such experiment brings it to hangup state, while my remote hardware reset procedure is somewhat complicated, so I just did experiments until my patience was exhausted... Then I came here to ask For that gpu a --gpu-intensity 22 for example should be ok. I don't have such an old card, so i couldn't test. But why isn't it 'picking up' the intensity value you set, i have no idea. Btw auto tune parameter values : 0-disabled, 1-normal, 2-fast Try --gpu-intensity 0 --gpu-auto-tune 2 , might do something useful. But if the intensity parameter isn't applied then there's not much use. |
|
|
|
Is SRBMiner-MULTI latest version supposed to be working on good old R9 280x cards? I see they are in the supported devices list, however any attempt to mine 'autolycos2' crashes the system badly, sometimes to the point where only hardware reset helps.
Tried to run it on HiveOS, both on a single card, and a bunch of them - no way, the miner works for some time, with extremely low hashrate on some cards, and with zero hash on others, then system freezes. The 'lolminer' works however (more or less stably), so its not rig issue... I just read somewhere SRBMiner should be better for those older cards, especially given the fact they are in supported device list...
Have you tried to manually tune the --gpu-intensity parameter? Or anything else beside just starting the miner with the default settings? |
|
|
|
1. Improved stratum implemenation that can boost the profit +5% poolside
 |
|
|
|
Does this fix the miner from completely exiting out of a bash script? I'm still having this issue. Been using a different miner until this is fixed.
Im not sure i can fix anything for you. Miner on SIGINT or SIGBREAK does a cleanup, shutdown and exits to shell, it's up to you what you do in your script after that. Mining distros like Hiveos, Mmpos, etc have no issues with the shutdown procedure... And you will prob. now say but other miners work normally [this is what people usually say]. |
|
|
|
V0.8.0
+ Added algorithm 'randomgrft' (GRFT - Graft coin) for CPU mining, fee 0.85%
+ Performance increase on 'ethash' algorithm for RX6800/6900 GPU's
+ Performance increase on 'etchash' algorithm for RX6800/6900 GPU's
+ Performance increase on 'ubqhash' algorithm for RX6800/6900 GPU's
+ Performance increase on 'verthash' algorithm for RX6800/6900 GPU's
+ Performance increase on 'heavyhash' algorithm for RX6800/6900 GPU's
+ Performance increase on 'autolykos2' algorithm on ZEN2+ AMD CPU's (up to ~90%) (*)
+ Fixed 'cryptonight_gpu' algorithm for RDNA/RDNA2 GPU's
+ Fixed 'cryptonight_xhv' algorithm for RDNA/RDNA2 GPU's
+ Added GPU power consumption details to stats & api
+ Decreased time needed for algorithm switch when using --multi-algorithm-job-mode 3 with cpu mining
+ Minor bug fixes
* - might apply to other AVX2 CPU's too - not tested
for navi cards -- ethash 080 bad 078 best Specifically which one? RX5700 ? |
|
|
|
|
V0.8.0
+ Added algorithm 'randomgrft' (GRFT - Graft coin) for CPU mining, fee 0.85%
+ Performance increase on 'ethash' algorithm for RX6800/6900 GPU's
+ Performance increase on 'etchash' algorithm for RX6800/6900 GPU's
+ Performance increase on 'ubqhash' algorithm for RX6800/6900 GPU's
+ Performance increase on 'verthash' algorithm for RX6800/6900 GPU's
+ Performance increase on 'heavyhash' algorithm for RX6800/6900 GPU's
+ Performance increase on 'autolykos2' algorithm on ZEN2+ AMD CPU's (up to ~90%) (*)
+ Fixed 'cryptonight_gpu' algorithm for RDNA/RDNA2 GPU's
+ Fixed 'cryptonight_xhv' algorithm for RDNA/RDNA2 GPU's
+ Added GPU power consumption details to stats & api
+ Decreased time needed for algorithm switch when using --multi-algorithm-job-mode 3 with cpu mining
+ Minor bug fixes
* - might apply to other AVX2 CPU's too - not tested
|
|
|
|
Do you wish to add support for 4000G or 5000G iGPU in the Miner?
list-gpu-devices says and lists the device but the Actual miner application just ignored it when trying to use it.
Said no Suitable GPU devices found?
Not something you wish to add? I was just curious what kind of performance one could get but could not start to even test.
I don't have a ryzen with an integrated gpu so i can't do much here. Do you need a device ID or something to add it in the code? I presume you have a list of approved GPU's or something for the miner to allow? Yeah, but you assume that its enough to allow a codename, and it will magically work You need sku specific optimization/code and such to be done? Bummer. It's supposed to be "VEGA", so was guessing it shouldn't have been too much work to do a test. But it's work, nonetheless. Will not bother to ask you more about it. I don't expect them to be any performance killers either. i could allow those codenames and set them to use gfx900 kernels for example, but i can't test it if it works. might work, who knows. And if it works, it would probably still be better if it was optimised specifically for that GPU, and not just use the gfx900 ones. |
|
|
|
Do you wish to add support for 4000G or 5000G iGPU in the Miner?
list-gpu-devices says and lists the device but the Actual miner application just ignored it when trying to use it.
Said no Suitable GPU devices found?
Not something you wish to add? I was just curious what kind of performance one could get but could not start to even test.
I don't have a ryzen with an integrated gpu so i can't do much here. Do you need a device ID or something to add it in the code? I presume you have a list of approved GPU's or something for the miner to allow? Yeah, but you assume that its enough to allow a codename, and it will magically work |
|
|
|
Do you wish to add support for 4000G or 5000G iGPU in the Miner?
list-gpu-devices says and lists the device but the Actual miner application just ignored it when trying to use it.
Said no Suitable GPU devices found?
Not something you wish to add? I was just curious what kind of performance one could get but could not start to even test.
I don't have a ryzen with an integrated gpu so i can't do much here. |
|
|
|
TeamRed miner is the best for me, I tried SRBminer and NBminer then I lost significant amount of hashrate using RX Vega 56 cards, I instantly went back to team red miner..
Teamred SRbminer NBminer
46MH 36MH 36MH with DAG error
you were doing something very wrong with SRBMiner. On ethash TRM isnt so much better. |
|
|
|
|
Show Posts
