Biodom
Legendary
 Online
Activity: 3738
Merit: 3836
|
 |
December 20, 2016, 07:56:58 PM |
|
where does it go if you don't specify anything apart from kano.is-nevada or to closest depending on location?
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If you see garbage posts (off-topic, trolling, spam, no point, etc.), use the "report to moderator" links. All reports are investigated, though you will rarely be contacted about your reports.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
ZACHM
|
|
December 20, 2016, 08:02:19 PM |
|
Nevada if you don't specify. There is no auto-switching thing, that would create extra latency.
|
|
|
|
|
Biodom
Legendary
Online
Activity: 3738
Merit: 3836
|
|
December 20, 2016, 08:20:09 PM |
|
Nevada if you don't specify. There is no auto-switching thing, that would create extra latency.
cool, thanks |
|
|
|
|
|
gt_addict
|
|
December 20, 2016, 08:49:49 PM |
|
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?
|
**SUPPORT SIDEHACK** Miner Development Donations to: 1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr
Donations/Tips to:- 1GTADDicTXD1uachKKgW24DZDxDGhSMdRa
Join Bitconnect: https://bitconnect.co/?ref=gtaddict
|
|
|
|
elokk
|
|
December 20, 2016, 10:37:20 PM |
|
Anybody Kano miners in China other than Canaan? I was thinking about hosting some gear over there and pointing to the pool
|
t.me/bitcoinasic
|
|
|
firetreeactual
Legendary
 Offline
Activity: 952
Merit: 1003
|
|
December 20, 2016, 11:46:05 PM |
|
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.
|
To infinity and beyond...on two 741s and one of only 3...nope, make that 4...full nodes in Hawaii...on <30A. (I have other gear on the Hoth ice planet)
|
|
|
|
ZACHM
|
|
December 20, 2016, 11:51:43 PM |
|
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.
|
|
|
|
|
kano (OP)
Legendary
Offline
Activity: 4466
Merit: 1798
Linux since 1997 RedHat 4
|
|
December 21, 2016, 12:13:48 AM |
|
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?
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. |
|
|
|
Biffa
Legendary
Offline
Activity: 3220
Merit: 1220
|
|
December 21, 2016, 12:16:21 AM |
|
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.
|
|
|
|
kano (OP)
Legendary
Offline
Activity: 4466
Merit: 1798
Linux since 1997 RedHat 4
|
|
December 21, 2016, 12:27:13 AM |
|
Anybody Kano miners in China other than Canaan? I was thinking about hosting some gear over there and pointing to the pool
Not a lot. The main issue is the GFW for miners. Also, since a node requires a reliable always on connection, running a node across the GFW is inadvisable. Some days it would be OK and other days you'd get regular disconnects. I do run 2 nodes inside the GFW for block distribution (but no mining) and they do exactly that, randomly lose connection - and the way a node works they kick off the miners when that happens. That was the top of my todo list - distributing ckdb, but all this messing around with segwit (and some other diversions  ...) has meant I've not really touched ckdb code for a while and wont until it's all sorted - though all but the last bit of the segwit related stuff is done now and that will be completed shortly. |
|
|
|
tbonetony
Sr. Member
Offline
Activity: 441
Merit: 250
No zuo no die why you try, u zuo u die dont be shy
|
|
December 21, 2016, 12:36:51 AM |
|
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.
I have a backup of 20160715-550M fw for my batch 8ish. You can file a support ticket to BM and they should provide you a link to download it. |
|
|
|
Biffa
Legendary
Offline
Activity: 3220
Merit: 1220
|
|
December 21, 2016, 12:44:03 AM |
|
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.
I have a backup of 20160715-550M fw for my batch 8ish. You can file a support ticket to BM and they should provide you a link to download it. Thanks, but I've got a copy of the old firmware, the other two are happy with one at 550 and one at 556Mhz for now, so if I can get the third one rebooted I'll set it to 556Mhz and see if its stable. |
|
|
|
Biodom
Legendary
Online
Activity: 3738
Merit: 3836
|
|
December 21, 2016, 12:54:33 AM |
|
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.
yep https://bitcointalk.org/index.php?topic=789369.msg17237291#msg17237291good luck on restarting i will not bother with this "upgrayedd" again until... maybe never |
|
|
|
|
Biffa
Legendary
Offline
Activity: 3220
Merit: 1220
|
|
December 21, 2016, 01:05:19 AM |
|
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.
yep https://bitcointalk.org/index.php?topic=789369.msg17237291#msg17237291good luck on restarting i will not bother with this "upgrayedd" again until... maybe never heh, well its worth it if it helps find more blocks here imho I've got them running as well as they were before the upgrade now. Temps back to normal. These are all hosted, so gotta wait till remote hands do the reboot of the problem one. |
|
|
|
firetreeactual
Legendary
Offline
Activity: 952
Merit: 1003
|
|
December 21, 2016, 03:20:32 AM |
|
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.
If you were referring to me, it is. Nevada is the ~70ms; NY is the ~140ms. NY is 2.500 mi further than NV from me (HI). Sometimes physical distance isn't everything, though. Thought I'd try it. |
To infinity and beyond...on two 741s and one of only 3...nope, make that 4...full nodes in Hawaii...on <30A. (I have other gear on the Hoth ice planet)
|
|
|
|
ZACHM
|
|
December 21, 2016, 03:47:03 AM |
|
Yes, I was referring to you. If I am replying to a post directly above mine I do not quote it, I usually only use quotes if it is a few posts back. I think this keeps the threads a little cleaner. Yeah, I thought that Nevada would be better, but like you said distance isn't everything, so you never now until you try it. |
|
|
|
|
|
ComputerGenie
|
|
December 21, 2016, 04:41:17 AM |
|
... one has locked up or exploded or something...
Good technical reply. |
If you have to ask "why?", you wouldn`t understand my answer.
Always be on the look out, because you never know when you'll be stalked by hit-men that eat nothing but cream cheese....
|
|
|
xxxgeniy
Member
Offline
Activity: 89
Merit: 10
|
|
December 21, 2016, 10:27:27 AM |
|
BTClock by Rdawg! with 577.53THs ) First Block Today!  Go Go Kano!!!
|
St.Lapland Farm
|
|
|
scouse15
Newbie
Offline
Activity: 41
Merit: 0
|
|
December 21, 2016, 11:39:05 AM |
|
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?? Ok, so, I have read that the france one is no longer available. I am also in the UK, I have been mining for months to... stratum8080.kano.is:8080 I am wondering now if I should be mining to stratum8080.kano.de:8080 Please confirm ? Thanks |
|
|
|
|
kano (OP)
Legendary
Offline
Activity: 4466
Merit: 1798
Linux since 1997 RedHat 4
|
|
December 21, 2016, 12:02:25 PM |
|
stratum+tcp://de.kano.is:8080 If you are mining to fr.kano.is then you are already mining to de.kano.is fr.kano.is simply points to de.kano.is, ever since I announced that |
|
|
|
|
