Main Menu

AMD OpenCL Momentum miner

Started by NaN, January 26, 2014, 08:41:40 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

krpetrov

Nvidia cards support will be greatly appreciated. ;)
Please make it happened!

bey


Darkbane

#72
Quote from: NaN on January 29, 2014, 02:13:25 PM
This means that the miner isn't able to connect to the server. That's a different problem. It could be a boost related problem, i.e. boost::asio::connect somehow fails. Did your IP change before that happens? I'm trying to fix it
UPDATE newly released version v0.1.2 should fix it.

Okay ran v0.1.1 for windows the past 12 hours straight and it seems to still be running solid no issues... I'll get the new version and fire it up...

windows 8.1 64bit
AMD driver 13.251.0.0

NaN

working on it. hopefully I can release it tomorrow.

bey

Quote from: NaN on January 29, 2014, 02:13:25 PM

UPDATE newly released version v0.1.2 should fix it.

hello :)

what about 1Gh or Ypool version ? :)
Thx ^^

rots

No, ip is fixed. I restart miner can connect.

Quote from: NaN on January 29, 2014, 02:13:25 PM
This means that the miner isn't able to connect to the server. That's a different problem. It could be a boost related problem, i.e. boost::asio::connect somehow fails. Did your IP change before that happens? I'm trying to fix it

NaN

#68
This means that the miner isn't able to connect to the server. That's a different problem. It could be a boost related problem, i.e. boost::asio::connect somehow fails. Did your IP change before that happens? I'm trying to fix it
UPDATE newly released version v0.1.2 should fix it.

rots

with this version, after 2hours run, I still got
6 (0.42%), ST: 0 (0.00%)
failed to connect (system:10061). sleep 10 seconds until retry
[STATS] 2014-Jan-29 21:22:49 | 500.43 c/m | 0.02 sh/m | VL: 6223 (99.58%), RJ: 2
6 (0.42%), ST: 0 (0.00%)
failed to connect (system:10061). sleep 10 seconds until retry
[STATS] 2014-Jan-29 21:22:59 | 499.08 c/m | 0.02 sh/m | VL: 6223 (99.58%), RJ: 2
6 (0.42%), ST: 0 (0.00%)
[STATS] 2014-Jan-29 21:23:09 | 497.74 c/m | 0.02 sh/m | VL: 6223 (99.58%), RJ: 2
6 (0.42%), ST: 0 (0.00%)
failed to connect (system:10061). sleep 10 seconds until retry
[STATS] 2014-Jan-29 21:23:19 | 496.41 c/m | 0.02 sh/m | VL: 6223 (99.58%), RJ: 2
6 (0.42%), ST: 0 (0.00%)
failed to connect (system:10061). sleep 10 seconds until retry

It retry repeatedly, restart miner can work again


Quote from: NaN on January 29, 2014, 12:51:03 AM
I updated the miner to version 0.1.1, which should fix with the "doing no work" bug in Windows.

@darkbane: the miner used a corrupted block with a wrong share target. therefore it is very likely that the miner will find zero shares in a reasonable time because it has a very difficult share target. it looked like as some buffers got corrupted. most likely windows missed some resources because i used many asynchronous events but v0.1.1 implements better code.

visterln

[WORKER1] share found: 39302792 <-> 23252414 #2677 (172270) @ 1390965621
[WORKER1] share found: 19725197 <-> 35205832 #2678 (172328) @ 1390965637
[WORKER1] share found: 15219440 <-> 6413293 #2679 (172504) @ 1390965695
[WORKER0] share found: 2669651 <-> 56902601 #2680 (172504) @ 1390965710
[WORKER0] share found: 65841309 <-> 26210212 #2681 (172534) @ 1390965724
[WORKER0] share found: 5100596 <-> 17821504 #2682 (172588) @ 1390965740
[STATS] 2014-Jan-29 10:47:26 | 3499.38 c/m | 54.36 sh/m | VL: 2584 (99.81%)
5 (0.19%), ST: 0 (0.00%)
[WORKER0] share found: 19313389 <-> 24836122 #2683 (172672) @ 1390965762
[WORKER0] share found: 31654685 <-> 65801234 #2684 (172750) @ 1390965782
[WORKER1] share found: 41656377 <-> 30877221 #2685 (172786) @ 1390965775
[WORKER0] share found: 23386461 <-> 49631312 #2686 (172886) @ 1390965816
[WORKER0] share found: 35802758 <-> 22282221 #2687 (172918) @ 1390965828
[WORKER0] share found: 38276454 <-> 35582920 #2688 (172988) @ 1390965850
[WORKER1] share found: 7672694 <-> 17473679 #2689 (173104) @ 1390965869
[WORKER0] share found: 65527925 <-> 45901985 #2690 (173152) @ 1390965894
[WORKER1] share found: 25582390 <-> 22565606 #2691 (173170) @ 1390965881
[WORKER1] share found: 18761792 <-> 26609064 #2692 (173192) @ 1390965887
[WORKER0] share found: 4323306 <-> 55538948 #2693 (173254) @ 1390965922
[STATS] 2014-Jan-29 10:47:36 | 3500.53 c/m | 54.40 sh/m | VL: 2594 (99.81%)
5 (0.19%), ST: 0 (0.00%)
[WORKER0] share found: 45773293 <-> 48556919 #2694 (173354) @ 1390965952
[WORKER1] share found: 16444562 <-> 16153991 #2695 (173510) @ 1390965969
[WORKER1] share found: 362427 <-> 10585721 #2696 (173524) @ 1390965973

NOW.7950 work on 1750 CPM of one

visterln

Quote from: NaN on January 29, 2014, 02:27:35 AM
Quote from: visterln on January 29, 2014, 02:14:02 AM
There is a problem, only 13.1 driver can support more than 4 cards, means you can not update the driver supports more graphics, whether you can upgrade only OPCL it?
I have no idea. If this is possible it is most likely complicated. why isn't AMD able to support more gpus with current drivers? do you know whether 4 gpus work with the linux drivers?

I do not know to use LINUX, has been using WIN7 64. I do not know why, after 13.1 AMD drivers do not support more than 400 cards, including 270 270X drivers are needed in 13.1 in 7870 to support the mandatory installation of 6 cards. You see it can support 13.1 driver?

NaN

Quote from: visterln on January 29, 2014, 02:14:02 AM
There is a problem, only 13.1 driver can support more than 4 cards, means you can not update the driver supports more graphics, whether you can upgrade only OPCL it?
I have no idea. If this is possible it is most likely complicated. why isn't AMD able to support more gpus with current drivers? do you know whether 4 gpus work with the linux drivers?

visterln

There is a problem, only 13.1 driver can support more than 4 cards, means you can not update the driver supports more graphics, whether you can upgrade only OPCL it?

visterln

Quote from: NaN on January 29, 2014, 01:32:29 AM
Quote from: visterln on January 29, 2014, 01:15:55 AM
Quote from: NaN on January 29, 2014, 01:07:41 AM
which catalyst version are you using?

13-1_vista_win7_win8_64_dd_ccc_whql
and
SDK 12.9
Another user wrote that catalyst 13.1 does not work. same problem. please update the driver

try to 13.12,it's OK

[WORKER1] share found: 47542446 <-> 23048227 #278 (18510) @ 1390964351
[STATS] 2014-Jan-29 10:03:46 | 3278.12 c/m | 49.06 sh/m | VL: 216 (99.08%)
2 (0.92%), ST: 0 (0.00%)
[WORKER1] share found: 14390109 <-> 59640650 #279 (18584) @ 1390964373
[WORKER0] share found: 56117766 <-> 53405478 #280 (18766) @ 1390964440
[WORKER0] share found: 56011260 <-> 12477005 #281 (18886) @ 1390964474
[WORKER0] share found: 23711366 <-> 53320897 #282 (19050) @ 1390964530
[WORKER0] share found: 53238056 <-> 9688937 #283 (19080) @ 1390964538
[WORKER0] share found: 38155706 <-> 42210330 #284 (19142) @ 1390964558
[WORKER1] share found: 43616931 <-> 46186387 #285 (19162) @ 1390964539
[STATS] 2014-Jan-29 10:03:56 | 3284.91 c/m | 48.86 sh/m | VL: 222 (99.11%)
2 (0.89%), ST: 0 (0.00%)
[WORKER1] share found: 57056053 <-> 30333989 #286 (19180) @ 1390964543
[WORKER0] share found: 37509216 <-> 161646 #287 (19266) @ 1390964588
[WORKER1] share found: 60494598 <-> 61284186 #288 (19660) @ 1390964679
[WORKER1] share found: 19190590 <-> 11028309 #289 (19726) @ 1390964693
[WORKER0] share found: 46305233 <-> 40334684 #290 (19768) @ 1390964730
[STATS] 2014-Jan-29 10:04:06 | 3294.67 c/m | 48.33 sh/m | VL: 227 (99.13%)
2 (0.87%), ST: 0 (0.00%)
[WORKER0] share found: 5031941 <-> 34767294 #291 (19774) @ 1390964732
[WORKER1] share found: 63154609 <-> 39599691 #292 (19932) @ 1390964747
[WORKER1] share found: 18337791 <-> 59469530 #293 (19978) @ 1390964759
[WORKER0] share found: 56476755 <-> 37374914 #294 (20228) @ 1390964844
[WORKER0] share found: 35894059 <-> 10143253 #295 (20312) @ 1390964868

NaN

Quote from: visterln on January 29, 2014, 01:15:55 AM
Quote from: NaN on January 29, 2014, 01:07:41 AM
which catalyst version are you using?

13-1_vista_win7_win8_64_dd_ccc_whql
and
SDK 12.9
Another user wrote that catalyst 13.1 does not work. same problem. please update the driver

visterln

Quote from: NaN on January 29, 2014, 01:07:41 AM
which catalyst version are you using?

13-1_vista_win7_win8_64_dd_ccc_whql
and
SDK 12.9