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

[livada]

how i use this for all card without gpu conf?

"gpu_conf" :
[
{ "id" : 0, "intensity" : 120, "worksize" : 16, "threads" : 2},
{ "id" : 1, "intensity" : 120, "worksize" : 16, "threads" : 2},
{ "id" : 2, "intensity" : 120, "worksize" : 16, "threads" : 2},

]
}

this is not work

"intensity" : 120,
"worksize" : 16,
"double_threads" : true,

W alwys 8 not 16

@DOCTOR ?

[UnclWish]

[2018-06-08 23:07:33] Error CL_OUT_OF_HOST_MEMORY when creating clCreateCommandQueue for DeviceID 0 (Thread 0)
[2018-06-08 23:07:33] Error initing GPU's. Stopping miner process

what caused the error ?

You can read? Miner all wrote to you. Not enogh memory on card. Lower intensity.

1.4.9 works, and 1.5.9 gives the following error
with the same settings

From 1.4.9 to 1.5.9 was 10 versions. I don't want to find in wich version what was changed. But you must understand that through 10 versions same settings can used by miner different ways. Just try to lower intensity and increase pagefile size to 8Gb * number of videocards.

that's obviously not the point. installed 8 GB of RAM and 80 GB of virtual 6 cards .

What algo? What intensity, worksize and threads?

[duyquang06]

In ver 1.6.0 my 580 4gb final break 1020h/s  v7

[StarLordRammi]

V1.6.0
- Added support for Haven new algo after fork (block 89200)
- Added support for Masari new algo (fast) after fork (block 204000)
- Job timeout default is now 20 minutes
- More logging on miner startup
- Added option 'persistent_memory' in gpu_conf

+ 2 new algos added : 'haven' and 'fast'
So after the fork you can use them like :

"cryptonight_type" : "fast"
"cryptonight_type" : "haven"


+ As some have issues with miner 'just waiting some time' on startup, i added more logging option so we can catch where it hangs, and i can possibly fix that
+ 'persistent_memory' parameter added to gpu_conf, basically what it does is tries to allocate some memory that is normally not available to the GPU. It can increase hashrate in some ocassions, by finding the right intensity and threads setup, but also it can make the gpu crash, so it's up to you to experiment

I am still looking for the cause of random miner crashes (mostly on new 'great' win 1803 update), also for the abnormality that causes higher hashrate on after X runs.

Hi Doc!

as I told you before, you have to take a good look at memory usage in task manager for the first run after reboot and all the next ones.
There is something strange there!
Behaviour is different.

PS. This doesn't happening in other miners.

same here.. sometimes on heavy algo my 3 cards are:
750h/s - 1100h/s - 950 h/s
or
780h/s - 950h/s - 950h/s
or
750h/s - 1050h/s - 920h/s

sometimes restarting the program i get more hasrate, doesnt always work but i dont know why it does that BUT all other miners dont even give me 2.5Kh/s in total where im getting up to 2.8Kh/s with this sometimes

cannot seem to get over 760h/s on my RX 570 4GB Samsung Memory card also

In ver 1.6.0 my 580 4gb final break 1020h/s  v7

what memory and what clocks?

[Kgonla]

V1.6.0
+ As some have issues with miner 'just waiting some time' on startup, i added more logging option so we can catch where it hangs, and i can possibly fix that

Reproduced
[2018-06-10 02:38:44] Heating up system, please wait...

[2018-06-10 02:38:43] CryptonightV7 mode enabled
[2018-06-10 02:38:44] DevFee pools loaded
[2018-06-10 02:38:44] DevFee pool SET
[2018-06-10 02:38:44] DevFee address SET

ok, now i know its not the new devfee method that is problematic.
But i would suggest to try now a previous version that you know was working good.
Nothing was changed in the new version in the GPU's initialisation process (this is where it hangs), so my guess is something at your side is causing this.

Comparing his log with mine:

[2018-06-09 13:52:22] CryptonightV7 mode enabled
[2018-06-09 13:53:46] DevFee pool SET
[2018-06-09 13:53:46] DevFee address SET

I don't have the "DevFee pools loaded", maybe is this what is slowing down my startup.

[Kgonla]

I keep getting this now on 1.5.9 every now and then.  Nothing changed in settings.
shut_down_miner exception: Resource deadlock avoided

I also getting this, suddenly all GPU hashing speed 0 h/s.

[2018-06-10 00:41:42] pool_ping: Sent keepalive message to pool
[2018-06-10 00:41:42] json_receive: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"KEEPALIVED"}}
[2018-06-10 00:41:42] json_receive: Pool responded with KEEPALIVED
[2018-06-10 00:42:07] watchdog: GPU0 [BUS: 1] hashing speed is 0 H/S
[2018-06-10 00:42:07] watchdog: GPU1 [BUS: 2] hashing speed is 0 H/S
[2018-06-10 00:42:07] watchdog: GPU2 [BUS: 3] hashing speed is 0 H/S
[2018-06-10 00:42:07] watchdog: GPU3 [BUS: 4] hashing speed is 0 H/S
[2018-06-10 00:42:07] watchdog: GPU4 [BUS: 5] hashing speed is 0 H/S
[2018-06-10 00:42:07] watchdog: GPU5 [BUS: 6] hashing speed is 0 H/S
[2018-06-10 00:42:07] watchdog: GPU6 [BUS: 9] hashing speed is 0 H/S
[2018-06-10 00:42:07] watchdog: GPU7 [BUS: 10] hashing speed is 0 H/S
[2018-06-10 00:42:07] watchdog: GPU8 [BUS: 11] hashing speed is 0 H/S
[2018-06-10 00:42:07] watchdog: GPU9 [BUS: 12] hashing speed is 0 H/S
[2018-06-10 00:42:07] watchdog: GPU10 [BUS: 13] hashing speed is 0 H/S
[2018-06-10 00:42:07] watchdog: GPU11 [BUS: 15] hashing speed is 0 H/S
[2018-06-10 00:42:33] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"0707d1a3f0d805256279b460556b7c15ee3cd01fcdba90cfdadfbdcc0654c667f5a4ae0a9a78530 00000001ab26cc8554f6b2671add6a9c76cbaaa20eb9f31179f7e0d5c9d969a8fd7194303","job_id":"276673124018431","target":"cf8b0000"}}
[2018-06-10 00:42:38] pool_ping: Sent keepalive message to pool
[2018-06-10 00:42:38] json_receive: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"KEEPALIVED"}}
[2018-06-10 00:42:38] json_receive: Pool responded with KEEPALIVED
[2018-06-10 00:42:56] shut_down_miner exception: Resource deadlock avoided
[2018-06-10 00:42:56] Stopping miner process

0 hash and shutdown exception are not related. this is just an information that on shutdown process resource clean up avoided a deadlock

For everybody having "hashing speed is 0 H/S" even randomly.

In my tests all the time I had this have been because intensity was too high.
I think you should set intensity to 10 or any other low value & see if it happens again.

[Kgonla]

I did not know how this works, I thought it was detected automatically.
About the time, I think it depends on how often the pool sets difficulty too high.
This option could be very useful for pools with badly configured vardiff to avoid loosing shares.
So, for me the shortest the best but every one is different
Maybe a command to choose between 1 & 60 secs.

No worries, i managed to make it to be instant, so it will be a next version update.
Also i changed the reconnecting procedure, don't know if it will help you in the miner closing after 4th diff reconnect. (i can't reproduce this)

Maybe a O.S. related problem, I'm using Server 2008 R2, not the W10 crap
Thank you Dok, your are the best!

[efecanhll]

fan control would really be great
i hate it when my fans always turn off and on. i have a feeling that it will degrade faster than a static fan. setting target temp too low will also make the fan try harder, so its a no as well.

[Sgsg666]

fan control would really be great
i hate it when my fans always turn off and on. i have a feeling that it will degrade faster than a static fan. setting target temp too low will also make the fan try harder, so its a no as well.

dok have added it. Although its rpm not % yet.

[duyquang06]

what memory and what clocks?
[/quote]

Samsung 1250/2050.

[doktor83]

V1.6.0
+ As some have issues with miner 'just waiting some time' on startup, i added more logging option so we can catch where it hangs, and i can possibly fix that

Reproduced
[2018-06-10 02:38:44] Heating up system, please wait...

[2018-06-10 02:38:43] CryptonightV7 mode enabled
[2018-06-10 02:38:44] DevFee pools loaded
[2018-06-10 02:38:44] DevFee pool SET
[2018-06-10 02:38:44] DevFee address SET

ok, now i know its not the new devfee method that is problematic.
But i would suggest to try now a previous version that you know was working good.
Nothing was changed in the new version in the GPU's initialisation process (this is where it hangs), so my guess is something at your side is causing this.

Comparing his log with mine:

[2018-06-09 13:52:22] CryptonightV7 mode enabled
[2018-06-09 13:53:46] DevFee pool SET
[2018-06-09 13:53:46] DevFee address SET

I don't have the "DevFee pools loaded", maybe is this what is slowing down my startup.

well then your firewall is probably blocking srbminer.com domain, and it cant get the devfee pools from online. add an exception to your firewall for the srbminer.com domain.

[abg00]

test a lot of configs

18.5.1 drivers is best. stable high rate

[wgestickley]

Hey Guys,

anybody got luck with "persistent_memory' on CNheavy Algo.

I run my RX580 8GB (Samsung Memory) with Double Threads and Intensity 54. All above 54 decrease the Hashrate.

Any ideas how to profit from this new function?

[treanski]

Hey Guys,

anybody got luck with "persistent_memory' on CNheavy Algo.

I run my RX580 8GB (Samsung Memory) with Double Threads and Intensity 54. All above 54 decrease the Hashrate.

Any ideas how to profit from this new function?

i tried a little bit around but couldnt gain no speedbest...best result i was able to get same speed like without this option.
persistent memory uses more gpu ram, so you need to use lower intensity, otherwise you slow down your gpus.
on my vegas i need to use 2-4 lower intensity...i dont know, maybe i need to test more settings, but im to lazy now

[ripcurrent]

Anyone figure out how to control fan speeds on the Vega FE cards?

[istr]

test a lot of configs

18.5.1 drivers is best. stable high rate

Anyone have noticed the inability of 18.5.1 driver to recognize RX 570's???
In my system it sees all my RX 570 as 580!!!
So I couldn't run miner.
I reverted back to 18.3.4.
win update 1803.
Even the 18.5.2 driver does the same.

Thanks in advance.

[abg00]

test a lot of configs

18.5.1 drivers is best. stable high rate

Anyone have noticed the inability of 18.5.1 driver to recognize RX 570's???
In my system it sees all my RX 570 as 580!!!
So I couldn't run miner.
I reverted back to 18.3.4.
win update 1803.
Even the 18.5.2 driver does the same.

Thanks in advance.

possible trouble in win1803
all 570\4 and 570\8 card work stable with max possible rate on v7 and heavy

ps 470\4 on win1803 work fine with 18.5.1 drivers

[hesido]

test a lot of configs

18.5.1 drivers is best. stable high rate

Anyone have noticed the inability of 18.5.1 driver to recognize RX 570's???
In my system it sees all my RX 570 as 580!!!
So I couldn't run miner.
I reverted back to 18.3.4.
win update 1803.
Even the 18.5.2 driver does the same.

Thanks in advance.

win1803 should be avoided at all cost.

[istr]

test a lot of configs

18.5.1 drivers is best. stable high rate

Anyone have noticed the inability of 18.5.1 driver to recognize RX 570's???
In my system it sees all my RX 570 as 580!!!
So I couldn't run miner.
I reverted back to 18.3.4.
win update 1803.
Even the 18.5.2 driver does the same.

Thanks in advance.

win1803 should be avoided at all cost.

Gentlemen,

it's not 1803 update definitely.
I installed 18.5.1 on my previous win 1709 and there was the problem!
So I decided to update to 1803.

[StarLordRammi]

what memory and what clocks?

Samsung 1250/2050.

thanks

not sure whats up but sometimes i get 1100h/s on Heavy on my samsung and sometimes 1000h/s

when samsung does 1100h/s my micron does less and sometimes other way around
cant get both to do 1100h/s at the same time

GPU0: RX 570 4GB Samsung Memory
GPU1: RX 580 8GB Samsung Memory
GPU2: RX 580 8GB Micron Memory

http://i67.tinypic.com/2ld8ydv.png