Search content
Sort by

Showing 20 of 583 results by damNmad
Post
Topic
(Unknown Title)
by
damNmad
on 18/04/2020, 14:47:00 UTC
Joined.

My ETH Address : 0xDb398Dd84734e7B83eE7D047888306ccDf5378a4
Post
Topic
Board Mining (Altcoins)
Re: PhoenixMiner 4.8c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
by
damNmad
on 30/11/2019, 23:15:13 UTC
Can someone suggest best OC settings for GTX 1060 (6GB - Samsung Memory) for Linux, Thanks.

Currently I'm on below settings, getting 23.xx and getting 190 MH for 8 cards, I think I should get 200 MH, I've tried different combinations but haven't found a stable one yet!

Code:
POWERLIMIT_WATTS=76
CORE_OVERCLOCK=100
MEMORY_OVERCLOCK=1300
Post
Topic
Board Mining (Altcoins)
Re: [OS] nvOC Community Release free-easy-to-use Linux Nvidia Mining
by
damNmad
on 20/11/2019, 22:04:07 UTC
ZXC is not included in the default template, you need to add as usual. Look at previous page about BEAM, it's the same with every coin. Everything is documented in the help text in 1bash, you have examples and explanations for each section you need to touch when adding new coins, algos or miners.

In the 1bash file I already had the mtp algorithm added, the xzc coin is indicated as the mtp algorithm coin - xzc, the miner for the mtp algorithm is cryptodredge. 
However, mining does not start. 

For mining beam coin, I added BEAM_OPTS="--ssl 1"
And  - -algo beamhash


what needs to be added for mining xzc?


Please post the details you currently have for MTP and the pool you want to mine it with, I'll try my best to get it sorted.
Post
Topic
Board Mining (Altcoins)
Re: [OS] nvOC Community Release free-easy-to-use Linux Nvidia Mining
by
damNmad
on 07/11/2019, 23:10:15 UTC
Guys, anyone using nicehash? been on wtm switching for too long, wanted to switch to nicehash but mining doesn't start!
Post
Topic
Board Mining (Altcoins)
Re: PhoenixMiner 4.6c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
by
damNmad
on 26/09/2019, 08:03:39 UTC
Hello there,

I'm getting 'Bad -coin value: qkc' error while mining Quark (qkc) coin?

I'm using '-coin qkc'
Post
Topic
Board Announcements (Altcoins)
Re: [ANN][100%POW][SCRYPT] TRINACOIN New Blockchain Project
by
damNmad
on 20/06/2019, 10:40:04 UTC
Sorry, the info were only on subject of topic...

So Trinacoin is a 100% Proof Of Work blockchain, mining algo is Scrypt.

The premine we have is only 50000 trinacoin because when we published on Github someone started to mine it (an Ip unknow to us) so the blocks are mined the most from that entity that is not affiliate to us.

For the future we hope that experts could help us with suggestion for make the project grow! We are open to all suggestions!

Thank you for interest!  Smiley

It would've added more +ve wait if you would've said that 50000 coins were your premine.

But what you said leans more towards the other side.
Post
Topic
Board Mining (Altcoins)
Re: [OS] nvOC Community Release free-easy-to-use Linux Nvidia Mining
by
damNmad
on 20/05/2019, 08:18:56 UTC
Did you try already to run the compiler script via miners upgrade script? Probably this won't make any difference but…

Yes, I have, I tried through it first and then tried independently myself.
Post
Topic
Board Mining (Altcoins)
Re: [OS] nvOC Community Release free-easy-to-use Linux Nvidia Mining
by
damNmad
on 19/05/2019, 20:18:48 UTC
@damnMad hardcoded monero currency can be removed from manifest if you include such a setting in 1bash.template where needed by default (ie for each coin where xmr-stak is selected as miner by default add _XMR_Stak_OPTS="--currency xxx"). Open the two needed PRs for these changes (against 3.2 branch).

Give me some more detail on the compilation failure, maybe better if you open an issue for that on https://github.com/papampi/nvOC_miners

Thanks @LuKePicci, appreciate it.

Yes, you are right, we can add a note in 1bash and ask people to add _XMR_Stak_OPTS="--currency xxx".

I don't think we have any other better miner available for cryptonight coins other than XMR-STAK.

I'll try to apply those two changes in a PR.

Regarding compilation error, this is the error I'm getting!

Code:
m1@m1-desktop:~/NVOC/mining/miners/XMR_Stak/xmr-stak/build$ make install
Scanning dependencies of target xmr-stak-asm
[  2%] Building ASM object CMakeFiles/xmr-stak-asm.dir/xmrstak/backend/cpu/crypto/asm/cryptonight_v8_main_loop.S.o
[  4%] Building ASM object CMakeFiles/xmr-stak-asm.dir/xmrstak/backend/cpu/crypto/asm/cnR/CryptonightR_template.S.o
[  6%] Linking C static library bin/libxmr-stak-asm.a
[  6%] Built target xmr-stak-asm
Scanning dependencies of target xmr-stak-c
[  9%] Building C object CMakeFiles/xmr-stak-c.dir/xmrstak/backend/cpu/crypto/c_skein.c.o
[ 11%] Building C object CMakeFiles/xmr-stak-c.dir/xmrstak/backend/cpu/crypto/c_groestl.c.o
[ 13%] Building C object CMakeFiles/xmr-stak-c.dir/xmrstak/backend/cpu/crypto/c_jh.c.o
[ 15%] Building C object CMakeFiles/xmr-stak-c.dir/xmrstak/backend/cpu/crypto/c_blake256.c.o
[ 18%] Building C object CMakeFiles/xmr-stak-c.dir/xmrstak/backend/cpu/crypto/c_keccak.c.o
[ 20%] Linking C static library bin/libxmr-stak-c.a
[ 20%] Built target xmr-stak-c
Scanning dependencies of target xmr-stak-backend
[ 22%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/version.cpp.o
[ 25%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/jconf.cpp.o
[ 27%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/backend/cpu/cpuType.cpp.o
[ 29%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/backend/cpu/minethd.cpp.o
[ 31%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/backend/cpu/jconf.cpp.o
[ 34%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/backend/cpu/hwlocMemory.cpp.o
[ 36%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/backend/backendConnector.cpp.o
[ 38%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/backend/globalStates.cpp.o
[ 40%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/backend/cpu/crypto/cryptonight_common.cpp.o
[ 43%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/backend/cpu/crypto/cn_gpu_avx.cpp.o
[ 45%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/backend/cpu/crypto/CryptonightR_gen.cpp.o
[ 47%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/backend/cpu/crypto/cn_gpu_ssse3.cpp.o
[ 50%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/http/httpd.cpp.o
[ 52%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/http/webdesign.cpp.o
[ 54%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/misc/utility.cpp.o
[ 56%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/misc/executor.cpp.o
[ 59%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/misc/uac.cpp.o
[ 61%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/misc/telemetry.cpp.o
[ 63%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/misc/console.cpp.o
[ 65%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/net/socket.cpp.o
[ 68%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/net/jpsock.cpp.o
[ 70%] Linking CXX static library bin/libxmr-stak-backend.a
[ 70%] Built target xmr-stak-backend
[ 72%] Building NVCC (Device) object CMakeFiles/xmrstak_cuda_backend.dir/xmrstak/backend/nvidia/nvcc_code/xmrstak_cuda_backend_generated_cuda_extra.cu.o
/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9220): error: argument of type "const void *" is incompatible with parameter of type "const float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9231): error: argument of type "const void *" is incompatible with parameter of type "const float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9244): error: argument of type "const void *" is incompatible with parameter of type "const double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9255): error: argument of type "const void *" is incompatible with parameter of type "const double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9268): error: argument of type "const void *" is incompatible with parameter of type "const float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9279): error: argument of type "const void *" is incompatible with parameter of type "const float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9292): error: argument of type "const void *" is incompatible with parameter of type "const double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9303): error: argument of type "const void *" is incompatible with parameter of type "const double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9316): error: argument of type "const void *" is incompatible with parameter of type "const int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9327): error: argument of type "const void *" is incompatible with parameter of type "const int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9340): error: argument of type "const void *" is incompatible with parameter of type "const long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9352): error: argument of type "const void *" is incompatible with parameter of type "const long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9365): error: argument of type "const void *" is incompatible with parameter of type "const int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9376): error: argument of type "const void *" is incompatible with parameter of type "const int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9389): error: argument of type "const void *" is incompatible with parameter of type "const long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9401): error: argument of type "const void *" is incompatible with parameter of type "const long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9410): error: argument of type "void *" is incompatible with parameter of type "float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9419): error: argument of type "void *" is incompatible with parameter of type "float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9428): error: argument of type "void *" is incompatible with parameter of type "double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9437): error: argument of type "void *" is incompatible with parameter of type "double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9445): error: argument of type "void *" is incompatible with parameter of type "float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9454): error: argument of type "void *" is incompatible with parameter of type "float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9463): error: argument of type "void *" is incompatible with parameter of type "double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9472): error: argument of type "void *" is incompatible with parameter of type "double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9481): error: argument of type "void *" is incompatible with parameter of type "int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9490): error: argument of type "void *" is incompatible with parameter of type "int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9499): error: argument of type "void *" is incompatible with parameter of type "long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9508): error: argument of type "void *" is incompatible with parameter of type "long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9517): error: argument of type "void *" is incompatible with parameter of type "int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9526): error: argument of type "void *" is incompatible with parameter of type "int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9535): error: argument of type "void *" is incompatible with parameter of type "long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h(9544): error: argument of type "void *" is incompatible with parameter of type "long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512pfintrin.h(55): error: argument of type "const void *" is incompatible with parameter of type "const long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512pfintrin.h(63): error: argument of type "const void *" is incompatible with parameter of type "const int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512pfintrin.h(73): error: argument of type "const void *" is incompatible with parameter of type "const long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512pfintrin.h(81): error: argument of type "const void *" is incompatible with parameter of type "const int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512pfintrin.h(91): error: argument of type "void *" is incompatible with parameter of type "const long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512pfintrin.h(100): error: argument of type "void *" is incompatible with parameter of type "const int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512pfintrin.h(109): error: argument of type "void *" is incompatible with parameter of type "const long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512pfintrin.h(117): error: argument of type "void *" is incompatible with parameter of type "const int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512pfintrin.h(127): error: argument of type "void *" is incompatible with parameter of type "const long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512pfintrin.h(136): error: argument of type "void *" is incompatible with parameter of type "const int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512pfintrin.h(145): error: argument of type "void *" is incompatible with parameter of type "const long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512pfintrin.h(153): error: argument of type "void *" is incompatible with parameter of type "const int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(10799): error: argument of type "const void *" is incompatible with parameter of type "const float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(10811): error: argument of type "const void *" is incompatible with parameter of type "const float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(10823): error: argument of type "const void *" is incompatible with parameter of type "const double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(10835): error: argument of type "const void *" is incompatible with parameter of type "const double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(10847): error: argument of type "const void *" is incompatible with parameter of type "const float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(10859): error: argument of type "const void *" is incompatible with parameter of type "const float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(10871): error: argument of type "const void *" is incompatible with parameter of type "const double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(10883): error: argument of type "const void *" is incompatible with parameter of type "const double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(10895): error: argument of type "const void *" is incompatible with parameter of type "const int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(10907): error: argument of type "const void *" is incompatible with parameter of type "const int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(10919): error: argument of type "const void *" is incompatible with parameter of type "const long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(10931): error: argument of type "const void *" is incompatible with parameter of type "const long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(10943): error: argument of type "const void *" is incompatible with parameter of type "const int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(10955): error: argument of type "const void *" is incompatible with parameter of type "const int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(10967): error: argument of type "const void *" is incompatible with parameter of type "const long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(10979): error: argument of type "const void *" is incompatible with parameter of type "const long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(10989): error: argument of type "void *" is incompatible with parameter of type "float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11000): error: argument of type "void *" is incompatible with parameter of type "float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11009): error: argument of type "void *" is incompatible with parameter of type "float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11020): error: argument of type "void *" is incompatible with parameter of type "float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11029): error: argument of type "void *" is incompatible with parameter of type "double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11040): error: argument of type "void *" is incompatible with parameter of type "double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11049): error: argument of type "void *" is incompatible with parameter of type "double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11060): error: argument of type "void *" is incompatible with parameter of type "double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11069): error: argument of type "void *" is incompatible with parameter of type "float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11080): error: argument of type "void *" is incompatible with parameter of type "float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11089): error: argument of type "void *" is incompatible with parameter of type "float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11100): error: argument of type "void *" is incompatible with parameter of type "float *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11109): error: argument of type "void *" is incompatible with parameter of type "double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11120): error: argument of type "void *" is incompatible with parameter of type "double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11129): error: argument of type "void *" is incompatible with parameter of type "double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11140): error: argument of type "void *" is incompatible with parameter of type "double *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11149): error: argument of type "void *" is incompatible with parameter of type "int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11160): error: argument of type "void *" is incompatible with parameter of type "int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11169): error: argument of type "void *" is incompatible with parameter of type "int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11180): error: argument of type "void *" is incompatible with parameter of type "int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11189): error: argument of type "void *" is incompatible with parameter of type "long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11200): error: argument of type "void *" is incompatible with parameter of type "long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11209): error: argument of type "void *" is incompatible with parameter of type "long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11220): error: argument of type "void *" is incompatible with parameter of type "long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11229): error: argument of type "void *" is incompatible with parameter of type "int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11240): error: argument of type "void *" is incompatible with parameter of type "int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11249): error: argument of type "void *" is incompatible with parameter of type "int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11260): error: argument of type "void *" is incompatible with parameter of type "int *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11269): error: argument of type "void *" is incompatible with parameter of type "long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11280): error: argument of type "void *" is incompatible with parameter of type "long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11289): error: argument of type "void *" is incompatible with parameter of type "long long *"

/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512vlintrin.h(11300): error: argument of type "void *" is incompatible with parameter of type "long long *"

92 errors detected in the compilation of "/tmp/tmpxft_000033a8_00000000-14_cuda_extra.compute_70.cpp1.ii".
CMake Error at xmrstak_cuda_backend_generated_cuda_extra.cu.o.cmake:266 (message):
  Error generating file
  /home/m1/NVOC/mining/miners/XMR_Stak/xmr-stak/build/CMakeFiles/xmrstak_cuda_backend.dir/xmrstak/backend/nvidia/nvcc_code/./xmrstak_cuda_backend_generated_cuda_extra.cu.o


CMakeFiles/xmrstak_cuda_backend.dir/build.make:70: recipe for target 'CMakeFiles/xmrstak_cuda_backend.dir/xmrstak/backend/nvidia/nvcc_code/xmrstak_cuda_backend_generated_cuda_extra.cu.o' failed
make[2]: *** [CMakeFiles/xmrstak_cuda_backend.dir/xmrstak/backend/nvidia/nvcc_code/xmrstak_cuda_backend_generated_cuda_extra.cu.o] Error 1
CMakeFiles/Makefile2:143: recipe for target 'CMakeFiles/xmrstak_cuda_backend.dir/all' failed
make[1]: *** [CMakeFiles/xmrstak_cuda_backend.dir/all] Error 2
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2
m1@m1-desktop:~/NVOC/mining/miners/XMR_Stak/xmr-stak/build$

I can raise an issue if you think this is not specific for my rig.

Thanks Smiley
Post
Topic
Board Mining (Altcoins)
Re: [OS] nvOC Community Release free-easy-to-use Linux Nvidia Mining
by
damNmad
on 14/05/2019, 22:18:27 UTC
Do we have a progpow miner on nvoc? Antone tried this yet?

Check the builtin miners list in 1st post.

If none support it let us know the miner for it and we can add it.


Don't think we have that one @papampi

Also, I tried to compile the latest xmr-stak, failing to compile! I've tried to mine sumo coin, not working as expected, when you got a min please look into this


Code:
screen -c /home/m1/NVOC/mining/screenrc-miner -dmSL miner /home/m1/NVOC/mining/miners/XMR_Stak/recommended/xmr-stak.nvoc.sh --config /home/m1/NVOC/mining/miners/XMR_Stak/recommended/config.txt --nvidia /home/m1/NVOC/mining/miners/XMR_Stak/recommended/nvidia.txt --currency cryptonight_r --noCPU -o sumokoin.miner.rocks:4005 -u Sumoo3JbC5Vd2hSngWM6EW8t6ZgpbifSF6QgyQkRbtotH9xpSAX7CPWK1bsbn2kCEzBjYbHZidu9VJt3WTWV458S1iyX82JdD2b.RIGV1932 -p x -r RIGV1932 -i 0
/home/m1/NVOC/mining/miners/XMR_Stak/recommended/xmr-stak.nvoc.sh: 3: /home/m1/NVOC/mining/miners/XMR_Stak/recommended/xmr-stak.nvoc.sh: Bad substitution
/home/m1/NVOC/mining/miners/XMR_Stak/recommended/xmr-stak.nvoc.sh: 6: /home/m1/NVOC/mining/miners/XMR_Stak/recommended/xmr-stak.nvoc.sh: [[: not found
/home/m1/NVOC/mining/miners/XMR_Stak/recommended/xmr-stak.nvoc.sh: 14: /home/m1/NVOC/mining/miners/XMR_Stak/recommended/xmr-stak.nvoc.sh: [[: not found
vm.nr_hugepages = 128
/home/m1/NVOC/mining/miners/XMR_Stak/recommended/xmr-stak.nvoc.sh: 25: /home/m1/NVOC/mining/miners/XMR_Stak/recommended/xmr-stak.nvoc.sh: /home/m1/xmr-stak: not found
   
[WARNING] - Unable to instruct /home/m1/NVOC/mining/miners/XMR_Stak/recommended about which GPUs to enable, it will likely use all of them
screen -c /home/m1/NVOC/mining/screenrc-miner -dmSL miner /home/m1/NVOC/mining/miners/XMR_Stak/recommended/xmr-stak.nvoc.sh --config /home/m1/NVOC/mining/miners/XMR_Stak/recommended/config.txt --nvidia /home/m1/NVOC/mining/miners/XMR_Stak/recommended/nvidia.txt --currency cryptonight_r --noCPU -o sumokoin.miner.rocks:4005 -u Sumoo3JbC5Vd2hSngWM6EW8t6ZgpbifSF6QgyQkRbtotH9xpSAX7CPWK1bsbn2kCEzBjYbHZidu9VJt3WTWV458S1iyX82JdD2b.RIGV1932 -p x -r RIGV1932 -i 0
/home/m1/NVOC/mining/miners/XMR_Stak/recommended/xmr-stak.nvoc.sh: 3: /home/m1/NVOC/mining/miners/XMR_Stak/recommended/xmr-stak.nvoc.sh: Bad substitution
/home/m1/NVOC/mining/miners/XMR_Stak/recommended/xmr-stak.nvoc.sh: 6: /home/m1/NVOC/mining/miners/XMR_Stak/recommended/xmr-stak.nvoc.sh: [[: not found
/home/m1/NVOC/mining/miners/XMR_Stak/recommended/xmr-stak.nvoc.sh: 14: /home/m1/NVOC/mining/miners/XMR_Stak/recommended/xmr-stak.nvoc.sh: [[: not found
vm.nr_hugepages = 128
/home/m1/NVOC/mining/miners/XMR_Stak/recommended/xmr-stak.nvoc.sh: 25: /home/m1/NVOC/mining/miners/XMR_Stak/recommended/xmr-stak.nvoc.sh: /home/m1/xmr-stak: not found

It is failing to find/generate the nvidia.txt file
The json needs tweaking as the default coin is hard coded as monero, it should be a variable (user should be able to select coins from the below list)


Supported coin options:
   - aeon7
   - bbscoin
   - bittube
   - cryptonight
   - cryptonight_bittube2
   - cryptonight_masari
   - cryptonight_haven
   - cryptonight_heavy
   - cryptonight_lite
   - cryptonight_lite_v7
   - cryptonight_lite_v7_xor
   - cryptonight_r
   - cryptonight_superfast
   - cryptonight_turtle
   - cryptonight_v7
   - cryptonight_v8
   - cryptonight_v8_double
   - cryptonight_v8_half
   - cryptonight_v8_reversewaltz
   - cryptonight_v8_zelerius
   - cryptonight_v7_stellite
   - cryptonight_gpu
   - cryptonight_conceal
   - freehaven
   - graft
   - haven
   - lethean
   - masari
   - monero
   - qrl
   - ryo
   - stellite
   - turtlecoin
   - plenteum
   - zelerius
   - xcash


Please let me know if you need any further information.
Post
Topic
Board Mining (Altcoins)
Merits 1 from 1 user
Re: [OS] nvOC Community Release free-easy-to-use Linux Nvidia Mining
by
damNmad
on 03/05/2019, 10:25:47 UTC
⭐ Merited by papampi (1)
Post
Topic
Board Mining (Altcoins)
Re: GPU mining will die in 2018!
by
damNmad
on 22/03/2018, 21:30:30 UTC
I think this defeats the whole purpose of the decentralized coin idea and it will not be allowed to die.

I think the future of crypto currency is in the coins that are ASIC resistant or for coins that strive to be ASIC resistant, like someone was saying BTG is trying to avoid ASICs as much as possible.

I think everyone is aware of the fact that the BTC network has become very congested (transactions are being processed very slow) thus sellers are starting to keep away from it.

I mean even the bitcoin conference did not accept btc as a form of payment. That tell us something right?

There are plenty of ASIC resistant coins to mine profitably with your GPUs.

ASIC devices will just be a part of the mining market. Most of miners are using GPU rigs, because if you're bored with mining, you can just sell your GPUs for gamers.

A bunch of ASIC devices is already obsolete, nobody wants it and it's not profitable anymore.
Post
Topic
Board Mining (Altcoins)
Re: [OS] nvOC easy-to-use Linux Nvidia Mining vBASIC || Community Edition 2.0
by
damNmad
on 19/03/2018, 19:43:52 UTC
Have anyone here mining raven coin yet. I wondering if it possible to run cc miner on nvoc.

Yes we have already added instructions for adding RAVEN coin and getting the ccminer for it, it uses MSFT ccminer.

You can get most of the ccminers available in the market on nvOC, if there isn't one on the list we will provide instructions how to get it and how to build it as well.

See the below post which explains more in detail;

https://bitcointalk.org/index.php?topic=1854250.msg31430936#msg31430936





Where can I find instruction on how to add raven coin on nvoc 19.2 and get msftccminer


You can find instructions here for most of the new coins bruv.

https://github.com/damNmad/nvOC_testing_repo/tree/damNmad

I add them almost instantly (haven't found good coins recently) if I find the good ones, and also based on request as well.


To get the MSFTccminer, use papampi's instructions from here

https://bitcointalk.org/index.php?topic=1854250.msg29774627#msg29774627

You can almost get every miner from the above posted instructions and compile it on your RIG.

Let us know if you need any help.
Post
Topic
Board Mining (Altcoins)
Re: Baikal Giant N - Cryptonight, Cryptonight-lite FPGA/ASIC miner
by
damNmad
on 14/03/2018, 22:41:29 UTC
This is total RIPOFF for all the GPU miners, these money mongers will do anything they possibly can to make the cryptos centralised.

Cryptonight is the only algo many small miners, like a PC holders are able to mine it, but these guys already made ASICS out of them, their agenda is simple, make rich richer.
Post
Topic
Board Mining (Altcoins)
Re: [OS] nvOC easy-to-use Linux Nvidia Mining vBASIC || Community Edition 2.0
by
damNmad
on 14/03/2018, 21:34:30 UTC
Have anyone here mining raven coin yet. I wondering if it possible to run cc miner on nvoc.

Yes we have already added instructions for adding RAVEN coin and getting the ccminer for it, it uses MSFT ccminer.

You can get most of the ccminers available in the market on nvOC, if there isn't one on the list we will provide instructions how to get it and how to build it as well.

See the below post which explains more in detail;

https://bitcointalk.org/index.php?topic=1854250.msg31430936#msg31430936



Post
Topic
Board Mining (Altcoins)
Re: [OS] nvOC easy-to-use Linux Nvidia Mining vBASIC || Community Edition 2.0
by
damNmad
on 07/03/2018, 11:20:36 UTC

I didn't any change in 1bash just change coin to dual_eth_dcr   other code in 1bash is from nvoc 19. I made worker in dcr.suprnova.cc  with user and pass i think should set my password from worker i made in pool to 1bash!

Ok, I know that you haven't changed a thing in 1bash.

We've been on version 19 from past 8 months, we had 6 sub versions under 19, I don't know which version you using.

NOPE!

Setting your password doesn't just let you mine, I would suggest you to set your worker password to 'x' on suprnova dashboard. (no one can access your coins with this password, keep the actual login password safe)

I need two things from you, to help you further...

1) I've asked you to paste the DCR details from 1bash because, i want to know how you set it up, need to correct them if there is any mistake.

2) I don't know which sub version you are using, so

a. I would suggest you to look for 0miner file in home folder, if you can find it then search for 'DUAL_ETH_DCR' and paste that code over here.
b. If you unable to find 0miner file, then look for 3main file and search for the same 'DUAL_ETH_DCR' and get those lines here.

I can help you in minutes once I have the above information.

PS : Every pool uses different approach, account based and address based are different.



thanks for your help
search for 0miner but i cant find it.i found 3main and this  code
Code:
if [ $COIN == "DUAL_ETH_DCR" ]
then

if [ $CLAYMORE_VERSION == "9_8" ]
then
HCD='/home/m1/eth/9_8/ethdcrminer64'
fi

if [ $CLAYMORE_VERSION == "9_7" ]
then
HCD='/home/m1/eth/9_7/ethdcrminer64'
fi

if [ $CLAYMORE_VERSION == "9_5" ]
then
HCD='/home/m1/eth/9_5/ethdcrminer64'
fi

if [ $CLAYMORE_VERSION == "9_4" ]
then
HCD='/home/m1/eth/9_4/ethdcrminer64'
fi

if [ $CLAYMORE_VERSION == "8_0" ]
then
HCD='/home/m1/eth/8_0/ethdcrminer64'
fi

ETHADDR="$ETH_ADDRESS/$ETH_WORKER"

if [ $DOT_POOL_FORMAT_or_FORWARD_SLASH_POOL_FORMAT == "DOT" ]
then
ETHADDR="$ETH_ADDRESS.$ETH_WORKER"
fi

DADDR="$DCR_ADDRESS.$DCR_WORKER"

screen -dmS miner $HCD -epool $ETH_POOL -ewal $ETHADDR -epsw x -dpool $DCR_POOL -dwal $DADDR -dpsw x -dbg -1 $ETH_EXTENSION_ARGUMENTS


if [ $LOCALorREMOTE == "LOCAL" ]
then
screen -r miner
fi

BITCOIN="theGROUND"

while [ $BITCOIN == "theGROUND" ]
do
sleep 60
done
fi




Thanks bruv, you should've posted the DCR coin details from 1bash as well, anyway, by looking at the above code seems normal to me, so i will post the solutions below.

Not sure what sort of pool you are using for ETH, but if it is account based pool like suprnova then, check/change the below option

Quote
$DOT_POOL_FORMAT_or_FORWARD_SLASH_POOL_FORMAT == "DOT"

Add the extension arguments and make sure about the format;
Quote
ETH_WORKER="workerName"
ETH_ADDRESS="loginName"
ETH_POOL="poolAddress"
ETH_EXTENSION_ARGUMENTS="-allpools 1"    # add any additional claymore arguments desired here

If you are using non account based pools like nanopool or dwarfpool then don't touch change the below variable :

Quote
$DOT_POOL_FORMAT_or_FORWARD_SLASH_POOL_FORMAT

Add the extension arguments and make sure about the format;
Quote
ETH_WORKER=$WORKERNAME
ETH_ADDRESS="yourWalletAddress"
ETH_POOL="poolAddress"
ETH_EXTENSION_ARGUMENTS="-allpools 1"    # add any additional claymore arguments desired here

Must change the DCR settings according to the below format, if you are dual mining.
Quote
DCR_WORKER="workerName"
DCR_ADDRESS="joviSupra"
DCR_POOL="dcr.suprnova.cc:3252" (guess this is what you are using??)

Try the above options and let me know how it goes, if you still see authentication error, just go to guake

Code:
ps aux | grep miner

type this and pass the result to me; i will try to help you based on that.

Post
Topic
Board Mining (Altcoins)
Re: [OS] nvOC easy-to-use Linux Nvidia Mining vBASIC || Community Edition 2.0
by
damNmad
on 06/03/2018, 22:37:32 UTC
hi
I am a beginner in mining.I start mining with nvOC. now I want to change my payout in nanopool setting but can't change it because I haven't password. how can I set a password for my workers in onebash file??



Hello there,

Welcome to nvOC.

What coin you mining? The easy and best way is to append your email to worker, password is always 'x' i think.

To achieve that, append your worker name;

for eg; If you are mining ETH then, get your current worker name from nanopool (you must have the exact name to amend the payout)

In 1bash fine this variable & change this (please hard code the worker name & email - don't use variables)

Quote
ETH_WORKER="workerNameFromNanoPool/youremail@mail.com"

It takes some time for pool to append these changes, any questions please let us know.

Thank U my friend
change it in eth and wating for pool to append changes.
I have another question  When i running dual mining eth+dcr, miner shows this error>>>  dcr : authorization failed : (null). What should I do!?

Hope you will be able to change payout soon.

It means your DCR login isn't getting accepted by pool, paste your DCR coin details from 1bash and ETH_DCR details from 0miner here.

I will rectify them according to your needs and paste them back.



I didn't any change in 1bash just change coin to dual_eth_dcr   other code in 1bash is from nvoc 19. I made worker in dcr.suprnova.cc  with user and pass i think should set my password from worker i made in pool to 1bash!

Ok, I know that you haven't changed a thing in 1bash.

We've been on version 19 from past 8 months, we had 6 sub versions under 19, I don't know which version you using.

NOPE!

Setting your password doesn't just let you mine, I would suggest you to set your worker password to 'x' on suprnova dashboard. (no one can access your coins with this password, keep the actual login password safe)

I need two things from you, to help you further...

1) I've asked you to paste the DCR details from 1bash because, i want to know how you set it up, need to correct them if there is any mistake.

2) I don't know which sub version you are using, so

a. I would suggest you to look for 0miner file in home folder, if you can find it then search for 'DUAL_ETH_DCR' and paste that code over here.
b. If you unable to find 0miner file, then look for 3main file and search for the same 'DUAL_ETH_DCR' and get those lines here.

I can help you in minutes once I have the above information.

PS : Every pool uses different approach, account based and address based are different.

Post
Topic
Board Mining (Altcoins)
Re: [OS] nvOC easy-to-use Linux Nvidia Mining vBASIC || Community Edition 2.0
by
damNmad
on 06/03/2018, 21:09:48 UTC
hi
I am a beginner in mining.I start mining with nvOC. now I want to change my payout in nanopool setting but can't change it because I haven't password. how can I set a password for my workers in onebash file??



Hello there,

Welcome to nvOC.

What coin you mining? The easy and best way is to append your email to worker, password is always 'x' i think.

To achieve that, append your worker name;

for eg; If you are mining ETH then, get your current worker name from nanopool (you must have the exact name to amend the payout)

In 1bash fine this variable & change this (please hard code the worker name & email - don't use variables)

Quote
ETH_WORKER="workerNameFromNanoPool/youremail@mail.com"

It takes some time for pool to append these changes, any questions please let us know.

Thank U my friend
change it in eth and wating for pool to append changes.
I have another question  When i running dual mining eth+dcr, miner shows this error>>>  dcr : authorization failed : (null). What should I do!?

Hope you will be able to change payout soon.

It means your DCR login isn't getting accepted by pool, paste your DCR coin details from 1bash and ETH_DCR details from 0miner here.

I will rectify them according to your needs and paste them back.

Post
Topic
Board Mining (Altcoins)
Re: [OS] nvOC easy-to-use Linux Nvidia Mining vBASIC || Community Edition 2.0
by
damNmad
on 06/03/2018, 15:31:52 UTC
hi
I am a beginner in mining.I start mining with nvOC. now I want to change my payout in nanopool setting but can't change it because I haven't password. how can I set a password for my workers in onebash file??



Hello there,

Welcome to nvOC.

What coin you mining? The easy and best way is to append your email to worker, password is always 'x' i think.

To achieve that, append your worker name;

for eg; If you are mining ETH then, get your current worker name from nanopool (you must have the exact name to amend the payout)

In 1bash fine this variable & change this (please hard code the worker name & email - don't use variables)

Quote
ETH_WORKER="workerNameFromNanoPool/youremail@mail.com"

It takes some time for pool to append these changes, any questions please let us know.
Post
Topic
Board Mining (Altcoins)
Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0019-1.4
by
damNmad
on 04/03/2018, 13:00:22 UTC

Thank you damNmad that did the trick.  Cheesy

It is that simple that i feel kind of embarassed. Should have found it myself. But i do have a question following this.

All my rigs are running again with var diff (cpu and gpu´s) under nvOC 2.0 after eliminating the worker address from 0main and 3main but these rigs did work under nvOC 19 1.4 so you guys put that code into the two files for the community release. But right after updating from 1.4 to 2.0  i tried several etn mining pools and got the same result everytime. So for mining etn should the worker address stay in 0main and 3main?

In other words am i the only one experiencing this mistake while mining etn or is it a mistake that the worker address is added in 0main and 3main for etn mining?

Your user name resembles fullzero (it should be halfzero instead of hallzero Cheesy ).

Yeah, these are very minor things, but they are easy for me because of my experience.

Coming to your question, its hard to create a single template covering/satisfying/working all the pools and coins, but we tried to cover most of the scenarios (not sure its 100% legit but at least I can find the bug quickly by comparing).

So, in 1.4 version all the all the mining code used to be in 3main, but from 2.0 version it has been split between 0miner and 3main.

0miner covers all the coins, where as 3main covers overclocking (not 100% sure), CPU mining, all the coin/algo switching code.

Its not just you, it was like that in the release, has been fixed in the upcoming release.

Yes i am sorry for the username, hope nobody is offended. I joined the forum as a newbie to cryptos before i found out about nvOC so i didn´t know. But then again it should not be halfzero but instead zerozero so that we would have fullzero as the legendary knowledgeable creator and me as the total newbie.

As for the question, so i thought i did ask just for understanding. For etn mining we could add the workername by using a "+" instead of the "."

That works using the cryptonight pools on etn but i do not know whether that works with other coins out there, my rigs are too small, so i am just mining two coins


Hahaha don't be sorry bruv, I don't think any one will get offended by your name, i was just expressing it in a funny way Smiley

Yep, you only asked for explanation, but I have answered in general perspective.

Quote
For etn mining we could add the workername by using a "+" instead of the "."

Can you please give an example, illustrating the above statement, sorry i didn't quite get that to be honest.

So, this as well just a general explanation (not just for you but for any new miners to understand) of how actually 1bash, 0miner or 3main works.

We add all the coin details and they are stored/attached to variables.

We call those variables in 3main or 0miner and shape them up according to how pool expects.

We follow the same procedure for every single coin.

Feel free to ask any further questions you have.
Post
Topic
Board Mining (Altcoins)
Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0019-1.4
by
damNmad
on 02/03/2018, 22:01:50 UTC

Thank you damNmad that did the trick.  Cheesy

It is that simple that i feel kind of embarassed. Should have found it myself. But i do have a question following this.

All my rigs are running again with var diff (cpu and gpu´s) under nvOC 2.0 after eliminating the worker address from 0main and 3main but these rigs did work under nvOC 19 1.4 so you guys put that code into the two files for the community release. But right after updating from 1.4 to 2.0  i tried several etn mining pools and got the same result everytime. So for mining etn should the worker address stay in 0main and 3main?

In other words am i the only one experiencing this mistake while mining etn or is it a mistake that the worker address is added in 0main and 3main for etn mining?

Your user name resembles fullzero (it should be halfzero instead of hallzero Cheesy ).

Yeah, these are very minor things, but they are easy for me because of my experience.

Coming to your question, its hard to create a single template covering/satisfying/working all the pools and coins, but we tried to cover most of the scenarios (not sure its 100% legit but at least I can find the bug quickly by comparing).

So, in 1.4 version all the all the mining code used to be in 3main, but from 2.0 version it has been split between 0miner and 3main.

0miner covers all the coins, where as 3main covers overclocking (not 100% sure), CPU mining, all the coin/algo switching code.

Its not just you, it was like that in the release, has been fixed in the upcoming release.