Arux
|
|
October 16, 2015, 01:25:15 PM |
|
700 h/s for a 7950, it's much more efficient than win build. i uploaded my (nasty) build on https://github.com/Arux-BTT/wolf-aeon-miner/releases. only if someone want to test without compiling itself i used mingw-w64. to achieve compilation, i added #include <ws2tcpip.h> into main.c and -lws2_32 into Makefile
|
|
|
|
Shrikez
|
|
October 16, 2015, 02:38:25 PM |
|
Arux thank you for the instructions. Unfortunately I still can't get it to run. the relevant part in makefile is: CC = gcc LD = gcc CFLAGS = -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -std=c11 -pthread -c -I./include/ LDFLAGS = -pthread -O0 -ggdb3 LIBS = -ljansson -Wl,./lib/x86_64/sdk/libOpenCL.so -ldl but when running the miner it still seems to be referring to /usr/lib/etc. instead of the AMD SDK bit I included in the miner folder. Error: ./miner: /usr/lib/x86_64-linux-gnu/libOpenCL.so.1: version `OPENCL_2.0' not found (required by ./miner) I checked the relevant path and all but.... I'm still kind of newbish on Linux so I hope in someone helping me out. Thank you!
|
Die Würde des Menschen ist unantastbar
|
|
|
Arux
|
|
October 16, 2015, 09:26:56 PM |
|
@Shrikez: perhaps your catalyst version (fglrx) is too old. for opencl 2.0, you need at least catalyst 14.12 (=14.501) or above to use and SDK 3.0 to compile check catalyst with: ls /var/lib/dkms/fglrx/ or ls /usr/src/fglrx* and to verify if your OpenCL library path is ok, locate it sudo updatedb locate libOpenCL.so
|
|
|
|
languagehasmeaning
|
|
October 16, 2015, 11:03:11 PM |
|
Are there any estimates about the an official GUI will be ready? Is AEON also interested in the CT discussions from /r/Monero?
|
|
|
|
nioc
Legendary
Offline
Activity: 1624
Merit: 1008
|
|
October 16, 2015, 11:41:59 PM |
|
I am now running a Monero node using the 0.9 beta version which is using almost no resources. Can I run an Aeon node at the same time? My comp is not very powerful but it does not have much problem running Aeon. My internet connection is 30 Mbs down and 5 Mbs up and is hardwired if it makes a difference.
If you can run AEON by itself then yes you can very likely run AEON along with Monero 0.9. Yes I ran them both with no issues. I will start Aeon again after I deal with restoring my Monero wallets.
|
|
|
|
generalizethis
Legendary
Offline
Activity: 1750
Merit: 1036
Facts are more efficient than fud
|
|
October 17, 2015, 03:58:40 AM |
|
Any plans in the works for a web-wallet?
|
|
|
|
Arux
|
|
October 17, 2015, 09:24:08 AM |
|
some rejected with win64 gpu miner pool side: 2015-10-16 13:14:24 [pool] (Thread 1) Rejected low difficulty share of 3 from WmsSW.....8PqRiNs@xx.xx.xx.xx 2015-10-16 13:14:24 [pool] (Thread 1) Share trust broken by WmsSW.....8PqRiNs@xx.xx.xx.xx 2015-10-16 13:14:25 [pool] (Thread 1) height 618179, light 1 2015-10-16 13:14:25 [pool] (Thread 1) Rejected low difficulty share of 7 from WmsSW.....8PqRiNs@xx.xx.xx.xx 2015-10-16 13:14:25 [pool] (Thread 1) Share trust broken by WmsSW.....8PqRiNs@xx.xx.xx.xx miner side: [15:13:18] Share accepted: 5/5 (100.00%) [15:13:18] Total Hashrate: 473.96H/s [15:13:22] Thread 0: SHARE found (nonce 0x000028FC)! [15:13:22] Thread 0: SHARE found (nonce 0x00002E87)! [15:13:22] Thread 0: 479.06H/s [15:13:22] Got something:{"jsonrpc":"2.0","method":"job","params":"blob":"0100f1ef83b10536db560eb216ca3dc929e5d8bdc246ba8babc8983b63c73d87db7bdfe0860ceb0000000008d0c221c867ecce6e795b20e00ea01c9fad98b92e2f50e11842e16e0fee2b801","job_id":"159169602952897","target":"4d621000"}} [15:13:22] Pool requested miner discard all previous work - probably new block on the network. [15:13:22] Request: {"method": "submit", "params": {"id": "293719172803685", "job_id": "159169602952897", "nonce": "fc280000","result": "05832f9750ccd0e0d3ceda8be48084cf230b15acb0d1be3f49edc98d7e6f9342"}, "id": 1} [15:13:22] Request: {"method": "submit", "params": {"id": "293719172803685", "job_id": "159169602952897", "nonce": "872e0000", "result": "550885d78982dfbe4813585fa95558e7a3e6aea95797d3a116439c246d6f5924"}, "id": 1} [15:13:22] Got something: {"id":1,"jsonrpc":"2.0","error":{"code":-1,"message":"Low difficulty share"}} [15:13:22] Share rejected ((null)): 6/7 (85.71%) [15:13:22] Total Hashrate: 479.06H/s [15:13:22] Got something: {"id":1,"jsonrpc":"2.0","error":{"code":-1,"message":"Low difficulty share"}} [15:13:22] Share rejected ((null)): 5/7 (71.43%) [15:13:22] Total Hashrate: 479.06H/s [15:13:26] Thread 0: 479.18H/s [15:13:26] Detected new job, regenerating work. [15:13:30] Thread 0: 479.06H/s [15:13:34] Thread 0: 480.98H/s [15:13:39] Thread 0: SHARE found (nonce 0x00001781)! [15:13:39] Thread 0: 479.18H/s [15:13:39] Request: {"method": "submit", "params": {"id": "293719172803685", "job_id": "159169602952897", "nonce": "81170000", "result": "d0bb1cbe2fea1d8a42e673b2ca7ab38231a3183b32eb34505874e6b50fc90b00"}, "id": 1} [15:13:39] Got something: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"OK"}} [15:13:39] Share accepted: 6/8 (75.00%) [15:13:39] Total Hashrate: 479.18H/s not sure but i guess it's normal behavior, two shares found 15:13:22 but just before "Pool requested miner discard all previous work - probably new block on the network." so they are rejected ?
|
|
|
|
sammy007
Legendary
Offline
Activity: 1904
Merit: 1003
|
|
October 18, 2015, 06:34:13 AM |
|
not sure but i guess it's normal behavior, two shares found 15:13:22 but just before "Pool requested miner discard all previous work - probably new block on the network." so they are rejected ?
Low difficulty share is not a stale share. It's invalid share, maybe miner error.
|
|
|
|
smooth
Legendary
Offline
Activity: 2968
Merit: 1198
|
|
October 18, 2015, 06:53:55 AM |
|
not sure but i guess it's normal behavior, two shares found 15:13:22 but just before "Pool requested miner discard all previous work - probably new block on the network." so they are rejected ?
Low difficulty share is not a stale share. It's invalid share, maybe miner error. Yeah it seems like this miner only partially works. Someone commented earlier that Wolf plans to work on the Monero version some more so whatever fixes get developed there should port over directly.
|
|
|
|
Arux
|
|
October 19, 2015, 09:04:45 AM |
|
http://52.8.47.33:8080 down during the night, the server was rebooted (amazon instance). i work on it to relaunch asap i don't know the reason of the reboot for now.
|
|
|
|
AdamWhite
|
|
October 20, 2015, 03:09:43 AM |
|
Anyone interested in this coin should be mining it, hit another block today with this setup All coins mined in the past 5 weeks or so
|
|
|
|
aerbax
|
|
October 20, 2015, 03:22:58 AM |
|
Yep! I'm getting about 1 block a day with a ~1.2k h/s Xeon.
|
|
|
|
ralfs
Newbie
Offline
Activity: 57
Merit: 0
|
|
October 22, 2015, 08:09:09 AM |
|
700 h/s for a 7950, it's much more efficient than win build.
I'm running your Windows build at 565 H/s using AMD 270x.
|
|
|
|
smooth
Legendary
Offline
Activity: 2968
Merit: 1198
|
|
October 22, 2015, 05:17:16 PM |
|
I proposed a large block auction for buyers and sellers on the Speculation thread hereIf you are interested in trading AEON 25k or more please join on that thread and indicate your interest. Especially sellers, since there seems to be more buyers than sellers. That means as a seller you may very well be able to command a premium (no guarantees of course). If there is participation this will be a real auction with a moderator and a set ending time so trades can occur. Discuss at Speculation thread (link above).
|
|
|
|
Arux
|
|
October 23, 2015, 12:30:48 AM |
|
http://52.8.47.33:8080 is up. it was very slow to synchronize aeon daemon due to a lack of ram on the server. i test the pruned blockchain to minimize swap. load, pruning and storage of the blockchain lasted approximately 30 hours. It's a pity, uptime was correct (~65d without downtime) My apologies for the inconvenience. I do not still know why the server rebooted.
|
|
|
|
LucyLovesCrypto
|
|
October 23, 2015, 06:01:27 AM |
|
I am syncing Aeon 0.9.5.0 from scratch and keep getting stuck on block 64,952
Any clues why? I know there is a bootstrap I could use but I want to figure out why the daemon is getting stuck.
|
|
|
|
LucyLovesCrypto
|
|
October 23, 2015, 06:54:17 AM |
|
I am syncing Aeon 0.9.5.0 from scratch and keep getting stuck on block 64,952
Any clues why? I know there is a bootstrap I could use but I want to figure out why the daemon is getting stuck.
After restarting the daemon several times I made it past block 64,952 and syncing continues. What is the reason why it would get stuck on the same block several times?
|
|
|
|
smooth
Legendary
Offline
Activity: 2968
Merit: 1198
|
|
October 23, 2015, 10:16:15 AM |
|
I am syncing Aeon 0.9.5.0 from scratch and keep getting stuck on block 64,952
Any clues why? I know there is a bootstrap I could use but I want to figure out why the daemon is getting stuck.
I've never seen that. If you or anyone are able to produce it please try with --log-level=2 and upload your aeond.log somewhere (suggest compressed)
|
|
|
|
smooth
Legendary
Offline
Activity: 2968
Merit: 1198
|
|
October 23, 2015, 04:18:21 PM |
|
I am syncing Aeon 0.9.5.0 from scratch and keep getting stuck on block 64,952
Any clues why? I know there is a bootstrap I could use but I want to figure out why the daemon is getting stuck.
I've never seen that. If you or anyone are able to produce it please try with --log-level=2 and upload your aeond.log somewhere (suggest compressed) Just did a resync from scratch. It isn't done yet but it blew past 64,952 without any problem. Has already reported passing the 175500 checkpoint. 2015-Oct-23 18:16:59.643001 [P2P2]CHECKPOINT PASSED FOR HEIGHT 175500 <3f7dd748b3b863b04654d87a387f2b65a365f467188971f3192eab2368e64a35>
|
|
|
|
LucyLovesCrypto
|
|
October 23, 2015, 07:27:16 PM |
|
I am syncing Aeon 0.9.5.0 from scratch and keep getting stuck on block 64,952
Any clues why? I know there is a bootstrap I could use but I want to figure out why the daemon is getting stuck.
I've never seen that. If you or anyone are able to produce it please try with --log-level=2 and upload your aeond.log somewhere (suggest compressed) Unfortunately I already deleted my log. I do not run a node. I was just testing the sync time compared to Monero (Aeon was much faster). Whatever the issue was, it appears to have been temporary because I just tried to sync again now and I passed that block with no problems.
|
|
|
|
|