Hello Claymore,
I've tried to use your v4.6 miner with a local nicehash pool setup. Though it is working basically, there are problems like a drop in average hashrate comparing to pool metrics and lots of stale, rejected shares. Do you have any idea why is it so?
I have no ideas, need to see the log. |
|
|
|
Hello Claymore. Having an issue with trying execute reboot.bat file in you manager. I'm getting red message in miner "File reboot.bat not found" and miner just closing. How to resolve this problem? reboot.bat at the same folder where miner is located. Experiencing this issue since you add this option in miner, but found time only now.
P.S. In future maybe it is possible to add in manager function Wake on Lan + option do it automatically (in case power loss in electrical lines and computer didn't restart for some reason after power restore) .
Miner gets path to its .exe, then appends "reboot.bat" string, then tries to open that file for reading. If failed, it shows that message. It works for me and right now I have no idea how to reproduce this issue, it must work. You can ask if someone else have same issue, right now you are the first person who sees it. Add please on\off sound notification ? You don't have sound off button while warning notification in tray needs to be working.
To disable sound, you can remove text in the textbox for filename. |
|
|
|
new release working great on nicehash so far.. I couldnt get it to work by using the config file at all. ended up just making a new shortcut with the command line you provided in the example.. If you use the config file it will say incorrect btc address and it never fully connects to nicehash.
For failover, use "epools.txt" as described in "FAILOVER" section of Readme. Do not put failover pools to "config.dat" or to command line. |
|
|
|
-ttdcr reduce Decred intensity automatically if GPU temperature is above specified value. For example, "-ttdcr 80" reduces Decred intensity if GPU temperature is above 80C.
You can see current Decred intensity coefficients in detailed statistics ("s" key). So if you set "-dcr 50" but Decred intensity coefficient is 20% it means that GPU currently mines DCR at "-dcri 10".
You can also specify values for every card, for example "-ttdcr 80,85,80". You also should specify non-zero value for "-tt" option to enable this option.
NOTE: Check "KNOWN ISSUES" section. GPU indexes in temperature control sometimes don't match GPU indexes in mining! I didn't find specification of option -dcr. Could you explain this option, or is a mistake in the description? Fixed, it must be "-dcri 50" instead of "-dcr 50". |
|
|
|
Claymore - I know this is probably considered pointless for 99.99% of people, so I don't really expect it - but since it's rather easy, I'm hoping you might get bored:
Is it possible you could add an option to load a kernel binary instead of using the builtin one? I'm of course not suggesting you load yours this way, but I meant, as an option to use others. NOT OpenCL, but a kernel binary.
It's possible of course, though it's not so easy as you describe because I use several kernels and a bit different params. Anyway, I don't see any reasons to spend time for such thing. |
|
|
|
Hi, Claymore!
Can you increase the time given to the activation of the sound notification to 1 minute?
In my rigs I observe periodic drawdown reported heshreyt for about 20% of that last 5-40 seconds. I do not know what causes it, but because this is a false positive alerts. And if I turn it off - miss a moment, when really everything stopped working.
If you spend some time monitoring options - it would be great.
For example allow the user to manually select the time interval, which is critical to start alert, and give the opportunity to choose which Hashrate drop (%) considered critical.
Thank you, and regards!
Ok, I'll add these options. |
|
|
|
|
v4.6:
- added "-esm 3" option value to support Nicehash Stratum implementation.
- added "-ttdcr" option.
- improved "-tstop" option - now you can specify negative values to close miner instead of stopping GPU.
- added "-fanmax" option.
- failover if pool rejects too many shares.
- fixed issue with wrong "-esm" value that miner could show.
- bug fixes.
- EthMan: added sound notification.
|
|
|
|
Instead, I prefer to spend time for other things, for example, check what coins can be mined instead of Decred in dual mode.
Or other coin instead of ETH (based on last trend) It would be a different miner in a different discussion thread  |
|
|
|
Have anyone managed to make CDM with new Dagger-Hashimoto algo on Nicehash? Could you share the config or bat file?
Nicehash created another stratum version, incompatible with other versions. So I have to implement "-esm 3", working on it. Has this been implemented / released yet? Extremely interested. Thanks Also, what bout decred support for nicehash? Ethereum - yes. Decred - no. I do not understand why they create own stratum implementations for every coin, slightly different, with no benefits. I would have to create some option like "-esm" but for Decred. May be I will do it in future (if I get several requests about that), but not right now. Instead, I prefer to spend time for other things, for example, check what coins can be mined instead of Decred in dual mode. |
|
|
|
Could you add sound notification when miner is down with ability on\off that feauture.
Already done in v4.6, just wait for 2-3 hours until I release it. |
|
|
|
Hey Claymore, how do you think, maybe hashrate of each card's separatelly in your monitor would be more informative ?
Already done, set appropriate checkbox in "Options" tab. |
|
|
|
Hi Claymore, when do you plan to give us a new release?
In a few hours. |
|
|
|
not to change the subject, but Claymore I have a feature request, and that is to fall back to failover if all the ETH shares are being rejected (hi dwarfpool).
Ok, it will disconnect if number of shares >= 5 and invalid shares rate > 50%. But note that it will lose some time anyway because it has to wait for 5 shares. |
|
|
|
Yeah Claymore, if you indeed wrote in a backdoor - I'm sure you'd tell us, RIGHT?
WTF - There is %0 chance of risk abatement by asking the developer anything about this.
You are 100% correct. I understand your work here has value, but, it's based on software that others have built.
At some point, you really should consider releasing the code.
You are wrong. I don't use any GPL code and I don't have to release sources. There are a few ETH miners, you can easily detect if a miner is based on original ethminer. Or, address the problems of virus "confusion" like a typical software vendor.
Did you ever try that? I did. The only real option is to contact AV vendor and tell them about false alarm. And usually false alarms are from weak AV with no real support, they just ignore your messages. It's impossible task. Especially for mining software that can be used in botnets with almost no changes. This is why I refuse to use your miner, and don't promote it.
No problem. Some people use only free and open-source software like Linux. Some people pay for closed-source software like Windows. You always have a choice. |
|
|
|
Have anyone managed to make CDM with new Dagger-Hashimoto algo on Nicehash? Could you share the config or bat file?
Nicehash created another stratum version, incompatible with other versions. So I have to implement "-esm 3", working on it. |
|
|
|
Currently this is only cosmetic and annoying to see it. But what happens if pool owner changes something at pool side and i'm locked at "esm 2" only? Claymore may decide to fix it -esm option works properly, so you can set -esm 2 if you want. But you are correct, now I see that miner can show incorrect -esm value in some cases, I will fix it in next update. |
|
|
|
When can we, exactly expect temperature dependent eth mode/eth+dcri mode switching?
I'm testing what approach is more effective, for now it looks lowering -dcri automatically is better, so probably I will select it instead of disabling DCR mining at all. An update will be available in 1-2 days. f But dual mode costs 2percent fee instead of 1% so if lowered dcri will give decresese earning increase it could be unprofitable.. Yea thats why I suggested to have a thereshold value for -dcri so people can adjust it depending on their own electricity costs/profitability. For example if you calculate that you need at least -dcri 30 for it to cover the extra 1 % then you would set -dcri changing between 30-50 or something. When your card couldnt keep the temperature setting even at -dcri 30 it would then change to the 1 % ether only mode. Right now devfee is not card-related, it is either 36 or 72 seconds. With your approach, if some cards mine DCR and some not, time must be recalculated and it will be between 36 and 72 seconds. Ok, I'm going to do it, but it will require more time to implement it. |
|
|
|
When can we, exactly expect temperature dependent eth mode/eth+dcri mode switching?
I'm testing what approach is more effective, for now it looks lowering -dcri automatically is better, so probably I will select it instead of disabling DCR mining at all. An update will be available in 1-2 days. |
|
|
|
Claymore, could you please add an option to show Hashrate for individual cards in monitoring please? It helps to spot a problem tremendously!
Already done, set checkbox on "Options" tab. |
|
|
|
|
Show Posts
