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

[liomojo1]

    I DO RECOMMEND  this miner , cause I was using cast-xmr and it was showing better hashrate , but my average on the pool  was low 17500-18000.
  Then i started using your miner and it is showing less hashrate may be 5% , BUT my average hashrate started growing and now after 24 hours it is 19955 and is stable . Keep the good work boys!!!!!!!!!!!!! And guys don`t get fooled by the better hash of other miners it is not real obviosly!!!

[1714127677]

1714127677

[1714127677]

1714127677

[zloy_hulk]

Hello!
Can you help me please with such problem - "your ip is banned" - i saw this message many times on different rigs. What it means actually?

[liomojo1]

When you send to many invalid shares  the pool bans your ip for a while! You have to be sure you use the correct algo set in config file!

[JuanHungLo]

vega 64 cryptonigh v7 or old hash 1950-2000 h/s new heavy algo hash 1450-1500 h/s
rx 580 cryptonigh v7 or old hash 1000 h/s new heavy algo hash 1000 h/s

why bad performance for vega 64?

my vega 64 setup. i have 2890 h/s

   { "id" : 0, "intensity" : 58, "worksize" : 8, "threads" : 2},
   { "id" : 1, "intensity" : 58, "worksize" : 8, "threads" : 2},

Try worksize 16 on Vegas

[RaidoP2]

Can anyone comment how much hashrate they have gotten from R9 290 or 290X with SRB?

[bruslie]

- Added average time to find share in stats


thx a lot much <3

[doktor83]

Hello!
Can you help me please with such problem - "your ip is banned" - i saw this message many times on different rigs. What it means actually?

Which version are you using?
From v1.4.6 there is duplicate share sending protection, which can cause ip ban too.

[doktor83]

   I DO RECOMMEND  this miner , cause I was using cast-xmr and it was showing better hashrate , but my average on the pool  was low 17500-18000.
  Then i started using your miner and it is showing less hashrate may be 5% , BUT my average hashrate started growing and now after 24 hours it is 19955 and is stable . Keep the good work boys!!!!!!!!!!!!! And guys don`t get fooled by the better hash of other miners it is not real obviosly!!!

Thank you man, really appreciate the good words !!

[lebuawu2]

Vega, RX 5xx series 4GB, and RX 4xx series 4GB will get lower hash in CN-Heavy because they said CN-Heavy use more memory than CN or CN-V7.
so your Vega hash on CN-Heavy is normal.

vega 64 cryptonigh v7 or old hash 1950-2000 h/s new heavy algo hash 1450-1500 h/s
rx 580 cryptonigh v7 or old hash 1000 h/s new heavy algo hash 1000 h/s

why bad performance for vega 64?

my vega 64 setup. i have 2890 h/s

   { "id" : 0, "intensity" : 58, "worksize" : 8, "threads" : 2},
   { "id" : 1, "intensity" : 58, "worksize" : 8, "threads" : 2},

[Larvitar]

V1.4.7
- Added shutdown_temperature parameter (in config.txt) which shuts down the system, default is 95c if not set
- Added average time to find share in stats
- Added keepalive option in pools to prevent possible connection timeouts (pool must support this method)
- Possible fix for Nicehash "job not found"
- Added kernel parameter to gpu_conf

: Keepalive does not work with Nanopool, Nicehash, Minergate. Maybe some others too. Even if you set it to TRUE on these pools, it will auto turn them off.
: kernel parameter can be used so if you have a mixed gpu rig with new+old cards, and the old ones work better with pre-gcn kernels for example

Thanks, doc!

About old cards: my old R7 260X is coming from reballing and I want to ask for who have old GCN2 cards:
SRB is beating (very) old Claymore 9.7? If yes, what configuration I can start from?

I'll try mine with then to see if it's profitable

Thanks in advance

[UnclWish]

V1.4.7
- Added shutdown_temperature parameter (in config.txt) which shuts down the system, default is 95c if not set
- Added average time to find share in stats
- Added keepalive option in pools to prevent possible connection timeouts (pool must support this method)
- Possible fix for Nicehash "job not found"
- Added kernel parameter to gpu_conf

: Keepalive does not work with Nanopool, Nicehash, Minergate. Maybe some others too. Even if you set it to TRUE on these pools, it will auto turn them off.
: kernel parameter can be used so if you have a mixed gpu rig with new+old cards, and the old ones work better with pre-gcn kernels for example

Thanks, doc!

About old cards: my old R7 260X is coming from reballing and I want to ask for who have old GCN2 cards:
SRB is beating (very) old Claymore 9.7? If yes, what configuration I can start from?

I'll try mine with then to see if it's profitable

Thanks in advance

On my 270X 4Gb card best miner is Claymore 11.3, 2nd place SRBMiner, 3rd place - GGS.
Each miner needs right parameters to recieve max speed.

[UnclWish]

doctor, did you plan to add adl support for Pitcairn like GCN1.0 GPU's? Did you plan to add clock, voltage, fans and pw controls?

Often recieve rejected shares "Job not found" on nicehash cryptonightV7.

Not at the moment, OverdriveNEXT supported cards only. That's a whole bunch of cards starting from 290 to Vega.

Oh, ok. What about adding clock, voltage, fans and pw controls?

And another one: i think that's good to add parameter for minrigspeed. If speed 5 minutess less than that parameter - restart rig.

In 1.4.7 how to set target and shutdown temperatures individual for each card?

