|
681
|
Bitcoin / Pools / Re: [35 PH] ** 5x AVALON6 GIVEAWAY ** Kano CKPool (kano.is) [0.9% PPLNS] US,DE,SG
|
on: May 06, 2016, 08:28:13 PM
|
I moved my 4 S7's over to bitmain.
it seems every time I move them kano hits a block!
I sure hope it's not my miners causing the issues.
I'm securely behind a firewall..could this really be a thing???
This is not a good place to talk about mining anywhere but on kano pool. However, for the sake of bitcoin you should: a) Mine on smaller pools. Hashrate distribution is good for the bitcoin ecosystem, hashrate consolidation is bad for it. b) Not hash on chinese pools. And despite what the dude from fishpool might think, this isn't a racist comment. More than half of the network hashrate is concentrated in a single country, a country which is known to have packet inspection filters which slow data transmission into and out of the country. This is bad for bitcoin. We happen to be talking about China but it would be true no matter what country it was. |
|
|
|
|
683
|
Bitcoin / Hardware / Re: ANTMINER S7 is available at bitmaintech.com with 4.86TH/s, 0.25J/GH
|
on: May 06, 2016, 01:42:14 AM
|
In the interest of safety, I was thinking about changing the point at which the S7 stops from 80 Celsius down to something like 70 Celsius. Has anyone come across where that value of 80 is stored? I found some stuff in /config that was close, but not it. I really don't want to do a grep of 80 on the entire filesystem or anything else like that  If you find where to change this please let me know. I have looked, but not to lower it, to raise it. I can't find it. If you turn off the setting to stop mining at 80 it will stop at 90 anyway and I can't find anything to disable that. |
|
|
|
|
687
|
Bitcoin / Pools / Re: [35 PH] ** 5x AVALON6 GIVEAWAY ** Kano CKPool (kano.is) [0.9% PPLNS] US,DE,SG
|
on: May 01, 2016, 03:00:20 AM
|
Thought so. So all the large rentals are effectively lowering the earnings due to the larger pool hash rate, while lowering the chance to hit a block.
No it doesn't work like that. The shares that arrive at the pool are evaluated at that time. Even though there will have been delay in getting them to the pool they won't be producing an artificial increase in pool hashrate because the pool will either accept or reject them at the moment they arrive at the pool. What you are really looking at is increased chance for stales and probably wasted hashrate in the form of rejects. If the miners pointed at NH were pointed directly at kano pool then the work updates and submissions would have less latency but as long as the share is still valid when it arrives at the pool through the more circuitous route through NH, it still has as much chance of producing a block as any other share. I hit a block on the pool with a rental this past month. The latency just means that more of those arriving shares will have become rejects (or potentially stales) due to that latency then would have otherwise been the case. Really the loss here, if there is any, will be on the person who paid the rental. I believe the shares will be deemed valid by NH and so part of the rental expense, and paid by NH to the actual miner, even though they may be deemed invalid by the kano pool due to latency. |
|
|
|
|
689
|
Bitcoin / Pools / Re: [30 PH] ** 5x AVALON6 GIVEAWAY ** Kano CKPool (kano.is) [0.9% PPLNS] US,DE,SG
|
on: April 27, 2016, 08:07:45 PM
|
Anyone know where blocks 409066, 409062 went? They haven't shown up in my wallet yet. This part of the same weirdness that was going on yesterday?
N8
Those two blocks have not been payed out yet...last block out was 408929. Be patient, they will be out later today  we are sitting on 8 blocks I think 2 confirmed and 6 waiting to confirm. and I had good 5n for all of them  Last block I have a payment from is 408877. EDIT: Now that I look at totals I see that the wallet has them listed in a different order, presumably because they all confirmed in the same block and it doesn't care about when they were broadcast. So yeah, 408929 looks like the last one. |
|
|
|
|
691
|
Bitcoin / Hardware / Re: ANTMINER S7 is available at bitmaintech.com with 4.86TH/s, 0.25J/GH
|
on: April 25, 2016, 03:31:11 PM
|
step 1) release $100 off coupons to drum up new business step 2) take down site which is responsible for confirming network connectivity in bitmain cgminer script so miners arrive doa strep 3) await slew of foolish americans re-ordering parts to troubleshoot because they know support will take weeks to sort out any issues. step 4) Profit! anyone wanna buy some spare io and bb boards? That code is only active in the older miners. I have a batch 8 with original Dec 2 firmware that has this code commented out so they haven't been selling miners with this issue in 5 months. Also the site in question never belonged to bitmain so they didn't take it down. It was (maybe still is) a DNS for a chinese ISP which is probably only used because it is easy to remember just like 8.8.8.8 in the US. |
|
|
|
|
692
|
Bitcoin / Pools / Re: [30 PH] ** 5x AVALON6 GIVEAWAY ** Kano CKPool (kano.is) [0.9% PPLNS] US,DE,SG
|
on: April 22, 2016, 10:46:57 PM
|
Yeah not sure what's up with blocktrail and blockchain not showing the payout transactions before they are confirmed today.
The last 5 payouts I've sent (in the last hour) are:
408360 22807123e353a876093dca394512266ed7ddce9d2301346aa9edb952f1822bda
408368 c2596266b5d5e943c9d6bcc4a50bc0697519e2ae69a500e06d94ce7185312374
408373 5669c8134ffa1be3ac6aa4b61eb440ee5d0729d311e7fcc7177aae36211d8cf5
408392 e7a37e1f1ea9ada2379a9b9597a321dd76d5cfc381d1acb98f41cecfea368c2f
408395 bfb0a3bb5a2dafa51922e63db79ec9095b0ab5e54db7c517570eec4d53b45cf8
They're all in our block work, so the next block we find should confirm them all.
well for blockchain anyway: Transaction rejected by our node. Reason: The Maximum number of outputs in a single transaction is 250 They suck but they are consistent about it.  blocktrail just doesn't seem to be seeing them blockexplorer.com sees them |
|
|
|
|
693
|
Bitcoin / Hardware / Re: ANTMINER S7 is available at bitmaintech.com with 4.86TH/s, 0.25J/GH
|
on: April 22, 2016, 06:55:57 PM
|
That one above is an S5. Here is an S7 Batch 8 or 9. Looks like that bit is commented out: # check network state
#network_ok=`ping -c 1 114.114.114.114 | grep " 0% packet loss" | wc -l`
#if [ $network_ok -eq 0 ];then
# return
#fi
# gpio1_16 = 48 = net check LED
if [ ! -e /sys/class/gpio/gpio48 ]; then
echo 48 > /sys/class/gpio/export
fi
echo low > /sys/class/gpio/gpio48/direction
gateway=$(route -n | grep 'UG[ \t]' | awk '{print $2}')
if [ x"" == x"$gateway" ]; then
gateway="192.168.1.1"
fi
if [ "`ping -w 1 -c 1 $gateway | grep "100%" >/dev/null`" ]; then
prs=1
echo "$gateway is Not reachable"
else
prs=0
echo "$gateway is reachable"
fi
#ping $gateway -W1 -c1 & > /dev/null
#prs=$?
if [ $prs = "0" ]; then
echo heartbeat > /sys/class/leds/beaglebone:green:usr3/trigger
echo 1 > /sys/class/gpio/gpio48/value
else
echo none > /sys/class/leds/beaglebone:green:usr3/trigger
return
fi
sleep 5s
I have an S7 from batch 3 or 4 (I can't remember which). I'll take a look at it. I also just realized that 192.168.1.1 is not the correct gateway on these machines although that address does exist on my network. Well there it is in the older firmware: network_ok=`ping -c 1 114.114.114.114 | grep " 0% packet loss" | wc -l`
if [ $network_ok -eq 0 ];then
return
fi
# gpio1_16 = 48 = net check LED
if [ ! -e /sys/class/gpio/gpio48 ]; then
echo 48 > /sys/class/gpio/export
fi
echo low > /sys/class/gpio/gpio48/direction
gateway=$(route -n | grep 'UG[ \t]' | awk '{print $2}')
if [ x"" == x"$gateway" ]; then
gateway="192.168.1.1"
fi
if [ "`ping -w 1 -c 1 $gateway | grep "100%" >/dev/null`" ]; then
prs=1
echo "$gateway is Not reachable"
else
prs=0
echo "$gateway is reachable"
fi
#ping $gateway -W1 -c1 & > /dev/null
Not commented out. So maybe a firmware update would be enough to fix the problem for anyone who has it. EDIT: Just noticed that Cyper_BLC can't use the firmware update because he has the controller controlling extra cards. Cyper_BLC looks like you can put # symbols in front and comment it out per the instructions from lanfeusst above. If you are on Windows download Putty to SSH into the miner. To connect just put in root@<miner IP> as shown below  when it connects, use the password admin Then use the steps from lanfeusst above. |
|
|
|
|
694
|
Bitcoin / Hardware / Re: ANTMINER S7 is available at bitmaintech.com with 4.86TH/s, 0.25J/GH
|
on: April 22, 2016, 06:50:00 PM
|
This is what I see in my S5. do_start() {
# gpio1_16 = 48 = net check LED
if [ ! -e /sys/class/gpio/gpio48 ]; then
echo 48 > /sys/class/gpio/export
fi
echo low > /sys/class/gpio/gpio48/direction
gateway=$(route -n | grep 'UG[ \t]' | awk '{print $2}')
if [ x"" == x"$gateway" ]; then
gateway="192.168.1.1"
fi
if [ "`ping -w 1 -c 1 $gateway | grep "100%" >/dev/null`" ]; then
prs=1
echo "$gateway is Not reachable"
else
prs=0
echo "$gateway is reachable"
fi
#ping $gateway -W1 -c1 & > /dev/null
#prs=$?
if [ $prs = "0" ]; then
echo heartbeat > /sys/class/leds/beaglebone:green:usr3/trigger
echo 1 > /sys/class/gpio/gpio48/value
else
echo none > /sys/class/leds/beaglebone:green:usr3/trigger
return
fi
sleep 5s
..and so on... Looks like it only checks for the gateway. I'll check out an S7 in a second. |
|
|
|
|
696
|
Bitcoin / Hardware / Re: ANTMINER S7 is available at bitmaintech.com with 4.86TH/s, 0.25J/GH
|
on: April 22, 2016, 06:11:24 PM
|
|
I restarted both of my S5's a couple of hours ago without issue. 114.114.114.114 is apparently a DNS server in china. It may indeed be down since it is not responding to DNS queries from me but I am on the outside of the great firewall so maybe that is normal? I have all of my miners set with static IP's and 8.8.8.8 for DNS.
|
|
|
|
|
697
|
Bitcoin / Hardware / Re: ANTMINER S7 is available at bitmaintech.com with 4.86TH/s, 0.25J/GH
|
on: April 22, 2016, 03:49:01 PM
|
my 3 b1 S7 miners goes to silence yesterday, they can reachable but dont hashing, cgminer cant start hashing. i tried nearly everything 1 solution is flash new firmware and go. but i am using 6hashboards  latest version is not handle 6 hashboards. I suspect for date settings with ntpd . like a timebomb. change date settings to 2015 not works. any ideas ? i am not linux guy i cant figured out. Are you saying you had 3 miners all stop working at the same time? If so that doesn't sound like a problem with the miners, it sounds like a network problem. Do you have backup pools configured? Do the pools show alive or dead? |
|
|
|
|
700
|
Bitcoin / Hardware / Re: ANTMINER S7 is available at bitmaintech.com with 4.86TH/s, 0.25J/GH
|
on: April 21, 2016, 02:54:03 PM
|
Hi, i have a problem with a miner: it only shows the temp of two boards, the central one is NOT showed. What can i do to fix this??
Thanks!!
If it's mining fine, do nothing. You have a bad a temp sensor I guess. I wouldn't be too worried since you two good sensor ... the unit will detect if it is overheating or not. I have asked before with bitmain and as long as you have a good sensor they say you should be good. This goes all the way back to S3 day's they were happy if just one was working, so in your case with 2 you should be fine as even if another failed still have one. You only really need one for it to shutdown if it get's to hot. But I know the feeling getting a new one and seeing one dead my first time I got that I thought was something to worry and it's not. Your MUCH better off running it then going weeks possibly without a hashing board for a temp sensor (and I don't think they would take a RMA for just temp sensor anyways). I have a machine that has a board that often reports a zero temp but occasionally it reports some random temp, I have seen numbers from the 30's to 140's. What sucks is that the miner will not mine if the temp is reported above 90. If you turn off the checkmark to stop mining above 80 it will indeed mine with a temp between 80 and 90 but there does not appear to be any way to make it mine with a temp reported above 90. I have poked around in the file system and can't find anything to disable that. So when it reports a temp above 90 all I can do is power cycle it over and over again until it reports a temp below that. It usually runs for days without that erroneous temp changing (whatever it is) but every so often it just changes, and if it randomly changes to something above 90 it stops mining. I don't have a way to remotely power cycle it either so sometimes I have to get in the car and drive down to the miner's location and power cycle it over and over to get it back up and working. I am thoroughly unimpressed with the S7's both in terms of the price (including the drastic price drops) and the quality. These look likely to be the first miners I have bought since Butterfly fucking labs that will not even break even. |
|
|
|
|
Show Posts
