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

OK lets go step by step.
What algo do you want to mine and what pool?
Which cards do you have?

Can anyone share their config, bat, etc files to see what I'm doing wrong here please? Can't get the miner to do shares.

Thanks!

Hi Doc!

I'll play with algo switching. It's nice to see it integrated in your SRB.

I have a little question: The "GPU-Z trick" for heavy/haven mining still needed? Or is there another way to stick hashrate at max? I hadn't needed it before, but now my 470 8GB fluctuates between 889 and 1000H/s, its pretty high variation.

Thanks in advance. Fastest miner ever

Awesome work! Thanks!

I've rolled back the drivers to 18.3.4 and used the new release, and it still sits there doing no shares, which is really strange. With another miner, after 5 secs I get shares. Surely I'm doing something wrong on the config or bat, but can't seem to see what. Can you help please? :/

I am expecting you to do that 

Very good work. I'll implement support in my proxy relay as soon as possible.

V1.6.6
- Added support for algo/coin switching protocol BETA (pool must support it)
- "restart_devices_on_startup" and "restart_devices_on_startup_script" is now replaced with --resetvega and --startupscript
- Fixed "reboot_script" parameter, which should be triggered by hashrate watchdog
- Kernel 2 should be now automatically selected for R9 200 series
- Auto setup for RX 4XX and 5XX series should be now a little bit better
- Fixed a bug which could occur when receiving jobs too rarely
- Added miner version to API
- DevFee mining is not displayed anymore

+ At the moment the only pool that supports algo switching is Monero Ocean.
To enable this mode put --usealgoswitching in your .bat

How much is algo switching profitable that's something for the user to decide. The tool for that is here, so you can use it.
Fee for using the miner in algo switching mode is ~0.91% / 24hr. The miner is tracking when was the fee mined last time, so it's not mining it every time when it switches algo. This is only working if you are using the native way of algo switching.
You can see on the first page how to set it up, or on THIS LINK
One bad news is that the switching is done by restarting the miner, at the moment.

+ Removed "restart_devices_on_startup" and "restart_devices_on_startup_script", and replaced them with --resetvega and --startupscript
If you want to reset your Vega's before mining just append --resetvega in your .bat
To start a custom batch script before the miner starts, use the --startupscript filename in .bat
I had to go this way (and not the config way) because this is run before the miner initialises stuff

+ 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.

stock exchange not a pool

read on poll how to use wallet with payment id

can I mine on the stock exchange with the payment ID?

For the love of God Almighty remove the gigantic OP quotes, my mouse wheel broke.

Are you planning to release linux version?

I am using 18.5.1 as suggested in the original post.  They don't drop to nothing.  They just go down.  Once I restart the miner, everything is fine.  It is almost like a memory leak or something.  I have had it happen on 2 different systems with different cards so we shall see.

well, that's exactly what happens on my vega 56 rig and why I'm trying SRB (besides the fact I'm not overall happy with cast). Goes up just fine, let's say 3 vega do 6K. after a while, one drops, and it may be like that for hours, or really drop to ridiculously low hashrate, and/or more cards to the same.

lowering P7 or P3 does nothing to it... which drivers are you using?

I only had GPU crashes with too aggressive intensity or too aggressive memstraps/overclock/undervolt settings.
So, you could try setting the intensity manually lower than SRBMiner now does it based on your setting 0. This might work, but more likely it is in the profile you use with Overdriventool. I don't have VEGa's, but general advice here would be to cut back what you are doing there more to stock value and then see if it improves. Once you have a stable situation, crank it up.
Hope this works for you. May be somebody else can give you his Vega settings as a reference to try.
[/quote]


I don't think it's related to that. I know for experience I'm not pushing them hard and Vega's immediately complain when we taken them to the limit

Maybe it's because I'm using the latest drivers that it doesn't do any shares, and I'll revert to other drivers to test it, but I'd appreciate it if someone could help me fine tune the files to run the miner properly with the watchdog, restarting gpu's at the start, etc =)

I noticed the issue again with the miner seeming to drop hashing speeds on cards by around 100 H/s per Vega 64 card.  I looked back through the mining log and didn't see anything strange.  I tried resetting the cards while the miner ran (Overdriventool -r and then -p) and that didn't fix the issue.  I closed the miner down and restarted it.  That caused all of the cards to go back up to where they were at originally. 



I just lowered it to 1095 from 1100 on the memory.

I used to get best on non-claymore miners with 390 with 740-860 intensity/threads 2/work 4 that was with sgminer/ xmr stak/ gatelessgate old/new also, thats for CN normal 1040 mhz 830-840 h/s
older 290/290x go for Stilt's bioses blindly, i remember the last Hawaii i had (i burnt 4-5 of them ) was 90 watts chip power, doing 870 h/s-900 h/s.

I only had GPU crashes with too aggressive intensity or too aggressive memstraps/overclock/undervolt settings.
So, you could try setting the intensity manually lower than SRBMiner now does it based on your setting 0. This might work, but more likely it is in the profile you use with Overdriventool. I don't have VEGa's, but general advice here would be to cut back what you are doing there more to stock value and then see if it improves. Once you have a stable situation, crank it up.
Hope this works for you. May be somebody else can give you his Vega settings as a reference to try.

Hi! First off, congrats on the work done on this miner.

I've been using cast and not happy with it and it became very unstable.

I've tried SRB using minimal config and it connected correctly. Immediately I saw better hashrate with the same configs, but it gets several jobs and sends no shares, which is really strange. So I started playing around with the settings, and now it doesn't even start  

These are my files. What am I doing wrong here? Also want to put the restart script in, but haven't tried yet.

I'd really appreciate if you could help me on getting SRB cracking =)

Thanks

PS: the GPU restart seems to do it one by one, then says it restarted correctly, and shuts down after a quick message in red

start file

setx GPU_MAX_HEAP_SIZE 100
setx GPU_MAX_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_MAX_SINGLE_ALLOC_PERCENT 100
@echo off
cd %~dp0

cd C:\Users\vega\Desktop\SRBMiner-CN-V1-6-5
OverdriveNTool.exe -p1Vega-h4 -p2Vega-h3 -p3Vega-h1 -p4Vega-h2
timeout /t 1

cls
set EXE=SRBMiner-CN.exe
%EXE% --sendallstales --config config.txt --pools pools.txt

reboot file

shutdown.exe /r /t 10

pools file

{
"pools" :
[
   {"pool" : "xmr-eu1.nanopool.org:14444", "wallet" : "XXXwallet.USER/[email protected]", "password" : "x"},
]
}

config file

{
"cryptonight_type" : "normalv7",
"intensity" : 0,
"double_threads" : true,
"restart_devices_on_startup" : true,
"min_rig_speed" : 7400,
"target_temperature" : 60,

/* THERE ARE A LOT OF OPTIONS/PARAMETERS YOU CAN USE HERE */
/* YOU CAN FIND THEM IN THE README FILE */
}

I can't remember!
Been on holiday. Haven't turned on these rigs for three weeks...
Bah, it's not like I'm missing out on a lot of profits these days. Whenever I have some time, I'll fire them back up and check.