Pages:
Author

Topic: [ANN] New Primecoin Pool + GPU Miner - page 12. (Read 19667 times)

full member
Activity: 140
Merit: 100
May 07, 2014, 03:45:00 AM
#42
13.12 dont work

OpenCL error: -45 at ..\xpmclient.cpp:101
OpenCL error: -61 at ..\xpmclient.cpp:196
member
Activity: 70
Merit: 10
May 07, 2014, 03:40:55 AM
#41
Hey madMAX, I notice the share values change. How is that calculated? What's the value of 11-ch/higher or is it the same as 10-ch on the pool?
Yeah they change based on pool luck. They are calculated based on the blocks vs. shares found in the last 24h. Once the pool has more hashpower the share values should stabilize.
11-ch is the same as 10 because they are too rare to make an exception.

will work on catalyst 13.12?
Don't know. You can try, but it might be slower, so compare your results with other miners.

...
Isn't it required to use 14.3 or higher driver, he is using 13.2.
In this case juve4v has the same error and he uses 14.4 ... i'm looking for the bug right now.
newbie
Activity: 34
Merit: 0
May 07, 2014, 03:40:21 AM
#40
...
GPU 2: sieve size = 550556388001 (7 bits)
GPU 2: max bits used 341/352
Connecting to frontend: 54.187.143.168:6666 ...
Connecting to bitcoin: 54.187.143.168:60002 ...
Connecting to signals: 54.187.143.168:60003 ...
Work received: height=529506 diff=10.890167 latency=760ms
error: ProbablePrimeChainTestFast 0/4

I have win7, 13.2 driver and I clocked both mem and core to 1000. 280x. Restart and still same error. I know newer driver should be installed but I got the same software setup on other rigs and it works fine.
Does it crash and stop mining? or shows only one error and keeps going?

It crashes.
Sometimes it has several rows of error: ProbablePrimeChainTestFast 0/4. Like 20 or so. On two other rigs I have pretty much all same except processors are Sempron 145 and this rig has i5. And I use this rig for gaming and stuff also, so maybe there is some kind of other issues.

I will try driver update later.
Actually there is something odd: GPU 2: sieve size = 550556388001 (7 bits)
This value is wrong and it's no wonder the miner crashes. I'm gonna have to investigate how this can happen...
It should be: GPU 2: sieve size = 55050240 (26 bits)

Isn't it required to use 14.3 or higher driver, he is using 13.2.

It is working on my other rigs with 13.2. And it shows 11.5 CPD for 3 card rig with 1080/1250. With cpuload="0".
hero member
Activity: 518
Merit: 500
May 07, 2014, 03:35:20 AM
#39
...
GPU 2: sieve size = 550556388001 (7 bits)
GPU 2: max bits used 341/352
Connecting to frontend: 54.187.143.168:6666 ...
Connecting to bitcoin: 54.187.143.168:60002 ...
Connecting to signals: 54.187.143.168:60003 ...
Work received: height=529506 diff=10.890167 latency=760ms
error: ProbablePrimeChainTestFast 0/4

I have win7, 13.2 driver and I clocked both mem and core to 1000. 280x. Restart and still same error. I know newer driver should be installed but I got the same software setup on other rigs and it works fine.
Does it crash and stop mining? or shows only one error and keeps going?

It crashes.
Sometimes it has several rows of error: ProbablePrimeChainTestFast 0/4. Like 20 or so. On two other rigs I have pretty much all same except processors are Sempron 145 and this rig has i5. And I use this rig for gaming and stuff also, so maybe there is some kind of other issues.

I will try driver update later.
Actually there is something odd: GPU 2: sieve size = 550556388001 (7 bits)
This value is wrong and it's no wonder the miner crashes. I'm gonna have to investigate how this can happen...
It should be: GPU 2: sieve size = 55050240 (26 bits)

Isn't it required to use 14.3 or higher driver, he is using 13.2.
full member
Activity: 140
Merit: 100
May 07, 2014, 03:22:37 AM
#38
will work on catalyst 13.12?
member
Activity: 70
Merit: 10
May 07, 2014, 03:21:57 AM
#37
...
GPU 2: sieve size = 550556388001 (7 bits)
GPU 2: max bits used 341/352
Connecting to frontend: 54.187.143.168:6666 ...
Connecting to bitcoin: 54.187.143.168:60002 ...
Connecting to signals: 54.187.143.168:60003 ...
Work received: height=529506 diff=10.890167 latency=760ms
error: ProbablePrimeChainTestFast 0/4

