Re: [ANN] sgminer v5 - new unified multi-algorithm on-the-fly kernel switching miner

Is there a log file that I can look through to see what is causing an issue?

I added a restart crontab as a hacky fix for now. Unsure if it will work.

On Asus DCII 280x x 6 :

Code:

{
   "pools": [
   {
   "name": "TradeMyBit_X11",
   "url": "stratum+tcp://west01.us.trademybit.com:4010",
   "user": "x",
   "pass": "x",
   "nfactor": "10",
   "algorithm": "darkcoin-mod",
   "profile": "X-Coins"
   },
   {
   "name": "TradeMyBit_X13",
   "url": "stratum+tcp://west01.us.trademybit.com:4011",
   "user": "x",
   "pass": "x",
   "nfactor": "10",
   "algorithm": "marucoin-mod",
   "profile": "X-Coins"
   },
   {
   "name": "TradeMyBit_X15",
   "url": "stratum+tcp://west01.us.trademybit.com:4012",
   "user": "x",
   "pass": "x",
   "algorithm": "bitblock",
   "profile": "X-Coins"
   },
   {
   "name": "TradeMyBit_Nist5",
   "url": "stratum+tcp://west01.us.trademybit.com:4013",
   "user": "x",
   "pass": "x",
   "algorithm": "talkcoin-mod",
   "profile": "Nist5"
   },
   {
   "name": "TradeMyBit_Scrypt-N",
   "url": "stratum+tcp://west01.us.trademybit.com:2220",
   "user": "x",
   "pass": "x",
   "profile": "Scrypt-N"
   },
   {
   "name": "TradeMyBit_Scrypt",
   "url": "stratum+tcp://west01.us.trademybit.com:3330",
   "user": "x",
   "pass": "x",
   "nfactor": "10",
   "algorithm": "zuikkis"
   }
   ],
   "profiles": [
   {
   "name": "X-Coins",
   "intensity": "16",
   "gpu-engine": "1100",
   "gpu-memclock": "1800"
   },
   {
   "name": "Scrypt-N",
   "intensity": "13",
   "gpu-threads": "1",
   "gpu-engine": "1000",
   "gpu-memclock": "1500",
   "thread-concurrency": "10240"
   },
   {
   "name": "Nist5",
   "worksize": "64",
   "intensity": "18",
   "hamsi-expand-big": "1",
   "gpu-powertune": "8"
   }
   ],
   "hamsi-expand-big": "4",
   "worksize": "256",
   "thread-concurrency": "8192",

   "gpu-threads": "2",
   "gpu-powertune": "20",
   "gpu-engine": "1070",
   "gpu-memclock": "1600",

   "auto-fan": true,
   "gpu-fan": "50-85",
   "temp-target": "75",
   "temp-cutoff": "95",
   "temp-overheat": "85",

   "api-listen": true,
   "api-port": "4028",
   "api-mcast-port": "4028",
   "api-allow": "W:127.0.0.1",

   "queue": "0",
   "expiry": "1",
   "show-coindiff": true,
   "no-submit-stale": true,
   "failover-only": true,
   "failover-switch-delay": "30",
   "extranonce-subscription": true,
   "no-extranonce": true,
   "hotplug": "5",
   "no-restart": true,
   "remove-disabled": true
}

hmm have you tried all the different algo's individually to make sure they all work?
i know TC for nscrypt is about half of what it is for scrypt
also if you recently updated to 14.6 drivers TC will need to be reevaluated
other than that, your cards seem to be able to run way higher mem clocks than any of mine (sapphire 290x BF4 edition, and gigabyte 290 windforce) mine crash if i go above 1400 for any length of time

They all do work by themselves.

I just added the scrypt-n today, so I know it didn't cause the locks in the past few days. Going to remove scrypt-n for now just to keep things simple.

In sitting here at work, I have watched it switch back and forth multiple times without issue.

Do these things kinda pop up randomly? Work great with no HW errors or rejects and then boom dead?

I appreciate your help!

in my experience when you have a miner that runs fine for a while then suddenly goes sick the clocks are set just a tad too high
my 290's will run fine at 1100/1400 for a while then at some random time 1 or both will go sick on me
i solved that by setting them at 1075/1350 and no more problems
granted i lost the extra 200kh/s i was getting per card but that does't help if they crash all the time
and yes they will be hashing perfect and just suddenly go sick