My firsts tests with RX 580 cards V8 algo: v1.6.8 4gb = 1000 H/s v1.6.8 8gb = 935 H/s v1.6.9 4gb = 985 H/s  v1.6.9 8gb = 975 H/s  v1.7.0 4gb = 1010 H/s v1.7.0 8gb = 975 H/s  for 1.6.8 & previous best intensity for 4gb was 61 & 116 for 8gb for 1.6.9 & 1.7.0 best intensity for 4gb is 54 & 100 for 8gb Also say that with newer versions the card connected to monitor is much more sensitive to background programs loosing more than 200 H/s in some cases when with 1.6.8 & previous was loosing at most 30 H/s Ok so obviously your 8G has some issue, maybe the strap, maybe just a bad card. Anyways. You lowered the intensities and get same or better results. That's what i call a win  Probably lower power consumption with lower intensities. |
|
|
|
Okay, so some of you said that the hashrate on Rx560 4g is lower on 1.7.0 vs 1.6.9 on heavy algos (said Haven) - HEREI took some time and made some tests : Both cards are without bios mod. Before every test i used the 'reset' button in ODT , just to be sure. 5 minute average result taken, same card, same clocks same driver same machine same everything. RX550 4G:Intensity : 15 Worksize : 12 Threads : 2 1.6.9 Fragments 1 : 292 h/s Fragments 32 : 270 h/s 1.7.0 Fragments 1 : 322 h/s Fragments 32 : 304 h/s RX560 4G:Intensity : 15 Worksize : 8 Threads : 2 1.6.9 Fragments 1 : 349 h/s Fragments 32 : 340 h/s 1.7.0 Fragments 1 : 354 h/s Fragments 32 : 356 h/s So as you can see i can't reproduce the huge -100hs drop you said. As a matter of fact, i can only produce + hash, not -  |
|
|
|
what to do if you get compute errors?
also getting compute errors, can't shake them, on vega FEs, 18.q3.1-oct1 driver, Heavy Try lowering you memory clock by 10mhs, and see if that helps |
|
|
|
480 8gb samsung (strap Ubermax 3.1) 1300/2000/1.00v Bittube config: { "id" : 0, "intensity" : 59, "worksize" : 8, "threads" : 2} srb 1.6.9 1169h srb 1.7.0 1100h  Speed increase on BitTube/Haven/Heavy/Italo algos up to ~10% (depends of gpu) Houston we have a problem!  Good for you if you had that speed on 1.6.9, continue using that version then Hello
I found a bug with the new startup monitor option
If you run benchmark-algos.bat, the startup monitor will kick in and restart the miner every 120seconds and the benchmark never finishes
The .bat file needs "--disablestartupmonitor" OR make sure that "--benchmarkalgos" always disables all watchdogs
edit: one more! benchmark-algos doesn't benchmark "dark" nor "festival"
Thanks for reporting these, i will check it out So... My RX 574 + 100H/s (v.1.6.9 = 750-770 v.1.7.0= 850-870) - nice! But RX 564 lower on new version (v.1.6.9 = 500 v.1.7.0= 450) bad! All cards same options at two versions.
distinguished developer
one question
do you still support old pitcairn video cards ?
After the test of your latest version 1.7.0 I am at a loss?
srb 1.6.9 pitcairn 370 2 gb stelite v4 --- 485h / s
srb 1.7.0 ---- 226h / s
total failure
Confirming the problem  On the RX560 cards there is big hashrate fall... (measured now on haven algo) v1.6.9 = 613H/s v1.7.0 = 501H/s The settings, the driver version - all the same. If I copy the kernel files, compiled on v1.6.9, to the .\Cache dir of v1.7.0, the RX560's hashrate is about 520-530H/s. But anyway - the problem is present P.S. RX570/580 have some hashrate increase, is about 30H/s Could you guys try out other configurations, like change the intensity and fragments parameter? Yes i know you would all like if always the same settings would work, but that is not possible unfortunately, one code has different effects on different gpu types. For 560 4g try setting fragments in gpu_conf to 32 for haven algo (that was the value in the previous version), leave the intensity same for this test.and clear the cache folder, don't copy binaries from older versions etc. also please leave it work for minimum 5 minutes to get the 5 min average EDIT: Ok, my tests show this on Haven : RX550 4G no mod : Intensity : 15 Worksize : 12 Threads : 2 5 minute average result1.6.9Fragments 1 : 292 h/s Fragments 32 : 270 h/s 1.7.0Fragments 1 : 322 h/s Fragments 32 : 304 h/s Later i will do this same test on my Rx560 4G and report back. |
|
|
|
But either way, I'm running the latest version now and still having a spastic secondary GPU. In fact, even on TeamRedMiner I'm seeing something similar. One GPU gets around 1900h/s, but teh secondary is even worse, around 600h/s... I seriously don't know what to do anymore, I'm helpless. Reinstalled Windows, updated drivers, updated BIOS, did everything I could, no hope.
Sell that gpu to a gamer and get yourself one that works |
|
|
|
So, where can we download it?
are you for real or is this a joke ? For real... The dl link on the official page still says 1.6.9...  Meh... shift+f5 in browser makes your cached page go away |
|
|
|
So, where can we download it?
are you for real or is this a joke ? |
|
|
|
Hello,
I need some help,
I have 4 RX 580 nitro + (8go) , 1 hynix , 3 micron . I was mining with SRB at 850h/s each (V8 Xmr)
I did this to increase my hashrate.
- Custom build with SRB Polaris ( I just pressed PIMP my strap then save BIOS and flash)
- then I DDU my old driver and install new one 18.6.1.
- then used atidmkpacher
- I tried the latest version of the miner with 58 intensity double thread for each RX580.
But now I'm mining at 350h/s each...
{ "cryptonight_type" : "normalv8", "intensity" : 100, "double_threads" : true, "worksize" : 8, "threads" : 2, "fragments" : 16, "bralock" : 50 } 1180/2150 900/950mv 942h per card. Thanks, one card is running at 950h/s with these setting , the 3 others still 850.. All 4 at 1250clock /2250 memory This is a little malformed config, you should set your gpu's in gpu_conf : Open config file for your V8 algo , and make it look like this: {
"cryptonight_type" : "normalv8",
"intensity" : 0,
"double_threads" : true,
"gpu_conf" :
[
{ "id" : 0, "intensity" : 100, "worksize" : 8, "threads" : 2, "fragments" : 16, "bralock" : 50},
{ "id" : 1, "intensity" : 100, "worksize" : 8, "threads" : 2, "fragments" : 16, "bralock" : 50},
{ "id" : 2, "intensity" : 100, "worksize" : 8, "threads" : 2, "fragments" : 16, "bralock" : 50}
]
}i dont know the exact id's and settings of your GPU's this is just an example, you should change it to suit your needs. |
|
|
|
V1.7.0- Speed increase on BitTube/Haven/Heavy/Italo algos up to ~10% (depends of gpu) - Small speed increase on V8 algo for Vegas - Added new algo CN-Dark [CryoNote] - Added new algo CN-Fest [Festival coin] - Added startup monitor which monitors miner startup process - Added new work mode for GPU hashrate watchdog [--gpuwatchdogdisablemode] - Added yet another gpu tuning parameter 'aes' - Fixed a bug related to hash speed monitor and algo switching - Small bug fixes + Performance boost for BitTube/Haven/Heavy/Italo algos up to ~10%, some cards gained 1% some 10%, i don't have exact numbers, you should try it out and see. Vegas gained the most, also i hope that i fixed the Ellesmere 8Gb cards problem, not reaching max hashing speed. If you had 1k+ on some earlier versions, you should be able to reach it now again but you MUST set fragments to 0 if you are setting it by hand, otherwise it probably won't reach max speeds. And no fee increase because of the extra performance, it stays at ~0.85%+ Some small optimisation gained around +10hs on my test Vega56 on V8 algo + Added new algos : Cryptonight Dark and Fest+ Startup monitor, a few of you have problems that sometimes miner wont hang, but it stops on GPU init process. I added a watchdog that should restart miner or run a user defined script if miner won't start working for a period of time. User can define this time period, default is 2 minutes. So if miner can't init gpu's but the process did not freeze, or hang, the watchdog should trigger after 2 minutes and restart the miner. Parameters that can be set in start.bat : --maxstartuptime value (max time to init gpu's and start mining, min 10 sec, max 10 min, def. 2 min) --maxstartuptimescript filename (run this script if maxstartuptime is exceeded) --disablestartupmonitor (disable watchdog for miner startup interval) + If you dont want the gpu hashrate watchdog to restart the whole miner if a gpu hangs, now a new mode is available : disable mode What this does is if it detects that your card can't hash (speed is 0), and its not because your driver crashed (because if that happens nothing can help you ), then it will disable that gpu, so the other gpu's can continue to work and no miner restart will occur. To use this mode put --gpuwatchdogdisablemode in start.bat+ gpu_conf, new parameter 'aes' . Never enough of extra tuning parameters, right ? This parameter can have the value of 0,1 or 2. Default is 0, and it is probably the best option for newer cards. This parameter just select the method for AES calculation part in the kernel. You can try it out, maybe you gain a few more hashes if you find the right one for your GPU
|
|
|
|
What is the best way to disable GPU in conf?
i.e -di in Claymore
for example if you want to use gpu 0,2,4,5 : "gpu_conf" :
[
{ "id" : 0, "intensity" : 50, "worksize" : 8, "threads" : 2},
{ "id" : 2, "intensity" : 45, "worksize" : 8, "threads" : 2},
{ "id" : 4, "intensity" : 40, "worksize" : 8, "threads" : 2},
{ "id" : 5, "intensity" : 55, "worksize" : 8, "threads" : 2}
] |
|
|
|
Both SRBMiner 1.6.8 and 1.6.9 are always stop mining because of devfee connection. I'm mining XMR on nanopool.Problem started few days ago and I didn't change anything or any settings. But my miners are stop after 4-10 hours after start mining. I check the log and the reason is can't connect to srbminer servers because of devfee. I'm not using any firewall /antivirus or i didn't change any settings in windows. Please help me... Log: [2018-11-05 23:18:03] miner_result: Pool accepted result 0x0000477E
[2018-11-05 23:18:10] hashrate: GPU0: 1949 H/s [BUS:3]
[2018-11-05 23:18:10] hashrate: GPU1: 1794 H/s [BUS:6]
[2018-11-05 23:18:10] hashrate: GPU2: 1797 H/s [BUS:10]
[2018-11-05 23:18:10] hashrate: GPU3: 1787 H/s [BUS:13]
[2018-11-05 23:18:10] hashrate: GPU4: 1950 H/s [BUS:16]
[2018-11-05 23:18:10] hashrate: Total: 9277 H/s
[2018-11-05 23:18:13] DFP online load: FAIL
[2018-11-05 23:18:13] devfee: Tried to contact http://srbminer.com a few times, but couldn't! Please check you firewall/antivirus is not blocking connections!
[2018-11-05 23:18:13] GPU devices disabled!
[2018-11-05 23:18:38] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"09099ccb82df052000470b275e855f7fc0bddec6e66d85d332ef5587d123ecae79497ca82d2d8d000000007fdbf809f7f1c393372b235952fa9d5d065ef55f6b85cfe44b5d16379478aa8f11","job_id":"26959","target":"cf8b0000"}}
[2018-11-05 23:18:38] pool_have_job: Pool sent a new job (ID: 26959)
[2018-11-05 23:19:38] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"0909d9cb82df052000470b275e855f7fc0bddec6e66d85d332ef5587d123ecae79497ca82d2d8d000000002128e76038ebc5877de5d30ef6ce777fee1a164e92609904ae3291b08804a89013","job_id":"26960","target":"cf8b0000"}}
[2018-11-05 23:19:38] pool_have_job: Pool sent a new job (ID: 26960)
[2018-11-05 23:19:52] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"0909e7cb82df05adb0ec44c0fa30bd4880834613a4d1ced482636a905455a1e9dffda32d5fe0ff00000000695abbfdff3108a5545ebbfccfceb75e8c897b7c7cd5af7054ba84cbbbd3cbc50c","job_id":"26961","target":"cf8b0000"}}
[2018-11-05 23:19:52] pool_have_job: Pool sent a new job (ID: 26961)
[2018-11-05 23:20:10] hashrate: GPU0: 0 H/s [BUS:3]
[2018-11-05 23:20:10] hashrate: GPU1: 0 H/s [BUS:6]
[2018-11-05 23:20:10] hashrate: GPU2: 0 H/s [BUS:10]
[2018-11-05 23:20:10] hashrate: GPU3: 0 H/s [BUS:13]
[2018-11-05 23:20:10] hashrate: GPU4: 0 H/s [BUS:16]
[2018-11-05 23:20:10] hashrate: Total: 0 H/s
[2018-11-05 23:20:52] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"0909a3cc82df05adb0ec44c0fa30bd4880834613a4d1ced482636a905455a1e9dffda32d5fe0ff0000000079cfa3f7ca31dce5a65e237a3c4799ea723a48d3e7a4bdb4c67343d9e763070d0f","job_id":"26962","target":"cf8b0000"}}
[2018-11-05 23:20:52] pool_have_job: Pool sent a new job (ID: 26962)
[2018-11-05 23:21:52] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"0909dfcc82df05adb0ec44c0fa30bd4880834613a4d1ced482636a905455a1e9dffda32d5fe0ff00000000462277818a7213d95dd8a7a1613d1589b973545b939dffa2d08f3016b142c00312","job_id":"26963","target":"cf8b0000"}}
[2018-11-05 23:21:52] pool_have_job: Pool sent a new job (ID: 26963)
[2018-11-05 23:22:01] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"0909e8cc82df05add27b1f85c9f24682b3e2961a325e35424050d1e0403355f27a174b3c8a3d5f00000000a444d6ef9957489461d33bc2d04591b60714cf193204d96f184c12807b6fe1ff07","job_id":"26964","target":"cf8b0000"}}
[2018-11-05 23:22:01] pool_have_job: Pool sent a new job (ID: 26964)
[2018-11-05 23:22:10] hashrate: GPU0: 0 H/s [BUS:3]
[2018-11-05 23:22:10] hashrate: GPU1: 0 H/s [BUS:6]
[2018-11-05 23:22:10] hashrate: GPU2: 0 H/s [BUS:10]
[2018-11-05 23:22:10] hashrate: GPU3: 0 H/s [BUS:13]
[2018-11-05 23:22:10] hashrate: GPU4: 0 H/s [BUS:16]
[2018-11-05 23:22:10] hashrate: Total: 0 H/s
If it started a few days ago, and you did not have this problem before, it really looks to me that something did change there on your computer/rig. I checked the srbminer.com was not down for a looooooong time, so that wasn't the issue. Anyways, i will loosen on this check a little bit in the next version. |
|
|
|
SUCCESS: Specified value was saved.
Initializing OpenCL devices, please wait..
ASDASDASDASDASDASDASD
ASDASDASDASDASDASDASD
ASDASDASDASDASDASDASD
ASDASDASDASDASDASDASD
ASDASDASDASDASDASDASD
ASDASDASDASDASDASDASD
ASDASDASDASDASDASDASD
ASDASDASDASDASDASDASD
ASDASDASDASDASDASDASD
ASDASDASDASDASDASDASD
ASDASDASDASDASDASDASD
ASDASDASDASDASDASDASD
GPU0: Radeon RX 580 Series [ellesmere] [4096 MB][I: 59.0][W: 8][T: 2][F: 16][K: 1][BUS: 5]
GPU1: Radeon RX 580 Series [ellesmere] [4096 MB][I: 59.0][W: 8][T: 2][F: 16][K: 1][BUS: 8]
GPU2: Radeon RX 580 Series [ellesmere] [4096 MB][I: 59.0][W: 8][T: 2][F: 16][K: 1][BUS: 12]
GPU3: Radeon RX 580 Series [ellesmere] [4096 MB][I: 59.0][W: 8][T: 2][F: 16][K: 1][BUS: 4]
GPU4: Radeon RX 580 Series [ellesmere] [4096 MB][I: 59.0][W: 8][T: 2][F: 16][K: 1][BUS: 14]
GPU5: Radeon RX 580 Series [ellesmere] [4096 MB][I: 59.0][W: 8][T: 2][F: 16][K: 1][BUS: 9]
GPU6: Radeon RX 580 Series [ellesmere] [4096 MB][I: 59.0][W: 8][T: 2][F: 16][K: 1][BUS: 13]
GPU7: Radeon RX 580 Series [ellesmere] [4096 MB][I: 59.0][W: 8][T: 2][F: 16][K: 1][BUS: 2]
GPU8: Radeon RX 580 Series [ellesmere] [4096 MB][I: 59.0][W: 8][T: 2][F: 16][K: 1][BUS: 3]
GPU9: Radeon RX 580 Series [ellesmere] [4096 MB][I: 59.0][W: 8][T: 2][F: 16][K: 1][BUS: 11]
GPU10: Radeon RX 580 Series [ellesmere] [4096 MB][I: 59.0][W: 8][T: 2][F: 16][K: 1][BUS: 1]
GPU11: Radeon RX 580 Series [ellesmere] [4096 MB][I: 59.0][W: 8][T: 2][F: 16][K: 1][BUS: 10]
what does this means?!
Ahahahaha, i was doing some debug and left this uncommented  Sorry about that, i will remove it in next version. Maybe there are a few more hidden messages, i don't know Oh you made me laugh so hard |
|
|
|
Looks like i finally found the 'secret' of hash increase on heavy algos , it can be applied to v8 also.
Just wondering how the hell i did not think of this earlier, it was so obvious lol
if everything goes well i hope i can push the new version in max a week.
Don't know about the speed compared to other miners, we will see. But probably won't reach the JCE advertised 1750hs, but my preliminary tests on Vega56 show an increase of ~ 6-7%
@doktor83 In my opinion, your script can easily surpass 1750 H/s. My rig is the example here, I'm using stock bios (this card is not reference card so I can't flash it to 64) on Gigabyte Vega 56 OC and I can achieve close to 1870 H/s easily: My config files as the followings: {
"cryptonight_type" : "normalv8",
"intensity" : 0,
"double_threads" : true,
"target_temperature" : 50,
"persistent_memory" : false,
"gpu_conf" :
[
{ "id" : 0, "intensity" : 112, "worksize" : 16, "threads" : 2},
{ "id" : 1, "intensity" : 112, "worksize" : 16, "threads" : 2},
{ "id" : 2, "intensity" : 112, "worksize" : 16, "threads" : 2},
{ "id" : 3, "intensity" : 112, "worksize" : 16, "threads" : 2},
{ "id" : 4, "intensity" : 112, "worksize" : 16, "threads" : 2},
{ "id" : 5, "intensity" : 112, "worksize" : 16, "threads" : 2},
]
}
In OverdriveNTool, I set my GPU clock to 1474MHz and Memory clock to 960MHz I'm currently using SRBMiner V1.6.8 and Adrenalin V18.6.1 Since you already found the 'secret', perhaps the next version might be able to reach 1900 H/s 1750 is for the heavy algos, not v8 |
|
|
|
Dok... JCE and Teamredminer are really upping their game with Heavy and CNv8.
Vega 56 1750h/s on heavy
Vega 64 2200h/s on CNv8
Are you planning any performance increases with SRB soon?
Hmm, come on mk111, you expect to Doktor do miracle (once again), and expect it today? Think what U can do to improve miner, lets start with reading Doktor post on this same page: are you going to reduce power usee like team red miner did, it uses 10 to 15 percent power same hash
too unstable for me tho compared to srb
Well that miner gave me homework to do, so i am working on something since then. It will definitely increase the hashrate, but don't know about the power consumption. we will see. Looks like i finally found the 'secret' of hash increase on heavy algos , it can be applied to v8 also. Just wondering how the hell i did not think of this earlier, it was so obvious lol if everything goes well i hope i can push the new version in max a week. Don't know about the speed compared to other miners, we will see. But probably won't reach the JCE advertised 1750hs, but my preliminary tests on Vega56 show an increase of ~ 6-7% |
|
|
|
Hi, Doc!
Is "Cryptonight Adaptive" support planned?
No , not at the moment. are you going to reduce power usee like team red miner did, it uses 10 to 15 percent power same hash
too unstable for me tho compared to srb
Well that miner gave me homework to do, so i am working on something since then. It will definitely increase the hashrate, but don't know about the power consumption. we will see. |
|
|
|
Hi Doc,
I maybe found a Bug in latest Miner and Profit switching. In my config, I set in each the 5 min average hashrate for restart, but when Miner switch from a higher HR Algo (fast) to a slower one (maybe haben) it does not reset the values and restart the Miner with the text that average HR is lower than defined.
Can you please check it? After the Algo switch Miner should load the average HR value and reset the average numbers...
Oliver
Going to check it out |
|
|
|
i am more interested in your pools file, have you defined a 'cryptonight_type' for the monero ocean pool?
{
"pools" :
[
{
"pool" : "gulf.moneroocean.stream:10064",
"wallet" : "someaddress",
"password" : "MinerSRBAuto:someemail@yahoo.com"
},
{
"pool" : "gulf.moneroocean.stream:10064",
"wallet" : "someaddress",
"password" : "MinerSRBAuto:someemail@yahoo.com"
}
]
}OK, so no 'cryptonight_type' set here for MO. That's good. Maybe you could try dropping the --forcedshutdown, and let the miner release the gpu resources before restarting, let's see is that going to help. |
|
|
|
I just wanted to report that I've solved my problem with one of my Vegas being quite spastic, like less than half hashrate of its sibling. My Windows key was deactivated for a while now, and I finally contacted the supports and they helped me reactivating my Windows copy. I got an update, and after restarting both cards are running at the same speed:  Edit: Um, it seems I started celebrating too early. My 4th miner report shows it dropped to around 1100h/s again... you need to cool those vegas, set the fan to 3000rpm. That is why the hashrate drops, hbm gets too hot |
|
|
|
|
i am more interested in your pools file, have you defined a 'cryptonight_type' for the monero ocean pool?
|
|
|
|
|
Show Posts
