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

[dingdongtobias]

RX Vega x6 rig,  One GPU always turns off 0 kh/s with default settings, any suggestions before i just change miner?

this happened with my 7X GPU rig aswell, it did it on all gpu's there for rx570 / rx580's randomly, and since this one uses alot more power and same hashrates as cast xmr, this isn't even an option for rx580 / rx570's at all.

you even not try to set miner config, but have time to cry here not work not work....

set inetsity by hand, also miner uses much thread as YOU define, visit first page there you have info for all

[1714045214]

1714045214

[doktor83]

To the people with 0 kh or slowdowns/crashes.
Default intensity is too high. Windows dmw.exe uses almost 200mb of vram on the primary gpu and this miner tries to allocate the full 4GB / 8gb. For example you have 4.2gb of vram usage on a 4gb gpu and the system crashes or the miner fails at 0kh/s.
Solution: rollback to windows 7 and disable aero OR reduce default mining intensity by 2 or 3 points on the gpu that is using more vram (use GPU-Z or hwinfo32 to find out).
Please OP, tweak this miner so that it never tries to allocate more vram than that you have on your system. It should be possible to predict the mining intensity based on the available vram. I've spent hours tweaking the intensity settings and still can't get more than 3-4 hours uptime on a multi-algo pool.

as intensitivity is 0 by default, whats recommended for rx vega? also, since this miner uses 2 threads it really does pull alot more electricity just for 100 h/s over cast xmr so far. im 110w 1320 h/s on cast xmr, meanwhile on this im 1440 h/s at like 140 watt which is 30% increase for only 100 h/s

You should really open the readme.txt that comes with the miner.
Also on the first page you can find some settings for various cards on various algos, also some for Vega too.

As with the power consumption, you need to tweak a few things (properly set overdriventool, find good intensity/power ratio etc..), it won't set everything magically for you, sorry.

[igotek]

When i try to use %DATE-TIME% for logging, It does not create a text file at all?
Any solution?

I got it working if i type in : Logfile.txt

This works for my rigs.

Code:

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

cls
set LOGTIME=%date:~10,4%_%date:~4,2%_%date:~7,2%_%time:~0,2%_%time:~3,2%
set LOGTIME=%LOGTIME: =%
set LOGTIME=%LOGTIME:,=.%.txt

SRBMiner-CN.exe --config Config\config-stellitev4.txt --pools pools_XTL.txt --logfile %LOGTIME%

[m1dz0]

Monero v8 soon?

cast sux

Ajmo DOKTORE!

[glowbg]

do you there will be an upgrade for CN v8?

[RuMiner]

When i try to use %DATE-TIME% for logging, It does not create a text file at all?
Any solution?

%time% results a ":" symbol forbiden in filenames. I'm using --logfile logs\%date%-%random%.log
or use more complex construction from above

[doktor83]

V1.6.8
- New Monero algo added (normalv8)
- Small speed increase on some cards
- Fee is now ~0.85% for both normal mode and algo switching mode
- Faster miner startup
- Pools with different algos can now be used in pools.txt, miner will re-init on switch
- Added a new parameter for gpu tuning in gpu_conf : bralock
- Rewritten release of resources on miner shutdown/restart
- Added parameter --forcedshutdown if you don't want to release resources on exit
- Fixed bug when setting compute mode on more than 9 cards
- Fixed a bug showing bad date for 'connected since' and 'average share find time'
- Gpu hashrate watchdog now won't trigger if user is not connected to a pool
- reboot_script parameter removed and added 'reboot_script_min_rig_speed' and 'reboot_script_gpu_watchdog' instead
- Added more logging in gpu init part
- API parameters now have to be set in start.bat (--apienable, --apiport, --apirigname) , removed them from config.txt
- Press 'o' to switch to the previous pool from pools.txt
- If you add 'stratum+ssl://' before the pool address, TLS will be automatically enabled

+ Monero will fork on block 1685555 (that is approx Oct 18th). A new algo is introduced, use 'normalv8' for cryptonight_type
+ Fee is now equal for both normal and algo switching mode (~0.85%)
+ Miner now starts up a little bit faster
+ Pools can now use cryptonight_type, and if the next/previous pool algo isn't the current one, miner will restart with the correct settings
There is a short explanation on how to use this option on the first page and in the readme.txt

+ Added parameter bralock in gpu_conf, it is a value from 1-256, it *may* give you a little speedup if you find the right value for your algo/gpu
+ Removed the reboot_script parameter, and instead made 2 new parameters :
"reboot_script_gpu_watchdog" : filename to a batch file in miner directory, if set it turns off built in miner reset procedure on gpu failure, and instead runs this script
"reboot_script_min_rig_speed" : filename to a batch file in miner directory, if set it turns off built in miner reset procedure on min_rig_speed trigger, and instead runs this script

+ API parameters removed from config file, so they don't have to be defined in every config separately.
Now you can set them in start.bat with :

--apienable (enable statistics API)
--apiport value (port where statistics API is reachable - default 21555)
--apirigname value (identifier name for your rig in statistics API)

+ Added possibility to switch to the previous pool from your pools list by pressing 'o'. If you get to the first pool on the list, and press 'o' it will go around, and jump to the last pool.

Also i implemented a temporary solution for the transition from V7 to V8 algo, so the miner can switch automatically when the fork happens.
You can read it HERE on how to do it.

Basically you set the config for normalv8 in Config folder(intensity and everything else), enable the algo switching (by adding --usealgoswitching in start.bat), and create a temporary pools file, where you put 2 pools, the first one is the V7 pool, the second one is V8.

Set start.bat to use that temporary pools file, and when the time comes, miner will detect if the received job is for the new algo, and will switch to the next pool on the list, which in this case is the pool using the V8 algo.

Also the config-normalv8 settings will apply.

[strh]

1200h/s and no shares per day

https://cdn1.savepice.ru/uploads/2018/10/8/19d82b3b18f387ad0a7d540ab9140c22-full.png

[doktor83]

1200h/s and no shares per day

Have you read the big red text on the first page that say which driver versions NOT to use when compiling?

[PIOUPIOU99]

thks for v8 dok.
intensity auto  for rx 550 2GB : 30 intensity } blue screen for me .
Max 27 /32 Woksize 
and rx 460 unlock 27/16 worksize

[doktor83]

thks for v8 dok.
intensity auto  for rx 550 2GB : 30 intensity } blue screen for me .
Max 27 /32 Woksize  
and rx 460 unlock 27/16 worksize

ill have to lower that then , 30 is good for 4gb

[abg00]

ill have to lower that then , 30 is good for 4gb

rate low for rx570\8 on cn-heavy
was 1060 in 1.6.7 now 890-960 in 1.6.8
same config same drivers 18.3.4

in additional. remove kernel folder and recompile binary solve trouble
work 10 min and low rate again. back to 1.6.7

[doktor83]

ill have to lower that then , 30 is good for 4gb

rate low for rx570\8 on cn-heavy
was 1060 in 1.6.7 now 890-960 in 1.6.8
same config same drivers 18.3.4

in additional. remove kernel folder and recompile binary solve trouble
work 10 min and low rate again. back to 1.6.7

Wait 10-15 min for it to get to the max speed.
Nothing has changed for heavy algos in the code.

[abg00]

ill have to lower that then , 30 is good for 4gb

rate low for rx570\8 on cn-heavy
was 1060 in 1.6.7 now 890-960 in 1.6.8
same config same drivers 18.3.4

in additional. remove kernel folder and recompile binary solve trouble
work 10 min and low rate again. back to 1.6.7

Wait 10-15 min for it to get to the max speed.

wait 27 min rate low. back to 1.6.7
check on two rig

rx560\4 work stable with high rate on 1.6.8 cn-heavy

[doktor83]

ill have to lower that then , 30 is good for 4gb

rate low for rx570\8 on cn-heavy
was 1060 in 1.6.7 now 890-960 in 1.6.8
same config same drivers 18.3.4

in additional. remove kernel folder and recompile binary solve trouble
work 10 min and low rate again. back to 1.6.7

Wait 10-15 min for it to get to the max speed.

wait 27 min rate low. back to 1.6.7
check on two rig

rx560\4 work stable with high rate on 1.6.8 cn-heavy

interesting..and on 1.6.7 you get the 1000+ speed on all cards ?

[abg00]

interesting..and on 1.6.7 you get the 1000+ speed on all cards ?

[doktor83]

interesting..and on 1.6.7 you get the 1000+ speed on all cards ?

Ok going to re-check and test.

Can you test on bittube too?

[GKumaran]

Hey Doc, thc for update !!

Using Binary kernals on Vega 64:
v7 : HR up from 2130 to 2145
v8 : HR is 580
Is that normal, only 580 H/s? Cause i think the devs said approx 7% drop so was expecting at least 1950 h/s

I got the same HR result for v8 on both benchmark mode and mining on the test pools:

"pool": "killallasics.moneroworld.com:7777",
"difficulty": 10000,

{
            "device": "GPU0",
            "device_id": 0,
            "model": "Radeon RX Vega",
            "bus_id": 19,
            "kernel_id": 1,
            "hashrate": 593,
            "core_clock": 1630,
            "memory_clock": 1100,
            "temperature": 54,
            "fan_speed_rpm": 4576
},

GPU was on dual thread and auto worksize, auto intensity

[doktor83]

Hey Doc, thc for update !!

Using Binary kernals on Vega 64:
v7 : HR up from 2130 to 2145
v8 : HR is 580
Is that normal, only 580 H/s? Cause i think the devs said approx 7% drop so was expecting at least 1950 h/s

I got the same HR result for v8 on both benchmark mode and mining on the test pools:

"pool": "killallasics.moneroworld.com:7777",
"difficulty": 10000,

{
            "device": "GPU0",
            "device_id": 0,
            "model": "Radeon RX Vega",
            "bus_id": 19,
            "kernel_id": 1,
            "hashrate": 593,
            "core_clock": 1630,
            "memory_clock": 1100,
            "temperature": 54,
            "fan_speed_rpm": 4576
},

GPU was on dual thread and auto worksize, auto intensity

Yes something not ok, try setting by hand for example 120/16 2 threads

I really hurried to push the v8 version, so of course bugs are to be expected, and we still have time to fix them until the fork

[abg00]

Can you test on bittube too?

check rx550\4g on cn-v7
same trouble in 1.6.8
low rate
420-450 in 1.6.7
370-390 in 1.6.8


rx550\2g rate high in 1.6.8 was 460 now 490