dacman61
Member
Activity: 87
Merit: 10
|
 |
September 13, 2013, 01:38:21 AM |
|
Ok, I am about had it with Slashe's constant weird fluctuations.
Trying to setup Bitminter pool,.. but I just cant seem to figure it out.
2. Enabled (1 or 0), Pool address, port, user, password
Yes mint.bitminter.com 8332 workername_BF password
But when I fire that off just by itself Hashrate drops to 0 so I know it's not connecting.
Am I missing something?
Chainminer doesn't always like ports that aren't 3333. It specifically doesn't like port 8332. Change that to 3333 and it should work for you. I got nothing.  Even tried port forwarding in the firewall... Zurg, For BitMinter for your username, make sure you type in your username as "username_workname" Ex. dacman61_dacman61worker I had the same problem as you... Also I was using port 8332 |
|
|
|
|
|
zurg
|
|
September 13, 2013, 11:56:07 AM |
|
Ok, I am about had it with Slashe's constant weird fluctuations.
Trying to setup Bitminter pool,.. but I just cant seem to figure it out.
2. Enabled (1 or 0), Pool address, port, user, password
Yes mint.bitminter.com 8332 workername_BF password
But when I fire that off just by itself Hashrate drops to 0 so I know it's not connecting.
Am I missing something?
Chainminer doesn't always like ports that aren't 3333. It specifically doesn't like port 8332. Change that to 3333 and it should work for you. I got nothing. Even tried port forwarding in the firewall... Zurg, For BitMinter for your username, make sure you type in your username as "username_workname" Ex. dacman61_dacman61worker I had the same problem as you... Also I was using port 8332 Yeah, their instructions are not very clear. lol I actually got ahold of the owner on IRC and we had it rolling shortly.  I did go back to Slush's pool for a bit now as it seems to be giving me the best bang for the hashrate. 8min, 9min per block. So far in the fiasco I lost about 1/2 of mining or so.. At 1.6097 BTC at 1week and 20 hours. |
|
|
|
|
|
zurg
|
|
September 13, 2013, 01:05:39 PM |
|
Ok, today for some weird reason running nano /run/shm/.stat.log through SSH is reporting 240 chips, to bad after 25 they are all at 0, lol
Where before it would stop at 25.
I didn't reboot my Pi either.. go figure, lol.
Dave, I think my invisible boards past 2nd one are defective, please send new, lmao.
|
|
|
|
|
|
jspielberg
|
|
September 13, 2013, 01:11:07 PM |
|
For what it is worth, my soldering attempts to jumper the "problem" chips and revive the rest of the board was unsuccessful. I have de-soldered the jumpers and I am back where I started. I will probably need to cut the leads, which I am unlikely to do until more of my pre-orders start showing up. Right now this board represents a large percent of my total hashing power.
|
|
|
|
|
|
zurg
|
|
September 13, 2013, 01:23:06 PM |
|
For what it is worth, my soldering attempts to jumper the "problem" chips and revive the rest of the board was unsuccessful. I have de-soldered the jumpers and I am back where I started. I will probably need to cut the leads, which I am unlikely to do until more of my pre-orders start showing up. Right now this board represents a large percent of my total hashing power.
Ahh, quit being a wuss and cut it. lol just kidding. |
|
|
|
|
dacman61
Member
Activity: 87
Merit: 10
|
|
September 14, 2013, 02:34:11 PM |
|
Guys heads up on pencil mod for overvolting and thus aiding overclocking.
Use pencil mod on R2F, make it around 1.1 - 1.2K, voltage goes from 0.66V to 0.81V. The default value is ~1.3K. It may blow the 30AFuse if you go too high; so make sure you do it only if you have a soldering station handy  After Mod (I have only 3 H cards ) Bank 1
1: 30.781GH/s
2: 33.315GH/s
3: 30.022GH/s
4: 0GH/s Do you know where you can find some good instructions for this "pencil mod"? Thanks! |
|
|
|
|
|
juhakall
|
|
September 14, 2013, 02:50:24 PM |
|
Guys heads up on pencil mod for overvolting and thus aiding overclocking.
Use pencil mod on R2F, make it around 1.1 - 1.2K, voltage goes from 0.66V to 0.81V. The default value is ~1.3K. It may blow the 30AFuse if you go too high; so make sure you do it only if you have a soldering station handy After Mod (I have only 3 H cards ) Bank 1
1: 30.781GH/s
2: 33.315GH/s
3: 30.022GH/s
4: 0GH/s Do you know where you can find some good instructions for this "pencil mod"? Thanks! |
|
|
|
|
Swimmer63
Legendary
Activity: 1593
Merit: 1004
|
|
September 14, 2013, 03:38:31 PM |
|
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. |
|
|
|
|
|
mdbssm
|
|
September 14, 2013, 03:44:44 PM |
|
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. |
|
|
|
|
Swimmer63
Legendary
Activity: 1593
Merit: 1004
|
|
September 14, 2013, 03:47:35 PM |
|
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. |
|
|
|
|
|
mdbssm
|
|
September 14, 2013, 03:51:01 PM |
|
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? |
|
|
|
|
Swimmer63
Legendary
Activity: 1593
Merit: 1004
|
|
September 14, 2013, 04:08:09 PM |
|
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" |
|
|
|
|
|
Foofighter
|
|
September 14, 2013, 04:21:41 PM |
|
the problem is oviously the wrong sub ip?
you are using: 192.168.0.xx
miner is using: 192.168.1.xx
|
ex official Canaan Distributor (Cryptouniverse)
|
|
|
|
-Redacted-
|
|
September 14, 2013, 04:23:04 PM |
|
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
|
|
|
|
|
Swimmer63
Legendary
Activity: 1593
Merit: 1004
|
|
September 14, 2013, 04:26:27 PM |
|
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! |
|
|
|
|
Swimmer63
Legendary
Activity: 1593
Merit: 1004
|
|
September 14, 2013, 04:33:25 PM |
|
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. |
|
|
|
|
Swimmer63
Legendary
Activity: 1593
Merit: 1004
|
|
September 14, 2013, 04:52:13 PM |
|
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. |
|
|
|
|
Syke
Legendary
Activity: 3878
Merit: 1193
|
|
September 14, 2013, 04:53:37 PM |
|
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. |
Buy & Hold
|
|
|
Swimmer63
Legendary
Activity: 1593
Merit: 1004
|
|
September 14, 2013, 04:56:29 PM |
|
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. |
|
|
|
|
Syke
Legendary
Activity: 3878
Merit: 1193
|
|
September 14, 2013, 05:01:33 PM |
|
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. Type "cat /run/shm/.stat.log" and post the output. |
Buy & Hold
|
|
|
|
