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

[ikyo]

I have updated to 1.6.6 on this machine, but I also ran the log to see if we could tell anything about the hash rate drop.  This is what it shows in the log (doesn't seem to show anything to me):

unfortunately i dont have a full rig of vegas, i have only one card im testing on, but what i noticed is that if i start mining, and use a browser for a few minutes the hashrate on cnv7 drops and never recovers back to the original one.
Also hash is lower while im connected to this machine on teamviewer/anydesk.

Maybe someone with much more experience with Vega rigs can help you. 

This machine is run headless with the iGPU used for display purposes and teamviewer.  This happens when I am not connected to it.  You are more than welcome to test stuff with me on this rig if you would want.  I also wonder if I setup up the watch dog setting, will it pretty much do a full reset of the miner just like me restarting it (rerun the startupscript and everything)?

[1575728321]

1575728321

[1575728321]

1575728321

[1575728321]

1575728321

[doktor83]

I have updated to 1.6.6 on this machine, but I also ran the log to see if we could tell anything about the hash rate drop.  This is what it shows in the log (doesn't seem to show anything to me):

unfortunately i dont have a full rig of vegas, i have only one card im testing on, but what i noticed is that if i start mining, and use a browser for a few minutes the hashrate on cnv7 drops and never recovers back to the original one.
Also hash is lower while im connected to this machine on teamviewer/anydesk.

Maybe someone with much more experience with Vega rigs can help you.  

This machine is run headless with the iGPU used for display purposes and teamviewer.  This happens when I am not connected to it.  You are more than welcome to test stuff with me on this rig if you would want.  I also wonder if I setup up the watch dog setting, will it pretty much do a full reset of the miner just like me restarting it (rerun the startupscript and everything)?

Why not try and set "min_rig_speed" parameter in config + add --resetvega in .bat.
This will trigger a miner restart on hashrate drop + restart the vegas with devcon before mining starts.

("min_rig_speed" parameter defines the average hashrate we want to maintain. If 5 min average hashrate is less than the value we defined, restart miner. This option expects you to enter a value in H/S)

[ikyo]

I have updated to 1.6.6 on this machine, but I also ran the log to see if we could tell anything about the hash rate drop.  This is what it shows in the log (doesn't seem to show anything to me):

unfortunately i dont have a full rig of vegas, i have only one card im testing on, but what i noticed is that if i start mining, and use a browser for a few minutes the hashrate on cnv7 drops and never recovers back to the original one.
Also hash is lower while im connected to this machine on teamviewer/anydesk.

Maybe someone with much more experience with Vega rigs can help you.  

This machine is run headless with the iGPU used for display purposes and teamviewer.  This happens when I am not connected to it.  You are more than welcome to test stuff with me on this rig if you would want.  I also wonder if I setup up the watch dog setting, will it pretty much do a full reset of the miner just like me restarting it (rerun the startupscript and everything)?

Why not try and set "min_rig_speed" parameter in config + add --resetvega in .bat.
This will trigger a miner restart on hashrate drop + restart the vegas with devcon before mining starts.

("min_rig_speed" parameter defines the average hashrate we want to maintain. If 5 min average hashrate is less than the value we defined, restart miner. This option expects you to enter a value in H/S)

That is perfect.  It does what I thought it would say I will start setting that on the rigs.  I added the resetvega this morning along with the new startup script to call Overdriventool.

[duyquang06]

- If using Blockchain drivers, hashing speed should be like it was before in ver 1.6.2


U save my vegas, again !

[doktor83]

- If using Blockchain drivers, hashing speed should be like it was before in ver 1.6.2


U save my vegas, again !

Just out of curiosity, why dont you use some of the preferred drivers?

[feekiller]

V1.6.6


+ DevFee mining is not displayed anymore to the user. The first devfee isn't mined in the first 5 minutes, so if you want to kill / restart the miner, set your scripts to do it before 5 minutes.
Also if using a custom algo switching software (that restarts the miner) , you are using the miner in normal mode (not algo switching mode), so the devfee is not tracked across switches.

NICE. OR ALL USE THIS:

DEVFEE = 0

Ver 1.6.4

Start.bat

start coin.bat
timeout 6970
taskkill SRBMiner-CN.exe
start start.bat



OR:
Start.bat

start "coin.bat"
timeout 6970
taskkill /F /IM "SRBMiner-CN.exe"
start "start.bat"

[christiano88]

V1.6.6


+ DevFee mining is not displayed anymore to the user. The first devfee isn't mined in the first 5 minutes, so if you want to kill / restart the miner, set your scripts to do it before 5 minutes.
Also if using a custom algo switching software (that restarts the miner) , you are using the miner in normal mode (not algo switching mode), so the devfee is not tracked across switches.

NICE. OR ALL USE THIS:

DEVFEE = 0

Ver 1.6.4

Start.bat

start coin.bat
timeout 6970
taskkill SRBMiner-CN.exe
start start.bat



OR:
Start.bat

start "coin.bat"
timeout 6970
taskkill /F /IM "SRBMiner-CN.exe"
start "start.bat"

Dude, just GTFO already...

[hmgp]

Thanks Dok! Trying Monero on nanopool and I have 4 Vega 56 - 2 are Sapphire, 1 is MSI, 1 is Powercolor, in case this detail matters. It goes off correctly, connects to the pool and just stays there getting jobs but doing zero shares... switch the miner and I have shares after 5 secs, but I really don't want to switch miner

Let's try this :

Working! Thank you =) Must have been something with the regedit I was doing before. I'll leave it for now and later on try to add the --resetvega, min_rig_speed and try to put the overdrive profiles on the start bat so it's called in the beginning.

Thanks again

[citronick]

doktor,

For pools file:

Can I put moneroocean pool as the first pool, and non-algo swicthing pool, ie xmr.nanopool in the subsequent pools.

I assume, sbrminer will lock in the first pool and will failover to 2nd pool when moneroocean pools goes offline.

At the moment this is working with 2 x Vega54 with latest blockchain drivers.

Thanks

[dragonmike]

At the moment this is working with 2 x Vega54...

Are these the extra-marital love children of a Vega 56 daddy and a Vega 64 mommy?

[citronick]

At the moment this is working with 2 x Vega54...

Are these the extra-marital love children of a Vega 56 daddy and a Vega 64 mommy?

LOL.... given the crypto bloodbath, your post really made my day... ha ha!

[doktor83]

doktor,

For pools file:

Can I put moneroocean pool as the first pool, and non-algo swicthing pool, ie xmr.nanopool in the subsequent pools.

I assume, sbrminer will lock in the first pool and will failover to 2nd pool when moneroocean pools goes offline.

At the moment this is working with 2 x Vega54 with latest blockchain drivers.

Thanks

it will detect that pool is not capable of algo switching, so it will revert back to normal mode (itt will turn off the --usealgoswitching)

[duyquang06]

- If using Blockchain drivers, hashing speed should be like it was before in ver 1.6.2


U save my vegas, again !

Just out of curiosity, why dont you use some of the preferred drivers?

Because it BlueScreenOfDeath everytime i install new driver, no matter which version, idk why, and yes i try so fucking many drivers version, so tired. So i just stick with Aug23.

[wgestickley]

Do i have to setup a own config file for xtl tu use Algo switch?

[doktor83]

Do i have to setup a own config file for xtl tu use Algo switch?

every algo you plan to use needs to have its own config file, because for example you use intensity 56 for heavy, but its not 56 for xtl.

[wgestickley]

Do i have to setup a own config file for xtl tu use Algo switch?

every algo you plan to use needs to have its own config file, because for example you use intensity 56 for heavy, but its not 56 for xtl.

Understood

5 supported algos - 5 configs

[doktor83]

Do i have to setup a own config file for xtl tu use Algo switch?

every algo you plan to use needs to have its own config file, because for example you use intensity 56 for heavy, but its not 56 for xtl.

Understood

5 supported algos - 5 configs

that's right. Its better this way because you can set everything separately for every algo, like min_rig_speed, reboot_script etc

[iisbetoq]

Do i have to setup a own config file for xtl tu use Algo switch?

every algo you plan to use needs to have its own config file, because for example you use intensity 56 for heavy, but its not 56 for xtl.

Understood

5 supported algos - 5 configs

that's right. Its better this way because you can set everything separately for every algo, like min_rig_speed, reboot_script etc

how about pools ? do i need make separated pools ? or just change on algos.txt
pools" : "pools-algoswitch.txt", to pools" : "pools-normalv7.txt",

[N2DCRYPT]

Dok, thanks for all your wonderful work on this miner, been on it for a while!

I'm curious, could you clarify how MoneroOcean works? I can figure most stuff out on my own, and I've got algoswitch algos and config files all setup and going, but one thing that confuses me is that I'm only getting NormalV7 jobs, even if I modify my algos.txt file for normalv7 hashes down to 200 H/s.

How can I verify and be sure that the switcher works and will switch to other algos when they're more profitable? Or does MoneroOcean decide what coin will be mined by all miners regardless of individual hashrate? Will appreciate any help!

[doktor83]

Do i have to setup a own config file for xtl tu use Algo switch?

every algo you plan to use needs to have its own config file, because for example you use intensity 56 for heavy, but its not 56 for xtl.

Understood

5 supported algos - 5 configs

that's right. Its better this way because you can set everything separately for every algo, like min_rig_speed, reboot_script etc

how about pools ? do i need make separated pools ? or just change on algos.txt
pools" : "pools-algoswitch.txt", to pools" : "pools-normalv7.txt",

At the moment only Monero Ocean is the only pool supporting this so you can set it in pools-algoswitch.txt :

{
"pools" :
[
{"pool" : "gulf.moneroocean.stream:10016", "wallet" : "your-xmr-wallet", "password" : "x"},
{"pool" : "de.moneroocean.stream:10016", "wallet" : "your-xmr-wallet", "password" : "x"},
]
}

then in algos.txt set on every algo the pool to pools-algoswitch.txt.

So you made only 1 pool file.