Ok, so looks like i finally resolved the ellesmere 8gb heavy algos thing.
Now they easily hash over 1.1khs.

New version in a few days

Da je to tako lako, vec bi odavno uradio 

ok, in global which version worked the best on those R7 370 pitcairns ?
Im asking because i can try to replace kernel 2 with that old one you say worked the best for you, and add all new algos without trying to mess up too much.

Also do you get compute errors on new SRB version on V7 too ?

Because V8 can make more compute errors, it's more 'sensitive' to overclocking and the strap you are using.
If i remember good you had a lot of compute errors even on 1.6.4

Intensity 56 is too low for V8, if im right you have a vega, so set it to :

intensity : 112
worksize: 16

something on your side is up

Do you get the same results with kernel 2?
which SRB version was best for your pitcairns?

Look at the fragments in 1.6.9 and 1.7.1.
Try using these in 1.7.1  :

GPU0 : F1
GPU1 : F1
GPU2 : F1
GPU3 : F1
GPU4 : F1
GPU5 : F16

Set in gpu_conf, you can see on the first page how.
Then come back here and tell me is it better.

For 560 4g try different settings for fragments, try 0,1,2,4,8, 9999 one of these should bring back the hash

its not if you configure it yourself and not use the auto settings

I could create a binary for pitcairn for kernel1 without problems. (stellite)
Here it is, try it : https://ufile.io/33ldw

Compiled with your settings :
Worksize : 8
Fragments : 0

You must set exact settings so the miner uses the binary i linked.

I am more curious why it reports 6 GPU's. You are not using every GPU in the machine in the config file?

ok, ok, you remember i connected a few times with teamviewer trying to help you even before v8.
you don't need to be sarcastic every time.

Better give me more info, something that can help me, so i can help you.
Upload part of log file where the build fails.

Also i want to know what hashrates you get on which card/algo.

I ran an offline compile of kernels and basically it could compile on every GCN, that means pitcairn also.

And now tell me do i need to fix anything, or not change anything ??

 
 

If you don't really want to play try :


"intensity" : 61,
"double_threads" : true,
"worksize" : 9,
"fragments" : 1,
"aes" : 0,
"bralock" : 32,
"heavy_mode" : 2

you got 370 2gb right?

Auto setup for freehaven is sh*t, i forgot to tune it, so it uses settings like for heaven, which is obviously bad.

For Vega try intensity 110, for other i dunno 

V1.7.1
- Added new algo FreeHaven
- Small OpenCL optimisations
- Added 3 different modes for heavy algos (Heavy, Haven, BitTube, Italo, FreeHaven)
- Added value '9999' for fragments, that sets internally to the value it was in previous 1.6.8 version
- Fixed benchmarking mode + startup monitor bug
- Fragments, aes, bralock and heavy_mode can be set now outside gpu_conf, so it applies to every GPU


- Freehaven algo is here, a lot of you were waiting for this
- Added new parameter "heavy_mode", it can be used in gpu_conf, or just in the config, it is applied if not in auto mode (intensity = 0).
It can be 1,2,3.
1: This is the default method for doing heavy calculations now, it's more stable and should produce less compute errors than in the previous 1.7.0 version. Note that worksize 9 isn't the optimal worksize anymore for Vegas if using this mode. Worksize 8 now gives better results, you just need to find a good value for intensity.

2: This is the calculation method from the previous 1.7.0 version, use it if you can get better results with it than with mode 1. Note for Vegas : worksize 9 is optimal here.

3: Experimental mode, it is the fastest but tends to produce the most compute errors, if your GPU's are tuned maximally to the edge. I put it here because maybe someone can get the best results with it.

- Ellesmere 8gb cards just love to throttle hashrate on heavy algos, lot of you said you had better results on previous versions, so if you set fragments to 9999 it uses the same internal settings for it used in 1.6.8.
I am sure with the new mode for heavy calculations higher hashrates can be achieved, but a lot of users just copy over the old settings and guess what, does are not optimal anymore.
With the new method you should lower the intensity a little bit than before, and find the right fragments setting for your GPU's. Some users reported they have higher hashrates after playing a little bit with these settings.

- I had to add parameters 'fragments', 'aes', 'bralock, and now 'heavy_mode' to the config file outside the 'gpu_conf' because.. well, nobody reads the first page or readme.txt anymore

You are missing a , after "double_threads" : true

Don't repeat, but read back. Try various values for 'fragments' parameter. Benchmark uses same config as normal mining.

It looks like that at the end 1.7.0 is better also with Ellesmere 8G cards than older SRB versions, just needs some fine tuning, as few users who played a little bit with fragments reported.
This is good to know.