Pages:
Author

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

full member
Activity: 178
Merit: 102
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
legendary
Activity: 3248
Merit: 1070
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
legendary
Activity: 1797
Merit: 1028
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
member
Activity: 99
Merit: 10
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.
copper member
Activity: 20
Merit: 0
Hello,

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

legendary
Activity: 1797
Merit: 1028
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
legendary
Activity: 2716
Merit: 1094
Black Belt Developer
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?
newbie
Activity: 1
Merit: 0
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
legendary
Activity: 2716
Merit: 1094
Black Belt Developer
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
newbie
Activity: 25
Merit: 0
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?
newbie
Activity: 1
Merit: 0
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...
newbie
Activity: 4
Merit: 0
I am on macOS and I tried following the instructions on https://github.com/tpruvot/ccminer/blob/linux/INSTALL. However, I got the following error when I run  ./build.sh. Does anyone know how to fix this?
Code:
make: *** No rule to make target `distclean'.  Stop.
clean
checking build system type... x86_64-apple-darwin17.3.0
checking host system type... x86_64-apple-darwin17.3.0
checking target system type... x86_64-apple-darwin17.3.0
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... ./install-sh -c -d
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... gcc3
checking for gcc option to accept ISO C99... none needed
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking whether gcc needs -traditional... no
checking dependency style of gcc... gcc3
checking for ranlib... ranlib
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking for gcc option to support OpenMP... unsupported
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking sys/endian.h usability... no
checking sys/endian.h presence... no
checking for sys/endian.h... no
checking sys/param.h usability... yes
checking sys/param.h presence... yes
checking for sys/param.h... yes
checking syslog.h usability... yes
checking syslog.h presence... yes
checking for syslog.h... yes
checking for sys/sysctl.h... yes
checking whether be32dec is declared... no
checking whether le32dec is declared... no
checking whether be32enc is declared... no
checking whether le32enc is declared... no
checking for size_t... yes
checking for working alloca.h... yes
checking for alloca... yes
checking for getopt_long... yes
checking for json_loads in -ljansson... no
checking for pthread_create in -lpthread... yes
checking for gzopen in -lz... yes
checking for SSL_free in -lssl... yes
checking for EVP_DigestFinal_ex in -lcrypto... yes
[b]./configure: line 6165: syntax error near unexpected token `,'
./configure: line 6165: `LIBCURL_CHECK_CONFIG(, 7.15.2, ,'[/b]
make: *** No targets specified and no makefile found.  Stop.
newbie
Activity: 1
Merit: 0
Did anybody get ccminer working with Nvidia Tesla GPUs?

I tried it with a Tesla K80/M60? Whenever I try, it usually says what the latest block is but no mining activity.


Hey,

I do,
PM me your email if you need help.
newbie
Activity: 14
Merit: 0
Did anybody get ccminer working with Nvidia Tesla GPUs?

I tried it with a Tesla K80/M60? Whenever I try, it usually says what the latest block is but no mining activity.


I am not a expert but think your Tesla is to strong for the settings in or not compatible with mining. Try with high options bat file. dont ask me what to do. you card is just to high performance need to make high setting for your card. or it would not work properly. good luck


forget what i said before. Use ccminer cuda 9.0 hope that wil help
newbie
Activity: 14
Merit: 0
http://yiimp.eu Is offline

its up again. I think they are hacked again.  Sad

hope I didnt lose my coins
legendary
Activity: 1797
Merit: 1028
http://yiimp.eu Is offline

STILL DOWN--

What is up?       --scryptr
full member
Activity: 243
Merit: 105
newbie
Activity: 14
Merit: 0
I'm getting 100% CPU utilization when using ccminer and mining Garlicoin...This is killing my hashrates on my 5 GTX 1070 Ti rig. (CPU: Intel G3920)


Is there a fix for this?

any update on this? seeing the same thing with 4x1070Ti's

Nothing major, but adding this helped a little: --lookup-gap=2 --cpu-affinity=o


Still doesn't explain why ccminer is pinning the CPU at 100%

Even my 7700K struggles with it...ccminer was pinning the i7 at over 80%

Again and I'm sorry, but this is probably the worst performing miner I've come across and this has been pretty much the response from this forum "lol meme coin  ¯\_(ツ)_/¯ "

Same problem here guys...garlic is goood, but so consumption of CPU is killing me. Something better in .conf of ccminer setting 0 cpu intensity


Yeah, this forum appears to be dead. Neither --cpu-affinity nor --cpu-priority fix this issue. I'm willing to give some Garlicoin to anybody who has a workaround and/or finds another miner that will work with mining Garlicoin.

The process was using 60% of my I7700k,  I set the CPU-Priority to 0 and backed down on my OC & CPU voltage down and now it's using, a still unreasonable, 34%, but at-least it's not running hot.
newbie
Activity: 16
Merit: 0
I tried mining bitcore on my rigs and I'm getting "Cuda error in func 'cuda_check_cpu_setTarget' at line 41" on GTX 1080Ti Palit rigs. It happens on 1080Ti Palit Super JetStream and 1080Ti Palit GameRock. It mines for like 5 minutes then this error appear and crash miner. How to fix this problem?

Here is screenshot of miner https://i.imgur.com/gaxpFuK.png
newbie
Activity: 16
Merit: 0
I'm getting 100% CPU utilization when using ccminer and mining Garlicoin...This is killing my hashrates on my 5 GTX 1070 Ti rig. (CPU: Intel G3920)


Is there a fix for this?

any update on this? seeing the same thing with 4x1070Ti's

Nothing major, but adding this helped a little: --lookup-gap=2 --cpu-affinity=o


Still doesn't explain why ccminer is pinning the CPU at 100%

Even my 7700K struggles with it...ccminer was pinning the i7 at over 80%

Again and I'm sorry, but this is probably the worst performing miner I've come across and this has been pretty much the response from this forum "lol meme coin  ¯\_(ツ)_/¯ "

Same problem here guys...garlic is goood, but so consumption of CPU is killing me. Something better in .conf of ccminer setting 0 cpu intensity


Yeah, this forum appears to be dead. Neither --cpu-affinity nor --cpu-priority fix this issue. I'm willing to give some Garlicoin to anybody who has a workaround and/or finds another miner that will work with mining Garlicoin.
Pages:
Jump to: