On the rigs that i have connected to the same network as my ETH Pool ( one PC running geth ) i get the
"No new jobs where received from the pool" error
its connected to the pool, it shows GPU temp but it wont start mining
any suggestions?
geth must show "imported 1 block" message a few times per minute. If it does not, that's the reason. |
|
|
|
@ Claymore
Which windows Version is recommened for the Rx470?
Win7 or Win10 no difference for miner. Hi, Claymore!
Will you be adding the up-coming Zcash into your dual mining? They have a bounty of $30k for CPU and GPU miner.
I will not do anything until this coin is released. Hello everybody!
This is weird:
It's a RX 470 Red Dragon 4GB board on an old machine (that I use for tests) running Windows 10 and AMD 16.9.1 drivers.
Claymore recognizes correctly other boards like 4GB Tongas. But reports only 3072 MB on Ellesmeres.
I tried with 3 different models and other driver versions. Always same result.
OpenCL reduced available memory for OpenCL applications on your system, usually it is related to environment variables and size of RAM installed. But detecting 3GB instead of 4GB will not change your mining speed. So what's the problem? |
|
|
|
what is this error ? please help me to use the miner.  Use port 3333, not 80. Use moneropool.com, not .org. You ignored default pools.txt (which contains correct settings for moneropool.com), now it does not work and you have no idea what happend. Read carefully: https://moneropool.com/#getting_started |
|
|
|
Claymore, Can you tell me why this hard locks PC everytime? I have to manually power off / on and it drives me insane lol
System is unstable for some reason, GPU #1 fails. Check hardware. |
|
|
|
for the -cclock and -mclock ; i can't get it to work.
Start miner for 5 minutes and PM me the log file. |
|
|
|
another issue with Linux version, from few days it constantly switching SIA pools every 30-40minutes.. Windows version is ok, even if I revert rigs :S SC: http error #28.
SC: Failed to check work on pool, retry in 10 sec.. This error code means "operation timeout". I can say again and again: don't use Linux if you can use Windows! Most problems are related not to miner but to Linux itself and I have to find workarounds all the time. |
|
|
|
@claymore I like the new v9.6 the remote tool is great. tested it with only 1 mining computer but i couldn't see the Temperature of my gfx cards ( i have 2 MSI RX 480 8gb ). Anything i need to do to get this feature to work properly? I know after runing the application Ethman.exe , an option.ini is generated. didn't take a look at it yet, was late last night when i played with it. Also the -cclock and -mclock didn't do anything for me, i have to say that i use the 16.x drivers ; i know you mention that 15.x works better with your miner, would it be a problem with my drivers? keep up the good work, if you could fix these details and "upgrade" your miner to be more efficient with 16.x drivers. i would be happy. I am waiting to receive 5 more RX 480, so more hash your way soon!  If you use Windows, overclocking must work, check the log for details. Sounds good, i'll try again tonight and check the logs to see what's wrong. Any idea about the temperature not showing in Ethman.exe (the remote tool)? "-tt 1" must help. |
|
|
|
@claymore I like the new v9.6 the remote tool is great. tested it with only 1 mining computer but i couldn't see the Temperature of my gfx cards ( i have 2 MSI RX 480 8gb ). Anything i need to do to get this feature to work properly? I know after runing the application Ethman.exe , an option.ini is generated. didn't take a look at it yet, was late last night when i played with it. Also the -cclock and -mclock didn't do anything for me, i have to say that i use the 16.x drivers ; i know you mention that 15.x works better with your miner, would it be a problem with my drivers? keep up the good work, if you could fix these details and "upgrade" your miner to be more efficient with 16.x drivers. i would be happy. I am waiting to receive 5 more RX 480, so more hash your way soon! If you use Windows, overclocking must work, check the log for details. |
|
|
|
stuck...
It seems now AMD drivers have problems because OpenCL does not work, miner asks OpenCL about AMD platform and it returns nothing. So the reason is in drivers. |
|
|
|
bad issue with SSH linux strikes again  To remind: When I want to end/break/kill screen session miner don't want to hear me  Today I noticed that then GPU hangs and miner restart info.. In previous versions everything was OK... How can I reproduce this issue? |
|
|
|
I am going to mirror the sentiment that intensity needs to be reduced during dag generation. Previous memory OCs were stable, now with the latest epoc they are no longer stable during generation. Please add the ability to reduce intensity on the miner during DAG generation.
I can generate the dag without a memory OC just fine then OC the memory after the miner is running and it works. If I try to generate the DAG while the memory OC is in place the GPUs crash.
Ok, in next update I'll add "-lidag" option. New version will be available in 1-2 days. |
|
|
|
If i run in claymore 7.1 my HD 7990 i have only 36 Mhs ... If i run on ethproxy+ethminer i have 50 mhs why this? Thanks
Because claymore reports the hash rate accurately. I dont think this is the exactly problem ... There are other question i think ... Ethminer show costant 50 mhs and The HD 7990 working fine ... Whit ckaymore this card work many many to hard... And i cant find what is the problem ... And hashrate in solo or dual mode its equal for this GPU near 17+17 ... On ethminer show 50 or 25+25 mhs ...  Make sure you use 15.12 drivers. |
|
|
|
Hello claymore,
I lately had the issue that the miner stops doing anything and if I press a key it starts saying outdated shares 1000s of them and then stating pool maybe had problems and mines again.
It states then the pool had problem but it happened now 3 times in 1h and minergate techs say no issues :-(
What else could cause the miner to pause or hold ?
Windows 10 if you clicked inside of terminal window, if you see cursor inside of terminal it means that Windows paused application and wait until you select text and press escape. If it is not the case then I have no other ideas. HI Claymore, I am also having problems with this issue (app sleeping and hundreds of outdated shares), any suggestions on how to avoid it? Thanks. Jaime I explained my thoughts above: Windows 10 if you clicked inside of terminal window, if you see cursor inside of terminal it means that Windows paused application and wait until you select text and press escape. If it is not the case then I have no other ideas. If you know how I can reproduce it in some different way - let me know and I will check it. |
|
|
|
Claymore in 7.1 when i mixed a tonga card with a 370, 470 and 390 they all got listed as tonga cards.
I think on mixed GPU rigs there's a bug in 7.1 when one card is a tonga. Works fine in 7.0 and below.
Confirmed, will be fixed in next update. |
|
|
|
|
Wow, 11 GPUs. Miner supports only 10 max. Ok I will fix it in next update (hope 16 will be enough) but note that you won't be able to use some options, for example, there is no way to specify card #10 in "-di" option, disable GPU #10 from keyboard etc.
|
|
|
|
@claymore One of my systems has an AMD Pro Duo and I am getting invalid shares from GPU 1. It is not hot and not overclocked. Using Windows 7 64bit with crimson 16.9.2. I have reinstalled it a few times. Is there a setting in Claymore I can change that would effect this ? I am on 7.1.
It's a good idea to tell me how much % of shares are invalid, if it's <0.5% it's ok. If you want zero invalid shares - use "-etha 2" option. If it does not help - something is wrong with your GPU. |
|
|
|
@claymore :
Sure, there is no reason to start talking about hashrate, as that depends completely from your configuration.
Tried to start your miner, to test on eth, I got this result ;
20:16:01:274 abf62840 cudaGetDeviceCount failed (35, CUDA driver version is insufficient for CUDA runtime version), probably no CUDA devices
My version is cuda 7.5 , the highest I get offered for Linux. Prolly that's the error ?
On which of your versions I can fall back ?
thanks !
Linux version of the miner requires CUDA 8. I decided I want to try solo mining with my rigs. Can somebody tell me what eth node is recommended, geth or parity ? And what proxy should I use for it that will work with claymore ? Or do I just point claymore's miner to local node address and everything will be fine/optimal ?
No proxy is required, see "SAMPLE USAGE" section for solo sample. Miner supports both geth and parity. |
|
|
|
1. Definition of eth_submitLogon : {"jsonrpc": "2.0", "id": 2, "method": "eth_submitLogin", "worker": "<WorkerID>", "params": ["<Wallet-Address>", "x"]} Code : https://github.com/sammy007/open-ethereum-pool/blob/master/proxy/stratum.go#L1132. You are mentioned that it would be resulting due connection quallity and so on, but why show other miners accurat hashrates like orginal cpp-ethereum miner or genoil fork ? 1. It seems you see and test only Sammy007 stratum implementation. Unfortunately, there are several others. Here is how I added pools and various stratums: a. Take stratum software (eth-proxy, qtminer, miner-proxy). b. Learn sources, sniff traffic, see data. c. Implement it. Now you take another (fourth? fifth?) stratum implementation which was created after I added all -esm values, and tell me that my miner works incorrectly for all "-esm 0" pools. It is not true because "-esm 0" mode was created for Dwarfpool originally and it works fine there. But it can be true Sammy007 pools, though I remember when I saw first Sammy007-based pool I tested it and it worked well. If it does not, send me some pool address and explain the issue(s) in details, if necessary I will add "-esm 4" for it if other modes don't work. Or, if sending rig name as "worker" in login string will help and solve all issues - just let me know, I will add it in next update and we all will be happy. Again: "-esm 0" was created to work exactly as eth-proxy software, it was not designed for Sammy007 pool, this pool was designed later. 2. I measure time spent in GPU and calculate hashrate as NumberOfHashes/GpuTime, that is all, I don't know how other miners calculate hashrate. If you think that I show more hashrate that miner actually gives, I cannot prove anything because my miner is closed source. The only way to measure real hashrate - test my miner and others and see how much they earn. It's not so difficult if you have several GPUs and not in a hurry, and I'm sure many people already did it. Everyone who sees that Genoil's miner (or ethminer) earns more can use his miner, and vice versa. Talking more about differences in hashrate in miner and pool is useless, all my thoughts I've written in FAQ. |
|
|
|
why did your "fine" miner submit eth1.0 as workername everytime also when -eworker parameter is set ?
"eth1.0" is not related to -eworker parameter, it just marks miner, miner sends "eth1.0" only in "-esm 0" mode and only for "eth_submitLogin" command, in this command you can ignore "worker" at all, it is not used by pools. Though I can send -eworker value there if you want. -eworker value is used in "eth_submitWork" and "eth_submitHashrate" commands only, but most pools that want "-esm 0" mode ignore it even there and take worker name from wallet address (WALLET.WORKER). PS. If "worker: eth1.0" string in "eth_submitLogin" looks strange for you, I can explain more First version of my miner did not have "-eworker" parameter (and "-esm" too), it used "worker" in login string just as miner signature, not as rig name. Then I found that there are several ETH-stratum versions and some of them send rig name in "worker" parameter in some commands, I added it to support these pools. But I did not touch original code for "eth_submitLogin" (because it was not necessary) so it still sends the miner marker. that is not true... all pools at your named esm 0 mode stratum implementation are using it also in eth_submitLogin, but they have implement a workaround to set a fixed workerid when not given like your miner and nicehash do... so that it isn't possible to to identify different rigs ... by the way your hashrate displayed at miner isn't corrct shows exactly 5 % more then the real hashrate messured at stratum-pool directly connected with a lat. of 0 - 1 ms so that this could not be a connection to pool related issue 1. Ok, take Dwarfpool as example of "-esm 0" pool. It uses own eth-proxy software to connect ethminer via stratum to the pool. Sources of eth-proxy are available. Show me the code line that sends worker name in "eth_submitLogin" command and I will agree that I'm wrong. Other "-esm 0" pools must work with eth-proxy properly (because this mode is called "0 - eth-proxy mode" in readme), otherwise you should used "-esm 1" or "-esm 2" mode for them. 2. Please read OP or Readme, "FAQ" section, question "Why pool shows less hashrate than miner?" |
|
|
|
@Claymore
can you explain in what order your read the cards or number the cards ?
With old crimson driver it was easy to determine a faulty card because of aticonfig --lsa printed the gpu number and the PCI ID.. With the PCI ID it was easy to find the PCI-E slot.
Now with amdgpu-pro driver there is no aticonfig tool which prints gpu number and PCI IDs .
So now, if your miner reports an error because of OpenCL hang i only get the GPU number from your miner, but i've no idea what PCI-ID is behind that GPU number to identify faulty card physically.
Thanks
OpenCL: clGetDeviceIDs ADL: ADL_Adapter_NumberOfAdapters_Get why did your "fine" miner submit eth1.0 as workername everytime also when -eworker parameter is set ?
"eth1.0" is not related to -eworker parameter, it just marks miner, miner sends "eth1.0" only in "-esm 0" mode and only for "eth_submitLogin" command, in this command you can ignore "worker" at all, it is not used by pools. Though I can send -eworker value there if you want. -eworker value is used in "eth_submitWork" and "eth_submitHashrate" commands only, but most pools that want "-esm 0" mode ignore it even there and take worker name from wallet address (WALLET.WORKER). PS. If "worker: eth1.0" string in "eth_submitLogin" looks strange for you, I can explain more First version of my miner did not have "-eworker" parameter (and "-esm" too), it used "worker" in login string just as miner signature, not as rig name. Then I found that there are several ETH-stratum versions and some of them send rig name in "worker" parameter in some commands, I added it to support these pools. But I did not touch original code for "eth_submitLogin" (because it was not necessary) so it still sends the miner marker. @Claymore
My Rig temperature is not being reported by 7.1 on windows 10. I have 8 AMD GPU's and it use to work fine. I closed the miner and changed the DRC % from 30 to 20 due to summer hitting us and when i started it only shows GPU 0 temperature.
I have no ideas, sorry, it can be something related to videodrivers. |
|
|
|
|
Show Posts
