Cablez
Legendary
Offline
Activity: 1400
Merit: 1000
I owe my soul to the Bitcoin code...
|
|
September 11, 2013, 08:51:52 PM |
|
You can 'overclock' them with the pencil mod but you cannot do it on a full rig if I am not mistaken.
You can do full rig but you need some thing to cool down boards or put heatsink on each board. I thought that was too much power for the regulator to handle. Definitely agree about upping the cooling.
|
Tired of substandard power distribution in your ASIC setup??? Chris' Custom Cablez will get you sorted out right! No job too hard so PM me for a quote Check my products or ask a question here: https://bitcointalk.org/index.php?topic=74397.0
|
|
|
Soros Shorts
Donator
Legendary
Offline
Activity: 1617
Merit: 1012
|
|
September 11, 2013, 10:53:25 PM |
|
You can 'overclock' them with the pencil mod but you cannot do it on a full rig if I am not mistaken.
You can do full rig but you need some thing to cool down boards or put heatsink on each board. I thought that was too much power for the regulator to handle. Definitely agree about upping the cooling. I've done it on a full rig, albeit moderately to about 440 GH/s. The regulator and 30A fuse are on each individual H-card.
|
|
|
|
Spotswood
|
|
September 11, 2013, 11:06:35 PM Last edit: September 11, 2013, 11:53:46 PM by Spotswood |
|
I had a bunch of issues with mine when I first set them up due to fans. They caused the boards to vibrate slightly and that killed my hashrate.
I moved the fan a LOT further away where they just keep the air moving around the cards. Now there's no problem.
You might be seeing a similar issue depending on your setup.
Ha! I thought this could be the reason, vibration induced by the flow, so I removed my fans from Spotswood case. I'll try to have them reversed, so that they suck up air through the cards instead of pushing it, this should cause less vibrations. We'll see. spiccioli Or you could put a bit more downward pressure onto the top edges of the h-boards by "raising" the rig a millimeter or two, by putting washers underneath each spacer ( between the extrusion and the spacer).
|
|
|
|
Swimmer63
Legendary
Offline
Activity: 1593
Merit: 1004
|
|
September 11, 2013, 11:45:31 PM |
|
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!
|
|
|
|
-Redacted-
|
|
September 11, 2013, 11:47:23 PM |
|
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)
|
|
|
|
Morblias
|
|
September 11, 2013, 11:55:51 PM |
|
I got my replacement M-board after first one was DOA, thanks Dave!
When I use pools that start with stratum+tcp:// it doesn't seem to work. I can connect fine to pools without that at the beginning, but with that it doesn't seem to start.
|
Tips / Donations accepted: 1Morb18DsDHNEv6TeQXBdba872ZSpiK9fY
|
|
|
-Redacted-
|
|
September 11, 2013, 11:57:05 PM |
|
You can't use http:// or stratum+tcp:// at the beginning of hostnames. Also, it doesn't like 8332 (for eclipsemc.com, for example) as a port number - use 3333 instead.
|
|
|
|
Morblias
|
|
September 11, 2013, 11:59:54 PM |
|
You can't use http:// or stratum+tcp:// at the beginning of hostnames...
Hmmm, my other cgminers have those in them as full path. without using stratum+tcp:// it doesn't seem like it is submitting shares to the pool I am using. My hashrate shows fine on the pool, but still has 0 accepted shares. Maybe it just takes a while before the pool updates, I will let it go for an hour or so.
|
Tips / Donations accepted: 1Morb18DsDHNEv6TeQXBdba872ZSpiK9fY
|
|
|
-Redacted-
|
|
September 12, 2013, 12:01:19 AM |
|
Yes, cgminer wants the http:// or stratum+tcp:// in front of the hostname. Chainminer isn't cgminer, and it doesn't work if you use them.
|
|
|
|
Morblias
|
|
September 12, 2013, 12:05:54 AM |
|
Yes, cgminer wants the http:// or stratum+tcp:// in front of the hostname. Chainminer isn't cgminer, and it doesn't work if you use them.
Ok thanks, I will wait a while and see if the pool just needs time to update. Also, is there anyway in SSH to show the chainminer screen (like in minepeon screen -r to show the cgminer screen)? I tried the screen -r which comes up with no screen to attach, and am not sure if it's possible to show it or not. It would be nice to see what is going on with my miner in SSH
|
Tips / Donations accepted: 1Morb18DsDHNEv6TeQXBdba872ZSpiK9fY
|
|
|
-Redacted-
|
|
September 12, 2013, 12:08:14 AM |
|
Yes, but not so easy. The screen is attached to root. You'll see a selection of available screens using "sudo screen -r", and can reattach to them using "sudo screen -r <proc_number>". Three of them are the stratum proxies, none of them show much of anything interesting real-time, unfortunately. The fourth shows some info about each chip as it gets programmed.
|
|
|
|
Morblias
|
|
September 12, 2013, 12:11:42 AM |
|
Yes, but not so easy. The screen is attached to root. You'll see a selection of available screens using "sudo screen -r", and can reattach to them using "sudo screen -r <proc_number>". None of them show anything interesting real-time, unfortunately.
Awesome! Thank you again. I got a screen open which shows the pool is accepting shares so I am all good. Just need the pool to update
|
Tips / Donations accepted: 1Morb18DsDHNEv6TeQXBdba872ZSpiK9fY
|
|
|
-Redacted-
|
|
September 12, 2013, 12:13:48 AM |
|
If you have a noncerate showing near at the top of the Bitfury admin page, you can be pretty sure that you're getting work and submitting shares. I submit to BTCGuild and have each of the three admin pool entries using a different worker number...
|
|
|
|
Swimmer63
Legendary
Offline
Activity: 1593
Merit: 1004
|
|
September 12, 2013, 12:24:21 AM |
|
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??
|
|
|
|
-Redacted-
|
|
September 12, 2013, 12:32:15 AM |
|
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).
|
|
|
|
Morblias
|
|
September 12, 2013, 01:02:52 AM Last edit: September 12, 2013, 01:20:31 AM by Morblias |
|
1 more noob question, is there a command to check the chip temps? or is that in some log file somewhere?
|
Tips / Donations accepted: 1Morb18DsDHNEv6TeQXBdba872ZSpiK9fY
|
|
|
-Redacted-
|
|
September 12, 2013, 01:05:13 AM |
|
No. There are no temperature sensors on these boards.
|
|
|
|
zurg
|
|
September 12, 2013, 02:06:52 AM |
|
OK, after much monitoring and troubleshooting I am thinking that my hashrate drop at Slushs's pool occurs about every 6 hours or so. The only way to bring it back up is stopping the miner and restarting it.
Any way I can make it auto restart every 2 hours?
|
|
|
|
superduh
|
|
September 12, 2013, 03:11:22 AM |
|
OK, after much monitoring and troubleshooting I am thinking that my hashrate drop at Slushs's pool occurs about every 6 hours or so. The only way to bring it back up is stopping the miner and restarting it.
Any way I can make it auto restart every 2 hours?
just switch to btcguild - heh
|
ok
|
|
|
Swimmer63
Legendary
Offline
Activity: 1593
Merit: 1004
|
|
September 12, 2013, 03:51:55 AM |
|
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.
|
|
|
|
|