When I configure CFLAGS="-03" is says that "C cannot compile executables"
It's "-O3", not "-03". See the difference? (It's big O, not zero.) 
Topic: An (even more) optimized version of cpuminer (pooler's cpuminer, CPU-only) - page 42. (Read 1958546 times)
June 26, 2013, 02:37:38 PM
June 26, 2013, 02:29:04 PM
Question on CFLAGS:
When I configure CFLAGS="-03" is says that "C cannot compile executables"
But if I use "./configure CPPFLAGS="" and then "make" tehre are no errors after the configure command
Does this make any sense and is there any reason NOT to do this when the miner seems to work just fine (sometimes better depending on the pool)?
I put a paste up addressing this issue.
http://pastebin.com/iLSck4ES
Please not that I am aware of teh typo re: "CPFLAGS" it was supposed to read "CFLAGS"
Would like some feedback
Thanks
When I configure CFLAGS="-03" is says that "C cannot compile executables"
But if I use "./configure CPPFLAGS="" and then "make" tehre are no errors after the configure command
Does this make any sense and is there any reason NOT to do this when the miner seems to work just fine (sometimes better depending on the pool)?
I put a paste up addressing this issue.
http://pastebin.com/iLSck4ES
Please not that I am aware of teh typo re: "CPFLAGS" it was supposed to read "CFLAGS"
Would like some feedback
Thanks
June 26, 2013, 02:11:25 PM
I run cpuminer at ARM CPU and it crashes [...]
I have pushed a fix to the git repo, would you be so kind to test it?
Fixed version of cpuminer was tested and it is OK. Thank you!
June 26, 2013, 05:19:36 AM
there is guide how to install, but please how to configure it and run (for linux noobs) ?
June 24, 2013, 04:40:07 PM
I run cpuminer at ARM CPU and it crashes [...]
Thanks for reporting, using the data you provided I was able to locate a bug that can cause a crash on certain Stratum data, but apparently only when compiling with older versions of gcc. It's not an architecture-dependent bug, though.I have pushed a fix to the git repo, would you be so kind to test it?
June 24, 2013, 02:28:04 AM
I run cpuminer at ARM CPU and it crashes when I try to mine MNC from local p2pool. I tried other scrypt coins on the same ARM machine (Toshiba AC100 running Ubuntu 12.10) with similar configurations and those are OK. cpuminer crashes only when I try to mine MNC from local p2pool. I tried the same configuration at AMD64 and i386 but those work fine. MNC crashes at ARM are 100% repeatable.
Technical details:
Protocol dump:
UPDATE:
I tried to replicate crash at Raspberry PI running Raspbian (ARMv6-compatible processor rev 7 (v6l)) but it runs OK...
$ uname -a
Linux raspberrypi 3.6.11+ #456 PREEMPT Mon May 20 17:42:15 BST 2013 armv6l GNU/Linux
UPDATE2:
When I disable stratum, it works OK at AC100:
Technical details:
Code:
$ minerd -V
cpuminer 2.3.1
libcurl/7.27.0 OpenSSL/1.0.1c zlib/1.2.7 libidn/1.25 librtmp/2.3
$ uname -a
Linux ac100u 3.1.10-6-ac100 #9-Ubuntu SMP Wed Oct 3 16:27:06 UTC 2012 armv7l armv7l armv7l GNU/Linux
$ cat /proc/cpuinfo
Processor : ARMv7 Processor rev 0 (v7l)
processor : 0
BogoMIPS : 1987.37
processor : 1
BogoMIPS : 1987.37
Features : swp half thumb fastmult vfp edsp thumbee vfpv3 vfpv3d16 tls
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x1
CPU part : 0xc09
CPU revision : 0
Hardware : Toshiba AC100 / Dynabook AZ
Revision : 0000
Serial : 0000000000000000
$ minerd -a scrypt -s1 -o http://core.home:9771 -O MKu8qtbgp1oYa4jcwht4BucdJrFxMhc5Tt:x -D
[2013-06-24 08:58:50] 2 miner threads started, using 'scrypt' algorithm.
[2013-06-24 08:58:50] Binding thread 0 to cpu 0
[2013-06-24 08:58:50] Binding thread 1 to cpu 1
[2013-06-24 08:58:50] Starting Stratum on stratum+tcp://core.home:9771
[2013-06-24 08:58:50] Failed to get Stratum session id
[2013-06-24 08:58:50] Stratum difficulty set to 0.144607
[2013-06-24 08:58:50] DEBUG: job_id='144648547319056197500219055794967619236' extranonce2=0000 ntime=51c7ee1b
*** stack smashing detected ***: ./minerd terminated
Aborted (core dumped)
Protocol dump:
Code:
$ minerd -a scrypt -s1 -t1 -o http://core.home:9771 -O MKu8qtbgp1oYa4jcwht4BucdJrFxMhc5Tt:x -DP
[2013-06-24 09:35:16] 1 miner threads started, using 'scrypt' algorithm.
[2013-06-24 09:35:16] JSON protocol request:
{"method": "getwork", "params": [], "id":0}
* About to connect() to core.home port 9771 (#0)
* Trying 192.168.222.9...
* TCP_NODELAY set
* connected
* Connected to core.home (192.168.222.9) port 9771 (#0)
* Server auth using Basic with user 'MKu8qtbgp1oYa4jcwht4BucdJrFxMhc5Tt'
> POST / HTTP/1.1
Authorization: Basic TUt1OHF0YmdwMW9ZYTRqY3dodDRCdWNkSnJGeE1oYzVUdDp4
Host: core.home:9771
Accept-Encoding: deflate, gzip
Content-Type: application/json
Content-Length: 45
User-Agent: cpuminer/2.3.1
X-Mining-Extensions: midstate
* additional stuff not fine transfer.c:1037: 0 0
* additional stuff not fine transfer.c:1037: 0 0
* HTTP 1.1 or later with persistent connection, pipelining supported
< HTTP/1.1 200 OK
< Content-Length: 662
< X-Roll-Ntime: expire=100
< X-Long-Polling: /long-polling
< Server: TwistedWeb/10.2.0
< X-Is-P2pool: true
< X-Stratum: stratum+tcp://core.home:9771
< Date: Mon, 24 Jun 2013 07:35:16 GMT
< Content-Type: application/json
<
* Connection #0 to host core.home left intact
[2013-06-24 09:35:16] JSON protocol response:
{
"result": {
"submitold": true,
"data": "00000001ae7905966717cc474aa4bbcdadd3edb40c23c16c3d688d58b198720e06db5ec5a062a04696a8604fba857d23805ec55e9fc7e498d50b35050862081389b016f151c7f6921d03beb400000000000000800000000000000000000000000000000000000000000000000000000000000000000000000000000080020000",
"hash1": "00000000000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000010000",
"target": "0000000000000000000000000000000000000000000000f4a9a3cd44ca190000",
"identifier": "6936",
"midstate": "46f3a9c53445ef1ea4e1ce9d99a637a39fcff41d09a8b9bb8068f2f07bc1a049"
},
"jsonrpc": "2.0",
"error": null,
"id": 0
}
[2013-06-24 09:35:16] Starting Stratum on stratum+tcp://core.home:9771
* About to connect() to core.home port 9771 (#0)
* Trying 192.168.222.9...
* TCP_NODELAY set
* connected
* Connected to core.home (192.168.222.9) port 9771 (#0)
* Connection #0 to host core.home left intact
[2013-06-24 09:35:16] > {"id": 1, "method": "mining.subscribe", "params": ["cpuminer/2.3.1"]}
[2013-06-24 09:35:16] < {"error": null, "jsonrpc": "2.0", "id": 1, "result": [["mining.notify", "ae6812eb4cd7735a302a8a9dd95cf71f"], "", 2]}
[2013-06-24 09:35:16] Failed to get Stratum session id
[2013-06-24 09:35:16] > {"id": 2, "method": "mining.authorize", "params": ["MKu8qtbgp1oYa4jcwht4BucdJrFxMhc5Tt", "x"]}
[2013-06-24 09:35:16] < {"params": [0.6203833329345798], "jsonrpc": "2.0", "method": "mining.set_difficulty", "id": 69424852}
[2013-06-24 09:35:16] Stratum difficulty set to 0.620383
[2013-06-24 09:35:16] < {"params": ["190974152538387491535221088437790233360", "ae7905966717cc474aa4bbcdadd3edb40c23c16c3d688d58b198720e06db5ec5", "01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff0b03e18d01062f503253482fffffffff0440420f00000000001976a9142c0cdd9704f52e76e5af0ddacb84ee3d2b81efe488acc07fdc0b000000001976a91483a059a9c570a9ce78ebc70cad81f7f1d822721c88ac0000000000000000434104ffd03de44a6e11b9917f3a29f9443283d9871c9d743ef30d5eddcd37094b64d1b3d8090496b53256786bf5c82932ec23c3b74d9f05a6f95a8b5529352656664bac00000000000000002524f35f09e45d5b8f29946da80d4d1124de4d288176ea50502e7ab6f4fcc0cb9ab10200", "00000000", [], "00000001", "1d03beb4", "51c7f692", true], "jsonrpc": "2.0", "method": "mining.notify", "id": 294034871}
[2013-06-24 09:35:16] < {"error": null, "jsonrpc": "2.0", "id": 2, "result": null}
[2013-06-24 09:35:16] DEBUG: job_id='190974152538387491535221088437790233360' extranonce2=0000 ntime=51c7f692
*** stack smashing detected ***: ./minerd terminated
Aborted (core dumped)
UPDATE:
I tried to replicate crash at Raspberry PI running Raspbian (ARMv6-compatible processor rev 7 (v6l)) but it runs OK...
$ uname -a
Linux raspberrypi 3.6.11+ #456 PREEMPT Mon May 20 17:42:15 BST 2013 armv6l GNU/Linux
UPDATE2:
When I disable stratum, it works OK at AC100:
Code:
$ minerd -a scrypt -s1 -t1 -o http://core.home:9771 -O MKu8qtbgp1oYa4jcwht4BucdJrFxMhc5Tt:x --no-stratum -D
[2013-06-24 09:59:59] 1 miner threads started, using 'scrypt' algorithm.
[2013-06-24 09:59:59] Long-polling activated for http://core.home:9771/long-polling
[2013-06-24 09:59:59] DEBUG: got new work in 107 ms
[2013-06-24 10:00:02] LONGPOLL detected new block
[2013-06-24 10:00:02] DEBUG: got new work
[2013-06-24 10:00:02] thread 0: 912 hashes, 0.31 khash/s
...
June 22, 2013, 09:25:36 AM
is this miner optimized for SSE 4.1?
The algorithm implementations don't use any SSE4 instruction. I just didn't find much use for them. 
June 21, 2013, 09:31:03 PM
hi pooler,
is this miner optimized for SSE 4.1?
thanks
is this miner optimized for SSE 4.1?
thanks
June 20, 2013, 04:57:12 AM
ANYTHING that can turn a profit using CPU power will be distributed by malware and labeled as the malware by incompetent AV personell. If you trust the publisher and the checksums match, you need to complain to your AV, not the publisher. If you don't trust the publisher, then you'd better be able to review the source and compile yourself. When the AV still calls it a virus, you'll know how incompetent they are. If you can't do that, you might as well trust the AV and not use the publisher's software, because EVERY version WILL be called a virus.
tldr: recurring FALSE POSITIVES cannot be fixed by anyone other than AV companies who are too incompetent and lazy to do it.
ETA: ANYTHING that can turn a profit using CPU power is POTENTIALLY unwanted, for the same reasons as above and the fact that employees can run it on their employer's computer, using/wasting/stealing excess electricity. If AV says it is potentially unwanted, it is NOT a false positive. In that case, you need to tell your AV software you do want it (via configuration).
tldr: recurring FALSE POSITIVES cannot be fixed by anyone other than AV companies who are too incompetent and lazy to do it.
ETA: ANYTHING that can turn a profit using CPU power is POTENTIALLY unwanted, for the same reasons as above and the fact that employees can run it on their employer's computer, using/wasting/stealing excess electricity. If AV says it is potentially unwanted, it is NOT a false positive. In that case, you need to tell your AV software you do want it (via configuration).
June 20, 2013, 03:40:13 AM
Reiterates its request to release a new version, the online synchronization published MD5, SHA1, SHA256 value that prevent the virus!
Thank you very much
Thank you very much
June 18, 2013, 10:00:53 AM
Virus over there in win32 version.
Known false positive. https://github.com/pooler/cpuminer/issues/13I just bought Haswell is there chance to have some big benefit from AVX2 or TSX, ect in near future?
Yes, and I have plans to work on that. 
June 18, 2013, 09:45:19 AM
this is minerd not cgminer! its for scrypt and sha256d
Oh Thanks! In that case I can probably update it just fine then.
-MarkM-
June 18, 2013, 09:26:30 AM
I just bought Haswell is there chance to have some big benefit from AVX2 or TSX, ect in near future?
June 18, 2013, 09:04:57 AM
Virus over there in win32 version.
June 18, 2013, 05:20:46 AM
Version 2.3.1
The source code is, as always, available at GitHub. Source tarball and binaries are available at Sourceforge.
- Fixed a critical bug that only made SHA-256d mining work correctly with difficulty-1 targets.
- Fixed a compatibility issue with the Stratum implementation in P2Pool ("authentication failed").
- Fixed a bug that only shows up with some Stratum servers (notably the one used by HHTT).
- Added an option to specify a self-signed SSL certificate.
The source code is, as always, available at GitHub. Source tarball and binaries are available at Sourceforge.
June 17, 2013, 10:25:56 AM
I tried git pull on the cgminer-git i am using and saw it was from ckolivas not from pooler.
It also said I am not on a branch abd need to choose a branch.
So now I have to wonder what if any relationship exists between what i was using and this one?
Is this one only for scrypt, maybe? Or does it include all the latest stuff for all the sha256 FPGAs and ASICs and such?
If it doesn't contain the latest stuff I was already using, will it walk over my existing binary or use a new name for its executable so I can continue to use my existing cgminer for what it is already doing and use this one for scrypt?
Or does this one basically obsolete the ckolivas one, containing all its stuff plus this new upgrade for scrypt?
come to that, does it also support the weird new variant scrypts or have the people pushing those not actually made pulls available yet to get their new variants into the mainline code?
(I have been unable to use any of their stuff yet because they seem to plan to walk all over my existing install instead of beign a new separate package.)
-MarkM-
this is minerd not cgminer! its for scrypt and sha256d It also said I am not on a branch abd need to choose a branch.
So now I have to wonder what if any relationship exists between what i was using and this one?
Is this one only for scrypt, maybe? Or does it include all the latest stuff for all the sha256 FPGAs and ASICs and such?
If it doesn't contain the latest stuff I was already using, will it walk over my existing binary or use a new name for its executable so I can continue to use my existing cgminer for what it is already doing and use this one for scrypt?
Or does this one basically obsolete the ckolivas one, containing all its stuff plus this new upgrade for scrypt?
come to that, does it also support the weird new variant scrypts or have the people pushing those not actually made pulls available yet to get their new variants into the mainline code?
(I have been unable to use any of their stuff yet because they seem to plan to walk all over my existing install instead of beign a new separate package.)
-MarkM-
Code:
$ minerd --help
Usage: minerd [OPTIONS]
Options:
-a, --algo=ALGO specify the algorithm to use
scrypt scrypt(1024, 1, 1) (default)
sha256d SHA-256d
-o, --url=URL URL of mining server (default: http://127.0.0.1:9332/)
-O, --userpass=U:P username:password pair for mining server
-u, --user=USERNAME username for mining server
-p, --pass=PASSWORD password for mining server
--cert=FILE certificate for mining server using SSL
-x, --proxy=[PROTOCOL://]HOST[:PORT] connect through a proxy
-t, --threads=N number of miner threads (default: number of processors)
-r, --retries=N number of times to retry if a network call fails
(default: retry indefinitely)
-R, --retry-pause=N time to pause between retries, in seconds (default: 30)
-T, --timeout=N network timeout, in seconds (default: 270)
-s, --scantime=N upper bound on time spent scanning current work when
long polling is unavailable, in seconds (default: 5)
--no-longpoll disable X-Long-Polling support
--no-stratum disable X-Stratum support
-q, --quiet disable per-thread hashmeter output
-D, --debug enable debug output
-P, --protocol-dump verbose dump of protocol-level activities
-S, --syslog use system log for output messages
-B, --background run the miner in the background
--benchmark run in offline benchmark mode
-c, --config=FILE load a JSON-format configuration file
-V, --version display version information and exit
-h, --help display this help text and exit
June 17, 2013, 09:50:33 AM
I tried git pull on the cgminer-git i am using and saw it was from ckolivas not from pooler.
It also said I am not on a branch abd need to choose a branch.
So now I have to wonder what if any relationship exists between what i was using and this one?
Is this one only for scrypt, maybe? Or does it include all the latest stuff for all the sha256 FPGAs and ASICs and such?
If it doesn't contain the latest stuff I was already using, will it walk over my existing binary or use a new name for its executable so I can continue to use my existing cgminer for what it is already doing and use this one for scrypt?
Or does this one basically obsolete the ckolivas one, containing all its stuff plus this new upgrade for scrypt?
come to that, does it also support the weird new variant scrypts or have the people pushing those not actually made pulls available yet to get their new variants into the mainline code?
(I have been unable to use any of their stuff yet because they seem to plan to walk all over my existing install instead of beign a new separate package.)
-MarkM-
It also said I am not on a branch abd need to choose a branch.
So now I have to wonder what if any relationship exists between what i was using and this one?
Is this one only for scrypt, maybe? Or does it include all the latest stuff for all the sha256 FPGAs and ASICs and such?
If it doesn't contain the latest stuff I was already using, will it walk over my existing binary or use a new name for its executable so I can continue to use my existing cgminer for what it is already doing and use this one for scrypt?
Or does this one basically obsolete the ckolivas one, containing all its stuff plus this new upgrade for scrypt?
come to that, does it also support the weird new variant scrypts or have the people pushing those not actually made pulls available yet to get their new variants into the mainline code?
(I have been unable to use any of their stuff yet because they seem to plan to walk all over my existing install instead of beign a new separate package.)
-MarkM-
June 17, 2013, 07:17:45 AM
Thank you very much.
So is it possible for you to publish the binaries, please?
So is it possible for you to publish the binaries, please?
June 17, 2013, 06:02:15 AM
Code:
minerd -a scrypt -t1 -o http://p2pool.org:9327 -O Lc8TWMiKM7gRUrG8VB8pPNP1Yvt1SGZnoH:x -D
[2013-06-16 20:54:01] 1 miner threads started, using 'scrypt' algorithm.
[2013-06-16 20:54:03] Starting Stratum on stratum+tcp://p2pool.org:9327
[2013-06-16 20:54:04] Failed to get Stratum session id
[2013-06-16 20:54:04] Stratum difficulty set to 308.794
[2013-06-16 20:54:04] Stratum authentication failed
[2013-06-16 20:54:04] ...retry after 30 seconds
I have found the problem. P2Pool returns a result of null in response to stratum.authorize.
As far as I know, the Stratum protocol specification only defines true and false as meaningful results for that method, and this is why cpuminer 2.3 requires a result of true in response to stratum.authorize.
This should now be fixed in the git repo. The miner now only considers a result of false as an authentication error.
June 16, 2013, 07:32:38 PM
thank you for your reply.
yes,add --no-stratum can do, but In this way, I can not use stratum,yes?
however, cgminer can connect to stratum+tcp://p2pool.org, cpuminer shows connection error
why this?
thank you very much
yes,add --no-stratum can do, but In this way, I can not use stratum,yes?
however, cgminer can connect to stratum+tcp://p2pool.org, cpuminer shows connection error
why this?
thank you very much
Jump to: