This is the part of log-file  Nothing has changed in 4.3, the bug is present. I don't need part of log. I need full log. It is because I have a rig with several 290X and I cannot reproduce the issue that you mention. So the complete log file is the only thing that can help me. |
|
|
|
In remote manager, select one miner (on linux os),
right click - restart miner.
After this miner change to red, and not update status.
Now his all time red))) i re-add him to RM - nothing.
Fixed, I re-uploaded Linux version. Download it again. Working. But can u add somthing like "Hard restart"? Like a call run reboot.sh in RM. I'll add support for .sh in next update. |
|
|
|
In remote manager, select one miner (on linux os),
right click - restart miner.
After this miner change to red, and not update status.
Now his all time red))) i re-add him to RM - nothing.
Fixed, I re-uploaded Linux version. Download it again. |
|
|
|
19:55:52:255 830 GPU #0 recognized as Radeon 290X
19:55:52:255 830 GPU #1 recognized as Radeon 290X
19:55:52:255 830 GPU #2 recognized as Radeon 290X
19:55:52:255 830 GPU #3 recognized as Radeon 290X
19:55:52:255 830 GPU #4 recognized as Radeon 290
19:55:52:255 830 POOL/SOLO version
19:55:52:255 830 b136
19:55:52:255 830 start building OpenCL program...
19:55:53:865 830 done
19:55:53:865 830 GPU #0: set -etha as 1 (ETH algo for slow cards)
19:55:53:865 830 GPU #1: set -etha as 1 (ETH algo for slow cards)
19:55:53:865 830 GPU #2: set -etha as 1 (ETH algo for slow cards)
19:55:53:865 830 GPU #3: set -etha as 1 (ETH algo for slow cards)
19:55:53:865 830 GPU #4: set -etha as 1 (ETH algo for slow cards) I`m asking dev for fixing this issue  PS Of course I set to -etha 0 in bat-file, but it seems no way to fix manualy PM me the log file. |
|
|
|
What u mean in remote manager "Target MH" ?
Value for?
You can specify miner hashrate. If miner will report less hashrate, it will be in red color in the list. Okay, one more q: Why u use .bash ? why not .sh?  I'm not guru in Linux, .bash in Linux looks for me like .bat for Windows. |
|
|
|
What u mean in remote manager "Target MH" ?
Value for?
You can specify miner hashrate. If miner will report less hashrate, it will be in red color in the list. |
|
|
|
|
v4.3:
- added "EthMan" - an utility for remote monitoring/management.
- added "-estale" option to send stale shares for Ethereum, it can increase effective hashrate a bit.
- now all options can be stored in "config.txt" file.
- added "-ftime" option.
- added "-erate" option.
- added "-tstop" option.
- now miner sends hashrate to geth in solo mining mode.
- added "-mport" option for remote management.
- bug fixes.
|
|
|
|
Dear Claymore! Tried to solomine I found -etht parameter couldn't set less than 200 ms. Is it normal? Thanks a lot for miner, happy using it.
It can be less up to about 10ms, but -etht is the pause between requests, so if HTTP request takes 200ms in your environment, you will not be able to check for new job faster. Ok, I see it. The question is because using another miner before. It allows put the request-between time as low as you wrote. Such feature isn't pool-friendly, of course (we shouldn't help DDoSers). But node allows some experiments. And I have a bad luck with CDM. Check readme: ... note that this mode is not intended for proxy or HTTP pools ... The miner supports all Stratum versions for Ethereum, so HTTP is necessary for solo mining only. Using a proxy will reduce effective hashrate by at least 1%. Using HTTP pools will reduce effective hashrate by at least 5%. |
|
|
|
So... i create files in prog dir: reboot.bat reboot.sh reboot.bash With reboot command in linux (uebuntu 14.04). And....: 22:20:53:241 94710780 watchdog - thread 7, hb time 262
22:20:53:241 94710780 Starting "reboot.bat"...
22:20:53:241 94710780 File "reboot.bat" not found
22:20:53:400 777fe700 ETH: put share nonce 3fb3793822d I will check it and fix if necessary in next update, it will be available within 24 hours. |
|
|
|
Hi Claymore,
What the ETA on the gpu, rig management feature?
Thanks
Edit: any sneak peak of the features?
New version with remote monitoring/management will be available in a day. Some new features/options will be added as well. The monitoring utility can have a lot of advanced features, but I prefer to release it asap so first version will have only main set of features like monitoring hashrates, temperatures etc and remote setting pools and options. |
|
|
|
Dear Claymore! Tried to solomine I found -etht parameter couldn't set less than 200 ms. Is it normal? Thanks a lot for miner, happy using it.
It can be less up to about 10ms, but -etht is the pause between requests, so if HTTP request takes 200ms in your environment, you will not be able to check for new job faster. |
|
|
|
Some suggestions.
-di should also apply to temperature monitor, or was there also a chance for different order?
Add "incorrect" count to report line.
Display both total hashes in different color (value only), white or bright yellow to stand out.
Lose job name (target 0x00.... name only) to save 1 line.
Display share found and accepted in same line. To save 1 line.
If program doesnt start, give some time to read the error messages, not close instantly.
A good idea, but because of possible different order in OpenCL and ADL lists I cannot make temperature control only for selected cards in "-di". It would required another option similar to "-di" but for ADL. Target is important sometimes to see if pool has vardiff and check how often miner must find shares. Share found and accepted in same line is difficult because miner would have to display "Share Found" line only when it got answer from server for that share, it can cause problems if server delays reponse, in general, it's a good idea to always show "share found" as soon as miner found share. Perhaps I should add an option "verbose" to select how miner should display info. |
|
|
|
Check history.txt: - default value for "-ethi" option is "8" now (instead of "16"), it slightly reduces delays when miner accepts new job. You can set is back to 16 if you want to see max hashrate. |
|
|
|
thanks Claymore for the miner.. it works very good!
i´m getting kinda slow hashrates across all my rigs (compared to what other users report)
rigs are win7, 4gb, 15.12 dll in dir (it works the same as clean installed driver), variables set...
270x = 13.4 Mh/s
7950 = 18 Mh/s
280x = 18 Mh/s (!) gigabyte ones, 1020/1550
when i try to set -cclock or -mclock values, the miner fails to start and closes itself.
any help or tips will be appreciated.
Try to set "-etha 0" or "-etha 1" option and select the best for every card, check readme for details. |
|
|
|
Claymore, as the run on dual miner miningrigrentals.com?
Thank you!
Search for "miningrigrentals" in this thread, some people use miner there. dev fee not work Make sure that miner has access to internet and specify "-allpools 1" (or better "-allcoins 1") so it will use default pools for devfee. |
|
|
|
Claymore, as the run on dual miner miningrigrentals.com?
Thank you!
Search for "miningrigrentals" in this thread, some people use miner there. |
|
|
|
Claymore would it be possible to add worker and hashrate sending with http and eth-proxy? ( http://127.0.0.1:8080/f1) I think it has been requested past few days, but I am not sure I have seen a definitive yes/no answer  This is just for convenience when viewing the stats at dwarfpool. Without the worker name, the proxy replaces it with some random numbers. What I cannot understand is why do you want to use miner with proxy if it can work with pools directly? It will reduce effective hashrate by 1% at least. |
|
|
|
My miner does not use any sources from ethminer, so any bugs/fixes related to ethminer are not related to it. Hi Claymore, I'm also wondering how your miner handles such cases what genoil has fixed here: After having received a new job, will your miner still submit stale shares for the replaced job? In fact, stale shares are invalid shares. If some pools want to get stale shares I will add such option, but some pools can count stale shares as invalid shares and you will ask me why miner sends more invalid shares. Therefore I will check all popular pools how they work with stale shares, so I can decide if this option must be enabled or disabled by default. Anyway, I will add this option in next update. BTW, stale shares rate is less than 1% for my miner. |
|
|
|
claymore could you please add power limit options in the miner..
What about checking "-powlim" option in OP? |
|
|
|
How to specify a worker name for the http (solo) mode?
Why do you need it in solo mining? |
|
|
|
|
Show Posts
