Version 4.1, like all previous ones, still uses a weird ID scheme and it can be a bit confusing when the miner's GPU 0 is Afterburner's GPU 3 or something like that.
Check my explanations: https://bitcointalk.org/index.php?topic=1433925.msg14659010;topicseen#msg14659010So there is no way to fix GPUs order automatically, thanks to AMD devs. But you can do it manually. For example, if you have two cards, you can change their order by adding "-di 10". Another example, reverse order for six cards: "-di 543210". |
|
|
|
Claymore, please, add decred support on miningrigrentals
It must work there if they support http or stratum. is not working: DCR:job timeout, retry in 20 sec... they support stratum: Miner Configuration Examples miningrigrentals : ccminer/cgminer -o stratum+tcp://eu-01.miningrigrentals.com:3333 -u xxx.xxx -p x PM me the log file. |
|
|
|
Claymore, please, add decred support on miningrigrentals
It must work there if they support http or stratum. |
|
|
|
Claymore, please, add power limit
Ok, it will be added in next update. |
|
|
|
Where is the problem please help me...
From your screenshot miner hangs not after 1 day but at starting. |
|
|
|
|
Check the thread, some pages ago someone mentioned that he runs miner on a system with 1GB of system RAM.
|
|
|
|
Hi Claymore, Sorry if I missed it, but do you plan on integrating some sort of API that will send stats to an IP address so that I can build a little webpage to check on my miners? Thank you  It will work in a different way: in a few days I will release utility-proxy that will monitor rigs and will have web server that displays status. |
|
|
|
Claymore, In certain cases after automatic respawn of the miner, the DAG can't be loaded error appears (I don't remember the exact words). I'm talking about ubuntu 15.04 with catalyst 15.12. It is an error that used to happen with the stock ethminer and the only solution was to reboot the computer. Is it possible to make the watchdog flush the GPU ram before respawning the miner?
The only option is to reboot computer. Miner must execute "reboot.bash" if you use "-r 1", though I did not test it in Linux. If it does not work, send me sample "reboot.bash" that must reboot computer and I will check it. |
|
|
|
Claymore - do we need to put "--no-precompute" in batch file to ensure DAG files are current? Just curious.
I hardly see any rejects mining at ethpool, so surely DAGs are ok.
I have read somewhere that a guy got no rewards because he was mining with a wrong DAG. Thanks
Do you see "--no-precompute" option in readme file? I don't see So it is not supported. DAGs are often corrupted when they are stored as files. But now miner generates DAGs on GPU so it can be corrupted only if your GPU does not work properly. I did not see such behaviour yet. If I get some feedbacks about it, I can add CRC check for DAGs (so GPU will check CRC after DAG generation). thanks - that makes sense - my shares are accepted since day 1 using the dual miner, so I guess my cards are functioning well. however, this case about someone mining on a wrong DAG (not corrupted) but maybe a past version -- I wonder how does a case like that happen? Miner will show you warnings that GPU finds incorrect shares again and again. Such incorrect shares won't be sent to pool. |
|
|
|
Claymore - do we need to put "--no-precompute" in batch file to ensure DAG files are current? Just curious.
I hardly see any rejects mining at ethpool, so surely DAGs are ok.
I have read somewhere that a guy got no rewards because he was mining with a wrong DAG. Thanks
Do you see "--no-precompute" option in readme file? I don't see So it is not supported. DAGs are often corrupted when they are stored as files. But now miner generates DAGs on GPU so it can be corrupted only if your GPU does not work properly. I did not see such behaviour yet. If I get some feedbacks about it, I can add CRC check for DAGs (so GPU will check CRC after DAG generation). |
|
|
|
Claymore help, I am getting way too much of fluctuation in my effective hash rate in 4.1 miner for windows. Miner shows 62.4MH/s but effective is 55 MH/s, and it goes down to 40 and up to 65 etc. With 3.2 miner I got way better effective hash rate. Help?
I got -ethi 16 and ethermine pool.
With your hashrate (<100MH) you should run miner for at least 24 hours to see average hashrate. Run 3.2 and 4.1 for 24 hours and compare average hashrates, they must be the same. Checking miner for a few hours with not very high hashrate is not a good idea. If you still see that 3.2 works much faster: I did not change OpenCL code between these versions, so it must be some kind of magic I think. |
|
|
|
Testet it over the last night.
Made no difference for me at dwarfpool. Switched back to ethminer.
I'm on Ubuntu with 4x R9 280x.
Any suggestions how to improve? Also tried -ethi -16384 and it just got slower. try set "-etha" to "0" and then to "1". From readme: ..... -etha Ethereum algorithm mode. 0 - optimized for fast cards, 1 - optimized for slow cards. -1 - autodetect (default). You can also set this option for every card individually, for example "-etha 0,1,0". ..... If it does not help - make sure you use Catalyst 15.12. If still see higher hashrate on pool with ethminer - use it. PS. For Dual mode: I get the best hashrate on Ethereum if I change Decred intensity manually by "+" and "-" keys at some value (press "s" to see current stats). After that you can set best found value with "-dcri" option. |
|
|
|
Hi Claymore and thank you for the miner,
on my pc with ubuntu 14.04 the current consumption increases by approximately about 20% (and temperature) respect ethminer, if I use "mode 1" (only eth) and "-ethi 6" the consumtpion it's similar.
This is it normal? or it's a linux problem?
If you mine Ethereum+Decred the power consumption will be higher than if you mine Ethereum only. |
|
|
|
|
- UPDATE: Fixed bug with Linux build when miner shows message "read(): Resource temporarily unavailable", re-download v4.1 for Linux.
|
|
|
|
UPDATE: Fixed bug with Linux build when miner is closed after some time, re-download v4.1 for Linux.
Testing again  I have been testing overnight and there is another problem. The miners don't stop mining, shares are still coming on both eth and dcr but this issue appears: read(): Resource temporarily unavailable read(): Resource temporarily unavailable read(): Resource temporarily unavailable read(): Resource temporarily unavailable read(): Resource temporarily unavailable read(): Resource temporarily unavailable read(): Resource temporarily unavailable read(): Resource temporarily unavailable read(): Resource temporarily unavailable ... Very fast scrolling, and cpu usage skyrockets. Looks like another bug with porting sockets to Linux. Today I will check/fix it. |
|
|
|
why do i need -allpools 1 when mining to dwarfpool. in the example i doesnt have it.
EthDcrMiner64.exe -allpools 1 -epool eth-eu.dwarfpool.com:8008 -ewal xx -epsw x -eworker gpu1 -dpool stratum+tcp://dcr.suprnova.cc:2252 -dwal x.dcr -dpsw x -dcri 40
and it 30.5-31MHs eth and about 600 dcr good speeds ? for a 390x running at 1100mhz @75c
Why do you think that you need "-allpools 1" for dwarfpool? Use this: EthDcrMiner64.exe -epool eth-eu.dwarfpool.com:8008 -ewal 0xD69af2A796A737A103F12d2f0BCC563a13900E6F/YourWorkerName -epsw x i get this if use that You use different command line. My command line sample cannot cause this error. If you don't believe me, ask someone here to test my command line and confirm that it works. my bad then. i'll have a look and see what i've done wrong. copy/paste the commandline from the readme change the wallet and u/p for dcr and i got the same error This pool (eth-eu.dwarfpool.com) does not support Ethereum addresses as login (or requires worker name in "Login.Worker" format) and cannot be used for devfee mining, therefore it is not supported. 11:56:03:329 2b58 However, you can mine on this pool if you specify "-allpools 1" option, default pools (different from this pool) will be used for devfee. i must be stupid but there is no login for dwarf i must be missing something.. sorry for beeing the stupid one.. someone needs to be :p Do not change wallet. Works? It means that your wallet address is incorrect. |
|
|
|
why do i need -allpools 1 when mining to dwarfpool. in the example i doesnt have it.
EthDcrMiner64.exe -allpools 1 -epool eth-eu.dwarfpool.com:8008 -ewal xx -epsw x -eworker gpu1 -dpool stratum+tcp://dcr.suprnova.cc:2252 -dwal x.dcr -dpsw x -dcri 40
and it 30.5-31MHs eth and about 600 dcr good speeds ? for a 390x running at 1100mhz @75c
Why do you think that you need "-allpools 1" for dwarfpool? Use this: EthDcrMiner64.exe -epool eth-eu.dwarfpool.com:8008 -ewal 0xD69af2A796A737A103F12d2f0BCC563a13900E6F/YourWorkerName -epsw x i get this if use that You use different command line. My command line sample cannot cause this error. If you don't believe me, ask someone here to test my command line and confirm that it works. |
|
|
|
Dwarfpool help recommends to use WALLET/WORKER format. This works for me:
EthDcrMiner64.exe -epool eth-eu.dwarfpool.com:8008 -ewal 0xD69af2A796A737A103F12d2f0BCC563a13900E6F/SampleRig -epsw x
This sample works. It looks like my fault is that I always RTFM (in this case, the README!!!.txt for the miner) :-) - the examples for ethpool/ethermine do NOT show how to use rig name; - the example for Dwarfpool does NOT show how to use rig name, but says 'you can also specify "-eworker YourWorkerName" option' - exactly that I did and that does not work. So for both ethermine and dwarfpool the -eworker option does not work as expected. I would recommend you either update examples with rig names, or add a note that -eworker might not work, and in that case makes sense to use pool-recommended format with dot or slash for the rig name. Since no source available, it is not obvious if wallet name should/may be concatenated with other URL options like rig or password, because there are options for them and maybe there are same in the stratum protocol variations. It's also a good idea to read RTFM for pool. I will update sample for dwarfpool, you are right, current sample is not good if you want to see hashrate. I had to add "-eworker" because there are 3 stratum versions and many pools that also add some variants on these versions for logon process. Some pools ignore "-worker" but search worker name in wallet string, some require only wallet as username but require worker name when worker sends a share. Some work with both approaches but don't show hashrate as expected. Such problems are not related to the miner, they are because of some chaos in Ethereum stratum implementations on pools. |
|
|
|
why do i need -allpools 1 when mining to dwarfpool. in the example i doesnt have it.
EthDcrMiner64.exe -allpools 1 -epool eth-eu.dwarfpool.com:8008 -ewal xx -epsw x -eworker gpu1 -dpool stratum+tcp://dcr.suprnova.cc:2252 -dwal x.dcr -dpsw x -dcri 40
and it 30.5-31MHs eth and about 600 dcr good speeds ? for a 390x running at 1100mhz @75c
Why do you think that you need "-allpools 1" for dwarfpool? Use this: EthDcrMiner64.exe -epool eth-eu.dwarfpool.com:8008 -ewal 0xD69af2A796A737A103F12d2f0BCC563a13900E6F/YourWorkerName -epsw x |
|
|
|
Yes, it sends hashrate in -esm 0. Since I see no hashrate report, could you please give a definitely working command line for that? As with the case of ethermine I suspect that the miner has some issues with command line parsing. At least for ethermine the shares reports depend on the command line args order. So I suspect the same is with -esm 0. To be precise, here is the command line which does NOT report hashrate to dwarfpool: EthDcrMiner64.exe -epool eth-ru.dwarfpool.com:8008 -ewal 0xab..cd -eworker rig01 -epsw monitor@email.com -esm 0 Dwarfpool help recommends to use WALLET/WORKER format. This works for me: EthDcrMiner64.exe -epool eth-eu.dwarfpool.com:8008 -ewal 0xD69af2A796A737A103F12d2f0BCC563a13900E6F/SampleRig -epsw x |
|
|
|
|
Show Posts
