old version of pooler's cpuminer was optimized for intel cpu only, but the recent version is also optimized for AMD cpu. on my i7-920@2.0GH(a dell-M6500 notebook),8 thread Is your pooler's cpuminer built for x64? My implementation uses only 8 SSE registers available on x86. x64 has 16 SSE registers. May be that is the reason of performance difference.
|
|
|
it seems to be slower than minerd, anyone confirm? 6khash compared to 10 khash (minerd)
Please tell me what CPU/number of threads? I think pooler-cpuminer is optimized for AMD. On Intel Core 2 results are more similar.
|
|
|
0.24 released
ADDED: LiteCoin/TeneBrix CPU mining (option -a scrypt)
|
|
|
I'll reply here since I'm a noob and can't post in your other thread... ( https://bitcointalk.org/index.php?topic=3486.0) The 0.22 exe for windows gives the same "Error 80004005: Unspecified error" that K1773R mentioned in the other thread. The error shows when attached to BitClockers pool but doesn't show when attached to my own client. Error is shown in the console ever 10 seconds or so but it still seems to be processing and reporting results. 0.23 released. Some bugs fixed Can be compiled by GCC 4.4 too.
|
|
|
tell me what exactly you need I have said already. SSH access. Any other way to debug is not effective.
|
|
|
EDIT: sometimes it directly exit after Error 80004005 and returns an exit code of 02, if its not exiting then i see 3 times the error and 0 MHash/s, after each time 0Mhash/s gets updated (after the sleep in the program) it throws another Error 80004005. greetings
Thank you. But I think it should be debugged. This info is not enough to fing bug.
|
|
|
well, compiled now but im getting a error 80004005, any advices? Need backtrace of stack when this exception thrown. Can be printed under GDB debugger.
|
|
|
could you be so friendly and compile a x64 version? tryd it on another (debian sid, up to date) machine but there i get the same error as before "terminate called after..."
I am interested to debug such cases. So if your build had crashed and if it is possible to give us shell account to your system, please write to support@ufasoft.com. I will debug the program on your system.
|
|
|
still not working, now its getting REALLY ugly!
the project requires GCC 4.5 at least.
|
|
|
Temporary patch: insert following line into start of el/inc/default-defs.h#define UCFG_CPP11_EXPLICIT_CAST 0
|
|
|
Спасибо за замечание. Исходники подправим для совместимости с GCC 4.5 в следующей версии.
На GCC 4.6 соберется без этих ошибок.
|
|
|
Ok, then why is it an archive in an archive? When i uncompress the lzma archive i get a tar archive which also needs to be untarred. It would be awesome if ufasoft would just use .tar archive instead of double compression.
.tar.lzma (or .tar.bz2 in former years) is Unix standard for packaging source code.
|
|
|
Ufasoft, would it be possible for future releases of the sourcecode to use ZIP instead of LZMA because apparently my winzip does not recognize lzma, so i need another tool for that.
You want to use commercial tool for opening Source Code archive. It is not logical )) Yes, use 7-Zip
|
|
|
Error 80072EE9
It is code of CL_PLATFORM_NOT_FOUND_KHR error Some AMD adapter/driver specific error. I cannot reproduce it. Try to update Catalyst+OpenCL drivers to latest. And please tell what is your Video Card Model?
|
|
|
bitcoin-miner 0.21 Copyright (c) 2011 Ufasoft http://ufasoft.com/open/bitcoin Mining for mining.eligius.st Using CPU (2 threads) Error 80072EE9
Anyone knows how to fix it? I'm getting it on all systems, trying to mine on Eligius. Works perfectly on Linux though. That is error ERROR_INTERNET_INVALID_OPTION What is your Windows version and command line parameters?
|
|
|
How about precedent? No miner software or pool uses uppercase except yours. It may seem trivial to you but every operation counts on the poolserver side and having to convert a long string to lowercase everytime is a waste of cycles. particularly when in 99.9% of cases the string is already completely lowercase. If you have a good reason for converting to uppercase then fine but if you don't please do what every other miner does so I can stop wasting cpu time for absolutely no reason.
There is reference implementation exists. Function ParseHex() in the file util.cpp of Bitcoin client: vector<unsigned char> ParseHex(const char* psz) { static char phexdigit[256] = { -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1, -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1, -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1, 0,1,2,3,4,5,6,7,8,9,-1,-1,-1,-1,-1,-1, -1,0xa,0xb,0xc,0xd,0xe,0xf,-1,-1,-1,-1,-1,-1,-1,-1,-1, -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1, -1,0xa,0xb,0xc,0xd,0xe,0xf,-1,-1,-1,-1,-1,-1,-1,-1,-1 -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,
As you can see, it parses equally Uppercase and Lowercase Hex-digits with NO additional cost by simple translation table. Without specs, all that works with reference implementation is right, all that don't work is wrong. Isn't it?
|
|
|
ufasoft, is there any modification in user agent for this version? It would be nice to know if pool can enable LP for given worker or not...
User-Agent contains substring: Ufasoft bitcoin-miner/0.21 I think LP can be enabled for versions >= 0.21
|
|
|
|