I have win7, 13.2 driver and I clocked both mem and core to 1000. 280x. Restart and still same error. I know newer driver should be installed but I got the same software setup on other rigs and it works fine.
Does it crash and stop mining? or shows only one error and keeps going?

It crashes.
Sometimes it has several rows of error: ProbablePrimeChainTestFast 0/4. Like 20 or so. On two other rigs I have pretty much all same except processors are Sempron 145 and this rig has i5. And I use this rig for gaming and stuff also, so maybe there is some kind of other issues.

I will try driver update later.
Actually there is something odd: GPU 2: sieve size = 550556388001 (7 bits)
This value is wrong and it's no wonder the miner crashes. I'm gonna have to investigate how this can happen...
It should be: GPU 2: sieve size = 55050240 (26 bits)
hero member
Activity: 518
Merit: 500
May 07, 2014, 03:20:25 AM
#36
Hey madMAX, I notice the share values change. How is that calculated? What's the value of 11-ch/higher or is it the same as 10-ch on the pool?
hero member
Activity: 518
Merit: 500
May 07, 2014, 03:02:25 AM
#35
Is this miner free or is it a 10% dev fee like others?

Pool fee is 10%, so yup, it's the same. At least this miner is the fastest one currently.
legendary
Activity: 1148
Merit: 1000
May 07, 2014, 02:59:58 AM
#34
Is this miner free or is it a 10% dev fee like others?
hero member
Activity: 518
Merit: 500
May 07, 2014, 02:55:35 AM
#33
I'm running a MSI Twin Frozr III HD7970 OC BE @ 1150core/1500mem getting 4.29~4.35 CPD Temp=62C and a Gigabyte HD7850 2GB @ 1150core/1500mem getting 2.08~2.17 CPD Temp=52C.

Nice work on the new pool and nice to have an alternative to ypool.

What will happen to the rewards system once it hits 11 on the Diff?

How do the miner calculate the CPD? ie. 1-ch,2-ch,3-ch,4-ch, etc.....
Nice to know it works on 7850, and pretty good actually. How do you keep that 7970 so cool? Smiley

2.) Don't know yet. Keep in mind diff 11 is still easily ~5 times more difficult than 10.9 so it's gonna be a while.

3.) It depends on the cpuload setting: with cpuload=1 it uses 4-ch and with cpuload=2 it uses 3-ch and so on. But still, i'm using a custom formula that has proven itself to be pretty accurate.

Found 1 devices
Using device 0 as GPU 0
N=11 SIZE=4096 STRIPES=420 WIDTH=20 PCOUNT=40960 TARGET=10
GPU 0: has 40 CUs
GPU 0: hash primorial = 30030 (14 bits)
GPU 0: sieve primorial = 435656388001 (58 bits)
GPU 0: sieve size = 550556388001 (7 bits)
GPU 0: max bits used 341/352
Failed to ADL_Adapter_ID_Get. Error -1Failed to ADL_Adapter_ID_Get. Error -1Con
ecting to frontend: 54.187.143.168:6666 ...

Connecting to bitcoin: 54.187.143.168:60002 ...
Connecting to signals: 54.187.143.168:60003 ...
Work received: height=529501 diff=10.890152 latency=842ms
error: ProbablePrimeChainTestFast 0/2
error: ProbablePrimeChainTestFast 0/2
error: ProbablePrimeChainTestFast 0/2

W8x64 with 14.4

Any suggestions?
There are 2 problems: ADL not working and "error: ProbablePrimeChainTestFast".
The first one is probably win8 related. The second one is either too much OC or some other driver/win8 problem...

Right now i have no time to test/debug win8.
Maybe try 14.3 driver...

Cool, great to know the calculation part.

The 7970 has an aftermarket cooler, Arctic Accelero 7970 Extreme and it's in Corsair 400R case also. The 7850 2GB I own runs like a champ and cool. LOL

As of now, these are my stats:
7970: CPD=4.33
7850: CPD=2.24

7850 is using the same sieveprimorial as the 7970. Same temps stills, both cards are in the same ATX case.
newbie
Activity: 34
Merit: 0
May 07, 2014, 02:30:02 AM
#32
...
GPU 2: sieve size = 550556388001 (7 bits)
GPU 2: max bits used 341/352
Connecting to frontend: 54.187.143.168:6666 ...
Connecting to bitcoin: 54.187.143.168:60002 ...
Connecting to signals: 54.187.143.168:60003 ...
Work received: height=529506 diff=10.890167 latency=760ms
error: ProbablePrimeChainTestFast 0/4

I have win7, 13.2 driver and I clocked both mem and core to 1000. 280x. Restart and still same error. I know newer driver should be installed but I got the same software setup on other rigs and it works fine.
Does it crash and stop mining? or shows only one error and keeps going?

It crashes.
Sometimes it has several rows of error: ProbablePrimeChainTestFast 0/4. Like 20 or so. On two other rigs I have pretty much all same except processors are Sempron 145 and this rig has i5. And I use this rig for gaming and stuff also, so maybe there is some kind of other issues.

I will try driver update later.
member
Activity: 70
Merit: 10
May 07, 2014, 02:24:13 AM
#31
...
GPU 2: sieve size = 550556388001 (7 bits)
GPU 2: max bits used 341/352
Connecting to frontend: 54.187.143.168:6666 ...
Connecting to bitcoin: 54.187.143.168:60002 ...
Connecting to signals: 54.187.143.168:60003 ...
Work received: height=529506 diff=10.890167 latency=760ms
error: ProbablePrimeChainTestFast 0/4

I have win7, 13.2 driver and I clocked both mem and core to 1000. 280x. Restart and still same error. I know newer driver should be installed but I got the same software setup on other rigs and it works fine.
Does it crash and stop mining? or shows only one error and keeps going?
newbie
Activity: 34
Merit: 0
May 07, 2014, 02:15:33 AM
#30
Found 3 devices
Using device 0 as GPU 0
Using device 1 as GPU 1
Using device 2 as GPU 2
N=11 SIZE=4096 STRIPES=420 WIDTH=20 PCOUNT=40960 TARGET=10
GPU 0: has 32 CUs
GPU 0: hash primorial = 30030 (14 bits)
GPU 0: sieve primorial = 435656388001 (58 bits)
GPU 0: sieve size = 550556388001 (7 bits)
GPU 0: max bits used 341/352
N=11 SIZE=4096 STRIPES=420 WIDTH=20 PCOUNT=40960 TARGET=10
GPU 1: has 32 CUs
GPU 1: hash primorial = 30030 (14 bits)
GPU 1: sieve primorial = 435656388001 (58 bits)
GPU 1: sieve size = 550556388001 (7 bits)
GPU 1: max bits used 341/352
N=11 SIZE=4096 STRIPES=420 WIDTH=20 PCOUNT=40960 TARGET=10
GPU 2: has 32 CUs
GPU 2: hash primorial = 30030 (14 bits)
GPU 2: sieve primorial = 435656388001 (58 bits)
GPU 2: sieve size = 550556388001 (7 bits)
GPU 2: max bits used 341/352
Connecting to frontend: 54.187.143.168:6666 ...
Connecting to bitcoin: 54.187.143.168:60002 ...
Connecting to signals: 54.187.143.168:60003 ...
Work received: height=529506 diff=10.890167 latency=760ms
error: ProbablePrimeChainTestFast 0/4


I have win7, 13.2 driver and I clocked both mem and core to 1000. 280x. Restart and still same error. I know newer driver should be installed but I got the same software setup on other rigs and it works fine.
sr. member
Activity: 479
Merit: 250
May 07, 2014, 02:12:44 AM
#29
yeah this miner does run hotter
member
Activity: 70
Merit: 10
May 07, 2014, 02:08:08 AM
#28
I'm running a MSI Twin Frozr III HD7970 OC BE @ 1150core/1500mem getting 4.29~4.35 CPD Temp=62C and a Gigabyte HD7850 2GB @ 1150core/1500mem getting 2.08~2.17 CPD Temp=52C.

Nice work on the new pool and nice to have an alternative to ypool.

What will happen to the rewards system once it hits 11 on the Diff?

How do the miner calculate the CPD? ie. 1-ch,2-ch,3-ch,4-ch, etc.....
Nice to know it works on 7850, and pretty good actually. How do you keep that 7970 so cool? Smiley

2.) Don't know yet. Keep in mind diff 11 is still easily ~5 times more difficult than 10.9 so it's gonna be a while.

3.) It depends on the cpuload setting: with cpuload=1 it uses 4-ch and with cpuload=2 it uses 3-ch and so on. But still, i'm using a custom formula that has proven itself to be pretty accurate.

Found 1 devices
Using device 0 as GPU 0
N=11 SIZE=4096 STRIPES=420 WIDTH=20 PCOUNT=40960 TARGET=10
GPU 0: has 40 CUs
GPU 0: hash primorial = 30030 (14 bits)
GPU 0: sieve primorial = 435656388001 (58 bits)
GPU 0: sieve size = 550556388001 (7 bits)
GPU 0: max bits used 341/352
Failed to ADL_Adapter_ID_Get. Error -1Failed to ADL_Adapter_ID_Get. Error -1Con
ecting to frontend: 54.187.143.168:6666 ...

Connecting to bitcoin: 54.187.143.168:60002 ...
Connecting to signals: 54.187.143.168:60003 ...
Work received: height=529501 diff=10.890152 latency=842ms
error: ProbablePrimeChainTestFast 0/2
error: ProbablePrimeChainTestFast 0/2
error: ProbablePrimeChainTestFast 0/2

W8x64 with 14.4

Any suggestions?
There are 2 problems: ADL not working and "error: ProbablePrimeChainTestFast".
The first one is probably win8 related. The second one is either too much OC or some other driver/win8 problem...

Right now i have no time to test/debug win8.
Maybe try 14.3 driver...
hero member
Activity: 505
Merit: 500
May 07, 2014, 02:07:56 AM
#27
Found 1 devices
Using device 0 as GPU 0
N=11 SIZE=4096 STRIPES=420 WIDTH=20 PCOUNT=40960 TARGET=10
GPU 0: has 40 CUs
GPU 0: hash primorial = 30030 (14 bits)
GPU 0: sieve primorial = 435656388001 (58 bits)
GPU 0: sieve size = 550556388001 (7 bits)
GPU 0: max bits used 341/352
Failed to ADL_Adapter_ID_Get. Error -1Failed to ADL_Adapter_ID_Get. Error -1Con
ecting to frontend: 54.187.143.168:6666 ...

Connecting to bitcoin: 54.187.143.168:60002 ...
Connecting to signals: 54.187.143.168:60003 ...
Work received: height=529501 diff=10.890152 latency=842ms
error: ProbablePrimeChainTestFast 0/2
error: ProbablePrimeChainTestFast 0/2
error: ProbablePrimeChainTestFast 0/2

W8x64 with 14.4

Any suggestions?
hero member
Activity: 518
Merit: 500
May 07, 2014, 01:31:27 AM
#26
I'm running a MSI Twin Frozr III HD7970 OC BE @ 1150core/1500mem getting 4.29~4.35 CPD Temp=62C and a Gigabyte HD7850 2GB @ 1150core/1500mem getting 2.08~2.17 CPD Temp=52C.

Nice work on the new pool and nice to have an alternative to ypool.

What will happen to the rewards system once it hits 11 on the Diff?

How does the miner calculates the CPD? ie. 1-ch,2-ch,3-ch,4-ch, etc.....
legendary
Activity: 1078
Merit: 1050
May 07, 2014, 12:54:14 AM
#25
No ammount of overclock change has seemed to get it to stop crashing on startup i had the same error and now that i have lowered the overclock i don't even seem to get that error but its just straight up crashing as soon as it gets work from the server.

 I'm testing it on a rig of 4 sapphires 290x, windows 8, i7 3820 and 14.3 drivers however on my other rig using windows 7 it all seems to work nice and if you actually pay out then this is one hot smoking miner but would love a fix for windows 8 rig if possible brah
Does it show any OpenCL error when crashing?
You need to manually open a CMD window and start the miner from there to see the error. Otherwise the console closes immediately.
EDIT: just to make sure, have you tried to reboot the machine?

Yes i reset the machine many times and i've sent you a screenshot of the console and i can also send you the output if needed but now its not even showing the error its just closing right after it gets work from the server
member
Activity: 70
Merit: 10
May 07, 2014, 12:45:33 AM
#24
No ammount of overclock change has seemed to get it to stop crashing on startup i had the same error and now that i have lowered the overclock i don't even seem to get that error but its just straight up crashing as soon as it gets work from the server.

 I'm testing it on a rig of 4 sapphires 290x, windows 8, i7 3820 and 14.3 drivers however on my other rig using windows 7 it all seems to work nice and if you actually pay out then this is one hot smoking miner but would love a fix for windows 8 rig if possible brah
Does it show any OpenCL error when crashing?
You need to manually open a CMD window and start the miner from there to see the error. Otherwise the console closes immediately.
EDIT: just to make sure, have you tried to reboot the machine?
member
Activity: 70
Merit: 10
May 07, 2014, 12:19:39 AM
#23
Hi,

Thank you, finally one for Linux!! I was lazy to try out other's XPM miners as all of my rigs are Linux.
Just downloaded Linux version and testing with a 5xR270. Seems working but all the set core and powertune failed.
Does it even support R270? I will test with 7950/7970 later.
The followings are the corresponding error messages.

It looks like ADL doesn't work.
I will test this on my linux machine and fix it if possible, until then you can ignore the errors and set your clocks with some other tool.

270/270X should work as they are GCN, but i don't know how the performance will be.
You should def. try lower sieve primorials with these, like 12 or 11 (see config.txt).
Pages:
Jump to: