Author

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

jr. member
Activity: 153
Merit: 2
Gonna have to try this out =)


This is my config for SRBMiner:

"cryptonight_type" : "normalv7",
"intensity" : 0,
"target_temperature" : 72,

   { "id" : 0, "intensity" : 0, "worksize" : 8, "threads" : 1},
   { "id" : 1, "intensity" : 0, "worksize" : 8, "threads" : 1},
   { "id" : 2, "intensity" : 0, "worksize" : 8, "threads" : 1},
   { "id" : 3, "intensity" : 0, "worksize" : 8, "threads" : 1},
]*/

You are doing two things at once. At top you have intensity 0 for auto and at the bottom you removed one of the */ combo but not the other. You either mine with 0 at the top or make custom at the bottom, not both. Try replacing */ where I have it to try mining with auto settings.


Realized you left a line out. You may have it correct. disregard.
newbie
Activity: 88
Merit: 0
what coin uses this ultraheavy algo?

IPBC will once it forks. Should be in the next few hours.

How is this UltraHeavy??
Results from my test rig IPBC Forked:

RX570/8G-RX570/8G-RX580/4G-RX560/4G-RX560/4G

[2018-04-16 14:12:06] GPU0:    1874.0 H/S [T: 54c, RPM: 1119]
[2018-04-16 14:12:06] GPU1:    1991.0 H/S [T: 55c, RPM: 837]
[2018-04-16 14:12:06] GPU2:    1932.0 H/S [T: 63c, RPM: 1092]
[2018-04-16 14:12:06] GPU3:    816.0 H/S [T: 59c, RPM: 1221]
[2018-04-16 14:12:06] GPU4:    913.0 H/S [T: 59c, RPM: 1195]
[2018-04-16 14:12:06] Total:   7526.0 H/S



4x Vega 56
[2018-04-16 14:19:33] GPU0:    2634.0 H/S [T: 49c, RPM: 2559]
[2018-04-16 14:19:33] GPU1:    2650.0 H/S [T: 49c, RPM: 2879]
[2018-04-16 14:19:33] GPU2:    2648.0 H/S [T: 51c, RPM: 2780]
[2018-04-16 14:19:33] GPU3:    2650.0 H/S [T: 49c, RPM: 2738]

Is the hash rate per one vega 56 is 2600 H/s on V7 ?
hero member
Activity: 714
Merit: 512
Gonna have to try this out =)

On my first rig... for some reason will not pick up all four GPUs & then also crashes.

I have Adrenalin 18 series drivers -- now I am trying the very newest one (installing now).

The per-GPU speed is greater than XMR-STAK already, though, with intensity at 0 , worksize 8, and threads 1.

Okay -- newest 18.3.4 Adrenalin driver still crashing... GPU 0 hashes 0 H/S before the crash.

XMR-STAK detects them all and they all hash.

This is my config for SRBMiner:

"cryptonight_type" : "normalv7",
"intensity" : 0,
"target_temperature" : 72,
[
   { "id" : 0, "intensity" : 0, "worksize" : 8, "threads" : 1},
   { "id" : 1, "intensity" : 0, "worksize" : 8, "threads" : 1},
   { "id" : 2, "intensity" : 0, "worksize" : 8, "threads" : 1},
   { "id" : 3, "intensity" : 0, "worksize" : 8, "threads" : 1},
]*/
hero member
Activity: 714
Merit: 512
Gonna have to try this out =)

On my first rig... for some reason will not pick up all four GPUs & then also crashes.

I have Adrenalin 18 series drivers -- now I am trying the very newest one (installing now).

The per-GPU speed is greater than XMR-STAK already, though, with intensity at 0 , worksize 8, and threads 1.
newbie
Activity: 80
Merit: 0
what coin uses this ultraheavy algo?

IPBC will once it forks. Should be in the next few hours.

How is this UltraHeavy??
Results from my test rig IPBC Forked:

RX570/8G-RX570/8G-RX580/4G-RX560/4G-RX560/4G

[2018-04-16 14:12:06] GPU0:    1874.0 H/S [T: 54c, RPM: 1119]
[2018-04-16 14:12:06] GPU1:    1991.0 H/S [T: 55c, RPM: 837]
[2018-04-16 14:12:06] GPU2:    1932.0 H/S [T: 63c, RPM: 1092]
[2018-04-16 14:12:06] GPU3:    816.0 H/S [T: 59c, RPM: 1221]
[2018-04-16 14:12:06] GPU4:    913.0 H/S [T: 59c, RPM: 1195]
[2018-04-16 14:12:06] Total:   7526.0 H/S



