yeah the file unpacked is way too big, using win32dskmgr, but obviously it would not fit onto the poor little 8gb card.

i hope there's aversion that can be easily flashed.

thx.

rewards page you should be able to see how much btc is going to be paid to you , refer to block # then chk on block page, once confirmed with manual payout thats the amt going to you.

correct me if wrong.

those who are on sg node pls switch to main for now, some bugs.

kano n ck zzz now brb in few hrs.

same here, was talking to kano, they zzz now.

point to main for now till issues fixed.

ah ha, i was informed by kano just a hiwle ago. yes did not failover. not using ip addy though

advised to use main till next couple hrs. he off to bed. im on main.

3rd pcie melted

3 connected

3 pcie, 3rd can't see cuz it's molten pcie LoL

just a standard s7 no oc nothing powered with server psu.

not mine my friend's s7, sad to see though.

like i said new is NOT always good, for your viewing pleasure

https://bitcointalk.org/index.php?topic=1165628.msg13466880#msg13466880

waiting for mine, got a shipping label notification from UPS last couple of days but no movement yet. must be timezone & i think holidays ?

let's see some movement. yeah do update us.

not mine, my friend's s7, not b8 though .. for your viewing pleasure :

not b8 not mine, one of my friends s7 :

now it's back to normal at home i see the normal ip add:


C:\Users\xxx>ping sg.kano.is

Pinging sg.kano.is [139.162.5.112] with 32 bytes of data:
Reply from 139.162.5.112: bytes=32 time=38ms TTL=53
Reply from 139.162.5.112: bytes=32 time=36ms TTL=53
Reply from 139.162.5.112: bytes=32 time=35ms TTL=53
Reply from 139.162.5.112: bytes=32 time=36ms TTL=53

Ping statistics for 139.162.5.112:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 35ms, Maximum = 38ms, Average = 36ms

at dc :

C:\Users\User>ping sg.kano.is

Pinging sg.kano.is [2400:8901::f03c:91ff:fef1:5056] with 32 bytes of data
Reply from 2400:8901::f03c:91ff:fef1:5056: time=13ms
Reply from 2400:8901::f03c:91ff:fef1:5056: time=15ms
Reply from 2400:8901::f03c:91ff:fef1:5056: time=12ms
Reply from 2400:8901::f03c:91ff:fef1:5056: time=12ms

Ping statistics for 2400:8901::f03c:91ff:fef1:5056:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 12ms, Maximum = 15ms, Average = 13ms

maybe thats the problem causing miner not to hash or getting frozen ?

ck & kano shud be zzz now. let's see what happens. i'll just use my proxy for now.

thx for response guys

i see this when i ping sg.kano.is

C:\Users\User>ping sg.kano.is

Pinging sg.kano.is [2400:8901::f03c:91ff:fef1:5056] with 32 bytes of data:
Reply from 2400:8901::f03c:91ff:fef1:5056: time=12ms
Reply from 2400:8901::f03c:91ff:fef1:5056: time=13ms
Reply from 2400:8901::f03c:91ff:fef1:5056: time=14ms
Reply from 2400:8901::f03c:91ff:fef1:5056: time=13ms

Ping statistics for 2400:8901::f03c:91ff:fef1:5056:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 12ms, Maximum = 14ms, Average = 13ms

no ip address ?

main kano.is is ok

de is also ok

dash says it's dead & alive time to time but when it's back, miner hangs & does not failover.

happened about 3 & 1/2 hour ago from current post.

same issue, rebooted then ok, miners did not failover.

fixed now.

if sg dc server give prob, we send cit to go dc n smack that server !

SG had a dip, now seem to be up again.

have not set to main as failover, will do later, tied up atm. thx for looking into it. FIX FIX FIX.

btw where the block ? me hungry

n another, wanna see 3 or more in a row !

did i just see a block ?

yeehaaaaaaaaaaaaaaaaaaaaaaaaa

more more more !

try to set queue to 0 or 1 when mining on p2p

i think it might be able to help a little with this new fw

was out entire evening & realised it was down, fail over kicked in. prolly roughly 2 hours or so. SG is up now & all miners connected working normally.