Search content
Sort by
Showing 19 of 19 results by softclickbr
Re: Gateless Gate Sharp 1.2.16: zawawa's open-source dual ETH/XMR/PASC/LBC/FTC miner
Hi guys!
People that uses overclock feature (we have started to use 2 days ago)... We found a same problem in 2 RIGs:
When using overclock setted equal to all GPUs, one of them, starts using lower memory, like 0.6g instead of 1.2g.
As result, the hash/s is lower than the another GPUs.
Sometimes, closing and reopening resolves the problem, sometimes no.
Disabling the GPU with the problem, another GPU starts with the same problem.
So, we tried to disable just the OC of the problematic GPU and setted the OC by Wattman.
Works fine, the problematic GPU works fast, but one of the GPUs with OC by GGS starts to work with lower memory and hashrate.
We guess be the rawintensity and threads are not be setting for the first (one of them) gpu with OC, using some default setting that uses just 0.6g.
At this time, to use all GPUs in the max hashrate we need to disable OC by GGS in all GPUs.
Should be just a little thing to resolve about the setting application from DB OC Data.
People that uses overclock feature (we have started to use 2 days ago)... We found a same problem in 2 RIGs:
When using overclock setted equal to all GPUs, one of them, starts using lower memory, like 0.6g instead of 1.2g.
As result, the hash/s is lower than the another GPUs.
Sometimes, closing and reopening resolves the problem, sometimes no.
Disabling the GPU with the problem, another GPU starts with the same problem.
So, we tried to disable just the OC of the problematic GPU and setted the OC by Wattman.
Works fine, the problematic GPU works fast, but one of the GPUs with OC by GGS starts to work with lower memory and hashrate.
We guess be the rawintensity and threads are not be setting for the first (one of them) gpu with OC, using some default setting that uses just 0.6g.
At this time, to use all GPUs in the max hashrate we need to disable OC by GGS in all GPUs.
Should be just a little thing to resolve about the setting application from DB OC Data.
Re: Gateless Gate Sharp 1.2.16: zawawa's open-source dual ETH/XMR/PASC/LBC/FTC miner
2 bugs about DB:
1-
I was having the overclock of the GPU 0 all times did incorrect by GGS (with a old value), I thought be another program doing this, but not finding anything, I tried to reset all settings with the reset buttons, and setted all data again... Well, so the overclock starts to use correct config to all cards.
I guess have some GUI option, like the OC setting for another algorithm, that writes in the same DB field, causing the error, and I can setted another algorithm by mistake sometime, but when corrected, the OC setting still valid to Neoscrypt.
2-
All times, when de GGS goes to save the config data, I need to wait about 10 seconds with the program freezed to save. Saving in the roaming data folder or with save as option in documents folder. This problem occours in our 4 rigs in test with GGS, I thought be a same problem than many users here.
Best regards.
1-
I was having the overclock of the GPU 0 all times did incorrect by GGS (with a old value), I thought be another program doing this, but not finding anything, I tried to reset all settings with the reset buttons, and setted all data again... Well, so the overclock starts to use correct config to all cards.
I guess have some GUI option, like the OC setting for another algorithm, that writes in the same DB field, causing the error, and I can setted another algorithm by mistake sometime, but when corrected, the OC setting still valid to Neoscrypt.
2-
All times, when de GGS goes to save the config data, I need to wait about 10 seconds with the program freezed to save. Saving in the roaming data folder or with save as option in documents folder. This problem occours in our 4 rigs in test with GGS, I thought be a same problem than many users here.
Best regards.
Re: Gateless Gate Sharp 1.2.15: zawawa's open-source dual ETH/XMR/PASC/LBC/FTC miner
Gateless Gate Sharp 1.2.16 alpha
https://github.com/zawawawa/GatelessGateSharp/releases/tag/v1.2.16-alpha
* Fixed a critical bug in logging.
Sorry, guys! This should fix the problem.
https://github.com/zawawawa/GatelessGateSharp/releases/tag/v1.2.16-alpha
* Fixed a critical bug in logging.
Sorry, guys! This should fix the problem.
miner restarted 2 times in 1 hour, 1.2.3 worked for days without 1 restart. i roll back.
i really dont want to hurt your feelings but i need to say this. Everytime you get to a good and stable version like 1.22, 1.23 you fuck it up in the next version with some stuff or changes nobody needs!
example
first versions after addng graphs where very instable
example
" Added the "Boost Performance" automatic overclocking/undervolting feature for RX 470/480/570/580, R9 Nano, and HD 7990."
why wasting working time with something like this? Real Miners know to config their cards, every card needs its own config to run stable, even if its from the same brand with same memory. this feature will only cause problems because people will try it and it will not work maybe proper on every system. on the other hand it will just support lazy fucktards who are to dumb and/or to lazy to do a simple biosflash, do some little research about settings for gpus.
example
planed on the fly memory mods
same as above for what? if somebody is to dumb or to lazy to do a biosflash, fuck him he deserves stock speed. you aint gonna earn more by supporting lazy fucktards.
if you want to increase your earnings why dont you focus on whats really important? Real Miners just wants a stable and fast miner. stability is even more important than speed, because nobody wants to check his rigs every hour.
- add new algos like equihash/skunkhash/tribus to gain new users
- optimise current algos and make them faster and stable(people goes there where the most profit is...faster/stable miner then other miners = gives people a reason to switch and pay the fee)
why should somebody for example switch from sgminer or xmrstak(0%fee version) if its running more stable and have same speed?
just my few cents
I have fear to touch in a BOOST button. Exactly as you said, we have dozens of GPUs in sequence serial number (bought from manufacturer in the original package of 8 GPU each), and never one GPU is equal another. Is impossible to a boost button do a good work, just can try different working size, threads, etc.
The difference between GPUs is so important, that we like to have a field to rename the "NAME" of the GPUs in the GPU Column, to be possible to identify with our stickers pasted on each GPU.
I understand to be necessary change the DB structure to add fields, and I know that uses the old db of the installation on each new version, but I think is possible to do the implementation altering the db tables and preserving backward compatibilty.
If db will be changed, need to put a option to insert new custom pools and name them, just 4 is little, and need to read the login to try to remember what coin is.
Re: Gateless Gate Sharp 1.2.16: zawawa's open-source dual ETH/XMR/PASC/LBC/FTC miner
I have lowered from 2186 to 2132 on my 580 8gb micron rigs almost while moving to 832 the voltage.
Non perfect but it works stable with version 1.2.3 if I remember correctly
On the test rigs with 3 elpida 570 pulse 4gb I simply reinstalled my original bios WITHOUT the new straps and set the same value I had before (subtrack 24) and I'm getting 1970 mh/s with neoscrypt, so not bad.
I need to restart the rig once a day as Cpu utilization tend to increase.
Neoscrypt only for both rigs.
You wrote that also criptonight can be a good choice for AMD, but I haven't find a good coin to mine that generate the same profit as ETH.
If you can, please hint me on that.Tx
Non perfect but it works stable with version 1.2.3 if I remember correctly
On the test rigs with 3 elpida 570 pulse 4gb I simply reinstalled my original bios WITHOUT the new straps and set the same value I had before (subtrack 24) and I'm getting 1970 mh/s with neoscrypt, so not bad.
I need to restart the rig once a day as Cpu utilization tend to increase.
Neoscrypt only for both rigs.
You wrote that also criptonight can be a good choice for AMD, but I haven't find a good coin to mine that generate the same profit as ETH.
If you can, please hint me on that.Tx
3 RX 570 at 1970kh/s is bad yes. You should get 2400 with GGS 3 RX 570
https://i.imgur.com/eP9WYao.png
Re: Gateless Gate Sharp 1.2.13: zawawa's open-source dual ETH/XMR/PASC/LBC/FTC miner
I confirm, if internet connection brokes GGS interface became very unresponsible... Even if connection is restored.
I'm sure of this, I'm a professional miner. The problems are not related to my RIG configs. I use all of them without problems, inclusive without problems in GGS, but when the Internet is out, when comes back, unresponsible.
I understand the developer tired of amateur people asking about things not related to the software, but don't disconnect their internet to test, prefering guilty the user , after all stability problems reported here ?
Some guys don't knows that where have a large areas to solar power generation and eolic generation are remote areas where Internet connection are not so good as the mayor cities. But, even with 2 redundant connections, swtiching when problems occours, the GGS starts to have problems.
Re: Gateless Gate Sharp 1.2.13: zawawa's open-source dual ETH/XMR/PASC/LBC/FTC miner
I confirm, if internet connection brokes GGS interface became very unresponsible... Even if connection is restored.
I'm sure of this, I'm a professional miner. The problems are not related to my RIG configs. I use all of them without problems, inclusive without problems in GGS, but when the Internet is out, when comes back, unresponsible.
I understand the developer tired of amateur people asking about things not related to the software, but don't disconnect their internet to test, prefering guilty the user , after all stability problems reported here ?
My connection changes the IP to another connection when have some problem. And the problems with the GGS starts to occours. Is not a load balancing problem dude.
Re: Gateless Gate Sharp 1.2.13: zawawa's open-source dual ETH/XMR/PASC/LBC/FTC miner
I confirm, if internet connection brokes GGS interface became very unresponsible... Even if connection is restored.
I'm sure of this, I'm a professional miner. The problems are not related to my RIG configs. I use all of them without problems, inclusive without problems in GGS, but when the Internet is out, when comes back, unresponsible.
I understand the developer tired of amateur people asking about things not related to the software, but don't disconnect their internet to test, prefering guilty the user , after all stability problems reported here ?
Re: Gateless Gate Sharp 1.2.13: zawawa's open-source dual ETH/XMR/PASC/LBC/FTC miner
To reproduce high CPU usage and instability issues, use any pool, just disconnect internet and reconnect after some seconds or minutes, when come back, comes with many issues. Never auto recover. Only relaunching to resolve the problem.
Well, GGS is auto-recovering with my setups without a problem. Which version of GGS are you using?
Well, I saw GUI interface problems with different resolution, you say "it's perfect".
I said, instability after internet connection problems, you say, "it's auto recovering"...
I'm not earning nothing to say for you about problems that not exists. I say, because exists.
Do your tests, disconnect, reconnect your network cable, 1 min, 10 min, reconnect.
Many users are talking about instability, I just gave a way to follow against the problem. Probably the same old problem with dev fee, due the disconnection and reconnection to the pool.
I will, allways, report problems just with the LAST VERSION, I'm not stupid to report problems those can be resolved in a new released version.
Re: Gateless Gate Sharp 1.2.13: zawawa's open-source dual ETH/XMR/PASC/LBC/FTC miner
To reproduce high CPU usage and instability issues, use any pool, just disconnect internet and reconnect after some seconds or minutes, when come back, comes with many issues. Never auto recover. Only relaunching to resolve the problem.
Re: Gateless Gate Sharp 1.2.13: zawawa's open-source dual ETH/XMR/PASC/LBC/FTC miner
The screen scaling problems still under 4k. Try different dpi sizes to reproduce!
https://www.imageupload.co.uk/images/2018/01/30/4kProblems.png
https://www.imageupload.co.uk/images/2018/01/30/4kProblems.png
Scaling works perfectly fine with Windows 10 Creators Update. Which operating system are you using?
Windows 10 last version. Using terminal mstsc in different versions. Scaling not works perfectly fine. If you want, I can get more details about resolution and DPI fonts
Re: Gateless Gate Sharp 1.2.13: zawawa's open-source dual ETH/XMR/PASC/LBC/FTC miner
The screen scaling problems still under 4k. Try different dpi sizes to reproduce!
https://www.imageupload.co.uk/images/2018/01/30/4kProblems.png
https://www.imageupload.co.uk/images/2018/01/30/4kProblems.png
Re: Gateless Gate Sharp 1.2.12: zawawa's open-source dual ETH/XMR/PASC/LBC/FTC miner
I resolved the problem with dev fee in 1.2.7A version setting fixed diff in bsod.pw.
1.2.12 resolved the anoying windows dialog alerts during dev fee period.
Now, I saw the dev fee mode switching, nice and smooth (but at de minute 15, I believe have more 85 min without dev fee)
Congratulations.
Best regards,
Vinicius
1.2.12 resolved the anoying windows dialog alerts during dev fee period.
Now, I saw the dev fee mode switching, nice and smooth (but at de minute 15, I believe have more 85 min without dev fee)
Congratulations.
Best regards,
Vinicius
Re: Gateless Gate Sharp 1.2.10: zawawa's open-source dual ETH/XMR/PASC/LBC/FTC miner
Gateless Gate Sharp 1.2.11 alpha
https://github.com/zawawawa/GatelessGateSharp/releases/tag/v1.2.11-alpha
* Addressed compatibility issues with yiimp-based pools.
* Made stratum-related codes more robust.
* Adjusted default settings for RX 470/480/570/580.
* Switched from intensity to row intensity for NeoScrypt.
* Enhanced the automatic upgrade feature.
This should fix all the reported pool-related problems.
Please do let me know if they still persist.
that's awesome neoscrypt best use raw intensityhttps://github.com/zawawawa/GatelessGateSharp/releases/tag/v1.2.11-alpha
* Addressed compatibility issues with yiimp-based pools.
* Made stratum-related codes more robust.
* Adjusted default settings for RX 470/480/570/580.
* Switched from intensity to row intensity for NeoScrypt.
* Enhanced the automatic upgrade feature.
This should fix all the reported pool-related problems.
Please do let me know if they still persist.
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)
...
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...
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.
Re: Gateless Gate Sharp 1.2.7: zawawa's open-source dual ETH/XMR/PASC/LBC/FTC miner
Any idea to get 30mh/s or more with a Rx580 in Lyra2Rev with Gateless Gate Sharp as is possible with another miner?
Worksize, intensity...
Or wait for a new version?
Worksize, intensity...
Or wait for a new version?
I didn't do anything to optimize Lyra2REv2 yet.
I know for a fact that pre-calc with CPU is possible for the first rounds, though.
I will get to it when I have time.
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).
Re: Gateless Gate Sharp 1.2.10: zawawa's open-source dual ETH/XMR/PASC/LBC/FTC miner
Gateless Gate Sharp 1.2.11 alpha
https://github.com/zawawawa/GatelessGateSharp/releases/tag/v1.2.11-alpha
* Addressed compatibility issues with yiimp-based pools.
* Made stratum-related codes more robust.
* Adjusted default settings for RX 470/480/570/580.
* Switched from intensity to row intensity for NeoScrypt.
* Enhanced the automatic upgrade feature.
This should fix all the reported pool-related problems.
Please do let me know if they still persist.
that's awesome neoscrypt best use raw intensityhttps://github.com/zawawawa/GatelessGateSharp/releases/tag/v1.2.11-alpha
* Addressed compatibility issues with yiimp-based pools.
* Made stratum-related codes more robust.
* Adjusted default settings for RX 470/480/570/580.
* Switched from intensity to row intensity for NeoScrypt.
* Enhanced the automatic upgrade feature.
This should fix all the reported pool-related problems.
Please do let me know if they still persist.
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
Re: Gateless Gate Sharp 1.2.7: zawawa's open-source dual ETH/XMR/PASC/LBC/FTC miner
Any idea to get 30mh/s or more with a Rx580 in Lyra2Rev with Gateless Gate Sharp as is possible with another miner?
Worksize, intensity...
Or wait for a new version?
Worksize, intensity...
Or wait for a new version?
Re: Gateless Gate Sharp 1.2.7: zawawa's open-source dual ETH/XMR/PASC/LBC/FTC miner
Downgraded to 1.2.9 and number of shares in Gui is not correct. See the status bar against Gui:
https://i.imgur.com/DwhWMkE.png
https://i.imgur.com/DwhWMkE.png
Re: Gateless Gate Sharp 1.2.9: zawawa's open-source dual ETH/XMR/PASC/LBC/FTC miner
version 1.2.10
Now the hashrate seems be stable after switching, but....no shares...So, after switching back to my pool there are no shares to it, while cards are mining well.
Now the hashrate seems be stable after switching, but....no shares...So, after switching back to my pool there are no shares to it, while cards are mining well.
It must be your pool, then. Which coin are you mining at which pool?
Confirm this problem on some pools, zpool and mine, in both tested Neoscrypt, after some time workers disappear at pools, but app still works and load GPU 100%
Exactly same problem here with pool.Bsod.pw. Downgrading...
1.2.10:
...
2018-01-28 22:41:14.2152 [16] Device #2 submitted Share #13 to pool.bsod.pw as RQL48SX2P3m1ySmsyFFexNNKFiJiQ9e4e9.RXNITROMQ0.
2018-01-28 22:41:14.5339 [15] Share #12 accepted.
2018-01-28 22:41:14.7889 [16] Device #2: 884,41 Kh/s (NeoScrypt)
2018-01-28 22:41:14.8848 [15] Share #13 accepted.
2018-01-28 22:41:24.7909 [16] Device #2: 900,33 Kh/s (NeoScrypt)
2018-01-28 22:41:34.7973 [16] Device #2: 899,49 Kh/s (NeoScrypt)
2018-01-28 22:41:44.7997 [16] Device #2: 897,40 Kh/s (NeoScrypt)
2018-01-28 22:41:54.8027 [16] Device #2: 898,04 Kh/s (NeoScrypt)
2018-01-28 22:42:01.8441 [15] Received new job: 7e
2018-01-28 22:42:04.8299 [16] Device #2: 902,64 Kh/s (NeoScrypt)
2018-01-28 22:42:09.9310 [10] Running garbage collection...
2018-01-28 22:42:09.9310 [10] Memory used before collection: 46MB
2018-01-28 22:42:09.9565 [10] Memory used before collection: 12MB
2018-01-28 22:42:14.8569 [16] Device #2: 902,66 Kh/s (NeoScrypt)
2018-01-28 22:42:23.4647 [1] Switching to the DEVFEE mode...
2018-01-28 22:42:24.8840 [16] Device #2: 900,22 Kh/s (NeoScrypt)
2018-01-28 22:42:26.2380 [16] Restarting miner thread...
2018-01-28 22:42:27.4606 [1] Stopping miners...
2018-01-28 22:42:27.5470 [16] Exception in miner thread: Stratum server failed to send a new job. em GatelessGateSharp.OpenCLNeoScryptMiner.MinerThread()
2018-01-28 22:42:27.5746 [1] Stopped miners.
2018-01-28 22:42:38.5971 [1] Stopping miners...
2018-01-28 22:42:38.6335 [1] Stopped miners.
2018-01-28 22:42:38.6480 [1] Launching NeoScrypt miners for DEVFEE...
2018-01-28 22:42:39.9507 [20] Miner thread for Device #2 started.
2018-01-28 22:42:39.9593 [20] Loaded Kernels\neoscrypt.cl for Device #2.
2018-01-28 22:42:41.4645 [1] Stopping miners...
2018-01-28 22:42:44.8357 [20] Built neoscrypt program for Device #2.
2018-01-28 22:42:44.8357 [20] Build options: -O5 -legacy -IKernels -DWORKSIZE=256
2018-01-28 22:42:44.8793 [1] Stopped miners.
2018-01-28 22:42:54.9307 [1] Stopping miners...
2018-01-28 22:42:54.9845 [1] Stopped miners.
2018-01-28 22:42:54.9965 [1] Launching NeoScrypt miners for DEVFEE...
2018-01-28 22:42:56.4951 [20] Miner thread for Device #2 started.
2018-01-28 22:42:56.5026 [20] Loaded Kernels\neoscrypt.cl for Device #2.
2018-01-28 22:42:57.4622 [1] Stopping miners...
2018-01-28 22:43:01.4841 [20] Built neoscrypt program for Device #2.
2018-01-28 22:43:01.4841 [20] Build options: -O5 -legacy -IKernels -DWORKSIZE=256
2018-01-28 22:43:01.5132 [1] Stopped miners.
2018-01-28 22:43:11.5371 [1] Stopping miners...
2018-01-28 22:43:11.5715 [1] Stopped miners.
2018-01-28 22:43:11.5890 [1] Launching NeoScrypt miners for DEVFEE...
2018-01-28 22:43:12.9924 [20] Miner thread for Device #2 started.
2018-01-28 22:43:12.9989 [20] Loaded Kernels\neoscrypt.cl for Device #2.
2018-01-28 22:43:13.4632 [1] Stopping miners...
2018-01-28 22:43:17.9529 [20] Built neoscrypt program for Device #2.
2018-01-28 22:43:17.9529 [20] Build options: -O5 -legacy -IKernels -DWORKSIZE=256
2018-01-28 22:43:17.9956 [1] Stopped miners.
2018-01-28 22:43:28.0267 [1] Stopping miners...
2018-01-28 22:43:28.0796 [1] Stopped miners.
2018-01-28 22:43:28.0915 [1] Launching NeoScrypt miners for DEVFEE...
2018-01-28 22:43:29.4734 [20] Miner thread for Device #2 started.
2018-01-28 22:43:29.4810 [20] Loaded Kernels\neoscrypt.cl for Device #2.
2018-01-28 22:43:30.2591 [1] Switching back from the DEVFEE mode...
2018-01-28 22:43:34.7274 [20] Built neoscrypt program for Device #2.
2018-01-28 22:43:34.7274 [20] Build options: -O5 -legacy -IKernels -DWORKSIZE=256
2018-01-28 22:43:44.7576 [20] Device #2: 900,42 Kh/s (NeoScrypt)
2018-01-28 22:43:54.7726 [20] Device #2: 899,57 Kh/s (NeoScrypt)
2018-01-28 22:44:04.7843 [20] Device #2: 893,86 Kh/s (NeoScrypt)
2018-01-28 22:44:14.7944 [20] Device #2: 901,79 Kh/s (NeoScrypt)
2018-01-28 22:44:24.8033 [20] Device #2: 899,74 Kh/s (NeoScrypt)
2018-01-28 22:44:34.8135 [20] Device #2: 897,45 Kh/s (NeoScrypt)
2018-01-28 22:44:44.8322 [20] Device #2: 898,16 Kh/s (NeoScrypt)
2018-01-28 22:44:54.8449 [20] Device #2: 891,87 Kh/s (NeoScrypt)
2018-01-28 22:45:04.8669 [20] Device #2: 898,01 Kh/s (NeoScrypt)
2018-01-28 22:45:14.8865 [20] Device #2: 899,04 Kh/s (NeoScrypt)
2018-01-28 22:45:24.9138 [20] Device #2: 896,59 Kh/s (NeoScrypt)
2018-01-28 22:45:34.9307 [20] Device #2: 901,32 Kh/s (NeoScrypt)
2018-01-28 22:45:44.9454 [20] Device #2: 897,82 Kh/s (NeoScrypt)
2018-01-28 22:45:54.9626 [20] Device #2: 902,09 Kh/s (NeoScrypt)
2018-01-28 22:46:04.9801 [20] Device #2: 898,35 Kh/s (NeoScrypt)
2018-01-28 22:46:14.9901 [20] Device #2: 901,94 Kh/s (NeoScrypt)
2018-01-28 22:46:25.0078 [20] Device #2: 900,17 Kh/s (NeoScrypt)
Never comes to send any share.
Another problem in 1.2.9 aplha, at 4k resolution, not able to see Local Work size dua GUI design error .
http://tinypic.com/r/w003zo/9