Topic: SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching - page 179. (Read 237247 times)

I supported you partly, in the sense that I do not agree with Dok's calculations, but for me it ends here.
@Dok: I honestly appreciate your complete openness on how the devfee is levied, you have put it in the release notes and explained it here. This works for me, thank you for your efforts in making this a great miner.

I do not argue with dev (with DEV I'm writing to PM).. I fight with idiots like you are.

Clowns are two here - some retards spamming topic with idiotic conclusion and arguing with author and other people. There are many here in this forum  ... just ignore, absolutely useless.

I love this so much. When I was questioning something regarding hashrate, I was made fun of by some guys. Now, the same guys become clowns because of fee 

yea. im smart but you stupid. why read my post? just ignore my post and be smart.

why ask this:
Go use other miner and stop ask

So you are the smart guy who found that fee is not 0.85% but 20%? Author must close topic immediately! We all are in big waiting for Your Gorgeous Miner with 0.86% fee (real) and few little minor bugs!

write config here

yвepeн чтo v7 включeнo? тaм oбычный aлгo y мoнeты

OR you dont read  my post if you angry where i ask why fee.......

or all stop ask why miner dont work with....(i dont read this- go use other miner)
or all stop ask why miner have bug in watchdog and GPU core clock....(i dont read this- go use other miner)
or all stop ask why miner not use forked coin...(i dont read this- go use other miner)
or stop post like :miner work better with driver 18.((i dont read this- go use other miner I want a smaller HR:)  )

mybe is best CLOSE this topic?? and nobody will ever ask anything and all happy?

I do not think that's good. And you?

hints:

if you go away intensity on zero it will play safe, so in lots of instances you can increase that value to get better outcomes
For higher consequences set double_threads to real, and depart intensity on zero
if you get an blunders that asserts it may’t create scratchpad buffer, you have to decrease depth
largest intensity placing gained’t usually come up with the great hashrate. experiment and discover the nice placing in your GPU.

realy. tnx. get v7 config and not change
rig work. tnx

Agree, do not use this miner if you don't like the fee ...use others or make your own miner.

The whole discussion about dev fee is hilarious. It works the way it works. If you mine 24hrs with SRBminer you'll pay 0.85%. If you auto-switch and hence turn in off and back on lots of times, you pay more fee. If you don't like it, suggest some improvement ideas to Doktor in a constructive way, or else, suck it up, basically.

Tnx, miner works, what about intensities and worksize? Now I am on 0 and 8 but seems not fast, both two card are mining slower than my older Tahitis.

Maybe You are idiot here and not set "cryptonight_type" : "mox" in config?

check again
GPU0: AMD Radeon R9 200 Series [Hawaii] [8192 MB][Intensity 46.0][W: 8][T: 2][K: 2][BUS: 7]
GPU1: AMD Radeon R9 200 Series [Hawaii] [4096 MB][Intensity 43.0][W: 8][T: 2][K: 2][BUS: 8]
GPU2: AMD Radeon R9 200 Series [Hawaii] [4096 MB][Intensity 43.0][W: 8][T: 2][K: 2][BUS: 6]

[2018-08-04 11:47:55] Connected to crypto9coin.cf:62477
[2018-08-04 11:47:55] User logged in
[2018-08-04 11:47:55] Pool difficulty: 22222
[2018-08-04 11:47:55] Pool sent a new job (ID: 385523145366460)
[2018-08-04 11:48:02] Pool rejected result 0x0002826B (rejected share: invalid result)
[2018-08-04 11:48:03] Pool rejected result 0x000182FF (rejected share: invalid result)
[2018-08-04 11:48:05] Pool rejected result 0x00004895 (rejected share: invalid result)

log
[2018-08-04 11:50:13] hashrate: GPU0: 0 H/s [BUS:7]
[2018-08-04 11:50:13] hashrate: GPU1: 0 H/s [BUS:8]
[2018-08-04 11:50:13] hashrate: GPU2: 0 H/s [BUS:6]
[2018-08-04 11:50:13] hashrate: Total: 0 H/s
[2018-08-04 11:50:15] miner_result: Sending user result to pool
[2018-08-04 11:50:15] json_send: {"id":1,"jsonrpc": "2.0","method":"submit","params":{"id":"511865336680784","job_id":"118325158976949","nonce":"7f28c771","result":"95c64bcff0d41710a97ffad0aa7c65daaa8bbec5085e8cc0739967e3b6970200"}}
[2018-08-04 11:50:15] json_receive: {"id":1,"jsonrpc":"2.0","error":{"code":-1,"message":"Rejected share: invalid result"}}
[2018-08-04 11:50:15] miner_result: Pool rejected result 0x000297B6 (rejected share: invalid result)
[2018-08-04 11:50:16] miner_result: Sending user result to pool
[2018-08-04 11:50:16] json_send: {"id":1,"jsonrpc": "2.0","method":"submit","params":{"id":"511865336680784","job_id":"118325158976949","nonce":"157f1cc7","result":"c769157260fe9d1ff1f6e39e552b827fdbe1730ed09db9779fa21dbe83bf0100"}}
[2018-08-04 11:50:17] json_receive: {"id":1,"jsonrpc":"2.0","error":{"code":-1,"message":"Rejected share: invalid result"}}
[2018-08-04 11:50:17] miner_result: Pool rejected result 0x0001BF83 (rejected share: invalid result)
[2018-08-04 11:50:19] Stopping miner process

I can't reproduce it, tried on a few rigs and kernel 2 everywhere works on mox algo.

mox
100% rejected
crypto9coin.cf

on v7 work fine with kernel 1

No, first says you think i am bad at math, but no matter how you calculate 0.85% of 86400 is always the same, and it is 734.
Now how do i divide those 734 seconds in the fee mining is my decision, is it 1x734 seconds or divided into 30 fee minings its still 0.85%.

I decided how it should be used, if you use it any way other than that, its your business, accept the consequences of it. (if it is 6% than it is 6% because you did not use it the way it was projected - like when you step on the gas pedal, the car uses more gasoline than the factory projected)

You see up there in the gpus line it says K:1, that means its using kernel 1, not kernel 2. You must set gpu_conf in config.txt and there you set kernel/card

tongas should use k1, the r9 200 should use k2

Guys... if you don't like the way the dev fee works move to some other miner.
Dok just ignore everyone complaining about the dev fee.