its doesnt seem profitable for me. take ROI is too long. for me better take litle high risk but more profitable.
Like what? Gambling or ponzi? Ow come on there is no easy way of getting money even in gambling you will lose in the long term There are legit ways to make money in crypto. It does require a lot of reading, lots of trails and errors and using your head a bit. No, this is not advertising for anything and I m not going to promote anything. Just saying, there are legit, hard working ways. As usual. And like it should be. Shortcuts are luck or available for a short time. Then comes the balance.
|
|
|
Both 3.0.2 and Wolf0's cryptonight do compile fine on my amd fx.
|
|
|
Safer and easier: a VM with windows and mingw in it. No visual studio, no conflicts ;-)
|
|
|
I'm getting dizzy with all the direction changes. Now I'm on the mingw path to build a windows version. Don't want to make any promises but if things go well there could be a v3.1 soon with windows support.
I need some help with mingw on Linux. It compiles and builds cpuminer.exe bu it fails to start because libcrypto-10.dll is missing. I have mingw64-openssl-1.0.1j-1.fc20.noarch installed and used the --with-crypto option so it looks ok on the linux end. I installed openssl on windows and it still fails, seems libcrypto-10.dll wasn't included. Google wasn't friendly. All kinds of people were offering the file but I know what that was about.. It's probably another noob issue but I need help with it. Didn't someone tell me mingw was easy? After peeling the onion with missing dll's I ended up draggin along about ten of them. But now there's something i've never seen. cpuminer starts up but crashes on a call to parse-arg. The function and the calls are all in cpu-miner.c, there's nothng special about it just a simple function call. BUT wew nevr get there. I have a printf on the line before the call to parse arg and another just inside the opening brace in parse_arg and only one gets hit before the crash. Itg's crashing on a simple function call. I dpn't know how to get past this. I compiled sgminer on windows using mingw, it wasn't trivial but following the instructions I made it. About your specific crash issue, is it code you wrote or modified, or was it there for long? Maybe it's just some issue with memory allocation.
|
|
|
Don't you guys think that renting on nicehash and mining on a bitcoin pool would be a too easy way of making money? It simply cannot be true, thus don't expect to profit so easily.
|
|
|
Just for fun I tried to compile miner version 3.0.2 on my old Athlon, setting march=corei7-avx in the configure. And it compiled without a hitch.
Then tried to run it, but it core dumps :
Checking CPU capatibility... AMD Athlon(tm) 64 Processor 3200+ AES_NI: No. SSE2: No, start mining without optimizations...
[2016-01-22 20:15:18] Starting Stratum on stratum+tcp://hashpower.co:4733 [2016-01-22 20:15:18] 1 miner threads started, using 'qubit' algorithm. /home/bobben/miner_cpu_qubit: line 12: 5354 Illegal instruction (core dumped) cpuminer -t $thr -a qubit -o stratum+tcp://hashpower.co:4733 -u $ADDR_BTC
Of course it doesn't work. You compiled for a cpu which isn't compatible with yours. The compiler used some instructions which your cpu doesn't understand. I realize an old computer can't run new instructions but I assumed the run time checks would protect it. Obviously I was wrong. I need compile time checks to avoid compiling the aesni code on older cpus. I also need to find out if the lower level kernels are poluted with higher level code, among many other things. I'll see if cygwin can come to my rescue. Hmmmm the check itself could be made of incompatible instructions.... every part of the code could. It's not just AES_NI but many other extensions as well. You just can't compile for a pentium and expect it to run on a 386!
|
|
|
Just for fun I tried to compile miner version 3.0.2 on my old Athlon, setting march=corei7-avx in the configure. And it compiled without a hitch.
Then tried to run it, but it core dumps :
Checking CPU capatibility... AMD Athlon(tm) 64 Processor 3200+ AES_NI: No. SSE2: No, start mining without optimizations...
[2016-01-22 20:15:18] Starting Stratum on stratum+tcp://hashpower.co:4733 [2016-01-22 20:15:18] 1 miner threads started, using 'qubit' algorithm. /home/bobben/miner_cpu_qubit: line 12: 5354 Illegal instruction (core dumped) cpuminer -t $thr -a qubit -o stratum+tcp://hashpower.co:4733 -u $ADDR_BTC
Of course it doesn't work. You compiled for a cpu which isn't compatible with yours. The compiler used some instructions which your cpu doesn't understand.
|
|
|
Tried compiling on a non-aesni cpu (core2), but it tries to use aesni on cryptonight:
In file included from /usr/lib/gcc/x86_64-linux-gnu/5/include/x86intrin.h:43:0, from algo/cryptonight/cryptonight-aesni.c:1: algo/cryptonight/cryptonight-aesni.c: In function ‘ExpandAESKey256_sub2’: /usr/lib/gcc/x86_64-linux-gnu/5/include/wmmintrin.h:87:1: error: inlining failed in call to always_inline ‘_mm_aeskeygenassist_si128’: target specific option mismatch _mm_aeskeygenassist_si128 (__m128i __X, const int __C) ^ algo/cryptonight/cryptonight-aesni.c:26:7: error: called from here tmp4 = _mm_aeskeygenassist_si128(*tmp1, 0x00); ^
I posted about this back half a page or so. Try using -march=corei7-avx. It seems counter intuitive but we need to fool the compiler to compile the AESNI code. Once compile the run time checks will avoid falling into it. If you know of the appropriate compiler directive to check CPU architecture, please advise. I would simply: configure --disable-aesni wolf0 did it on his cryptonight cpuminer. If you're confirming it works for you, I'll document in the build instructions for next release. Know how to do it on VS? I don't know if it works, it must be implemented first :-) On linux you need to modify the m4 files and, possibly, add some precompiler directives. That's why I suggested looking at how Wolf0 did it on his miner.
|
|
|
Tried compiling on a non-aesni cpu (core2), but it tries to use aesni on cryptonight:
In file included from /usr/lib/gcc/x86_64-linux-gnu/5/include/x86intrin.h:43:0, from algo/cryptonight/cryptonight-aesni.c:1: algo/cryptonight/cryptonight-aesni.c: In function ‘ExpandAESKey256_sub2’: /usr/lib/gcc/x86_64-linux-gnu/5/include/wmmintrin.h:87:1: error: inlining failed in call to always_inline ‘_mm_aeskeygenassist_si128’: target specific option mismatch _mm_aeskeygenassist_si128 (__m128i __X, const int __C) ^ algo/cryptonight/cryptonight-aesni.c:26:7: error: called from here tmp4 = _mm_aeskeygenassist_si128(*tmp1, 0x00); ^
I posted about this back half a page or so. Try using -march=corei7-avx. It seems counter intuitive but we need to fool the compiler to compile the AESNI code. Once compile the run time checks will avoid falling into it. If you know of the appropriate compiler directive to check CPU architecture, please advise. I would simply: configure --disable-aesni wolf0 did it on his cryptonight cpuminer.
|
|
|
performance report with 3.0.2:
AMD FX(tm)-8320 Eight-Core Processor AES_NI: Yes, start mining with AES_NI optimizations...
[2016-01-22 12:01:02] Starting Stratum on stratum+tcp://hashpower.co:3533 [2016-01-22 12:01:02] 8 miner threads started, using 'x11' algorithm. [2016-01-22 12:01:02] Stratum difficulty set to 0.016 [2016-01-22 12:04:22] accepted: 1/1 (100.00%), 364.68 kH/s yes! [2016-01-22 12:06:12] accepted: 2/2 (100.00%), 353.90 kH/s yes! [2016-01-22 12:08:01] accepted: 3/3 (100.00%), 344.48 kH/s yes! [2016-01-22 12:10:11] accepted: 4/4 (100.00%), 340.22 kH/s yes! [2016-01-22 12:10:44] accepted: 5/5 (100.00%), 340.28 kH/s yes!
|
|
|
Tried compiling on a non-aesni cpu (core2), but it tries to use aesni on cryptonight:
In file included from /usr/lib/gcc/x86_64-linux-gnu/5/include/x86intrin.h:43:0, from algo/cryptonight/cryptonight-aesni.c:1: algo/cryptonight/cryptonight-aesni.c: In function ‘ExpandAESKey256_sub2’: /usr/lib/gcc/x86_64-linux-gnu/5/include/wmmintrin.h:87:1: error: inlining failed in call to always_inline ‘_mm_aeskeygenassist_si128’: target specific option mismatch _mm_aeskeygenassist_si128 (__m128i __X, const int __C) ^ algo/cryptonight/cryptonight-aesni.c:26:7: error: called from here tmp4 = _mm_aeskeygenassist_si128(*tmp1, 0x00); ^
|
|
|
ah right f*** that
actually another alternative would be something a la opencl with precompile kernel (a priori that wouldn't violate the licensing) but again lots of work... ...and something which doesn't permit reverse engineering the kernel... ...and sometimes the magic is in the miner itself, not the kernel... actually what I did in my miner with fee (for vanillacoin) was to hash some stuff through keccak, then xor it into the final hash so that if someone hack into the program, it never solves the correct hash... doesn't having the source of the miner be enough to figure it out? and how did you do the fee part? if you have the sources, you can remove it.
|
|
|
ah right f*** that
actually another alternative would be something a la opencl with precompile kernel (a priori that wouldn't violate the licensing) but again lots of work... ...and something which doesn't permit reverse engineering the kernel... ...and sometimes the magic is in the miner itself, not the kernel...
|
|
|
I agree. Bittrex has worked very fine for me, for a long time. But so has Poloniex.
|
|
|
Hi Folks, I switced off most of my rigs some time agoand didn't checked. what's going on.My elec. cost is 0.15 cent.Is there anything worth to min?.,any new algo,coins or miners for both amd and nv cards. ? Thanks for help ) Due to a higher BTC/USD change, X11 and lyra2ve may be profitable at times. They say ether is always more profitable but I don't mine it. I say mine if you use the heat you generate, to save gas/diesel/pellets/whatever.
|
|
|
The x11 chain has the same difficulty as the x15 one. Come on guys! :-)
|
|
|
On my 970 rig, I've found out that lowering TDP may bring a less-than-expected hashrate reduction.
Example: TDP set at 150, hashrate -5%, power -12% Cards in P2, algo is NON memory intensive, power at the wall.
Possible causes: chips work more efficiently at lower temperature, fans turn slower.
|
|
|
Isn't this a funny graph? It would be good if it was upside-down :-D Not much to laugh, actually.
|
|
|
This is a really weird statement. WHO on the forums actually does release their miner with conditions and prices that are clearly disclosed in advance? That's one of my biggest problems with the private kernel devs on this forum. SP so far is one of the most open individuals when it comes to price, even if it fluctuates.
He tells you what you get, how much power it uses, and how much it costs. He posts it everywhere.
What kernels are Wolf0 selling? Pallas? DJM (besides Neo)? Oh yeah, you don't know... 'Contact the customer service rep for pricing and availability'
not sure we really have a customer service, but where there is something to sell, the community usually gets informed... that customer service thing is a nice idea... maybe we should do it :-D seriously.... I currently have two things for sale and both have been advertised in the relavant threads.
|
|
|
i hope WOLF0 will make a good pablic algo for decred coin when the mining will start.....
ps: wolf0 u must know that u r my favorite...U prove yr work with facts & not with many sauces.....THANKS FOR ALL!
I hope Wolf0 will prove me wrong, but I fear there is not a lot to optimise on blake 14 rounds.
|
|
|
|