Quote from: sereupin on June 24, 2018, 09:50:02 AM

sorry but what do you mean with "(to prevent crash when is lyra2v2 used)" and "new method Lyra2REv2" ?!

I don't understand...

I am using a watchdog usb hardware in case the rig goes on freezing... should I disable it ?!

thanks

ps: still not compatible with Awesome miner?

edit:

after few minutes it stopped to work again, i think while it connects to dev fees and the program still can't be closed!!! i can only reboot the rig now

update2:

I am trying the "-a lyra2v2-old" and from +610Mh/s, now it works at 570Mh/s ; I noticed that every GPU works at similar hashrate now, instead of earlier when 4 GPU were working at 80Mh/s and other 4 GPU were working slower as you can see in the screenshot

The last advice that I want to give you is to implement the difficult parameter.. when i start to mine, I waste around 4/5 minutes with refused results or thousands of little result before that the pool adjust slowly the miner with highter difficult number... it is not good and it is necessary to can put a fixed number of difficult

Sorry for the misunderstanding. In case if you have issues with the current implementation of Lyra2REv2 (lyra2v2), you might want to try lyra2v2-old
The built-in watchdog might conflict with a third-party watchdog. In that case, you could disable it
Awesome Miner will be available next week
Could you provide an example of a miner which provides "the difficult parameter"?