Pages:
Author

Topic: [ANN] 1GH.COM - HVC / MAX / MMC / PTS / VIA Anonymous Pool ★ - page 2. (Read 75205 times)

sr. member
Activity: 462
Merit: 250
I just downloaded the latest Windows built 64bit minerd and it does not work. It has the same problem above.  I did not try the 32bit minerd.
Sorry, this must be now something on your side this time: there are about 1000 nodes mining on xcnpool-apac right now, tests show it is accessible too.
newbie
Activity: 50
Merit: 0

It does not match. Single CPU on dedicated address makes 340 khash in minerd, never shown more than 290 in pool (that is maximum), average hashrate @pool is around 250 khash. Boooo vs Yay Smiley is that Boooo-s are 7,8%
We have started a server stratum+tcp://xcnpool-apac.1gh.com:7333 now, would you please kindly let me know if this one shows better results for you.

can't connect to the server

[2014-08-04 09:03:57] Stratum connection failed: Resolving timed out after 30539 milliseconds
[2014-08-04 09:03:57] ...retry after 5 seconds

I have just rechecked:
[2014-08-04 05:06:58] Starting Stratum on stratum+tcp://xcnpool-apac.1gh.com:7333
[2014-08-04 05:06:58] 4 miner threads started, using 'm7' algorithm.
[2014-08-04 05:07:08] thread 1: 262144 hashes, 30.36 khash/s

It also only makes sense to use this server if you have better ping to it than to xcnpool.1gh.com

I got similar error.

[2014-08-05 02:20:07] 2 miner threads started, using 'm7' algorithm.
[2014-08-05 02:20:07] Starting Stratum on stratum+tcp://xcnpool-apac.1gh.com:7333
[2014-08-05 02:20:07] Binding thread 1 to cpu 1
[2014-08-05 02:20:07] Binding thread 0 to cpu 0
[2014-08-05 02:20:28] Stratum connection failed: Failed to connect to xcnpool-apac.1gh.com port 7333: Timed out
[2014-08-05 02:20:28] ...retry after 30 seconds

Would you please try now?

I just downloaded the latest Windows built 64bit minerd and it does not work. It has the same problem above.  I did not try the 32bit minerd.
sr. member
Activity: 328
Merit: 250
Pinging xcnpool.1gh.com [142.4.218.34] with 32 bytes of data:
Reply from 142.4.218.34: bytes=32 time=161ms TTL=50
Reply from 142.4.218.34: bytes=32 time=148ms TTL=50
Reply from 142.4.218.34: bytes=32 time=159ms TTL=50
Reply from 142.4.218.34: bytes=32 time=155ms TTL=50

Ping statistics for 142.4.218.34:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 148ms, Maximum = 161ms, Average = 155ms


We have now tuned servers to request a lot more shares of lower diff, to reduce stales. Please tell if it has helped.

Latest changes = improvements. Will observe more.
hero member
Activity: 979
Merit: 510
Has improved, getting 84% of expected hash rate, accounting for bad shares(which are now only 4-5%)
[2014-08-05 00:48:41] accepted: 905/944 (95.87%), 425.24 khash/s (yay!!!)
Edit: 88%~ currently, so things are improving.
member
Activity: 71
Merit: 10
Wayla is sometimes a man!
Thanks for the pool Smiley only one working right now.

However I'm only getting 65% of my hashrate on the pool, accounting for bad shares as well(9%).
This 250KH is max on the pool I've seen, dips down to 220 at times.
Miner is showing 422KH +-15KH.
This is over the past hour, and is just 1 computer.
Edit: Also is there a way to set a custom difficulty ?

