Wow, thank you very much! The article is very helpful, it can help beginners with setting up the miner. Thanks again Alina  |
|
|
|
Is it normal for miner to do "precompilation" during mining?
I thought it only does precompiling before it starts mining.
It always does, it is doing it since CN/R was added, only that it wasn't displayed to the user earlier on the screen/log. |
|
|
|
test again  )) You are not using cmd configuring, you are using config and pools file. You only added one parameter, there are a few you need to set. Please check the readme for examples on how to set up gpus in cmdline. Or you have my example i gave. Theres no mixing of config files and cmd parameters. |
|
|
|
Hi Doc. Any idea what is the problem for the above message? I am using the right algo as you can see. Normal v4
I just tried pool.supportxmr.com:7777 and get valid results with v189. I have no idea what caused that. Have you tried another pool ?
when i start miner with --cgputweakprofile 9,9,9,9 then the miner doesn't set level on 9
confirm. work only in gpu_conf Wrong confirm, i just tested in cmd and it gets applied : SRBMiner-CN.exe --ccryptonighttype conceal --cpool conceal.herominers.com:10361 --cwallet xxx --cgpuid 0,1,2,3 --cgpuintensity 0,0,0,0 --cgputhreads 2,2,2,2 --cgputweakprofile 5,4,3,2
 I don't know how Awesome miner works, so have you checked without it ? |
|
|
|
{
"cryptonight_type" : "normalv4",
"intensity" : 161,
"worksize" : 16,
"double_threads" : true,
"shutdown_temperature" : 77,
"off_temperature" : 77
}This is with 18.8.8 Try intensity 112 Dok, how to disable the "Precompiling program"?
GPU can crash after a certain times of these "Precompiling program" and hashrate dropped (as if it didn't load the tweak profile) after the Precompiling Program.
You can't that is how CN/R works. |
|
|
|
I use 18.6.1. CC: 1407 MHz MC: 900 MHz (hynix memory - very unstable over ~910 on cn7, cn8) HR cn pico turtle = ~14880 H/s {
"cryptonight_type" : "turtle",
"intensity" : 0,
"double_threads" : true,
"shutdown_temperature" : 77,
"off_temperature" : 77
}No, i mean't on Cn/r , you said you have problems on CN/r |
|
|
|
Пoдcкaжитe ктo нe бyдь,чтo зa aлгopитм cryptonight-superfast? ecть ли oн в SRBminere?
what coin? its english topic кaкaя мoнeтa. пиши пo-aнглийcки, тoпикcтapтep pyccкий нe знaeт Furycoin,here is this coin,on algorithm SuperFast "cryptonight_type" : "cryptonight_superfast" or "cryptonight_type" : "swap" I have a decent hr on cn pico (turtle) but cnR i have horrible and unstable.
Should i raise core clock? Mem clock is pretty much at max (hynix memory) and it can't get over 910.
What are optimal settings for vega56 on cnr?
Driver version you use ? Also how does your config looks like? What hashrate do you get on CN/R ? |
|
|
|
Version 1.8.9 eventually crashes for me and ends up spitting only this :
[2019-05-26 10:25:49] miner_result: GPU0[BUS:1] result rejected for job[2] [invalid job id]
[2019-05-26 10:26:33] json_receive[269]: {"jsonrpc":"2.0","method":"job","params":{"blob":"0b0ba9ffa8e70537e99fa7db36c5a4dde2f1ad1294fc7d53e17e50f1130701247f4ca8b9d5485c0 0000000799dc1c161b7d129985fd562330eefce621530ea39965683170a3fb3d6ca822503","job_id":"207536794639743","target":"8b4f0100","height":1842901}}
[2019-05-26 10:26:34] json_send[202]: {"id":139,"jsonrpc": "2.0","method":"submit","params":{"id":"536912071801769","job_id":"959042067134134","nonce":"011f6900","result":"5209d27598e2285070b5aee1b0916b1b27bc7c62e6d4789cc6ea379d93870000"}}
[2019-05-26 10:26:34] json_receive[73]: {"id":139,"jsonrpc":"2.0","error":{"code":-1,"message":"Invalid job id"}}
[2019-05-26 10:26:34] miner_result: Too many invalid job errors, connecting to next pool
[2019-05-26 10:27:05] json_send[202]: {"id":140,"jsonrpc": "2.0","method":"submit","params":{"id":"536912071801769","job_id":"959042067134134","nonce":"dd516900","result":"a64fbb05010809a06e1a0118e1ef2b4d76f0cc9b84de6ac7c3b00acddf230100"}}
[2019-05-26 10:27:05] json_receive[73]: {"id":140,"jsonrpc":"2.0","error":{"code":-1,"message":"Invalid job id"}}
[2019-05-26 10:27:05] miner_result: GPU0[BUS:1] result rejected for job[2] [invalid job id]
[2019-05-26 10:28:01] json_receive[269]: {"jsonrpc":"2.0","method":"job","params":{"blob":"0b0b8180a9e7051daf5d91e61e074a63cc188ad34c8fb189808534be9ebf12df1eae1a6808b70a0 000000028740b2df6004a6e509c6d581f1ce5ac18dcc37e572128cb7320e20ae40dc79d17","job_id":"339747801201164","target":"8b4f0100","height":1842902}}
[2019-05-26 10:28:11] json_receive[269]: {"jsonrpc":"2.0","method":"job","params":{"blob":"0b0b8b80a9e705799ce479fc0c098816a99ebec48a2acdd9de1a0e28e802ae04492f11de4e80760 00000007c98b47f59706fe070a0d7c21e09a47b9c25efde346b48f3ab3cb40c373469e702","job_id":"635405887252134","target":"8b4f0100","height":1842903}}
Can you please add --extendedlog to start.bat, and if this happens again send me the whole log file. |
|
|
|
I removed the --preparedata and is working.
But I do not see any significant gain other than getting the same hashrate as with old_mode: true on 1.8.8, without it 1.8.8 was slower for me.
Also CPU utilization went up and since I am mining with CPU lost 600 h/s
- 1.8.8: hash 175K with old_mode true
- 1.8.9: hash 175k without old_mode and tweaks 1-8 and no preparedata at command line
So the small gain 100/200 h/s is canceled by higher CPU usage which cost 600 h/s
my card RX580 8Gb bios modded are at CC 1200/940 MC 1950/900
I fixed this issue and re-uploaded 189, so you can download it again and use old_mode + preparedata together. Work fine 1.8.9. Checked with profiles settings, got a speed increase of ~5.5% on standard VBIOS. A little, but nice. Algos with small scratchpad size like upx2, turtle have the least benefit from tweaking profiles on RX, if you look at it in %. Others should be there about 3-5%, depending how good is the strap in the modded vbios. I don't understand why are you still on stock vbios |
|
|
|
Just update to 1.8.9, Win 10, 7 RX 580 cards
getting an error:
Error CL_INVALID_WORK_GROUP_SIZE when calling clEnqueueNDRangeKernel for kernel 00 for DeviceID 4 (Thread 9)
any idea?
this is my config:
{
"cryptonight_type" : "upx2",
"double_threads" : true,
"gpu_conf" :
[
{"id" : 0, "intensity" : 107, "worksize" : 8, "threads" : 2, "fragment": 0, "tweak_profile": 1, "old_mode" : true},
{"id" : 1, "intensity" : 107, "worksize" : 8, "threads" : 2, "fragment": 0, "tweak_profile": 1, "old_mode" : true},
{"id" : 2, "intensity" : 107, "worksize" : 8, "threads" : 2, "fragment": 0, "tweak_profile": 1, "old_mode" : true},
{"id" : 3, "intensity" : 107, "worksize" : 8, "threads" : 2, "fragment": 0, "tweak_profile": 1, "old_mode" : true},
{"id" : 4, "intensity" : 107, "worksize" : 8, "threads" : 2, "fragment": 0, "tweak_profile": 1, "old_mode" : true},
{"id" : 5, "intensity" : 107, "worksize" : 8, "threads" : 2, "fragment": 0, "tweak_profile": 1, "old_mode" : true},
{"id" : 6, "intensity" : 105, "worksize" : 8, "threads" : 2, "fragment": 0, "tweak_profile": 1, "old_mode" : true}
]
}
Try adding --nobinaries to the cmd Or just remove the --preparedataedit: yes i see what i have forgot, going to fix and re upload later old_mode + preparedata dont cooperate |
|
|
|
installed the V1.8.9, works but same as the last version, I have no increase on rx 570 8GB (mining XHV) while downloading from https://www.srbminer.com it is still written v1.8.8  You need to use tweaking profiles to have some increase |
|
|
|
V1.8.9- Added tweaking profiles for RX 550/560, RX 470/480/570/580/590 - for some small fine tuning of existing vbios straps - Profiles 1-6 for Vegas are now a little lighter, 7-10 stayed same - Added embedded binaries for some gpu's - Added parameter --nobinaries, use it to disable usage of embedded binaries - Fixed some bugs in GPU detection code - Added more info to log when using tweaking profiles - Added watchdog for too many invalid job results, switches to next pool if more than 5 within the same connection - Usage of external tweaking tool is now allowed, so you can now fine tune a profile even more if you know how - Minor bug fixes + Added tweak profiles for RX 550/560, RX 470/480/570/580/590 cards, this is for already modded cards, but can be used also on stock vbioses. In this case the performance will be much lower than with a modded vbios. This is more like just to get out a little bit more hash of your already highly tuned Rx gpu + Tweak profiles 1-6 for Vegas are now little lighter, because not every gpu can handle profile 10, right ? + Added embedded (built-in) binaries for Vegas & Ellesmere & Baffin gpus when using auto setup. If you have problems with using them, add --nobinaries to your start.bat + 'External tweaker protection' removed, because of multiple reasons, but let's stay positive and say this was done so you can fine tune even more
|
|
|
|
Hi team
I have 9 mine Rigs use rx 470
Sometime all of them has same issues below
[2019-05-23 10:35:52] json_receive[259]: {"jsonrpc":"2.0","method":"job","params":{"blob":"0b0bb8aa98e70559de9e62ca77708cf1ad3cadf4cffa2898c9fb220e3f2f6bb54cc729d1b3be2e0 00000006f1c48800660941e0cd2da3101431efb1d04f0d1f57b68923f2f44294917be3202","job_id":"27518","target":"cf8b0000","height":1840555}}
[2019-05-23 10:36:47] watchdog: GPU0 [BUS: 3] hashing speed is 0 H/S
[2019-05-23 10:36:47] watchdog: GPU1 [BUS: 5] hashing speed is 0 H/S
[2019-05-23 10:36:47] watchdog: GPU2 [BUS: 6] hashing speed is 0 H/S
[2019-05-23 10:36:47] watchdog: GPU3 [BUS: 7] hashing speed is 0 H/S
[2019-05-23 10:36:47] watchdog: GPU4 [BUS: 1] hashing speed is 0 H/S
[2019-05-23 10:36:47] watchdog: GPU5 [BUS: 4] hashing speed is 0 H/S
[2019-05-23 10:36:51] json_receive[259]: {"jsonrpc":"2.0","method":"job","params":{"blob":"0b0bf2aa98e7058aa992fcacf54f6b6b27e548d4d674e1be98611f3cbf49de0b264e078d6bb9130 0000000acbfdbf080ca1ea35f6ea55ea52d8814648fab56e91d7b6f8e21d06adc20eb030f","job_id":"27519","target":"cf8b0000","height":1840556}}
[2019-05-23 10:41:37] Startup monitor attached
How about that
Here is my config pool
{
"pools" :
[
{"pool_use_tls" : false,
"pool" : "xmr-asia1.nanopool.org:14444",
"wallet" : "41hgaCaFC......3NS6n6znSJoFEWN1pUcjG.a75df28f221a445a2174115d8f7a5a07c798071535 be256e1234567890abeef8.Mi9/thanhtoan17@gmail.com",
"password" : "x",
"location" : "europe"},
]
}
This happens shortly after the message "Precompiling program" ? If not, describe is the miner crashing, or what is happening. Also upload log somewhere so i can take a look at it ?
Not every card can handle the same intensity/tweak profile. So what you need to do is to test separately which tweak profile can you use on which gpu.
For that you need to use the 'gpu_conf' or set gpu's in cmd line.
Thanks for the answer Dok! so, the settings of my OverdriveNtool and even changing my Adrenaline Driver from 18.5.1 to 18.6.1 won't affect anything much to the hashrate right? can you please tell me the recommended Base Intensity, threads and worksize of "gpu_conf" for Vega56 - CN-Haven algorithm to start tweaking with? Currently I'm still using basic cn-haven config with "intensity" : 0 thank you ! can i please get the answer Dok? 112 Intensity with tweak profile 3 crashed my Vega56, sometimes even to BSOD. how much should i set my base intensity (for cn-haven algo) before setting the tweaking profile? also, is it mandatory to change the driver from 18.5.1 to 18.6.1 to see the increased performance on Hashrate? sorry for noob questions, thanks For Haven you should try this for Vega56: "gpu_conf" :
[
{
"id" : 0,
"intensity" : 56,
"worksize" : 8,
"threads" : 2
}
] No need to change drivers, 18.5.1 is ok. Also add --preparedata to your start.bat cmd line, it gives a little boost on Haven for Vegas |
|
|
|
I am done with 1.8.9, atm in the testing phase. It contains tweak profiles that can be used on rx 450/460/550/560 rx 470/480/570/580/580/590.
It is intended for already modified cards - to get out a little bit more juice, but of course it will work on stock bios too, but the performance is far from a modded vbios.
This will be a great update. Recently I use only SRBminer. And with such new settings it will be even better. Approximately when can we expect the next version? I am testing it already on a few rigs, so if everything goes OK, i will release it tomorrow. |
|
|
|
Dont you worry about that message, it is just a notice. Hi,
any plans to add AMDTweakTool or Claymore type of stripe to increase AMD RX cards hashrate ?
thx
I am done with 1.8.9, atm in the testing phase. It contains tweak profiles that can be used on rx 450/460/550/560 rx 470/480/570/580/580/590. It is intended for already modified cards - to get out a little bit more juice, but of course it will work on stock bios too, but the performance is far from a modded vbios. |
|
|
|
Nope , every 3-4 minutes , your miner is restarting , and he is trying to get that gpu working on ... before ... i mean ... on 1.8.4 it was ok , after that version the issues has appearead . its stock values bios ... really weird ... i will upload the LOG . Here it is , i uploaded here because is too much ... https://ufile.io/vokk5az6You can try to add --watchdogrounds 10 to start.bat , this will trigger the watchdog later. But i have a feeling that's not the problem. |
|
|
|
Hey dok , i have a problem . i have a 7 gpu RX570 4GB msi model , and the latest version of this miner , and i have this issues : 1. https://ibb.co/FHnXCLW2. https://ibb.co/B6LRdWQHow can i solve it ? I tested with another miners and algos , and all 7 gpus are working properly . Thank you very much ! Hi, maybe those cards can't handle that intensity. Have you tried to lower intensity only for those GPU's ? Are they crashing ? A log would be helpful. Hello Doktor! I just recently switched to SBR Miner Ver. 1.8.8. Can you please kindly explain more to me about step 2 & 3? I Don't know ElioVP's tool, PPT and is ODT = OverdriveNTool? I'm Haven miner, and i have three (Windows10 Pro) Rigs with 4x Asus RX Vega56 (Hynix Mem) each. I'm using 18.5.1 Driver, and here is my OverdriveNtool base settings i got trouble with: GPU: MHz/mV P0 : 852 / 800 P1 : 991 / 900 P2 : 1138 / 950 P3 : 1269 / 1000 P4 : 1312 / 1050 P5 : 1474 / 1100 P6 : 1212 / 905 P7 : 1450 / 925Memory: MHz/mV P0 : 167 / 800 P1 : 500 / 800 P2 : 700 / 900 P3 : 940 / 925Nothing changed in config-haven.txt with above settings, my base Hash rate is ~1700 H/s for each Vega56. i press "+" up to Tweaking Profile 2, then it is increased to ~1800 H/s for each Vega. but, starting from Tweaking Profile 3, it went to ~2000 H/s then drop to ~1200 H/s in about 10s and not recovering back. (stuck at 1200H/s each Vega) I've tried Tweaking Profile to 4,5 and 10 and it gave me BSOD with "Video TDR Failure" Error Code.
Here are some numbers from my Vega56 with Hynix memory, just pushed mem up to 940mhs and P7 to 925mV.
Applied only "tweak_profile" : 10 to every config, nothing else changed in config.
Before tweak / After tweak ~ increase in percents
v4: 1854 / 2128 ~ 15%
haven: 1800 / 2000 ~ 11%
Is It possible for all Vega56 to reach 2000H/s per Card with CN-Haven Algorithm? can you please help me / tell me what to do to reach that Hashrate? I'm sorry if this question is too noob and if it's already answered before. I'm not very good at computer things. but i can follow guide well,hopefully. Thank you very much for your awesome miner and your contribution to Crypto World! Not every card can handle the same intensity/tweak profile. So what you need to do is to test separately which tweak profile can you use on which gpu. For that you need to use the 'gpu_conf' or set gpu's in cmd line. |
|
|
|
I wish I could, but I don't see any log files being created like in the previous versions.
If you open start.bat you will see this : REM LOGGING ENABLED
REM SRBMiner-CN.exe --config Config\config-normalv4.txt --pools pools.txt --logfile %LOGTIME%
REM LOGGING DISABLED
SRBMiner-CN.exe --config Config\config-normalv4.txt --pools pools.txt
if you remove the REM under the 'LOGGING ENABLED', and put a REM before the 'LOGGING DISABLED' part, you will get logging enabled. REM LOGGING ENABLED
SRBMiner-CN.exe --config Config\config-normalv4.txt --pools pools.txt --logfile %LOGTIME%
REM LOGGING DISABLED
REM SRBMiner-CN.exe --config Config\config-normalv4.txt --pools pools.txt
Or if you have a custom start script use the --logfile parameter. It's all the same as before, just it's not turned on by default. |
|
|
|
Ok, will look into it.
The last working version for me is V 1.8.7 .
With version 1.8.8 SRBminer seems to fail at compilation.
However, even on rigs with the same devices ( as in 2 cards of the same type), 1.8.8 will start and then fail after a few minutes. It will also have more rejected shares.
I'm mining Monero with the following settings:
{
"cryptonight_type" : "normalv4",
"intensity" : 0,
"double_threads" : true,
"adl_type" : 2,
"giveup_limit": 3,
"timeout": 10,
"gpu_conf" :
[
{ "id" : 0, "intensity" : 62, "worksize" : 16, "threads" : 1, "target_temperature" : 85, "target_fan_speed": 2000, "off_temperature":92, "adl_type": 2},
{ "id" : 1, "intensity" : 62, "worksize" : 16, "threads" : 1, "target_temperature" : 85, "target_fan_speed": 2000, "off_temperature":92, "adl_type": 2},
]
}
Can you upload a log file that SRB generates somewhere so i can take a look at it ? |
|
|
|
|
Show Posts
