KanoPool since 2014 🐈 - PPLNS and Solo 0.5% fee - Worldwide - 2435 blocks

[hhumaidan]

Block by Kais!

[1714815729]

1714815729

[1714815729]

1714815729

[1714815729]

1714815729

[Biodom]

good luck, it overheated a couple of my miners, so i had to rollback.

You opinion of "overheated" and the manufacture's seem to be 2 different things.  

what are you are talking about?
they were reaching 110-114C at some point before I rolled back.
good luck running your equipment at these temperatures.
note to myself: don't buy used equipment from the OP 

[ComputerGenie]

what are you are talking about?
they were reaching 110-114C at some point before I rolled back.
good luck running your equipment at these temperatures.
note to myself: don't buy used equipment from the OP  

...The miner with automatic frequency adjustment firmware will stop running when the Temp(Chips) reach to 125 -­135 ° C ,there will be a error message “ Fatal Error: Temperature is too high! ” shown in the bottom of kernel log page.
The fans peed must be set above 60% to keep the PCB temperature below 80°C,and chip Temperature below 115°C...

Last I looked, 114 < 115.
That being said, they aren't designed to run in a room with an ambient temp north of 27C.
There's a perverse irony in buying a Lamborghini and deciding that it idles too high while in 2nd gear.  

[kano]

On to a lighter subject
I guess few noticed, but no one asked, about the thread title.
Well I added another node the other day that can be mined to.
nya.kano.is

What's NYA? Well ... actually nya is the Japanese word for the sound a cat makes

or
https://www.youtube.com/watch?v=KlwVBKs5T_E

... oh and also ... it's in NY (New York)
If you are between the link between NY and Vegas it wont really help.
If you connect to NY and it's WAY faster than to Vegas then it may reduce your stales.

[ComputerGenie]

On to a lighter subject
...
http....

Dafuq did I just watch? 

[fvineyard]

So the ping times are better to NY than Vegas for me (being in Virginia). So if I was using:

stratum+tcp://stratum80.kano.is:80

Would I now use this?

stratum+tcp://stratum80.nya.kano.is:80

Thanks

[n200UG]

Upgraded my 2 S9s to v2.  Was a little harrowing to watch the kernel log and try to figure out what was going on.  Seemed to take forever with the first one.  Second one went much faster and the amazing thing was it gained about 1TH.  It had been showing a random smattering of bad asics under the old firmware and they all look good with the new.  I went from about 10.8TH/s to 11.8TH/s so I am impressed.

Now we need to given some time and make sure it is stable.

Note: These were both older, non-autotune batches.

Just did mine ... Suck! The frequency can only be change once. Has anyone been successful changing the FREQ with batch file ? Example pscp.exe -scp \cgminer.conf root@192.168.1.17:/config/cgminer.conf  

I haven't tried that with the new firmware but I used to do that with the old firmware for summertime heat.  The method ComputerGenie is referring to which he posted earlier is to use the web page on the miner: http://192.168.1.247/cgi-bin/minerAdvanced.cgi which still exists even though they removed the link to it.  Let me know if that actually works on an older miner that was upgraded to the newer firmware.

EDIT: The script I was using to change freq was developed with the help of this thread: https://bitcointalk.org/index.php?topic=956098.msg10462772#msg10462772

I still do this in summer, across all my miners. I even setup the batch in window Schedule days at a time base on weather condition. I'm guessing if the link still exist on the web interface the batch method most still be possible. I will test it this weekend.   

[kano]

So the ping times are better to NY than Vegas for me (being in Virginia). So if I was using:

stratum+tcp://stratum80.kano.is:80

Would I now use this?

stratum+tcp://stratum80.nya.kano.is:80

Thanks

stratum+tcp://nya.kano.is:3333
or 80 or 81 or 443 or 8080

...
If you are between the link between NY and Vegas it wont really help.
If you connect to NY and it's WAY faster than to Vegas then it may reduce your stales.

[Biodom]

what are you are talking about?
they were reaching 110-114C at some point before I rolled back.
good luck running your equipment at these temperatures.
note to myself: don't buy used equipment from the OP  

...The miner with automatic frequency adjustment firmware will stop running when the Temp(Chips) reach to 125 -­135 ° C ,there will be a error message “ Fatal Error: Temperature is too high! ” shown in the bottom of kernel log page.
The fans peed must be set above 60% to keep the PCB temperature below 80°C,and chip Temperature below 115°C...

Last I looked, 114 < 115.
That being said, they aren't designed to run in a room with an ambient temp north of 27C.
There's a perverse irony in buying a Lamborghini and deciding that it idles too high while in 2nd gear.  

this stuff is breaking up at 10-16% frequency by itself (at least earlier batches), so, no siree about 115C constantly, but you go ahead.
it will be instructive (or not).

[fvineyard]

Thanks Kano. I went for the trial and error method and got it right on the second try. I did not have a lot of stales but since my pings dropped from the 90's  to mid 20's so I figured why not make the change.

[ComputerGenie]

this stuff is breaking up at 10-16% frequency by itself (at least earlier batches), so, no siree about 115C constantly, but you go ahead.
it will be instructive (or not).

I could run mine @750M before they'd hit 115C; I'm not the one that decided to try to run a high-speed professional-grade miner in my home. 

[oh337]

