Post
Topic
Board Mining (Altcoins)
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.8 (Windows/Linux)
by
project13et
on 26/08/2017, 11:51:48 UTC
There are too many miners that use the software, and most of them use Linux .. so problems like this are isolated and will probably not gone be fixed, since they are not even seen as a problem by author. As simple as that we are invited to use a different software if we don't like what we get , or to resolve the issue our self a simple fuck off... even if some of us are new register doesn't mean we where not here from the begin.
If is not a software issue then why Claymore zCash works fine with all AMD cards, or Claymore dual mining works to launch simulate multiple scripts?
...btw similar issue describe by youtuber Cryptomined in one of his video.
Thanks,

1. Mining process involves several things: hardware, OS, drivers, miner software, internet connection, pool. To make sure that the problem is in miner, it is a good idea to confirm it by checking that other miners work as expected.
Same for other things, for example, to make sure that the problem is in pool, you should try to use some different pool to confirm it. That's why I tell you to try different miner, not because I'm going to ignore issues related to my miner.
For example, yesterday some people had probems with DAG #128, some of them were sure that the problem is in my miner, I said that it's a good idea to try different miner or pool to confirm the reason, because this problem can be due to miner or due to pool. I said it not because I don't care.
2. This issue can be related to miner or to drivers, or to hardware, but if other miners work, it will prove that the problem is in miner. Other coins require different OpenCL parameters so miners for ZEC may work fine. Also OpenCL drivers may have some bugs/limitations that allow to use all cards from different miner instances but fail if all calls are from single instance.
3. Note that right now I cannot investigate the issue directly because I don't have mb with 12 pcie, it was not necessary for me until today and it will take some time to buy it. So right now I can only suggest to confirm the reason of the issue by checking if other miners work. I can also check log files if you PM me them, that's all I can do.
[/quote]
I can confirm that I just try multiple pools on different servers didn't fix the problem, in the past I remember one of my rig that had 10 cards inside it worked fine with 7 AMD and 3 Nvidia and running by Claymore miner, so maybe it has something to do with mapping 13 GPU's

Regarding hardware I can say that I have this problem on all combinations GTX 1070 with RX 580 / GTX 1060 with RX 570 or GTX 1060 with RX 580 etc. All my AMD cards in the 13 rig slots are 5xx but with multiple Nvidia cards.

Regarding internet connection I run dual WAN 1GB with 100MB bandwish for backup both with guarantee band from provider.
Same story with the divers I try multiple drivers from AMD , mixed drivers for old versions or latest one.

I will try to investigate more during weekend and to clean up all the logs on one system and to send you some clean logs.

Thank you,

After testing all morning I can confirm the problem I present and also other members is NOT present with another miner software.

I tested on 2 rig's with 13 cards Sgminer version 5.5.5 and everything is working fine, all the AMD cards are loaded , no frozen similar to Claymore miner.

Here is a imagine proof that all 7 AMD are working, on the other rig I got 8x580 AMD cards.
https://i.gyazo.com/86d91bc377a7352d9c021fcd75764a39.png


The SgMiner use only --gpu-platform 1 parameter and the .conf file included:
{
  "pools": [
    {
      "name": "Ethermine",
      "nfactor": "10",
      "algorithm": "ethash",
      "url": "eu1.ethermine.org:4444",
      "user": "Rig",
      "pass": "x"
    }
  ],
  "api-port": "4032",
  "failover-only": true,
  "api-listen": true,
  "api-allow": "W:127.0.0.1/32",
  "expiry": "120",
  "log": "5",
  "queue": "1",
  "scan-time": "60",
  "temp-hysteresis": "3"
}

From my point of view I eliminate all the other possible variables: pools, drivers, mixed cards models etc, so is clear that the last possibility that the problem to be from the miner have been confirmed since the problem is not present on another miner software.


Can you please look at this and try to fix it?
Thank you