CCminer(SP-MOD) Modded NVIDIA Maxwell / Pascal kernels. - page 1008.

chrysophylax

legendary

Activity: 2912

Merit: 1091

--- ChainWorks Industries ---

Quote from: hashbrown9000 on August 10, 2015, 09:38:37 PM

Does anyone have any suggestions for fixing these errors during compile? it is SP_'s build #907. All 750ti.

Quote

lyra2/lyra2REv2.o: In function `lyra2v2_hash':
tmpxft_000039b3_00000000-6_lyra2REv2.compute_52.cudafe1.cpp:(.text+0x20): multiple definition of `lyra2v2_hash'
lyra2/lyra2REv2.o:tmpxft_000039b3_00000000-6_lyra2REv2.compute_52.cudafe1.cpp:(.text+0x20): first defined here
lyra2/lyra2REv2.o: In function `scanhash_lyra2v2':
tmpxft_000039b3_00000000-6_lyra2REv2.compute_52.cudafe1.cpp:(.text+0x200): multiple definition of `scanhash_lyra2v2'
lyra2/lyra2REv2.o:tmpxft_000039b3_00000000-6_lyra2REv2.compute_52.cudafe1.cpp:(.text+0x200): first defined here
lyra2/cuda_lyra2v2.o: In function `lyra2v2_gpu_hash_32_v3(unsigned int, unsigned int, uint2*)':
tmpxft_000039fd_00000000-6_cuda_lyra2v2.compute_52.cudafe1.cpp:(.text+0x20): multiple definition of `lyra2v2_gpu_hash_32_v3(unsigned int, unsigned int, uint2*)'
lyra2/cuda_lyra2v2.o:tmpxft_000039fd_00000000-6_cuda_lyra2v2.compute_52.cudafe1.cpp:(.text+0x20): first defined here
lyra2/cuda_lyra2v2.o: In function `lyra2v2_gpu_hash_32(unsigned int, unsigned int, uint2*)':
tmpxft_000039fd_00000000-6_cuda_lyra2v2.compute_52.cudafe1.cpp:(.text+0xa0): multiple definition of `lyra2v2_gpu_hash_32(unsigned int, unsigned int, uint2*)'
lyra2/cuda_lyra2v2.o:tmpxft_000039fd_00000000-6_cuda_lyra2v2.compute_52.cudafe1.cpp:(.text+0xa0): first defined here
lyra2/cuda_lyra2v2.o: In function `lyra2v2_cpu_init(int, unsigned int, unsigned long*)':
tmpxft_000039fd_00000000-6_cuda_lyra2v2.compute_52.cudafe1.cpp:(.text+0x120): multiple definition of `lyra2v2_cpu_init(int, unsigned int, unsigned long*)'
lyra2/cuda_lyra2v2.o:tmpxft_000039fd_00000000-6_cuda_lyra2v2.compute_52.cudafe1.cpp:(.text+0x120): first defined here
lyra2/cuda_lyra2v2.o: In function `lyra2v2_cpu_hash_32(int, unsigned int, unsigned int, unsigned long*)':
tmpxft_000039fd_00000000-6_cuda_lyra2v2.compute_52.cudafe1.cpp:(.text+0x150): multiple definition of `lyra2v2_cpu_hash_32(int, unsigned int, unsigned int, unsigned long*)'
lyra2/cuda_lyra2v2.o:tmpxft_000039fd_00000000-6_cuda_lyra2v2.compute_52.cudafe1.cpp:(.text+0x150): first defined here
lyra2/cuda_lyra2v2.o: In function `__device_stub__Z22lyra2v2_gpu_hash_32_v3jjP5uint2(unsigned int, unsigned int, uint2*)':
tmpxft_000039fd_00000000-6_cuda_lyra2v2.compute_52.cudafe1.cpp:(.text+0x320): multiple definition of `__device_stub__Z22lyra2v2_gpu_hash_32_v3jjP5uint2(unsigned int, unsigned in t, uint2*)'
lyra2/cuda_lyra2v2.o:tmpxft_000039fd_00000000-6_cuda_lyra2v2.compute_52.cudafe1.cpp:(.text+0x320): first defined here
lyra2/cuda_lyra2v2.o: In function `__device_stub__Z19lyra2v2_gpu_hash_32jjP5uint2(unsigned int, unsigned int, uint2*)':
tmpxft_000039fd_00000000-6_cuda_lyra2v2.compute_52.cudafe1.cpp:(.text+0x3a0): multiple definition of `__device_stub__Z19lyra2v2_gpu_hash_32jjP5uint2(unsigned int, unsigned int, uint2*)'
lyra2/cuda_lyra2v2.o:tmpxft_000039fd_00000000-6_cuda_lyra2v2.compute_52.cudafe1.cpp:(.text+0x3a0): first defined here
lyra2/lyra2REv2.o: In function `scanhash_lyra2v2':
tmpxft_000039b3_00000000-6_lyra2REv2.compute_52.cudafe1.cpp:(.text+0x5a5): undefined reference to `bmw256_setTarget(void const*)'
tmpxft_000039b3_00000000-6_lyra2REv2.compute_52.cudafe1.cpp:(.text+0x608): undefined reference to `cubehash256_cpu_hash_32(int, unsigned int, unsigned int, unsigned long*)'
tmpxft_000039b3_00000000-6_lyra2REv2.compute_52.cudafe1.cpp:(.text+0x647): undefined reference to `cubehash256_cpu_hash_32(int, unsigned int, unsigned int, unsigned long*)'
tmpxft_000039b3_00000000-6_lyra2REv2.compute_52.cudafe1.cpp:(.text+0x661): undefined reference to `bmw256_cpu_hash_32(int, unsigned int, unsigned int, unsigned long*, unsigned i nt*)'
tmpxft_000039b3_00000000-6_lyra2REv2.compute_52.cudafe1.cpp:(.text+0x7c0): undefined reference to `bmw256_cpu_init(int, unsigned int)'
lyra2/lyra2REv2.o: In function `scanhash_lyra2v2':
tmpxft_000039b3_00000000-6_lyra2REv2.compute_52.cudafe1.cpp:(.text+0x5a5): undefined reference to `bmw256_setTarget(void const*)'
tmpxft_000039b3_00000000-6_lyra2REv2.compute_52.cudafe1.cpp:(.text+0x608): undefined reference to `cubehash256_cpu_hash_32(int, unsigned int, unsigned int, unsigned long*)'
tmpxft_000039b3_00000000-6_lyra2REv2.compute_52.cudafe1.cpp:(.text+0x647): undefined reference to `cubehash256_cpu_hash_32(int, unsigned int, unsigned int, unsigned long*)'
tmpxft_000039b3_00000000-6_lyra2REv2.compute_52.cudafe1.cpp:(.text+0x661): undefined reference to `bmw256_cpu_hash_32(int, unsigned int, unsigned int, unsigned long*, unsigned i nt*)'
tmpxft_000039b3_00000000-6_lyra2REv2.compute_52.cudafe1.cpp:(.text+0x7c0): undefined reference to `bmw256_cpu_init(int, unsigned int)'
collect2: error: ld returned 1 exit status
make[2]: *** [ccminer] Error 1
make[2]: Leaving directory `/opt/miners/ccminer-sp907/ccminer'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/opt/miners/ccminer-sp907/ccminer'
make: *** [all] Error 2

is this a computer 5.2 error? ...

remark it out of the makefile then retry ...

when you git clone - the Makefile.am has compute 5.2 as the primary compute version with 5.0 as being the additional ...

remark it out with # and remove the + from the compute 5.0 version ...

from this ...

nvcc_ARCH = -gencode=arch=compute_52,code=\"sm_52,compute_52\"
nvcc_ARCH += -gencode=arch=compute_50,code=\"sm_50,compute_50\"
#nvcc_ARCH += -gencode=arch=compute_35,code=\"sm_35,compute_35\"
#nvcc_ARCH += -gencode=arch=compute_30,code=\"sm_30,compute_30\"

to this ...

#nvcc_ARCH = -gencode=arch=compute_52,code=\"sm_52,compute_52\"
nvcc_ARCH = -gencode=arch=compute_50,code=\"sm_50,compute_50\"
#nvcc_ARCH += -gencode=arch=compute_35,code=\"sm_35,compute_35\"
#nvcc_ARCH += -gencode=arch=compute_30,code=\"sm_30,compute_30\"

save the file - then recompile ... see if that works ...

edit - that probably wont work actually ... i just tried on remote and it doesnt compile with very similar errors ... its obviously a compile issue of some sort - which is way out of my understanding ...

apologies ...

#crysx

hashbrown9000

sr. member

Activity: 427

Merit: 250

Does anyone have any suggestions for fixing these errors during compile? it is SP_'s build #907. All 750ti.

Quote

lyra2/lyra2REv2.o: In function `lyra2v2_hash':
tmpxft_000039b3_00000000-6_lyra2REv2.compute_52.cudafe1.cpp:(.text+0x20): multiple definition of `lyra2v2_hash'
lyra2/lyra2REv2.o:tmpxft_000039b3_00000000-6_lyra2REv2.compute_52.cudafe1.cpp:(.text+0x20): first defined here
lyra2/lyra2REv2.o: In function `scanhash_lyra2v2':
tmpxft_000039b3_00000000-6_lyra2REv2.compute_52.cudafe1.cpp:(.text+0x200): multiple definition of `scanhash_lyra2v2'
lyra2/lyra2REv2.o:tmpxft_000039b3_00000000-6_lyra2REv2.compute_52.cudafe1.cpp:(.text+0x200): first defined here
lyra2/cuda_lyra2v2.o: In function `lyra2v2_gpu_hash_32_v3(unsigned int, unsigned int, uint2*)':
tmpxft_000039fd_00000000-6_cuda_lyra2v2.compute_52.cudafe1.cpp:(.text+0x20): multiple definition of `lyra2v2_gpu_hash_32_v3(unsigned int, unsigned int, uint2*)'
lyra2/cuda_lyra2v2.o:tmpxft_000039fd_00000000-6_cuda_lyra2v2.compute_52.cudafe1.cpp:(.text+0x20): first defined here
lyra2/cuda_lyra2v2.o: In function `lyra2v2_gpu_hash_32(unsigned int, unsigned int, uint2*)':
tmpxft_000039fd_00000000-6_cuda_lyra2v2.compute_52.cudafe1.cpp:(.text+0xa0): multiple definition of `lyra2v2_gpu_hash_32(unsigned int, unsigned int, uint2*)'
lyra2/cuda_lyra2v2.o:tmpxft_000039fd_00000000-6_cuda_lyra2v2.compute_52.cudafe1.cpp:(.text+0xa0): first defined here
lyra2/cuda_lyra2v2.o: In function `lyra2v2_cpu_init(int, unsigned int, unsigned long*)':
tmpxft_000039fd_00000000-6_cuda_lyra2v2.compute_52.cudafe1.cpp:(.text+0x120): multiple definition of `lyra2v2_cpu_init(int, unsigned int, unsigned long*)'
lyra2/cuda_lyra2v2.o:tmpxft_000039fd_00000000-6_cuda_lyra2v2.compute_52.cudafe1.cpp:(.text+0x120): first defined here
lyra2/cuda_lyra2v2.o: In function `lyra2v2_cpu_hash_32(int, unsigned int, unsigned int, unsigned long*)':
tmpxft_000039fd_00000000-6_cuda_lyra2v2.compute_52.cudafe1.cpp:(.text+0x150): multiple definition of `lyra2v2_cpu_hash_32(int, unsigned int, unsigned int, unsigned long*)'
lyra2/cuda_lyra2v2.o:tmpxft_000039fd_00000000-6_cuda_lyra2v2.compute_52.cudafe1.cpp:(.text+0x150): first defined here
lyra2/cuda_lyra2v2.o: In function `__device_stub__Z22lyra2v2_gpu_hash_32_v3jjP5uint2(unsigned int, unsigned int, uint2*)':
tmpxft_000039fd_00000000-6_cuda_lyra2v2.compute_52.cudafe1.cpp:(.text+0x320): multiple definition of `__device_stub__Z22lyra2v2_gpu_hash_32_v3jjP5uint2(unsigned int, unsigned in t, uint2*)'
lyra2/cuda_lyra2v2.o:tmpxft_000039fd_00000000-6_cuda_lyra2v2.compute_52.cudafe1.cpp:(.text+0x320): first defined here
lyra2/cuda_lyra2v2.o: In function `__device_stub__Z19lyra2v2_gpu_hash_32jjP5uint2(unsigned int, unsigned int, uint2*)':
tmpxft_000039fd_00000000-6_cuda_lyra2v2.compute_52.cudafe1.cpp:(.text+0x3a0): multiple definition of `__device_stub__Z19lyra2v2_gpu_hash_32jjP5uint2(unsigned int, unsigned int, uint2*)'
lyra2/cuda_lyra2v2.o:tmpxft_000039fd_00000000-6_cuda_lyra2v2.compute_52.cudafe1.cpp:(.text+0x3a0): first defined here
lyra2/lyra2REv2.o: In function `scanhash_lyra2v2':
tmpxft_000039b3_00000000-6_lyra2REv2.compute_52.cudafe1.cpp:(.text+0x5a5): undefined reference to `bmw256_setTarget(void const*)'
tmpxft_000039b3_00000000-6_lyra2REv2.compute_52.cudafe1.cpp:(.text+0x608): undefined reference to `cubehash256_cpu_hash_32(int, unsigned int, unsigned int, unsigned long*)'
tmpxft_000039b3_00000000-6_lyra2REv2.compute_52.cudafe1.cpp:(.text+0x647): undefined reference to `cubehash256_cpu_hash_32(int, unsigned int, unsigned int, unsigned long*)'
tmpxft_000039b3_00000000-6_lyra2REv2.compute_52.cudafe1.cpp:(.text+0x661): undefined reference to `bmw256_cpu_hash_32(int, unsigned int, unsigned int, unsigned long*, unsigned i nt*)'
tmpxft_000039b3_00000000-6_lyra2REv2.compute_52.cudafe1.cpp:(.text+0x7c0): undefined reference to `bmw256_cpu_init(int, unsigned int)'
lyra2/lyra2REv2.o: In function `scanhash_lyra2v2':
tmpxft_000039b3_00000000-6_lyra2REv2.compute_52.cudafe1.cpp:(.text+0x5a5): undefined reference to `bmw256_setTarget(void const*)'
tmpxft_000039b3_00000000-6_lyra2REv2.compute_52.cudafe1.cpp:(.text+0x608): undefined reference to `cubehash256_cpu_hash_32(int, unsigned int, unsigned int, unsigned long*)'
tmpxft_000039b3_00000000-6_lyra2REv2.compute_52.cudafe1.cpp:(.text+0x647): undefined reference to `cubehash256_cpu_hash_32(int, unsigned int, unsigned int, unsigned long*)'
tmpxft_000039b3_00000000-6_lyra2REv2.compute_52.cudafe1.cpp:(.text+0x661): undefined reference to `bmw256_cpu_hash_32(int, unsigned int, unsigned int, unsigned long*, unsigned i nt*)'
tmpxft_000039b3_00000000-6_lyra2REv2.compute_52.cudafe1.cpp:(.text+0x7c0): undefined reference to `bmw256_cpu_init(int, unsigned int)'
collect2: error: ld returned 1 exit status
make[2]: *** [ccminer] Error 1
make[2]: Leaving directory `/opt/miners/ccminer-sp907/ccminer'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/opt/miners/ccminer-sp907/ccminer'
make: *** [all] Error 2

joblo

legendary

Activity: 1470

Merit: 1114

Quote from: sp_ on August 10, 2015, 03:18:49 PM

Quote from: joblo on August 10, 2015, 03:08:27 PM

The CPU problem is fixed but there's still a problem. I have a linux rig with a 970 and a 780ti, compiled
ccminer for compute versions 3.5, 5.0 & 5.2.
When I start mining neoscrypt on both GPUs I get nothing but HW errors on the 780ti (GPU1). But I can mine
each GPU in seperate instances of ccminer.

This fork doesn't support compute 3.5. Maxwell only. (5.0 and up). but it might work for some algos. Don't have a 3.5 card anymore.

I don't know what he hardware errors were about but they've gone away.

Neoscrypt vs r58: 970 550kh (+25k), 780ti 335kh (-45k), +120 OC on both.
It looks like I'll be keeping r58 for mining neoscrypt on the 780ti.

antonio8

legendary

Activity: 1400

Merit: 1000

Is it just me or is the hash rate all over the place on lyrav2 algo?

750ti's from 4 Mh all the way down to 1.5 Mh and up again.

EDIT: No extra flags or anything.

chrysophylax

legendary

Activity: 2912

Merit: 1091

--- ChainWorks Industries ---

Quote from: scryptr on August 10, 2015, 07:00:31 PM

DONATION FOR GOOD WORK--

DJM34, Pallas, I flipped you each a nickle. The overall improvement on both Lyra2v2, and on Neoscrypt, was excellent!!!

As soon as I can compile SP_ 's release dot 60 on Linux, he's up for his reward, too. The teamwork and co-operation is really good for ccminer. Everyone should donate....

Thanks!

--scryptr

wow - so much happened in the couple of days ive been ill ... and ive still got another day or two before i get back to the office ...

seems that the miner has gone through a few changes also - any major issues that i need to look out for with the latest v60? ...

is cuda 6.5 still the best to compile with? ...

cant wait to try this out ...

#crysx

scryptr

legendary

Activity: 1797

Merit: 1028

DONATION FOR GOOD WORK--

DJM34, Pallas, I flipped you each a nickle. The overall improvement on both Lyra2v2, and on Neoscrypt, was excellent!!!

As soon as I can compile SP_ 's release dot 60 on Linux, he's up for his reward, too. The teamwork and co-operation is really good for ccminer. Everyone should donate....

Thanks!

--scryptr

djm34

legendary

Activity: 1400

Merit: 1050

Quote from: fenomenhaa on August 10, 2015, 06:23:04 PM

Quote from: djm34 on August 10, 2015, 06:15:39 PM

Quote from: fenomenhaa on August 10, 2015, 06:07:50 PM

Quote from: scryptr on August 10, 2015, 06:05:45 PM

Quote from: fenomenhaa on August 10, 2015, 05:52:52 PM

With -a lyra2v2 i just get share above target !!! what's wrong?

POOL PROBLEM--

I think it is a pool problem. I get the same thing on Nicehash. Other pools work fine. I read that a miner should use the "--diff 2" command flag to adjust the difficulty, but it did not work for me. --scryptr

Already tried 3 pools,(nicehash,ffpool and Cointron) all same error, This pools also works with "a lyra2" but with lyra2v2 noo...

well if the pool still use lyra2, then they didn't update... so don't mine there, you'll be mining on a wrong fork

Yeah it seems that's truth,pool.verters. is working without problem..with latest realese 750 ti 4800m/hash 970 : 10200m/hash

coinotron is working too and p2pool.pl (as far as I know)

fenomenhaa

sr. member

Activity: 248

Merit: 250

Quote from: djm34 on August 10, 2015, 06:15:39 PM

Quote from: fenomenhaa on August 10, 2015, 06:07:50 PM

Quote from: scryptr on August 10, 2015, 06:05:45 PM

Quote from: fenomenhaa on August 10, 2015, 05:52:52 PM

With -a lyra2v2 i just get share above target !!! what's wrong?

POOL PROBLEM--

I think it is a pool problem. I get the same thing on Nicehash. Other pools work fine. I read that a miner should use the "--diff 2" command flag to adjust the difficulty, but it did not work for me. --scryptr

Already tried 3 pools,(nicehash,ffpool and Cointron) all same error, This pools also works with "a lyra2" but with lyra2v2 noo...

well if the pool still use lyra2, then they didn't update... so don't mine there, you'll be mining on a wrong fork

Yeah it seems that's truth,pool.verters. is working without problem..with latest realese 750 ti 4800m/hash 970 : 10200m/hash

djm34

legendary

Activity: 1400

Merit: 1050

Quote from: fenomenhaa on August 10, 2015, 06:07:50 PM

Quote from: scryptr on August 10, 2015, 06:05:45 PM

Quote from: fenomenhaa on August 10, 2015, 05:52:52 PM

With -a lyra2v2 i just get share above target !!! what's wrong?

POOL PROBLEM--

I think it is a pool problem. I get the same thing on Nicehash. Other pools work fine. I read that a miner should use the "--diff 2" command flag to adjust the difficulty, but it did not work for me. --scryptr

Already tried 3 pools,(nicehash,ffpool and Cointron) all same error, This pools also works with "a lyra2" but with lyra2v2 noo...

well if the pool still use lyra2, then they didn't update... so don't mine there, you'll be mining on a wrong fork

scryptr

legendary

Activity: 1797

Merit: 1028

Quote from: fenomenhaa on August 10, 2015, 06:07:50 PM

Quote from: scryptr on August 10, 2015, 06:05:45 PM

Quote from: fenomenhaa on August 10, 2015, 05:52:52 PM

With -a lyra2v2 i just get share above target !!! what's wrong?

POOL PROBLEM--

I think it is a pool problem. I get the same thing on Nicehash. Other pools work fine. I read that a miner should use the "--diff 2" command flag to adjust the difficulty, but it did not work for me. --scryptr

Already tried 3 pools,(nicehash,ffpool and Cointron) all same error, This pools also works with "a lyra2" but with lyra2v2 noo...

POOL PROBLEM--

If it works with "-a lyra2", it really is a pool problem. They are generating bogus blockchains. Try "ccminer.exe -a lyra2v2 -o stratum+tcp://vtc.give-me-coins.com:3337 -u dummy -p passwd". You need to set up an account and a worker.

--scryptr

P.S. From what I read, the time window from announcement of the algo change to the actual hardfork was 10 days, and exchanges and pools are behind. EDIT: Bittrex VTC wallets are no longer in maintenance mode, you can send and receive VTC.

--scryptr

Zels

full member

Activity: 203

Merit: 100

lyra2 & lyra2v2 are 2 differents algos

fenomenhaa

sr. member

Activity: 248

Merit: 250

Quote from: scryptr on August 10, 2015, 06:05:45 PM

Quote from: fenomenhaa on August 10, 2015, 05:52:52 PM

With -a lyra2v2 i just get share above target !!! what's wrong?

POOL PROBLEM--

I think it is a pool problem. I get the same thing on Nicehash. Other pools work fine. I read that a miner should use the "--diff 2" command flag to adjust the difficulty, but it did not work for me. --scryptr

Already tried 3 pools,(nicehash,ffpool and Cointron) all same error, This pools also works with "a lyra2" but with lyra2v2 noo...

scryptr

legendary

Activity: 1797

Merit: 1028

Quote from: fenomenhaa on August 10, 2015, 05:52:52 PM

With -a lyra2v2 i just get share above target !!! what's wrong?

POOL PROBLEM--

I think it is a pool problem. I get the same thing on Nicehash. Other pools work fine. I read that a miner should use the "--diff 2" command flag to adjust the difficulty, but it did not work for me. --scryptr

fenomenhaa

sr. member

Activity: 248

Merit: 250

With -a lyra2v2 i just get share above target !!! what's wrong?

djm34

legendary

Activity: 1400

Merit: 1050

Quote from: scryptr on August 10, 2015, 04:43:27 PM

Quote from: facanferff on August 10, 2015, 04:35:11 PM

I don't have much knowledge about this new algo lyra2v2 but would want to know if it's normal a "big" increase in speed in comparison to lyra2.

I ran both in benchmark mode (one at a time) and got:
lyra2:

Quote

[2015-08-10 22:32:43] GPU #0 Found nounce 00af3bbf
[2015-08-10 22:32:43] GPU #0: GeForce GTX 850M, 683.23
[2015-08-10 22:32:43] CPU #0: 683.23 kH/s

lyra2v2:

Quote

[2015-08-10 22:31:43] GPU #0 Found nounce 0dd624a1
[2015-08-10 22:31:43] GPU #0: GeForce GTX 850M, 3755
[2015-08-10 22:31:43] CPU #0: 3755 kH/s

Is it normal this increase?

THE INCREASE IS REAL--

DJM34's Lyra2v2 ccminer truly rocks! Answering your question, however: The increase is NOT normal!

Increases usually take 5-10-50kh/s steps. But, DJM34 completely re-did the code, and he is like the main developer for the miner, with the most know-how and experience on vertcoin.

THANKS! DJM34!!! --scryptr

it isn't an optimization per se but a new set of algos and more gpu friendly settings for lyra2

Grin

however the point was to increase gpu/cpu ratio from 1~2 to around 10 not nvidia/amd ratio (which actually should be about the same as it was with the optimized lyra2 with the 750ti running at 1500kh/s), also getting rid of groestl is probably more beneficial to the amd (even though it wasn't Christian "killer Groestl").

djm34

legendary

Activity: 1400

Merit: 1050

Quote from: sp_ on August 10, 2015, 03:37:56 PM

I am building release 60 now with the new lyra2v2 and the fixed neoscrypt(cpu and powerusage)

a 280x is doing only doing 3.5 MHASH. so this miner from djm34 is a goldmine for NVIDIA owners

it should do more, my 290x does 7.5MH/s (it needs small worksize and plenty of thread and to adjust the intensity so it fills up the memory)

facanferff

newbie

Activity: 8

Merit: 0

Quote from: scryptr on August 10, 2015, 04:43:27 PM

Quote from: facanferff on August 10, 2015, 04:35:11 PM

I don't have much knowledge about this new algo lyra2v2 but would want to know if it's normal a "big" increase in speed in comparison to lyra2.

I ran both in benchmark mode (one at a time) and got:
lyra2:

Quote

[2015-08-10 22:32:43] GPU #0 Found nounce 00af3bbf
[2015-08-10 22:32:43] GPU #0: GeForce GTX 850M, 683.23
[2015-08-10 22:32:43] CPU #0: 683.23 kH/s

lyra2v2:

Quote

[2015-08-10 22:31:43] GPU #0 Found nounce 0dd624a1
[2015-08-10 22:31:43] GPU #0: GeForce GTX 850M, 3755
[2015-08-10 22:31:43] CPU #0: 3755 kH/s

Is it normal this increase?

THE INCREASE IS REAL--

DJM34's Lyra2v2 ccminer truly rocks! Answering your question, however: The increase is NOT normal!

Increases usually take 5-10-50kh/s steps. But, DJM34 completely re-did the code, and he is like the main developer for the miner, with the most know-how and experience on vertcoin.

THANKS! DJM34!!! --scryptr

I see, then it is an excellent gift

.

scryptr

legendary

Activity: 1797

Merit: 1028

Quote from: facanferff on August 10, 2015, 04:35:11 PM

I don't have much knowledge about this new algo lyra2v2 but would want to know if it's normal a "big" increase in speed in comparison to lyra2.

I ran both in benchmark mode (one at a time) and got:
lyra2:

Quote

[2015-08-10 22:32:43] GPU #0 Found nounce 00af3bbf
[2015-08-10 22:32:43] GPU #0: GeForce GTX 850M, 683.23
[2015-08-10 22:32:43] CPU #0: 683.23 kH/s

lyra2v2:

Quote

[2015-08-10 22:31:43] GPU #0 Found nounce 0dd624a1
[2015-08-10 22:31:43] GPU #0: GeForce GTX 850M, 3755
[2015-08-10 22:31:43] CPU #0: 3755 kH/s

Is it normal this increase?

THE INCREASE IS REAL--

DJM34's Lyra2v2 ccminer truly rocks! Answering your question, however: The increase is NOT normal!

Increases usually take 5-10-50kh/s steps. But, DJM34 completely re-did the code, and he is like the main developer for the miner, with the most know-how and experience on vertcoin.

THANKS! DJM34!!! --scryptr

facanferff

newbie

Activity: 8

Merit: 0

I don't have much knowledge about this new algo lyra2v2 but would want to know if it's normal a "big" increase in speed in comparison to lyra2.

I ran both in benchmark mode (one at a time) and got:
lyra2:

Quote

[2015-08-10 22:32:43] GPU #0 Found nounce 00af3bbf
[2015-08-10 22:32:43] GPU #0: GeForce GTX 850M, 683.23
[2015-08-10 22:32:43] CPU #0: 683.23 kH/s

lyra2v2:

Quote

[2015-08-10 22:31:43] GPU #0 Found nounce 0dd624a1
[2015-08-10 22:31:43] GPU #0: GeForce GTX 850M, 3755
[2015-08-10 22:31:43] CPU #0: 3755 kH/s

Is it normal this increase?

pallas

legendary

Activity: 2716

Merit: 1094

Black Belt Developer

Quote from: bensam1231 on August 10, 2015, 04:31:27 PM

Quote from: sp_ on August 10, 2015, 03:55:14 PM

-fixed 100% cpu in neoscrypt and removed powerusage.
-Added lyra2rev2 from the DJM34 fork

1.5.60(sp-MOD) is available here: (10-08-2015)

https://github.com/sp-hash/ccminer/releases/

The sourcecode is available here:

https://github.com/sp-hash/ccminer

Does this fix the 30w increase in power usage?

it should... depending on the wattage difference from idle to 100% of your cpu :-)

Topic: CCminer(SP-MOD) Modded NVIDIA Maxwell / Pascal kernels. - page 1008. (Read 2347601 times)