[ANN] ccminer 2.3 - opensource - GPL (tpruvot)

[noided]

So I'm running into an issue when I run the build.sh script on Linux.

Code:

/usr/bin/ld: scrypt/fermi_kernel.o: relocation R_X86_64_32 against `.bss' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: scrypt/kepler_kernel.o: relocation R_X86_64_32 against `.bss' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: scrypt/nv_kernel.o: relocation R_X86_64_32 against `.bss' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: scrypt/nv_kernel2.o: relocation R_X86_64_32 against `.bss' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: scrypt/titan_kernel.o: relocation R_X86_64_32 against `.bss' can not be used when making a shared object; recompile with -fPIC

ect...

I tried setting my CFLAGS and CXXFLAGS variables to "-fPIC", aswell as just passing them directly to Make, but neither of those worked, so I'm pretty stumped as to what I should try next...

[1714864107]

1714864107

[1714864107]

1714864107

[1714864107]

1714864107

[1714864107]

1714864107

[lathrodectus]

So I'm running into an issue when I run the build.sh script on Linux.

Code:

/usr/bin/ld: scrypt/fermi_kernel.o: relocation R_X86_64_32 against `.bss' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: scrypt/kepler_kernel.o: relocation R_X86_64_32 against `.bss' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: scrypt/nv_kernel.o: relocation R_X86_64_32 against `.bss' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: scrypt/nv_kernel2.o: relocation R_X86_64_32 against `.bss' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: scrypt/titan_kernel.o: relocation R_X86_64_32 against `.bss' can not be used when making a shared object; recompile with -fPIC

ect...

I tried setting my CFLAGS and CXXFLAGS variables to "-fPIC", aswell as just passing them directly to Make, but neither of those worked, so I'm pretty stumped as to what I should try next...

Are you using gcc 5?

[pallas]

So I'm running into an issue when I run the build.sh script on Linux.

Code:

/usr/bin/ld: scrypt/fermi_kernel.o: relocation R_X86_64_32 against `.bss' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: scrypt/kepler_kernel.o: relocation R_X86_64_32 against `.bss' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: scrypt/nv_kernel.o: relocation R_X86_64_32 against `.bss' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: scrypt/nv_kernel2.o: relocation R_X86_64_32 against `.bss' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: scrypt/titan_kernel.o: relocation R_X86_64_32 against `.bss' can not be used when making a shared object; recompile with -fPIC

ect...

I tried setting my CFLAGS and CXXFLAGS variables to "-fPIC", aswell as just passing them directly to Make, but neither of those worked, so I'm pretty stumped as to what I should try next...

Try CPPFLAGS instead of CXXFLAGS

[Jbise1008]

Hi
I am trying to raise my intensity and having a few problems.   It is set to --intensity=9 and works just fine but when I try to go higher --intensty=15 cmd faults shortly after opening.   Any help would be greatly appreciated. 
Thanks

[pallas]

Hi
I am trying to raise my intensity and having a few problems.   It is set to --intensity=9 and works just fine but when I try to go higher --intensty=15 cmd faults shortly after opening.   Any help would be greatly appreciated.  
Thanks

How much gpu ram have you got and what algo?

[scryptr]

Hi
I am trying to raise my intensity and having a few problems.   It is set to --intensity=9 and works just fine but when I try to go higher --intensty=15 cmd faults shortly after opening.   Any help would be greatly appreciated.  
Thanks

How much gpu ram have you got and what algo?

I'VE NOTICED THAT INTENSITY SETTINGS DON'T WORK--

In the most recent versions of CCminer (2.2+), intensity settings appear to be ignored, and a default setting is applied.  Other users have posted about not being able to disable auto-tuning on algos like Scrypt pr CryptoNight. 

Frankly, default or auto-tune settings are often the best, but I have noticed that some older tuning parameters are ignored.       --scryptr

[ggminer2]

Hello,

Is ccminer 2.2.4 ready for linux or windows only ?
I would like to mine -phi algo

[konqueror]

Hello,

Is ccminer 2.2.4 ready for linux or windows only ?
I would like to mine -phi algo

There is a better phi miner by anorganix.

[scryptr]

Hello,

Is ccminer 2.2.4 ready for linux or windows only ?
I would like to mine -phi algo

LINUX AND WINDOWS BOTH--

Windows binaries are available on GitHub.  However, you will need to compile the source code for Linux.       --scryptr

[Amph]

when getwork will be added to ccminer? i see plenty of coins that need this lately for mining, solo is blatantly fucked for now unless you have a private pool or modified version of ccminer

[duffann]

when getwork will be added to ccminer? i see plenty of coins that need this lately for mining, solo is blatantly fucked for now unless you have a private pool or modified version of ccminer

exactly

[Epsylon3]

when your IQ will reach 100

[integrale]

may i ask why ccminer 2.2.4 is ignoring in Solo mining-mode the scantime function   for example   -s 1 ( 5 second interval )

tried with other forked ccminer and it works on some of them    -s 1 ( 1 second )


thx for any answer

[santan]

Recently i tried to solo mine few new coming coins..... But not succeded....
Perhaps the new coins based on new forks of bitcoin.... does not have solo mining enabled...as it had been dead for bitcoin.
Always Get Work failed. So i decided to stop trying solo mine....

[pallas]

Recently i tried to solo mine few new coming coins..... But not succeded....
Perhaps the new coins based on new forks of bitcoin.... does not have solo mining enabled...as it had been dead for bitcoin.
Always Get Work failed. So i decided to stop trying solo mine....

yeah, new coins usually don't support getwork, getblocktemplate only.
one solution is building your own pool.
but you may find a fork of ccminer with gbt support, I heard nanashi has it.

[krnlx]

http://yiimp.eu/ is offline again 

[Epsylon3]

yep tx, fixed...

[Amph]

when your IQ will reach 100

which has nothing to do with my question, also your cpu miner has it already

Recently i tried to solo mine few new coming coins..... But not succeded....
Perhaps the new coins based on new forks of bitcoin.... does not have solo mining enabled...as it had been dead for bitcoin.
Always Get Work failed. So i decided to stop trying solo mine....

yeah, new coins usually don't support getwork, getblocktemplate only.
one solution is building your own pool.
but you may find a fork of ccminer with gbt support, I heard nanashi has it.

you mean this? https://github.com/nicehash/ccminer-nanashi/releases

[pallas]

Recently i tried to solo mine few new coming coins..... But not succeded....
Perhaps the new coins based on new forks of bitcoin.... does not have solo mining enabled...as it had been dead for bitcoin.
Always Get Work failed. So i decided to stop trying solo mine....

yeah, new coins usually don't support getwork, getblocktemplate only.
one solution is building your own pool.
but you may find a fork of ccminer with gbt support, I heard nanashi has it.

you mean this? https://github.com/nicehash/ccminer-nanashi/releases

static bool gbt_work_decode_full(const json_t *val, struct work *work)

:-)

[xpulse]

Hi All,

Maybe someone will be able to help with issue ccminer.

CPU AMD Opteron 2356 QC
MB Nvidia

4 Nvidia cards.

Any algo running via ccminer gave me an error Illegal instruction.

Please give me an idea, why this is happened.


Here is screen log:
./ccminer --version
*** ccminer 2.2 for nVidia GPUs by tpruvot@github ***
    Built with the nVidia CUDA Toolkit 8.0 64-bits

  Originally based on Christian Buchner and Christian H. project
  Include some algos from alexis78, djm34, sp, tsiv and klausT.

BTC donation address: 1AJdfCpLWPNoAMDfHF1wD5y8VgKSSTHxPo (tpruvot)

ccminer v2.2
libcurl/7.47.0 OpenSSL/1.0.2g zlib/1.2.8 libidn/1.32 librtmp/2.3


./ccminer -a neoscrypt -o stratum+tcp://neoscrypt.usa.nicehash.com:3341 -u xxx.0 -p x
*** ccminer 2.2 for nVidia GPUs by tpruvot@github ***
    Built with the nVidia CUDA Toolkit 8.0 64-bits

  Originally based on Christian Buchner and Christian H. project
  Include some algos from alexis78, djm34, sp, tsiv and klausT.

BTC donation address: 1AJdfCpLWPNoAMDfHF1wD5y8VgKSSTHxPo (tpruvot)

[2018-02-02 21:54:41] Starting on stratum+tcp://neoscrypt.usa.nicehash.com:3341
[2018-02-02 21:54:41] NVML GPU monitoring enabled.
[2018-02-02 21:54:41] 4 miner threads started, using 'neoscrypt' algorithm.
Illegal instruction

/ccminer -a lyra2v2 -o stratum+tcp://lyra2rev2.usa.nicehash.com:3347 -u xxxxx.0 -p x
*** ccminer 2.2 for nVidia GPUs by tpruvot@github ***
    Built with the nVidia CUDA Toolkit 8.0 64-bits

  Originally based on Christian Buchner and Christian H. project
  Include some algos from alexis78, djm34, sp, tsiv and klausT.

BTC donation address: 1AJdfCpLWPNoAMDfHF1wD5y8VgKSSTHxPo (tpruvot)

[2018-02-02 21:45:27] Starting on stratum+tcp://lyra2rev2.usa.nicehash.com:3347
[2018-02-02 21:45:27] NVML GPU monitoring enabled.
[2018-02-02 21:45:27] 4 miner threads started, using 'lyra2v2' algorithm.
Illegal instruction


Thanks