SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching - page 142.

doktor83

hero member

Activity: 2548

Merit: 626

Quote from: N2DCRYPT on October 09, 2018, 03:18:45 PM

Quote from: doktor83 on October 09, 2018, 12:30:01 AM

Quote from: N2DCRYPT on October 08, 2018, 07:41:22 PM

Nice Dok! Can confirm ~2035 H/s for a V64 on V8. ~2135 H/s on current V7. V8 Only works using your pre-compiled kernels though. Running 18.6.1 drivers which are recommended, strange that they can't compile for V8. Just wanted to pass the info along, thx for all your wonderful work, best CN miner in my book by a long shot!

Do you get an error when trying to compile, or ?

Dok, I apologize, was wrong. I simply did not wait long enough. V8 takes longer to compile on a V64 than the other versions. But can verify that the kernel can be compiled on a V64 with the 18.6.1 drivers!

No problem, thanks

N2DCRYPT

jr. member

Activity: 148

Merit: 5

Quote from: doktor83 on October 09, 2018, 12:30:01 AM

Quote from: N2DCRYPT on October 08, 2018, 07:41:22 PM

Nice Dok! Can confirm ~2035 H/s for a V64 on V8. ~2135 H/s on current V7. V8 Only works using your pre-compiled kernels though. Running 18.6.1 drivers which are recommended, strange that they can't compile for V8. Just wanted to pass the info along, thx for all your wonderful work, best CN miner in my book by a long shot!

Do you get an error when trying to compile, or ?

Dok, I apologize, was wrong. I simply did not wait long enough. V8 takes longer to compile on a V64 than the other versions. But can verify that the kernel can be compiled on a V64 with the 18.6.1 drivers!

JJF

newbie

Activity: 42

Merit: 0

Quote from: doktor83 on October 09, 2018, 02:29:27 PM

@JJF

Ok, i will try to solve the R9 290 problem somehow.

Which kernel works on 1.6.7 ?
Also which settings did you use?

Both kernels - 1 and 2 - works fine with R9 290 on 1.6.7. With almost the same speed.
And I use default settings with one addition - ADL type should be 2 for correct detection

For example, the miner automatically detects my R9 290 for stellitev4 as:

Quote

GPU5: AMD Radeon R9 200 Series [Hawaii] [4096 MB][Intensity 42.0][W: 8][T: 2][K: 2][BUS: 4]

So, I've added in conf file the following setting for this card:

Quote

{ "id" : 5, "intensity" : 0, "worksize" : 8, "threads" : 2, "adl_type" : 2, "kernel" : 2}

And it works fine.
Also, if I decide to change kernel from 2 to 1 - it will work fine too with the same hashrate.

ZaGMaN

newbie

Activity: 4

Merit: 0

doktor83
limit of 2 personal messages per day )

Quote

Do you have any other cards, maybe some oldies like r9 290 ? Smiley

no, i have only R9 380

doktor83

hero member

Activity: 2548

Merit: 626

I managed to make kernel 1 work with R7 370 cards, thanks to ZaGMaN.
Hashrate is let's call it decent, but it will work on V8 too.

Tomorrow i will upload 1.6.8 fixed for this.
I guess it should work also on Pitcairn, Tahiti and Oland too.

@JJF

Ok, i will try to solve the R9 290 problem somehow.

Which kernel works on 1.6.7 ?
Also which settings did you use?

JJF

newbie

Activity: 42

Merit: 0

Quote from: doktor83 on October 09, 2018, 01:23:26 AM

Quote from: caki2004 on October 08, 2018, 10:51:36 PM

Could anyone help me,when i start the miner with my r9 290 i get the following error:

[2018-10-09 14:48:01] Error CL_LINK_PROGRAM_FAILURE when calling clLinkProgram [ctx->Program] for DeviceID 0 (Thread 0)
[2018-10-09 14:48:01] Error CL_INVALID_PROGRAM when calling clGetProgramBuildInfo for length of build log output for DeviceID 0 (Thread 0)

On top where you have something like : GPU0: Radeon RX 580 Series [ellesmere] [8192 MB][Intensity 56.0][W: 8][T: 2][K: 1][BUS: 2]

What do you have, [K: 1] or [K: 2] ?

Also driver version?

I've tried both kernels. On both, I have the same error (just as quoted) when compiling the kernel for R290:

Quote

Error CL_LINK_PROGRAM_FAILURE when calling clLinkProgram [ctx->Program] for DeviceID 5 (Thread 10)
Error CL_INVALID_PROGRAM when calling clGetProgramBuildInfo for length of build log output for DeviceID 5 (Thread 10)
Error initing GPU's. Stopping miner process

