GGS now sees my GPUS and loads, but i give it work and the threads become unresponsive and show zero H/S
Confirm, 1.1.9 alpha miner threads unresponsive. This may be recovered only with coldboot in my case (RX470*2). Restarting of thread never work in 1.1.9 and maybe the thread must be completely dropped with freeing its memory and only then we need to start new mining thread.
I have only tested it on neoscrypt.
Alpha 1.1.6 till 1.1.8 are Ok however. But all of the have some other problems as well.
For example I need manually start/stop mining after reasonable amount of time ~ 60...90 minutes. Just because pool looses the miner. Maybe you need to add some more logic to miner, completely disconnecting from pool and reconnecting if and when we cannot mine any share for while (3x average time of finding shares) after 5 minutes of mining. Also we can switch to next custom pool in this case.
The next problem is not loading any of the previous custom pools and settings to the program fields when starting GGS. However they all are present in GatelessGateSharp.sqlite. This makes using of the GGS a headache. I use this custom pool settings:
pool.bsod.pw
1995
Ga59VHEiMTYPcnLm2mqmGfwSqUX294RB9q.470x2
c=SPK,d=128
Some piece of log for unresponsive thread case:
2018-01-01 13:37:55.0997 [4] Device #0 submitted a share.
2018-01-01 13:37:55.1477 [5] Share #38 accepted.
2018-01-01 13:37:56.3228 [6] Device #1: 686,77 Kh/s (NeoScrypt)
2018-01-01 13:37:56.7968 [4] Device #0: 708,77 Kh/s (NeoScrypt)
2018-01-01 13:38:06.3284 [6] Device #1: 682,01 Kh/s (NeoScrypt)
2018-01-01 13:38:06.3494 [5] Received new job: 3a
2018-01-01 13:38:13.8398 [5] Received new job: 3b
2018-01-01 13:38:14.8138 [6] Device #1 submitted a share.
2018-01-01 13:38:14.8648 [5] Share #39 accepted.
2018-01-01 13:38:16.3309 [6] Device #1: 690,27 Kh/s (NeoScrypt)
2018-01-01 13:38:26.0525 [6] Device #1 submitted a share.
2018-01-01 13:38:26.1015 [5] Share #40 accepted.
2018-01-01 13:38:26.3455 [6] Device #1: 323,31 Kh/s (NeoScrypt)
2018-01-01 13:38:26.9955 [5] Received new job: 3c
2018-01-01 13:38:36.3501 [6] Device #1: 682,54 Kh/s (NeoScrypt)
2018-01-01 13:38:46.3516 [6] Device #1: 689,51 Kh/s (NeoScrypt)
2018-01-01 13:38:56.3622 [6] Device #1: 681,50 Kh/s (NeoScrypt)
2018-01-01 13:38:59.5754 [1] Miner thread is unresponsive. Restarting...
2018-01-01 13:38:59.5754 [8] Miner thread for Device #0 started.
2018-01-01 13:38:59.5794 [8] Loaded Kernels\neoscrypt.cl for Device #0.
2018-01-01 13:39:06.3738 [6] Device #1: 685,24 Kh/s (NeoScrypt)
2018-01-01 13:39:08.8339 [8] Built NeoScrypt program for Device #0.
2018-01-01 13:39:08.8339 [8] Build options: -O5 -legacy -IKernels -DWORKSIZE=256
2018-01-01 13:39:16.3804 [6] Device #1: 684,43 Kh/s (NeoScrypt)
2018-01-01 13:39:19.9356 [5] Received new job: 3d
2018-01-01 13:39:26.3869 [6] Device #1: 660,76 Kh/s (NeoScrypt)
2018-01-01 13:39:27.5290 [5] Received new job: 3e
2018-01-01 13:39:34.9964 [5] Received new job: 3f
2018-01-01 13:39:36.3895 [6] Device #1: 683,76 Kh/s (NeoScrypt)
2018-01-01 13:39:45.6870 [6] Device #1 submitted a share.
2018-01-01 13:39:45.7370 [5] Share #41 accepted.
2018-01-01 13:39:46.3921 [6] Device #1: 685,95 Kh/s (NeoScrypt)
2018-01-01 13:39:56.3926 [6] Device #1: 687,36 Kh/s (NeoScrypt)
2018-01-01 13:39:58.7938 [6] Device #1 submitted a share.
2018-01-01 13:39:58.8428 [5] Share #42 accepted.
2018-01-01 13:40:03.4561 [6] Device #1 submitted a share.
2018-01-01 13:40:03.5051 [5] Share #43 accepted.
2018-01-01 13:40:06.4012 [6] Device #1: 685,59 Kh/s (NeoScrypt)
2018-01-01 13:40:07.9043 [6] Device #1 submitted a share.
2018-01-01 13:40:07.9563 [5] Share #44 accepted.
2018-01-01 13:40:07.9653 [6] Device #1 submitted a share.
2018-01-01 13:40:08.0153 [5] Share #45 accepted.
2018-01-01 13:40:10.0084 [1] Miner thread is unresponsive. Restarting...
2018-01-01 13:40:10.0084 [9] Miner thread for Device #0 started.
2018-01-01 13:40:10.0124 [9] Loaded Kernels\neoscrypt.cl for Device #0.
2018-01-01 13:40:13.8166 [6] Device #1 submitted a share.
2018-01-01 13:40:13.8656 [5] Share #46 accepted.