|
I will check this fast algo thing.
You guys have enough size for pagefile?
|
|
|
|
|
I added a full copy paste example on how to use algo switching on Monero Ocean.
Check it out on the first page
|
|
|
|
Hi, Thanks for this awesome miner!
But two of rigs throws the following issue today and restarted :
"The Interactive Services Detection service terminated with the following error: Incorrect function."
- <EventData>
<Data Name="param1">Interactive Services Detection</Data>
<Data Name="param2">%%1</Data>
<Binary>5500490030004400650074006500630074000000</Binary>
</EventData>
</Event>
Is that any solution for this issue =)?
I'm not sure this is miner related at all as : Interactive Services Detection (the blinking button on the taskbar). Blinking button on the taskbar  |
|
|
|
Hi Dok
Can i use gpu0123 with normalv7 and gpu456 with heavy? need run two copy of miner? or add in config two section for different algo? use 1.6.6 now
If you want to do algo switching then you must do it in config files, if you want to mine 'normally' you can do it either way. SRBMiner-CN.exe --ccryptonighttype normalv7 --cgpuid 0,1,2,3 --cgpuintensity 0,0,0,0 --cgputhreads 2,2,2,2 --cpool POOL --cwallet WALLET --cpassword x --sendallstales SRBMiner-CN.exe --ccryptonighttype heavy --cgpuid 4,5,6 --cgpuintensity 0,0,0 --cgputhreads 2,2,2 --cpool POOL --cwallet WALLET --cpassword x --sendallstales |
|
|
|
Something is wrong, when trying to force haven (only adding this algo to algos.txt) it says it cannot login the user to the pool (using monero ocean + enablealgoswitching parameter). With bittube and v7 it works fine. I see haven listed on their website, so why is it not working?
you are using your Monero wallet for login, not haven, right ? Exactly. Since the payment are done in XMR, I figured it would be the right thing to do. Also, for bittube it works just fine. Also wrote to moneroocean team on discord and you replied, but that solution is already applied from the beginning.L.E. Nevermind, it works now, it seems that it must first start in normalv7, then pool will request the most profitable coin, and it was able to switch to haven. You can start it with any algo, haven, stellite doesn't matter, it will switch to the algo the pool requested when connected. |
|
|
|
Something is wrong, when trying to force haven (only adding this algo to algos.txt) it says it cannot login the user to the pool (using monero ocean + enablealgoswitching parameter). With bittube and v7 it works fine. I see haven listed on their website, so why is it not working?
you are using your Monero wallet for login, not haven, right ? |
|
|
|
Hi doktor, I was using version 1.6.3 in my vega 56, using the 1.6.6 i got less 30 hs Using same settings, On other rigs with rx 580 and vega 64 got the same hashes. Just reporting  Tell him which driver you using. and which algo is it Hi doc, Using the recommended 1.6.1, The algo is Heavy, mining LOKI. ( 1 vega 56 mining solo) I have other strange issue in other rig (9 vegas 64) in fast algo mining masari. When i start miner 1 gpu (Vega 64) stills on 36xx hs and the others 8 in 40xx hs. Is i restart is random the gpu that will hash less that others. (But this behavior is not always, if i restart many times, one time will be ok , all performing the same.. very strange) Thanks wait now, did you want to write 18.6.1 ? Or miner version 1.6.1  |
|
|
|
--logfile log.txt does not seem to do anything if set in the start.bat command line when using auto-switching now. None of my rigs have created a file it seems. Is that something that can be fixed?
Don't know what is happening there because it created log when i was doing the development. Just put the --logfile log-switching.txt in start.bat and it is used on every algo switch. |
|
|
|
Ok, so i have to set it in each config file... Can you please check whats wrong here:
{
"cryptonight_type" : "fast",
"target_temperature" : 64,
"intensity" : 59,
"double_threads" : true
"gpu_conf" :
[
{ "id" : 3, "intensity" : 54.5, "worksize" : 8, "threads" : 2},
]
}
you are missing a comma after "double_threads" : true |
|
|
|
Good Morning,
i have trouble to run 2 different instances of SRB Miner with the new Algo Switching Option.
While i have a rig with 5xRX570 and 1XRX580, i want to run the Miner bundeld for the Cards. So 1X with the 570ies and 1X with the RX580.
The GPU ID for the 580 is 3 and i put this in the start.bat
SRBMiner-CN.exe --config config-fast.txt --cgpuid 3 --cgpuintensity 60.5 --cgputhreads 2 --pools pools-algoswitch.txt --sendallstales --usealgoswitching
The Miner closes instently after start. When i dont exclude any GPU (all 6 togehter) it runs fine....
Thank you
put pause after the SRBMiner-CN.exe --config config-fast.txt... line so the window wont close on error, and you can see what is the error, like this : SRBMiner-CN.exe --config config-fast.txt --cgpuid 3 --cgpuintensity 60.5 --cgputhreads 2 --pools pools-algoswitch.txt --sendallstales --usealgoswitching pause ccryptonighttype valid values: [normal, normalv7, lite, litev7, heavy, bittubev2, artocash, alloy, marketcash, b2n, stellitev4, haven, fast, italo, mox] Drücken Sie eine beliebige Taste . . . *** And my config-fast.txt is like this { "cryptonight_type" : "fast", "target_temperature" : 64, "intensity" : 59, "double_threads" : true } Make it look like this : SRBMiner-CN.exe --ccryptonighttype fast --config config-fast.txt --cgpuid 3 --cgpuintensity 60.5 --cgputhreads 2 --pools pools-algoswitch.txt --sendallstales --usealgoswitching And now it will use intensity 60.5 instead of 59 you defined in config. CMD parameters are always "stronger" than the ones in config file. Now he detects only this 1 specified GPU... BUT :-) Pool send a new job for bittubev2, he starts initializing it and is in an endless loop of initializing betwen fast and bittubev2.... Hmmmm.... oh yes, there is something on the first page that says : It is VERY IMPORTANT to use config files here, and not set GPU's and pool in command line. If you do so, algo switching probably won't work. |
|
|
|
Good Morning,
i have trouble to run 2 different instances of SRB Miner with the new Algo Switching Option.
While i have a rig with 5xRX570 and 1XRX580, i want to run the Miner bundeld for the Cards. So 1X with the 570ies and 1X with the RX580.
The GPU ID for the 580 is 3 and i put this in the start.bat
SRBMiner-CN.exe --config config-fast.txt --cgpuid 3 --cgpuintensity 60.5 --cgputhreads 2 --pools pools-algoswitch.txt --sendallstales --usealgoswitching
The Miner closes instently after start. When i dont exclude any GPU (all 6 togehter) it runs fine....
Thank you
put pause after the SRBMiner-CN.exe --config config-fast.txt... line so the window wont close on error, and you can see what is the error, like this : SRBMiner-CN.exe --config config-fast.txt --cgpuid 3 --cgpuintensity 60.5 --cgputhreads 2 --pools pools-algoswitch.txt --sendallstales --usealgoswitching pause ccryptonighttype valid values: [normal, normalv7, lite, litev7, heavy, bittubev2, artocash, alloy, marketcash, b2n, stellitev4, haven, fast, italo, mox] Drücken Sie eine beliebige Taste . . . *** And my config-fast.txt is like this { "cryptonight_type" : "fast", "target_temperature" : 64, "intensity" : 59, "double_threads" : true } Make it look like this : SRBMiner-CN.exe --ccryptonighttype fast --config config-fast.txt --cgpuid 3 --cgpuintensity 60.5 --cgputhreads 2 --pools pools-algoswitch.txt --sendallstales --usealgoswitching And now it will use intensity 60.5 instead of 59 you defined in config. CMD parameters are always "stronger" than the ones in config file. |
|
|
|
Good Morning,
i have trouble to run 2 different instances of SRB Miner with the new Algo Switching Option.
While i have a rig with 5xRX570 and 1XRX580, i want to run the Miner bundeld for the Cards. So 1X with the 570ies and 1X with the RX580.
The GPU ID for the 580 is 3 and i put this in the start.bat
SRBMiner-CN.exe --config config-fast.txt --cgpuid 3 --cgpuintensity 60.5 --cgputhreads 2 --pools pools-algoswitch.txt --sendallstales --usealgoswitching
The Miner closes instently after start. When i dont exclude any GPU (all 6 togehter) it runs fine....
Thank you
put pause after the SRBMiner-CN.exe --config config-fast.txt... line so the window wont close on error, and you can see what is the error, like this : SRBMiner-CN.exe --config config-fast.txt --cgpuid 3 --cgpuintensity 60.5 --cgputhreads 2 --pools pools-algoswitch.txt --sendallstales --usealgoswitching pause |
|
|
|
Hi doktor, I was using version 1.6.3 in my vega 56, using the 1.6.6 i got less 30 hs Using same settings, On other rigs with rx 580 and vega 64 got the same hashes. Just reporting Tell him which driver you using. and which algo is it |
|
|
|
I've got a question about the reboot script when using pool switching: do you have to set it for each algo separately or can you just add it at the end of the start.bat command line?
...Doc? reboot script is the one you add in config.txt, so yes, add it in every config. That is handy because maybe your heavy algo clock settings in overdriventool are not the same as for v7, so on every algo start it will run the appropriate batch file. |
|
|
|
The trick is working on "v7" algos, on heavy, tube, haven nope  |
|
|
|
Hey,
while playing around with auto switch, I was wondering, if there is an detailed overview for GPUs with best settings and intensity’s For SRB Miner?!
you can find a few in the first post, those are some numbers users posted here. |
|
|
|
Here's a nice little tip on how to increase your hashrate even more : Example for Vega56 doing normalv7 algo : 1.Put --enableduplicategpuid in start.bat at the end of line ( SRBMiner-CN.exe --config config-normalv7.txt --pools pools-normalv7.txt --sendallstales --enableduplicategpuid ) 2.Set gpu in config-normalv7.txt : {
"cryptonight_type" : "normalv7",
"intensity" : 0,
"double_threads" : true,
"gpu_conf" :
[
{
"id" : 0,
"intensity" : 122,
"worksize" : 8,
"threads" : 1
},
{
"id" : 0,
"intensity" : 124,
"worksize" : 8,
"threads" : 1
}
]
}
What was done here? When using 2 threads , the best value for intensity is 123. By enabling the usage of duplicate gpu id, you make 2 separate threads for 1 gpu, but one has value 123-1, the other 123+1. This method can be used on any GPU, you just need to experiment with the intensities. |
|
|
|
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!
it should send you jobs based on your own hashrate + some calc it does on the profitability. I don't know how it works. To test it try setting an algo hashrate other than normalv7 to a high number |
|
|
|
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. |
|
|
|
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 |
|
|
|
|
Show Posts