[locbet]

   I DO RECOMMEND  this miner , cause I was using cast-xmr and it was showing better hashrate , but my average on the pool  was low 17500-18000.
  Then i started using your miner and it is showing less hashrate may be 5% , BUT my average hashrate started growing and now after 24 hours it is 19955 and is stable . Keep the good work boys!!!!!!!!!!!!! And guys don`t get fooled by the better hash of other miners it is not real obviosly!!!

Thank you man, really appreciate the good words !!

SRBMiner support json report stats. Please answer because i'm want Development UI Control for SRBMiner

Thanks

[arvonceda]

how to auto restart SRBMiner
example every 2 hours SRBMiner auto reconnect to pool, and back to the begin
(if on claymore we use command -r 120)


ty sir...

[treanski]

1.47

4 Vega 56 @ IPBC

[2018-04-23 18:19:11] GPU0:    3935.0 H/S [T: 60c, RPM: 3083, CC: 1508 MHz, MC: 950 MHz]
[2018-04-23 18:19:11] GPU1:    3805.0 H/S [T: 60c, RPM: 1386, CC: 1528 MHz, MC: 950 MHz]
[2018-04-23 18:19:11] GPU2:    3818.0 H/S [T: 60c, RPM: 1665, CC: 1528 MHz, MC: 950 MHz]
[2018-04-23 18:19:11] GPU3:    3918.0 H/S [T: 65c, RPM: 3062, CC: 1508 MHz, MC: 950 MHz]
[2018-04-23 18:19:11] Total:   15476.0 H/S

not bad

[cryptosize]

1.) Nope, and don't think he's going to, but never know later on.

Far as claymore 9.7 goes.. probably some shady coding he doesn't want anyone to know, or just wants to keep it away from everyone for fee's possibly, never know.

2.) I did notice on 14.4 drivers that my vram was more around 1GB and switching over to 15.7.1 it has 2047MB for some reason detected on all the other miners, but claymore did find 2047 on both drivers..
     so determining how it gets the m1 and m2 should be an easy fix, I know for a fact I only have 512MB dedicated, which is also shown in m2.. I'll have a look at which way xmrig/stak is polling the memory.  iirc this has been an issue with those for quite awhile.. I've never been able to get any miner to work without dying except for claymore on 15.7.1, and believe me I am trying to find a workaround that doesn't involve switching and mangling drivers around to make something work.

How much memory does 14.4 show you compared to 15.7.1?

1) The thing is, Claymore recently removed the devfee from his miner (v11.3). Apparently he's leaving the scene, which means no more support.

It sucks that he doesn't want to release the source code...

2) 14.4 detects the entire memory, while 15.7.1 says only 384MB of VRAM is available.

I really want to know how Claymore v9.7 detects the entire memory with 15.7.1 drivers... yet another secret hiding in the closed-source binary.

Yeah I did notice he took out the fee's at least for 3GB or under cards i think..

But how much memory do you have exactly in total when it's correct? Then I might be able to finally dig into it and see if i can get something going.
Since mines actually doing the opposite for some reason.. on 14.4 it's showing 1024 iirc, and 2047 for 15.7.1...not sure why it isn't 2048 though..

766MB IIRC.

I have a discrete GPU, so I'm not sure about your APU.

Also, Claymore v9.7 is the only miner that maxes out my GPU utilization/D3D usage (99-100%) in HWiNFO64, without spilling data to the main/CPU RAM (which drops hashrate a lot because of PCI-e bottlenecks).

Do you know if it's possible to program VLIW GPUs in pure assembly? IIRC, GCN GPUs support shader intrinsics, which is kinda like console/code to the metal programming:

https://www.gamersnexus.net/guides/2646-shader-intrinsic-functions-bypass-abstraction-layers

[cryptosize]

1. No, and won't do it. Why ? As soon as i release it, people will remove devfee, and upload that version to the forum and everywhere else. If that happens, i won't work on the miner anymore. Why ? Look at SRBPolaris, it's free, you know how much donation i got for it ? About 150$ maybe 200$. But of course lot of people use it.

2. Claymore is a magician, he probably worked at AMD and knows all the good insider stuff

I fully understand your concerns and I'll gladly pay a devfee, as long as the miner works properly (full hashrate, low intensity) and it's supported with new algos for a long time.

As I said, my concern with closed-source miners is that we might end up in a Claymore v9.7 situation, where v7 CN algo is not supported...

And yeah, Claymore is a magician. Too bad he doesn't want to release the source code, even though people have offered him BTC/ETH donations (not everyone is a cheapskate ).

[locbet]

Very bad: Vega 64 Cryptonight V7

[2018-04-23 23:25:53] Pool accepted result 0x000059B4
[2018-04-23 23:25:55] Pool accepted result 0x000044B1
[2018-04-23 23:25:55] Pool difficulty: 50625
[2018-04-23 23:25:55] Pool sent a new job (ID: 119620357058010)
[2018-04-23 23:25:58] Pool accepted result 0x0000EC14
[2018-04-23 23:26:03] Pool sent a new job (ID: 133028621855191)
[2018-04-23 23:26:11] GPU0:    1494.0 H/S [T: 51c, RPM: 3446, CC: 1408 MHz, MC: 1100 MHz]
[2018-04-23 23:26:11] GPU1:    1493.0 H/S [T: 51c, RPM: 3772, CC: 1408 MHz, MC: 1100 MHz]
[2018-04-23 23:26:11] GPU2:    1498.0 H/S [T: 48c, RPM: 3253, CC: 1408 MHz, MC: 1100 MHz]
[2018-04-23 23:26:11] GPU3:    1493.0 H/S [T: 47c, RPM: 3544, CC: 1408 MHz, MC: 1100 MHz]
[2018-04-23 23:26:11] GPU4:    1492.0 H/S [T: 47c, RPM: 3535, CC: 1408 MHz, MC: 1100 MHz]
[2018-04-23 23:26:11] GPU5:    1484.0 H/S [T: 48c, RPM: 3373, CC: 1408 MHz, MC: 1100 MHz]
[2018-04-23 23:26:11] Total:   8954.0 H/S
[2018-04-23 23:26:12] Pool sent a new job (ID: 264038743241690)
[2018-04-23 23:26:13] Pool accepted result 0x0000CEB1
[2018-04-23 23:26:16] Pool accepted result 0x000102BE
[2018-04-23 23:26:21] Pool accepted result 0x0000B950
[2018-04-23 23:26:24] Pool difficulty: 75939

[treanski]

Very bad: Vega 64 Cryptonight V7

[2018-04-23 23:25:53] Pool accepted result 0x000059B4
[2018-04-23 23:25:55] Pool accepted result 0x000044B1
[2018-04-23 23:25:55] Pool difficulty: 50625
[2018-04-23 23:25:55] Pool sent a new job (ID: 119620357058010)
[2018-04-23 23:25:58] Pool accepted result 0x0000EC14
[2018-04-23 23:26:03] Pool sent a new job (ID: 133028621855191)
[2018-04-23 23:26:11] GPU0:    1494.0 H/S [T: 51c, RPM: 3446, CC: 1408 MHz, MC: 1100 MHz]
[2018-04-23 23:26:11] GPU1:    1493.0 H/S [T: 51c, RPM: 3772, CC: 1408 MHz, MC: 1100 MHz]
[2018-04-23 23:26:11] GPU2:    1498.0 H/S [T: 48c, RPM: 3253, CC: 1408 MHz, MC: 1100 MHz]
[2018-04-23 23:26:11] GPU3:    1493.0 H/S [T: 47c, RPM: 3544, CC: 1408 MHz, MC: 1100 MHz]
[2018-04-23 23:26:11] GPU4:    1492.0 H/S [T: 47c, RPM: 3535, CC: 1408 MHz, MC: 1100 MHz]
[2018-04-23 23:26:11] GPU5:    1484.0 H/S [T: 48c, RPM: 3373, CC: 1408 MHz, MC: 1100 MHz]
[2018-04-23 23:26:11] Total:   8954.0 H/S
[2018-04-23 23:26:12] Pool sent a new job (ID: 264038743241690)
[2018-04-23 23:26:13] Pool accepted result 0x0000CEB1
[2018-04-23 23:26:16] Pool accepted result 0x000102BE
[2018-04-23 23:26:21] Pool accepted result 0x0000B950
[2018-04-23 23:26:24] Pool difficulty: 75939

its not the miner your config/ clocking / volting settings sucks for 100%

[locbet]

Very bad: Vega 64 Cryptonight V7

[2018-04-23 23:25:53] Pool accepted result 0x000059B4
[2018-04-23 23:25:55] Pool accepted result 0x000044B1
[2018-04-23 23:25:55] Pool difficulty: 50625
[2018-04-23 23:25:55] Pool sent a new job (ID: 119620357058010)
[2018-04-23 23:25:58] Pool accepted result 0x0000EC14
[2018-04-23 23:26:03] Pool sent a new job (ID: 133028621855191)
[2018-04-23 23:26:11] GPU0:    1494.0 H/S [T: 51c, RPM: 3446, CC: 1408 MHz, MC: 1100 MHz]
[2018-04-23 23:26:11] GPU1:    1493.0 H/S [T: 51c, RPM: 3772, CC: 1408 MHz, MC: 1100 MHz]
[2018-04-23 23:26:11] GPU2:    1498.0 H/S [T: 48c, RPM: 3253, CC: 1408 MHz, MC: 1100 MHz]
[2018-04-23 23:26:11] GPU3:    1493.0 H/S [T: 47c, RPM: 3544, CC: 1408 MHz, MC: 1100 MHz]
[2018-04-23 23:26:11] GPU4:    1492.0 H/S [T: 47c, RPM: 3535, CC: 1408 MHz, MC: 1100 MHz]
[2018-04-23 23:26:11] GPU5:    1484.0 H/S [T: 48c, RPM: 3373, CC: 1408 MHz, MC: 1100 MHz]
[2018-04-23 23:26:11] Total:   8954.0 H/S
[2018-04-23 23:26:12] Pool sent a new job (ID: 264038743241690)
[2018-04-23 23:26:13] Pool accepted result 0x0000CEB1
[2018-04-23 23:26:16] Pool accepted result 0x000102BE
[2018-04-23 23:26:21] Pool accepted result 0x0000B950
[2018-04-23 23:26:24] Pool difficulty: 75939

its not the miner your config/ clocking / volting settings sucks for 100%

Using OverDriveNTool:

[Profile_0]
Name=Vega64
GPU_P0=852;900;0
GPU_P1=991;900;0
GPU_P2=1084;900;0
GPU_P3=1138;900;0
GPU_P4=1150;900;0
GPU_P5=1202;900;0
GPU_P6=1212;905;0
GPU_P7=1408;925
Mem_P0=167;900;0
Mem_P1=500;900;0
Mem_P2=800;900;0
Mem_P3=1100;905
Fan_Min=3000
Fan_Max=4900
Fan_Target=65
Fan_Acoustic=1500
Power_Temp=70
Power_Target=-25

And PowerPlay:

_1100MHz_HBM_905mv
Wrong

Because using Cast XMR -->2055H/s