4x Vega 56
[2018-04-16 14:19:33] GPU0:    2634.0 H/S [T: 49c, RPM: 2559]
[2018-04-16 14:19:33] GPU1:    2650.0 H/S [T: 49c, RPM: 2879]
[2018-04-16 14:19:33] GPU2:    2648.0 H/S [T: 51c, RPM: 2780]
[2018-04-16 14:19:33] GPU3:    2650.0 H/S [T: 49c, RPM: 2738]
newbie
Activity: 1
Merit: 0


good day dok! how can i decide "error invalid buffer size" on rig rx580*8,  if i increasing intensivety from 50 ? on another same  rig, the card intensivety is 59 and it work well. all parameters, besides intensivety, is same.  can you help me, please?
hero member
Activity: 935
Merit: 1001
I don't always drink...
Upgrading to new version and have questions, what to insert in config for "worksize" and "threads", for gpu's: 570, 580 and Vega 56 ?
thanks

in the config.txt file at the bottom like this:
Quote
"gpu_conf" :
[
   { "id" : 0, "intensity" : 0, "worksize" : 8, "threads" : 2},
   { "id" : 1, "intensity" : 0, "worksize" : 8, "threads" : 2},
]
}

Be sure and remove the  (/* comment ) at the beginning and end
newbie
Activity: 65
Merit: 0
1.4.0 was operating until now really stable! Trying out the newest version of the miner, will report laters. Good luck bois
newbie
Activity: 165
Merit: 0
Upgrading to new version and have questions, what to insert in config for "worksize" and "threads", for gpu's: 570, 580 and Vega 56 ?
thanks
jr. member
Activity: 153
Merit: 2
what coin uses this ultraheavy algo?

IPBC will once it forks. Should be in the next few hours.
member
Activity: 443
Merit: 13
Yeah, my rx 580 8gb works even better on heavy.
V7 - 1070 hs
Heavy - 1120~1140 hs

Could you please share your settings? What bios mod are you using and your cclock and mclock settings is possible/ intensity etc etc Cheesy I am trying to pull a bit more than 900h/s on my RX580s.
newbie
Activity: 2
Merit: 0
newbie
Activity: 50
Merit: 0
is it possible to get same hashrate on HEAVY algo like normalV7?
for example: at normalv7 one of my rigs (5xRX570 4gb) do ~5000h/s +/- (SRBminer) but on heavy i get only ~3500h/s


no. its made and called heavy for a reason. everyone will experience the same, so you are not behind.

It is expected lower hash but there are some RX580 8GB users reporting same hash....

Yeah, my rx 580 8gb works even better on heavy.
V7 - 1070 hs
Heavy - 1120~1140 hs
jr. member
Activity: 202
Merit: 2
take of the commenting (/* and */)

Thank you so much.

Figured out autostart of Devcon.exe and the start.bat with the blockchain driver.
Hashing at 2060-2070 on Vega 64s.
Auto reboots on fail and up and running automatically within 2 min.  

Rockin!

(Now just to play with tweaks on individual cards for less crashing)

does that means no hashrate drop on  vega?
Could you share a short how-to-do-it so other Vega users can set it up too ? Smiley

This is old knowledge to Vega users since the main Vega mining guide has it since long time ago.
http://vega.miningguides.com

It all started with this script that today evolved to a small software called PreciousGuardian...
This is the original script:
https://github.com/zbobyuan/JJ-s-XMR-STAK-HashRate-Monitor-and-Restart-Tool
It need to be modified manually(miner name and folders) to work with your software, CAst or any other version of xmr-stak.

Now the guide is updated so the instructions to use the script are not there anymore since it was replaced by PreciousGuardian.exe. Basically you`ll need devcon.exe in the same folder of the miner and OverdriveNTool.
newbie
Activity: 205
Merit: 0
what coin uses this ultraheavy algo?
newbie
Activity: 61
Merit: 0
V1.4.2
- Small speedup on R9 380 cards

Can confirm, thanks!  Grin

@RaidoP2, what is the hashrate you are doing on RX380 and at what intensity and setings in config.txt?
Thanks.

With this version I'm running 37.6 intensity with double threads on my 380 and 380x cards. I have memory overclocked to 1600mhz and core underclocked to 850mhz, doing ~650h/s for 380x and ~600h/s for 380. This is for regular v7.

Probably could get some more out of them but I don't have time to tinker with it right now.
sr. member
Activity: 425
Merit: 250
V1.4.2
- Small speedup on R9 380 cards

Can confirm, thanks!  Grin

@RaidoP2, what is the hashrate you are doing on RX380 and at what intensity and setings in config.txt?
Thanks.
newbie
Activity: 61
Merit: 0
V1.4.2
- Small speedup on R9 380 cards

Can confirm, thanks!  Grin
newbie
Activity: 38
Merit: 0
is it a big latency 110ms ?
hero member
Activity: 2548
Merit: 626
I'm getting rejected for low difficulty shares and got my IP ban on V1.4.2 before this I was using V1.3.2 and it was ok...

or just use the right algo  Smiley
Jump to: