Topic: Gateless Gate Sharp 1.3.8: 30Mh/s (Ethash) on RX 480! - page 67. (Read 214410 times)

(1) That message is pretty harmless. You can ignore it.
(2) I'm uploading v1.2.12 right now. Please try it first.
(3) I changed colors a little bit with v.1.2.12. Please let me know if that would work for you.
      I could let the user change the color scheme, but that is not a priority at this point.

I installed version 1.2.11 and the problem with the drop-out of the pool seems to be missing. thanks for the prompt decision.
now I have a few questions from others.
--------------------------------------------------------------------------------------------------------------------------------
which means the string that sometimes appears:
[9] Unknown stratum method: {"id": null, "method": "client.show_message", "params": ["welcome on ALTMINER.NET - happy mining!"]}

the second question - began to appear "Invalid share". for 4 hours approximately 2-3%. Previously, they were not.
---------------------------------------------------------------------------------------------------------------------------------

Yes, and the last question. Can I make custom panel colors? Some color combinations of numbers are indistinguishable against the background by default.

I have copied the log.
Well, the part that I thought to be interesting... but i don't think I found much

A couple of thing from someone that last thing I have programmed was a text only adventure....

Please create a log / session or a log/day in order to make life easier to retrieve it

The one minute hashrate report just add garbage, its interesting for testing, but real life a 10 minutes is fine.

I noticed you have created one devfee wallet / algo, good choice it will easy the switch

2018-01-29 09:13:09.0839 [18] Device #0 submitted Share #11 to neoscrypt.mine.zpool.ca as a DEVFEE.
2018-01-29 09:13:09.2150 [22] Share #11 accepted.
2018-01-29 09:13:11.3677 [19] Device #1: 625,83 Kh/s (NeoScrypt)
2018-01-29 09:13:11.6665 [20] Device #2: 626,09 Kh/s (NeoScrypt)
2018-01-29 09:13:11.7878 [18] Device #0: 660,36 Kh/s (NeoScrypt)
2018-01-29 09:13:13.9726 [1] Switching back from the DEVFEE mode...
2018-01-29 09:13:21.3716 [19] Device #1: 655,35 Kh/s (NeoScrypt)
2018-01-29 09:13:21.6674 [20] Device #2: 659,25 Kh/s (NeoScrypt)
2018-01-29 09:13:21.7897 [18] Device #0: 321,10 Kh/s (NeoScrypt)
2018-01-29 09:13:25.4407 [17] Received new job: 2394
2018-01-29 09:13:25.7455 [17] Difficulty set to 32.
2018-01-29 09:13:28.0854 [20] Device #2 submitted Share #4 to arcpool.com as RQMQ5vdT7UkrU2gvEUwbmrzXz2hK3zwEWD.
2018-01-29 09:13:28.1185 [17] Share #4 rejected: Invalid share
2018-01-29 09:13:29.0703 [20] Device #2 submitted Share #5 to arcpool.com as RQMQ5vdT7UkrU2gvEUwbmrzXz2hK3zwEWD.
2018-01-29 09:13:29.0983 [17] Share #5 rejected: Invalid share
2018-01-29 09:13:30.3863 [20] Device #2 submitted Share #6 to arcpool.com as RQMQ5vdT7UkrU2gvEUwbmrzXz2hK3zwEWD.
2018-01-29 09:13:30.4153 [17] Share #6 rejected: Invalid share
2018-01-29 09:13:31.1435 [20] Device #2 submitted Share #7 to arcpool.com as RQMQ5vdT7UkrU2gvEUwbmrzXz2hK3zwEWD.
2018-01-29 09:13:31.1775 [17] Share #7 rejected: Invalid share
2018-01-29 09:13:31.4142 [19] Device #1: 184,79 Kh/s (NeoScrypt)
2018-01-29 09:13:31.6699 [20] Device #2: 458,93 Kh/s (NeoScrypt)
2018-01-29 09:13:31.8032 [18] Device #0: 614,26 Kh/s (NeoScrypt)
2018-01-29 09:13:33.4704 [19] Device #1 submitted Share #8 to arcpool.com as RQMQ5vdT7UkrU2gvEUwbmrzXz2hK3zwEWD.
2018-01-29 09:13:33.5086 [17] Share #8 rejected: Invalid share
2018-01-29 09:13:33.9166 [18] Device #0 submitted Share #9 to arcpool.com as RQMQ5vdT7UkrU2gvEUwbmrzXz2hK3zwEWD.
2018-01-29 09:13:33.9477 [17] Share #9 rejected: Invalid share
2018-01-29 09:13:35.5904 [20] Device #2 submitted Share #10 to arcpool.com as RQMQ5vdT7UkrU2gvEUwbmrzXz2hK3zwEWD.
2018-01-29 09:13:35.6204 [17] Share #10 rejected: Invalid share
2018-01-29 09:13:36.8449 [19] Device #1 submitted Share #11 to arcpool.com as RQMQ5vdT7UkrU2gvEUwbmrzXz2hK3zwEWD.
2018-01-29 09:13:36.8730 [17] Share #11 rejected: Invalid share
2018-01-29 09:13:37.8761 [18] Device #0 submitted Share #12 to arcpool.com as RQMQ5vdT7UkrU2gvEUwbmrzXz2hK3zwEWD.
2018-01-29 09:13:37.9132 [17] Share #12 rejected: Invalid share
2018-01-29 09:13:38.0295 [19] Device #1 submitted Share #13 to arcpool.com as RQMQ5vdT7UkrU2gvEUwbmrzXz2hK3zwEWD.
2018-01-29 09:13:38.0686 [17] Share #13 rejected: Invalid share
2018-01-29 09:13:41.3337 [19] Device #1 submitted Share #14 to arcpool.com as RQMQ5vdT7UkrU2gvEUwbmrzXz2hK3zwEWD.
2018-01-29 09:13:41.3759 [17] Share #14 rejected: Invalid share
2018-01-29 09:13:41.4240 [19] Device #1: 149,29 Kh/s (NeoScrypt)
2018-01-29 09:13:41.6787 [20] Device #2: 627,00 Kh/s (NeoScrypt)
2018-01-29 09:13:41.8200 [18] Device #0: 346,12 Kh/s (NeoScrypt)
2018-01-29 09:13:42.4096 [18] Device #0 submitted Share #15 to arcpool.com as RQMQ5vdT7UkrU2gvEUwbmrzXz2hK3zwEWD.
2018-01-29 09:13:42.4417 [17] Share #15 rejected: Invalid share
2018-01-29 09:13:44.9479 [19] Device #1 submitted Share #16 to arcpool.com as RQMQ5vdT7UkrU2gvEUwbmrzXz2hK3zwEWD.
2018-01-29 09:13:44.9759 [17] Share #16 rejected: Invalid share
2018-01-29 09:13:45.4883 [20] Device #2 submitted Share #17 to arcpool.com as RQMQ5vdT7UkrU2gvEUwbmrzXz2hK3zwEWD.
2018-01-29 09:13:45.5184 [17] Share #17 rejected: Invalid share
2018-01-29 09:13:45.9356 [18] Device #0 submitted Share #18 to arcpool.com as RQMQ5vdT7UkrU2gvEUwbmrzXz2hK3zwEWD.
2018-01-29 09:13:45.9656 [17] Share #18 rejected: Invalid share

2018-01-29 10:13:31.7653 [18] Device #0 submitted Share #318 to arcpool.com as RQMQ5vdT7UkrU2gvEUwbmrzXz2hK3zwEWD.
2018-01-29 10:13:31.8004 [17] Share #318 accepted.
2018-01-29 10:13:32.2305 [17] Difficulty set to 32.
2018-01-29 10:13:33.1290 [19] Device #1 submitted Share #4 to arcpool.com as RQMQ5vdT7UkrU2gvEUwbmrzXz2hK3zwEWD.
2018-01-29 10:13:33.1601 [17] Share #4 rejected: Invalid share
2018-01-29 10:13:34.1265 [20] Device #2 submitted Share #5 to arcpool.com as RQMQ5vdT7UkrU2gvEUwbmrzXz2hK3zwEWD.
2018-01-29 10:13:34.1576 [17] Share #5 rejected: Invalid share
2018-01-29 10:13:34.1696 [19] Device #1: 262,34 Kh/s (NeoScrypt)
2018-01-29 10:13:34.7121 [20] Device #2: 664,07 Kh/s (NeoScrypt)
2018-01-29 10:13:34.9026 [18] Device #0: 652,64 Kh/s (NeoScrypt)
2018-01-29 10:13:35.9261 [20] Device #2 submitted Share #6 to arcpool.com as RQMQ5vdT7UkrU2gvEUwbmrzXz2hK3zwEWD.
2018-01-29 10:13:35.9582 [17] Share #6 rejected: Invalid share
2018-01-29 10:13:36.7945 [19] Device #1 submitted Share #7 to arcpool.com as RQMQ5vdT7UkrU2gvEUwbmrzXz2hK3zwEWD.
2018-01-29 10:13:36.8256 [17] Share #7 rejected: Invalid share
2018-01-29 10:13:37.6593 [18] Device #0 submitted Share #8 to arcpool.com as RQMQ5vdT7UkrU2gvEUwbmrzXz2hK3zwEWD.
2018-01-29 10:13:37.6904 [17] Share #8 accepted.

2018-01-29 10:32:11.1316 [17] Share #194 accepted.
2018-01-29 10:32:11.5287 [6] ADL.ADL_Overdrive5_PowerControl_Set() failed with Device #2.
2018-01-29 10:32:11.5498 [6] ADL.ADL_Overdrive5_PowerControl_Set() failed with Device #2.

I do run tests for all algos. Custom pools are a whole different issue, though...
I think it is safe to say stratum-related codes are the worst part of miner development by a large margin.

zawawa - you are pretty fast releasing new versions of your miner that's great. But I wonder what kind of testing you do between build?  Do you test only specific algos?

Reported from neoscrypt no increase in hashrate in R9, Fury and RX series card but new version looks better no problem
Thanks...

I think I identified the root cause. I will push a fix soon.

Zawawa, the new version is better but not good either.
The hashrate went down in 4 hour from 1970 to 790 for the small 3 rx570 rig.

I have to deal with a motherboard problem with another rig, and then I will estract something from the log and send to you

I confirm. Also such a problem is Gateless Gate Sharp 1.2.10 (NeoScrypt). in the miner the extraction is normal, but the miner disappears on the pool. I so understand it happens after reconnecting to the pool (lycheebit.com) .. on other pools, too, such a problem, so I think it's not a problem in them.
today I'll try version 1.2.11 - I will write about the result.

I tested 1.2.10, 1.2.9, and had similar problems after dev fee.

So, I'm using 1.2.7, that comes back to work after dev dee, but with all GPUs instable, with 200h/s and 800 h/s, jumping.

This occours in a RIG with 6 GPU and a Celeron processor with 4GB RAM.

But in AMD Ryzen 7 1700 with 4 GPUs comes back normal.

I tried to stop, release memory and start and problem continues.

I tried to relaunch and start, and problem continues. The jumps does total hashrate/s drops 10%+

The Act. column never stays 100%, stays 100 70 0 2 50 32 90...

Stopping, closing the GGS and starting again (double clicking in the .exe) the problem disappears.

Is it possible to save custom pools and settings?

The problem was quite simple. The pool was just too slow to send a new job, and GGS did not wait for long enough.
Let me see...

Thank you, I'm happy to know that you didn't tried anything yet. The mkxminer is doing +30mh/s against 6, 7mh/s of sgminer in the same GPU (rx580).

The new version is working fine with zpool.ca, though. What is up with these pools... I will try pool.bsod.pw now.

No luck man !!! I installed 1.2.11 alpha and not comes back after dev mode:

2018-01-29 05:07:26.8410 [15] Share #17 accepted.
2018-01-29 05:07:28.0624 [16] Device #2 submitted Share #18 to pool.bsod.pw as RQL48SX2P3m1ySmsyFFexNNKFiJiQ9e4e9.RXNITROMQ0.Maq0.
2018-01-29 05:07:28.4408 [15] Share #18 accepted.
2018-01-29 05:07:30.5536 [16] Device #2: 933,28 Kh/s (NeoScrypt)
2018-01-29 05:07:40.5611 [16] Device #2: 931,50 Kh/s (NeoScrypt)
2018-01-29 05:07:59.3665 [19] Difficulty set to 256.
2018-01-29 05:08:01.6120 [1] Switching to the DEVFEE mode...
2018-01-29 05:08:02.1390 [19] Received new job: 12fc
2018-01-29 05:08:11.0358 [19] Received new job: 1306
2018-01-29 05:08:57.7259 [19] Received new job: 1303
2018-01-29 05:09:06.6388 [1] Switching back from the DEVFEE mode...
2018-01-29 05:09:38.5400 [15] Received new job: 85
2018-01-29 05:09:41.1849 [15] Difficulty set to 1024.
2018-01-29 05:10:41.7154 [15] Received new job: 86
2018-01-29 05:11:45.6607 [15] Received new job: 87
2018-01-29 05:12:03.1656 [11] Running garbage collection...
2018-01-29 05:12:03.1656 [11] Memory used before collection: 25MB
2018-01-29 05:12:03.1916 [11] Memory used before collection: 11MB
2018-01-29 05:12:14.8002 [15] Received new job: 88
2018-01-29 05:12:27.3602 [15] Received new job: 89

that's awesome neoscrypt best use raw intensity

I would love to hear your results. That color means the acceptance ratio is at least above 95%. I just changed that color to black.

I was waiting for the neoscrypt patch....
Installed, the double graph is nice.

still chasing about the 24000 mb  even if I set minimum 24000 max 32000

I will tell you in 1h.17 minutes how it goes, as the previous version was unstable after that time mining.

If  I will not be in bed..

I forgot: when there is an incorrect shares, with the GPU listed at 3 or 4 position, the highlighted colour is almost the same as the background color, so I can't read

"Share #8" This "8" refers to a serial number for JSON RPC messages, so what you see on the graph is still correct.
I guess this numbering scheme is pretty confusing...