BitShares Forum
Other => Graveyard => MemoryCoin => Topic started by: alexxy on December 24, 2013, 04:12:48 am
-
Hi all!
I'm releasing sources for minerd based cpuminer. Its not fully optimized but it at least suitable for solo mine. Also it will work with any getwork based pools.
Sources available cpuminer (https://github.com/alexxy/cpuminer)
64bit linux here (https://drive.google.com/file/d/0B3MNiK86m0F9aEh2dHFmeHlkWWs/edit?usp=sharing)
-
Hi all!
I'm releasing sources for minerd based cpuminer. Its not fully optimized but it at least suitable for solo mine. Also it will work with any getwork based pools.
Sources available https://github.com/alexxy/cpuminer (https://github.com/alexxy/cpuminer)
Upload binary please.
-
I can upload binary for 64bit linux only
-
I've work with Minerd too for my Pool.
Congratulations for your code :)
FaSan
-
Sorry, I have a missing dependency.. ?
Running Debian
uname -r
3.2.0-4-amd64
./minerd: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by ./minerd)
-
Nice one, but doing one hash per thread instead of splitting the job between threads is asking for orphans..
-
Nice one, but doing one hash per thread instead of splitting the job between threads is asking for orphans..
It will increase probability to find block btw.
-
Sorry, I have a missing dependency.. ?
Running Debian
uname -r
3.2.0-4-amd64
./minerd: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by ./minerd)
If you're on linux then its better to build it from source. I have more recent glibc on my laptop
-
Nice one, but doing one hash per thread instead of splitting the job between threads is asking for orphans..
I think there is probably a happy medium between all the threads working on one hash (stock) and one thread per hash.
Working two hashes at a time, with half the threads in each would probably maximise the hash rate with a low orphan rate. Maybe 4 hashes for very powerful comps.
-
Hi all!
I'm releasing sources for minerd based cpuminer. Its not fully optimized but it at least suitable for solo mine. Also it will work with any getwork based pools.
Sources available cpuminer (https://github.com/alexxy/cpuminer)
64bit linux here (https://drive.google.com/file/d/0B3MNiK86m0F9aEh2dHFmeHlkWWs/edit?usp=sharing)
Thanks for this. Will try a windows compile later.
-
How to use it for solo mining?
-
I can`t compile from source.
mv -f .deps/minerd-momentum.Tpo .deps/minerd-momentum.Po
g++ -g -O2 -pthread -o minerd minerd-cpu-miner.o minerd-util.o minerd-momentum.o -L/usr/lib/x86_64-linux-gnu -lcurl -ljansson -lpthread
/usr/bin/ld: minerd-momentum.o: undefined reference to symbol 'SHA512@@OPENSSL_1.0.0'
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0: error adding symbols: DSO missing from command line
collect2: error: ld returned 1 exit status
make[2]: *** [minerd] Error 1
make[2]: Leaving directory `/home/ubuntu/mmcminer'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/ubuntu/mmcminer'
make: *** [all] Error 2
-
How to use it for solo mining?
This is a really good question ! Does anybody knows how to do it ?
-
to compile miner you need ssl library
in makefile.am change
minerd_LDADD = @LIBCURL@ @JANSSON_LIBS@ @PTHREAD_LIBS@to
minerd_LDADD = @LIBCURL@ @JANSSON_LIBS@ @PTHREAD_LIBS@ -lssl -lcrypto
-
to compile miner you need ssl library
in makefile.am change
minerd_LDADD = @LIBCURL@ @JANSSON_LIBS@ @PTHREAD_LIBS@to
minerd_LDADD = @LIBCURL@ @JANSSON_LIBS@ @PTHREAD_LIBS@ -lssl -lcrypto
hey, i wonder, does it help anything to increase memory usage?
-
to compile miner you need ssl library
in makefile.am change
minerd_LDADD = @LIBCURL@ @JANSSON_LIBS@ @PTHREAD_LIBS@to
minerd_LDADD = @LIBCURL@ @JANSSON_LIBS@ @PTHREAD_LIBS@ -lssl -lcrypto
hey, i wonder, does it help anything to increase memory usage?
If you mean - adding RAM to the system or closing other applications, then yes, it will decrease paging out of data miner needs to access. Turning off swap in Linux or setting a very low swappiness would help achieve that too.