ty but fan go to 100%....normal?
Only on startup, then it calms down
otherwise re-do it.solved with this
https://www.dropbox.com/s/a3qqhgh3awcrw1i/SD-S5-20150107_cgm_4_9_0-queue_1_submit.tar.gz?dl=0
thank you, and thank you -ck for this version
Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 125. (Read 2591920 times)
November 24, 2015, 09:50:41 AM
Only on startup, then it calms down
otherwise re-do it.solved with this
https://www.dropbox.com/s/a3qqhgh3awcrw1i/SD-S5-20150107_cgm_4_9_0-queue_1_submit.tar.gz?dl=0
thank you, and thank you -ck for this version
November 24, 2015, 09:34:53 AM
Runs fine yes, but the bitmain driver throws away what could be potential block solves on p2pool...
the problem is only for s7? or even s5 - s3....?
There is a discussion that contains all modified antminer drivers for p2pool?
Maybe does not make sense to do firmware forks for S *, so we are constantly catching up and more and more losing hashrate.
Now it is so small that it can be said that p2pool is dead.
And many of those who get ASICs, can never replace firmware and getting out on p2pool they switch to a another type of pools.
Maybe it's time for develpers to join and modify and adapt it for the new ASICs? Perhaps it's needed to rewrite it on C, as in Python it loads only one core and often on 100%
We need creative solutions, or this topic can be closed and we should stop our nodes and move to antpool, f2pool and similar.
As to your other points, we've discussed numerous times rewriting p2pool in a language that can handle multiple threads. Thus far, nobody's stepped up to take on that challenge. Even so, rewriting the pool code in C or some other language will not handle the underlying problem of crappy cgminer forks not submitting shares which could be solving blocks.
November 24, 2015, 09:29:36 AM
Runs fine yes, but the bitmain driver throws away what could be potential block solves on p2pool...
the problem is only for s7? or even s5 - s3....?
There is a discussion that contains all modified antminer drivers for p2pool?
.. but it certainly isn't the only one 
.
.Do you think it's just bad luck or other?
As to your other question regarding luck... yes, I believe it is just poor luck. We are experiencing normal swings in variance. As I initially mentioned, S7s are certainly a potential influencing factor since there are no (to my knowledge, -ck/kano can correct me) updated cgminer binaries for it. However, I don't know how many people currently mining on p2pool are using S7s, so I don't have any reference for how much of an impact it might have
. 
November 24, 2015, 09:28:14 AM
Runs fine yes, but the bitmain driver throws away what could be potential block solves on p2pool...
the problem is only for s7? or even s5 - s3....?
There is a discussion that contains all modified antminer drivers for p2pool?
Maybe does not make sense to do firmware forks for S *, so we are constantly catching up and more and more losing hashrate.
Now it is so small that it can be said that p2pool is dead.
And many of those who get ASICs, can never replace firmware and failing on p2pool they switch to a another type of pools.
Maybe it's time for develpers to join and modify and adapt it for the new ASICs? Perhaps it's needed to rewrite it on C, as in Python it loads only one core and often on 100%
We need creative solutions, or this topic can be closed and we should stop our nodes and move to antpool, f2pool and etc.
November 24, 2015, 09:07:29 AM
ty but fan go to 100%....normal?
Only on startup, then it calms down
otherwise re-do it. November 24, 2015, 09:04:52 AM
ty but fan go to 100%....normal?
November 24, 2015, 09:02:07 AM
thank you
I have 3 s5 ... you can write me the command ssh for install?
ty
S5 binary install:
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
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 is NOT persistent - re-do after reboot.
Or you can use this firmware version:
https://www.dropbox.com/s/a3qqhgh3awcrw1i/SD-S5-20150107_cgm_4_9_0-queue_1_submit.tar.gz?dl=0
Which is persistent through reboots.
November 24, 2015, 08:47:03 AM
thank you
I have 3 s5 ... you can write me the command ssh for install?
ty
What Forrest thinks about this situation? His help here is very needed!
All want hear him here.
I think that need rewriting of p2pool sources whith multicore computing support.
+1 All want hear him here.
I think that need rewriting of p2pool sources whith multicore computing support.
November 24, 2015, 08:39:20 AM
Runs fine yes, but the bitmain driver throws away what could be potential block solves on p2pool...
the problem is only for s7? or even s5 - s3....?
There is a discussion that contains all modified antminer drivers for p2pool?
.. but it certainly isn't the only one .
.Do you think it's just bad luck or other?
Antminer binaries: http://ck.kolivas.org/apps/cgminer/antminer/
Bad luck, rising diff, crap firmware, lack of hash power - all of these are contributory factors I'm afraid, although bad luck & high diff affects all pools, not just p2pool.
November 24, 2015, 08:35:21 AM
Runs fine yes, but the bitmain driver throws away what could be potential block solves on p2pool...
the problem is only for s7? or even s5 - s3....?
There is a discussion that contains all modified antminer drivers for p2pool?
November 24, 2015, 08:32:14 AM
What Forrest thinks about this situation? His help here is very needed!
All want hear him here.
I think that need rewriting of p2pool sources whith multicore computing support.
All want hear him here.
I think that need rewriting of p2pool sources whith multicore computing support.
November 24, 2015, 08:19:47 AM
Runs fine yes, but the bitmain driver throws away what could be potential block solves on p2pool...
the problem is only for s7? or even s5 - s3....?
There is a discussion that contains all modified antminer drivers for p2pool?
.. but it certainly isn't the only one .
.Do you think it's just bad luck or other?
November 24, 2015, 08:00:48 AM
That everyone updated their gear to S7s, but because they did now p2pool doesn't find any blocks because those same S7s throw away potential solutions?
Sure... I suppose that could be one of the reasons... but it certainly isn't the only one.
Sure... I suppose that could be one of the reasons... but it certainly isn't the only one
. November 24, 2015, 07:50:53 AM
could this be the cause of the recent bad luck?
November 24, 2015, 06:44:38 AM
I think it would encourage more miners to p2pool if they knew their S7's worked properly here.
My S7 runs fine on p2pool...
November 24, 2015, 04:18:12 AM
I think it would encourage more miners to p2pool if they knew their S7's worked properly here.
My S7 runs fine on p2pool...
November 23, 2015, 10:02:41 PM
With all these S7's flying out the door, p2pool is missing out due to the usual bitmain firmware that broke cgminer.
I'd like to suggest starting a bounty for kano to do his magic on the S7 as he did with previous bitmain firmwares - I think it would encourage more miners to p2pool if they knew their S7's worked properly here.
We need moar powa!
No point sending me any BTC I'd like to suggest starting a bounty for kano to do his magic on the S7 as he did with previous bitmain firmwares - I think it would encourage more miners to p2pool if they knew their S7's worked properly here.
We need moar powa!
Until I get the S7 that was supposedly gonna be sent to me ... ages ago ... I'm just gonna wait on that.
Though maybe Bitmain didn't like the idea of me getting one before they pushed the network above where I wouldn't lose money mining with it more than 9hrs a day
I was thinking if I got it in the first batch I'd be able to mine 18hrs a day, but now it's already approaching a loss for me to use it anything more than the 9hrs each night when my elec is cheap
... but they don't really care either way anyway, my fixes have been in master cgminer for more than a year and a half now and they aren't in the S7 either ...
How about if you had access to an S7 via ssh? Or I could volunteer one of mine for testing purposes?......
EDIT: Or could I install the mainline cgminer into an S7?
... yes I do actually still have every old miner I got since I started mining
(though not sure if they all still work ...)
I've sold 2 miners over the years, that I had more that one of each of the 2 I sold.
November 23, 2015, 09:11:59 PM
With all these S7's flying out the door, p2pool is missing out due to the usual bitmain firmware that broke cgminer.
I'd like to suggest starting a bounty for kano to do his magic on the S7 as he did with previous bitmain firmwares - I think it would encourage more miners to p2pool if they knew their S7's worked properly here.
We need moar powa!
No point sending me any BTC I'd like to suggest starting a bounty for kano to do his magic on the S7 as he did with previous bitmain firmwares - I think it would encourage more miners to p2pool if they knew their S7's worked properly here.
We need moar powa!
Until I get the S7 that was supposedly gonna be sent to me ... ages ago ... I'm just gonna wait on that.
Though maybe Bitmain didn't like the idea of me getting one before they pushed the network above where I wouldn't lose money mining with it more than 9hrs a day
I was thinking if I got it in the first batch I'd be able to mine 18hrs a day, but now it's already approaching a loss for me to use it anything more than the 9hrs each night when my elec is cheap
... but they don't really care either way anyway, my fixes have been in master cgminer for more than a year and a half now and they aren't in the S7 either ...
How about if you had access to an S7 via ssh? Or I could volunteer one of mine for testing purposes?......
EDIT: Or could I install the mainline cgminer into an S7?
November 23, 2015, 09:04:27 PM
Finds blocks very rarely. Why is that?
because global hashrate on P2Pool don't evolve ... but Bitcoin hashrate skyrocket
Global warming?
November 23, 2015, 08:56:45 PM
With all these S7's flying out the door, p2pool is missing out due to the usual bitmain firmware that broke cgminer.
I'd like to suggest starting a bounty for kano to do his magic on the S7 as he did with previous bitmain firmwares - I think it would encourage more miners to p2pool if they knew their S7's worked properly here.
We need moar powa!
No point sending me any BTC I'd like to suggest starting a bounty for kano to do his magic on the S7 as he did with previous bitmain firmwares - I think it would encourage more miners to p2pool if they knew their S7's worked properly here.
We need moar powa!
Until I get the S7 that was supposedly gonna be sent to me ... ages ago ... I'm just gonna wait on that.
Though maybe Bitmain didn't like the idea of me getting one before they pushed the network above where I wouldn't lose money mining with it more than 9hrs a day
I was thinking if I got it in the first batch I'd be able to mine 18hrs a day, but now it's already approaching a loss for me to use it anything more than the 9hrs each night when my elec is cheap
... but they don't really care either way anyway, my fixes have been in master cgminer for more than a year and a half now and they aren't in the S7 either ...
Jump to: