CK your last cgminer binary will not work with the Jan 2015 Bitmain S3 firmware. the cgminer that is part of the Jan 2015 firmware is version 4.70 not 4.6. Do you know if this has the fix in it.
No it doesn't. 
Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 209. (Read 2591920 times)
February 19, 2015, 04:18:06 PM
February 19, 2015, 11:18:36 AM
I'm running an s5 with the January firmware.
Is there anything I should do to improve performance on the P2Pool?
Is there anything I should do to improve performance on the P2Pool?
Change the queue setting to 0 or 1 - whatever gives you the lowest DOA/reject rate
February 19, 2015, 10:14:12 AM
I'm running an s5 with the January firmware.
Is there anything I should do to improve performance on the P2Pool?
Is there anything I should do to improve performance on the P2Pool?
February 19, 2015, 09:19:26 AM
CK your last cgminer binary will not work with the Jan 2015 Bitmain S3 firmware. the cgminer that is part of the Jan 2015 firmware is version 4.70 not 4.6. Do you know if this has the fix in it.
February 19, 2015, 06:39:32 AM
This seems like a problem if you rent hash?
Best bet for renting hash for use with p2pool is to stick to renters who advertise using Spondoolies boxes. You'll get less problems with the rental that way since they're great on p2pool.
February 19, 2015, 06:31:29 AM
So normal CGminer has submit stale on by default correct?
I know CK provided a fix for the S3, what do we do about the S5? (Assuming we need corrective action)
Is it safe to say that Spondoolies did this the correct way, that is submit stale is on by default?
S5 binary also available here (antminer's fork binaries still screw this up):I know CK provided a fix for the S3, what do we do about the S5? (Assuming we need corrective action)
Is it safe to say that Spondoolies did this the correct way, that is submit stale is on by default?
http://ck.kolivas.org/apps/cgminer/antminer/
Spondoolies do the right thing here.
@ck: Am I right in saying that this has to be applied after every reboot - or is there a way to make it permanent:
Code:
cd /tmp
wget http://ck.kolivas.org/apps/cgminer/antminer/s5/4.9.0-150105/cgminer
chmod +x cgminer
mv /usr/bin/cgminer /usr/bin/cgminer.bak
cp cgminer /usr/bin
/etc/init.d/cgminer.sh restart
This seems like a problem if you rent hash?
February 19, 2015, 05:58:29 AM
If someone has added himself to p2pool 3 days before 344101 block was found he would get paid the same amount as if he added himself 4 or 5 days before it?
Theoretically speaking, yes. It depends largely on your individual luck.
M
February 19, 2015, 05:48:07 AM
Replacing cgminer binary is permanent, after firmware update one should do it again
I'm not so sure about that, according to ck:
Here's a quick binary for the S5 based on bitmain's existing code which will ignore any queue parameter, not discard stales, should be able to ramp up smoothly if you find yourself on a very low diff pool, and use a little less CPU:
http://ck.kolivas.org/apps/cgminer/antminer/s5/4.9.0-150105/cgminer
Binaries will only be temporary so will not survive a machine reboot.
The following will change the cgminer binary for you (set the appropriate IP address), the default root password is "admin":
There should be a more comprehensive merge in the future into mainline cgminer, hopefully by Kano. Bitmaintech has provided us both with S5s to support cgminer development.
http://ck.kolivas.org/apps/cgminer/antminer/s5/4.9.0-150105/cgminer
Binaries will only be temporary so will not survive a machine reboot.
The following will change the cgminer binary for you (set the appropriate IP address), the default root password is "admin":
Code:
ssh 192.168.1.x -l root
cd /tmp
wget http://ck.kolivas.org/apps/cgminer/antminer/s5/4.9.0-150105/cgminer
chmod +x cgminer
mv /usr/bin/cgminer /usr/bin/cgminer.bak
cp cgminer /usr/bin
/etc/init.d/cgminer.sh restart
There should be a more comprehensive merge in the future into mainline cgminer, hopefully by Kano. Bitmaintech has provided us both with S5s to support cgminer development.
As far as I know the merge didn't happen yet, cos if it had we wouldn't have to download this binary.
February 19, 2015, 05:13:30 AM
So normal CGminer has submit stale on by default correct?
I know CK provided a fix for the S3, what do we do about the S5? (Assuming we need corrective action)
Is it safe to say that Spondoolies did this the correct way, that is submit stale is on by default?
S5 binary also available here (antminer's fork binaries still screw this up):I know CK provided a fix for the S3, what do we do about the S5? (Assuming we need corrective action)
Is it safe to say that Spondoolies did this the correct way, that is submit stale is on by default?
http://ck.kolivas.org/apps/cgminer/antminer/
Spondoolies do the right thing here.
@ck: Am I right in saying that this has to be applied after every reboot - or is there a way to make it permanent:
Code:
cd /tmp
wget http://ck.kolivas.org/apps/cgminer/antminer/s5/4.9.0-150105/cgminer
chmod +x cgminer
mv /usr/bin/cgminer /usr/bin/cgminer.bak
cp cgminer /usr/bin
/etc/init.d/cgminer.sh restart
Replacing cgminer binary is permanent, after firmware update one should do it again
February 19, 2015, 03:40:41 AM
So normal CGminer has submit stale on by default correct?
I know CK provided a fix for the S3, what do we do about the S5? (Assuming we need corrective action)
Is it safe to say that Spondoolies did this the correct way, that is submit stale is on by default?
S5 binary also available here (antminer's fork binaries still screw this up):I know CK provided a fix for the S3, what do we do about the S5? (Assuming we need corrective action)
Is it safe to say that Spondoolies did this the correct way, that is submit stale is on by default?
http://ck.kolivas.org/apps/cgminer/antminer/
Spondoolies do the right thing here.
@ck: Am I right in saying that this has to be applied after every reboot - or is there a way to make it permanent:
Code:
cd /tmp
wget http://ck.kolivas.org/apps/cgminer/antminer/s5/4.9.0-150105/cgminer
chmod +x cgminer
mv /usr/bin/cgminer /usr/bin/cgminer.bak
cp cgminer /usr/bin
/etc/init.d/cgminer.sh restart
February 19, 2015, 12:59:33 AM
So normal CGminer has submit stale on by default correct?
I know CK provided a fix for the S3, what do we do about the S5? (Assuming we need corrective action)
Is it safe to say that Spondoolies did this the correct way, that is submit stale is on by default?
S5 binary also available here (antminer's fork binaries still screw this up):I know CK provided a fix for the S3, what do we do about the S5? (Assuming we need corrective action)
Is it safe to say that Spondoolies did this the correct way, that is submit stale is on by default?
http://ck.kolivas.org/apps/cgminer/antminer/
Spondoolies do the right thing here.
February 19, 2015, 12:56:46 AM
If someone has added himself to p2pool 3 days before 344101 block was found he would get paid the same amount as if he added himself 4 or 5 days before it?
February 18, 2015, 10:10:38 PM
So normal CGminer has submit stale on by default correct?
I know CK provided a fix for the S3, what do we do about the S5? (Assuming we need corrective action)
Is it safe to say that Spondoolies did this the correct way, that is submit stale is on by default?
I know CK provided a fix for the S3, what do we do about the S5? (Assuming we need corrective action)
Is it safe to say that Spondoolies did this the correct way, that is submit stale is on by default?
February 18, 2015, 09:54:18 PM
It won't show-up on your node since it was orphaned or dead on P2Pool's pseudoshare chain. But since it was a valid on the real-chain, we get paid anyway.
I remember this happening before, is this really a problem?P2pool will come back, and we'll find blocks back to back or something. Luck is luck.
Not really a problem since we all still get paid. You just won't see it on normal nodes (Coincadence does additional Blockchain data capturing to show these pseudo-orphaned but valid blocks).
It definitely highlights why we should set our miners to submit all work though. If a miner is not set to submit all, this could have been thrown out and not submitted and we wouldn't have gotten paid.
Edit: words
February 18, 2015, 09:23:39 PM
It won't show-up on your node since it was orphaned or dead on P2Pool's pseudoshare chain. But since it was a valid on the real-chain, we get paid anyway.
I remember this happening before, is this really a problem?P2pool will come back, and we'll find blocks back to back or something. Luck is luck.
February 18, 2015, 09:07:38 PM
Thats what I did thanks
February 18, 2015, 05:47:38 PM
Looks like p2pool.info is locked up and not updating
p2pool.info hasn't worked since forrestv took it over many months ago - use http://minefast.coincadence.com/p2pool-stats.php
February 18, 2015, 05:47:03 PM
Looks like p2pool.info is locked up and not updating
Has been broken for a long time...
February 18, 2015, 05:37:51 PM
Looks like p2pool.info is locked up and not updating
February 18, 2015, 04:55:26 PM
So Good News & Bad News....
Good News - P2Pool finally broke through the drought and found a block. We got paid!!!
Bad News - The block that was found and valid/paid from bitcoind was an orphaned/dead P2Pool share so it won't show on your Nodes. So kids, let this be a reminder to always have your miners set to submit all otherwise we could be missing more Bitcoin valid shares that are dead on the pseudoshare chain.
\Good News - P2Pool finally broke through the drought and found a block. We got paid!!!
Bad News - The block that was found and valid/paid from bitcoind was an orphaned/dead P2Pool share so it won't show on your Nodes. So kids, let this be a reminder to always have your miners set to submit all otherwise we could be missing more Bitcoin valid shares that are dead on the pseudoshare chain.
Fantastic.. Back on the game.....
Just a quick reality check...
Not much has changed. The pool's hash rate is below 1 PH/s for the first time in a long time. According to my node, expected time to block is 2.7 days. That means ridiculous variance.
M
What I have noticed on the node I am mining on is that some miners are still there just not throwing as much hash at the pool. So maybe with them getting paid something they will be bring more back. Right now Share difficulty is :3634201.15 so a guy could pick up a lot of shares now just in case the hash rate takes a jump in the next few days. (unless my thinking is wrong?)
Jump to: