Hey guys,
getting error message while trying to run --current
Failed to load EIO.dll
Are you using SRBminer? It blocks it (( Hah. What a surprise. SRB basically took eliovp's free tool and integrated a few self-compiled mem timing straps into his latest closed-source fee-including miner. TRM had the decency not to integrate it. They chose to add a timing-optimised mode - should you want to run eliovp's tool whilst using TRM. Yes i was waiting for this. Now if you look closely i couldn't integrate ElioVP's tool into my miner, but i guess you just don't have enough knowledge to inspect these kind of things. Oh wait, here's one tip : we are not even using the same kernel driver to access phyisical memory, that means i can;t be using the ASUS files he uses because his complete implementation is built on that. But how should you know that.. Claymore is coming with built in timings manipulation too.. Guess he took ElioVP's tool too. Also what is a 'self-compiled mem timing straps' if you could explain, cause i never heard about compiled mem timing straps. Whatever, Dok. You know what you did and didn't. So you play on semantics. What you did (and Claymore is going to), is a direct consequence of eliovp releasing his open-source tool. You could have been giving him credit at least before putting it (in whatever form) into your paid miner. Yes, offsets from his code helped me finish an ongoing project. You wrote i took his tool, and emphasized how im using it in a closed source fee including miner.  Now it's whatever... 1. Look at the readme that comes with SRB 2. Look at the first page in SRB thread, bottom of 1st post 3. Look at ElioVP's btc donation address. 3 donations, Claymore, Me and 1 more. Please next time before you write something like this do your homework first. But you wont, it's whatever.. |
|
|
|
Hey guys,
getting error message while trying to run --current
Failed to load EIO.dll
Are you using SRBminer? It blocks it (( Simply use the --disabletweaking parameter and you can use ElioVP's tool with it. |
|
|
|
Hey guys,
getting error message while trying to run --current
Failed to load EIO.dll
Are you using SRBminer? It blocks it (( Hah. What a surprise. SRB basically took eliovp's free tool and integrated a few self-compiled mem timing straps into his latest closed-source fee-including miner. TRM had the decency not to integrate it. They chose to add a timing-optimised mode - should you want to run eliovp's tool whilst using TRM. Yes i was waiting for this. Now if you look closely i couldn't integrate ElioVP's tool into my miner, but i guess you just don't have enough knowledge to inspect these kind of things. Oh wait, here's one tip : we are not even using the same kernel driver to access phyisical memory, that means i can;t be using the ASUS files he uses because his complete implementation is built on that. But how should you know that.. Claymore is coming with built in timings manipulation too.. Guess he took ElioVP's tool too. Also what is a 'self-compiled mem timing straps' if you could explain, cause i never heard about compiled mem timing straps. |
|
|
|
|
V1.8.5
- Fixed the 'tweak_profile' changing with + - on keyboard
- Tweaking is now auto disabled if no supported devices found
This release is a quick fix
+ There was a bug with using + - while mining to switch tweak_profiles. Miner reported 0 hash after switch and restarted itself. This should now be fixed.
+ If no tweak supported devices found, tweaking is auto disabled so no unneccessary resources are used
|
|
|
|
It doesn't really work for me.
Vega 56 with Samsung Memory, conservative power settings, cvddc and mvddc 900, cclock 1200, mclock 940.
Perfectly stable for days with 1.8.1, ~1800 H/s.
With tweak settings, HBB goes boom and starts hashing @ 1100 H/s.
Reduced memory clock to 900 and set voltage to 950 mv. Can go up to 3, just as fast as 940 Mhz memory with 1.8.1 and no tweak (obviously).
Tweak setting 4 gave imediate screen corruption.
Should I test it with default memory clock?
Even at profile 1 you should have a minimum 5% increase. Clocks are ok, vddc is ok, so i don't really get it why you get lower hash. Did you just use + - , or set the profile in the config file ? If only + -, there's a bug i fixed, it will be released in a day. No, I set the profile in config, and setup 1.8.4 from scratch. Maybe because of Samsung memory? (Reported by GPU-Z) Some Vegas are a bit finecky with memory overclock and disable HBM, starting to hash at much lower speeds. You have to reset the card to get it working again. I got it from too much memory overclock, and lowered it to 940 until it fully stabilize. No problems now, still haven't upgraded from 1.8.1 because it's really stable with my 480/580/Vega 56 rig. Samsung is ok, you should use the --resetvega switch, which is mega recommended if you have Vegas.. It disables/enables the gpu before mining. |
|
|
|
It doesn't really work for me.
Vega 56 with Samsung Memory, conservative power settings, cvddc and mvddc 900, cclock 1200, mclock 940.
Perfectly stable for days with 1.8.1, ~1800 H/s.
With tweak settings, HBB goes boom and starts hashing @ 1100 H/s.
Reduced memory clock to 900 and set voltage to 950 mv. Can go up to 3, just as fast as 940 Mhz memory with 1.8.1 and no tweak (obviously).
Tweak setting 4 gave imediate screen corruption.
Should I test it with default memory clock?
Even at profile 1 you should have a minimum 5% increase. Clocks are ok, vddc is ok, so i don't really get it why you get lower hash. Did you just use + - , or set the profile in the config file ? If only + -, there's a bug i fixed, it will be released in a day. |
|
|
|
tweak work only on vegas?
4xx 5xx dont work?
Polaris cards can be modded and yours probably are, if you are mining. If not, i recommend you SRBPolaris and pimp my straps feature. That said, messing with an already tweaked bios is the right way to freeze/bsod/crash. There would be sense in tweaking an unmodded gpu, but i believe there are not many of those in the mining world  |
|
|
|
New version seems to be a little bit faster , but i want to mine Wtips , wich algo should i use ? The coin need PICO algo ... i cant find it in setup guide . Thanks .
turtle |
|
|
|
On my two rigs the WinIO64.sys blocked usage of WinAMDTweak.exe by blocking the loading of EIO.dll. This persisted even after rebooting. The only way of deleting the file was by booting into safe mode and deleting the SRB 1.8.4 folder.
Winio gets started/loaded on demand when miner starts. When miner is closed Winio gets unloaded but it wont get disabled until windows restart. After restart it won't be active so you probably ran miner again after restart, that's why you could not delete it. |
|
|
|
Is there any way to see if tweak profile was set successfully from config?
I made this config.txt:
{
"gpu_conf" :
[
{ "id" : 0, "tweak_profile": 5 },
{ "id" : 1, "tweak_profile": 5 }
]
}
But I don't see any differences in hashrates and when I press "+" it says it switches to profile 1, so it looks like it was using profile 0 in the beginning.
you should really check out the readme or the first page , there are examples on how to use gpu_confI read it and I took this piece of config above from there. Also tried this: "use the "tweak_profile" parameter on top of config so the same profile is used for all cards": { "tweak_profile": 5 } Also no visible change in miner's behavior. That's why I decided to ask if there is any way to check if tweak profile is applied on miner start. Well what you pasted there is not from any of my examples, sorry You need to make a full config file, not just some partial stuff. And yes, there is a notification on miner start that it applied profile X to gpu bus id Y. Here's a minimal config file that applies tweak profile 5 to every gpu and uses miner auto settings. {
"cryptonight_type" : "normalv4",
"intensity" : 0,
"double_threads" : true,
"tweak_profile" : 5
} |
|
|
|
There are 5 (6) profiles, where :
0 - no change, uses your original settings
1 - light tweak
2
3
4
5 - max tweak
You should find separately for every gpu the profile it can handle, and set it in gpu_conf or cmdline.
Is there any way to see if tweak profile was set successfully from config? I made this config.txt: { "gpu_conf" : [ { "id" : 0, "tweak_profile": 5 }, { "id" : 1, "tweak_profile": 5 } ] } But I don't see any differences in hashrates and when I press "+" it says it switches to profile 1, so it looks like it was using profile 0 in the beginning. you should really check out the readme or the first page , there are examples on how to use gpu_conf |
|
|
|
|
Here are some numbers from my Vega56 with Hynix memory, just pushed mem up to 940mhs and P7 to 925mV.
Applied only "tweak_profile" : 5 to every config, nothing else changed in config.
Before tweak / After tweak ~ increase in percents
v4: 1854 / 2128 ~ 15%
haven: 1800 / 2000 ~ 11%
turtle: 15630 / 18440 ~ 18%
mox: 3845 / 4525 ~ 17%
fast2: 3604 / 4111 ~ 14%
conceal: 3726 / 4065 ~9%
litev7: 4386 / 4965 ~13%
xcash: 958 / 1106 ~15%
|
|
|
|
2 doctor83
I don't think it is good idea to mix miner and memory timings optimizer in such manner. User should understand what benefit he/she gets from miner optimization and what benefits from timings.
I thinks Elio's utility will help to understand what timings you apply when "tuning" ))
Nevertheless, thanks for hard work, I'm still using your miner for older cards. But for vegas teamred is the king now.
I think you are wrong, the user doesn't have to know how things work, the user just needs to get out as much as possible from his mining hardware. The curious ones who want to learn how stuff works will learn. Also 1% of people want to know how the various timing parameters work, the other 99% just wants everything prepared so they can copy paste. Sometimes even that is too much work for them. And i am glad you shared what's your favorite miner, or who's da king with me, thank you Does your miner return back stock timings when it exits? Sorry, no time to check it by myself on the rig Yes it does, it returns the ones that were active before running SRBMiner. |
|
|
|
2 doctor83
I don't think it is good idea to mix miner and memory timings optimizer in such manner. User should understand what benefit he/she gets from miner optimization and what benefits from timings.
I thinks Elio's utility will help to understand what timings you apply when "tuning" ))
Nevertheless, thanks for hard work, I'm still using your miner for older cards. But for vegas teamred is the king now.
I think you are wrong, the user doesn't have to know how things work, the user just needs to get out as much as possible from his mining hardware. The curious ones who want to learn how stuff works will learn. Also 1% of people want to know how the various timing parameters work, the other 99% just wants everything prepared so they can copy paste. Sometimes even that is too much work for them. And i am glad you shared what's your favorite miner, or who's da king with me, thank you |
|
|
|
That tweaking, is it fixed per profile number (so it will be always the same depending on the number)? Or will it run some tweaks in the background to find a sweetspot?
For the same gpu it will be the same, yes. There is no auto tuning. |
|
|
|
V1.8.4- Performance increase for Vega56/64/Fe/Vii up to 15%!- Minimum for 'main_pool_reconnect' is now 60 seconds instead of 180 - Added new cmd parameters: --disabletweaking, --cgputweakprofile - Added new config parameter: tweak_profile - Minor bug fixes + Yes, you read it right. Performance increase on ALL algos on Vega56/64/Fe/VII up to 15%! A new parameter 'tweak_profile' was added, which if used can significantly boost your hashrate. There is section about this on the first page, but in short: There are 5 (6) profiles, where : 0 - no change, uses your original settings
1 - light tweak
2
3
4
5 - max tweakYou should find separately for every gpu the profile it can handle, and set it in gpu_conf or cmdline. VERY IMPORTANT :1. Miner must run with administrator privileges [right click on SRBMiner-CN.exe->properties->compatibility-> check 'Run this program as an administrator' option-> click OK button
2. Don't apply any memory timings with ElioVP's tool before running miner
3. Don't start testing/tweaking with your highly optimised PPT and ODT settings - because it is probably optimised for a miner/algo combination.. Start with stock settings.
4. Be patient, it takes some time to find settings optimal for your gpu/rigTweaking is enabled by default, and can be used on supported devices. If you want to disable it use the --disabletweaking parameter in start.bat It can't get easier to use, just use + and - on your keyboard to move between the profiles. Examples on how to use it can be found on the first page. Special thanks goes to ElioVP for sharing the offset of the timings position.
|
|
|
|
Getting the same here:
Miner does 6500
"min_rig_speed" : 5000
"gpu_conf" :
[
{ "id" : 0, "intensity" : 0, "worksize" : 0, "threads" : 2},
{ "id" : 1, "intensity" : 0, "worksize" : 0, "threads" : 2},
{ "id" : 2, "intensity" : 0, "worksize" : 0, "threads" : 2},
{ "id" : 3, "intensity" : 0, "worksize" : 0, "threads" : 2},
]
Miner restarts on the avg 5min mark constantly.
Cn/r ? Weak cards? How many ? worksize 0 ? |
|
|
|
if someone has managed to get Tube2 version 1.7.1 to Rx 580 8 GB without fail it will be thankful to share settings.with adrenaline 18.6.1 I tried a lot of combinations but for now without success. "heavy_mode": 3,"Fragments": 9999 was the best I got on 7 cards - 8310 h/s on heavy, but one of seven cards did not go away."intensity" : 58. Doc, how do you benchmark the cards when running the program? It is interesting that with the same settings they give different crashes. Have one reached half or some percentage of their power and there are stuck?
Version 1.7.1 ? You should switch to the latest version, i can't help you with older versions. |
|
|
|
1) When the miner freezes, the system error window appears.
But the SRB-Miner process is still in computer memory.
The SRB-Restarter utility thinks that the miner is working. But the miner is frozen.
Not every crash can be catched, restarter works for restarting the miner when a crash occurs because of miner bug code (access violation etc.) RX562, miner 1.8.2 - 1.8.3 - not OK
{
"cryptonight_type" : "normalv4",
"intensity" : 0,
"double_threads" : true,
"retry_time" : 2,
"persistent_memory" : false,
"min_rig_speed" : 2100, <<<<<<<<<============== only works if set to 100. otherwise restart miner!!!!!!!
"min_rig_speed_duration" : 60,
"gpu_conf" :
[
{ "id" : 0, "intensity" : 26, "worksize" : 32, "threads" : 2, "fragments" : 8},
{ "id" : 1, "intensity" : 26, "worksize" : 32, "threads" : 2, "fragments" : 8},
{ "id" : 2, "intensity" : 26, "worksize" : 32, "threads" : 2, "fragments" : 8},
{ "id" : 3, "intensity" : 26, "worksize" : 32, "threads" : 2, "fragments" : 8},
{ "id" : 4, "intensity" : 26, "worksize" : 32, "threads" : 2, "fragments" : 8}
]
}
Someone else also reported the 'min_rig_speed' parameter is broken and triggers much earlier than it is set. I am testing it, but so far so good. On a rig that does 38khs turtle i set it to 36khs and it's not triggering - restarting miner. Im using with minimal config : {
"cryptonight_type" : "turtle",
"intensity" : 0,
"double_threads" : true,
"min_rig_speed" : 36000
}
Going to check it out in code, maybe when gpu_conf is set this parameter gets omitted, or idk. Ok, so i think i know what is happening. Cn/R precompiles 10 kernels on miner startup. That takes some time * number of gpus in the system. Your "min_rig_speed_duration" is 60, it is too low, because miner does not start hashing until it precompiled the kernels. So just set the "min_rig_speed_duration" to a higher number, try few minutes... |
|
|
|
has anyone tried configuring haven+bloc in hashvaultpro? could you share your configs please?
You don't need configs, you need pools file : {
"pools" :
[
{"pool" : "pool.haven.hashvault.pro:80",
"wallet" : "HAVEN_WALLET:BLOC_WALLET",
"password" : "x"
}
]
}WAtch the : sign between HAVEN and BLOC wallet. |
|
|
|
|
Show Posts
