|
UnclWish
|
 |
October 14, 2018, 08:43:24 AM |
|
What about video memory stripes? Does video bios mods for cryptonight v7/heavy would be good for V8?
|
|
|
|
|
HardKano
Newbie
 Offline
Activity: 76
Merit: 0
|
|
October 14, 2018, 11:49:12 AM |
|
I'm doing it right now. I'll first provide a simple implementation based on the on from the official Monero team, then i'll optimize. It will also contain a little optim for Heavy/Tube (unrelated to v8, just i'll release it at the same time). If you wonder why it took so long just to make the CPU version, so that's because 1. v8 is completely different from v7, i couldn't reuse anything but the implode/explode parts 2. I support 32-bits, and the 32-bits version was hell to make, because i run out of registers everywhere 3. Every x1 to x6 multihash has it own assenbly 4. the uncached version adds two more (for 64 and 32) 5. each time, there are specialization for some CPUs like core2, nehalem or ryzen so that was about one hundred asm to update, bench and test  God damn... i hope they won't make a v9 in 6 month ... |
|
|
|
|
mrwhitti
Newbie
Offline
Activity: 4
Merit: 0
|
|
October 14, 2018, 01:57:48 PM |
|
Hi , i get the following error on all the pools i try , even the killallasics test pool
+------------------------------------------+
+-- Thread 3 config -----------------------+
| Run on CPU: 3 |
| Use cache: yes |
| Multi-hash: no |
| Assembly module: generic_aes |
+------------------------------------------+
+-- Thread 4 config -----------------------+
| Run on CPU: 4 |
| Use cache: yes |
| Multi-hash: no |
| Assembly module: generic_aes |
+------------------------------------------+
+-- Thread 5 config -----------------------+
| Run on CPU: 5 |
| Use cache: yes |
| Multi-hash: no |
| Assembly module: generic_aes |
+------------------------------------------+
+-- Thread 6 config -----------------------+
| Run on CPU: 6 |
| Use cache: yes |
| Multi-hash: no |
| Assembly module: generic_aes |
+------------------------------------------+
+-- Thread 7 config -----------------------+
| Run on CPU: 7 |
| Use cache: yes |
| Multi-hash: no |
| Assembly module: generic_aes |
+------------------------------------------+
+-- Thread 8 config -----------------------+
| Run on CPU: 8 |
| Use cache: yes |
| Multi-hash: no |
| Assembly module: generic_aes |
+------------------------------------------+
+-- Thread 9 config -----------------------+
| Run on CPU: 10 |
| Use cache: yes |
| Multi-hash: no |
| Assembly module: generic_aes |
+------------------------------------------+
+-- Thread 10 config ----------------------+
| Run on CPU: 12 |
| Use cache: yes |
| Multi-hash: no |
| Assembly module: generic_aes |
+------------------------------------------+
+-- Thread 11 config ----------------------+
| Run on CPU: 14 |
| Use cache: yes |
| Multi-hash: no |
| Assembly module: generic_aes |
+------------------------------------------+
+-- Thread 12 config ----------------------+
| Run on CPU: 16 |
| Use cache: yes |
| Multi-hash: no |
| Assembly module: generic_aes |
+------------------------------------------+
+-- Thread 13 config ----------------------+
| Run on CPU: 17 |
| Use cache: yes |
| Multi-hash: no |
| Assembly module: generic_aes |
+------------------------------------------+
+-- Thread 14 config ----------------------+
| Run on CPU: 18 |
| Use cache: yes |
| Multi-hash: no |
| Assembly module: generic_aes |
+------------------------------------------+
+-- Thread 15 config ----------------------+
| Run on CPU: 19 |
| Use cache: yes |
| Multi-hash: no |
| Assembly module: generic_aes |
+------------------------------------------+
+-- Thread 16 config ----------------------+
| Run on CPU: 20 |
| Use cache: yes |
| Multi-hash: no |
| Assembly module: generic_aes |
+------------------------------------------+
+-- Thread 17 config ----------------------+
| Run on CPU: 21 |
| Use cache: yes |
| Multi-hash: no |
| Assembly module: generic_aes |
+------------------------------------------+
+-- Thread 18 config ----------------------+
| Run on CPU: 22 |
| Use cache: yes |
| Multi-hash: no |
| Assembly module: generic_aes |
+------------------------------------------+
+-- Thread 19 config ----------------------+
| Run on CPU: 23 |
| Use cache: yes |
| Multi-hash: no |
| Assembly module: generic_aes |
+------------------------------------------+
+-- Thread 20 config ----------------------+
| Run on CPU: 24 |
| Use cache: yes |
| Multi-hash: no |
| Assembly module: generic_aes |
+------------------------------------------+
+-- Thread 21 config ----------------------+
| Run on CPU: 26 |
| Use cache: yes |
| Multi-hash: no |
| Assembly module: generic_aes |
+------------------------------------------+
+-- Thread 22 config ----------------------+
| Run on CPU: 28 |
| Use cache: yes |
| Multi-hash: no |
| Assembly module: generic_aes |
+------------------------------------------+
+-- Thread 23 config ----------------------+
| Run on CPU: 30 |
| Use cache: yes |
| Multi-hash: no |
| Assembly module: generic_aes |
+------------------------------------------+
Cryptonight Variation: Cryptonight V8 fork of Oct-2018
Low intensity.
Starting CPU Mining thread 0, affinity: CPU 0
Thread 0 successfully bound to CPU 0
Allocated shared Large Page at: 0000000005200000
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 0 of NUMA node 0 at: 0
000000005400000
Starting CPU Mining thread 1, affinity: CPU 1
Thread 1 successfully bound to CPU 1
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 1 of NUMA node 0 at: 0
000000005600000
Starting CPU Mining thread 2, affinity: CPU 2
Thread 2 successfully bound to CPU 2
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 2 of NUMA node 0 at: 0
000000005c00000
Starting CPU Mining thread 3, affinity: CPU 3
Thread 3 successfully bound to CPU 3
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 3 of NUMA node 0 at: 0
000000005e00000
Starting CPU Mining thread 4, affinity: CPU 4
Thread 4 successfully bound to CPU 4
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 4 of NUMA node 0 at: 0
000000006000000
Starting CPU Mining thread 5, affinity: CPU 5
Thread 5 successfully bound to CPU 5
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 5 of NUMA node 0 at: 0
000000006200000
Starting CPU Mining thread 6, affinity: CPU 6
Thread 6 successfully bound to CPU 6
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 6 of NUMA node 0 at: 0
000000006600000
Starting CPU Mining thread 7, affinity: CPU 7
Thread 7 successfully bound to CPU 7
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 7 of NUMA node 0 at: 0
000000006800000
Starting CPU Mining thread 8, affinity: CPU 8
Thread 8 successfully bound to CPU 8
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 8 of NUMA node 0 at: 0
000000006c00000
Starting CPU Mining thread 9, affinity: CPU 10
Thread 9 successfully bound to CPU 10
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 10 of NUMA node 0 at:
0000000007000000
Starting CPU Mining thread 10, affinity: CPU 12
Thread 10 successfully bound to CPU 12
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 12 of NUMA node 0 at:
0000000007400000
Starting CPU Mining thread 11, affinity: CPU 14
Thread 11 successfully bound to CPU 14
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 14 of NUMA node 0 at:
0000000007600000
Starting CPU Mining thread 12, affinity: CPU 16
Thread 12 successfully bound to CPU 16
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 16 of NUMA node 1 at:
0000000007800000
Starting CPU Mining thread 13, affinity: CPU 17
Thread 13 successfully bound to CPU 17
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 17 of NUMA node 1 at:
0000000007a00000
Starting CPU Mining thread 14, affinity: CPU 18
Thread 14 successfully bound to CPU 18
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 18 of NUMA node 1 at:
0000000007c00000
Starting CPU Mining thread 15, affinity: CPU 19
Thread 15 successfully bound to CPU 19
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 19 of NUMA node 1 at:
0000000007e00000
Starting CPU Mining thread 16, affinity: CPU 20
Thread 16 successfully bound to CPU 20
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 20 of NUMA node 1 at:
0000000008200000
Starting CPU Mining thread 17, affinity: CPU 21
Thread 17 successfully bound to CPU 21
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 21 of NUMA node 1 at:
0000000008600000
Starting CPU Mining thread 18, affinity: CPU 22
Thread 18 successfully bound to CPU 22
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 22 of NUMA node 1 at:
0000000008800000
Starting CPU Mining thread 19, affinity: CPU 23
Thread 19 successfully bound to CPU 23
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 23 of NUMA node 1 at:
0000000008a00000
Starting CPU Mining thread 20, affinity: CPU 24
Thread 20 successfully bound to CPU 24
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 24 of NUMA node 1 at:
0000000008c00000
Starting CPU Mining thread 21, affinity: CPU 26
Thread 21 successfully bound to CPU 26
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 26 of NUMA node 1 at:
0000000009000000
Starting CPU Mining thread 22, affinity: CPU 28
Thread 22 successfully bound to CPU 28
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 28 of NUMA node 1 at:
0000000009200000
Starting CPU Mining thread 23, affinity: CPU 30
Thread 23 successfully bound to CPU 30
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 30 of NUMA node 1 at:
0000000009600000
Connecting to mining pool xmrpool.eu:3333 ...
Devfee for CPU is 1.5%
14:54:29 | Monero (XMR/XMV) Mining session starts!
During mining time, press:
h display hashrate for each mining thread.
r display full report.
p pause all.
q quit.
14:54:29 | Will autoclose in 20 minutes.
14:54:29 | Connected to pool. Now logging in...
14:54:29 | Successfuly logged as 43iTLAWVGiv5T53hXS7S35ehZtvJ7zmP6gnyMqoCP66gPoq
RNiSY34TXhiaQEGiCaMe79YVzRicRA1wAnYsvTNTEJ5ojZPu
14:54:29 | Pool changes Difficulty to 10000.
14:54:30 | CPU Thread 13 finds a Share, value 10000
14:54:30 | Rejected by the pool in 47 ms.
14:54:30 | Message from the pool: Low difficulty share
14:54:30 | Your first share was rejected, you probably need to change the fork
14:54:30 | with parameter --variation N, try different values for N in [1-15]
14:54:30 | until you find the one that works.
14:54:37 | CPU Thread 8 finds a Share, value 10000
14:54:37 | Rejected by the pool in 47 ms.
14:54:37 | Message from the pool: Low difficulty share
14:54:39 | Pause All
|
|
|
|
|
JCE-Miner (OP)
Member
Offline
Activity: 350
Merit: 22
|
|
October 14, 2018, 02:12:19 PM
Last edit: October 14, 2018, 02:32:12 PM by JCE-Miner |
|
The very precise log you gave is normal: you're mining Monero with V8 algo and it hasn't forked yet. I'll however redo a test on the 0.33a just to be sure.
To force V7 until it forks, add parameter --variation 3
The autoconfig for GPU will remain the same, because it's a safe config, not an optimal one. In short, that's 2M per GPU thread for about 80% of your video memory, and all values alpha, beta... to default. It may make it more specialized for V8, but i'll look at that later.
edit:
I retested, and here's the status:
* On Monero, you have rejected shares because Monero hasn't forked yet. Normal.
* On killallasics, their dummy wallet 9.... is detected as Fonero by JCE (because it really looks like a Fonero wallet) and so it mines with CN-classic, and produce only bad shares. Normal.
Add --variation 3 to mine Monero V7 until it forks (JCE default to V8 in advance) and --variation 15 to test on killallasics.
To mine Wownero, all is already automatic.
|
|
|
|
|
JCE-Miner (OP)
Member
Offline
Activity: 350
Merit: 22
|
|
October 14, 2018, 02:45:30 PM |
|
What about video memory stripes? Does video bios mods for cryptonight v7/heavy would be good for V8?
Yes, good, better than ever. V7 did two reads and two writes to memory per round. V8 does six more of each. That make the memory still more critical. CPUs have no problem because they have prefetch, consistant memory and ultra-fast cache. GPU have almost nothing. As I said before, even if it's very theorical, i expect V8 to close the gap between big and small GPUs having the same memory controller, like HD7850 and 7870, or RX550 and RX560. I may be surprised if the compute cost of the new Divide and SquareRoot is really big. In such case, high-compute GPUs like Vega will be the winner, as with the old but powerfull GPUs like HD7900. To be benched. |
|
|
|
|
mrwhitti
Newbie
Offline
Activity: 4
Merit: 0
|
|
October 14, 2018, 03:04:39 PM |
|
The very precise log you gave is normal: you're mining Monero with V8 algo and it hasn't forked yet. I'll however redo a test on the 0.33a just to be sure.
To force V7 until it forks, add parameter --variation 3
The autoconfig for GPU will remain the same, because it's a safe config, not an optimal one. In short, that's 2M per GPU thread for about 80% of your video memory, and all values alpha, beta... to default. It may make it more specialized for V8, but i'll look at that later.
edit:
I retested, and here's the status:
* On Monero, you have rejected shares because Monero hasn't forked yet. Normal.
* On killallasics, their dummy wallet 9.... is detected as Fonero by JCE (because it really looks like a Fonero wallet) and so it mines with CN-classic, and produce only bad shares. Normal.
Add --variation 3 to mine Monero V7 until it forks (JCE default to V8 in advance) and --variation 15 to test on killallasics.
To mine Wownero, all is already automatic.
Ahh ok , i set variation to 3 & all working ok so, do we change it back to 0 after the fork ? |
|
|
|
|
lilu5151515151
Newbie
Offline
Activity: 3
Merit: 0
|
|
October 14, 2018, 06:00:09 PM |
|
I'm doing it right now. I'll first provide a simple implementation based on the on from the official Monero team, then i'll optimize. It will also contain a little optim for Heavy/Tube (unrelated to v8, just i'll release it at the same time). If you wonder why it took so long just to make the CPU version, so that's because 1. v8 is completely different from v7, i couldn't reuse anything but the implode/explode parts 2. I support 32-bits, and the 32-bits version was hell to make, because i run out of registers everywhere 3. Every x1 to x6 multihash has it own assenbly 4. the uncached version adds two more (for 64 and 32) 5. each time, there are specialization for some CPUs like core2, nehalem or ryzen so that was about one hundred asm to update, bench and test Hi, I've been trying to run jce_cn_gpu_miner.032q and jce_cn_gpu_miner.prototype.032n on this card. I'm using Windows 10 and 18.8.1 drivers. No overclock. Card Sapphire Radeon RX 560 4GB. Help me pls. +------------------------------------------+
| JC Expert Cryptonote CPU+GPU Miner 0.32n |
+------------------------------------------+
For Windows 64-bits
Analyzing Processors topology...
AMD Ryzen 5 1600 Six-Core Processor
Assembly codename: ryzen
SSE2 : Yes
SSE3 : Yes
SSE4 : Yes
AES : Yes
AVX : Yes
AVX2 : Yes
Found CPU 0, with:
L1 Cache: 32 KB, shared with CPU 1
L2 Cache: 512 KB, shared with CPU 1
L3 Cache: 8192 KB, shared with CPU 1, 2, 3, 4, 5
Found CPU 1, with:
L1 Cache: 32 KB, shared with CPU 0
L2 Cache: 512 KB, shared with CPU 0
L3 Cache: 8192 KB, shared with CPU 0, 2, 3, 4, 5
Found CPU 2, with:
L1 Cache: 32 KB, shared with CPU 3
L2 Cache: 512 KB, shared with CPU 3
L3 Cache: 8192 KB, shared with CPU 0, 1, 3, 4, 5
Found CPU 3, with:
L1 Cache: 32 KB, shared with CPU 2
L2 Cache: 512 KB, shared with CPU 2
L3 Cache: 8192 KB, shared with CPU 0, 1, 2, 4, 5
Found CPU 4, with:
L1 Cache: 32 KB, shared with CPU 5
L2 Cache: 512 KB, shared with CPU 5
L3 Cache: 8192 KB, shared with CPU 0, 1, 2, 3, 5
Found CPU 5, with:
L1 Cache: 32 KB, shared with CPU 4
L2 Cache: 512 KB, shared with CPU 4
L3 Cache: 8192 KB, shared with CPU 0, 1, 2, 3, 4
Found CPU 6, with:
L1 Cache: 32 KB, shared with CPU 7
L2 Cache: 512 KB, shared with CPU 7
L3 Cache: 8192 KB, shared with CPU 7, 8, 9, 10, 11
Found CPU 7, with:
L1 Cache: 32 KB, shared with CPU 6
L2 Cache: 512 KB, shared with CPU 6
L3 Cache: 8192 KB, shared with CPU 6, 8, 9, 10, 11
Found CPU 8, with:
L1 Cache: 32 KB, shared with CPU 9
L2 Cache: 512 KB, shared with CPU 9
L3 Cache: 8192 KB, shared with CPU 6, 7, 9, 10, 11
Found CPU 9, with:
L1 Cache: 32 KB, shared with CPU 8
L2 Cache: 512 KB, shared with CPU 8
L3 Cache: 8192 KB, shared with CPU 6, 7, 8, 10, 11
Found CPU 10, with:
L1 Cache: 32 KB, shared with CPU 11
L2 Cache: 512 KB, shared with CPU 11
L3 Cache: 8192 KB, shared with CPU 6, 7, 8, 9, 11
Found CPU 11, with:
L1 Cache: 32 KB, shared with CPU 10
L2 Cache: 512 KB, shared with CPU 10
L3 Cache: 8192 KB, shared with CPU 6, 7, 8, 9, 10
Detecting OpenCL-capable GPUs...
Pм)╨╫�
+------------------------------------------+
| JC Expert Cryptonote CPU+GPU Miner 0.32q |
+------------------------------------------+
For Windows 64-bits
Analyzing Processors topology...
AMD Ryzen 5 1600 Six-Core Processor
Assembly codename: ryzen
SSE2 : Yes
SSE3 : Yes
SSE4 : Yes
AES : Yes
AVX : Yes
AVX2 : Yes
Auto-configuration, selected CPUs will be highlighted...
Found CPU 0, with:
L1 Cache: 32 KB, shared with CPU 1
L2 Cache: 512 KB, shared with CPU 1
L3 Cache: 8192 KB, shared with CPU 1, 2, 3, 4, 5
Found CPU 1, with:
L1 Cache: 32 KB, shared with CPU 0
L2 Cache: 512 KB, shared with CPU 0
L3 Cache: 8192 KB, shared with CPU 0, 2, 3, 4, 5
Found CPU 2, with:
L1 Cache: 32 KB, shared with CPU 3
L2 Cache: 512 KB, shared with CPU 3
L3 Cache: 8192 KB, shared with CPU 0, 1, 3, 4, 5
Found CPU 3, with:
L1 Cache: 32 KB, shared with CPU 2
L2 Cache: 512 KB, shared with CPU 2
L3 Cache: 8192 KB, shared with CPU 0, 1, 2, 4, 5
Found CPU 4, with:
L1 Cache: 32 KB, shared with CPU 5
L2 Cache: 512 KB, shared with CPU 5
L3 Cache: 8192 KB, shared with CPU 0, 1, 2, 3, 5
Found CPU 5, with:
L1 Cache: 32 KB, shared with CPU 4
L2 Cache: 512 KB, shared with CPU 4
L3 Cache: 8192 KB, shared with CPU 0, 1, 2, 3, 4
Found CPU 6, with:
L1 Cache: 32 KB, shared with CPU 7
L2 Cache: 512 KB, shared with CPU 7
L3 Cache: 8192 KB, shared with CPU 7, 8, 9, 10, 11
Found CPU 7, with:
L1 Cache: 32 KB, shared with CPU 6
L2 Cache: 512 KB, shared with CPU 6
L3 Cache: 8192 KB, shared with CPU 6, 8, 9, 10, 11
Found CPU 8, with:
L1 Cache: 32 KB, shared with CPU 9
L2 Cache: 512 KB, shared with CPU 9
L3 Cache: 8192 KB, shared with CPU 6, 7, 9, 10, 11
Found CPU 9, with:
L1 Cache: 32 KB, shared with CPU 8
L2 Cache: 512 KB, shared with CPU 8
L3 Cache: 8192 KB, shared with CPU 6, 7, 8, 10, 11
Found CPU 10, with:
L1 Cache: 32 KB, shared with CPU 11
L2 Cache: 512 KB, shared with CPU 11
L3 Cache: 8192 KB, shared with CPU 6, 7, 8, 9, 11
Found CPU 11, with:
L1 Cache: 32 KB, shared with CPU 10
L2 Cache: 512 KB, shared with CPU 10
L3 Cache: 8192 KB, shared with CPU 6, 7, 8, 9, 10
Detecting OpenCL-capable GPUs...
Found GPU 0, with:
Vendor: AMD
Processor: Baffin
Device: 09:00
Compute-Units: 16
Cache Memory: 16 KB
Local Memory: 32 KB
Global Memory: 4096 MB
Addressing: 64-bits
Preparing 10 Mining Threads...
+-- Thread 0 config -----------------------+
| Run on CPU: 0 |
| Use cache: yes |
| Multi-hash: no |
| Assembly module: ryzen |
+------------------------------------------+
+-- Thread 1 config -----------------------+
| Run on CPU: 1 |
| Use cache: yes |
| Multi-hash: no |
| Assembly module: ryzen |
+------------------------------------------+
+-- Thread 2 config -----------------------+
| Run on CPU: 2 |
| Use cache: yes |
| Multi-hash: no |
| Assembly module: ryzen |
+------------------------------------------+
+-- Thread 3 config -----------------------+
| Run on CPU: 4 |
| Use cache: yes |
| Multi-hash: no |
| Assembly module: ryzen |
+------------------------------------------+
+-- Thread 4 config -----------------------+
| Run on CPU: 6 |
| Use cache: yes |
| Multi-hash: no |
| Assembly module: ryzen |
+------------------------------------------+
+-- Thread 5 config -----------------------+
| Run on CPU: 7 |
| Use cache: yes |
| Multi-hash: no |
| Assembly module: ryzen |
+------------------------------------------+
+-- Thread 6 config -----------------------+
| Run on CPU: 8 |
| Use cache: yes |
| Multi-hash: no |
| Assembly module: ryzen |
+------------------------------------------+
+-- Thread 7 config -----------------------+
| Run on CPU: 10 |
| Use cache: yes |
| Multi-hash: no |
| Assembly module: ryzen |
+------------------------------------------+
+-- Thread 8 config -----------------------+
| Run on GPU: 0 |
| Multi-hash: 464 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 8 |
+------------------------------------------+
+-- Thread 9 config -----------------------+
| Run on GPU: 0 |
| Multi-hash: 464 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 8 |
+------------------------------------------+
Cryptonight Variation: Cryptonight V7 fork of April-2018
Low intensity.
Starting CPU Mining thread 0, affinity: CPU 0
Thread 0 successfully bound to CPU 0
Allocated shared Large Page at: 0000023044c00000
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 0 of NUMA node 0 at: 0000023044e00000
Starting CPU Mining thread 1, affinity: CPU 1
Thread 1 successfully bound to CPU 1
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 1 of NUMA node 0 at: 0000023045000000
Starting CPU Mining thread 2, affinity: CPU 2
Thread 2 successfully bound to CPU 2
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 2 of NUMA node 0 at: 0000023045200000
Starting CPU Mining thread 3, affinity: CPU 4
Thread 3 successfully bound to CPU 4
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 4 of NUMA node 0 at: 0000023045400000
Starting CPU Mining thread 4, affinity: CPU 6
Thread 4 successfully bound to CPU 6
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 6 of NUMA node 0 at: 0000023045600000
Starting CPU Mining thread 5, affinity: CPU 7
Thread 5 successfully bound to CPU 7
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 7 of NUMA node 0 at: 0000023045800000
Starting CPU Mining thread 6, affinity: CPU 8
Thread 6 successfully bound to CPU 8
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 8 of NUMA node 0 at: 0000023045a00000
Starting CPU Mining thread 7, affinity: CPU 10
Thread 7 successfully bound to CPU 10
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 10 of NUMA node 0 at: 0000023045c00000
Starting GPU Mining thread 8, on GPU 0
Created OpenCL Context for GPU 0 at 000002304485e040
Created OpenCL Thread 8 Command-Queue for GPU 0 at 0000023044872e10
Scratchpad Allocation success for OpenCL Thread 8
Allocating big 928MB scratchpad for OpenCL Thread 8...
Compiling kernels of OpenCL Thread 8...
Compilation of OpenCL kernels failed.
Error: CL_BUILD_PROGRAM_FAILURE Code: O-2.10
Starting GPU Mining thread 9, on GPU 0
Created OpenCL Thread 9 Command-Queue for GPU 0 at 0000023044846400
Scratchpad Allocation success for OpenCL Thread 9
Allocating big 928MB scratchpad for OpenCL Thread 9...
Compiling kernels of OpenCL Thread 9...
Compilation of OpenCL kernels failed.
Error: CL_BUILD_PROGRAM_FAILURE Code: O-2.10
Devfee for CPU is 1.5%
Devfee for GPU is 0.9%
15:34:41 | OpenCL Thread 8 failed, Stop.
15:34:41 | Unloaded OpenCL kernels of GPU Thread 8
15:34:41 | Connecting to mining pool pool.supportxmr.com:5555 ...
15:34:41 | Monero (XMR/XMV) 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.
t GPU temperature and fan speed.
q quit.
15:34:41 | GPU Compute allocation starts at 80% and reaches 100% after ~5min,
15:34:41 | during this time, the hashrate may be unstable and inconsistent.
15:34:41 | Let the miner warm-up if you're tuning for performance.
15:34:41 | OpenCL Thread 9 failed, Stop.
15:34:41 | Unloaded OpenCL kernels of GPU Thread 9
15:34:41 | Released OpenCL Thread 8 Scratchpad at 000002304ad32ac0
15:34:41 | Released OpenCL Thread 9 Scratchpad at 00000230449d9fb0
15:34:41 | Released OpenCL Thread 8 Command-Queue of GPU 0 at 0000023044872e10
15:34:42 | Released OpenCL Thread 9 Command-Queue of GPU 0 at 0000023044846400
15:34:42 | Connected to pool. Now logging in...
15:34:42 | Successfuly logged as 47aepaEmi318XjZV5k5Svf4jYdzb4dKcZX7bLbSPCP41Ade7NZs816rjXqrT3anyZ22j7DEE74GkbVc QFyH2nNiC3hzR3gr
15:34:42 | Pool changes Difficulty to 10000. Any thoughts on that? xmr-stak, Claymore and other GPU miners work just fine. |
|
|
|
|
JCE-Miner (OP)
Member
Offline
Activity: 350
Merit: 22
|
|
October 15, 2018, 02:14:51 AM |
|
JCE 0.33a is preconfigured in advance of a few days to use Monero V2 for XMR, so yes, force it to V7 with --variation 3 until it forks, then switch to --variation 15 (or 0, or remove the parameter) OpenCL compile: first, i apologize not to have answered the first time, i was focusing on the CPU version, and i still need to make the GPU one. The symptom is similar to JCE running on Windows7, which is not supported, but here you're on Win10. I tested fine on Win10 + RX560, but not with that precise version of the drivers. So i'll change one of my rig to the 18.8.1 and test again, but i won't have time immeditely, the V8 support has to be high priority. Again, compared to xmrig or stak or other, we all use different methods of handling the OpenCL (I generate, Claymore precompiled...) so we have different level of compatibility. For example Claymore 11.3 doesn't work on the RX550, JCE does. Please tell me what exact version of Win10 you have, to be able to reproduce the exact same way. Thanks for the detailled report  |
|
|
|
|
|
UnclWish
|
|
October 15, 2018, 05:06:13 AM |
|
@JCE-Miner, now you must explain to them, why only Windows 10. And why Windows 7 isn't support by miner...
|
|
|
|
|
|
|
|
UnclWish
|
|
October 15, 2018, 12:21:59 PM |
|
I know it, but most wouldn't search this... Thanx for direct link. |
|
|
|
|
JCE-Miner (OP)
Member
Offline
Activity: 350
Merit: 22
|
|
October 15, 2018, 01:52:25 PM
Last edit: October 15, 2018, 03:17:51 PM by JCE-Miner |
|
Windows 8.1 is supported too. And on the CPU version, that's all from Vista.
I'm releasing the V8 GPU version, based on the reference implementation provided by Monero. I'll work on the optimization later. I've had time to optimize the CPU assemblies, but i won't have any for the GPU.
I had to do the CPU first because the GPU version requires a working CPU implementation for the double-check.
0.33a GPU to be online in a few hours.
edit:
GPU version is online
Unlike what I said previously, i did not include the Heavy optim, i prefered doing an exact same version as 0.32, plus V8 support.
It still includes the CPU fixes for ETN introduced by CPU version 0.33a
Then I can add the feature i planned at short term:
* lower the fee to GPU level when all cpu are paused (more fair system)
* restart the warmup after a long disconnect
|
|
|
|
|
|
UnclWish
|
|
October 15, 2018, 03:18:44 PM |
|
Windows 8.1 is supported too. And on the CPU version, that's all from Vista.
I'm releasing the V8 GPU version, based on the reference implementation provided by Monero. I'll work on the optimization later. I've had time to optimize the CPU assemblies, but i won't have any for the GPU.
I had to do the CPU first because the GPU version requires a working CPU implementation for the double-check.
0.33a GPU to be online in a few hours.
edit:
GPU version is online
Unlike what I said previously, i did not include the Heavy optim, i prefered doing an exact same version as 0.32, plus V8 support.
It still includes the CPU fixes for ETN introduced by CPU version 0.33a
I'm sorry for offtopic, and didn't want to spend your time, but please explain me in two words V8 fork. Does it remooves v7, or it just will be new algo? |
|
|
|
|
JCE-Miner (OP)
Member
Offline
Activity: 350
Merit: 22
|
|
October 15, 2018, 03:24:24 PM |
|
JCE still contains all historical forks, Monero V8 is just the 15th in the list.
XMR and WOW wallets default to V8 (xmr in advance of 2 days), other are unchanged. So, to mine XMR before the fork, force it back to V7 with --variation 3. After, keep automatic mode.
Internally, V8 is not a superset of V7, like MSR or B2N are, it's a very new fork, with a very different scratchpad loop. And for the first time, it involves floating-point compute.
|
|
|
|
|
io8621
Member
Offline
Activity: 149
Merit: 11
|
|
October 15, 2018, 04:09:54 PM |
|
Hi.
0.32 version working fine on my rig, with 2gb and 4gb card.
But now, with last release have problem.
If force v7 algo is ok, kernel compile and mining normaly
but if try to set algo 0 (auto) or mining Wownero with V8 algo
miner stucking at compile kernel.
Now try with some 4 gb rig.
Tested Wownero V8 mining with srbminer and xmrstack 2.5 working fine.
This with Pitcairn r7 370 2gb card.
|
|
|
|
|
prvs
Newbie
Offline
Activity: 52
Merit: 0
|
|
October 15, 2018, 04:44:23 PM |
|
Hi.
0.32 version working fine on my rig, with 2gb and 4gb card.
But now, with last release have problem.
If force v7 algo is ok, kernel compile and mining normaly
but if try to set algo 0 (auto) or mining Wownero with V8 algo
miner stucking at compile kernel.
Now try with some 4 gb rig.
Tested Wownero V8 mining with srbminer and xmrstack 2.5 working fine.
This with Pitcairn r7 370 2gb card.
Also with 7970&280x cards ( |
|
|
|
|
coke15
Member
Offline
Activity: 176
Merit: 10
|
|
October 15, 2018, 05:03:29 PM |
|
hi
how will work jce in the moment of the fork?
if i put --variation 3---->v7 ok no v8
if i put 0 v7 ok/fork/v8 ok?
can't be behind the rigs at this moment,for hours :/
|
|
|
|
|
|
UnclWish
|
|
October 15, 2018, 05:49:15 PM |
|
JCE still contains all historical forks, Monero V8 is just the 15th in the list.
XMR and WOW wallets default to V8 (xmr in advance of 2 days), other are unchanged. So, to mine XMR before the fork, force it back to V7 with --variation 3. After, keep automatic mode.
Internally, V8 is not a superset of V7, like MSR or B2N are, it's a very new fork, with a very different scratchpad loop. And for the first time, it involves floating-point compute.
Does it means that after the fork V7 stops to works and v8 will be instead of it? What about heavy and other v7/cryptonight childs algos? |
|
|
|
|
|
Iamtutut
|
|
October 15, 2018, 08:42:38 PM |
|
No change for other cryptos that use V7 or CN based algo unless they announce a fork.
|
|
|
|
|
vmozara
Member
Offline
Activity: 190
Merit: 59
|
|
October 15, 2018, 09:00:53 PM |
|
Did anybody try v8 with Vega cards? I tried now on my home pc with Vega 64 and hashrate went from 2200 to about 1550  I tried mining wownero |
|
|
|
|
|
