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

Well mixed results with the move to 2.0

Had to clock two back to 550Mhz and one has locked up or exploded or something, gotta wait till someone reboots it then catch it before it overheats again.

New firmware seems to run a bit hotter than the original B13 firmware.

Wish there was a way to keep the existing firmware and just copy the miner binary over. hmm.

Yeah FR disappeared a while ago due to network problems there that they had no idea what was going on

It points to the DE node so the ping/connection is simply to germany.

I would think the one in Nevada would be faster for you based on distance. But I guess it depends on how the connections are routed.

Didn't ping it, but decided to move the A6 here at home over to NYA and see wha' hoppen. It was running a fair number of stales (the A7 next to it has none, though, over a period of several days...to LV) and I'll give it a couple of days to see how it churns out. I'll run some pings on the workstation a bit later. It came back up connected with no issue...we'll see.

EDIT: Well...did some pinging...NYA is around 140+ from here, while LV is (still) around 70+. I'll still let it run a bit on that node to get a baseline, but unless I see something unexpected I'll likely just go back to LV. All of that makes sense from where I'm at. Worth a try.

Anybody Kano miners in China other than Canaan? I was thinking about hosting some gear over there and pointing to the pool

Ok when I posted the pool title listed "FR" my miner is still showing up on the pool. Has the node been taken off or just the title changed?

cool, thanks

Nevada if you don't specify. There is no auto-switching thing, that would create extra latency.

where does it go if you don't specify anything apart from kano.is-nevada or to closest depending on location?

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??

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

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.  

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

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.

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.

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

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

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! 

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. 

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.