I reuploaded another test version (same file name) which is still closer to the 0.32a, for those who still get errors.
https://github.com/jceminer/cn_gpu_miner/raw/master/jce_cn_gpu_miner.prototype.032t.zip
@Lermite: why worksize 2?
Topic: [XMR] JCE Miner Cryptonight/forks, now with GPU! - page 71. (Read 90841 times)
Thanks all for the time you take to test.
I reuploaded another test version (same file name) which is still closer to the 0.32a, for those who still get errors.
https://github.com/jceminer/cn_gpu_miner/raw/master/jce_cn_gpu_miner.prototype.032t.zip
@Lermite: why worksize 2?
I reuploaded another test version (same file name) which is still closer to the 0.32a, for those who still get errors.
https://github.com/jceminer/cn_gpu_miner/raw/master/jce_cn_gpu_miner.prototype.032t.zip
@Lermite: why worksize 2?
RX 570 8GB and 4GB
Drivers 18.3.4
Win 1607 x64
The 0.32t runs definitely fine on CN Heavy (XHV).
I thought the rejected shares issue might affect only CN Saber but mining Bittube runs fine too, even if the hashrate of my 4BG is still crappy:
0: 570 8GB: 839 h/s
1: 570 4GB: 588 h/s
CN Heavy:
0: 570 8GB: 846 h/s
1: 570 4GB: 826 h/s
Drivers 18.3.4
Win 1607 x64
The 0.32t runs definitely fine on CN Heavy (XHV).
I thought the rejected shares issue might affect only CN Saber but mining Bittube runs fine too, even if the hashrate of my 4BG is still crappy:
Code:
"gpu_threads_conf" :
[
{ "mode": "GPU", "worksize": 4, "alpha": 64, "beta": 8, "gamma": 4, "delta": 4, "epsilon": 4, "zeta": 4, "index": 0, "multi_hash": 496 },
{ "mode": "GPU", "worksize": 4, "alpha": 64, "beta": 8, "gamma": 4, "delta": 4, "epsilon": 4, "zeta": 4, "index": 0, "multi_hash": 496 },
{ "mode": "GPU", "worksize": 2, "alpha": 64, "beta": 8, "gamma": 4, "delta": 4, "epsilon": 4, "zeta": 4, "index": 1, "multi_hash": 480 },
{ "mode": "GPU", "worksize": 2, "alpha": 64, "beta": 8, "gamma": 4, "delta": 4, "epsilon": 4, "zeta": 4, "index": 1, "multi_hash": 480 },
]
0: 570 8GB: 839 h/s
1: 570 4GB: 588 h/s
CN Heavy:
Code:
"gpu_threads_conf" :
[
{ "mode": "GPU", "worksize": 4, "alpha": 64, "beta": 8, "gamma": 4, "delta": 4, "epsilon": 4, "zeta": 4, "index": 0, "multi_hash": 512 },
{ "mode": "GPU", "worksize": 4, "alpha": 64, "beta": 8, "gamma": 4, "delta": 4, "epsilon": 4, "zeta": 4, "index": 0, "multi_hash": 512 },
{ "mode": "GPU", "worksize": 4, "alpha": 64, "beta": 8, "gamma": 4, "delta": 4, "epsilon": 4, "zeta": 4, "index": 1, "multi_hash": 480 },
{ "mode": "GPU", "worksize": 4, "alpha": 64, "beta": 8, "gamma": 4, "delta": 4, "epsilon": 4, "zeta": 4, "index": 1, "multi_hash": 480 },
]
0: 570 8GB: 846 h/s
1: 570 4GB: 826 h/s
I uploaded the 0.32t (t for test) which is a mix of the 0.32a and c code.
i tested it for hours on all my rigs and got zero bad shares. but i've no Ellesmere.
please tell me if it:
works or not on vega
works or not on other non-Elsmere (rx550, 560...)
works or not on Heavy or v7 or both
if it fails, what card and driver you have
if it fails, retry with a low multihash (to know if i overflow the vram)
that bug i cannot reproduce makes me crazy. it was luck the 32a worked...
i tested it for hours on all my rigs and got zero bad shares. but i've no Ellesmere.
please tell me if it:
works or not on vega
works or not on other non-Elsmere (rx550, 560...)
works or not on Heavy or v7 or both
if it fails, what card and driver you have
if it fails, retry with a low multihash (to know if i overflow the vram)
that bug i cannot reproduce makes me crazy. it was luck the 32a worked...
Win 10-64 build 1803.
18.6.1 drivers
Mining BITTUBE
3X RX570 4GB with bios mod, config file:
Code:
"gpu_threads_conf" :
[
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 0, "multi_hash": 304}, (display GPU core and mem freq: 1230/2100)
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 0, "multi_hash": 304},
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 1, "multi_hash": 464}, (1200/2020)
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 1, "multi_hash": 464},
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 2, "multi_hash": 464}, (1200/2020)
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 2, "multi_hash": 464},
],
So far (20mn testing) all's ok no stale no rejected, but raw hashrate is not faster than 0.32a and actual hashrate is low.
0.32t on Rx 570 4gb, bittube, using 18.5.1, winver 1709, lots of rejected shares, and my miner got banned by miner.rocks.
Backed to 0.32a and all is good.
Backed to 0.32a and all is good.
Continue testing:
The above testing was using multi hash 944.
Tried to decrease multi hash to 864, still got rejected shares some times.
Tried again to decrease multi hash to 832, still got rejected shares as well.
Backed to 0.32a with multi hash 944 and all is good, no reject shares.
Quote
17:19:21 | Pool sg.bittube.miner.rocks:5555
17:19:21 | Currency Cryptonote
17:19:21 | Current pool Difficulty 160003
17:19:21 | Valid Shares found 3
17:19:21 | Total hashes 480009
17:19:21 | Miner uptime 0:02:40
17:19:21 | Effective net hashrate 3000.06 h/s
17:19:23 | Hashrate GPU Thread 0: 714.35 h/s - Total GPU 0: 714.35 h/s
17:19:23 | Hashrate GPU Thread 1: 719.15 h/s - Total GPU 1: 719.15 h/s
17:19:23 | Hashrate GPU Thread 2: 714.35 h/s - Total GPU 2: 714.35 h/s
17:19:23 | Hashrate GPU Thread 3: 719.15 h/s - Total GPU 3: 719.15 h/s
17:19:23 | Hashrate GPU Thread 4: 720.69 h/s - Total GPU 4: 720.69 h/s
17:19:23 | Hashrate GPU Thread 5: 719.15 h/s - Total GPU 5: 719.15 h/s
17:19:23 | Total: 4306.81 h/s - Max: 4308.57 h/s
17:19:30 | GPU 5 Thread 5 Lane 819 finds a Share, value 160003
17:19:30 | Rejected by the pool.
17:19:30 | Message from the pool: Low difficulty share
17:20:46 | GPU 2 Thread 2 Lane 794 finds a Share, value 160003
17:20:46 | Rejected by the pool.
17:20:46 | Message from the pool: Low difficulty share
17:21:03 | Pool sends a new Job.
17:21:12 | Pool sends a new Job.
17:21:30 | GPU 0 Thread 0 Lane 507 finds a Share, value 160003
17:21:31 | Accepted by the pool.
17:22:08 | GPU 4 Thread 4 Lane 351 finds a Share, value 160003
17:22:08 | Accepted by the pool.
17:19:21 | Currency Cryptonote
17:19:21 | Current pool Difficulty 160003
17:19:21 | Valid Shares found 3
17:19:21 | Total hashes 480009
17:19:21 | Miner uptime 0:02:40
17:19:21 | Effective net hashrate 3000.06 h/s
17:19:23 | Hashrate GPU Thread 0: 714.35 h/s - Total GPU 0: 714.35 h/s
17:19:23 | Hashrate GPU Thread 1: 719.15 h/s - Total GPU 1: 719.15 h/s
17:19:23 | Hashrate GPU Thread 2: 714.35 h/s - Total GPU 2: 714.35 h/s
17:19:23 | Hashrate GPU Thread 3: 719.15 h/s - Total GPU 3: 719.15 h/s
17:19:23 | Hashrate GPU Thread 4: 720.69 h/s - Total GPU 4: 720.69 h/s
17:19:23 | Hashrate GPU Thread 5: 719.15 h/s - Total GPU 5: 719.15 h/s
17:19:23 | Total: 4306.81 h/s - Max: 4308.57 h/s
17:19:30 | GPU 5 Thread 5 Lane 819 finds a Share, value 160003
17:19:30 | Rejected by the pool.
17:19:30 | Message from the pool: Low difficulty share
17:20:46 | GPU 2 Thread 2 Lane 794 finds a Share, value 160003
17:20:46 | Rejected by the pool.
17:20:46 | Message from the pool: Low difficulty share
17:21:03 | Pool sends a new Job.
17:21:12 | Pool sends a new Job.
17:21:30 | GPU 0 Thread 0 Lane 507 finds a Share, value 160003
17:21:31 | Accepted by the pool.
17:22:08 | GPU 4 Thread 4 Lane 351 finds a Share, value 160003
17:22:08 | Accepted by the pool.
use --doublecheck to make bad shares detected before being sent to Pool, to avoid ban.
So far it would be a Ellesmere only bug? Any feedback about cn-v7 and on small rx ?
So far it would be a Ellesmere only bug? Any feedback about cn-v7 and on small rx ?
0.32t on Rx 570 4gb, bittube, using 18.5.1, winver 1709, lots of rejected shares, and my miner got banned by miner.rocks.
Backed to 0.32a and all is good.
Backed to 0.32a and all is good.
032t - vega 56 x7, windows 10 1803, adrenalin 18.6.1 or 18.7.1 (dont remember) working ok for me
CN-V7 14280 h/s
CN-V7 14280 h/s
lebuawu2: thanks for feedback
can you lower significantly your multi-hash param? it may be related to the config rather than the gpu.
any result on cn-v7 or vega ?
can you lower significantly your multi-hash param? it may be related to the config rather than the gpu.
any result on cn-v7 or vega ?
I still have to test it for a longer time but after 27 minutes, the only flaw I got is one stale share that was accepted by the pool:
Nothing to worry about.
Code:
11:01:38 | GPU 0 Thread 12 Lane 502 finds a Share, value 79000
11:01:38 | Stale Share that may be refused by the pool.
11:01:39 | Accepted by the pool.
11:01:38 | Stale Share that may be refused by the pool.
11:01:39 | Accepted by the pool.
Nothing to worry about.
I didn't test the 0.32t for a long time yet but it looks fine so far on ellesmere (RX 570 4GB and RX 570 8GB) and CN Heavy (HXV) with driver 18.3.4
you sure you don't get any rejected shares? I tried haven also RX 580 8GB got rejected shares after sometimes. driver 18.3.4
tested 032t driver 18.3.4 on bittube still got rejected shares.
may I know which driver you use?
https://imgur.com/a/VlWtrfJ
may I know which driver you use?
https://imgur.com/a/VlWtrfJ
thanks bro 
i take time to answer previous questions:
hiveOS: this is a Linux, right ? jce gpu is windows x64 only (win8.1 or 10)
the cpu miner exists on linux 32 and 64
squirrel: i avoid jumping in other dev topic, it could be seen as an indirect ad. but you may ask him to integrate JCE and he can come here to get help. jce has a JSON api and the kill bug is fixed now (killing the master process now kills the shadow attrib)
i take time to answer previous questions:
hiveOS: this is a Linux, right ? jce gpu is windows x64 only (win8.1 or 10)
the cpu miner exists on linux 32 and 64
squirrel: i avoid jumping in other dev topic, it could be seen as an indirect ad. but you may ask him to integrate JCE and he can come here to get help. jce has a JSON api and the kill bug is fixed now (killing the master process now kills the shadow attrib)
I didn't test the 0.32t for a long time yet but it looks fine so far on ellesmere (RX 570 4GB and RX 570 8GB) and CN Heavy (HXV) with driver 18.3.4
I uploaded the 0.32t (t for test) which is a mix of the 0.32a and c code.
i tested it for hours on all my rigs and got zero bad shares. but i've no Ellesmere.
please tell me if it:
works or not on vega
works or not on other non-Elsmere (rx550, 560...)
works or not on Heavy or v7 or both
if it fails, what card and driver you have
if it fails, retry with a low multihash (to know if i overflow the vram)
that bug i cannot reproduce makes me crazy. it was luck the 32a worked...
i tested it for hours on all my rigs and got zero bad shares. but i've no Ellesmere.
please tell me if it:
works or not on vega
works or not on other non-Elsmere (rx550, 560...)
works or not on Heavy or v7 or both
if it fails, what card and driver you have
if it fails, retry with a low multihash (to know if i overflow the vram)
that bug i cannot reproduce makes me crazy. it was luck the 32a worked...
JCE
Love your miner especially on rx550. It is a beast!!!!!
I am getting 530hs on cn7 and 1065hs on litev7.
Have you spoken with gpuhoarder about integrating your miner with the squirrel miner? I would love to keep using this miner when my accorns get here
can you share the rx 550 bios info, your overclocking info... Love your miner especially on rx550. It is a beast!!!!!
I am getting 530hs on cn7 and 1065hs on litev7.
Have you spoken with gpuhoarder about integrating your miner with the squirrel miner? I would love to keep using this miner when my accorns get here
JCE
Love your miner especially on rx550. It is a beast!!!!!
I am getting 530hs on cn7 and 1065hs on litev7.
Have you spoken with gpuhoarder about integrating your miner with the squirrel miner? I would love to keep using this miner when my accorns get here
Love your miner especially on rx550. It is a beast!!!!!
I am getting 530hs on cn7 and 1065hs on litev7.
Have you spoken with gpuhoarder about integrating your miner with the squirrel miner? I would love to keep using this miner when my accorns get here
Ok so i've a big problem on the Ellesmere code, thanks for your fast replay. On my 560 it runs fine. I'll compare step by step with the 0.32a code.
Thanks all for the quick replies
Thanks all for the quick replies
Hello, someone use this miner with hiveOS ? any way to make it work with this OS ?
Ok so i've a big problem on the Ellesmere code, thanks for your fast replay. On my 560 it runs fine. I'll compare step by step with the 0.32a code.
Thanks all for the quick replies
Thanks all for the quick replies
The 0.32a ran fine to me but the 0.32c just gave this while mining MSR (CN Fast):
Code:
21:13:09 | Pool sends a new Job.
21:13:56 | GPU 1 Thread 11 Lane 594 finds a Share, value 200007
21:13:57 | Accepted by the pool.
21:14:10 | GPU 1 Thread 11 Lane 449 finds a Share, value 200007
21:14:10 | Accepted by the pool.
21:15:20 | GPU 0 Thread 8 Lane 1038 finds a Share, value 200007
21:15:20 | Rejected by the pool.
21:15:20 | Message from the pool: Wrong algo, use monero7 miner
21:13:56 | GPU 1 Thread 11 Lane 594 finds a Share, value 200007
21:13:57 | Accepted by the pool.
21:14:10 | GPU 1 Thread 11 Lane 449 finds a Share, value 200007
21:14:10 | Accepted by the pool.
21:15:20 | GPU 0 Thread 8 Lane 1038 finds a Share, value 200007
21:15:20 | Rejected by the pool.
21:15:20 | Message from the pool: Wrong algo, use monero7 miner
Code:
21:35:42 | GPU 0 Thread 9 Lane 62 finds a Share, value 200007
21:35:42 | Stale Share that may be refused by the pool.
21:35:42 | Rejected by the pool.
21:35:42 | Message from the pool: Wrong algo, use monero7 miner
21:36:33 | GPU 1 Thread 11 Lane 74 finds a Share, value 200007
21:36:33 | Accepted by the pool.
21:35:42 | Stale Share that may be refused by the pool.
21:35:42 | Rejected by the pool.
21:35:42 | Message from the pool: Wrong algo, use monero7 miner
21:36:33 | GPU 1 Thread 11 Lane 74 finds a Share, value 200007
21:36:33 | Accepted by the pool.
0.32c online
Exact same as 0.32b but bad shares fixed (at least it runs fine on my Polaris)
Exact same as 0.32b but bad shares fixed (at least it runs fine on my Polaris)
still lots of invalid shares on rx480... although faster than other miners
Code:
+------------------------------------------+
| JC Expert Cryptonote CPU+GPU Miner 0.32c |
+------------------------------------------+
For Windows 64-bits
Detecting OpenCL-capable GPUs...
Found GPU 0, with:
Vendor: AMD
Processor: Ellesmere
Device: 01:00
Compute-Units: 36
Cache Memory: 16 KB
Local Memory: 32 KB
Global Memory: 8192 MB
Addressing: 64-bits
HTTP Local Server on port 4028
Preparing 2 Mining Threads...
+-- Thread 0 config -----------------------+
| Run on GPU: 0 |
| Multi-hash: 864 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 16 |
| Factor Gamma 4 |
| Factor Delta 4 |
| Factor Epsilon 4 |
| Factor Zeta 4 |
+------------------------------------------+
+-- Thread 1 config -----------------------+
| Run on GPU: 0 |
| Multi-hash: 864 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 16 |
| Factor Gamma 4 |
| Factor Delta 4 |
| Factor Epsilon 4 |
| Factor Zeta 4 |
+------------------------------------------+
Cryptonight Variation: Cryptonight-Heavy
Starting GPU Mining thread 0, on GPU 0
Created OpenCL Context for GPU 0 at 000001c7563d5cb0
Created OpenCL Thread 0 Command-Queue for GPU 0 at 000001c754fe7290
Allocating big 3456MB scratchpad for OpenCL Thread 0...
Scratchpad Allocation success for OpenCL Thread 0
Compiling kernels of OpenCL Thread 0...
Kernels of OpenCL Thread 0 compiled.
Starting GPU Mining thread 1, on GPU 0
Created OpenCL Thread 1 Command-Queue for GPU 0 at 000001c756390850
Allocating big 3456MB scratchpad for OpenCL Thread 1...
Scratchpad Allocation success for OpenCL Thread 1
Compiling kernels of OpenCL Thread 1...
Kernels of OpenCL Thread 1 compiled.
GPU Devfee is 0.9%
22:22:36 | Connecting to mining pool mine.RYO.fairpool.cloud:5555 ...
22:22:36 | Sumokoin (SUMO) Mining session starts!
During mining time, press:
h display hashrate for each mining thread.
r display full report.
p pause all.
u pause CPUs.
0-F pause GPU 0-15.
q quit.
22:22:36 | GPU Compute allocation starts at 80% and reaches 100% after 5min
22:22:36 | Let the miner warm-up if you're tuning for performance.
22:22:37 | Connected to pool. Now logging in...
22:22:37 | Successfuly logged as Sumoo5G6gz52snJ5pJEaT2g9xZ8s8WmchHXm8rbYGJznhG9jyGiAZHGfQ12zKU1fvCQgrLqxosPu3Cd6Dq9wLKc9P1EQXqDrc6g+FRACTAL_AMD
22:22:37 | Pool changes Difficulty to 2000.
22:22:38 | GPU 0 Thread 0 Lane 595 has found an invalid Share.
22:22:40 | GPU 0 Thread 0 Lane 692 has found an invalid Share.
22:22:40 | GPU 0 Thread 1 Lane 325 finds a Share, value 2000
22:22:40 | Accepted by the pool.
22:22:46 | GPU 0 Thread 1 Lane 764 has found an invalid Share.
22:22:48 | GPU 0 Thread 1 Lane 106 finds a Share, value 2000
22:22:48 | GPU 0 Thread 1 Lane 531 has found an invalid Share.
22:22:48 | Accepted by the pool.
22:22:48 | Hashrate GPU Thread 0: 637.35 h/s
22:22:48 | Hashrate GPU Thread 1: 586.54 h/s - Total GPU 0: 1223.89 h/s
22:22:48 | Total: 1223.89 h/s - Max: 1224.09 h/s
22:22:48 | GPU 0 Thread 0 Lane 688 has found an invalid Share.
22:22:51 | GPU 0 Thread 0 Lane 145 finds a Share, value 2000
22:22:51 | Accepted by the pool.
22:22:52 | GPU 0 Thread 1 Lane 612 has found an invalid Share.
22:22:53 | GPU 0 Thread 1 Lane 257 finds a Share, value 2000
22:22:53 | GPU 0 Thread 1 Lane 783 has found an invalid Share.
22:22:53 | Accepted by the pool.
22:22:54 | GPU 0 Thread 0 Lane 298 finds a Share, value 2000
22:22:54 | GPU 0 Thread 0 Lane 786 has found an invalid Share.
22:22:54 | Accepted by the pool.
22:22:55 | GPU 0 Thread 1 Lane 219 finds a Share, value 2000
22:22:55 | Accepted by the pool.
22:22:55 | GPU 0 Thread 0 Lane 392 has found an invalid Share.
22:22:57 | GPU 0 Thread 0 Lane 747 has found an invalid Share.
22:23:00 | GPU 0 Thread 0 Lane 180 finds a Share, value 2000
22:23:00 | Accepted by the pool.
22:23:01 | GPU 0 Thread 1 Lane 763 has found an invalid Share.
22:23:04 | GPU 0 Thread 1 Lane 127 finds a Share, value 2000
22:23:04 | Accepted by the pool.
22:23:06 | GPU 0 Thread 0 Lane 14 finds a Share, value 2000
22:23:06 | Accepted by the pool.
22:23:07 | GPU 0 Thread 1 Lane 83 finds a Share, value 2000
22:23:07 | Accepted by the pool.
22:23:08 | GPU 0 Thread 0 Lane 494 has found an invalid Share.
22:23:08 | Hashrate GPU Thread 0: 566.77 h/s
22:23:08 | Hashrate GPU Thread 1: 569.36 h/s - Total GPU 0: 1136.12 h/s
22:23:08 | Total: 1136.12 h/s - Max: 1224.09 h/s
22:23:09 | GPU 0 Thread 1 Lane 152 finds a Share, value 2000
22:23:09 | Accepted by the pool.
| JC Expert Cryptonote CPU+GPU Miner 0.32c |
+------------------------------------------+
For Windows 64-bits
Detecting OpenCL-capable GPUs...
Found GPU 0, with:
Vendor: AMD
Processor: Ellesmere
Device: 01:00
Compute-Units: 36
Cache Memory: 16 KB
Local Memory: 32 KB
Global Memory: 8192 MB
Addressing: 64-bits
HTTP Local Server on port 4028
Preparing 2 Mining Threads...
+-- Thread 0 config -----------------------+
| Run on GPU: 0 |
| Multi-hash: 864 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 16 |
| Factor Gamma 4 |
| Factor Delta 4 |
| Factor Epsilon 4 |
| Factor Zeta 4 |
+------------------------------------------+
+-- Thread 1 config -----------------------+
| Run on GPU: 0 |
| Multi-hash: 864 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 16 |
| Factor Gamma 4 |
| Factor Delta 4 |
| Factor Epsilon 4 |
| Factor Zeta 4 |
+------------------------------------------+
Cryptonight Variation: Cryptonight-Heavy
Starting GPU Mining thread 0, on GPU 0
Created OpenCL Context for GPU 0 at 000001c7563d5cb0
Created OpenCL Thread 0 Command-Queue for GPU 0 at 000001c754fe7290
Allocating big 3456MB scratchpad for OpenCL Thread 0...
Scratchpad Allocation success for OpenCL Thread 0
Compiling kernels of OpenCL Thread 0...
Kernels of OpenCL Thread 0 compiled.
Starting GPU Mining thread 1, on GPU 0
Created OpenCL Thread 1 Command-Queue for GPU 0 at 000001c756390850
Allocating big 3456MB scratchpad for OpenCL Thread 1...
Scratchpad Allocation success for OpenCL Thread 1
Compiling kernels of OpenCL Thread 1...
Kernels of OpenCL Thread 1 compiled.
GPU Devfee is 0.9%
22:22:36 | Connecting to mining pool mine.RYO.fairpool.cloud:5555 ...
22:22:36 | Sumokoin (SUMO) Mining session starts!
During mining time, press:
h display hashrate for each mining thread.
r display full report.
p pause all.
u pause CPUs.
0-F pause GPU 0-15.
q quit.
22:22:36 | GPU Compute allocation starts at 80% and reaches 100% after 5min
22:22:36 | Let the miner warm-up if you're tuning for performance.
22:22:37 | Connected to pool. Now logging in...
22:22:37 | Successfuly logged as Sumoo5G6gz52snJ5pJEaT2g9xZ8s8WmchHXm8rbYGJznhG9jyGiAZHGfQ12zKU1fvCQgrLqxosPu3Cd6Dq9wLKc9P1EQXqDrc6g+FRACTAL_AMD
22:22:37 | Pool changes Difficulty to 2000.
22:22:38 | GPU 0 Thread 0 Lane 595 has found an invalid Share.
22:22:40 | GPU 0 Thread 0 Lane 692 has found an invalid Share.
22:22:40 | GPU 0 Thread 1 Lane 325 finds a Share, value 2000
22:22:40 | Accepted by the pool.
22:22:46 | GPU 0 Thread 1 Lane 764 has found an invalid Share.
22:22:48 | GPU 0 Thread 1 Lane 106 finds a Share, value 2000
22:22:48 | GPU 0 Thread 1 Lane 531 has found an invalid Share.
22:22:48 | Accepted by the pool.
22:22:48 | Hashrate GPU Thread 0: 637.35 h/s
22:22:48 | Hashrate GPU Thread 1: 586.54 h/s - Total GPU 0: 1223.89 h/s
22:22:48 | Total: 1223.89 h/s - Max: 1224.09 h/s
22:22:48 | GPU 0 Thread 0 Lane 688 has found an invalid Share.
22:22:51 | GPU 0 Thread 0 Lane 145 finds a Share, value 2000
22:22:51 | Accepted by the pool.
22:22:52 | GPU 0 Thread 1 Lane 612 has found an invalid Share.
22:22:53 | GPU 0 Thread 1 Lane 257 finds a Share, value 2000
22:22:53 | GPU 0 Thread 1 Lane 783 has found an invalid Share.
22:22:53 | Accepted by the pool.
22:22:54 | GPU 0 Thread 0 Lane 298 finds a Share, value 2000
22:22:54 | GPU 0 Thread 0 Lane 786 has found an invalid Share.
22:22:54 | Accepted by the pool.
22:22:55 | GPU 0 Thread 1 Lane 219 finds a Share, value 2000
22:22:55 | Accepted by the pool.
22:22:55 | GPU 0 Thread 0 Lane 392 has found an invalid Share.
22:22:57 | GPU 0 Thread 0 Lane 747 has found an invalid Share.
22:23:00 | GPU 0 Thread 0 Lane 180 finds a Share, value 2000
22:23:00 | Accepted by the pool.
22:23:01 | GPU 0 Thread 1 Lane 763 has found an invalid Share.
22:23:04 | GPU 0 Thread 1 Lane 127 finds a Share, value 2000
22:23:04 | Accepted by the pool.
22:23:06 | GPU 0 Thread 0 Lane 14 finds a Share, value 2000
22:23:06 | Accepted by the pool.
22:23:07 | GPU 0 Thread 1 Lane 83 finds a Share, value 2000
22:23:07 | Accepted by the pool.
22:23:08 | GPU 0 Thread 0 Lane 494 has found an invalid Share.
22:23:08 | Hashrate GPU Thread 0: 566.77 h/s
22:23:08 | Hashrate GPU Thread 1: 569.36 h/s - Total GPU 0: 1136.12 h/s
22:23:08 | Total: 1136.12 h/s - Max: 1224.09 h/s
22:23:09 | GPU 0 Thread 1 Lane 152 finds a Share, value 2000
22:23:09 | Accepted by the pool.
Jump to: