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

[doktor83]

Hi everyone,

I`m trying to run the miner on a 12card RX580 rig. I`m receiving these errors.
Please could you help.

"Error CL_MEM_OBJECT_ALLOCATION_FAILURE when calling clEnqeueNDRangeKernel"

I tried both V1.6.7 and V1.6.8 and drivers 18.6.1

I just see red everywhere.

Thanks

You need to increase virtual memory to a mininum of 96gb

[logicalray77]

Hi everyone,

I`m trying to run the miner on a 12card RX580 rig. I`m receiving these errors.
Please could you help.

"Error CL_MEM_OBJECT_ALLOCATION_FAILURE when calling clEnqeueNDRangeKernel"

I tried both V1.6.7 and V1.6.8 and drivers 18.6.1

I just see red everywhere.

Thanks

You need to increase virtual memory to a mininum of 96gb

Many thanks that did the trick.

[abg00]

test rx 550\4g on v8 with 1.6.8

v7 27\2\12 440 h\s
v8 28\2\16 386 h\s

[Bael]

Hi

Excuse me because I am very new, I am trying to configure the intensities of the gpus manually.

If I use this configuration it works fine

{
"cryptonight_type" : "bittubev2",
"intensity" : 0,
"double_threads" : true
}

I'm trying to use this configuration but I do not know if it's okay

{
"cryptonight_type" : "bittubev2",
"gpu_conf" :
[
   { "id" : 0, "intensity" : 54, "worksize" : 8, "threads" : 2},
   { "id" : 1, "intensity" : 54, "worksize" : 8, "threads" : 2},
   { "id" : 2, "intensity" : 54, "worksize" : 8, "threads" : 2},
   { "id" : 3, "intensity" : 54, "worksize" : 8, "threads" : 2}
]
}

When the active rig is blocked, so I continue to use the initial configuration for now.

My gpus are rx 580/570

Is the configuration I try in manual wrong?

[doktor83]

Hi

Excuse me because I am very new, I am trying to configure the intensities of the gpus manually.

If I use this configuration it works fine

{
"cryptonight_type" : "bittubev2",
"intensity" : 0,
"double_threads" : true
}

I'm trying to use this configuration but I do not know if it's okay

{
"cryptonight_type" : "bittubev2",
"gpu_conf" :
[
   { "id" : 0, "intensity" : 54, "worksize" : 8, "threads" : 2},
   { "id" : 1, "intensity" : 54, "worksize" : 8, "threads" : 2},
   { "id" : 2, "intensity" : 54, "worksize" : 8, "threads" : 2},
   { "id" : 3, "intensity" : 54, "worksize" : 8, "threads" : 2}
]
}

When the active rig is blocked, so I continue to use the initial configuration for now.

My gpus are rx 580/570

Is the configuration I try in manual wrong?

This should work:

Code:

{
"cryptonight_type" : "bittubev2",
"intensity" : 0,
"double_threads" : true,
"gpu_conf" : 
[ 
	{ 
	  "id" : 0, 
	  "intensity" : 54, 
	  "worksize" : 8, 
	  "threads" : 2
	},
        { 
	  "id" : 1, 
	  "intensity" : 54, 
	  "worksize" : 8, 
	  "threads" : 2
	},
        { 
	  "id" : 2, 
	  "intensity" : 54, 
	  "worksize" : 8, 
	  "threads" : 2
	},
        { 
	  "id" : 3, 
	  "intensity" : 54, 
	  "worksize" : 8, 
	  "threads" : 2
	}
]
}

When the active rig is blocked

This i don't understand

[Bael]

This should work:

Code:

{
"cryptonight_type" : "bittubev2",
"intensity" : 0,
"double_threads" : true,
"gpu_conf" : 
[ 
	{ 
	  "id" : 0, 
	  "intensity" : 54, 
	  "worksize" : 8, 
	  "threads" : 2
	},
        { 
	  "id" : 1, 
	  "intensity" : 54, 
	  "worksize" : 8, 
	  "threads" : 2
	},
        { 
	  "id" : 2, 
	  "intensity" : 54, 
	  "worksize" : 8, 
	  "threads" : 2
	},
        { 
	  "id" : 3, 
	  "intensity" : 54, 
	  "worksize" : 8, 
	  "threads" : 2
	}
]
}

When the active rig is blocked

This i don't understand

[/quote]

Thanks !, now if it works

what the active miner blocked I was referring to the configuration that I put him.

Apologies because I speak english badly.

[twoxeons]

V1.6.8 running great on one computer, but cannot initialize GPU's on the other.  Log says Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram [ctx->Program] for DeviceID 0 (Thread 0).  I've done everything I can think to make certain the Config file has the correct syntax, to include changes like the post directly above.  What else can cause this problem?  V1.6.7 runs fine on same computer.

Solution found if anyone is interested:  Can't use build 1803.  Roll it back or reinstall.

[jazz1984]

PITCAIRN guys, re-download 1.6.8, compilation fixed  

My 7970 [Intensity 27.0][W: 4][T: 2] 485H/s with 1000 core/1375 memory(memory by default), now it is the fastest results for my clocks.

Try 1100 core, 1500 mem, for me, go over 520-550 H/s

Its really interesting result: on 1000/1500 hashrate increased to 495 H/s,
but increasing the memory frequency by at least 1mhz above 1500 results in a drop of hashrate to above 430-440. For now works at 1000/1500, if this clocks will be stable then later try to overclock the core. Thank you a lot, i thought that memory overclocking on this video card does not lead to improved results without modifying the timings.

That's normal since after 1500MHz on memory you are entering other strap which is less tighten.

I thought on my 7970 strap happens much earlier than 1500 and therefore did not overclock the memory. Now result with overclocked core to 1125, memory 1500   =  512 H/s.
UPD All my results in v7.

[io8621]

Works fine on Pitcairn 370 2gb.

1150 - 1500 gpu / mem

-i 25 -w 8 -k 1

get ~360 hs.

Big difference between v7 and v8.

With v7 get ~530 from this old card.

It's normal a so big drop?

[sky2018miner]

relative to pitcairn 370 2gb
I get a maximum of 370 h / s on v8
1000 - 1420 gpu / mem
-i 27 -w 16 -k 1
but new problems have arisen
there are compute errors on these maps
I tried the 18.6.1, 18.5.2 driver
changed the intensity of the core frequency and memory errors appear again
then tested v7 - 490h / s
970 - 1400 gpu / mem
-i 30 -w 8 -k 1
compute errors again
question where is the problem?

[dingdongtobias]

relative to pitcairn 370 2gb
I get a maximum of 370 h / s on v8
1000 - 1420 gpu / mem
-i 27 -w 16 -k 1
but new problems have arisen
there are compute errors on these maps
I tried the 18.6.1, 18.5.2 driver
changed the intensity of the core frequency and memory errors appear again
then tested v7 - 490h / s
970 - 1400 gpu / mem
-i 30 -w 8 -k 1
compute errors again
question where is the problem?

in your gpu bios and memory strap

[sky2018miner]

bios native without timings, produced only downvolt gpu - 1.018v
On version 1.6.4 that I used before, problems did not notice

[Bojcha]

on v8 try w16

[U4guk]

i to have many compute errors, how critical is it? hashrate in the miner indicated with these errors?

[abg00]

rx570\570 4g card need more core power on v8. add 10-30 mV on core power

[Bojcha]

Can you guys share your V7 and V8 results on the same card?

RX570 4GB Hynix v7/v8 exact same settings, except v8 is with worksize 16 instead 8.

- V7 - 975H/s
- V8 - 967H/s

Did not measure power but i smell ~20% more on V8

[lupaarSen]

hi i m trying to set up a multi-algo switching (Monero Ocean+ Miner2gether (XAO)
i set these 2 pools in pools-algo-switching with cryptonight_type option by pool
when i run miner it restart switching in loop cryptonightv7-->another MO currency-->cryptonight_V7-->another currency again and again with no mining
help plz
*SRBMiner 1.6.8

[flashgear]

Loving this miner!

Just a quick query, is there any built in hash rate monitoring? Did I miss it?

Sometimes Vega's are dropping hash and a hash watch dog where you can set a threshold before the miner restarts would be awesome!

[heavyarms1912]

Can you guys share your V7 and V8 results on the same card?

RX570 4GB Hynix v7/v8 exact same settings, except v8 is with worksize 16 instead 8.

- V7 - 975H/s
- V8 - 967H/s

Did not measure power but i smell ~20% more on V8

20%?  That pits it in 150w-160w range.

[doktor83]

Loving this miner!

Just a quick query, is there any built in hash rate monitoring? Did I miss it?

Sometimes Vega's are dropping hash and a hash watch dog where you can set a threshold before the miner restarts would be awesome!

I guess you haven't check the first page, or the readme.txt.

config.txt

"min_rig_speed" : number - in H/S, it defines the minimum rig hashing speed we want to maintain. If 5 minute average hashing speed is less than this, miner restarts.
"min_rig_speed_duration" : number - in seconds (minimum is 30 sec), defines the time period for average hashing speed calculation, used with 'min_rig_speed' parameter