Topic: [ANN] ccminer 2.3 - opensource - GPL (tpruvot) - page 11. (Read 500191 times)

Sorry, cant find answer, I have Nvidia Quadro 600 (GF108) SM2.1. Can i run ccminer 2.0 for lyra2z? Win 7 x64

I dont know where you read that but this is incorrect.
No GTX will reach that kind of hashrate.
You are in line with what other people have
https://cryptojunction.com/mining-hardware/gigabyte-gtx-970-g1-neoscrypt/

"Cuda error in func 'cuda_check_cpu_setTarget' at line 41 : unspecified launch failure."

HLP PLS?

GTX 1060's. Not mining with CPU. I've tried lowering my plimit but that didn't help.

Any ideas? Thanks

no, 1.5MH is only achieved by the 1080 Ti


rafuch0: this kind of errors can happen when you dont do a "make clean" between builds / gcc switches

I'm currently mining GBX (Neoscrypt) with the latest version of ccminer on a Asus Strix GTX970. I've read that this card can achieve 1.5Mh/s, but I'm achieving only 600kh/s. These are my OC settings:

https://ibb.co/jidJLx

and these are my ccminer settings:


I've also enabled the computing optimization on nVidia Control Panel, and DSR on 1.2x factor. I'm on CUDA 9.1.
Is there a way to improve that or I've reached the performance cap?

Yes Klaus-T only gets 4200 for 7 cards so I shut it down after 5 minutes.

Do you think its my MSI afterburner settings? Do you mind shared yours?


----

Update:

So far the fastest I get is

From this miner:
ccminer 2.2.3 (Dec. 2017)    "polytimos algo and keccakc (opt)"

Only 760 for each GTX1070 card.

Can someone please help me out?

Its been two months I am trying to get on Neoscrypt but every time I give up after hours and hours of trying. (Im tired of low profits on Equihash which runs builletproof without crashing in week so I need to switch algos)

I can never get over 720 per card from  my GTX1070 which is terrible I get only 5000 kH/s from my 7 GTX 1070 rig. I should get at least 7700.

HSRMiner doesnt download it says virus detected.

CUDAMiner is missing dll files and doesnt run.

Neoscrypt Miner has low hashrates.

ccminer 2.2.3 Cuda gives me low hashrates.

https://imgur.com/a/k5tnF

Heck I cant even embed an image, it just shows a link:

https://imgur.com/a/k5tnF

I stopped and restarted and only get 4200. What is going on?

@Epsylon3
ccminer seem to crash on more then 10 cards with timetravel algo (machinecoin).

Hello there

trying to get some help  i am compiling ccminer in Debian 9


/usr/bin/ld: x11/cuda_x11_luffa512_Cubehash.o: relocation R_X86_64_32S against `.bss' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: x11/x11evo.o: relocation R_X86_64_32S against `.data' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: x11/timetravel.o: relocation R_X86_64_32S against `.data' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: x11/bitcore.o: relocation R_X86_64_32S against `.data' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: x13/x13.o: relocation R_X86_64_32S against symbol `opt_benchmark' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: x13/cuda_x13_hamsi512.o: relocation R_X86_64_32S against symbol `stderr@@GLIBC_2.2.5' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: x13/cuda_x13_fugue512.o: relocation R_X86_64_32S against `.bss' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: x13/hsr.o: relocation R_X86_64_32S against symbol `opt_benchmark' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: x13/cuda_hsr_sm3.o: relocation R_X86_64_32S against `.bss' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: x15/x14.o: relocation R_X86_64_32S against symbol `opt_benchmark' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: x15/x15.o: relocation R_X86_64_32S against symbol `opt_benchmark' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: x15/cuda_x14_shabal512.o: relocation R_X86_64_32S against `.bss' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: x15/cuda_x15_whirlpool.o: relocation R_X86_64_32S against symbol `stderr@@GLIBC_2.2.5' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: x15/whirlpool.o: relocation R_X86_64_32S against `.bss' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: x15/cuda_x15_whirlpool_sm3.o: relocation R_X86_64_32S against `.bss' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: x17/x17.o: relocation R_X86_64_32S against symbol `opt_benchmark' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: x17/hmq17.o: relocation R_X86_64_32S against `.bss' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: x17/cuda_x17_haval256.o: relocation R_X86_64_32S against `.bss' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: x17/cuda_x17_sha512.o: relocation R_X86_64_32S against `.bss' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: x11/phi.o: relocation R_X86_64_32S against symbol `device_map' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: x11/cuda_streebog_maxwell.o: relocation R_X86_64_32S against `.bss' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: x11/c11.o: relocation R_X86_64_32S against symbol `device_map' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: x11/s3.o: relocation R_X86_64_32S against symbol `opt_benchmark' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: x11/sib.o: relocation R_X86_64_32S against symbol `device_map' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: x11/veltor.o: relocation R_X86_64_32S against symbol `device_map' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: x11/cuda_streebog.o: relocation R_X86_64_32S against `.bss' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: scrypt/blake.o: relocation R_X86_64_32S against `.bss' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: scrypt/keccak.o: relocation R_X86_64_32S against `.bss' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: scrypt/sha256.o: relocation R_X86_64_32S against `.bss' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: scrypt/salsa_kernel.o: relocation R_X86_64_32S against symbol `opt_nfactor' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: scrypt/test_kernel.o: relocation R_X86_64_32S against `.bss' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: scrypt/fermi_kernel.o: relocation R_X86_64_32S against `.bss' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: scrypt/kepler_kernel.o: relocation R_X86_64_32S against `.bss' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: scrypt/nv_kernel.o: relocation R_X86_64_32S against `.bss' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: scrypt/nv_kernel2.o: relocation R_X86_64_32S against `.bss' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: scrypt/titan_kernel.o: relocation R_X86_64_32S against `.bss' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: final link failed: Nonrepresentable section on output
collect2: error: ld returned 1 exit status
Makefile:1184: recipe for target 'ccminer' failed
make[2]: *** [ccminer] Error 1
make[2]: Leaving directory '/home/rafa/Desktop/ccminer'
Makefile:2201: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/rafa/Desktop/ccminer'
Makefile:654: recipe for target 'all' failed
make: *** [all] Error 2



have tried with gcc5 gcc6   g++-5  g++-6   and also diferent versions of clang 6.5 and 3.8 it always ends in error at that point.


Any clues?

I assume WebGL uses the GPU. Are we find as long as the browser is closed, though?

But it was working before on the same drivers I have now.

Downgrade the driver to 384.90, the newer drivers have this problem.

Hi, I have an issue with my CCminer 2.2.4.
I'm using it to mine XVG and it's been working just fine until I swapped my GTX 1050 to 1060 for a couple of days, and then when I installed the 1050 again the miner stopped showing the power consumption of the card. I reinstalled the drivers (performed a clean install), installed the card itself again on the motherboard and still nothing - it shows 0W all the time.

Any idea what could've caused it and how to fix it?

Given how many new and old coins are using neoscrypt it would be nice for tpruvot to actually have an update that creates stability with newer nvidia drivers. The last update I've seen is in may of 2016. maybe I've missed a few as I haven't really been paying attention to neoscrypt coins for the last six months and I think this has been part of the problem in general. it would be easier to mine anything but neoscrypt coins including ethash, equihash, lyra2v2 etc.

Hi tpruvot, you can add X12 algorithm to ccminer? X12 source for your ccminer is here: https://github.com/galaxycash/ccminer-x12

Apparently Epsylon feels the need to police everyones rig, sad days. Now we get to wait till someone forks Epsylons branch changing only one thing, which is allowing intensity changes.

Is it possible to add the following feature for solo mining?

      --no-getwork      disable getwork support

Why can't I force intensity?  For some reason it's setting it to whatever it wants when I'm mining this scrypt coin, I haven't had these issues with any other algo.  The --intensity flags worked just fine to throttle my gpu before.  I can't have it running at full blast, at that's what it sets it to.

This is my troubled config
ccminer-x64-75 -d 0 -a scrypt -o stratum+tcp://lycheebit.com:3433  -u D6rhrJqCK3DJuNZftuEEo181vjdPvhtLDF  -p c=DFS --cpu-priority 5 --no-autotune --intensity=10

I've tried playing muscial chairs and moving the parameters around and switching --intensity=10 to -i 10 and so on.  I'm confused why this one is giving me a headache.  No matter what I try the intensity is always set high causing 100% gpu load.

We looked at a number of those Pallas.

What we found were three things.

1 - The PSU are very cheaply made, as are the components. This lends itself to all sorts of things going wrong.
2 - The power delivery is subpar as opposed to say SEASONIC style of PSU's (like Corsair for example) where the power delivery is not tainted and steady. Spikes happen, but the better PSU units subdue these internal issues MUCH better than the any of these cheaper units.
3 - Warranty returns are a major pain, and sometimes costly for the amount of time these cheaper units are actually IN warranty.

These factors are why we choose the highest platinum series PSU that are local AND a 24hour replacement turnaround. Not three weeks like those cheaper ones.

Apart from that, Algos used in the ccminer-tpruvot and other quality mining apps that have variable hashfunctions active (like the latest X16R and TimeTravel/TimeTravel10) push the PSU really well with regards to power draw. A simple PSU made of poor quality components tend to die much easier, and I have had MANY (when theFARM was first started years ago) actually burn and melt the black Molex connectors TO the PSU as well as in some cases, the GPU connectors themselves.

#crysx

Sorry for the off topic, but since we are at it...

What do you guys think of these PSUs you can find on amazon, very powerful and cheap, with the right cables for a 6 gpus rig:

https://www.amazon.co.uk/dp/B0787BPNQ8

(price is 100-150$ for a 1600W gold rated unit).

I would get one just for curiosity, given the price, but I fear that it might fry some components.