[1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 226.

PatMan

hero member

Activity: 924

Merit: 1000

Watch out for the "Neg-Rep-Dogie-Police".....

Quote from: mdude77 on February 02, 2015, 06:06:09 PM

Quote from: PatMan on February 02, 2015, 05:56:24 PM

Quote from: mdude77 on February 02, 2015, 05:49:52 PM

I don't follow? The screenshot above shows them at 1,797, except for one, which is at 2,112. Neither is a factor of 2. (2, 4, 8, 16, 32, 64, 128, 256, 512, 1024, 2048, 4096, 8192, etc).

Every Ant I've had since S1s has had this issue.

M

Ah - I misunderstood, so it's only when the diff is a factor of 2 that the ants don't display best share - is that right?

Peace

Bingo!

And if you don't set your difficulty on p2pool, the odds of you getting a difficulty that is a factor of 2 is pretty slim.

M

Cool, that explains why I've never had a problem with it then...... Cheesy

Thanks mdude. I seem to remember messing about with diff back in the day, but found it to be of no benefit quite early, so I just let p2pool sort it out - easy.

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: PatMan on February 02, 2015, 05:56:24 PM

Quote from: mdude77 on February 02, 2015, 05:49:52 PM

I don't follow? The screenshot above shows them at 1,797, except for one, which is at 2,112. Neither is a factor of 2. (2, 4, 8, 16, 32, 64, 128, 256, 512, 1024, 2048, 4096, 8192, etc).

Every Ant I've had since S1s has had this issue.

M

Ah - I misunderstood, so it's only when the diff is a factor of 2 that the ants don't display best share - is that right?

Peace

Bingo!

And if you don't set your difficulty on p2pool, the odds of you getting a difficulty that is a factor of 2 is pretty slim.

M

PatMan

hero member

Activity: 924

Merit: 1000

Watch out for the "Neg-Rep-Dogie-Police".....

Quote from: mdude77 on February 02, 2015, 05:49:52 PM

I don't follow? The screenshot above shows them at 1,797, except for one, which is at 2,112. Neither is a factor of 2. (2, 4, 8, 16, 32, 64, 128, 256, 512, 1024, 2048, 4096, 8192, etc).

Every Ant I've had since S1s has had this issue.

M

Ah - I misunderstood, so it's only when the diff is a factor of 2 that the ants don't display best share - is that right?

Peace

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: PatMan on February 02, 2015, 05:40:01 PM

Not too sure about that tbh. Here's another screen I just took, only one of the miners is using a diff factor of 2, yet the best share is still being displayed:

- unless the display is only updated when the diff is at a factor of 2 of course......I've heard a few miners say they can't get the best share to show up either on the miner gui or on your monitor, but I've never had an issue with it personally.

Lucky, I guess..... Wink

I don't follow? The screenshot above shows them at 1,797, except for one, which is at 2,112. Neither is a factor of 2. (2, 4, 8, 16, 32, 64, 128, 256, 512, 1024, 2048, 4096, 8192, etc).

Every Ant I've had since S1s has had this issue.

M

jcumins

full member

Activity: 312

Merit: 100

Bcnex - The Ultimate Blockchain Trading Platform

That worked well have best share back.

Thanks much

PatMan

hero member

Activity: 924

Merit: 1000

Watch out for the "Neg-Rep-Dogie-Police".....

Not too sure about that tbh. Here's another screen I just took, only one of the miners is using a diff factor of 2, yet the best share is still being displayed:

- unless the display is only updated when the diff is at a factor of 2 of course......I've heard a few miners say they can't get the best share to show up either on the miner gui or on your monitor, but I've never had an issue with it personally.

Lucky, I guess..... Wink

jcumins

full member

Activity: 312

Merit: 100

Bcnex - The Ultimate Blockchain Trading Platform

I will give that a try

a -2049 on the address line thats easy to try

jcumins

full member

Activity: 312

Merit: 100

Bcnex - The Ultimate Blockchain Trading Platform

Well that version of cgminer will not work with the latest version of firmware for the S3

It will not even start

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: PatMan on February 02, 2015, 04:30:31 PM

I don't set share difficulty, p2pool looks after it & my display works fine......

Eg:

Not setting it means you're using what p2pool sets it to, which is likely not a factor of 2. Ergo, no problem.

M

PatMan

hero member

Activity: 924

Merit: 1000

Watch out for the "Neg-Rep-Dogie-Police".....

I don't set share difficulty, p2pool looks after it & my display works fine......

Eg:

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: jcumins on February 02, 2015, 03:35:25 PM

Wow my best share on a S3 running the latest firmware was showing 0

I think I will try that new cgminer.

Stats wise there not bad shares are about 15% dead or orphaned. The efficiency runs 98 to 105 so not bad.

Will see what the new cgminer does

The best share problem is caused by a difficulty set to a factor of 2. ie, 512, 1024, 2048, etc. Change the share difficulty slightly by adding one or two, say 514, 1025, 2049, and your best shares will show up again.

M

PatMan

hero member

Activity: 924

Merit: 1000

Watch out for the "Neg-Rep-Dogie-Police".....

Quote from: jcumins on February 02, 2015, 03:35:25 PM

Wow my best share on a S3 running the latest firmware was showing 0

You can ignore that - it's another bitmain firmware bug thing. Run it with what IYFTech suggested - you'll be good Wink

Bitmain firmware releases tend to be worse than the older ones they replace....... Roll Eyes

jcumins

full member

Activity: 312

Merit: 100

Bcnex - The Ultimate Blockchain Trading Platform

Wow my best share on a S3 running the latest firmware was showing 0

I think I will try that new cgminer.

Stats wise there not bad shares are about 15% dead or orphaned. The efficiency runs 98 to 105 so not bad.

Will see what the new cgminer does

IYFTech

hero member

Activity: 686

Merit: 500

WANTED: Active dev to fix & re-write p2pool in C

Quote from: jcumins on January 31, 2015, 11:30:07 PM

I have the latest S3 Firmware installed

Here is the version info.

=> VERSION

[CGMiner] => 4.7.0
[API] => 3.1
[Miner] => 7.0.0.3
[CompileTime] => Sat Jan 3 10:37:47 CST 2015
[Type] => S3

has the cgminer fix been added t this version.

Does any one know.

To my knowledge, the cgminer fork used in bitmain firmware(?) all suffer from the same issue with p2pool - which was why ck kindly compiled the S3 binary.

Nice to see a few more blocks drop in lately

sEpuLchEr

sr. member

Activity: 248

Merit: 250

Are we there yet?

Forgot to thank the last 2 donators.

Thank you! Much appreciated whoever you are!

jcumins

full member

Activity: 312

Merit: 100

Bcnex - The Ultimate Blockchain Trading Platform

I have the latest S3 Firmware installed

Here is the version info.

=> VERSION

[CGMiner] => 4.7.0
[API] => 3.1
[Miner] => 7.0.0.3
[CompileTime] => Sat Jan 3 10:37:47 CST 2015
[Type] => S3

has the cgminer fix been added t this version.

Does any one know.

IYFTech

hero member

Activity: 686

Merit: 500

WANTED: Active dev to fix & re-write p2pool in C

Quote from: theseraphgabriel on January 31, 2015, 02:35:09 PM

TY will test and get back in 24-48 hrs see if it changes
wish I had a like button

Not a bother man. I'd also suggest resetting your bitcoin settings to standard - I never found messing with them helped much with p2pool, in fact it usually made matters worse. The only setting that really helps is lowering the "maxconnection" if you suffer from low bandwidth, everything else runs fine using the default settings.

theseraphgabriel

newbie

Activity: 32

Merit: 0

Quote from: IYFTech on January 31, 2015, 02:31:12 PM

Quote from: theseraphgabriel on January 31, 2015, 02:06:43 PM

....how is it installed what just SSH in and exchange the cgminer in the S3 for this one?

Steps for installing ck's binary on S3:

SSH in then:

a) cd /usr/bin
b) mv cgminer cgminer.bak
c) wget http://ck.kolivas.org/apps/cgminer/antminer/s3/4.6.1-141020/cgminer
d) chmod +x cgminer
e) /etc/init.d/cgminer restart (or simply reboot)

To check cgminer version type: cgminer-api version

Job done Wink

TY will test and get back in 24-48 hrs see if it changes
wish I had a like button

IYFTech

hero member

Activity: 686

Merit: 500

WANTED: Active dev to fix & re-write p2pool in C

Quote from: theseraphgabriel on January 31, 2015, 02:06:43 PM

....how is it installed what just SSH in and exchange the cgminer in the S3 for this one?

Steps for installing ck's binary on S3:

SSH in then:

a) cd /usr/bin
b) mv cgminer cgminer.bak
c) wget http://ck.kolivas.org/apps/cgminer/antminer/s3/4.6.1-141020/cgminer
d) chmod +x cgminer
e) /etc/init.d/cgminer restart (or simply reboot)

To check cgminer version type: cgminer-api version

Job done Wink

theseraphgabriel

newbie

Activity: 32

Merit: 0

Quote from: IYFTech on January 31, 2015, 02:02:17 PM

Quote from: idonothave on January 31, 2015, 01:26:53 PM

Quote from: IYFTech on January 31, 2015, 12:14:59 PM

Quote from: idonothave on January 30, 2015, 04:10:10 AM

I would like to share my deep doubts about the sense of changing cgminer queue parameter.
I know there are many guys here setting queue to 0, but documentation says there has to be 0+ (nonzero) value, so if You set 0 You set 1.
Bitmain sets default 4096 for S3, 8192 for S4/5 units. Personally I do not see ANY difference in what is set there. Yes, ckolivas has written few times, that probably that number is too high, but he also says, he is not author of a driver. So we have to suppose it is better to set there 1 just because it is default setting of cgminer?
Spondoolies... I do not have any idea what queue value is it using, but probably default, so probably 1. I did not study it too much, but are there the same chips? Probably not.

Deep doubts? I posted the results of queue 0 v queue 1 a while ago here:

https://bitcointalksearch.org/topic/m.8348972

It is not a hard & fast rule, as everyone has a different set up & different circumstances - so it's best to try both for a while & check the results. Also, I've only ever found that changing the queue setting to 0 only benefits Bitmain hardware, probably due to the inferior firmware/hardware, as my Spondoolies gear runs fine with the default cgminer queue setting of 1.

It's a case of testing, checking & testing again..... Wink

IYFTech so will this fix my p2pool issue as you can see in my images below my S1 works fine and finds share with a BS around 5 million but my S3 has never worked right highest best share in a week was 8 million.

Antminer S1
https://i.imgur.com/hXv9p9g.png

Antminer S3
https://i.imgur.com/k8AHDDh.png

Someone told me it was a "luck" thing but I don't think so having same issues with it on regular pool mining also...
Thank You. It seems clear. Can You please share which firmware/cgminer versions are You using there?

Yeah sure, the test was done using the August 26th firmware (antMiner_S320140826.bin) with ckolivas S3 binary that fixes the stale share submission issue that Bitmain ignored. I found this firmware to be the most stable version for my S3's, & when used with ckolivas's binary they finally performed as they should do with p2pool

I have that firmware on it now do you have a link to the ckolivas fix???
NVRmind I found link but how is it installed what just SSH in and exchange the cgminer in the S3 for this one?

Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 226. (Read 2591928 times)