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

[doktor83]

I am glad you understand me.
For me 6-12 hours will be perfect, but i suggest to put some parameters , like 4 , 6, 8, 12 hours or 2,4,6,8 devfee mining times/24 hours. Of course, if my rig restarts , will be your bigger fee , but if not , I prefer you to devfee mine for 5 minutes 2 times a day then 1 minutes 10 times a day

About devfee mining, now I understand. I did not checked the percentile, as I consider this way of working more like a gentleman's agreement. I will never block your fee, as it permits you to keep working on improving. I thought you are hiding it for other reasons, now I get the idea why. I think you are right.

Cannot wait to have this time parameter feature.Even if you keep the time of mining hidden, basically will be 2-4 times every 24 hours, which looks great for me.

I won't make the user choose how often (4 , 6, 8, 12h), because .. you already know why ('the kill/start thing').
But i will think out something

[symplink]

Then put how many/24 hours and then do your algo for devfee.
Will not be a problem if you mine at 2  times at  1 hour interval even if i set 2/day , the rest of the day will be uninterrupted.
Just to not have reboots on my rigs, then you will get a lot of devfee , but this is my work to do.

[puntodecontrol]

It doesnt save the log file.... any ideas?

Maybe there are no write permissions for the miner to work in its own folder?

If i put manually (--logfile log.txt) works, but if i let the star file creates it, it doesnt work.

This its my start.bat file

setx GPU_MAX_HEAP_SIZE 100
setx GPU_MAX_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_MAX_SINGLE_ALLOC_PERCENT 100
@echo off
cd %~dp0

cls
set LOGTIME=%date:~10,4%_%date:~4,2%_%date:~7,2%_%time:~0,2%_%time:~3,2%
set LOGTIME=%LOGTIME: =%
set LOGTIME=%LOGTIME:,=.%.txt

SRBMiner-CN.exe --config Config\config.txt --pools pools.txt --logfile %LOGTIME%

[goodminer]

Hi, please tell me what is wrong here? I'm using the last version 1.6.7 and mining masari, cryptonight fast. On older versions it works great, but on the last 3 ones I can't start, it gives me this error...
https://imgur.com/a/XuoP2c7

[doktor83]

Hi, please tell me what is wrong here? I'm using the last version 1.6.7 and mining masari, cryptonight fast. On older versions it works great, but on the last 3 ones I can't start, it gives me this error...
https://imgur.com/a/XuoP2c7

if you just copied over the .exe to an older version without clearing the cache dir, you can get that

[leon22]

i use blochchain amd drivers by august
can Adrenalin 18.6.1 or Adrenalin 18.3.4 drivers decrease hashrate for RX570 4gb/ RX580 4gb ?

[alivanich]

i have 13gpu rig: 6x hd7850, 2x r9 270, 5x rx550
1.6.7 failed on both r9 270
another 11 gpu working good

version 1.5.9 working good with all 13 gpu

how i can fix this problem?

