Quote from: melloyellow on May 16, 2020, 09:23:50 PM

Quote from: melloyellow on May 16, 2020, 09:04:43 PM

Quote from: andrucrypt on May 16, 2020, 08:49:09 PM

Quote from: melloyellow on May 16, 2020, 08:41:04 PM

Quote from: andrucrypt on May 16, 2020, 08:36:40 PM

Quote from: melloyellow on May 16, 2020, 08:33:43 PM

Quote from: andrucrypt on May 16, 2020, 08:49:02 AM

0.24.0 beta
-added parameter --progpow-kernel(1 or 2 can give better hashrate on different drivers or gpu configuration)
-speedup ProgPow/KawPow up to 10% on pre-Navi gpu's

Compare different --progpow-kernel values(1 or 2) in benchmark(on KawPow add --benchmark --benchmark-epoch 170 on ProgPowZ try --benchmark --benchmark-epoch 17)

Kernel 2 is great for Vega 56's with 19.2 drivers around 19mh/s but I got too many Share Above Target rejects with Send Stale Shares activated. I turned send stale shares off and it seems to work fine. Is this expected behavior?

edit: As soon as I posted that, I started getting rejects for Share Above Target.

what pool it is? Difficulty?

Nicehash 256M

The rejects don't happen all the time. Could it be the person that 'rented' my hash pointed it to a bad pool?
Would a newer driver work better?

Looks I have found the reason. Job target should be all 256 bits, not just 64 bit I check. Will fix that in next release. But this is not critical, since miner shouldn't send this solutions anyway. What about drivers, I prefer good old one 18.3.4 or 18.6.1

I'm using 19.2 I don't think the miner is sending the solutions, it disconnects, then recompiles the kernel. Then the rejects start over again.

I think I misled you about the amount of rejects, it's pretty much all of them. I can't use kernel 2 at all the way it is now. I'm stuck using kernel 0 or 1 which give me about 14 mh/s. A hotfix would be greatly appreciated, you have the only public stable AMD kapow miner.

Hmmm, now this is too weird. Does this happen with pools or just NiceHash? And can you show logs or do you remember the diff that miner show near the "new job" message?

ps: testing here kernel 2 for more than hour on RX590 and drivers 20.2.1 on NiceHash and have no problems...