Pages:
Author

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

full member
Activity: 155
Merit: 100
May 07, 2014, 12:18:27 AM
#22
ok thank u i allready changed names:) 
member
Activity: 70
Merit: 10
May 07, 2014, 12:13:28 AM
#21
gj man, i see a little problem, i connected 6 rigs and ur pool shows me only 2 of them - can u check is everythink allright?

AMQfWsuHcXK1ZznDDTKdgCJt6S8etJB44F
Just checked, you are using the same name for multiple machines! All the rigs are there but you can't see them if they all have the same name.
legendary
Activity: 1078
Merit: 1050
May 07, 2014, 12:09:34 AM
#20
gj man, i see a little problem, i connected 6 rigs and ur pool shows me only 2 of them - can u check is everythink allright?

AMQfWsuHcXK1ZznDDTKdgCJt6S8etJB44F




Try having a look at the readout in the console i have a feeling you will see your cards saying crashed
ap1
newbie
Activity: 41
Merit: 0
May 07, 2014, 12:08:29 AM
#19
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.

Found 5 devices
Using device 0 as GPU 0
Using device 1 as GPU 1
Using device 2 as GPU 2
Using device 3 as GPU 3
Using device 4 as GPU 4
N=11 SIZE=4096 STRIPES=420 WIDTH=20 PCOUNT=40960 TARGET=10
GPU 0: has 20 CUs
GPU 0: hash primorial = 30030 (14 bits)
GPU 0: sieve primorial = 435656388001 (39 bits)
GPU 0: sieve size = 55050240 (26 bits)
GPU 0: max bits used 341/352
N=11 SIZE=4096 STRIPES=420 WIDTH=20 PCOUNT=40960 TARGET=10
GPU 1: has 20 CUs
GPU 1: hash primorial = 30030 (14 bits)
GPU 1: sieve primorial = 435656388001 (39 bits)
GPU 1: sieve size = 55050240 (26 bits)
GPU 1: max bits used 341/352
N=11 SIZE=4096 STRIPES=420 WIDTH=20 PCOUNT=40960 TARGET=10
GPU 2: has 20 CUs
GPU 2: hash primorial = 30030 (14 bits)
GPU 2: sieve primorial = 435656388001 (39 bits)
GPU 2: sieve size = 55050240 (26 bits)
GPU 2: max bits used 341/352
N=11 SIZE=4096 STRIPES=420 WIDTH=20 PCOUNT=40960 TARGET=10
GPU 3: has 20 CUs
GPU 3: hash primorial = 30030 (14 bits)
GPU 3: sieve primorial = 435656388001 (39 bits)
GPU 3: sieve size = 55050240 (26 bits)
GPU 3: max bits used 341/352
N=11 SIZE=4096 STRIPES=420 WIDTH=20 PCOUNT=40960 TARGET=10
GPU 4: has 20 CUs
GPU 4: hash primorial = 30030 (14 bits)
GPU 4: sieve primorial = 435656388001 (39 bits)
GPU 4: sieve size = 55050240 (26 bits)
GPU 4: max bits used 341/352
ADL Initialisation Error! Error -21!Set powertune not supported
set_powertune(0, 20) failed.
Set powertune not supported
set_powertune(1, 20) failed.
Set engineclock not supported
set_engineclock(2, 1050) failed.
Set memoryclock not supported
set_memoryclock(2, 1500) failed.
Set powertune not supported
set_powertune(2, 20) failed.
Set engineclock not supported
set_engineclock(3, 1050) failed.
Set memoryclock not supported
set_memoryclock(3, 1500) failed.
Set powertune not supported
set_powertune(3, 20) failed.
Set engineclock not supported
set_engineclock(4, 1050) failed.
Set memoryclock not supported
set_memoryclock(4, 1500) failed.
Set powertune not supported
set_powertune(4, 20) failed.
full member
Activity: 155
Merit: 100
May 07, 2014, 12:05:02 AM
#18
gj man, i see a little problem, i connected 6 rigs and ur pool shows me only 2 of them - can u check is everythink allright?

AMQfWsuHcXK1ZznDDTKdgCJt6S8etJB44F


legendary
Activity: 1078
Merit: 1050
May 06, 2014, 11:50:18 PM
#17
Code:
error: ProbablePrimeChainTestFast 0/4
It happens when you OC too much. Try lowering memory clock first, this helps a lot in my experience. Even stock memory clock isn't stable on some cards.
EDIT: Once a GPU has crashed you need to reboot for it to work again without errors.
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

newbie
Activity: 28
Merit: 0
May 06, 2014, 11:40:51 PM
#16
60-80%
member
Activity: 70
Merit: 10
May 06, 2014, 11:29:06 PM
#15
Code:
error: ProbablePrimeChainTestFast 0/4
It happens when you OC too much. Try lowering memory clock first, this helps a lot in my experience. Even stock memory clock isn't stable on some cards.
EDIT: Once a GPU has crashed you need to reboot for it to work again without errors.

in next version of miner please add GPU fan control
Can be done. Do you mean a static setting of how much % or an automatic control that tries to hold a certain temperature?
newbie
Activity: 28
Merit: 0
May 06, 2014, 11:25:03 PM
#14
in next version of miner please add GPU fan control
sr. member
Activity: 473
Merit: 250
Sodium hypochlorite, acetone, ethanol
May 06, 2014, 11:24:17 PM
#13
Code:
error: ProbablePrimeChainTestFast 0/4
newbie
Activity: 20
Merit: 0
May 06, 2014, 11:23:17 PM
#12
Does anyone have a link to 14.3 drivers for windows 8.1? At AMDs page I only find 14.4 now...
member
Activity: 70
Merit: 10
May 06, 2014, 11:07:44 PM
#11
got 1 xmp on balance allready & didnt reciew it yet(
It takes ~2days for the coins to mature. I don't have the funds to create a buffer to be able to pay immediately.
Although in the future this might be possible, once the hashrate has stabilized and is not increasing.

What are you valuing 11 and 12 chains? Also is there a block winning reward?
Anything above 10 is valued as 10, because these chains are so rare that you don't want to depend on them. Therefore 10 chains have higher value of course.
And there is no block reward for the same reasons.
newbie
Activity: 15
Merit: 0
May 06, 2014, 10:59:36 PM
#10
What are you valuing 11 and 12 chains? Also is there a block winning reward?
newbie
Activity: 28
Merit: 0
May 06, 2014, 10:58:27 PM
#9
got 1 xmp on balance allready & didnt reciew it yet(
member
Activity: 70
Merit: 10
May 06, 2014, 10:55:28 PM
#8
why so high latency at pool?
It's the average of all connected workers. But ~200ms is still very low, keep in mind this is 2x network ping latency + server cpu time needed to create all work.
On other pools this latency is in the order of multiple seconds and that's why they have so many stale/invalid shares.
newbie
Activity: 28
Merit: 0
May 06, 2014, 10:47:38 PM
#7
why so high latency at pool?
newbie
Activity: 28
Merit: 0
May 06, 2014, 10:39:32 PM
#6
i start to test with some of my rigs...wil report later
hero member
Activity: 812
Merit: 1000
May 06, 2014, 10:04:48 PM
#5
Can anyone vouch for this pool/miner?

I don't have the means to test it atm.
member
Activity: 70
Merit: 10
May 06, 2014, 09:55:46 PM
#4
sas that need 14.4 driver - its very bugged
Catalyst 14.3 should be ok too.
newbie
Activity: 28
Merit: 0
May 06, 2014, 09:52:34 PM
#3
sas that need 14.4 driver - its very bugged
Pages:
Jump to: