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

[bucah]

Vega owners, check your hotspot temps. My Vega didnt survive the night mining v8 even when I dropped the core to 1250@865mV
And a big fat F U to Monero devs

My Vega 56 seems normal for me. HBM temp at 66-67, up from around 62-63

It is my Vega 64 that I worry about. The temp is rising up to 72 from around 66-67

Core temps are not very much different. All are reference cards.

FYI, my rigs are on open air with no AC, here in Indonesia with up to 37 degrees Celcius of room temp.

I suggest you to try Power Color Red Dragon series. I have 1 of these and it is the coolest Vega I have.
Core temp on Red Dragon Vega 56 is up to 53 compare with reference up to 60-61
HBM temp on Red Dragon is 59-60 compare with reference up to 67
All are on V8

[Lno]

I have 5 vega56 Adrenalin 18.6.1
3 gfx 900 give by 1850 ~
2 gfx 901 give 1000 ~
what is the problem?

GPU 1,3 does not issue hashrate
https://yadi.sk/i/bRsgGNEm0T1SZw
https://yadi.sk/d/flYEAz8TeHSvtg

[tanatana]

After softfork 8.0 on Monero network, this miner became one of the best for AMD cards. Unfortunately, it does not support cards of the R9 280 generation. It would be nice to add support for these old, but rather productive video cards.

I thought this miner works with Tahiti cards R9 280's. I know that it supports Hawaii - 290 and 390's, so why not 280's?

Anyone still mining with the older Radeon 7970/280X or the R9 290 GPUs?

Was wondering what config you guys are using and what stability you guys get with this software, I am looking for an alternative to the Claymore XMR miner which will become obsolete when XMR forks on Oct 18th.

I tried to run the srmbminer on my 7970 with settings --cgpuintencity 15 --cgpuworksize 8 -cgputhreads 2, at the stock frequencies (925/1375) I got 360H / s on v7, its less than old claymore 11.3 (450)... but clay not support v8

PS Guys when need to change algo for Monero mining? Any dates?

Confirm that, but with intensity 27 i got even more hashes on v7.
Now my 7970 with 1125/1500 clocks on v8
intencity 31
worksize 8
threads 2
485 H/s
12 Hrs stable

no clock all default 1000@1500 card 7970, miner SRB
https://i.imgur.com/6k0yjTc.png

{
"cryptonight_type" : "normalv8",
"intensity" : 0,
"gpu_conf" :
[
   { "id" : 0, "intensity" : 60, "worksize" : 8, "threads" : 1}

]
}

[CharlieCox]

A loyal SRBMiner user here. According to Nanopool, my Vega rig has gotten more profitable thanks to the yesterday's fork. The approximated earnings calculator says cca 25% more profitable in terms of XMR and USD earnings.

If it uses 10% more electricity (I'm yet to check the exact number), it's still OK. I suspect the diff parameter has dropped, which is good.

Poz doktore!

[huntingthesnark]

I have 5 vega56 Adrenalin 18.6.1
3 gfx 900 give by 1850 ~
2 gfx 901 give 1000 ~
what is the problem?

GPU 1,3 does not issue hashrate
https://yadi.sk/i/bRsgGNEm0T1SZw
https://yadi.sk/d/flYEAz8TeHSvtg

Me too. Driving me bonkers.

[dragonmike]

Guys, seriously.
So many noobs in here lately.

1. v8 is not v7. It's a new algo version, it hashes a bit slower and draws more power. It's the same for everyone. Deal with it.
2. Monero difficulty adjust slowly over several blocks. If hashrate drops suddenly it will not become profitable immediately. Read up.
3. More power draw = more heat being produced. At the same cooling level it means your cards will run hotter. Increase cooling or deal with extra heat.

And a big fat F U to Monero devs

If the devs had not forked the algo, your Vega (that you didn't spend time testing with) would have become useless to mine XMR with within the scope of a few weeks.
Dimwit.

[x3t9fi]

About 50MH/s Network-Hash Drop after the Fork... What do you think - Some ASIC's and the GPU-Rig Drops?

[p3yot33]

So, is anybody else having problems with nicehash compatibility on this new version with v8 algo?
I am getting all "shares above target" if I run v8 with it.
Otherwise the hashrate is pretty much unchanged.

Could someone with nicehash config paste their pool lines since it seems I am too dumb to have it set correctly or the miner is broken...?
Mine is:

{
"pools" :
[
   {"pool" : "cryptonightv8.eu.nicehash.com:3367", "wallet" : "N/A", "password" : "x", "nicehash" : true},
   {"pool" : "cryptonightv8.usa.nicehash.com:3367", "wallet" : "N/A", "password" : "x", "nicehash" : true}
]
}

[CharlieCox]

1. v8 is not v7. It's a new algo version, it hashes a bit slower and draws more power. It's the same for everyone. Deal with it.

Exactly. This hash rate drop doesn't affect anybody's earnings in a negative way. You get your rewards proportionally, which means you will still earn as many XMR as before the fork. Keep it real guys.

The only issue could be increased power consumption and heat. I always preferred to mine XMR over ETH, since ETH uses more power and generates more heat. Thankfully, winter is coming in Europe so extra heat won't be an issue for a while.

[abg00]

So, is anybody else having problems with nicehash compatibility on this new version with v8 algo?
I am getting all "shares above target" if I run v8 with it.
Otherwise the hashrate is pretty much unchanged.

Could someone with nicehash config paste their pool lines since it seems I am too dumb to have it set correctly or the miner is broken...?
Mine is:

{
"pools" :
[
   {"pool" : "cryptonightv8.eu.nicehash.com:3367", "wallet" : "N/A", "password" : "x", "nicehash" : true},
   {"pool" : "cryptonightv8.usa.nicehash.com:3367", "wallet" : "N/A", "password" : "x", "nicehash" : true}
]
}

   {"pool" : "cryptonightv8.usa.nicehash.com:3367", "wallet" : "N/A", "password" : "x", "nicehash" : true},

[Pabu7]

Is the hashrate showed on the miner real?
I'm mining on supportxmr for 12hours now and my avg is in 4.72kh/s, the miner shows 5.42kh/s.
Before the fork I was using version 1.4.3, and my avg on the pool was 5.56kh/s, more or less the same that the miner showed.
I was using it with greedisgood, but even accounting for the miner fee 4.72 is too low compared to 5.42, it's almost 13% and not 0.85% of the total.
On xmr-stak I get about 4.9kh/s, minus the fee I will still get 4.85kh/s. That's why I ask if the hashrate shown is real.

[ntshb]

this is all i need to set in the config v8 file right?

{
"cryptonight_type" : "normalv8",
"intensity" : 0,
"double_threads" : true
"min_rig_speed" : 7000
}

do i need to include "reboot_script_min_rig_speed" : (??)

[kristikun]

im getting really sweet hashrates thx for hard work , wanted to ask about todays monero V9 Fork is  miner suporting it ?

[seefatlow]

Just to share my v8 Vega hashrates

Rx Vega 64(Samsung)  1941 H/s T: 61C CC 1448 MhZ MC 1050MHz
Rx Vega 56(Samsung)  1892 H/s T: 59C CC 1448 MHz MC 910 MHz
RX Vega 56 (Hynix) 1811 H/s T:62C CC 1448 MHz MC 910 MHz

Intensity 120/12/2

9 Vega Rig - 1950 W out of the wall power draw

[CharlieCox]

9 Vega Rig - 1950 W out of the wall power draw

Did you undervolt?

[seefatlow]

9 Vega Rig - 1950 W out of the wall power draw

Did you undervolt?

Most definitely

[ntshb]

1107w for 4 vega 64 is quite high isn't it?

[nightfury626]

can anyone help me, after switching from monero7 to monero8, my hashrates went from 2156 to 1275. what extra stuff is needed with this fork to get my hashrates back please?

[Bojcha]

Vega owners, check your hotspot temps. My Vega didnt survive the night mining v8 even when I dropped the core to 1250@865mV
And a big fat F U to Monero devs

Completely your fault. Many times was repeated - do not look GPU temp. Every Vega need to be set at 50c gpu temp (which is minimum by driver) and then HotSpot and HBM2 temps will be ok.

[goran89]

Strange thing with v8 is that my 570's hashrate is same (950 H/s) but my 580's droped from 1025 to 975 H/s. I use same settings just changed worksize from 8 to 16 and my power consumption went up for about 80-85 W for 5 cards.

On friends rig I also have problem with "Initialising open CL driver/cards...." It just stuck on that after I start miner. We have same windows version (1709), same driver (18.6.1) and same miner but on his rig it won't start.
Any solution (don't want to reinstall whole windows again  ) ?