[2018-09-05 01:26:51] Miner version: 1.6.7
[2018-09-05 01:26:51] Windows version: 10.0 build 14393
[2018-09-05 01:26:52] Video driver version: 23.20.15033.5003
[2018-09-05 01:27:00] AMD Platform ID: 0
[2018-09-05 01:27:00] AMD platform FOUND
[2018-09-05 01:27:00] Found 13 AMD devices
[2018-09-05 01:27:00] CPU AES-NI: TRUE
[2018-09-05 01:27:00] GPU0: Radeon 550 Series [gfx804] [2048 MB][Intensity 20.0][W: 8][T: 2][K: 1][BUS: 13]
[2018-09-05 01:27:00] GPU1: Radeon 550 Series [gfx804] [2048 MB][Intensity 20.0][W: 8][T: 2][K: 1][BUS: 18]
[2018-09-05 01:27:00] GPU2: AMD Radeon HD 7800 Series [Pitcairn] [2048 MB][Intensity 20.0][W: 8][T: 2][K: 2][BUS: 3]
[2018-09-05 01:27:00] GPU3: Radeon 550 Series [gfx804] [2048 MB][Intensity 20.0][W: 8][T: 2][K: 1][BUS: 8]
[2018-09-05 01:27:00] GPU4: AMD Radeon (TM) R9 200 Series [Pitcairn] [2048 MB][Intensity 20.0][W: 8][T: 2][K: 1][BUS: 15]
[2018-09-05 01:27:00] GPU5: AMD Radeon HD 7800 Series [Pitcairn] [2048 MB][Intensity 20.0][W: 8][T: 2][K: 2][BUS: 7]
[2018-09-05 01:27:00] GPU6: AMD Radeon HD 7800 Series [Pitcairn] [2048 MB][Intensity 20.0][W: 8][T: 2][K: 2][BUS: 16]
[2018-09-05 01:27:00] GPU7: Radeon 550 Series [gfx804] [2048 MB][Intensity 20.0][W: 8][T: 2][K: 1][BUS: 20]
[2018-09-05 01:27:00] GPU8: AMD Radeon HD 7800 Series [Pitcairn] [2048 MB][Intensity 20.0][W: 8][T: 2][K: 2][BUS: 2]
[2018-09-05 01:27:00] GPU9: AMD Radeon HD 7800 Series [Pitcairn] [2048 MB][Intensity 20.0][W: 8][T: 2][K: 2][BUS: 19]
[2018-09-05 01:27:00] GPU10: Radeon 550 Series [gfx804] [2048 MB][Intensity 20.0][W: 8][T: 2][K: 1][BUS: 17]
[2018-09-05 01:27:00] GPU11: AMD Radeon (TM) R9 200 Series [Pitcairn] [2048 MB][Intensity 20.0][W: 8][T: 2][K: 1][BUS: 1]
[2018-09-05 01:27:00] GPU12: AMD Radeon HD 7800 Series [Pitcairn] [2048 MB][Intensity 20.0][W: 8][T: 2][K: 2][BUS: 10]
[2018-09-05 01:27:00] ADL is enabled
[2018-09-05 01:27:00] CryptonightV7 mode enabled
[2018-09-05 01:27:00] DevFee pool SET
[2018-09-05 01:27:00] DevFee address SET
[2018-09-05 01:27:00] Starting init of mining threads
[2018-09-05 01:27:03] Loading compiled kernel for DEVICE BUS ID 13 ...
[2018-09-05 01:27:05] Loading compiled kernel for DEVICE BUS ID 13 ...
[2018-09-05 01:27:06] Loading compiled kernel for DEVICE BUS ID 18 ...
[2018-09-05 01:27:07] Loading compiled kernel for DEVICE BUS ID 18 ...
[2018-09-05 01:27:08] Loading compiled kernel for DEVICE BUS ID 3 ...
[2018-09-05 01:27:09] Loading compiled kernel for DEVICE BUS ID 3 ...
[2018-09-05 01:27:11] Loading compiled kernel for DEVICE BUS ID 8 ...
[2018-09-05 01:27:12] Loading compiled kernel for DEVICE BUS ID 8 ...
[2018-09-05 01:27:13] Compiling kernel for DEVICE BUS ID 15 ...
[2018-09-05 01:27:13] Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram for DeviceID 4 (Thread
[2018-09-05 01:27:13] Error initing GPU's. Stopping miner process
[2018-09-05 01:27:13] Stopping miner process

[goodminer]

Hi, please tell me what is wrong here? I'm using the last version 1.6.7 and mining masari, cryptonight fast. On older versions it works great, but on the last 3 ones I can't start, it gives me this error...
https://imgur.com/a/XuoP2c7

if you just copied over the .exe to an older version without clearing the cache dir, you can get that

No, I didn't do that, it is a fresh new version downloaded from first page. I have an r7 370 and I see someone else too can't start an r9 270, that is definitely problem with new version of miner, because on 1.5.9 it is working good. Is it bug?

[SpceGhst]

i have 13gpu rig: 6x hd7850, 2x r9 270, 5x rx550
1.6.7 failed on both r9 270
another 11 gpu working good

version 1.5.9 working good with all 13 gpu

how i can fix this

I think R9 cards are supposed to be kernel 2, not kernel 1.

[dannyprats]

i use blochchain amd drivers by august
can Adrenalin 18.6.1 or Adrenalin 18.3.4 drivers decrease hashrate for RX570 4gb/ RX580 4gb ?

Same question here..

I use blockchain Aug23 driver too..

for RX 470, 480, 570, 580..

Is there any difference in performance using the Adrenalin driver?

My hashrate currently (blockchain driver):

RX 470, 480, 570, 580 - 4GB:
-CN7, Stellitev4: 950-1000
-Heavy, Bittubev2: 750-775 (800+ in some cards)
-Fast: 1850-1900
-Litev7: 1900-1950

RX 470, 480, 580 - 8GB:
-CN7, Stellitev4: 1050-1100
-Heavy, Bittubev2: 1050-1100 (1100+ in some cards)
-Fast: 2050-2100
-Litev7: 2100

So.. Is it worth changing the driver?

[doktor83]

i have 13gpu rig: 6x hd7850, 2x r9 270, 5x rx550
1.6.7 failed on both r9 270
another 11 gpu working good

version 1.5.9 working good with all 13 gpu

how i can fix this

I think R9 cards are supposed to be kernel 2, not kernel 1.

Thats right, you should set it by hand to use kernel 2 in gpu_conf

[goodminer]

i have 13gpu rig: 6x hd7850, 2x r9 270, 5x rx550
1.6.7 failed on both r9 270
another 11 gpu working good

version 1.5.9 working good with all 13 gpu

how i can fix this

I think R9 cards are supposed to be kernel 2, not kernel 1.

Thats right, you should set it by hand to use kernel 2 in gpu_conf

I tried my r7 370 with both version of kernels and can't start it, so this is not problem about kernels, it looks like a some kind of bug in this new versions of miner.

[doktor83]

i have 13gpu rig: 6x hd7850, 2x r9 270, 5x rx550
1.6.7 failed on both r9 270
another 11 gpu working good

version 1.5.9 working good with all 13 gpu

how i can fix this

I think R9 cards are supposed to be kernel 2, not kernel 1.

Thats right, you should set it by hand to use kernel 2 in gpu_conf

I tried my r7 370 with both version of kernels and can't start it, so this is not problem about kernels, it looks like a some kind of bug in this new versions of miner.

Hm, unfortunately i dont have r7 370's to try it. You say you tried kernel 2, can you show me your config.txt ?

[Pennywis3]

"reboot_script" still not working, even if "min_rig_speed" is set.
It just restarts the miner doesn't run the script.

Had to change miner on 9 rigs because of this annoying issue 

[doktor83]

"reboot_script" still not working, even if "min_rig_speed" is set.
It just restarts the miner doesn't run the script.

Had to change miner on 9 rigs because of this annoying issue  

Reboot script is only for the gpu watchdog (which checks if gpu is working normal/crashed) , not for the min hashrate. It never was.
I guess it should be  

I was led by the logic that when the gpu crashes , sometimes a miner restart isn't enough, so the whole rig has to be rebooted.
But when only the hashrate falls, a miner restart is enough to get the hashrate back. That's why no reboot_script for this scenario.

But next version will use reboot_script on min_hashrate also.

[doktor83]

If any of you are having problems with sudden software miner stopping and a logfile that ends with something like this:

[2018-09-03 17:17:56] devfee: Could not connect to a devfee pool for a long time!
[2018-09-03 17:17:56] devfee: Tried few pools, but none of them could be connected, so you are probably blocking them.
[2018-09-03 17:17:56] devfee: Don't be a dick.
[2018-09-03 17:17:56] Stopping miner process

And you have made sure that your firewall is not blocking the program, or some other malware software,
then you should try adding to the hosts file of your operating system:

95.216.148.81   srbminer.com

Typically your hosts file is located at:  C:\Windows\System32\drivers\etc

This is the first time in a long time that some of my affected mining rigs have ran past 36 hours without a restart.

Thanks for the idea, Dok

I think you may be the only one still struggling with this 
Im glad it helped.

BTW, it's all in the logs, if you have DFP online load : SUCCESS, that means it could contact srbminer domain.
If you have multiple fails for devfee mining, that can be seen in the logs too..

[alivanich]

i have 13gpu rig: 6x hd7850, 2x r9 270, 5x rx550
1.6.7 failed on both r9 270
another 11 gpu working good

version 1.5.9 working good with all 13 gpu

how i can fix this

I think R9 cards are supposed to be kernel 2, not kernel 1.

Great, thank you!
Now it's working.

Config:
{
"cryptonight_type" : "normalv7",
"intensity" : 27,
"double_threads" : true,
"gpu_conf" :
[
   { "id" : 0, "intensity" : 27, "worksize" : 8, "threads" : 2},
   { "id" : 1, "intensity" : 27, "worksize" : 8, "threads" : 2},
   { "id" : 2, "intensity" : 27, "worksize" : 8, "threads" : 2},
   { "id" : 3, "intensity" : 27, "worksize" : 8, "threads" : 2},
   { "id" : 4, "intensity" : 27, "worksize" : 8, "threads" : 2, "kernel" : 2},
   { "id" : 5, "intensity" : 27, "worksize" : 8, "threads" : 2},
   { "id" : 6, "intensity" : 27, "worksize" : 8, "threads" : 2},
   { "id" : 7, "intensity" : 27, "worksize" : 8, "threads" : 2},
   { "id" : 8, "intensity" : 27, "worksize" : 8, "threads" : 2},
   { "id" : 9, "intensity" : 27, "worksize" : 8, "threads" : 2},
   { "id" : 10, "intensity" : 27, "worksize" : 8, "threads" : 2},
   { "id" : 11, "intensity" : 27, "worksize" : 8, "threads" : 2, "kernel" : 2},
   { "id" : 12, "intensity" : 27, "worksize" : 8, "threads" : 2}
]
}

[SpceGhst]

i have 13gpu rig: 6x hd7850, 2x r9 270, 5x rx550
1.6.7 failed on both r9 270
another 11 gpu working good

version 1.5.9 working good with all 13 gpu

how i can fix this

I think R9 cards are supposed to be kernel 2, not kernel 1.

Thats right, you should set it by hand to use kernel 2 in gpu_conf

I tried my r7 370 with both version of kernels and can't start it, so this is not problem about kernels, it looks like a some kind of bug in this new versions of miner.

Is your R7 Pitcairn architecture?  I have a R7 240 and it’s Oland architecture, which I don’t believe newer SRB supports.

[symplink]

I am glad you understand me.
For me 6-12 hours will be perfect, but i suggest to put some parameters , like 4 , 6, 8, 12 hours or 2,4,6,8 devfee mining times/24 hours. Of course, if my rig restarts , will be your bigger fee , but if not , I prefer you to devfee mine for 5 minutes 2 times a day then 1 minutes 10 times a day

About devfee mining, now I understand. I did not checked the percentile, as I consider this way of working more like a gentleman's agreement. I will never block your fee, as it permits you to keep working on improving. I thought you are hiding it for other reasons, now I get the idea why. I think you are right.

Cannot wait to have this time parameter feature.Even if you keep the time of mining hidden, basically will be 2-4 times every 24 hours, which looks great for me.

I won't make the user choose how often (4 , 6, 8, 12h), because .. you already know why ('the kill/start thing').
But i will think out something

I have an idea - why don't you give us a parameter - mine all devfee for 6/12/24 hours at beginning. After start, to start mining your devfee, then to not interrupt for that period. Then, once period pased, use same amount to mine for next period of 6/12/24 (our decision) Even a restart could not stop devmining, because at restart it will mine again for whole period. This should be perfect for both of us.

[io8621]

i have 13gpu rig: 6x hd7850, 2x r9 270, 5x rx550
1.6.7 failed on both r9 270
another 11 gpu working good

version 1.5.9 working good with all 13 gpu

how i can fix this

I think R9 cards are supposed to be kernel 2, not kernel 1.

Thats right, you should set it by hand to use kernel 2 in gpu_conf

I tried my r7 370 with both version of kernels and can't start it, so this is not problem about kernels, it looks like a some kind of bug in this new versions of miner.

Same for me, 370 with last version don't work, with past version on the same sysyem, 1.60 for example, working without problem.