Driver version is 18.6.1.
SRBMiner v1.6.7 works fine, with no errors at this card.

heavyarms1912

full member

Activity: 729

Merit: 114

Quote from: doktor83 on October 09, 2018, 12:36:02 PM

I am developing always on 18.6.1, but i test on various drivers, 18.5.1 , and 18.5.2 work equally good , i don't know about the power consumption i never measure that.

yea 18.5.1,18.5.2 work similar to 18.6.1. I have tried 18.9.3 and results were similar too.

doktor83

hero member

Activity: 2548

Merit: 626

Quote from: tvukoman on October 09, 2018, 11:48:37 AM

Quote from: doktor83 on October 09, 2018, 07:24:45 AM

OK, so after testing with 18.3.4 and V8 here is the conclusion :

Don't use 18.3.4 if you want to mine V8!

It's something in the V8 code that driver doesn't like, and probably not something i can fix.
I will put this info on the first page.

Txs Doktor! That is my problem with small H/s on Vega and 18.3.4 Grin

So, you tested V8 with 18.6.1 and 18.5.1, for Vega 56 is one of these two drivers make better H/s?

I am developing always on 18.6.1, but i test on various drivers, 18.5.1 , and 18.5.2 work equally good , i don't know about the power consumption i never measure that.

tvukoman

jr. member

Activity: 69

Merit: 5

Quote from: doktor83 on October 09, 2018, 07:24:45 AM

OK, so after testing with 18.3.4 and V8 here is the conclusion :

Don't use 18.3.4 if you want to mine V8!

It's something in the V8 code that driver doesn't like, and probably not something i can fix.
I will put this info on the first page.

Txs Doktor! That is my problem with small H/s on Vega and 18.3.4 Grin

So, you tested V8 with 18.6.1 and 18.5.1, for Vega 56 is one of these two drivers make better H/s?

abg00

jr. member

Activity: 288

Merit: 1

Quote from: doktor83 on October 09, 2018, 10:52:05 AM

Is this also happening on v 1.6.7 ?

return to 1.6.7 and wait too
same trouble on two rig rx570\micron 8gb cn-heavy

18.3.4 is more stable and high rate then 18.6.1

abg00

jr. member

Activity: 288

Merit: 1

Quote from: StaL89 on October 09, 2018, 10:07:10 AM

Haпишитe ecли нe cлoжнo кaкиe y вac 550? пaмять? и ecли oчeнь нe cлoжнo тaйминги)

pm to you not alowed. this topic not for card modifed. i have lot of different card with different memory

a тaйминги пoд paзныe кapты paзныe. пишитe в личкy вoпpocы

Xameleon07

newbie

Activity: 7

Merit: 0

Hello. Does not open srbmener 168 on win10 1803? how to fix thank you?

zafa

newbie

Activity: 136

Merit: 0

Quote from: doktor83 on October 09, 2018, 10:52:05 AM

Quote from: zafa on October 09, 2018, 10:50:04 AM

Hello doktor83

I have 1 rig 10 x RX570 8GB and 18.6.1 driver.
My OC settings: 1250 - 2130 - 925 mv
Intens: 56
Double threads on
All cards have same ram (Micron), and bios.

My problem is about hashrates, Some cards are constantly running at low hashrate. I wait about an hour the result does not change. Where am i making a mistake?

GPU0: 1052 H/s [BUS:5]
GPU1: 942 H/s [BUS:9]
GPU2: 905 H/s [BUS:14]
GPU3: 924 H/s [BUS:13]
GPU4: 924 H/s [BUS:4]
GPU5: 1051 H/s [BUS:12]
GPU6: 1052 H/s [BUS:15]
GPU7: 1052 H/s [BUS:1]
GPU8: 1052 H/s [BUS:2]
GPU9: 924 H/s [BUS:3]
Total: 9878 H/s

Is this also happening on v 1.6.7 ?

Yes.

doktor83

hero member

Activity: 2548

Merit: 626

Quote from: zafa on October 09, 2018, 10:50:04 AM

Hello doktor83

I have 1 rig 10 x RX570 8GB and 18.6.1 driver.
My OC settings: 1250 - 2130 - 925 mv
Intens: 56
Double threads on
All cards have same ram (Micron), and bios.

My problem is about hashrates, Some cards are constantly running at low hashrate. I wait about an hour the result does not change. Where am i making a mistake?

GPU0: 1052 H/s [BUS:5]
GPU1: 942 H/s [BUS:9]
GPU2: 905 H/s [BUS:14]
GPU3: 924 H/s [BUS:13]
GPU4: 924 H/s [BUS:4]
GPU5: 1051 H/s [BUS:12]
GPU6: 1052 H/s [BUS:15]
GPU7: 1052 H/s [BUS:1]
GPU8: 1052 H/s [BUS:2]
GPU9: 924 H/s [BUS:3]
Total: 9878 H/s

Is this also happening on v 1.6.7 ?

doktor83

hero member

Activity: 2548

Merit: 626

Quote from: starmax on October 09, 2018, 10:49:32 AM

Quote from: doktor83 on October 09, 2018, 10:47:14 AM

Quote from: starmax on October 09, 2018, 10:45:55 AM

Quote from: starmax on October 08, 2018, 11:00:16 PM

Hmm, testing with a single Vega56. Was getting ~2035 with 1.6.7, now getting ~1630 with 1.6.8. Tried both the Normal and Maxi versions, same results. Using the 18.6.1 drivers, so not sure what to make of this Huh

Ok, figured out my issue. I had intensity: 0 in the config, and specified a GPU-specific intensity (112). Once I removed the gpu_conf section, it worked perfectly. Don't know if this is a bug or a change in how inheritance works in the config files.

when you set intensity to 0, miner sets worksize, number of threads and intensity automatically

Yup, I knew that, but thought the gpu_conf section overwrote the global settings outside the gpu_conf section.

it should overwrite. maybe it really is a bug

zafa

newbie

Activity: 136

Merit: 0

Hello doktor83

I have 1 rig 10 x RX570 8GB and 18.6.1 driver.
My OC settings: 1250 - 2130 - 925 mv
Intens: 56
Double threads on
All cards have same ram (Micron), and bios.

My problem is about hashrates, Some cards are constantly running at low hashrate. I wait about an hour the result does not change. Where am i making a mistake?

GPU0: 1052 H/s [BUS:5]
GPU1: 942 H/s [BUS:9]
GPU2: 905 H/s [BUS:14]
GPU3: 924 H/s [BUS:13]
GPU4: 924 H/s [BUS:4]
GPU5: 1051 H/s [BUS:12]
GPU6: 1052 H/s [BUS:15]
GPU7: 1052 H/s [BUS:1]
GPU8: 1052 H/s [BUS:2]
GPU9: 924 H/s [BUS:3]
Total: 9878 H/s

starmax

jr. member

Activity: 69

Merit: 1

Quote from: doktor83 on October 09, 2018, 10:47:14 AM

Quote from: starmax on October 09, 2018, 10:45:55 AM

Quote from: starmax on October 08, 2018, 11:00:16 PM

Hmm, testing with a single Vega56. Was getting ~2035 with 1.6.7, now getting ~1630 with 1.6.8. Tried both the Normal and Maxi versions, same results. Using the 18.6.1 drivers, so not sure what to make of this Huh

Ok, figured out my issue. I had intensity: 0 in the config, and specified a GPU-specific intensity (112). Once I removed the gpu_conf section, it worked perfectly. Don't know if this is a bug or a change in how inheritance works in the config files.

when you set intensity to 0, miner sets worksize, number of threads and intensity automatically

Yup, I knew that, but thought the gpu_conf section overwrote the global settings outside the gpu_conf section.

doktor83

hero member

Activity: 2548

Merit: 626

Quote from: starmax on October 09, 2018, 10:45:55 AM

Quote from: starmax on October 08, 2018, 11:00:16 PM

Hmm, testing with a single Vega56. Was getting ~2035 with 1.6.7, now getting ~1630 with 1.6.8. Tried both the Normal and Maxi versions, same results. Using the 18.6.1 drivers, so not sure what to make of this Huh

Ok, figured out my issue. I had intensity: 0 in the config, and specified a GPU-specific intensity (112). Once I removed the gpu_conf section, it worked perfectly. Don't know if this is a bug or a change in how inheritance works in the config files.

when you set intensity to 0, miner sets worksize, number of threads and intensity automatically

starmax

jr. member

Activity: 69

Merit: 1

Quote from: starmax on October 08, 2018, 11:00:16 PM

Hmm, testing with a single Vega56. Was getting ~2035 with 1.6.7, now getting ~1630 with 1.6.8. Tried both the Normal and Maxi versions, same results. Using the 18.6.1 drivers, so not sure what to make of this Huh

Ok, figured out my issue. I had intensity: 0 in the config, and specified a GPU-specific intensity (112). Once I removed the gpu_conf section, it worked perfectly. Don't know if this is a bug or a change in how inheritance works in the config files.

doktor83

hero member

Activity: 2548

Merit: 626

Quote from: camchimonline on October 09, 2018, 10:28:51 AM

WOWnero(CryptoNight V2), so CryptoNight V8 is CryptoNight V2?

yes lol

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