this is what i get from suprnova when changing all rigs to v3
!!! WARNING !!! You seem to be sending a large amount of INVALID shares ! Check your rigs, you might be mining the wrong algo and your hashrate could be displayed wrong! !!! WARNING !!!
invalid shares are about 40-50%
will try v3.1
make a new worker eth hash went down mining on dwarfpool from 3.0 to 3.1 for tahiti cards If you get invalid shares - remove DAG files. To test exact hashrate you need at least 24 hours for fast rig and 48 hours for slow rig. My test rigs don't show any slowdown for both v3.0 and v3.1 for now. |
|
|
|
The problem occurs ... maybe someone at coinotron can confirm ... or not  ? History.txt: v2.0 ... - Added "-esm 2" option for "miner-proxy" Stratum version - for such pools like coinotron, coinmine, etc. ... So you need at least v2.0, not v1.2 |
|
|
|
Hi Claymore,
I'm already using "-esm 2" but "qtminer stratum mode" is activate any way. Maybe you have a problem with this stratum type implementation ? ... Please check
So if you take my command line (I posted it above) with no changes you see "qtminer mode"? If so, we need someone to confirm it because I cannot reproduce it, for me it shows "miner-proxy stratum mode". Here is my command line again: EthDcrMiner64.exe -epool coinotron.com:3344 -ewal Redhex.rig1 -esm 2 -epsw x -allpools 1 |
|
|
|
I really have no idea why you cannot make it work with coinotron. Here is my command line and it works, you can check it:
EthDcrMiner64.exe -epool coinotron.com:3344 -ewal Redhex.rig1 -esm 2 -epsw x -allpools 1
"Redhex" is my login, "rig1" is my worker name, "x" is worker's password. If you use your login, worker and password and it does not work it means that you are doing something wrong, check everything again and again until you find the mistake.
Hi again, Still same error: ... POOL version No pool specified for Decred! Ethereum-only mining mode is enabled ETHEREUM-ONLY MINING MODE ENABLED (-mode 1) ETH: qtminer stratum mode ETH: Stratum - connecting to 'coinotron.com' <178.217.186.125> port 3344 ETH: Stratum - Connected Auth failed : {"id":0,"result":null,"error":[-32600,"InvalidRequest",null]} I have inclusive change my worker and password name to "PC14" and restart my machine but same problem ! My computer is running windows 7 ... "-esm 2" is the key. Miner shows it: "qtminer stratum mode". coinotron does not work with qtminer, it works with "miner-proxy" which is enabled with "-esm 2", not with "-esm 1". |
|
|
|
|
I really have no idea why you cannot make it work with coinotron. Here is my command line and it works, you can check it:
EthDcrMiner64.exe -epool coinotron.com:3344 -ewal Redhex.rig1 -esm 2 -epsw x -allpools 1
"Redhex" is my login, "rig1" is my worker name, "x" is worker's password. If you use your login, worker and password and it does not work it means that you are doing something wrong, check everything again and again until you find the mistake.
|
|
|
|
found this too, but didnīt work here. myAccount.myWorker:Password seems to be a problem.
Authorization failed
:{"id":2,"result":null,"error":[-32600,"InvalidRequest",0}
For password there is "-epsw" option. Don't try to put password to "-eworker", sample demonstrates it clearly. Tried several variations, error above comes with -eworker myAccount.myWorker -epswd Password Full command line please. |
|
|
|
For the -wd watch dog function, the default is -wd 1. If I do not want the watch dog, what do I put, should that be -wd 0?
Yes. |
|
|
|
Yes I found "eth_submitHashrate" but I'd like to check some miner that sends this command to see how it works. There is no any documentation about it but it seems it has two params: first is the hashrate, second is filled by random and it's strange, it must be worker name so pool can know who reports the hashrate.
https://github.com/ethereum/wiki/wiki/JSON-RPC#eth_submithashrateParams: 1. Hashrate, a hexadecimal string representation (32 bytes) of the hash rate 2. ID, String - A random hexadecimal(32 bytes) ID identifying the client I am fairly sure most of the pools just ignore the ID string. Could ask dr_pra or miningpoolhub to confirm how they how they handle it. Ok, but if there are many workers and they send their hashrate - how pool will detect what hashrate from what worker? Seems strange for me, that's why I'd like to see working miner with Stratum to see how it works. |
|
|
|
found this too, but didnīt work here. myAccount.myWorker:Password seems to be a problem.
Authorization failed
:{"id":2,"result":null,"error":[-32600,"InvalidRequest",0}
For password there is "-epsw" option. Don't try to put password to "-eworker", sample demonstrates it clearly. |
|
|
|
Yes I found "eth_submitHashrate" but I'd like to check some miner that sends this command to see how it works. There is no any documentation about it but it seems it has two params: first is the hashrate, second is filled by random and it's strange, it must be worker name so pool can know who reports the hashrate. |
|
|
|
v3.1:
you can add vrm temp monitoring? my card critical point vrm not gpu 7990 not correct -tt monitoring and freq management - only 1 gpu see Try to disable CrossFire if you see only one card. |
|
|
|
Is Json Api for remote monitoring planned ?
Yes, looking for existing solutions for that. |
|
|
|
|
v3.1:
- reduced delays at shares sending, it must improve speed on pools a bit.
It is not a major update, just found some additional delays in v3.0 so I uplodaded an update. No other changes.
PS. I see dwarfpool has "Sent hashrate" column. How to make it work? I tried eth-proxy + ethminer but it is still empty. If someone can point me how to make it work for Stratum I will add it to my miner.
|
|
|
|
I have the same problem as DaveyJones. v3.0 not working for me.
When i run it through CMD it prompts the parameters and does nothing at all. No errors, no works, nothing.
Win7 x64, R9 380x, Crimson 15.12 (Crimson 16.1)
Bumping ... started with the 2.0 version Sorry, I have no idea why you see it. I think it must be something related to some software on your system. You can try it on clean Windows to check if it is true. Why should it be a software issue when everything till 1.2 ran fine? Must be a change that came into your miner between 1.2 and 2.0 I use third-party EXE packer to protect miner from disassembling and changes, perhaps it can cause such thing but I cannot remove it because I have some experience about how my miners can be used if they don't have this protection. Anyway, it works for >99% systems. So your system must have something special. |
|
|
|
I have the same problem as DaveyJones. v3.0 not working for me.
When i run it through CMD it prompts the parameters and does nothing at all. No errors, no works, nothing.
Win7 x64, R9 380x, Crimson 15.12 (Crimson 16.1)
Bumping ... started with the 2.0 version Sorry, I have no idea why you see it. I think it must be something related to some software on your system. You can try it on clean Windows to check if it is true. |
|
|
|
@Claymore <-- seems to get your attention  Any idea, v3 seems to crash after a while on 6x nano. v2 works perfectly (same settings, nothing changed) Also, speed remains the same. No improvement, in some cases even less.. As i said before, all my other rigs with older cards are doing A LOT better. So kudos on that!  No ideas about crashes, for Fury there are not any improvements, though on my Nano I don't see any slowdown, same speed exactly. |
|
|
|
@Claymore, because of the new check of invalid shares which checks before submition, is there any way to check how many invalids i have? Isnt it better to be send to pool to check are they valid or not and not loosing computing power locally...
Checking share locally takes 25-50mcs only. Pool can reject shares for several reasons, so checking share locally to detect tha GPU works incorrectly is a good idea. You can find "overclock" word in log file to find warning, perhaps I will also add a special text in miner stats about it. |
|
|
|
EthDcrMiner64.exe -epool coinotron.com:3344 -ewal almartins.PC-14 -esm 0 -epsw PC-14 -allpools 1
What are your oppinion ?
Regards
Are you sure this is the name of your worker? Follow the instructions on the OP: "-epsw Password for Ethereum pool, use "x" as password." Verifique o nome dos seus "workers" e a sua palavra passe. Tem a certeza que a palavra passe é "PC-14"? Boa sorte!  Check the instructions on the OP more carefully. You will notice "-esm 2" option for coinotron. |
|
|
|
with your coinotron example I only get "Authorisation failed" - no mining possible.
Probably there is one more text line after that line in red, it contains something like "Wrongworkernameorpassword". |
|
|
|
|
Nvidia - no. Failover - yes, in next release.
|
|
|
|
|
Show Posts