Hello Kano and fellow miners! This is my first post and i hope to have many more. I just received my antminer s7-ln from newegg to get my foot in the door and begin my new hobby. So far, it's going great! My first pool chosen was this one, i'm "oh337". If all goes well over the next few months i plan to purchase a few more miners (hopefully s9's). I'm excited to be here with all of yous and learn my way around the forums. I'm mining out of Pennsylvania, USA. My rig is located in my basement and i plan to slowly increase the frequency daily using my colder basement temperature as an advantage. Best wishes to all! 

[n200UG]

Hello Kano and fellow miners! This is my first post and i hope to have many more. I just received my antminer s7-ln from newegg to get my foot in the door and begin my new hobby. So far, it's going great! My first pool chosen was this one, i'm "oh337". If all goes well over the next few months i plan to purchase a few more miners (hopefully s9's). I'm excited to be here with all of yous and learn my way around the forums. I'm mining out of Pennsylvania, USA. My rig is located in my basement and i plan to slowly increase the frequency daily using my colder basement temperature as an advantage. Best wishes to all! 

Warm welcome oh337 -  Lot of experienced people here willing to help. 

[kano]

Doing a quick ckdb restart (right now) coz someone found a code bug that could crash ckdb - though it has, unexpectedly, never so far
No miners will be affected.
Web page/API will show lotsa ? for about 10 minutes.

CKDB restart complete.
Was from 2016-12-20 09:39:00.877+00 to 2016-12-20 09:45:39.569+00 - 6mins 39seconds

[ComputerGenie]

Hello Kano and fellow miners! This is my first post and i hope to have many more. I just received my antminer s7-ln ... i plan to slowly increase the frequency daily...

Welcome aboard!

With the LNs, they do have slower fans than the S7 and ventilation is your friend if you want to push up the hashrate.

[kremit]

  ....

I did see that actually but does it work?  ....

... (will not solve your micromanaging issues for the fans, but you can set freq how ever high/low you want).

HI All,

I just loaded two S9 with V2. Be patient!!! the route i have gone with is i first load the normal update, it took more than usual to come back so i loaded the upgrade fix and then the regular update for v2 takes about 15-20 minutes to come back to life.

i upgraded two for now will run for about 24 hours and if all is good i will load my other 3...

good luck

My S9 (earlier batch) accepted the normal update after a few minutes of chugging along... but then something weird happened. I lost the connection to the web interface (it's in a nearby datacenter) even though it was "alive" and accepting shares on Kano. Turns out the MAC address of the network port changed and so it was given another IP address by DHCP. Not quite sure why the firmware update would change the MAC address.

[ComputerGenie]

.... Turns out the MAC address of the network port changed and so it was given another IP address by DHCP. Not quite sure why the firmware update would change the MAC address.

I have 3 LNs that are like that; they, literally, have a different MAC depending on which firmware I use.

[Make-A-Buck]

On to a lighter subject
I guess few noticed, but no one asked, about the thread title.
Well I added another node the other day that can be mined to.
nya.kano.is

What's NYA? Well ... actually nya is the Japanese word for the sound a cat makes

... oh and also ... it's in NY (New York)
If you are between the link between NY and Vegas it wont really help.
If you connect to NY and it's WAY faster than to Vegas then it may reduce your stales.

Thanks for the heads up kano. Switching to nya cut ping time in half from my location.
Connected via Verizon/Frontier FIOS outside of Tampa FL.
(Only had a stale count of 3 for up time of 6d19h21m24s)

ping stratum.kano.is
PING stratum.kano.is (104.194.28.194): 56 data bytes
64 bytes from 104.194.28.194: seq=0 ttl=52 time=84.316 ms
64 bytes from 104.194.28.194: seq=1 ttl=52 time=84.105 ms
64 bytes from 104.194.28.194: seq=2 ttl=52 time=83.932 ms
64 bytes from 104.194.28.194: seq=3 ttl=52 time=83.765 ms
64 bytes from 104.194.28.194: seq=4 ttl=52 time=83.618 ms
64 bytes from 104.194.28.194: seq=5 ttl=52 time=83.460 ms
--- stratum.kano.is ping statistics ---
6 packets transmitted, 6 packets received, 0% packet loss
round-trip min/avg/max = 83.460/83.866/84.316 ms

ping nya.kano.is  Changed to this 11:43 AM 12/20/2016 after uptime of 6d19h21m24s
PING nya.kano.is (104.207.132.42): 56 data bytes
64 bytes from 104.207.132.42: seq=0 ttl=47 time=44.395 ms
64 bytes from 104.207.132.42: seq=1 ttl=52 time=41.763 ms
64 bytes from 104.207.132.42: seq=2 ttl=47 time=44.093 ms
64 bytes from 104.207.132.42: seq=3 ttl=47 time=44.052 ms
64 bytes from 104.207.132.42: seq=4 ttl=52 time=41.291 ms
64 bytes from 104.207.132.42: seq=5 ttl=52 time=41.160 ms
--- nya.kano.is ping statistics ---
6 packets transmitted, 6 packets received, 0% packet loss
round-trip min/avg/max = 41.160/42.792/44.395 ms

Speaking of uptime... (I'm running a single R4 B2) how often should these miners be rebooted?  (or do you even need to?)
Is any work 'lost' because of a reboot or does it pick up right where it left off?
sry - I should head over to the noob section. These questions have prob already been answered.  

[ZACHM]

Yeah, nya cut my ping time more than half! Which makes sense because I'm in NY. 

[gt_addict]

Yeah, nya cut my ping time more than half! Which makes sense because I'm in NY.  

Just tested it myself (im in the UK) and the nya has cut mine from 139ms to 85ms. Not sure how much of an improvement it will make to worker figures but its worth the change and restart I suppose.

EDIT:  I have just realised you have a node in france.  Ill be changing to that one seeing as its 26ms.

I assume fro manother members previous post it would be

fr.kano.is:3333 or 80,81 etc etc??