Hey Dok, I have a strange issue where the miner crashes after multiple hours and this is the end of the log: [2018-11-01 19:16:38] algo_switch: Pool requested algo switch to [normalv8]
[2018-11-01 19:16:38] Restarting miner with normalv8 algo
[2018-11-01 19:16:39] Miner version: 1.6.9
[2018-11-01 19:16:39] Windows version: 10.0 build 16299
[2018-11-01 19:16:39] Video driver version: 24.20.11021.1000
[2018-11-01 19:16:40] AMD Platform ID: 1
[2018-11-01 19:16:40] AMD platform FOUND
[2018-11-01 19:16:40] Found 3 AMD devices
[2018-11-01 19:16:40] CPU AES-NI: TRUE
[2018-11-01 19:16:40] GPU0: Radeon RX 580 Series [ellesmere] [8192 MB][I: 58.0][W: 8][T: 2][F: 4][K: 1][BUS: 6]
[2018-11-01 19:16:40] GPU1: Radeon RX Vega [gfx900] [8176 MB][I: 124.0][W: 16][T: 2][F: 4][K: 1][BUS: 9]
[2018-11-01 19:16:40] GPU2: Radeon RX Vega [gfx900] [8176 MB][I: 124.0][W: 16][T: 2][F: 4][K: 1][BUS: 3]
[2018-11-01 19:16:40] ADL is enabled
[2018-11-01 19:16:40] Algo switching mode enabled
[2018-11-01 19:16:40] Algo switch minimum time : 60 seconds
[2018-11-01 19:16:40] CryptonightV8 mode enabled
[2018-11-01 19:16:40] Starting init of mining threads
[2018-11-01 19:16:40] Created OCL context
[2018-11-01 19:16:40] Created OCL command queue for DeviceID 0 (Thread 0)
[2018-11-01 19:16:40] Created OCL input buffer for DeviceID 0 (Thread 0)
[2018-11-01 19:16:40] Created OCL output buffer for DeviceID 0 (Thread 0)
[2018-11-01 19:16:40] Loading normalv8 kernel for DEVICE BUS_ID[6] ...
[2018-11-01 19:16:40] ctx->Program for DeviceID 0 (Thread 0) loaded
[2018-11-01 19:16:40] Created OCL command queue for DeviceID 0 (Thread 1)
[2018-11-01 19:16:40] Created OCL input buffer for DeviceID 0 (Thread 1)
[2018-11-01 19:16:40] Created OCL output buffer for DeviceID 0 (Thread 1)
[2018-11-01 19:16:40] Loading normalv8 kernel for DEVICE BUS_ID[6] ...
[2018-11-01 19:16:40] ctx->Program for DeviceID 0 (Thread 1) loaded
[2018-11-01 19:16:41] Created OCL command queue for DeviceID 1 (Thread 2)
[2018-11-01 19:16:41] Created OCL input buffer for DeviceID 1 (Thread 2)
[2018-11-01 19:16:41] Created OCL output buffer for DeviceID 1 (Thread 2)
[2018-11-01 19:16:41] Loading normalv8 kernel for DEVICE BUS_ID[9] ...
[2018-11-01 19:16:41] ctx->Program for DeviceID 1 (Thread 2) loaded
[2018-11-01 19:16:41] Created OCL command queue for DeviceID 1 (Thread 3)
[2018-11-01 19:16:41] Created OCL input buffer for DeviceID 1 (Thread 3)
[2018-11-01 19:16:41] Created OCL output buffer for DeviceID 1 (Thread 3)
[2018-11-01 19:16:41] Loading normalv8 kernel for DEVICE BUS_ID[9] ...
[2018-11-01 19:16:41] ctx->Program for DeviceID 1 (Thread 3) loaded
[2018-11-01 19:16:41] Created OCL command queue for DeviceID 2 (Thread 4)
[2018-11-01 19:16:41] Created OCL input buffer for DeviceID 2 (Thread 4)
[2018-11-01 19:16:41] Created OCL output buffer for DeviceID 2 (Thread 4)
[2018-11-01 19:16:41] Loading normalv8 kernel for DEVICE BUS_ID[3] ...
[2018-11-01 19:16:41] ctx->Program for DeviceID 2 (Thread 4) loaded
[2018-11-01 19:16:41] Created OCL command queue for DeviceID 2 (Thread 5)
[2018-11-01 19:16:41] Created OCL input buffer for DeviceID 2 (Thread 5)
[2018-11-01 19:16:41] Created OCL output buffer for DeviceID 2 (Thread 5)
[2018-11-01 19:16:41] Loading normalv8 kernel for DEVICE BUS_ID[3] ...
[2018-11-01 19:16:41] ctx->Program for DeviceID 2 (Thread 5) loaded
need much more info, like config file and pool, is it Monero Ocean? All i see on the log is that miner switched algo to V8 and all gpu's were initialised. |
|
|
|
For all of us who are having more or less H/s with 1.6.9 than with previous....
I think H/s shown by the program is inaccurate.
Examples:
Pressed H, shown 992 H/s
Pressed S, it says max H/s have been 985
Set worksize to 1
I press H all the time I want, always showing 0 H/s but getting some hashes
S says H/s 200+
So I think the H/s shown by the S command are OK but the ones shown by H or automatically are not.
Max is 'refreshed' every 30 seconds. You probably did not wait 30 seconds to press 'S' after you pressed 'H' and saw 992hs. 'H' shows average hashrate for a very short period, like 8-10 seconds. 'S' shows average for much more, that's why you had there 200hs. |
|
|
|
I am trying this miner out. Why do I see connections being made to get.masaricoin.com while connected to MoneroOcean?
devfee for fast algo Ok that makes sense then. Is the only pool you are using or should I be expecting to see others show up as well? Probably others too because MO switches algos and devfee is always mined with the actual algo. |
|
|
|
I am trying this miner out. Why do I see connections being made to get.masaricoin.com while connected to MoneroOcean?
devfee for fast algo |
|
|
|
RX 560 2Gb 1.6.8 - 526 h/s 1.6.9 - 490 h/s  have no fear, just report here  Anyone with 4gb 560 can report a change in hashrate? I have only 4gb card and there nothing changed from 168->169 when testing. |
|
|
|
Hi guys. Use srb 1_6_9 on my 7970 and have a less hashrate compared to 1_6_8. The problem is that the value of "fragments" does not change, it is always 4. Heres my config.txt:
{
"cryptonight_type" : "normalv8",
"intensity" : 57,
"worksize" : 16,
"double_threads" : false,
"fragments" : 8
}
Where is my mistake? Thank you.
You can't define fragments there. Do it like this : "gpu_conf" :
[
{ "id" : 0, "intensity" : 57, "worksize" : 16, "threads" : 2, "fragments" : 8}
] Thank you, now it works. As i understand value of fragments can be equal only to this values:0,1,2,4,8,16,32,64,128 ? Yes, that's right. You said you have less hashrate with 169 compared to 168. Is that what the exact same settings? What numbers were you getting on 168, and now on 169 ? |
|
|
|
Hi guys. Use srb 1_6_9 on my 7970 and have a less hashrate compared to 1_6_8. The problem is that the value of "fragments" does not change, it is always 4. Heres my config.txt:
{
"cryptonight_type" : "normalv8",
"intensity" : 57,
"worksize" : 16,
"double_threads" : false,
"fragments" : 8
}
Where is my mistake? Thank you.
You can't define fragments there. Do it like this : "gpu_conf" :
[
{ "id" : 0, "intensity" : 57, "worksize" : 16, "threads" : 2, "fragments" : 8}
] |
|
|
|
Thx for the new version. You have added 2 new tuning param in last 2 versions: Can you pls help us as to the nature of the tuning ,its effects and sort of recommended values for vega cards. This will help us fine tune our cards better. Thx dude !!  Fragments -> my tests show it can REALLY be different for even the same type of GPU, but different vendor. So i can't give you a recommended setting for a vega, sorry. For my Gigabyte 56 with hynix mem the winner value is 4 for v8, and 1 for everything else. Bralock -> this is something similar as worksize, you will also need to experiment with the values Hmm, k dude. The miner shows fragments of 4 as defaults on my vega. Testing other fragments also generates the same 4, doesnt change to 8 or 2 etc.My config file: {
"cryptonight_type" : "normalv8",
"intensity" : 124,
"worksize" : 16,
"double_threads" : true,
"fragments" : 64,
"shutdown_temperature" : 80,
"timeout" : 5,
"retry_time" : 5,
"giveup_limit" : 5,
"main_pool_reconnect" : 300,
"min_rig_speed" : 11850,
"min_rig_speed_duration" : 250
}- Added a performance tuning parameter 'fragments' for gpu_conf and cmd |
|
|
|
Thx for the new version. You have added 2 new tuning param in last 2 versions: Can you pls help us as to the nature of the tuning ,its effects and sort of recommended values for vega cards. This will help us fine tune our cards better. Thx dude !! Fragments -> my tests show it can REALLY be different for even the same type of GPU, but different vendor. So i can't give you a recommended setting for a vega, sorry. For my Gigabyte 56 with hynix mem the winner value is 4 for v8, and 1 for everything else. Bralock -> this is something similar as worksize, you will also need to experiment with the values |
|
|
|
V1.6.9 - Algo switching without miner restart - Benchmark everything from algos.txt and just paste the hashrates (--benchmarkalgos) - Added number of algo switches to API and stats - Added cmd parameter --resetmineronalgoswitch which forces miner to reset on algo change - Changed minimum --algoswitchmintime from 3 min to 30 sec, default is still 600 sec - Fixed API pool stats when not connected to a pool - Added cmd parameters --cjobtimeout, --cmaxdifficulty, --ckeepalive - When critical temp is reached, ADL temp is now logged before shutdown - Notification on too many compute errors (set with --gpuerrorsalert value) - Added a performance tuning parameter 'fragments' for gpu_conf and cmd - Fixed a bug that could crash miner on shutdown + Algo switch without miner restart is here finally. This is now the default mode. If you want to use the 'old fashioned' switch where the miner restarts itself use --resetmineronalgoswitch in .bat. The only reason i can see to use the switching with restart is for Vegas, because they tend to drop hashrate on algo switch, and only --resetvega can help to regain full speed again. Check out here how to setup algo switching+ Some people were too lazy to benchmark algo by algo to get the 'hashrate' values for algos.txt, so there is a --benchmarkalgos now , that benchmarks the algos set in algos.txt, and creates benchmark_results.txt, from where you just have to take and paste the values into algos.txt + The --algoswitchmintime minimum value can now be 30 seconds, altough Monero Ocean really likes to disregard this setting + There is on-screen and log notification now when you have too much compute errors (default is 15). You can set this value with --gpuerrorsalert value+ (re)added fragments parameter for some performance tuning. This parameter was set internally, but my tests show it can REALLY be different for even the same type of GPU, but different vendor. So now everyone can find his 'optimal' value for this parameter. It differs for algos and also for the amount of VRAM, so a value that is good for 4GB cards maybe isn't the best value for 8GB cards.
|
|
|
|
thx for check  but why in my log miner will do first a restart ? can you share your reboot me .bat ? thx ! It could be anything in the .bat, as long as miner runs it  I just had something echoed for the test. |
|
|
|
I just checked, it is working : {
"cryptonight_type" : "normalv8",
"intensity" : 0,
"double_threads" : true,
"reboot_script_gpu_watchdog" : "run-me-watchdog.bat"
}
[2018-10-28 07:45:35] watchdog: GPU0 [BUS: 3] hashing speed is 0 H/S
[2018-10-28 07:45:40] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"090994b6d5de053c408e072491052f414699215faf87c20ebd7d0b40ba3dd729a4a499cdbd6480000000005975b98061a7aec57fd05f418a5d774a78ea762a1abf6639fdd5b00109919f1205","job_id":"474","target":"cf8b0000"}}
[2018-10-28 07:45:40] pool_have_job: Pool sent a new job (ID: 474)
[2018-10-28 07:45:46] watchdog: GPU0 [BUS: 3] hashing speed is 0 H/S
[2018-10-28 07:45:57] watchdog: GPU0 [BUS: 3] hashing speed is 0 H/S
[2018-10-28 07:46:08] Starting reboot script run-me-watchdog.bat...
[2018-10-28 07:46:09] ocl_release: Device BUS_ID3 thread0 resources released
[2018-10-28 07:46:09] ocl_release: Device BUS_ID3 thread1 resources released
[2018-10-28 07:46:09] Stopping miner process
|
|
|
|
It really is V2, but v2, v8, v9 who cares, as long as we know it is the new monero algo I won't play a detective anymore, but one last time : I don´t really want to go through that discussion again. I don´t care what is shown on the screen. If one miner, over the span of 10 days, gives 10 billion hashes and another gives 9 billion hashes, but both shows 12KH/s, then these miners are not the same speed. One is real (JCE, XMR-Stak) and another is fuckin´ liar and cheater. Cheers Of course anyone who follows, knows you are referring to SRB. I never blamed you, i am aware there were users who had this problem, there still are (for example there are people who disregard the ton of compute errors they have,and come here to blame the miner for stealing hashrate). Majority had their poolside hashrate approximately ok, and after the changes i made even more have, so i am happy it helped them (you). Yes, it never will be perfect i know. I am working on it a LOT trying to make it good for everyone. Ok, enough. I am glad it is ok for you now, and that's all what matters at the end |
|
|
|
Few versions of SRBminer ago, I was complaining that that miner reported hashrate and pool reported hashrate have big discrepancy, from few % up to 20%. For example, a 7x vega rig pool hashrate was only 12kh/s instead of 14.5.
Found here only mocking and making fun of, so I simpmy abandoned srbminer and went for another.
Since Monero upgraded to v9, i started using SRBminer again. The hashrate is now spot on - miner reports hashrate is now the same as pool reported hashrate (minus the fee, offcourse)
I am very happy that this problem has been repaired, despite never being admitted here. Thumbs up (y) for development!
There was no problem to "admit" it was clearly user error and its v8 not v9. He is partly right, the lower poolside hashrate was because of stale shares. Users who have no connection problems and less stale shares never had this problem. From v1.6.4 i changed the way stale shares are handled, and that resulted in better results for these users. There was never cheating, stealing etc. that you stated. Also i don't like the anti SRB campaign you are doing (yes, i read other forums too), makes me think you get payed for advertising that other miner (you know which one). But it's your call, you do whatever you want |
|
|
|
Please help. I have one Vega56 and one RX580-8G. Got the following error when running SRBMinber 1.6.8. Tried different drivers (18.5.1, 18.5.2, 18.6.1), DDU clean install every time. Also tried the default kernel and compiled kernel. One wired thing I noticed is that the miner recognizes my RX580 as "Radeon RX Vega [ellesmere]". The miner is working properly only when I use one card at a time to hash with fresh compiled kernel.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
[2018-10-25 14:17:10] Miner version: 1.6.8
[2018-10-25 14:17:10] Windows version: 10.0 build 17763
[2018-10-25 14:17:10] Video driver version: 24.20.11021.1000
[2018-10-25 14:17:11] AMD Platform ID: 0
[2018-10-25 14:17:11] AMD platform FOUND
[2018-10-25 14:17:11] Found 2 AMD devices
[2018-10-25 14:17:11] CPU AES-NI: FALSE
[2018-10-25 14:17:11] GPU0: Radeon RX Vega [ellesmere] [8192 MB][Intensity 61.0][W: 16][T: 2][K: 1][BUS: 15]
[2018-10-25 14:17:11] GPU1: Radeon RX Vega [gfx900] [8176 MB][Intensity 120.0][W: 16][T: 2][K: 1][BUS: 5]
[2018-10-25 14:17:11] ADL is enabled
[2018-10-25 14:17:11] CryptonightV8 mode enabled
[2018-10-25 14:17:11] Starting init of mining threads
[2018-10-25 14:17:11] Heating up system, please wait...
[2018-10-25 14:17:11] Created OCL context
[2018-10-25 14:17:11] Created OCL command queue for DeviceID 0 (Thread 0)
[2018-10-25 14:17:11] Created OCL input buffer for DeviceID 0 (Thread 0)
[2018-10-25 14:17:11] Created OCL output buffer for DeviceID 0 (Thread 0)
[2018-10-25 14:17:12] Loading kernel for DEVICE BUS ID 15 ...
[2018-10-25 14:17:12] Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram [ctx->Program] for DeviceID 0 (Thread 0)
[2018-10-25 14:17:12] Error initing GPU's. Stopping miner process
Open a command prompt and run clinfo, let's see what does it say, how does it recognise your cards. Also guys, please don't send me PM's without reading the first page of this thread, because 90% of your questions is answered there. I really don't have time to answer everyone separately. And don't send me PM's asking what intensity should you use, and why does your GPU crashes. Please take some time and read back, everything is answered in this thread. |
|
|
|
@doktor83 I just want to verify is this a bug in SRBMIner V1.6.8 or not? After 3 days running, my rig suddenly stopped working. And I saw this on the screen:  The messages stated: Critical shutdown temperature reached (80C)!!! (I did set "shutdown_temperature" : 80 in my config files) Shutting down system!However, if you look at the screen status, none of my GPU reach over 55C Thank you! If it is because of a bug then it is something in the driver, in ADL part, because miner gets the temperature data from it, and then just makes a simple compare (if adl value > user set value = problem). This gives me an idea, i will add to the log the value read from ADL if this happens. |
|
|
|
Force Compute Mode + Disable Crossfire & ULPS in one click [ just copy into note pad and save as a *.reg file, make sure to adjust reg locations for gpu's, i use this on all the rigs not just vega's] Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0001]
"KMD_EnableInternalLargePage"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0002]
"KMD_EnableInternalLargePage"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0003]
"KMD_EnableInternalLargePage"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0004]
"KMD_EnableInternalLargePage"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0005]
"KMD_EnableInternalLargePage"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0006]
"KMD_EnableInternalLargePage"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0007]
"KMD_EnableInternalLargePage"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0001]
"EnableCrossFireAutoLink"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0002]
"EnableCrossFireAutoLink"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0003]
"EnableCrossFireAutoLink"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0004]
"EnableCrossFireAutoLink"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0005]
"EnableCrossFireAutoLink"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0006]
"EnableCrossFireAutoLink"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0007]
"EnableCrossFireAutoLink"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0001]
"EnableUlps"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0002]
"EnableUlps"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0003]
"EnableUlps"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0004]
"EnableUlps"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0005]
"EnableUlps"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0006]
"EnableUlps"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0007]
"EnableUlps"=dword:00000000
The --setcomputemode also sets these 3 parameters per gpu, so no need to edit/run a registry file |
|
|
|
I'm only getting 1100h/s for Vega FE. what did i do wrong?
18.5.2
120 or 124/ 16/2
core 1222mhz and 1100mhz
You also did not read the big red letters on the first page |
|
|
|
doktor83 How to write "max_difficulty" if all parameters are in bat ? SRBMiner-CN.exe --config Config\config.txt --ccryptonighttype normalv8 --cgpuid 0,1,2,3,4 --cgpuintensity 26,26,26,26,26 --cgputhreads 2,2,2,2,2 --cgpuworksize 32,32,32,32,32 --cpool pool.supportxmr.com:7777 --cwallet "wallet" --cpassword x "keepalive" "job_timeout" "max_difficulty" Can't be set in cmd, but it's not a bad idea to implement them |
|
|
|
Greetings - using --startupscript to overclock / undervolt GPUs.
However when Algo switches some aglo's require different clock / voltage settings.
How can I use different --startupscript for each Algo?
Have you tried with the "startup_script" in algos.txt ? |
|
|
|
|
Show Posts