[2014-08-04 19:05:07] accepted: 591/640 (92.34%), 427.29 khash/s (yay!!!)
[2014-08-04 19:05:10] thread 6: 117584 hashes, 53.48 khash/s
[2014-08-04 19:05:10] accepted: 592/641 (92.36%), 427.32 khash/s (yay!!!)
[2014-08-04 19:05:12] thread 2: 259656 hashes, 53.48 khash/s
[2014-08-04 19:05:12] accepted: 593/642 (92.37%), 427.33 khash/s (yay!!!)
[2014-08-04 19:05:12] thread 2: 46541 hashes, 53.48 khash/s
[2014-08-04 19:05:13] accepted: 594/643 (92.38%), 427.33 khash/s (yay!!!)
[2014-08-04 19:05:13] thread 0: 345698 hashes, 52.49 khash/s
[2014-08-04 19:05:13] accepted: 595/644 (92.39%), 427.07 khash/s (yay!!!)
[2014-08-04 19:05:17] thread 6: 397927 hashes, 53.47 khash/s
[2014-08-04 19:05:17] accepted: 596/645 (92.40%), 427.05 khash/s (yay!!!)
[2014-08-04 19:05:17] thread 0: 214610 hashes, 52.76 khash/s
[2014-08-04 19:05:17] accepted: 597/646 (92.41%), 427.32 khash/s (yay!!!)
[2014-08-04 19:05:22] thread 1: 791102 hashes, 53.55 khash/s
[2014-08-04 19:05:22] accepted: 598/647 (92.43%), 427.31 khash/s (yay!!!)


Please tell if this has improved now.

yes ,improved.
sr. member
Activity: 462
Merit: 250
Thanks for the pool Smiley only one working right now.

However I'm only getting 65% of my hashrate on the pool, accounting for bad shares as well(9%).
This 250KH is max on the pool I've seen, dips down to 220 at times.
Miner is showing 422KH +-15KH.
This is over the past hour, and is just 1 computer.
Edit: Also is there a way to set a custom difficulty ?

[2014-08-04 19:05:07] accepted: 591/640 (92.34%), 427.29 khash/s (yay!!!)
[2014-08-04 19:05:10] thread 6: 117584 hashes, 53.48 khash/s
[2014-08-04 19:05:10] accepted: 592/641 (92.36%), 427.32 khash/s (yay!!!)
[2014-08-04 19:05:12] thread 2: 259656 hashes, 53.48 khash/s
[2014-08-04 19:05:12] accepted: 593/642 (92.37%), 427.33 khash/s (yay!!!)
[2014-08-04 19:05:12] thread 2: 46541 hashes, 53.48 khash/s
[2014-08-04 19:05:13] accepted: 594/643 (92.38%), 427.33 khash/s (yay!!!)
[2014-08-04 19:05:13] thread 0: 345698 hashes, 52.49 khash/s
[2014-08-04 19:05:13] accepted: 595/644 (92.39%), 427.07 khash/s (yay!!!)
[2014-08-04 19:05:17] thread 6: 397927 hashes, 53.47 khash/s
[2014-08-04 19:05:17] accepted: 596/645 (92.40%), 427.05 khash/s (yay!!!)
[2014-08-04 19:05:17] thread 0: 214610 hashes, 52.76 khash/s
[2014-08-04 19:05:17] accepted: 597/646 (92.41%), 427.32 khash/s (yay!!!)
[2014-08-04 19:05:22] thread 1: 791102 hashes, 53.55 khash/s
[2014-08-04 19:05:22] accepted: 598/647 (92.43%), 427.31 khash/s (yay!!!)


Please tell if this has improved now.
hero member
Activity: 979
Merit: 510
Thanks for the pool Smiley only one working right now.

However I'm only getting 65% of my hashrate on the pool, accounting for bad shares as well(9%).
This 250KH is max on the pool I've seen, dips down to 220 at times.
Miner is showing 422KH +-15KH.
This is over the past hour, and is just 1 computer.
Edit: Also is there a way to set a custom difficulty ?

[2014-08-04 19:05:07] accepted: 591/640 (92.34%), 427.29 khash/s (yay!!!)
[2014-08-04 19:05:10] thread 6: 117584 hashes, 53.48 khash/s
[2014-08-04 19:05:10] accepted: 592/641 (92.36%), 427.32 khash/s (yay!!!)
[2014-08-04 19:05:12] thread 2: 259656 hashes, 53.48 khash/s
[2014-08-04 19:05:12] accepted: 593/642 (92.37%), 427.33 khash/s (yay!!!)
[2014-08-04 19:05:12] thread 2: 46541 hashes, 53.48 khash/s
[2014-08-04 19:05:13] accepted: 594/643 (92.38%), 427.33 khash/s (yay!!!)
[2014-08-04 19:05:13] thread 0: 345698 hashes, 52.49 khash/s
[2014-08-04 19:05:13] accepted: 595/644 (92.39%), 427.07 khash/s (yay!!!)
[2014-08-04 19:05:17] thread 6: 397927 hashes, 53.47 khash/s
[2014-08-04 19:05:17] accepted: 596/645 (92.40%), 427.05 khash/s (yay!!!)
[2014-08-04 19:05:17] thread 0: 214610 hashes, 52.76 khash/s
[2014-08-04 19:05:17] accepted: 597/646 (92.41%), 427.32 khash/s (yay!!!)
[2014-08-04 19:05:22] thread 1: 791102 hashes, 53.55 khash/s
[2014-08-04 19:05:22] accepted: 598/647 (92.43%), 427.31 khash/s (yay!!!)
newbie
Activity: 50
Merit: 0

It does not match. Single CPU on dedicated address makes 340 khash in minerd, never shown more than 290 in pool (that is maximum), average hashrate @pool is around 250 khash. Boooo vs Yay Smiley is that Boooo-s are 7,8%
We have started a server stratum+tcp://xcnpool-apac.1gh.com:7333 now, would you please kindly let me know if this one shows better results for you.

can't connect to the server

[2014-08-04 09:03:57] Stratum connection failed: Resolving timed out after 30539 milliseconds
[2014-08-04 09:03:57] ...retry after 5 seconds

I have just rechecked:
[2014-08-04 05:06:58] Starting Stratum on stratum+tcp://xcnpool-apac.1gh.com:7333
[2014-08-04 05:06:58] 4 miner threads started, using 'm7' algorithm.
[2014-08-04 05:07:08] thread 1: 262144 hashes, 30.36 khash/s

It also only makes sense to use this server if you have better ping to it than to xcnpool.1gh.com

I got similar error.

[2014-08-05 02:20:07] 2 miner threads started, using 'm7' algorithm.
[2014-08-05 02:20:07] Starting Stratum on stratum+tcp://xcnpool-apac.1gh.com:7333
[2014-08-05 02:20:07] Binding thread 1 to cpu 1
[2014-08-05 02:20:07] Binding thread 0 to cpu 0
[2014-08-05 02:20:28] Stratum connection failed: Failed to connect to xcnpool-apac.1gh.com port 7333: Timed out
[2014-08-05 02:20:28] ...retry after 30 seconds

Would you please try now?

It works!  Thanks!
sr. member
Activity: 462
Merit: 250

It does not match. Single CPU on dedicated address makes 340 khash in minerd, never shown more than 290 in pool (that is maximum), average hashrate @pool is around 250 khash. Boooo vs Yay Smiley is that Boooo-s are 7,8%
We have started a server stratum+tcp://xcnpool-apac.1gh.com:7333 now, would you please kindly let me know if this one shows better results for you.

can't connect to the server

[2014-08-04 09:03:57] Stratum connection failed: Resolving timed out after 30539 milliseconds
[2014-08-04 09:03:57] ...retry after 5 seconds

I have just rechecked:
[2014-08-04 05:06:58] Starting Stratum on stratum+tcp://xcnpool-apac.1gh.com:7333
[2014-08-04 05:06:58] 4 miner threads started, using 'm7' algorithm.
[2014-08-04 05:07:08] thread 1: 262144 hashes, 30.36 khash/s

It also only makes sense to use this server if you have better ping to it than to xcnpool.1gh.com

I got similar error.

[2014-08-05 02:20:07] 2 miner threads started, using 'm7' algorithm.
[2014-08-05 02:20:07] Starting Stratum on stratum+tcp://xcnpool-apac.1gh.com:7333
[2014-08-05 02:20:07] Binding thread 1 to cpu 1
[2014-08-05 02:20:07] Binding thread 0 to cpu 0
[2014-08-05 02:20:28] Stratum connection failed: Failed to connect to xcnpool-apac.1gh.com port 7333: Timed out
[2014-08-05 02:20:28] ...retry after 30 seconds

Would you please try now?
newbie
Activity: 50
Merit: 0

It does not match. Single CPU on dedicated address makes 340 khash in minerd, never shown more than 290 in pool (that is maximum), average hashrate @pool is around 250 khash. Boooo vs Yay Smiley is that Boooo-s are 7,8%
We have started a server stratum+tcp://xcnpool-apac.1gh.com:7333 now, would you please kindly let me know if this one shows better results for you.

can't connect to the server

[2014-08-04 09:03:57] Stratum connection failed: Resolving timed out after 30539 milliseconds
[2014-08-04 09:03:57] ...retry after 5 seconds

I have just rechecked:
[2014-08-04 05:06:58] Starting Stratum on stratum+tcp://xcnpool-apac.1gh.com:7333
[2014-08-04 05:06:58] 4 miner threads started, using 'm7' algorithm.
[2014-08-04 05:07:08] thread 1: 262144 hashes, 30.36 khash/s

It also only makes sense to use this server if you have better ping to it than to xcnpool.1gh.com

I got similar error.

[2014-08-05 02:20:07] 2 miner threads started, using 'm7' algorithm.
[2014-08-05 02:20:07] Starting Stratum on stratum+tcp://xcnpool-apac.1gh.com:7333
[2014-08-05 02:20:07] Binding thread 1 to cpu 1
[2014-08-05 02:20:07] Binding thread 0 to cpu 0
[2014-08-05 02:20:28] Stratum connection failed: Failed to connect to xcnpool-apac.1gh.com port 7333: Timed out
[2014-08-05 02:20:28] ...retry after 30 seconds
sr. member
Activity: 308
Merit: 250
too much booo

Code:
[2014-08-04 17:36:10] thread 15: 270890 hashes, 53.32 khash/s
[2014-08-04 17:36:10] accepted: 1321/1435 (92.06%), 1705 khash/s (booooo)
[2014-08-04 17:36:10] thread 27: 287312 hashes, 53.32 khash/s
[2014-08-04 17:36:10] accepted: 1321/1436 (91.99%), 1705 khash/s (booooo)
[2014-08-04 17:36:10] thread 29: 295578 hashes, 53.19 khash/s
[2014-08-04 17:36:10] accepted: 1321/1437 (91.93%), 1705 khash/s (booooo)
[2014-08-04 17:36:12] thread 7: 391266 hashes, 53.21 khash/s
[2014-08-04 17:36:12] accepted: 1321/1438 (91.86%), 1705 khash/s (booooo)
[2014-08-04 17:36:13] thread 25: 432171 hashes, 53.32 khash/s
[2014-08-04 17:36:13] accepted: 1321/1439 (91.80%), 1705 khash/s (booooo)
[2014-08-04 17:36:13] thread 30: 435857 hashes, 53.22 khash/s
[2014-08-04 17:36:13] accepted: 1321/1440 (91.74%), 1705 khash/s (booooo)
[2014-08-04 17:36:13] thread 0: 451181 hashes, 53.28 khash/s
[2014-08-04 17:36:13] accepted: 1321/1441 (91.67%), 1705 khash/s (booooo)
[2014-08-04 17:36:14] thread 19: 474800 hashes, 53.31 khash/s
[2014-08-04 17:36:14] accepted: 1321/1442 (91.61%), 1705 khash/s (booooo)
[2014-08-04 17:36:14] thread 9: 482600 hashes, 53.35 khash/s
[2014-08-04 17:36:14] accepted: 1321/1443 (91.55%), 1705 khash/s (booooo)
newbie
Activity: 49
Merit: 0

Code:
[2014-08-04 11:11:45] thread 16: 3179920 hashes, 52.98 khash/s
[2014-08-04 11:11:45] thread 29: 3179943 hashes, 52.98 khash/s
[2014-08-04 11:11:45] thread 21: 3178083 hashes, 52.94 khash/s
[2014-08-04 11:11:45] thread 26: 3182991 hashes, 53.03 khash/s
[2014-08-04 11:11:45] thread 28: 3184239 hashes, 53.04 khash/s
[2014-08-04 11:11:45] thread 0: 3180678 hashes, 52.98 khash/s
[2014-08-04 11:11:45] thread 8: 3185592 hashes, 53.05 khash/s
[2014-08-04 11:11:45] thread 7: 3176664 hashes, 52.90 khash/s
[2014-08-04 11:11:45] thread 6: 3180061 hashes, 52.96 khash/s
[2014-08-04 11:11:45] thread 23: 3178024 hashes, 52.91 khash/s
[2014-08-04 11:11:45] thread 14: 3179769 hashes, 52.93 khash/s
[2014-08-04 11:11:45] thread 30: 3179639 hashes, 52.92 khash/s
[2014-08-04 11:11:49] thread 31: 3179764 hashes, 53.03 khash/s
[2014-08-04 11:11:52] thread 27: 3177642 hashes, 53.00 khash/s
[2014-08-04 11:11:58] thread 2: 3178923 hashes, 53.03 khash/s
[2014-08-04 11:12:04] thread 4: 3175476 hashes, 52.93 khash/s
[2014-08-04 11:12:09] thread 3: 1297180 hashes, 52.95 khash/s
[2014-08-04 11:12:09] accepted: 63/67 (94.03%), 1696 khash/s (yay!!!)
[2014-08-04 11:12:10] thread 5: 3175717 hashes, 52.94 khash/s

But when I mine with one server - all ok.

This means your vardiff value has hiked too high. Please append unique suffixes to your workers usernames/addresses, for example, 'WALLET.SERVER1', 'WALLET.SERVER2' and so on so that they get a better vardiff each. Your displayed statistics will still be combined over all workers this way.

it's working!thank you very much
sr. member
Activity: 462
Merit: 250

Code:
[2014-08-04 11:11:45] thread 16: 3179920 hashes, 52.98 khash/s
[2014-08-04 11:11:45] thread 29: 3179943 hashes, 52.98 khash/s
[2014-08-04 11:11:45] thread 21: 3178083 hashes, 52.94 khash/s
[2014-08-04 11:11:45] thread 26: 3182991 hashes, 53.03 khash/s
[2014-08-04 11:11:45] thread 28: 3184239 hashes, 53.04 khash/s
[2014-08-04 11:11:45] thread 0: 3180678 hashes, 52.98 khash/s
[2014-08-04 11:11:45] thread 8: 3185592 hashes, 53.05 khash/s
[2014-08-04 11:11:45] thread 7: 3176664 hashes, 52.90 khash/s
[2014-08-04 11:11:45] thread 6: 3180061 hashes, 52.96 khash/s
[2014-08-04 11:11:45] thread 23: 3178024 hashes, 52.91 khash/s
[2014-08-04 11:11:45] thread 14: 3179769 hashes, 52.93 khash/s
[2014-08-04 11:11:45] thread 30: 3179639 hashes, 52.92 khash/s
[2014-08-04 11:11:49] thread 31: 3179764 hashes, 53.03 khash/s
[2014-08-04 11:11:52] thread 27: 3177642 hashes, 53.00 khash/s
[2014-08-04 11:11:58] thread 2: 3178923 hashes, 53.03 khash/s
[2014-08-04 11:12:04] thread 4: 3175476 hashes, 52.93 khash/s
[2014-08-04 11:12:09] thread 3: 1297180 hashes, 52.95 khash/s
[2014-08-04 11:12:09] accepted: 63/67 (94.03%), 1696 khash/s (yay!!!)
[2014-08-04 11:12:10] thread 5: 3175717 hashes, 52.94 khash/s

But when I mine with one server - all ok.

This means your vardiff value has hiked too high. Please append unique suffixes to your workers usernames/addresses, for example, 'WALLET.SERVER1', 'WALLET.SERVER2' and so on so that they get a better vardiff each. Your displayed statistics will still be combined over all workers this way.
sr. member
Activity: 308
Merit: 250
Pinging xcnpool.1gh.com [142.4.218.34] with 32 bytes of data:
Reply from 142.4.218.34: bytes=32 time=161ms TTL=50
Reply from 142.4.218.34: bytes=32 time=148ms TTL=50
Reply from 142.4.218.34: bytes=32 time=159ms TTL=50
Reply from 142.4.218.34: bytes=32 time=155ms TTL=50

Ping statistics for 142.4.218.34:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 148ms, Maximum = 161ms, Average = 155ms


We have now tuned servers to request a lot more shares of lower diff, to reduce stales. Please tell if it has helped.


after 20 minutes..



Code:
[2014-08-04 10:15:07] accepted: 167/179 (93.30%), 1689 khash/s (yay!!!)
[2014-08-04 10:15:08] thread 31: 385704 hashes, 52.82 khash/s
[2014-08-04 10:15:08] accepted: 168/180 (93.33%), 1689 khash/s (yay!!!)
[2014-08-04 10:15:16] thread 22: 2428844 hashes, 52.73 khash/s
[2014-08-04 10:15:17] thread 9: 909500 hashes, 52.85 khash/s
[2014-08-04 10:15:17] accepted: 169/181 (93.37%), 1689 khash/s (yay!!!)

Please try again now, share difficulty reduced twice on the pool.

I have 50+ servers and can't mine with your pool.

Code:
[2014-08-04 11:11:45] thread 16: 3179920 hashes, 52.98 khash/s
[2014-08-04 11:11:45] thread 29: 3179943 hashes, 52.98 khash/s
[2014-08-04 11:11:45] thread 21: 3178083 hashes, 52.94 khash/s
[2014-08-04 11:11:45] thread 26: 3182991 hashes, 53.03 khash/s
[2014-08-04 11:11:45] thread 28: 3184239 hashes, 53.04 khash/s
[2014-08-04 11:11:45] thread 0: 3180678 hashes, 52.98 khash/s
[2014-08-04 11:11:45] thread 8: 3185592 hashes, 53.05 khash/s
[2014-08-04 11:11:45] thread 7: 3176664 hashes, 52.90 khash/s
[2014-08-04 11:11:45] thread 6: 3180061 hashes, 52.96 khash/s
[2014-08-04 11:11:45] thread 23: 3178024 hashes, 52.91 khash/s
[2014-08-04 11:11:45] thread 14: 3179769 hashes, 52.93 khash/s
[2014-08-04 11:11:45] thread 30: 3179639 hashes, 52.92 khash/s
[2014-08-04 11:11:49] thread 31: 3179764 hashes, 53.03 khash/s
[2014-08-04 11:11:52] thread 27: 3177642 hashes, 53.00 khash/s
[2014-08-04 11:11:58] thread 2: 3178923 hashes, 53.03 khash/s
[2014-08-04 11:12:04] thread 4: 3175476 hashes, 52.93 khash/s
[2014-08-04 11:12:09] thread 3: 1297180 hashes, 52.95 khash/s
[2014-08-04 11:12:09] accepted: 63/67 (94.03%), 1696 khash/s (yay!!!)
[2014-08-04 11:12:10] thread 5: 3175717 hashes, 52.94 khash/s

But when I mine with one server - all ok.
sr. member
Activity: 462
Merit: 250
Pinging xcnpool.1gh.com [142.4.218.34] with 32 bytes of data:
Reply from 142.4.218.34: bytes=32 time=161ms TTL=50
Reply from 142.4.218.34: bytes=32 time=148ms TTL=50
Reply from 142.4.218.34: bytes=32 time=159ms TTL=50
Reply from 142.4.218.34: bytes=32 time=155ms TTL=50

Ping statistics for 142.4.218.34:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 148ms, Maximum = 161ms, Average = 155ms


We have now tuned servers to request a lot more shares of lower diff, to reduce stales. Please tell if it has helped.
sr. member
Activity: 328
Merit: 250
Pinging xcnpool.1gh.com [142.4.218.34] with 32 bytes of data:
Reply from 142.4.218.34: bytes=32 time=161ms TTL=50
Reply from 142.4.218.34: bytes=32 time=148ms TTL=50
Reply from 142.4.218.34: bytes=32 time=159ms TTL=50
Reply from 142.4.218.34: bytes=32 time=155ms TTL=50

Ping statistics for 142.4.218.34:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 148ms, Maximum = 161ms, Average = 155ms

sr. member
Activity: 462
Merit: 250
who has some idea on this issue?

After LIBCURL="-lcurldll" ./configure CFLAGS="-O3"

checking gmp.h usability... yes
checking gmp.h presence... yes
checking for gmp.h... yes
./configure: line 5726: syntax error near unexpected token `,'
./configure: line 5726: `LIBCURL_CHECK_CONFIG(, 7.15.2, ,'

RHEL 6.5
-bash-4.1# uname -a
Linux 2.6.32-431.el6.x86_64 #1 SMP Sun Nov 10 22:19:54 EST 2013 x86_64 x86_64 x86_64 GNU/Linux

BTW,can 1gh provide a miner which compiled well on rhel 6.X ? Kiss
'yum install libcurl-devel' might help. You will need gmp-devel too btw.

Precompiled binaries for Linux make really little sense as they are going to be big and not optimized for specific CPU as they are when you build locally.
newbie
Activity: 1
Merit: 0
who has some idea on this issue?

After LIBCURL="-lcurldll" ./configure CFLAGS="-O3"

checking gmp.h usability... yes
checking gmp.h presence... yes
checking for gmp.h... yes
./configure: line 5726: syntax error near unexpected token `,'
./configure: line 5726: `LIBCURL_CHECK_CONFIG(, 7.15.2, ,'

RHEL 6.5
-bash-4.1# uname -a
Linux 2.6.32-431.el6.x86_64 #1 SMP Sun Nov 10 22:19:54 EST 2013 x86_64 x86_64 x86_64 GNU/Linux

BTW,can 1gh provide a miner which compiled well on rhel 6.X ? Kiss
sr. member
Activity: 462
Merit: 250

It does not match. Single CPU on dedicated address makes 340 khash in minerd, never shown more than 290 in pool (that is maximum), average hashrate @pool is around 250 khash. Boooo vs Yay Smiley is that Boooo-s are 7,8%
We have started a server stratum+tcp://xcnpool-apac.1gh.com:7333 now, would you please kindly let me know if this one shows better results for you.

can't connect to the server

[2014-08-04 09:03:57] Stratum connection failed: Resolving timed out after 30539 milliseconds
[2014-08-04 09:03:57] ...retry after 5 seconds

I have just rechecked:
[2014-08-04 05:06:58] Starting Stratum on stratum+tcp://xcnpool-apac.1gh.com:7333
[2014-08-04 05:06:58] 4 miner threads started, using 'm7' algorithm.
[2014-08-04 05:07:08] thread 1: 262144 hashes, 30.36 khash/s

It also only makes sense to use this server if you have better ping to it than to xcnpool.1gh.com
member
Activity: 71
Merit: 10
Wayla is sometimes a man!

It does not match. Single CPU on dedicated address makes 340 khash in minerd, never shown more than 290 in pool (that is maximum), average hashrate @pool is around 250 khash. Boooo vs Yay Smiley is that Boooo-s are 7,8%
We have started a server stratum+tcp://xcnpool-apac.1gh.com:7333 now, would you please kindly let me know if this one shows better results for you.

can't connect to the server

[2014-08-04 09:03:57] Stratum connection failed: Resolving timed out after 30539 milliseconds
[2014-08-04 09:03:57] ...retry after 5 seconds
Pages:
Jump to: