[Guide] Dogie's Comprehensive ASICMiner Blade Setup

[matt4054]

I also had 3 x'es within the O's just after a reconfiguration + restart.

Restarted again with fingers crossed, only one x remaining, and I set the clock to low.
Re-restarted still with fingers crossed, all x'es went away, all O's.
Set the clock back to high, waited for 30 mins, still all O's. Phew!

I wonder if these issues are heat related. Anyone experienced it, added cooling and didn't happen again?

[1714827786]

1714827786

[pikeadz]

I also had 3 x'es within the O's just after a reconfiguration + restart.

Restarted again with fingers crossed, only one x remaining, and I set the clock to low.
Re-restarted still with fingers crossed, all x'es went away, all O's.
Set the clock back to high, waited for 30 mins, still all O's. Phew!

I wonder if these issues are heat related. Anyone experienced it, added cooling and didn't happen again?

For me, my "x" didn't start until after a reconfiguration also.  The first time it happened it was after the initial setup.  Then today it happened when I switched pools.  Both times I "fixed" it by changing the clock to low again, and possibly another reset (can't remember it was fixed after the reset or the change in clock).  Then it works fine again on high.

The cooling setup is the same for this blade as my first, which has never displayed an "x" but also has firmware 0.2 (not sure if that's relevant or not).

[Lucky - Luciano]

I also had 3 x'es within the O's just after a reconfiguration + restart.

Restarted again with fingers crossed, only one x remaining, and I set the clock to low.
Re-restarted still with fingers crossed, all x'es went away, all O's.
Set the clock back to high, waited for 30 mins, still all O's. Phew!

I wonder if these issues are heat related. Anyone experienced it, added cooling and didn't happen again?

     I do not think cooling is concerned. Otherwise I do not understand much criticism for cooling. My blade is cooled with a single ASUS fan of 12 cm forward. The fan blows cold air on the right side of the blade. The blade is in the vertical position (standing on their part with the cooler). BLADE is overclocked cool as a cucumber. I can not believe that such a stable made.I think even my overclocked BLADE can operate without a fan.

[drlatino999]

I also had 3 x'es within the O's just after a reconfiguration + restart.

Restarted again with fingers crossed, only one x remaining, and I set the clock to low.
Re-restarted still with fingers crossed, all x'es went away, all O's.
Set the clock back to high, waited for 30 mins, still all O's. Phew!

I wonder if these issues are heat related. Anyone experienced it, added cooling and didn't happen again?

     I do not think cooling is concerned. Otherwise I do not understand much criticism for cooling. My blade is cooled with a single ASUS fan of 12 cm forward. The fan blows cold air on the right side of the blade. The blade is in the vertical position (standing on their part with the cooler). BLADE is overclocked cool as a cucumber. I can not believe that such a stable made.I think even my overclocked BLADE can operate without a fan.

I'll hit mine with a Infrared thermometer tomorrow, and I can get you some rough numbers to compare against. I can test with no cooling, 1x200mm, 1x200mm+1x120mm, and 1x200mm+2x120mm.

[matt4054]

I have experimented a bit, and it seems "normal" (at least not shockingly bad) that sometimes, some chips appear as 'x' instead of 'O' right away after reconfiguring + restarting. Waiting for a minute and restarting (sometimes multiple restarts are needed) seems to get rid of the 'x' and turn them back to 'O'. Fair enough for me as long as it says under control...

[Soros Shorts]

Has anyone successfully operated these blades in a subnet other than 192.168.1.0/24?

I was unable to switch to other subnets (tried 192.168.15.0/24 and 172.25.100.0/16), so I am just assuming that this is another one of the quirks of the communications firmware.

[Caesium]

Yes, I ran mine in 192.168.0/24 just fine - didn't try any other netmask though.

[WinTame2012]

Has anyone successfully operated these blades in a subnet other than 192.168.1.0/24?

I was unable to switch to other subnets (tried 192.168.15.0/24 and 172.25.100.0/16), so I am just assuming that this is another one of the quirks of the communications firmware.

I run it on other than default subnet with /24 mask.

[Soros Shorts]

Yes, I ran mine in 192.168.0/24 just fine - didn't try any other netmask though.

Has anyone successfully operated these blades in a subnet other than 192.168.1.0/24?

I was unable to switch to other subnets (tried 192.168.15.0/24 and 172.25.100.0/16), so I am just assuming that this is another one of the quirks of the communications firmware.

I run it on other than default subnet with /24 mask.

OK, thanks. I must have missed something.

[Phil21]

Has anyone successfully operated these blades in a subnet other than 192.168.1.0/24?

I was unable to switch to other subnets (tried 192.168.15.0/24 and 172.25.100.0/16), so I am just assuming that this is another one of the quirks of the communications firmware.

Yeah, works fine for me.  I do use a /24 though, haven't tried any other length than that.

[josh_nc]

All:

I thought you'd like to know the stats of these new blades. After 1 hour of operation (no proxy, will test proxies later on with one of the blades).
On both blades I have the voltage at 1.262 at full work load. Total brick amp at 2.08 A and 239 Watts stable. I have a large dual fan at the back (blades vertical) blowing on the chips and one 6" fan on half of each heat sink. Heat sinks are only slightly warm on the non ventilated side where I keep track of the temp by back of the hand feel. All seems to be in great working order. Please let me know if 1.262 is pushing too much.

Blade 1 (Margie):

Total MHS:    12833
Received:    0000014731
Accepted:    0000014625
Per Minute:    175.39
Efficiency:    099.28%
Up Time:    0d,01h,23m,23s

Current Server: btcguild.com:8332
Clock selected: High

Blade 2 (Lucy):

Total MHS:    13007
Received:    0000011295
Accepted:    0000011235
Per Minute:    177.72
Efficiency:    099.46%
Up Time:    0d,01h,03m,13s

Current Server: btcguild.com:8332
Clock selected: High

Total hashing at 25840 MH/s. Awesome!!!

Margie and Lucy ain't going nowhere anytime soon!

Many many thanks to forsetifox at irc #ozcoin,  Friedcat and Dogie for all your support and tips. I could not have overcome all of the issues without you all.

For those having problems between the blades and a local host, make sure the ip of the local host (say your pc) matches the ip of the blades to the second last portion of the ip. Example:

if the mask is 250.250.250.0  and the blade ip is aa.bb.cc.xx then the ip of the local host needs to be aa.bb.cc.yy. Only the last 2 entries (xx and yy) are different.


J/

[dogie]

There is no reason to have the voltages so high, 1.2 is is fine. Any more is just wasting power, creating more heat and reducing life span.

Also get a stratum proxy set up.

[drlatino999]

Update on the most annoying blade on the world:

Gave it it's own PSU so there is no more sharing of lines with my ESXi server, and received my Procurve switch from the bitcoinstore:



Vindication is mine! And wintame's as well for helping me troubleshoot this thing.

[WinTame2012]

Update on the most annoying blade on the world:

Gave it it's own PSU so there is no more sharing of lines with my ESXi server, and received my Procurve switch from the bitcoinstore:



Vindication is mine! And wintame's as well for helping me troubleshoot this thing.

Glad to see you are running well finally. Enjoy securing the Bitcoin network

[dogie]

Found my 3rd block. Would be 280% my pool earnings :/

[WinTame2012]

Found my 3rd block. Would be 280% my pool earnings :/

How long it was from the 1st block found and how much hashing power do you use in solo?

[josh_nc]

There is no reason to have the voltages so high, 1.2 is is fine. Any more is just wasting power, creating more heat and reducing life span.

Also get a stratum proxy set up.

When I started the blades the voltages were all around 1.206V. Then I tried a little higher then higher still and now both blades are at 1.282 and 241Watts. The wattage increased by only 2W from the original 239 Watts measured at the brick plug into the killawhat . I now have one blade on btc guild getwork at ~12.7 GH/s and the other blade on slush stratum via proxy hashing at ~13 GH/s. My next step is to slowly reduce the voltages to see where is the max hashing at ~240 Watts.

J/

[dogie]

Found my 3rd block. Would be 280% my pool earnings :/

How long it was from the 1st block found and how much hashing power do you use in solo?

Found a block with 26GH within a week, then another with 52 after another 3 weeks. Final one after another week. I was mining on pool though, so I earn't nothing.

[WinTame2012]

There is no reason to have the voltages so high, 1.2 is is fine. Any more is just wasting power, creating more heat and reducing life span.

Also get a stratum proxy set up.

When I started the blades the voltages were all around 1.206V. Then I tried a little higher then higher still and now both blades are at 1.282 and 241Watts. The wattage increased by only 2W from the original 239 Watts measured at the brick plug into the killawhat . I now have one blade on btc guild getwork at ~12.7 GH/s and the other blade on slush stratum via proxy hashing at ~13 GH/s. My next step is to slowly reduce the voltages to see where is the max hashing at ~240 Watts.

J/

Just to note: hashing speed is nothing to do with the voltage as far as all chips are working (displays OOOOOOOO in web-interface).

[WinTame2012]

Found my 3rd block. Would be 280% my pool earnings :/

How long it was from the 1st block found and how much hashing power do you use in solo?

Found a block with 26GH within a week, then another with 52 after another 3 weeks. Final one after another week. I was mining on pool though, so I earn't nothing.

Too bad Which pool you're mining at?