OK - I'm hashing. Two boards -one at 19 GH/s and one at 4 GH/s. Hmmm. Two under-performing boards and still not quite 25 GH/s.
Post the contents of /run/shm/.stat.log to find out what's going on. I assume I type that into the pi. I get Permission denied. |
|
|
|
Since your network is 192.168.0.xxx, it may not be liking the xxx.xxx.1.xxx address that's assigned.
First thing to try, assign it an address of 192.168.0.249, then "sudo reboot" and try to access it at 192.168.0.249 after a minute or two.
Next thing to try, set it up to automatically get an IP address assigned by your router. Make your interfaces file look like this, and your router should automatically assign it an IP inside your network. The important lines are bolded. Note that I have address, network, and broadcast commented out.
auto lo
iface lo inet loopback
iface eth0 inet dhcp
#address 192.168.1.50
netmask 255.255.255.0
#network 192.168.1.0
#broadcast 192.168.1.255
gateway 192.168.0.1
allow-hotplug wlan0
iface wlan0 inet manual
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
iface default inet dhcp
Excellent. Let me give these a try. Thanks Redacted! I'm in! Now to get this guy pointed to the right pool. Thanks again. Probably will be back for more help at some point. OK - I'm hashing. Two boards -one at 19 GH/s and one at 4 GH/s. Hmmm. Two under-performing boards and still not quite 25 GH/s. |
|
|
|
Since your network is 192.168.0.xxx, it may not be liking the xxx.xxx.1.xxx address that's assigned.
First thing to try, assign it an address of 192.168.0.249, then "sudo reboot" and try to access it at 192.168.0.249 after a minute or two.
Next thing to try, set it up to automatically get an IP address assigned by your router. Make your interfaces file look like this, and your router should automatically assign it an IP inside your network. The important lines are bolded. Note that I have address, network, and broadcast commented out.
auto lo
iface lo inet loopback
iface eth0 inet dhcp
#address 192.168.1.50
netmask 255.255.255.0
#network 192.168.1.0
#broadcast 192.168.1.255
gateway 192.168.0.1
allow-hotplug wlan0
iface wlan0 inet manual
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
iface default inet dhcp
Excellent. Let me give these a try. Thanks Redacted! I'm in! Now to get this guy pointed to the right pool. Thanks again. Probably will be back for more help at some point. |
|
|
|
Since your network is 192.168.0.xxx, it may not be liking the xxx.xxx.1.xxx address that's assigned.
First thing to try, assign it an address of 192.168.0.249, then "sudo reboot" and try to access it at 192.168.0.249 after a minute or two.
Next thing to try, set it up to automatically get an IP address assigned by your router. Make your interfaces file look like this, and your router should automatically assign it an IP inside your network. The important lines are bolded. Note that I have address, network, and broadcast commented out.
auto lo
iface lo inet loopback
iface eth0 inet dhcp
#address 192.168.1.50
netmask 255.255.255.0
#network 192.168.1.0
#broadcast 192.168.1.255
gateway 192.168.0.1
allow-hotplug wlan0
iface wlan0 inet manual
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
iface default inet dhcp
Excellent. Let me give these a try. Thanks Redacted! |
|
|
|
Could use some help. Unable to access the pi from a browser. I believe I have corrected the default gateway address to our networks. But when I try to pull up 192.168.1.249 in a browser I can't get in. Says " Oops! Google Chrome could not connect to 192.168.1.249" Miner appears to working. Chips are hot. Here are some screen shots. https://i.imgur.com/3rokbmB.jpghttps://i.imgur.com/cVDuT7g.jpgSuggestions would be appreciated. Connect a screen to the HDMI port, and a USB keyboard and manually setup the network parameters. My second rig came with 10.0.0.x addressing, not 192.x.x.x. Yes - the images are of the screen connected to the pi and the default IP has been changed to our network's default ip. I added the photos so someone more advanced then myself could check my work, but I am pretty sure that issue has been corrected. Followed Dave's instructions. Took two time, but the pi did save the change on the second try. The pics show a windows machine's network config's, not the pi. Are those the right pics? First pic of of the pi. See the bottom line - "pi@bitfury" |
|
|
|
Could use some help. Unable to access the pi from a browser. I believe I have corrected the default gateway address to our networks. But when I try to pull up 192.168.1.249 in a browser I can't get in. Says " Oops! Google Chrome could not connect to 192.168.1.249" Miner appears to working. Chips are hot. Here are some screen shots. https://i.imgur.com/3rokbmB.jpghttps://i.imgur.com/cVDuT7g.jpgSuggestions would be appreciated. Connect a screen to the HDMI port, and a USB keyboard and manually setup the network parameters. My second rig came with 10.0.0.x addressing, not 192.x.x.x. Yes - the images are of the screen connected to the pi and the default IP has been changed to our network's default ip. I added the photos so someone more advanced then myself could check my work, but I am pretty sure that issue has been corrected. Followed Dave's instructions. Took two time, but the pi did save the change on the second try. |
|
|
|
Could use some help. Unable to access the pi from a browser. I believe I have corrected the default gateway address to our networks. But when I try to pull up 192.168.1.249 in a browser I can't get in. Says " Oops! Google Chrome could not connect to 192.168.1.249" Miner appears to working. Chips are hot. Here are some screen shots. https://i.imgur.com/3rokbmB.jpghttps://i.imgur.com/cVDuT7g.jpgSuggestions would be appreciated. |
|
|
|
|
I'm interested in 25 if this GB starts to get going.
|
|
|
|
|
I don't like the wording of this letter. Maybe this is how the purchase agreement was framed and we don't have a choice. But it really says nothing about them being on time.
".....seven days or less until your chip order is scheduled to ship. Not READY to ship? Not CAN be shipped?
"Once we have confirmed receipt of the wire transfer, we will add your order into the queue for processing."
Not SHIP YOUR ORDER? Queue for processing what? The factory will ship the order won't it?
But maybe we have to pay prior to the "scheduled" shipping date.
I would suggest that before we pay, we ask for commitment to shipping date. If they are so close to being ready as to charge us then certainly they know what week or day the chips will ship.
I just have zero trust in this company and their wording purposely says nothing about actually shipping.
My .0002 BTC
|
|
|
|
|
Swimmer63; 10; 40; 1JNMtsVEf1RP26V1UR41scMYh2TxQFjUFT
Tx; dfdb96c6ebdf0f6963ba4fd45c4272aab1c23bda863e9d229175852020709577
(10 Blades + Back-Plane, GA) Email Sent
Swimmer63; 1; 4; 14ma1ET6KrGKqgqs3Coy2hSX2344b2Ca1b
Tx;380cad8d510239a699ce987e1a7878784f472840a056eca3a79d6e2f57ac2bbb
(1 Blade, FL) Email sent with 2nd Email for corrected Label.
Swimmer63; 1; 4; 1AMGsWtpXrC73fbFPnvyVRM99JkoG9jkkL
Tx; 2040b3e9d92761da3c49780a5c30479597449314699e5e876d23d5dfe5ab11a5
(1 Blade, Spain) Email sent with 2nd Email for corrected Label
Swimmer63; 1 + 6; 4.96; 1PbLcZnQypuBsQo2744YWoKvjTBZDay4Uq
Tx; 84b0701569d73e226aa0946e07b4b69baa677e5d38b6b39e6513be57a6252796
(1 Blade, 6 USB's, Netherlands) Email sent
|
|
|
|
It's "ifconfig". On a windows machine on your network, go to a command prompt and type "ipconfig". You'll see an entry for the correct gateway in what that command lists:
...
Link-local IPv6 Address . . . . . : fe80::4072:c744:ac4e
IPv4 Address. . . . . . . . . . . : 192.168.2.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
It might be set to something other than 192.168.0.1, like mine is (my gateway is 192.168.2.1).
I'm away from my miner now, but I did do this and got the same gateway. So I know that is correct. Tomorrow I will run ifconfig on the pi and check that and report. |
|
|
|
Double check the "address" entry in that file again, and/or check your router for the ip address. If you successfully changed the gateway, it may have been assigned a different IP address. On the Pi, you should be able to enter the ifconfig command and see a display like this that shows its IP:
pi@bitfury ~ $ ifconfig
eth0 Link encap:Ethernet HWaddr b8:27:eb:9c:49:63
inet addr:192.168.2.7 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:263752 errors:0 dropped:1 overruns:0 frame:0
TX packets:397420 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:37925441 (36.1 MiB) TX bytes:52238648 (49.8 MiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:30462510 errors:0 dropped:0 overruns:0 frame:0
TX packets:30462510 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4767221528 (4.4 GiB) TX bytes:4767221528 (4.4 GiB)
I get an error trying to do iconfig. But I put in the code line that Dave had us do to correct the gateway and it lists: Address 192.168.1.249 netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255 gateway 192.168.0.1 I think this means it did not change it?? |
|
|
|
|
Finally had time to make some setup progress. Had a monitor that would not work with the pi. Changed out monitors. Followed the instructions to correct the gateway address to my gateway. I went back and double checked. After two trys it stuck.
But now when I go one of my PC's and type the 192.168.1.249 in I just get "This Page can't be displayed." Tried it on two computers and two different browsers. Any thoughts? I'm close!
|
|
|
|
More blades have arrived today  THANK YOU! |
|
|
|
hi sorry about the confusion, between my incredibly busy life and the huge time zone difference between myself and lucko, and form we have some mis-communication. Please dont buy anything from the website until weve tested this board thoroughly. We will have prices and everything else worked out by the time the board is tested. thank you for being patient and sorry for confusing you - I was excited to finally get the PCBs in though  -JJ Thank you for the clarification JJ. Will wait to hear from you. |
|
|
|
They are definitely getting cheaper.
I'm guessing their cost on them is BTC.10 so this is as low as it goes probably without paying us to take them! I honestly think asicminer is producing these at as little as 0.03 BTC. They have no middle men for chips and other items so that brings cost down considerably. They might be producing them at that amount but , do you work for free? I don't think they are going to sell AT COST No I don't think they will sell at cost either. They will only continue to sell as long as they are turning a profit. I would assume the lowest they will sell at is 0.7-0.8 Their sales force (resellers) will drop out before it gets that low. If you can't make $5-6 a miner it's not worth the work. |
|
|
|
Outstanding JJ
If we are in Luckos GB do we need to order from you?
I'm in AZ.
All customers who are in North America can order from http://www.cointamination.com, if you have some sort of discount from Lucko contact him about that and we will work something out. We will have a solid coupon/discount solution for those who have earned discounts in the next day or so. thank you -JJ Any other options. $700 is a long way from the estimates. |
|
|
|
|
You would think there is a new chip coming from them. But if there is they will just use it themselves for 9 months then sell it.
|
|
|
|
|
I did. Just getting it up today. I was not going to start it up but it came with TWO boards.
So now I'm curious. They said if one was not hashing at the full 25 they would throw another in the box.
|
|
|
|
|
Outstanding JJ
If we are in Luckos GB do we need to order from you?
I'm in AZ.
|
|
|
|
|
Show Posts
