-logfile 0 do not working at 7.1
Where did you find "-logfile 0" option value? It must be filename, not "0" or "1" (or do you want to name file as "0"?). From readme: -logfile debug log file name. After restart, miner will append new log data to the same file. If you want to clear old log data, file name must contain "noappend" string. If missed, default file name will be used. If you want to disable logging, use "-dbg -1". It really doesn't work: UNKNOWN OPTION -logfile UNKNOWN OPTION ClaymorelogDamn! You are correct! Though "-logfile 0" is a strange choice so I did not check it, it really does not work. Though alevlaslo could explain it in details, like you did Weird bug. Fixed, I uploaded "7.2 Beta" again (for Windows only for now), re-download it if you need "-logfile" option.
|
|
|
Hellow, Claymore! I have one more suggestion for your miner. Please add option -fanmin -- minimum fan speed, used with -tt and -fanmax
Such situation. I use the option -tt 65. And while the card cool and the temperature reached 65 degrees fans do not rotate. However WRM not blown because all this time the fan is stopped, and therefore is strongly heated in these moments.
Good idea.. sometimes I have about 75degrees by tt 80 and fan at 25% It could be cooler if fan is faster Ok, I'll add it in next update.
|
|
|
-U --cuda-extragpu-mem 4096 --cuda-streams 1 --cuda-block-size 64 --cuda-grid-size 4096 for genoil for ccminer i use 1.8.2 with -i 23 no special parameter (but also not specifing intensity is giving me same results)
With these options, at stock clocks I get about 195MH/s LBC and 6.7MH/s ETH (ETH-only shows 25MH/s, LBC-only shows 278MH/s). It's difficult to see exact hashrates since both LBC and ETH miners show various numbers all the time in this mode. Sometimes Genoil shows 12MH/s, a couple of times I even saw 15MH/s, but average hashrate is 6.5...7MH/s. LBC miner shows more stable numbers, 180-210MH/s, average is 195MH/s. With my miner at "-dcri 500" I get 147MH/s LBC and 13.7MH/s ETH. So right now I don't see that Genoil+ccminer faster/better. However, I agree that LBC is not very good coin for dual mode anyway, it takes too much resources so ETH speed suffers.
|
|
|
Claymore, is there any workaround for gtx 1080 (372.90 / win 10) and not getting 5 Mhs ?
Yes, Windows 10 Anniversary + latest drivers wddm 2.1. After update on genoil 20 mh\s, your miner don't run and says that Opencl.dll is not found (Why Opencl for Nvidia ). I have updated to 1607 Win 10 (Anniversary) and didn't touch the drivers. Don't forget that the miner supports both OpenCL and CUDA, linking is static so opencl.dll is required. It's another bug of Win10 when it eats that dll, if you search for "opencl.dll" in this thread you'll find similar posts like yours, for example: https://bitcointalk.org/index.php?topic=1433925.msg16262905;topicseen#msg16262905
|
|
|
-U --cuda-extragpu-mem 4096 --cuda-streams 1 --cuda-block-size 64 --cuda-grid-size 4096 for genoil for ccminer i use 1.8.2 with -i 23 no special parameter (but also not specifing intensity is giving me same results)
Ok, I'll check it soon, though in my tests I always use stock settings, no OC, no changing power limits, no undervolting, no modded bios etc, it is not important when compare two miners.
|
|
|
at the moment claymore you should improve the code for libry coin... im speaking as nvidia user... not profitable to use your miner.... genoil + ccminer running at same time on windows will produce approximately 13% more than your miner and for free 3 x 1070 gtx @ 70 % power will produce 36 mhas eth and 610 lbry coin ... and no fee involved (except the pool fee dwarf pool... suprnova has no fee if i remember.) 365 w from the wall ( approximaterly 330 w REAL considering psu efficency. 100w /gpu considering 30w for system) 24h tested stable alternatively we can give more priority to eth and produce with same settings 67 Eth and 270 lbry
Ok, I'll check it. Can you send the command lines for both miners? If I run both Genoil+ccminer1.8.3 I get only 18.8MH/s ETH + 71MH/s LBC (single stock 1070). If I start ccminer1.8.3 only, I see 278MH/s LBC. Good day. Tell me what kind of error and whether it affects what the realties. ETH: Received error: {"id":4,"result":null,"error":[21,"jobnotfound"]}
Stale share response. Probably your pool does not accept stale shares, which is not good for ETH.
|
|
|
Claymore, is there any workaround for gtx 1080 (372.90 / win 10) and not getting 5 Mhs ?
Would say it's ok if yours was 1070, but it's 1080. I'm on GTX 970 Ti and Win 10 Anniversary x64 and get 4 Mhs (which i don't think it's ok). Drivers don't change it, latest or 352.84. For 9xx on Win10 you should use old drivers like 352.xx and miner cuda 6.5. From OP: NVIDIA DRIVERS: 9xx cards in Windows 7 x64: just use latest/recent drivers from Nvidia website (for example, 368.81). Note that latest 372.54 is slower than 368.81. 9xx cards in Windows 10 x64: you have to use old drivers (for example, 352.xx) and miner built for cuda6.5. 10xx cards in Windows 7 x64: just use latest 372.54 drivers from Nvidia website. 10xx cards in Windows 10 x64: just use latest 372.54 drivers from Nvidia website, note that you must have Win10 Anniversary update. @claymore, eth + SC or eth+lbc is 2%fee... eth +dcr 1%fee? that's according to op on 1st page. mind to clarify? thx.
From OP or Readme: This miner is free-to-use, however, current developer fee is 1% for Ethereum-only mining mode (-mode 1) and 2% for Ethereum+Decred mining mode (-mode 0) Well, if you think it is not clear, I will change it to: current developer fee is 1% for Ethereum-only mining mode (-mode 1) and 2% for dual mining mode (-mode 0)
|
|
|
Is there any way to specify difficulty in dual mining? like lbry static difficulty setting? Thank you
Difficulty means share target? Pool sets it. Command tar failed with return code 0 and error message Like in previous version... What does it mean?
I copied History.txt from Windows machine to Linux and Linux changed its time for some reason to future. Have no idea why it happend since other files have correct timestamp and original History.txt has correct time. May be another Linux "feature". You have to wait a day until it work, or change time on your system, or disable time checking in "tar" somehow. Claymore, is there any workaround for gtx 1080 (372.90 / win 10) and not getting 5 Mhs ?
Yes, Windows 10 Anniversary + latest drivers wddm 2.1. Claymore my miner thread hangs frequently, and it wont restart. I mean when remote-connect to the machine and on the miner window press down arrow "miner thread hanged, restarting" message pops up, but untill I do so, the machine just stays in freeze mode for 4 - 6 hours causing me significant loss. I need to keep checking on machines almost regular. I have set the miner to restart every 60 minutes with -r 60 but nothing happens. I'm using Ver 7.1 of your miner on RX 470's, 16.9.2 drivers on Win 10.
I'll try to reproduce it, PM me the complete log file. - added temperature/fan monitoring for Linux version for gpu-pro drivers. Only monitoring is supported currently, not management.
The temp monitor will work in linux right ? if it is overheat it will stop the gpu Yes it must work in Linux+gpupro drivers. All features must work except fan management.
|
|
|
is it possible to have 2.5% fee, boost hasrate and support [XMG] Magi ? it ll be great thanks in advance br 1. As always, I'm ready to reduce dev fee if someone who is not too lazy creates a good AMD miner to make some competition. 2. XMG requires some efforts, I will do it when I have time, right now I'm really busy with other miners. Have you devoloped any xmg miner,are you thinking to release it? I still have no time for it
|
|
|
Thanks Claymore ! Is it going to be posted on google drive soon ? I don't see it yet.
It is something related to google drive. Logout from google account and try to download, it's already there.
|
|
|
@Claymore I have some questions I use your miner for solo mining. When I solo mine 7.0 version rigs find more block then 7.1. Because of this I turned back to 7.0. I think something is wrong with 7.1 for solo mining and also if there is an issue, I don't know it still exists in 7.2 too. I use geth windows for etc. I run it from a different pc from the rigs in lan. Is it possible to put an option for GTX 1070 cards to disable fan speed monitoring from miner? I have RX 470 and GTX 1070 but I still don't know Which ''-etha'' option must I use for my card. If you write optimized cards or slow cards, I will be glad. My last question is about ''-etht'' Would you put more explanation about it? There aren't too much things and option in read me and mining forum communities. Because of this I need your help to use all the options for full optimization.
1. I did not change anything in speed. If you think that v7.0 works faster - use it. Because I cannot fix issue that does not exist. 2. You can only disable entire monitoring with "-tt 0". 3. Try all "-etha" values and see hashrates, then select the best for your card. It will not take much time. "-etha" is applied for AMD cards only. 4. In solo mode miner doesn't use stratum. So miner sometimes connects to geth and asks for current job. Default value is good for local network. Original ethminer has same option called "--farm-recheck". I'm still on version 6.4 It has been stable for weeks now, so I don't see any reason why I should change. Unless there is some mining speed improvement That was not the case with version 7.0, and a lot of folks felt that. @Claymore, have made any improvements to the mining code? PS: I run RX 480s No. When I do it, I will mention it in "History.txt".
|
|
|
v7.2:
- added "-lidag" option to reduce intensity of DAG generation, it can help with OC or weak PSU. - added temperature/fan monitoring for Linux version for gpu-pro drivers. Only monitoring is supported currently, not management. - "r" key reloads pools from epools.txt and dpools.txt in runtime. - fixed issue with wrong detection of card names. - systems with up to 32 GPUs are supported now (with some minor limitations). - Linux version: fixed issue with closing miner with "Ctrl-C". - several minor improvements and bug fixes. - EthMan: added "total online miners" and "total working gpus" info. - EthMan: added color and font size options for the list of miners.
Thank you claymore, you're the best. I only wished you would open source ethman so we can make it a lot better. With WireShark you can see JSON protocol details and create own even better tool in your favorite programming language. A few devs already did it, for example, there is app for Android.
|
|
|
v7.2:
- added "-lidag" option to reduce intensity of DAG generation, it can help with OC or weak PSU. - added temperature/fan monitoring for Linux version for gpu-pro drivers. Only monitoring is supported currently, not management. - "r" key reloads pools from epools.txt and dpools.txt in runtime. - fixed issue with wrong detection of card names. - systems with up to 32 GPUs are supported now (with some minor limitations). - Linux version: fixed issue with closing miner with "Ctrl-C". - several minor improvements and bug fixes. - EthMan: added "total online miners" and "total working gpus" info. - EthMan: added color and font size options for the list of miners.
|
|
|
Hello
Its possible that claymore bat send a email to me when miner stopped?
Thanks
You can execute .bat file in EthMan when miner stopped/disconnected/overheated or its hashrate is low. Probably you can send email from .bat. Miner itself cannot send email, use pool for it.
|
|
|
is it a known issue with rx 480 8gb that it takes 60-90 seconds after showing "POOL/SOLO version" for the miner to proceed to DAG generation? happens on all my 4 rigs with windows 7/windows 10
It depends on CPU speed, GPU name and number of GPUs, OpenCL recompiles kernels when necessary (for some cards). In past it worked faster, but currently miner has a lot of GPU code. I will reduce this delay, it's in my todo list.
|
|
|
Claymore, you could fix the issue when using NVIDIA GPUs without fans (watercooling, server-grade GPUs, etc.):
Ok, I see, you mean not to show messages. Ok, I will hide messages so they will appear in log file only. Claymore, any idea what the following might be? 4x RX470, win10: 10:56:51:597 1150 em hbt: 0, dm hbt: 0, fm hbt: 63, 10:56:51:597 1150 watchdog - thread 0, hb time 78 10:56:51:613 1150 watchdog - thread 1, hb time 219 10:56:51:613 1150 watchdog - thread 2, hb time 219 10:56:51:613 1150 watchdog - thread 3, hb time 94 10:56:51:613 1150 watchdog - thread 4, hb time 109 10:56:51:613 1150 watchdog - thread 5, hb time 234 10:56:51:613 1150 watchdog - thread 6, hb time 23828 10:56:51:628 1150 watchdog - thread 7, hb time 23688 10:56:51:628 1150 WATCHDOG: GPU error, you need to restart miner Faulty GPU, or Riser? Thanks in advance, if you have a XMR address I'll buy you an untraceable beer^^ Probably riser if you don't overclock GPUs. Due to dev fee you already buy me a beer when you use my miner
|
|
|
3 threads put it down to 47:
Well, try also 4 and 6 values to find the best. Fast mode speedups hashrate for most CPUs, but not for all. Probably it depends on CPU speed - on laptops sometimes I see that fast mode causes even slower speed, but I don't disable fast mode because the miner is not for laptops, though I can add such option.
|
|
|
Claymore could you make something like "GPU-reordering" command, so that the GPU number in miner and in GPU-Z are synchronized? Both for ETH and XMR miner.
Use "-di" option for that, see readme for Dual miner for detailed explanations.
|
|
|
-logfile 0 do not working at 7.1
Where did you find "-logfile 0" option value? It must be filename, not "0" or "1" (or do you want to name file as "0"?). From readme: -logfile debug log file name. After restart, miner will append new log data to the same file. If you want to clear old log data, file name must contain "noappend" string. If missed, default file name will be used. If you want to disable logging, use "-dbg -1".
|
|
|
finally got fast mode enabled.. but it does not seam to be faster then when it said slow mode. I have a phenom 6 core:
Hashrate depends on several factors. Try to change "-t" value to find best hashrate. From readme: -t number of threads. "-t 0" - autoselection. Autoselection does not work fine in all cases, so try different values. Optimal value depends mostly on L3 cache size. For example, if your CPU has 8 MB of L3 cache (i7 CPUs), use "-t 4". For 6MB L3 cache (i5 CPUs) use "-t 3". I doubt that your CPU has 10MB cache to use 5 threads, try "-t 3".
|
|
|
|