There is no charge on the pool Huh Mining 200% !!! Help solve the problem !!!
Thank you
Really? You have been reported to the moderator. Not sure now if maybe vadim15rus is a troll too. |
|
|
|
that's not clear, I started another 1 Mining on your website and revenue again will not display correctly
Your english is not clear, no one can understand you. Please show exactly what you are trying to do. Start with the command line. |
|
|
|
try to add one at time not all at once
Tried that too... still no work. I'm testing the same thing on a gigabyte p67a ds-3, and it's the same thing, 3 gpu ok, but 4+ not recognized (code 28). It is a chipset thing? What exactly happens? Does is start to boot Windows? Does it succeed? How many cards? If it doesn't get past the bios it's probably an underpowered PSU. |
|
|
|
Thanks! I used the following: ./configure CFLAGS="-DNO_AES_NI -O3 -march=native" --with-curl --with-crypto and ./configure CFLAGS="-DNO_AES_NI -O3 -march=amdfam10" --with-curl --with-crypto But it seems that still got an error: algo/echo/aes_ni/hash.c:387:4: note: in expansion of macro ‘TRANSFORM’
TRANSFORM(_state[i][j], _k_opt, t1, t2);
^
make[2]: *** [algo/echo/aes_ni/cpuminer-hash.o] Error 1
make[2]: Leaving directory `/home/***/cpuminer-opt-3.1.7'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/***/cpuminer-opt-3.1.7'
make: *** [all] Error 2
With ./configure CFLAGS="-DNO_AES_NI -O3 -march=core2" --with-curl --with-crypto I got a successful compile on AMD and it mines at 370 khash, which is about 10 khash slower than my scmorse build. and so far the best is: ./configure CFLAGS="-DNO_AES_NI -O3 -march=k8-sse3" --with-curl --with-crypto which gets 373-375 khash on that Phenom II. P.S. Stall searching my Ubuntu image for cross-compile. If I don't find it I will use MSYS and Win 7 x64...  The SSE2 compile should be on par with scmorse. Perhaps I should change the recommendation to always use -march=core2 for all non-aesni cpus since it works on AMD as well. |
|
|
|
Damn! Just when I get my hopes up for AMD cpus... It wont compile on AMD Phenom II X4 940. This is the error that I get: In file included from algo/cryptonight/cryptonight-aesni.c:2:0:
algo/cryptonight/cryptonight.h:65:6: note: expected ‘uint64_t *’ but argument is of type ‘union hash_state *’
void keccakf(uint64_t st[25], int rounds);
^
make[2]: *** [algo/cryptonight/cpuminer-cryptonight-aesni.o] Error 1
make[2]: Leaving directory `/home/***/cpuminer-opt-3.1.7'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/***/cpuminer-opt-3.1.7'
make: *** [all] Error 2
Can you do something about that? In the meantime I will find my cross-compile image so I can try to compile AES-NI and SSE2 win64 builds. Add "-DNO_AES_NI" to the CFLAGS. I haven't gotten Windows to compile since I forked from TPruvot, the project file hasn't been maintained. Good luck. |
|
|
|
Which motherboard do you use? For some mothboards, if you use the x1 riser, you need to short the A1B17 or B1A17 card presence pin.
MSI P67a-GD65 where is that pin located? Shorting out the pins just tells the motherboard to provide 75W to the slot, usually x1 is limited to 25W. It may result in more power going through the MB than it can handle. I don't recommend it. Make sure you use powered risers. With powered risers the power from the slot is not used. My rule of thumb is the MB is designed to supply enough power to as many GPUs as there are x16 slots. Any more GPUs than that and extra power is needed. |
|
|
|
Wich is good. Lyra2re was replaced by lyra2v2 because the botnets had most of the hashrate. (Vertcoin, lyrabar) lyra2v2 is usually also more profitable to mine.
Untfortunately my attempts to optimise lyra2v2 have not succeeded. I still don't know why lyra2 is so hot right now, but I'm not complaining. I can't even take credit for the lyra2 performance, it's unchanged since I forked from TPruvot. |
|
|
|
Regularly Lyra2RE is profitable with NiceHash. Wonder which coin peoples are mining.
how much is profitable? how much with one 970 per day? Lyra2 is even more profitable mining with a CPU using cpuminer-opt (see sig). It's normalised profitability rate is 1.25 x11 vs ccminer at .336. what this mean? i can not understand your profit in your post Lyra2re is paying 2.5Btc/ghash. 1 750ti shoild do around 1.1mhash with the sp-mod (1.1/1000)*2.5 gives you 1 dollar per day. I'm getting 930K on a 6700K. |
|
|
|
Regularly Lyra2RE is profitable with NiceHash. Wonder which coin peoples are mining.
how much is profitable? how much with one 970 per day? Lyra2 is even more profitable mining with a CPU using cpuminer-opt (see sig). It's normalised profitability rate is 1.25 x11 vs ccminer at .336. what this mean? i can not understand your profit in your post It has to do with the efficiency of the device mining a particular algo. A CPU can hash lyra2 1.25 times what it hashes x11. There are only a couple of algos that are CPU advantaged, lyra2 is one and cryptonight is likely another. Edit: the following claim was made using outaded measurements, the CPU advantage is less than stated. Actual numbers are 1.1 MH for 750ti and 930 KH for i7-6700K. A Core i-4790K @4 GHz will outperfrom a GTX750ti in raw hashrate on lyra2. That's nearly four times more hash with
a two times less power efficient device. A net gain of double the power efficiency for equal hash rate. Unfortunately
CPUs don't scale easilly, can't put 6 in one rig like with GPUs. The GTX9xx cards perform a little better than the 750ti but the CPU still has the advantage with this algo. |
|
|
|
Regularly Lyra2RE is profitable with NiceHash. Wonder which coin peoples are mining.
how much is profitable? how much with one 970 per day? Lyra2 is even more profitable mining with a CPU using cpuminer-opt (see sig). It's normalised profitability rate is 1.25 x11 vs ccminer at .336. |
|
|
|
The new version 3.1.6 returns only invalid (low-diff) shares with zr5 algo on ziftrpool.io AKAIK v3.1.5 worked just fine with that pool. There is some more room for improvement, especially on zr5. With scmorse/ziftr-cpu which is ig0tik3d/ziftr-cpu with stratum, I get about 640 khash on Core i7-4790K CPU @ 4.40GHz and with your miner I got as close to 600 khash... Just my 2 cents.  Thanks for the feedback, I'll look into it. Edit: No rejects for me with default options at yiimp. I also reviewed the code and found no changes that would affect zr5. Can you confirm that 3.1.5 & 3.1.6 behave differently? Could you also try yiimp? When I mine the diff is reported as .013. You could try setting the diff manually. On yaamp clones it is in the password string ( -p d=n ), but your pool may be different. Edit2: I took a look at the scmorse implementation and i might be able to do better. His implemetation does not use the aes-ni optimized groestl. If I can integrate that it should hash even faster. Merging my optimizations with scmorse gave a 33% increase to zr5 but I'll wait to release it until your issue is understood. Well after recompile of v3.1.6 on my Ubuntu box there is no low-diff rejects on ziftrpool.io v3.1.5 is also good, but little bit (about 5 khash) slower. Guess it was something wrong with the previous compile...  (I think I used ./build.sh script) 33% more harshrate on ZR5 sounds just AWESOME!  I expect that my Core i7-4790K will go upto ~800 khash... Just to compare - an older GPU, AMD HD6870 makes 860-900 khash average with wolf's GPU miner @ 845 MHz... I haven't looked at build.sh since the fork, I should clean it up. Thanks for the tip about scmorse. |
|
|
|
cpuminer-opt v3.1.7 is available for download: https://drive.google.com/file/d/0B0lVSGQYLJIZdVZlczRsVlFGUWs/view?usp=sharingNew in v3.1.7 For users: - zr5 algo +33% AES_NI and SSE2 optimised, +98% since v3.1.4 For developpers: - better handling of algo aliases - better handling of hashrate display Recently added algos: - x14 with AES_NI optimisations - blake - blake2s - vanilla (blake256r14vnl). - x17, blakecoin & fresh algos, benchmark tested only. Recently improved algos: - nist5 +54% AES_NI optimised. - c11 +27% AES_NI optimised. - SSE2 hashrate increases in many algos. See first post and for more details including normalisation factors. |
|
|
|
Proof of physical work, that is... http://fitcoin.chaoticmoon.comIf this becomes tradeable on the exchanges it could be very interesting. Maybe I need to buy a treadmill and start mining. |
|
|
|
The new version 3.1.6 returns only invalid (low-diff) shares with zr5 algo on ziftrpool.io AKAIK v3.1.5 worked just fine with that pool. There is some more room for improvement, especially on zr5. With scmorse/ziftr-cpu which is ig0tik3d/ziftr-cpu with stratum, I get about 640 khash on Core i7-4790K CPU @ 4.40GHz and with your miner I got as close to 600 khash... Just my 2 cents. Thanks for the feedback, I'll look into it. Edit: No rejects for me with default options at yiimp. I also reviewed the code and found no changes that would affect zr5. Can you confirm that 3.1.5 & 3.1.6 behave differently? Could you also try yiimp? When I mine the diff is reported as .013. You could try setting the diff manually. On yaamp clones it is in the password string ( -p d=n ), but your pool may be different. Edit2: I took a look at the scmorse implementation and i might be able to do better. His implemetation does not use the aes-ni optimized groestl. If I can integrate that it should hash even faster. Merging my optimizations with scmorse gave a 33% increase to zr5 but I'll wait to release it until your issue is understood. |
|
|
|
Proof of physical work, that is... http://fitcoin.chaoticmoon.comIf this becomes tradeable on the exchanges it could be very interesting. Will fitness fanatics work their butts off and sell their coins to lazy gamers? Maybe I need to buy an exercise bike and start mining. I wonder how much an hour of screen time would be worth. |
|
|
|
The new version 3.1.6 returns only invalid (low-diff) shares with zr5 algo on ziftrpool.io AKAIK v3.1.5 worked just fine with that pool. There is some more room for improvement, especially on zr5. With scmorse/ziftr-cpu which is ig0tik3d/ziftr-cpu with stratum, I get about 640 khash on Core i7-4790K CPU @ 4.40GHz and with your miner I got as close to 600 khash... Just my 2 cents. Thanks for the feedback, I'll look into it. Edit: No rejects for me with default options at yiimp. I also reviewed the code and found no changes that would affect zr5. Can you confirm that 3.1.5 & 3.1.6 behave differently? Could you also try yiimp? When I mine the diff is reported as .013. You could try setting the diff manually. On yaamp clones it is in the password string ( -p d=n ), but your pool may be different. Edit2: I took a look at the scmorse implementation and i might be able to do better. His implemetation does not use the aes-ni optimized groestl. If I can integrate that it should hash even faster. |
|
|
|
const char algo_alias_map[][2][] = {
...
{NULL, NULL}
}
if (algo_alias_map[n][0] == NULL)
should work.
Almost worked, needed to make a slight adjustment: const char *algo_alias_map[][2] = { Thanks. Still had to work a few things out, got mixed up with operator precedence: char * a[] means a array of char pointers, not a pointer to an array. The working version will be in the next release, just missed 3.1.6. // an algo can have multiple aliases but the aliases must be unique
#define PROPER (1)
#define ALIAS (0)
// Need to sort out all the blakes
// blake256r14 is apparently decred
// Vanilla was obvious, blakecoin is almosty identical to vanilla
// What is blake2s, pentablake?
const char* algo_alias_map[][2] =
{
// alias proper
{ "blake256r8vnl", "vanilla" },
{ "blake256r8", "blakecoin" },
{ "cryptonight-light", "cryptolight" },
{ "droplp", "drop" },
{ "flax", "c11" },
{ "lyra2", "lyra2re" },
{ "lyra2v2", "lyra2rev2" },
{ "myriad", "myr-gr" },
{ "neo", "neoscrypt" },
{ "sibcoin", "sib" },
{ "ziftr", "zr5" },
{ NULL, NULL } //add new aliases above this line
};
// if arg is a valid alias for a known algo it is updated with the proper name.
// No validation of the algo or alias is done, It is the responsinility of the
// calling function to validate the algo after return.
void get_algo_alias( char** algo_or_alias )
{
int i;
for ( i=0; algo_alias_map[i][ALIAS]; i++ )
if ( !strcasecmp( *algo_or_alias, algo_alias_map[i][ ALIAS ] ) )
{
// found valid alias, return proper name
*algo_or_alias = algo_alias_map[i][ PROPER ];
return;
}
}
After all that it might have been simpler to list all the aliases in ALGO_NAMES and use multiple case statements for algo with aliases. |
|
|
|
const char algo_alias_map[][2][] = {
...
{NULL, NULL}
}
if (algo_alias_map[n][0] == NULL)
should work.
Almost worked, needed to make a slight adjustment: const char *algo_alias_map[][2] = { Thanks. Still had to work a few things out, got mixed up with operator precedence: char * a[] means a array of char pointers, not a pointer to an array. The working version will be in the next release, just missed 3.1.6. // an algo can have multiple aliases but the aliases must be unique
#define PROPER (1)
#define ALIAS (0)
// Need to sort out all the blakes
// blake256r14 is apparently decred
// Vanilla was obvious, blakecoin is almosty identical to vanilla
// What is blake2s, pentablake?
const char* algo_alias_map[][2] =
{
// alias proper
{ "blake256r8vnl", "vanilla" },
{ "blake256r8", "blakecoin" },
{ "cryptonight-light", "cryptolight" },
{ "droplp", "drop" },
{ "flax", "c11" },
{ "lyra2", "lyra2re" },
{ "lyra2v2", "lyra2rev2" },
{ "myriad", "myr-gr" },
{ "neo", "neoscrypt" },
{ "sibcoin", "sib" },
{ "ziftr", "zr5" },
{ NULL, NULL } //add new aliases above this line
};
// if arg is a valid alias for a known algo it is updated with the proper name.
// No validation of the algo or alias is done, It is the responsinility of the
// calling function to validate the algo after return.
void get_algo_alias( char** algo_or_alias )
{
int i;
for ( i=0; algo_alias_map[i][ALIAS]; i++ )
if ( !strcasecmp( *algo_or_alias, algo_alias_map[i][ ALIAS ] ) )
{
// found valid alias, return proper name
*algo_or_alias = algo_alias_map[i][ PROPER ];
return;
}
}
|
|
|
|
const char algo_alias_map[][2][] = {
...
{NULL, NULL}
}
if (algo_alias_map[n][0] == NULL)
should work.
Almost worked, needed to make a slight adjustment: const char *algo_alias_map[][2] = { Thanks. |
|
|
|
|
Show Posts
