|
Title: ASIC BLADE Problem Post by: hardhatmac on November 05, 2013, 03:10:32 AM Hello
What im doing wrong here . Why is the efficiency so low ? Thanks Hardhatmac Total MHS: 00816 Received: 0000006216 Accepted: 0000000471 Per Minute: 011.13 Efficiency: 007.57% Up Time: 0d,00h,42m,17s Current Server: gbt.mining.eligius.st:9337 Chip: OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO IP 192.168.100.200 Mask 255.255.255.0 Gateway 192.168.100.1 WEB Port 8000 Primary DNS 192.168.100.1 Secondary DNS 211.148.192.141 Ports 9337,9337 Server addresses gbt.mining.eligius.st,gbt.mining.eligius.st user:pass Title: Re: ASIC BLADE Problem Post by: CrazyGuy on November 05, 2013, 03:26:20 AM Setup a local stratum proxy.
Title: Re: ASIC BLADE Problem Post by: hardhatmac on November 05, 2013, 03:45:49 AM Hello
How do i setup a local stratum proxy? Thanks Hardhatmac Title: Re: ASIC BLADE Problem Post by: poochone on November 05, 2013, 06:49:47 AM http://mining.bitcoin.cz/mining-proxy-howto
Title: Re: ASIC BLADE Problem Post by: sidehack on November 05, 2013, 07:23:57 AM Running hot could also contribute to reduced efficiency. Some of the newer blades don't have very good heatsink contact with the board.
Title: Re: ASIC BLADE Problem Post by: HellDiverUK on November 05, 2013, 03:51:21 PM Hello What im doing wrong here . Why is the efficiency so low ? Current Server: gbt.mining.eligius.st:9337 GBT is wrong. You want Getwork. There's a big difference. The Blades only support getwork. You want getwork.mining.eligius.st:8337 Edit: got to love the armchair miners, replying when they haven't got a clue. ::) Title: Re: ASIC BLADE Problem Post by: pontiacg5 on November 05, 2013, 03:52:49 PM Hello What im doing wrong here . Why is the efficiency so low ? Current Server: gbt.mining.eligius.st:9337 GBT is wrong. You want Getwork. There's a big difference. The Blades only support getwork. You want getwork.mining.eligius.st:8337 No, you want a stratum proxy. I'm surprised anyone is even running an outdated getwork pool any more, and I doubt it will even be around much longer. Armchair miners... lol Title: Re: ASIC BLADE Problem Post by: HellDiverUK on November 05, 2013, 03:55:59 PM Hello What im doing wrong here . Why is the efficiency so low ? Current Server: gbt.mining.eligius.st:9337 GBT is wrong. You want Getwork. There's a big difference. The Blades only support getwork. You want getwork.mining.eligius.st:8337 No, you want a stratum proxy. I'm surprised anyone is even running an outdated getwork pool any more, and I doubt it will even be around much longer. Armchair miners... lol Well, lets get him working on the correct server to start off with. GBT is totally wrong. THEN we get him running on a stratum proxy. I've got my Blades pointed to a local proxy as the primary server, and backup is set to the getwork server on Eligius - that means when/if the machine running the proxy is rebooting/crashed, the Blades can mine on their own as long as the internet is still working. Title: Re: ASIC BLADE Problem Post by: CrazyGuy on November 05, 2013, 11:07:17 PM Hello What im doing wrong here . Why is the efficiency so low ? Current Server: gbt.mining.eligius.st:9337 GBT is wrong. You want Getwork. There's a big difference. The Blades only support getwork. You want getwork.mining.eligius.st:8337 No, you want a stratum proxy. I'm surprised anyone is even running an outdated getwork pool any more, and I doubt it will even be around much longer. Armchair miners... lol Well, lets get him working on the correct server to start off with. GBT is totally wrong. THEN we get him running on a stratum proxy. I've got my Blades pointed to a local proxy as the primary server, and backup is set to the getwork server on Eligius - that means when/if the machine running the proxy is rebooting/crashed, the Blades can mine on their own as long as the internet is still working. Blades are inefficient and restart very frequently when mining against a remote getwork server. Pointing to the eligius getwork server is a useless exercise, but if you are into wasting time I suppose that's your choice... Did you coin the term "armchair miner"? Title: Re: ASIC BLADE Problem Post by: HellDiverUK on November 06, 2013, 11:31:59 AM Blades are inefficient and restart very frequently when mining against a remote getwork server. Can't say I've seen that myself. Quote Pointing to the eligius getwork server is a useless exercise, but if you are into wasting time I suppose that's your choice... It's not. As I said, getting the guy pointing to the correct server is only the first step of getting him mining efficiently. What he's trying to do is drive a car on a lake. My suggestion is getting him off water and on to dry land. THEN we worry about getting him on the road and going quickly. Quote Did you coin the term "armchair miner"? Seems I did. :P Title: Re: ASIC BLADE Problem Post by: defcon23 on November 07, 2013, 10:58:37 AM Hello What im doing wrong here . Why is the efficiency so low ? Thanks Hardhatmac Total MHS: 00816 Received: 0000006216 Accepted: 0000000471 Per Minute: 011.13 Efficiency: 007.57% Up Time: 0d,00h,42m,17s Current Server: gbt.mining.eligius.st:9337 Chip: OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO IP 192.168.100.200 Mask 255.255.255.0 Gateway 192.168.100.1 WEB Port 8000 Primary DNS 192.168.100.1 Secondary DNS 211.148.192.141 Ports 9337,9337 Server addresses gbt.mining.eligius.st,gbt.mining.eligius.st user:pass hello, i can offer remote assistance to help you to config your blades; PM me if it's still a problem .. |