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

[doktor83]

doktor83

How to write "max_difficulty" if all parameters are in bat ?

SRBMiner-CN.exe --config Config\config.txt --ccryptonighttype normalv8 --cgpuid 0,1,2,3,4 --cgpuintensity 26,26,26,26,26 --cgputhreads 2,2,2,2,2 --cgpuworksize 32,32,32,32,32 --cpool pool.supportxmr.com:7777 --cwallet "wallet" --cpassword x

"keepalive"
"job_timeout"
"max_difficulty"

Can't be set in cmd, but it's not a bad idea to implement them

[1610940467]

1610940467

[1610940467]

1610940467

[1610940467]

1610940467

[1610940467]

1610940467

[Marvell2]

Vega FE miner performance is horrible compared to where it should be. It’s not just this miner but other miners have the same performance issue. Just wondering if the mining dev team is looking into this.

The problem is i don't have a FE, so i can't really do anything

Not your fault Dok, it's not the miner, it's more a driver thing. Thanks for your patience, I'm sure the complaints get old after a while.
And double thanks for your continued development on what I believe is the best cryptonight miner around!

To those w/ FEs:

driver: win10-64bit-radeon-pro-software-enterprise-18.q3.1-oct1

But a couple of tricks you have to use to pull it off:

1. go into global settings and turn off HBCC memory.
2. if using SRBMiner, you have to have --enableduplicategpuid in the bat file, and then double up the threads in the config file for V8. I'm using 124 for intensity and 16 for worksize.

FE still the king, hashing V8 @ ~2125 H/s

one other thing: use the precompiled kernel that comes with SRBMiner, do not compile the kernel with the new drivers.

i use the tool to turn hbcc off thats not my issue, I am using the 18.5.2 drivers(may) though
what does enableduicategpuid do , can you post your full batch file fir FEs and your config setting?

also how do you force the use of precmplied kernels, Srb always compiles kernels on startup

thanks

[peteris-apse]

monero v8 made some instability to my vega rig so i lovered intensity from 120 to 100. Little less hasharate, but it is stable for few days.
12800 h/s on 7x vega 56 rig
1100w
1800-1850 hs on per card.

[R4fik]

Hey guys anyone have good Do you have nice settings for rx570? I used 40 pieces rx 570 and could not run properly

[dragonmike]

I'm just struggling with the Vegas.
Doesn't seem to matter whether I increase voltage or lower clocks, after a few minutes mining Monerov8, all GPUs go boom, i.e. SRBminer says hashrate is zero for every single card... and it will fail automatic re-initialisation.

Using 120/16/2. They're all 56's flashed to 64.
Maybe I'm just at the limit of what the PSU is able to cope with... Power draw is between 1400 and 1435 for a EVGA 1500 G2...

hmm .Mybe. my 6 nitro+ vega 56 use 1170W on V8 and 970W on V7 from the wall. i have 2*750W PSU and all work...

just try mining with 5 vega.

just del last gpu { "id" : 5, "intensity" : 120, "worksize" : 16, "threads" : 2},

and try.

if work your PSU is problem

1170W from the wall? That's pretty good... What frequencies and voltages are you using? I know I've got one card that's struggling but I have yet to find time to isolate it and test with different frequencies & voltages. Anything under Mem_P3@975mV will not initialise it.

6*vega56 nitro+ (hynix) - GPU: 1498/900mv MEM: 929/936/958mhz -900mv (3 card work with 958mhz - 2card 936mhz 1 card 929mhz -all use 900mv

V7 970W(11650HR) - V8 1270W(11120HR) - FAST 1020W(22600HR) - Heavy 940W(9110HR) - TUBE 960W(9380HR)

Ah you haven't flashed them, ok.
Still pretty good all together. And the hash/power ratio is nice.

[Dowper_]

When I start the miner all my RAM fulls up and the rig crashes, any ideas?

[Amigo9881]

monero v8 made some instability to my vega rig so i lovered intensity from 120 to 100. Little less hasharate, but it is stable for few days.
12800 h/s on 7x vega 56 rig
1100w
1800-1850 hs on per card.

Can you please share your ppt table ? my wattages are too high.

Thanks

[hesido]

I'd like to share my latest windows clean install adventure:

8x 8MB Rx580's all OC settings the same for each try

• Windows 10, build 1703 + 18.3.2 = very good on 1.6.7, good on 1.6.8 (CN-Heavy Hashrate maxes out at 8600 h/s) -Sometimes crashes on algo change, all cards maxes h/s
• Clean install of Windows 10, build 1803 + recommended driver 18.6.1 = shit (7600 h/s)
• Clean install of Windows Enterprise, build whatever + recommended driver 16.8.1 = somewhat shit (7800 h/s)
• Windows Enterprise + 18.3.2 = good (8200 h/s) -> This is what I'm doing right now. Seems to be stable on algo change, although randomly 2-4 cards would hash at shit speeds.

So the newer windows builds are shit, and Adrenalin 18.6.1 is not doing me any favors. Couldn't try 18.5.x with so much downtime biting my ass.
I'm not hashing v8 anymore because I'm losing to much hash with the 18.6.1 drivers, even on clean windows installs.

Anxiously waiting for the new version, I hope Doktor can do his magic once again.

[dragonmike]

I'd like to share my latest windows clean install adventure:

8x 8MB Rx580's all OC settings the same for each try

• Windows 10, build 1703 + 18.3.2 = very good on 1.6.7, good on 1.6.8 (CN-Heavy Hashrate maxes out at 8600 h/s) -Sometimes crashes on algo change, all cards maxes h/s
• Clean install of Windows 10, build 1803 + recommended driver 18.6.1 = shit (7600 h/s)
• Clean install of Windows Enterprise, build whatever + recommended driver 16.8.1 = somewhat shit (7800 h/s)
• Windows Enterprise + 18.3.2 = good (8200 h/s) -> This is what I'm doing right now. Seems to be stable on algo change, although randomly 2-4 cards would hash at shit speeds.

So the newer windows builds are shit, and Adrenalin 18.6.1 is not doing me any favors. Couldn't try 18.5.x with so much downtime biting my ass.
I'm not hashing v8 anymore because I'm losing to much hash with the 18.6.1 drivers, even on clean windows installs.

Anxiously waiting for the new version, I hope Doktor can do his magic once again.

What intensities are you running the cards at?
I just lowered my Vegas from 120 to 112. Not too sure why I thought going higher for v8 was ever going to be a good idea... just followed blindly what was written here as "suggestion".

So far all the Vegas are hashing fine - I isolated my flaky card and run slightly lower clocks and higher voltage on it to be on the safe side. So touch wood, I think I've solved my problems...

[Amigo9881]

Vega FE miner performance is horrible compared to where it should be. It’s not just this miner but other miners have the same performance issue. Just wondering if the mining dev team is looking into this.

The problem is i don't have a FE, so i can't really do anything

Not your fault Dok, it's not the miner, it's more a driver thing. Thanks for your patience, I'm sure the complaints get old after a while.
And double thanks for your continued development on what I believe is the best cryptonight miner around!

To those w/ FEs:

driver: win10-64bit-radeon-pro-software-enterprise-18.q3.1-oct1

But a couple of tricks you have to use to pull it off:

1. go into global settings and turn off HBCC memory.
2. if using SRBMiner, you have to have --enableduplicategpuid in the bat file, and then double up the threads in the config file for V8. I'm using 124 for intensity and 16 for worksize.

FE still the king, hashing V8 @ ~2125 H/s

one other thing: use the precompiled kernel that comes with SRBMiner, do not compile the kernel with the new drivers.

confirmed: When turning off hbcc Vega FE gets 2125

but when miner switch algo to heavy, vega FE is getting `500 h/s

how did you solve this ?

[Bojcha]

For those who have problems with FE
HBBC=OFF(any vega) and Largepags=ON

[livada]

I'm just struggling with the Vegas.
Doesn't seem to matter whether I increase voltage or lower clocks, after a few minutes mining Monerov8, all GPUs go boom, i.e. SRBminer says hashrate is zero for every single card... and it will fail automatic re-initialisation.

Using 120/16/2. They're all 56's flashed to 64.
Maybe I'm just at the limit of what the PSU is able to cope with... Power draw is between 1400 and 1435 for a EVGA 1500 G2...

hmm .Mybe. my 6 nitro+ vega 56 use 1170W on V8 and 970W on V7 from the wall. i have 2*750W PSU and all work...

just try mining with 5 vega.

just del last gpu { "id" : 5, "intensity" : 120, "worksize" : 16, "threads" : 2},

and try.

if work your PSU is problem

1170W from the wall? That's pretty good... What frequencies and voltages are you using? I know I've got one card that's struggling but I have yet to find time to isolate it and test with different frequencies & voltages. Anything under Mem_P3@975mV will not initialise it.

6*vega56 nitro+ (hynix) - GPU: 1498/900mv MEM: 929/936/958mhz -900mv (3 card work with 958mhz - 2card 936mhz 1 card 929mhz -all use 900mv

V7 970W(11650HR) - V8 1270W(11120HR) - FAST 1020W(22600HR) - Heavy 940W(9110HR) - TUBE 960W(9380HR)

what does your full system pull from the wall ? with V8 not just the cards

yes. this is 1 rig(6card + 6 extra fan from the wall)

[11th_miner]

I'd like to share my latest windows clean install adventure:

8x 8MB Rx580's all OC settings the same for each try

• Windows 10, build 1703 + 18.3.2 = very good on 1.6.7, good on 1.6.8 (CN-Heavy Hashrate maxes out at 8600 h/s) -Sometimes crashes on algo change, all cards maxes h/s
• Clean install of Windows 10, build 1803 + recommended driver 18.6.1 = shit (7600 h/s)
• Clean install of Windows Enterprise, build whatever + recommended driver 16.8.1 = somewhat shit (7800 h/s)
• Windows Enterprise + 18.3.2 = good (8200 h/s) -> This is what I'm doing right now. Seems to be stable on algo change, although randomly 2-4 cards would hash at shit speeds.

So the newer windows builds are shit, and Adrenalin 18.6.1 is not doing me any favors. Couldn't try 18.5.x with so much downtime biting my ass.
I'm not hashing v8 anymore because I'm losing to much hash with the 18.6.1 drivers, even on clean windows installs.

Anxiously waiting for the new version, I hope Doktor can do his magic once again.

What intensities are you running the cards at?
I just lowered my Vegas from 120 to 112. Not too sure why I thought going higher for v8 was ever going to be a good idea... just followed blindly what was written here as "suggestion".

So far all the Vegas are hashing fine - I isolated my flaky card and run slightly lower clocks and higher voltage on it to be on the safe side. So touch wood, I think I've solved my problems...

I have vega 64 and I had same problem, rig was stable for 6 to 18 hours and then crash, first tought it was power issue and removed one card from rig but same problem,managed to find a flaky card (which wasn't flaky on v7 ,maybe it is not flaky) removed it and again crash; lowered the intensity to 116, after 24 hours so far so good

[Boss_One]

Hi there

I'm back with my old grand ma card AMD 6950  

Ive try the lastest release since the fork V8 monero and i can't hash

This old pre gcn card work on V7, it could hash on V8 too ? ( i know it's very old card ) but i've 3 cards at work ...

i've try kernel cmd line --kernel 1 or 2 and it didn't start hashing.
The is a way to use specific kernel for this old card with a special command line ?

Thx

[Bare]

Hi guys!

Over the last few days I played with the SRBminer settings on my 390[hawaii] and fury[fiji] cards
and I wanna share my settings with the best results I've got for this v8 algo.

390 cards hash around 760 H/s with these settings

{ "id" : 0, "intensity" : 47, "worksize" : 16, "threads" : 2, "kernel" : 1, "persistent_memory" : true, "adl_type" : 1}

fury cards hash around 650 H/s with these settings

{ "id" : 1, "intensity" : 78, "worksize" : 16, "threads" : 1, "kernel" : 1, "persistent_memory" : true, "adl_type" : 1}
I observe for fury cards sometimes you can use worksize 8 if you get lower hashrate or 16 if you get lower hashrate with 8

OS:      Win 10 Pro v1709
Drivers: Adrenalin 18.6.1

I've tested worksizes 4-32,
Played mostly with intensities trying to find the sweet spot together with double and single thread usages,
Persistent memory mostly helps hawaii cards squeeze around 10-15 extra hashes, didn't observe any difference if there is any for fijis.
If you're gonna set "kernel" : 2, best to set "adl_type" : 2 too but I didn't manage to squeeze more hashes than with "kernel" : 1, "adl_type" : 1
as long as you don't mix "kernel" : 2, "adl_type" : 1  OR "kernel" : 1, "adl_type" : 2 you won't have bad hashrates (I don't remember exactly, something like around 500 h/s on both cards)

Previously on the claymore v11.3 algo v7 I was getting around 800 H/s for 390s and the same for furys too
So it's not as much big difference switching from v7 to v8 for hawaii cards as it is for furys

So I'm asking you guys who have fijis, what are your results, did somebody manage to get better results with fijis on v8 srbminer and of course share your settings

Thanks!

 

[hesido]

I'd like to share my latest windows clean install adventure:

8x 8MB Rx580's all OC settings the same for each try

• Windows 10, build 1703 + 18.3.2 = very good on 1.6.7, good on 1.6.8 (CN-Heavy Hashrate maxes out at 8600 h/s) -Sometimes crashes on algo change, all cards maxes h/s
• Clean install of Windows 10, build 1803 + recommended driver 18.6.1 = shit (7600 h/s)
• Clean install of Windows Enterprise, build whatever + recommended driver 16.8.1 = somewhat shit (7800 h/s)
• Windows Enterprise + 18.3.2 = good (8200 h/s) -> This is what I'm doing right now. Seems to be stable on algo change, although randomly 2-4 cards would hash at shit speeds.

So the newer windows builds are shit, and Adrenalin 18.6.1 is not doing me any favors. Couldn't try 18.5.x with so much downtime biting my ass.
I'm not hashing v8 anymore because I'm losing to much hash with the 18.6.1 drivers, even on clean windows installs.

Anxiously waiting for the new version, I hope Doktor can do his magic once again.

What intensities are you running the cards at?
I just lowered my Vegas from 120 to 112. Not too sure why I thought going higher for v8 was ever going to be a good idea... just followed blindly what was written here as "suggestion".

So far all the Vegas are hashing fine - I isolated my flaky card and run slightly lower clocks and higher voltage on it to be on the safe side. So touch wood, I think I've solved my problems...

I use the default intensities (56) for Rx580. Right now though it began hashing again at 8500, after a 2-3 hours though (it goes for 8200-8250 for quite a while), better late than never, awesome. Sometime 1 or two cards do get stuck at low hashrates, that's quite unpredictable. But ultimately, 18.6.1 is still a bad choice for my mining (Currently 18.3.2 is doing mighty fine) as the max it can go has been 7800 on my rig, even after hours.

[Bare]

Hi there

I'm back with my old grand ma card AMD 6950 

Ive try the lastest release since the fork V8 monero and i can't hash

This old pre gcn card work on V7, it could hash on V8 ? ( i know it's old) but i've 3 card at work ...

i've try kernel cmd line --kernel 1 or 2 and it didn't start hashing.
The is a way to use specific kernel for this old card with a special command line ?

Thx

Since you're using an older card I'd suggest you try "kernel" : 2 together with "adl_type" : 2
because it's set by default  "adl_type" : 1 which is better for newer cards.

you can set it in config-normalv8.txt not in batch afaik, ReadMe is your friend! and take care not to forget a comma[,] or something +when editing config-normalv8.txt otherwise your miner won't work.

[Bare]

I'd like to share my latest windows clean install adventure:

8x 8MB Rx580's all OC settings the same for each try

• Windows 10, build 1703 + 18.3.2 = very good on 1.6.7, good on 1.6.8 (CN-Heavy Hashrate maxes out at 8600 h/s) -Sometimes crashes on algo change, all cards maxes h/s
• Clean install of Windows 10, build 1803 + recommended driver 18.6.1 = shit (7600 h/s)
• Clean install of Windows Enterprise, build whatever + recommended driver 16.8.1 = somewhat shit (7800 h/s)
• Windows Enterprise + 18.3.2 = good (8200 h/s) -> This is what I'm doing right now. Seems to be stable on algo change, although randomly 2-4 cards would hash at shit speeds.

So the newer windows builds are shit, and Adrenalin 18.6.1 is not doing me any favors. Couldn't try 18.5.x with so much downtime biting my ass.
I'm not hashing v8 anymore because I'm losing to much hash with the 18.6.1 drivers, even on clean windows installs.

Anxiously waiting for the new version, I hope Doktor can do his magic once again.

What intensities are you running the cards at?
I just lowered my Vegas from 120 to 112. Not too sure why I thought going higher for v8 was ever going to be a good idea... just followed blindly what was written here as "suggestion".

So far all the Vegas are hashing fine - I isolated my flaky card and run slightly lower clocks and higher voltage on it to be on the safe side. So touch wood, I think I've solved my problems...

I use the default intensities (56) for Rx580. Right now though it began hashing again at 8500, after a 2-3 hours though (it goes for 8200-8250 for quite a while), better late than never, awesome. Sometime 1 or two cards do get stuck at low hashrates, that's quite unpredictable. But ultimately, 18.6.1 is still a bad choice for my mining (Currently 18.3.2 is doing mighty fine) as the max it can go has been 7800 on my rig, even after hours.

I observed my fury cards sometimes getting stuck at lower hashrates, changing worksizes for those cards helped, dunno what your default worksizes are for Rx580 but it helped my furys changing from 16 to 8 and vice versa

[Boss_One]

Hi there

I'm back with my old grand ma card AMD 6950  

Ive try the lastest release since the fork V8 monero and i can't hash

This old pre gcn card work on V7, it could hash on V8 ? ( i know it's old) but i've 3 card at work ...

i've try kernel cmd line --kernel 1 or 2 and it didn't start hashing.
The is a way to use specific kernel for this old card with a special command line ?

Thx

Since you're using an older card I'd suggest you try "kernel" : 2 together with "adl_type" : 2
because it's set by default  "adl_type" : 1 which is better for newer cards.

you can set it in config-normalv8.txt not in batch afaik, ReadMe is your friend! and take care not to forget a comma[,] or something +when editing config-normalv8.txt otherwise your miner won't work.

I've try what you say but miner doesn't start anymore  

Any idea ? i can't install adrenaline driver suggest, the card is not compatible.

"Please use : Adrenalin 18.5.1, 18.5.2 or 18.6.1 drivers
Total pools: 2

Please wait...

CryptonightV8 mode enabled

[2018-10-22 14:45:42] Heating up system, please wait...
[2018-10-22 14:45:42] GPU model not recognised or it is not GCN architecture ...
[2018-10-22 14:45:42] Let's check if we can compile the stuff ...
[2018-10-22 14:45:42] Error CL_COMPILE_PROGRAM_FAILURE when calling clCompileProgram [ctx->headers[0]] for DeviceID 0 (Thread 0)

[Njeroe]

The software sees 2 different GPUs on the same PCI Bus, the first one is an RX 570 8Gb and it is supposed to be on PCI Bus 13, is it a driver problem (18.5.1) or the miner software is bugged? Also the hashrate report shows like it was 2 GPUs, I mean 850 H/s x2...

[2018-10-22 15:23:58] GPU1: Radeon RX 580 Series [ellesmere] [8192 MB][Intensity 59.0][W: 8][T: 2][K: 1][BUS: 2]
[2018-10-22 15:23:58] GPU2: Radeon RX 580 Series [ellesmere] [4096 MB][Intensity 59.0][W: 8][T: 2][K: 1][BUS: 2]

GPU1 : 1712 H/s [T: 74c, RPM: 0, CC: 1220 MHz, MC: 2010 MHz][BUS:2]