Author

Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 2167. (Read 5352367 times)

sr. member
Activity: 440
Merit: 250
I don't mind smaller pools. If luck can wake up we start stacking up the coins.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Funny to see this block at only 150% after so long near 5PH/s
Just means your payout per block will be higher Smiley
hero member
Activity: 543
Merit: 500
full member
Activity: 224
Merit: 100
Funny to see this block at only 150% after so long near 5PH/s
legendary
Activity: 4354
Merit: 9201
'The right to privacy matters'
Rented 100 th I am tossing it here for a bit.
sr. member
Activity: 440
Merit: 250
I moved some stuff over to push this block.   Undecided
hero member
Activity: 700
Merit: 501
https://bitcointalk.org/index.php?topic=905210.msg
When I added my first SP20 here it takes a while to build up to the hashrate I usually see on other pools much faster.
I'm not complaining I want to understand.
Is it because I do not set a difficulty? Starting at 1k should be perfect for an SP20 and be right there at 1.3 1.6 however you have it setup.
I restored an S3, new used fans, re-pasted the chips, put it on the pool and local hashrate was straight to 450ish right away.
I try to pay attention and I know I've read the pool shows what matters. Does it truly take that long at any pool, do I have a poor connection, or something set wrong?
The 1 minute you see there means "rolling exponential average with 1 minute time constant" which means it gives you a more accurate estimate than grabbing just the last minute's shares and estimating a hashrate from them, but that also means if you start at zero it takes ~5 time constants to plateau meaning 5 minutes. The hashrate used as the accurate current hashrate on the website is the 5 minute time constant one so it takes even longer to rise. It does not mean your hashrate is less than on other pools during that time, it's just far more likely to give you an accurate estimate of hashrate. The per hashrate stats are now updated every minute on the website after one of the many changes recently added to both ckpool and ckdb instead of the old way which updated them every 10 minutes.

Specifically with the sp20, they go through a process of fine tuning each time they start as well so it takes them longer than S3s to get to their final hashrate.

Thank you very much for this level of detail in both yours and Kano's replies. It is refreshing.
legendary
Activity: 4354
Merit: 9201
'The right to privacy matters'
Payout 342302 sent and confirmed

Payment received thanks.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Payout 342302 sent and confirmed
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Thanks Kano, I have a question. Earlier you said tubes would be supported after the next restart. Did this every become implemented or was it cancelled due the bug you had mentioned? I tried to run them here and all shares were rejected, please look at my account stats.
I'll chase up what happened there - I think there was some extra change required that I didn't realise but yeah when all the restarting/debugging happen over the previous weeks, that pretty much got left in the dust.
It might be a "feature not working" issue.
It used to work and seems may be no longer functional?
I have seen a few workernames on the pool that include "tube" in the name with a bit higher than normal rejects, but still working.
If your one does work on other pools, then we'll have to add it back into the todo list for ckpool.
hero member
Activity: 546
Merit: 500
Thanks Kano, I have a question. Earlier you said tubes would be supported after the next restart. Did this every become implemented or was it cancelled due the bug you had mentioned? I tried to run them here and all shares were rejected, please look at my account stats.

You can proxy them through BFG miner and point the proxy here. I ran 3 for a while like that pointed here with no problems. If you need any info PM me.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Thanks Kano, I have a question. Earlier you said tubes would be supported after the next restart. Did this every become implemented or was it cancelled due the bug you had mentioned? I tried to run them here and all shares were rejected, please look at my account stats.
I'll chase up what happened there - I think there was some extra change required that I didn't realise but yeah when all the restarting/debugging happen over the previous weeks, that pretty much got left in the dust.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
sr. member
Activity: 351
Merit: 250
Thanks Kano, I have a question. Earlier you said tubes would be supported after the next restart. Did this every become implemented or was it cancelled due the bug you had mentioned? I tried to run them here and all shares were rejected, please look at my account stats.
full member
Activity: 214
Merit: 100
1KippERXwH1PdBxKNt1ksgqh89WBv6CtWQ
sr. member
Activity: 355
Merit: 276
hero member
Activity: 777
Merit: 1003
Another one found!

And lightsword found it without his 2ph on the pool.
full member
Activity: 214
Merit: 100
1KippERXwH1PdBxKNt1ksgqh89WBv6CtWQ
legendary
Activity: 1596
Merit: 1000
sloopy, good call on changing the PSUs on the S4s. They are garbage, I've had 4 out of 5 die so far. I'm using Delta 2000w (DPS-2000) as replacements with sidehack's breakout boards and couldn't be happier with them.
member
Activity: 105
Merit: 10
Has anyone updated their S4's with the new firmware from Bitmain Tech initramfs.bin.SD-20150129.tar.gz? Having problems with the new firmware update. When I change the frequency settings from stock, the miner will revert back to an old pool that I used to mine at. When I change the pool settings back to CKPool, it will revert the frequency settings back to stock settings. I have uploaded the backup copy of the miner before applying the new firmware, but without Joy, as in it's still doing the same thing.  

I had similar problems on 2 SD cards and this latest firmware update....one of them ended up dying completely and the other one wont allow any data to be written....it appears to take the settings but rebooting erases them and when I tried using SDFormatter it insists the write protect is on when I know its off...
FWIW both cards that had issues were ADATA 8GB class 10...I wont be buying any more of those
Simple solution: use a different SD card and a known working image from another machine...the readme says it fixes a uboot issue causing the miner not to boot...I seem to have more problems with that since this update also 1 board drops occasionally on a reboot which requires power off/on to get it back
Jump to: