Same result on 7 6x570 rig.
Topic: SRBMiner-MULTI GPU & CPU Miner 0.9.4 - page 58. (Read 44750 times)
Work fine on k12 for some hour and then crash. Clean win10 install 19.4.3 driver Adrenalin.
Same result on 7 6x570 rig.
Same result on 7 6x570 rig.
Doktor, can you compile win32 version of miner (at least for CPU algos)?
I can't sorry. The app i use to protect the binary is only x64
Doktor, can you compile win32 version of miner (at least for CPU algos)?
K12 is an old algo already available on FPGA no ?
It is. Just like a lot of algorithms
I've tested your new miner version on k12
it works well
this is just a testnet server right? I'm waiting the AEON fork, this is why I want be ready to mine on time
it works well
this is just a testnet server right? I'm waiting the AEON fork, this is why I want be ready to mine on time
Yes, this is just a testnet so you can test your cpu/gpu/fpga before the fork
K12 is an old algo already available on FPGA no ?
I've tested your new miner version on k12
it works well
this is just a testnet server right? I'm waiting the AEON fork, this is why I want be ready to mine on time
it works well
this is just a testnet server right? I'm waiting the AEON fork, this is why I want be ready to mine on time
V0.1.4 beta
+ Fixed a critical bug with work creation for fast algorithms [k12, keccak]
If you want to mine k12 or keccak algorithms with a rig, you should update to this version.
Also here are some numbers for K12, but on cards that used to mine ETH:
RX560 ~ 350 MHS [1180/1500]
RX470 ~ 790 MHS [1130/1900]
VEGA56 ~ 1770 MHS [1500/900]
You should absolutely raise core clock and lower mem clock to get more hash.
Test pool and address:
+ Fixed a critical bug with work creation for fast algorithms [k12, keccak]
If you want to mine k12 or keccak algorithms with a rig, you should update to this version.
Also here are some numbers for K12, but on cards that used to mine ETH:
RX560 ~ 350 MHS [1180/1500]
RX470 ~ 790 MHS [1130/1900]
VEGA56 ~ 1770 MHS [1500/900]
You should absolutely raise core clock and lower mem clock to get more hash.
Test pool and address:
Code:
{
"pool" : "162.210.173.150:4444",
"wallet" : "UmkHnTboxTobceosFgpM16CAkMZnwfqQCQrLY3zCZQLgEovYM72zpy21DjzS4vj8z3SrP3HWg6fKmSkcPz8oir5x1HDMQGKyn",
"password" : "x"
}
Ok, i found a bug in work creation, i just noticed this with the very fast K12 algo, where worker runs out of nonces very fast.
Fix incoming soon
Fix incoming soon
V0.1.3 beta
+ Keccak algorithm +15% faster on gpu
+ K12 algorithm +8-12% faster on gpu [vega56 ~1700mhs]
+ Guided setup got smarter a little bit
+ Keccak algorithm +15% faster on gpu
+ K12 algorithm +8-12% faster on gpu [vega56 ~1700mhs]
+ Guided setup got smarter a little bit
have you made some tests for K12 algo on RX 4xx/5xx 4/8gb also?
I'm asking cause I'm curious what clocks to use here
tnx
not really, but mem clock is not important, go as much high as you can with core clock
There is one testpool i know about : 162.210.173.150:4444
V0.1.3 beta
+ Keccak algorithm +15% faster on gpu
+ K12 algorithm +8-12% faster on gpu [vega56 ~1700mhs]
+ Guided setup got smarter a little bit
+ Keccak algorithm +15% faster on gpu
+ K12 algorithm +8-12% faster on gpu [vega56 ~1700mhs]
+ Guided setup got smarter a little bit
have you made some tests for K12 algo on RX 4xx/5xx 4/8gb also?
I'm asking cause I'm curious what clocks to use here
tnx
Thanks for supporting K12 on the fork for $AEON! If anyone wants additional support for Aeon please visit our Discord or IRC.
V0.1.3 beta
+ Keccak algorithm +15% faster on gpu
+ K12 algorithm +8-12% faster on gpu [vega56 ~1700mhs]
+ Guided setup got smarter a little bit
+ Keccak algorithm +15% faster on gpu
+ K12 algorithm +8-12% faster on gpu [vega56 ~1700mhs]
+ Guided setup got smarter a little bit
In guided-setup I can set only standart address 10-12 characters, but pools use id address
Noo, you can set up to 200 characters for wallet address in guided setup mode, so that should fit the wallet.payment-id format too.
I am happy that you have the best results with SRBMiner-MULTI
OK. I set config manually and start testing. DOK, you are great again) your miner more power effectively than NB or sparkminer. I have 346 Mh/sec from rx480 and less than 100 w from the wall)))
Hello, DOK) Could you fix using ckb accound adress? Most pools in test phase using it.
I don't understand what should be fixed? Tested on sparkpool and hashpool, both work.
In guided-setup I can set only standart address 10-12 characters, but pools use id address
Hello, DOK) Could you fix using ckb accound adress? Most pools in test phase using it.
I don't understand what should be fixed? Tested on sparkpool and hashpool, both work.
Hi Dok - thanks for all your hard work on SRB.
Quick question, just trying to understand why you said Cryptonite algo coins are slowly dying and why CN miner support is EOL (end of life)?
Cryptunit.com has many CN projects and they are all very active in development - just trying to understand your reasoning behind this decision, maybe you will re-think it and continue support, it is a great miner. CN algo is also very active with many projects, duno maybe I'm missing something here. Anyways just trying to understand. Thanks in advance!
Quick question, just trying to understand why you said Cryptonite algo coins are slowly dying and why CN miner support is EOL (end of life)?
Cryptunit.com has many CN projects and they are all very active in development - just trying to understand your reasoning behind this decision, maybe you will re-think it and continue support, it is a great miner. CN algo is also very active with many projects, duno maybe I'm missing something here. Anyways just trying to understand. Thanks in advance!
I think there won't be new CN variant algorithms anymore, probably a lot of old/new projects will follow the RandomX path. SRBMiner-CN is working with the existing algorithms, so any project that uses one of those could be mined with SRBMiner-CN.
If there will be any new CN variants though, i will consider adding them to the new MULTI miner. This one is an improved version of the old miner, i fixed a lot of bugs, added cpu mining support etc.
Hi Dok - thanks for all your hard work on SRB.
Quick question, just trying to understand why you said Cryptonite algo coins are slowly dying and why CN miner support is EOL (end of life)?
Cryptunit.com has many CN projects and they are all very active in development - just trying to understand your reasoning behind this decision, maybe you will re-think it and continue support, it is a great miner. CN algo is also very active with many projects, duno maybe I'm missing something here. Anyways just trying to understand. Thanks in advance!
Quick question, just trying to understand why you said Cryptonite algo coins are slowly dying and why CN miner support is EOL (end of life)?
Cryptunit.com has many CN projects and they are all very active in development - just trying to understand your reasoning behind this decision, maybe you will re-think it and continue support, it is a great miner. CN algo is also very active with many projects, duno maybe I'm missing something here. Anyways just trying to understand. Thanks in advance!
Hello, DOK) Could you fix using ckb accound adress? Most pools in test phase using it.
i like miners with different algos.
V0.1.2 beta
+ Added support for kangaroo12 algo [k12]
+ All algorithms that have a fee now have the same ~0.85% devfee
+ More bug fixes
Aeon will fork to k12 algo around Oct. 25th.
Unfortunately there are already FPGA bitstreams ready for this algo, but still, you should jump on GPU mining it at least a few days after the fork, cause it should be profitable.
Performance : ~1500MHS on Vega56 (40% faster than VulkanXMRMiner)
+ Added support for kangaroo12 algo [k12]
+ All algorithms that have a fee now have the same ~0.85% devfee
+ More bug fixes
Aeon will fork to k12 algo around Oct. 25th.
Unfortunately there are already FPGA bitstreams ready for this algo, but still, you should jump on GPU mining it at least a few days after the fork, cause it should be profitable.
Performance : ~1500MHS on Vega56 (40% faster than VulkanXMRMiner)
Jump to: