Hello, when I use this command: "-R E:\Crypto\DagETH", the CPU load is 50%. When I remove it, it's 0,5%. The problem is that my drive C is almost full and I want to change the DAG folder in drive E, but this 50% CPU load is a big problem.  What CPU are you using? AMD Phenom II X2 560 @ 3.6GHz. Yeah, very low-end dual core CPU, that makes sense. I'm afraid you'll need a more capable CPU to accommodate the miner. |
|
|
|
Hello, when I use this command: "-R E:\Crypto\DagETH", the CPU load is 50%. When I remove it, it's 0,5%. The problem is that my drive C is almost full and I want to change the DAG folder in drive E, but this 50% CPU load is a big problem. What CPU are you using? |
|
|
|
I can build this to work on linux? Any instructions on how to do this anywhere? Thanks in advance  I'm working on a new README.md. Almost there. For now, check out he knowledge base on ethpool. It has build instructions for my miner. I finally got DAG chunking working today. Not that it's really required now that the right AMD environment vars have been found. If there happens to be demand for it anyway, please let me know so I can implement it in a clean way that doesn't hurt the non-chunked version. Because on AMD chunking does negatively affect performance. Hey Genoil, I have a 5770 I could do some testing on with your "chunked" version. Did you make a new fork? Or is it in the 107 branch? thx AMD 5770 has at most 1GB memory. So it will not work to mine Ethereum, even with the "chunked" version. Ah - I misunderstood what he meant by "chunked". There was an effort some time ago to allow 1GB cards to use a "streamed" DAG - at least I can only assume that's how one would do it. Thanks for the info. Some 5770's have 2GB of RAM per core, I don't have one of those. I have the std 2 core 1GB per core. |
|
|
|
I can build this to work on linux? Any instructions on how to do this anywhere? Thanks in advance I'm working on a new README.md. Almost there. For now, check out he knowledge base on ethpool. It has build instructions for my miner. I finally got DAG chunking working today. Not that it's really required now that the right AMD environment vars have been found. If there happens to be demand for it anyway, please let me know so I can implement it in a clean way that doesn't hurt the non-chunked version. Because on AMD chunking does negatively affect performance. Hey Genoil, I have a 5770 I could do some testing on with your "chunked" version. Did you make a new fork? Or is it in the 107 branch? thx |
|
|
|
look at Genoil's first post in this thread, FAQ #1
Edit: if you're already using the old drivers, verify it is NOT using WDDM 2.0
if it is on the old WDDM, then just give up and put the cards into a spare Win7 box (is what I would do - some things are not worth the effort fighting with)
Speaking of fighting with something - I've managed to get this far building it on Ubuntu Xenial:
- built the miner only without setting -DBUNDLE to cudaminer
- tried running cmake again with -DBUNDLE=cudaminer
got this far:
[ 35%] Building NVCC (Device) object libethash-cuda/CMakeFiles/ethash-cuda.dir/ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o
nvcc fatal : redefinition of argument 'std'
CMake Error at ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o.cmake:207 (message):
Error generating
/home/pcchip/try2/cpp-ethereum/build/libethash-cuda/CMakeFiles/ethash-cuda.dir//./ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o
libethash-cuda/CMakeFiles/ethash-cuda.dir/build.make:63: recipe for target 'libethash-cuda/CMakeFiles/ethash-cuda.dir/ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o' failed
make[2]: *** [libethash-cuda/CMakeFiles/ethash-cuda.dir/ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o] Error 1
CMakeFiles/Makefile2:320: recipe for target 'libethash-cuda/CMakeFiles/ethash-cuda.dir/all' failed
make[1]: *** [libethash-cuda/CMakeFiles/ethash-cuda.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
Maybe I should take my own advice and switch it to a Win7 box ?
Ok - the error ways "mvcc fatal : redefinition of the argument 'std' SO, let's change that - **make your change (removing --std) to libethash-cuda/CMakeFiles/ethash-cuda.dir/ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o.cmake set(nvcc_flags -m64; --std;c++11;-DETH_JSONRPC;-DETH_READLINE;-DETH_MINIUPNPC;-DETH_ETHASHCL;-DETH_ETHASHCUDA;-DETH_STRATUM;-DETH_CURL;-DETH_FRONTIER;-DETH_TRUE) # list Delete the "--std" and try your build again. |
|
|
|
there is a great downwards trend in altcoin prices this days
very good for DMD Diamond each time in the past we did came out after this in a better position
because stability in uncertain times always is more visible and attractive to people
A downward trend is a downward trend - no coin will be immune as they are all tied to BitCoin for movement to spendable currency. If DMD were accepted by say NewEgg or other retailers, what your stating would have more weight. As people divest from crypto to "real" currency, the market prices will suffer. It's my opinion that is happening at this time - people are taking profits. |
|
|
|
>>> Round #15 (0.14$ or 33600 satoshi): sold 9,103 out of 100,000 <<<
I think it is weird that people buy the coins for 14 cents when you can but it on the exchange for just 1/10 of that. Are those people to lazy to transfer money to c-cex?  if u buy direct from the company u can sell it back for the same price u bought. if u buy at exchange u can sell it only at the exchange. thats the reason why some people buy direct from company. Is ist worth to pay 10 times more? I dont't think so. At the current rates, I suppose most sales of AMBER are happening in "real" money. AmberDev has hinted to this in previous posts. This implies outside influence on dividends that will likely impact payouts for shares not purchased directly from AmberTrade. Keep in mind, they can change the rules AT ANY TIME for investors not purchasing directly from AmberTrade. 10,000 coins? They may decide the minimum balance required for dividend payouts should be 20,000. Something like this will happen soon, the model of increasing available "stock" is unsustainable. What the Crypto markets need is a trading mechanism that allows for "shorting" coins. This may help to weed-out smaller valued coins, but, make it harder to start a "shit coin". |
|
|
|
Like Genoil says, the rate reporting isn't very sophisticated - so it skips around like mad.
One thing that's puzzling to me it the need for the DAG to reside in GPU memory.
I suppose accessing it via the PCI bus (in system RAM) would be slower, but, would all for 1GB cards to mine.
What do you think?
The whole point of ethash is RAM latency. Lower latency = faster mining. If you keep the DAG in system RAM, you might as well access it with the CPU. ethminer -C  Or sure, DDR5 GPU RAM is optimal - but, have you tried it? I'm planning on it, when I have a spare day or two. Any GPU is much better suited for mining than a CPU, of which I'm sure you are aware. With ethash, it doesn't look like there will be any kernel optimizations or "revelations". What I'm saying is that 1GB GPUs could likely mine much faster than a CPU. Of course, proof is in the pudding. A good rule of thumb for determining a card's hashrate is 80% * bandwidth / 8KB. 8KB is the amount of data that is retrieved from the DAG for each hash. 80% is the average effciency I've found to be common. i.e. 280X = 0.8*224GB/8KB = 22.4MH/s GTX970 = 0.8*196GB/8KB = 19.6MH/s Now you take the max PCIE 3.0 bandwidth (x16), which is about 16GB/s. This should give you a theoretical hashrate of about 1.6MH/s. In practise it's much worse though. I only had to change 2 lines of code in my CUDA miner to keep the DAG in device mapped system RAM. The hashrate of my GTX970 dropped to about 300KH/s. My i5-4570 CPU does about 400KH/s. This formula does not work with GTX 980 Ti with a hashrate a little above GTX 970 and bandwith of 313Gb/s Yeah, that is brutal. Nice work on testing, saved me the "told you so" from Genoil |
|
|
|
Like Genoil says, the rate reporting isn't very sophisticated - so it skips around like mad.
One thing that's puzzling to me it the need for the DAG to reside in GPU memory.
I suppose accessing it via the PCI bus (in system RAM) would be slower, but, would all for 1GB cards to mine.
What do you think?
The whole point of ethash is RAM latency. Lower latency = faster mining. If you keep the DAG in system RAM, you might as well access it with the CPU. ethminer -C Or sure, DDR5 GPU RAM is optimal - but, have you tried it? I'm planning on it, when I have a spare day or two. Any GPU is much better suited for mining than a CPU, of which I'm sure you are aware. With ethash, it doesn't look like there will be any kernel optimizations or "revelations". What I'm saying is that 1GB GPUs could likely mine much faster than a CPU. Of course, proof is in the pudding. |
|
|
|
guys is normal this result? i'am trying to mine with 7950 setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
ethminer -G -F http://127.0.0.1:8080/rig1 --cl-local-work 128 --cl-global-work 8192 I' am new on ETH, the real hashrate are first or second figure? Thanks Hi Wolf, your hash rate is a normal for 7950, do not use recheck 200 for mining without proxy, 400 is a optimal. Miner hash rate is digits before 'H/s =' Thanks drr0ss,farm recheck only shows hash rate more or less frequently or changing it also changes the result of hash? Hey Wolf0 - you can go to cl-local-work 256 --cl-global-work 16384 with the 7950. The one in next room is doing 24MH very consistently. Like Genoil says, the rate reporting isn't very sophisticated - so it skips around like mad. One thing that's puzzling to me it the need for the DAG to reside in GPU memory. I suppose accessing it via the PCI bus (in system RAM) would be slower, but, would all for 1GB cards to mine. What do you think? |
|
|
|
i'm trying to compile on 15.10
but i get error that cuda dont support higher then gcc-4.9
i've tried with
ln -s /usr/bin/g++-4.8 /usr/bin/g++
ln -s /usr/bin/gcc-4.8 /usr/bin/gcc
but it still says: #error -- unsupported GNU version! gcc versions later than 4.9 are not supported!
when i do gcc/g++ --version it says 4.8.5
nvcc doesn't always report errors correctly - are you using cuda 6.5 or 7.5? 7.5 i'm reinstalling 14.04 on my test machine. will try compile it on that when its done. I'm building a fresh 15.10 now - I'll let you know what I find. 15.10 is ready, I've been using it for quite awhile now. |
|
|
|
i'm trying to compile on 15.10
but i get error that cuda dont support higher then gcc-4.9
i've tried with
ln -s /usr/bin/g++-4.8 /usr/bin/g++
ln -s /usr/bin/gcc-4.8 /usr/bin/gcc
but it still says: #error -- unsupported GNU version! gcc versions later than 4.9 are not supported!
when i do gcc/g++ --version it says 4.8.5
nvcc doesn't always report errors correctly - are you using cuda 6.5 or 7.5? |
|
|
|
ubuntu 14.04 cuda-7.5 and use cmake -DCOMPUTE=30 -DBUNDLE=cudaminer .. from cpp-ethereum/build
with: installed
apt-get install build-essential fakeroot dh-make debconf execstack dh-modaliases dkms pkg-config
apt-get install libtool libncurses5-dev libcryptopp-dev libleveldb-dev libjsoncpp-dev libargtable2-dev libjson-rpc-cpp-dev
apt-get install libmicrohttpd-dev libreadline-dev libtool autotools-dev automake pkg-config libssl-dev libevent-dev bsdmainutils
apt-get install -f libsdl2-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler libgmp-dev cpuid
nvcc fatal : Unknown option '-std'
CMake Error at ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o.cmake:206 (message):
Error generating
/root/cpp-ethereum/build2/libethash-cuda/CMakeFiles/ethash-cuda.dir//./ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o
make[2]: *** [libethash-cuda/CMakeFiles/ethash-cuda.dir/ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o] Error 1
make[2]: Leaving directory `/root/cpp-ethereum/build2'
make[1]: *** [libethash-cuda/CMakeFiles/ethash-cuda.dir/all] Error 2
make[1]: Leaving directory `/root/cpp-ethereum/build2'
make: *** [all] Error 2
edit this file: /root/cpp-ethereum/build2/libethash-cuda/CMakeFiles/ethash-cuda.dir/ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o.cmake look for lines that set the nvcc_flags: set(CUDA_NVCC_FLAGS .......... -std isn't a valid option for some versions of mvcc - so, remove that option. My line looks like this: set(CUDA_NVCC_FLAGS --disable-warnings;--ptxas-options=-v;-use_fast_math;-lineinfo;-gencode;arch=compute_20,code=sm_20;-gencode;arch=compute_30,code=sm_30;-gencode;arch=compute_35,code=sm_35;-gencode;arch=compute_50,code=sm_50 ;; ) Also, stop building as root:) sudo is your friend, my friend. didnt help. got Error limit reached. 100 errors detected in the compilation of "/tmp/tmpxft_000008a0_00000000-6_ethash_cuda_miner_kernel.cpp1.ii". Compilation terminated. CMake Error at ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o.cmake:264 (message): Error generating file /root/cpp-ethereum/build2/libethash-cuda/CMakeFiles/ethash-cuda.dir//./ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o make[2]: *** [libethash-cuda/CMakeFiles/ethash-cuda.dir/ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o] Error 1 make[1]: *** [libethash-cuda/CMakeFiles/ethash-cuda.dir/all] Error 2 So, you have more/different errors. Stop building as root - you're killin' me??? What version of cuda? I use 7.5, I think Genoil is using 6.5. Here's what I do after failed builds. From your build directory, working as a NON PRIV user: rm -rf CMakeCache.txt && cmake -G "Unix Makefiles" -DEVMJIT=0 -DCMAKE_BUILD_TYPE=Release -DBUNDLE=cudaminer make clean **make your change (removing --std) to libethash-cuda/CMakeFiles/ethash-cuda.dir/ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o.cmake set(nvcc_flags -m64; --std;c++11;-DETH_JSONRPC;-DETH_READLINE;-DETH_MINIUPNPC;-DETH_ETHASHCL;-DETH_ETHASHCUDA;-DETH_STRATUM;-DETH_CURL;-DETH_FRONTIER;-DETH_TRUE) # list make VERBOSE=1 Then, show me the error. |
|
|
|
hello crew new to eth, i will to ask if it is possible to run 2 amd cards a 7950 and 7850 in the same rig, windows 8.1 64bit, the switches that i have read here for specifying add'l cards don't seem to work it starts to mine and stops, also i can mine with the single cards in position 0 of the mb works great but when i install the second card in position 1 it assigns itself position 0, here is my cmds i have tried, 1)single card, "ethminer.exe --farm-recheck 200 -G -F http://127.0.0.1:8332/username.workername:password --cl-global-work 8192 --cl-local-work 128: on the single 7950this works great, 20+ MHs/s 2)2cards, "ethminer.exe --farm-recheck 200 G -F http;//127.0.0.1:8332/username.workername:password opencl-device 0,1 --cl-global-work 8192 --cl-local-128" with settings it will start to hash until the second or third "got work" then it halts and the curser blinks,also i checked the status on the amd settings and it shows that the 7950 card is operating at 99% the 7850 is at idle. 3)2cards, "ethminer.exe --farm-recheck 200 -G -F http://127.0.0.1:8332/username.workername:password" it will ether loading dag or start hashing until the second or third "got work package" and it halts. thanks in advance Yeah, stop using Windows:) Here is an example "hillbilly winders" startup bat file: setx GPU_FORCE_64BIT_PTR 0 setx GPU_MAX_HEAP_SIZE 100 setx GPU_USE_SYNC_OBJECTS 1 setx GPU_MAX_ALLOC_PERCENT 100 cd C:\Users\dave\Desktop\ethminer-0.9.41-genoil-1.0.5 ethminer -G -R . --farm-recheck 400 --cl-local-work 128 --cl-global-work 8192 -F http://ethereum.usa.nicehash.com:3500/n1c3-1HtkaiWKeKZ6MJgag6a3fUQo3BxcT2gAKv.nvda/20There are a lot of things to check. 8GB of RAM is a good idea. Make sure you have available disk space - DAG files are ~3GB in total. Make sure your are using the latest AMD drivers - Crimson has been working well for most. Take all that malware off your "Winders" box too - strip it BARE, or even do a clean install of a 64bit OS. |
|
|
|
i need to know what farm check does exactly, it seems that my earning is increase with this set to 100
farm-recheck is the time (in milliseconds) interval your miner checks the farm for new work/block changes. You will punish your farm, but, get new work sooner after a block change. Won't make a world of difference, but, it will help a little. Notes: If you use a stratum proxy, a lower farm-recheck is fine as your actually just punishing your proxy. The proxy "subscribes" to block changes. Genoil's hard work implementing stratum should make the farm-recheck a thing of the past with stratum-capable pools. |
|
|
|
ubuntu 14.04 cuda-7.5 and use cmake -DCOMPUTE=30 -DBUNDLE=cudaminer .. from cpp-ethereum/build
with: installed
apt-get install build-essential fakeroot dh-make debconf execstack dh-modaliases dkms pkg-config
apt-get install libtool libncurses5-dev libcryptopp-dev libleveldb-dev libjsoncpp-dev libargtable2-dev libjson-rpc-cpp-dev
apt-get install libmicrohttpd-dev libreadline-dev libtool autotools-dev automake pkg-config libssl-dev libevent-dev bsdmainutils
apt-get install -f libsdl2-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler libgmp-dev cpuid
[ 65%] Building NVCC (Device) object libethash-cuda/CMakeFiles/ethash-cuda.dir/ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o
cd /root/cpp-ethereum/build2/libethash-cuda/CMakeFiles/ethash-cuda.dir && /usr/bin/cmake -E make_directory /root/cpp-ethereum/build2/libethash-cuda/CMakeFiles/ethash-cuda.dir//.
cd /root/cpp-ethereum/build2/libethash-cuda/CMakeFiles/ethash-cuda.dir && /usr/bin/cmake -D verbose:BOOL=1 -D build_configuration:STRING=Release -D generated_file:STRING=/root/cpp-ethereum/build2/libethash-cuda/CMakeFiles/ethash-cuda.dir//./ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o -D generated_cubin_file:STRING=/root/cpp-ethereum/build2/libethash-cuda/CMakeFiles/ethash-cuda.dir//./ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o.cubin.txt -P /root/cpp-ethereum/build2/libethash-cuda/CMakeFiles/ethash-cuda.dir//ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o.cmake
-- Removing /root/cpp-ethereum/build2/libethash-cuda/CMakeFiles/ethash-cuda.dir//./ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o
/usr/bin/cmake -E remove /root/cpp-ethereum/build2/libethash-cuda/CMakeFiles/ethash-cuda.dir//./ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o
-- Generating dependency file: /root/cpp-ethereum/build2/libethash-cuda/CMakeFiles/ethash-cuda.dir//ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o.NVCC-depend
/usr/bin/nvcc -M -D__CUDACC__ /root/cpp-ethereum/libethash-cuda/ethash_cuda_miner_kernel.cu -o /root/cpp-ethereum/build2/libethash-cuda/CMakeFiles/ethash-cuda.dir//ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o.NVCC-depend -ccbin /usr/bin/gcc-4.8 -m64 -DETH_JSONRPC -DETH_READLINE -DETH_MINIUPNPC -DETH_ETHASHCL -DETH_ETHASHCUDA -DETH_STRATUM -DETH_CPUID -DETH_CURL -DETH_FRONTIER -DETH_TRUE -Xcompiler ,\"-std=c++11\",\"-Wall\",\"-Wno-unknown-pragmas\",\"-Wextra\",\"-Wno-error=parentheses\",\"-pedantic\",\"-DSHAREDLIB\",\"-fPIC\",\"-fuse-ld=gold\",\"-O3\",\"-DNDEBUG\",\"-DETH_RELEASE\" --std=c++11 --disable-warnings --ptxas-options=-v -use_fast_math -lineinfo -gencode arch=compute_30,code=sm_30 -O3 -DNVCC -I/usr/include -I/root/cpp-ethereum/build2/gen -I/root/cpp-ethereum/build2 -I/root/cpp-ethereum/build2/libethash-cuda -I/usr/include -I/root/cpp-ethereum/libethash-cuda/..
nvcc fatal : Unknown option '-std'
CMake Error at ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o.cmake:206 (message):
Error generating
/root/cpp-ethereum/build2/libethash-cuda/CMakeFiles/ethash-cuda.dir//./ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o
make[2]: *** [libethash-cuda/CMakeFiles/ethash-cuda.dir/ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o] Error 1
make[2]: Leaving directory `/root/cpp-ethereum/build2'
make[1]: *** [libethash-cuda/CMakeFiles/ethash-cuda.dir/all] Error 2
make[1]: Leaving directory `/root/cpp-ethereum/build2'
make: *** [all] Error 2
edit this file: /root/cpp-ethereum/build2/libethash-cuda/CMakeFiles/ethash-cuda.dir/ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o.cmake look for lines that set the nvcc_flags: set(CUDA_NVCC_FLAGS .......... -std isn't a valid option for some versions of mvcc - so, remove that option. My line looks like this: set(CUDA_NVCC_FLAGS --disable-warnings;--ptxas-options=-v;-use_fast_math;-lineinfo;-gencode;arch=compute_20,code=sm_20;-gencode;arch=compute_30,code=sm_30;-gencode;arch=compute_35,code=sm_35;-gencode;arch=compute_50,code=sm_50 ;; ) Also, stop building as root:) sudo is your friend, my friend. |
|
|
|
Bump, still looking.
I can build these binaries and replace the current cgminer in the image you linked to in the ad (smit1237's image). Couple of questions/concerns. Not all the Bitmain devices use the same platform for the mining interface. Do you want an "archless" build of cgminer? In some cases, that will not be optimal for these devices. They are somewhat underpowered, and the cgminer binaries should be built specifically for the miner platform type. I'd be happy to get this done for you tomorrow (or asap), please let me know what you're expecting. Thanks! |
|
|
|
Can anyone can translate to NEON instructions in C? https://community.arm.com/groups/android-community/blog/2015/03/27/arm-neon-programming-quick-referenceI put it in scrypt_mine.cpp to run DMD wallet, it is far from optimized and ARMv8 supports NEON. #if defined(__aarch64__)
static inline void xor_salsa8(uint32_t B[16], const uint32_t Bx[16])
{
uint32_t x00,x01,x02,x03,x04,x05,x06,x07,x08,x09,x10,x11,x12,x13,x14,x15;
int i;
x00 = (B[ 0] ^= Bx[ 0]);
x01 = (B[ 1] ^= Bx[ 1]);
x02 = (B[ 2] ^= Bx[ 2]);
x03 = (B[ 3] ^= Bx[ 3]);
x04 = (B[ 4] ^= Bx[ 4]);
x05 = (B[ 5] ^= Bx[ 5]);
x06 = (B[ 6] ^= Bx[ 6]);
x07 = (B[ 7] ^= Bx[ 7]);
x08 = (B[ 8] ^= Bx[ 8]);
x09 = (B[ 9] ^= Bx[ 9]);
x10 = (B[10] ^= Bx[10]);
x11 = (B[11] ^= Bx[11]);
x12 = (B[12] ^= Bx[12]);
x13 = (B[13] ^= Bx[13]);
x14 = (B[14] ^= Bx[14]);
x15 = (B[15] ^= Bx[15]);
for (i = 0; i < 8; i += 2) {
#define R(a, b) (((a) << (b)) | ((a) >> (32 - (b))))
/* Operate on columns. */
x04 ^= R(x00+x12, 7); x09 ^= R(x05+x01, 7);
x14 ^= R(x10+x06, 7); x03 ^= R(x15+x11, 7);
x08 ^= R(x04+x00, 9); x13 ^= R(x09+x05, 9);
x02 ^= R(x14+x10, 9); x07 ^= R(x03+x15, 9);
x12 ^= R(x08+x04,13); x01 ^= R(x13+x09,13);
x06 ^= R(x02+x14,13); x11 ^= R(x07+x03,13);
x00 ^= R(x12+x08,18); x05 ^= R(x01+x13,18);
x10 ^= R(x06+x02,18); x15 ^= R(x11+x07,18);
/* Operate on rows. */
x01 ^= R(x00+x03, 7); x06 ^= R(x05+x04, 7);
x11 ^= R(x10+x09, 7); x12 ^= R(x15+x14, 7);
x02 ^= R(x01+x00, 9); x07 ^= R(x06+x05, 9);
x08 ^= R(x11+x10, 9); x13 ^= R(x12+x15, 9);
x03 ^= R(x02+x01,13); x04 ^= R(x07+x06,13);
x09 ^= R(x08+x11,13); x14 ^= R(x13+x12,13);
x00 ^= R(x03+x02,18); x05 ^= R(x04+x07,18);
x10 ^= R(x09+x08,18); x15 ^= R(x14+x13,18);
#undef R
}
B[ 0] += x00;
B[ 1] += x01;
B[ 2] += x02;
B[ 3] += x03;
B[ 4] += x04;
B[ 5] += x05;
B[ 6] += x06;
B[ 7] += x07;
B[ 8] += x08;
B[ 9] += x09;
B[10] += x10;
B[11] += x11;
B[12] += x12;
B[13] += x13;
B[14] += x14;
B[15] += x15;
}
static inline void scrypt_core(uint32_t *X, uint32_t *V)
{
uint32_t i, j, k;
int n=1024;
for (i = 0; i < n; i++) {
memcpy(&V[i * 32], X, 128);
xor_salsa8(&X[0], &X[16]);
xor_salsa8(&X[16], &X[0]);
}
for (i = 0; i < n; i++) {
j = 32 * (X[16] & (n - 1));
for (k = 0; k < 32; k++)
X[k] ^= V[j + k];
xor_salsa8(&X[0], &X[16]);
xor_salsa8(&X[16], &X[0]);
}
}
#endif
Hey utah - I'd just change your makefile to build that with nasm (if it builds). Otherwise, a good gcc version *should optimize that code for your ARMv8 chip. https://gcc.gnu.org/onlinedocs/gcc/AArch64-Options.html" The value ‘armv8.1-a’ implies ‘armv8-a’ and enables compiler support for the ARMv8.1 architecture extension. In particular, it enables the ‘+crc’ and ‘+lse’ features. " |
|
|
|
trying to build on ubuntu.
ethminer/CMakeFiles/ethminer.dir/build.make:62: recipe for target 'ethminer/CMakeFiles/ethminer.dir/main.cpp.o' failed
make[2]: *** [ethminer/CMakeFiles/ethminer.dir/main.cpp.o] Error 1
CMakeFiles/Makefile2:447: recipe for target 'ethminer/CMakeFiles/ethminer.dir/all' failed
make[1]: *** [ethminer/CMakeFiles/ethminer.dir/all] Error 2
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2
anyone know why i get this error ? have installed dependencies tried to compile https://github.com/ethereum/webthree-umbrella.git and that worked anyone with a working release for linux used https://github.com/Genoil/cpp-ethereum.gitI built the current master release for Ubuntu 14 yesterday without problems. What is the cmake command you've used? what commands did you use ? use this to build: make VERBOSE=1 That will give you output you can use to track-down your missing dependencies or compiler errors. Google is your friend |
|
|
|
For reference, by 390X ($369 at my local retailer) is doing a average of 34MH.
The only changes in my run line are -
--cl-local-work 256 --farm-recheck 200
how do you get 34MH with your 390x i only get 28MH might it be windows that does it. useing latest driver 16.2 and ethminer-0.9.41-genoil-1.0.4b3 have a Saphire 390x core 1080 I'm using Ubuntu 15.10 and the latest Crimson drivers (see my build notes in previous post) Overclocked the XFX card with - aticonfig --adapter=0 --od-setclocks=1160,1675 The card will go faster, but, I don't wanna temp it above 75c - fans too noisey Windows has always been shit for mining, IMHO. The code is ALWAYS a port that abstracts system functions and something is most always lost. Show me one coin that mines faster on Windows and I might switch, but I doubt it. ok. tried 1140 core but dont get more then 30MHs from what i've read mem speed dont do anything for hashing my card sits a about 70c What OS? What driver version? I have observed memory clock changes having an impact on hashrates. So, I think clocking your memory is worth a try. |
|
|
|
|
Show Posts
