@claymore Do we already have a fix for the issue where some of the cards hashes normally while the rest gives their OC hashes?
This is giving me problems right now as I have 8 Nitros and 5 of then hash 30.5 while the other three only manages 25.5.
Minspeed argument doesn’t work for me as it gives bsod to my miner and crashes it.
It would’ve been nice to have all cards hashing as expected upon startup.
This issue is not related to the miner, it is related to ADL library. Can you overclock all cards correctly with AfterBurner? |
|
|
|
Claymore, what about Pitcairn bugs? With -dmem 1 too much incorrect shares. Without -dmem 1 speed less than 9.7. Power consumption in 10.2 is less - it's better than 9.7.
Yes I can confirm this issue, it will take some time to fix it, it's something related to this chip only. |
|
|
|
|
I've just uploaded v10.2 for Linux.
|
|
|
|
@Claymore, Hi! Is it possible to add support for older cards? HD Series 69xx
v10 supports only ASM mode, so old cards are not supported, also RX550 is not supported currently. I can add non-ASM mode but it will work slowly, so it's better to use v9.7 for cards that are not supported by v10. |
|
|
|
v10.0 BETA:
- now miner uses the latest framework which is used for dual and zec miners. Therefore several new options are available.
- new assembler GPU kernels are used.
- added "-dmem" options that can improve performance in many cases. Note that twice more GPU memory is used in this mode.
- some old options were removed, some were renamed, please read Readme for detailed information and samples.
- reduced devfee, it's 1% now if you use secure SSL/TLS connection, 1.5% for unsecure connection.
- devfee mining is executed every hour, similar to dual and zec miners.
- a lot of minor improvements.
PS. Linux version will be available in a day.
After two weeks of waiting patiently... I'm on a trip (unexpected), I'm sorry for the delay with Linux version. I will be back in two days and will release Linux version asap. |
|
|
|
|
v10.2 BETA:
- added Nicehash pool support.
- added shares validation on CPU and statistics for incorrect shares.
|
|
|
|
hey claymore first of all thanks for your work...
i´ve tried out the new version vs sgminer & xmr stak amd...sorry bro but it is still not good enough at least for rx 580 8gb
restults
xmr stak + sgminer ~5500h/s - 650 watts from the wall---6*rx580 8gb @2gpu threads
claymore 10.0 ~5200h/s with dmem 1 - 650-680 watts from the wall(jumps between 650 - 680) ~5000h/s with dmem 0 and 650watts from the wall +dev fee
im not greedy and i dont care about 1% fee, but like all miners i have to look whats most profitable...
your miner with 1 gpu thread is nearly so fast like sgminer+xmrstak with 2 threads....im no coder or developer and i dont know shit about it, but if its somehow possible think about to implement mining with 2 gpu threads and your miner could the fastest ...
Don't worry, v11 will be better, I just need some time  |
|
|
|
It works now with stock settings but you didn't solve the Nicehash problem.
Because I need more time for it. |
|
|
|
AMD rx550 not work  no ASM binary found  Yes currently only popular cards are supported: Pitcairn, Tahiti, Hawaii, Fiji, Tonga, Ellesmere, Baffin, Vega. I will add other cards but a bit later. |
|
|
|
|
IF YOU USE V10.0 - UPDATE TO V10.1.
- fixed some critical bugs.
|
|
|
|
Why I get
"DevFee: failed to mine for a long time, something is wrong, "nofee" mode is enabled until successful devfee mining."
It's a bug. I've removed v10.0 and will upload v10.1 in a few minutes. I made too many changes in this version, bugs are quite possible. |
|
|
|
Version 10 not compatible with nicehash , unsecure and ssl connection always reject shares with error "..invalid nonce ... is it nicehash comapatible.. " 9.7 was working fine ?
I will check it. |
|
|
|
|
This version is not so easy to use because you have to adjust "-h" and "-dmem" values often, I will try to improve it soon.
1. "-dmem 1" requires twice more memory, make sure you have enough virtual memory. For example, if you have 6 GPUs 8GB, set virtual memory to 6*8=48GB.
2. Check how much memory miner allocates, it shows something like "(Memory used: 5128MB)", make sure you have this memory on your GPU.
3. You can see low hashrate if you use almost all memory on GPU, try to reduce "-h" value a bit.
|
|
|
|
|
v10.0 BETA:
- now miner uses the latest framework which is used for dual and zec miners. Therefore several new options are available.
- new assembler GPU kernels are used.
- added "-dmem" options that can improve performance in many cases. Note that twice more GPU memory is used in this mode.
- some old options were removed, some were renamed, please read Readme for detailed information and samples.
- reduced devfee, it's 1% now if you use secure SSL/TLS connection, 1.5% for unsecure connection.
- devfee mining is executed every hour, similar to dual and zec miners.
- a lot of minor improvements.
PS. Linux version will be available in a day.
|
|
|
|
Hey claymore lets tell us whats the speed for vega 56 and 64
I don't OC GPUs and use stock bios, don't enable HBCC, etc, so I get low speeds. For example, I see 1140H/s for stock Vega64. That's bad. You'll see 2-thread gain with HBCC only ((( HBCC can be enabled easy with blockchain drivers. But if you have Frontier - that is a problem )) For HBCC enabled with Vega56 or Vega64 be sure you have enough virtual memory, make clean uninstall of drivers (I used amd utiity), install blockchain drivers again, you will see HBCC slider in Gaming section Hmm, Vega56 shows about 1400H/s in stock. So it seems Vega56 is faster than Vega64 for my PoW implementation. I really need more time to find the reason, so I will release new version in several hours and then will spend more time for Vega. It can be that you Vega64 is throttling in stock setting. Try to set fans to the max ))) Vega64 is not a card to run at stock ))))))))))))))) And please - provide more flexibility to tune your miner for the end user. We need possibility to run it multi-threaded! Rebooted PC, now drivers show 64 CUs for Vega56 instead of 56 and the speed is only 1100 due to unknown reason... I will include "-h" option to select the number of hashes and "-dmem" to enable double sized memory mode (it's not two threads but it processes two set of hashes at once so it's similar), it works good for Polaris and earlier cards, but Vega is some kind of magic. |
|
|
|
Hey claymore lets tell us whats the speed for vega 56 and 64
I don't OC GPUs and use stock bios, don't enable HBCC, etc, so I get low speeds. For example, I see 1140H/s for stock Vega64. That's bad. You'll see 2-thread gain with HBCC only ((( HBCC can be enabled easy with blockchain drivers. But if you have Frontier - that is a problem )) For HBCC enabled with Vega56 or Vega64 be sure you have enough virtual memory, make clean uninstall of drivers (I used amd utiity), install blockchain drivers again, you will see HBCC slider in Gaming section Hmm, Vega56 shows about 1400H/s in stock. So it seems Vega56 is faster than Vega64 for my PoW implementation. I really need more time to find the reason, so I will release new version in several hours and then will spend more time for Vega. |
|
|
|
Hey claymore lets tell us whats the speed for vega 56 and 64
I don't OC GPUs and use stock bios, don't enable HBCC, etc, so I get low speeds. For example, I see 1140H/s for stock Vega64. That's bad. You'll see 2-thread gain with HBCC only ((( HBCC can be enabled easy with blockchain drivers. But if you have Frontier - that is a problem )) For HBCC enabled with Vega56 or Vega64 be sure you have enough virtual memory, make clean uninstall of drivers (I used amd utiity), install blockchain drivers again, you will see HBCC slider in Gaming section Yeah I use "amdcleanuputility", then install "Win10-64Bit-Crimson-ReLive-Beta-Blockchain-Workloads-Aug23". And I don't have control panel for GPU settings at all. Manually started "RadeonSettings.exe" shows errors about missed QT libs, copying them don't help, it shows another error, etc. Probably I need to reinstall Windows, but I don't have time for that right now. I remember a day when I used Windows7 and could not find "Gaming Mode" button, spent at least half a day and then found that this button is in Windows10 only, for some unknown reason... Don't want to spend another day like that. |
|
|
|
Hey claymore lets tell us whats the speed for vega 56 and 64
I don't OC GPUs and use stock bios, don't enable HBCC, etc, so I get low speeds. For example, I see 1140H/s for stock Vega64. |
|
|
|
What is the expected speed for Vega? Can't wait )))
It's just a bit faster than sgminer in my tests, my be you will get different results. The problem of this PoW is in GPU memory, so all tricks don't help much. To get full Vega speed you need HBCC enabled and 2 or more threads with total memory usage ascending to the upper limit. Will hope your miner let us configure threads and intensities. We need do break 2kh/s wall )) I use different approach, so I get best speed in a single thread, two threads have same speed. I did not try HBCC yet since I test everything on blockchain drivers and I don't see any dialogs with settings at all. |
|
|
|
Finally I have fixed the bug with Vega.
New version will be available within 24 hours.
Also I will reduce devfee and it will be executed once an hour, similar to dual and zec miners.
Linux will get an update as well? Or holding back on it for now? Yes I will release Linux version too. Though Vega won't work in Linux, currently I don't support ROCm drivers. What is the expected speed for Vega? Can't wait ))) It's just a bit faster than sgminer in my tests, may be you will get different results. The problem of this PoW is in GPU memory, so all tricks don't help much. |
|
|
|
|
Show Posts
