Topic: [Guide] Dogie's Comprehensive ASICMiner Blade Setup - page 15. (Read 580761 times)

okay I got it thx

9337,9337
gbt.mining.eligius.st, gbt.mining.eligius.st

Could you be very specific please...

What did you type into which fields?

Problem solved!  Here's what I did:

Instead of using getwork, I used the gbt server and port on eligius.  For some reason I just can't get getwork to work any more.  Input these, delete the cookies from the previous config and restart.  I'll update with my hashrates tomorrow.  Currently (a few minutes after startup I'm doing 20.4 gh/s).

Thanks to all who contributed.  This successfully proves the hypothesis that n00bs can, indeed, learn  

Capiche.  thx, I'll give it a try.

If you're trying to connect to a remote pool's getwork, you'll need their server address in the Pool addresses field, their getwork port in the Pool ports field, and an accurate Gateway so outgoing internet traffic knows where to start routing.

My initial reply was to pluMmet, using the mining_proxy command line. If you're using the mining proxy on a local machine, it might help to change the default getwork port (-gp option) and make sure to match the setting with the Pool ports field in your blade. If for some reason a local bitcoind is running on your machine, or some other software is using port 8332, it could hose up communications. That's a simple thing to rule out.

Got it.  However, the port on the site is 8337 (just checked).  Can I go ahead and use something else?  I thought that was the port on their server?

I'd give you a screenshot but I had trouble uploading.

Sorry, I'm still (really) a noob at all this  

Yeah, one for each pool\user:pass set.

Okay, do you still have to input twice (I assume so?)

No, the getwork port that is usually 8332. The -gp option in mining_proxy changes this, and it needs to match the blade's "Pool ports" setting.

The 'Web Port' that's usually 8000?

Have you tried configuring worker/pass in the blade config and not using -cu -cp? Have you tried changing the getwork port -gp in case something on your local machine is using it?

Totally-- the weird thing is they were designed for getwork.  I even did a factory reset, reconfigged and it still doesn't work.  I'll maybe restart my router, and then I'll go to stratum though I'm not optimistic.

Will do, thanks.

It's a serious issue as I've tried lots of getwork pools and the blades don't work on any of them.

Dude, I'm having the same problem with getwork-- it's so frustrating, especially when I didn't change anything, the blades just stopped connecting.

Let me know if you get it figured out; I'll reciprocate if I discover what's happening.

I wanted it to use Eligius so I used (Dogies suggestion): mining_proxy.py -o mining.eligius.st -p 3334 -cu 1yourSweetCoinsComeToThisAddress -cp x

Not only did it not work the terminal ignored that and was trying to connect to Slushs pool.

I ended up just doing: mining_proxy.py which had the slushs stuff already going and the blades synced up right away.

It looks like the proxy.py has been nurfed to just use slushes pool. I d/l'd two days ago for the slushes pool site and it's not .tar anymore but .zip. Still linux of course.. well py anyway.

I have them running now even though slushs pool is not awarding me anything.

Beyond that this is ridiculous. I had been using getwork just fine for months.. I obviously know how to do that but the blades just won't do it.

v2 blades btw.

What's your command line look like for the proxy?

My Blades (2 of them) stopped working 2 days ago and I have no idea why.

On the Config screen I have no "x"'s and it's been great until now.

My whole system is on a UPS system even the cooling so I know it's never gotten hot and I'm stuck on why this has happened.

I've been using them with getwork which I keep seeing people trash but that is why I bought them and the rest of my equipment is utilized anyway.

I had an issue a week or so ago due to eligius going down and me scrambling to get the blades on any getwork system. eventually I got it back on eligius and it had been fine until 2 days ago.

I now have to divert a cpu and finally got them working but only using proxy on Slushs pool and that was 2 days ago (would not work on my preferred pool or the 2 others I tried).. I just found out that after initially reporting my blades as generating shares slushes pool though accepting hashes from me the whole time is not reporting them as credit to me and though my Blades are working fine right now Slushes pool says 0/mh. They were reporting fine when I final got them running 2 days ago and it looks like within 2 or 3 hours the pool just started not noticing that my workers have been doing their work.

checking on my workers on eligius is a great process on slushes pool its a nightmare just logging in.

I'm at my wits end with these Blades... They only work on 1 pool now and that pool in my mind is just horrible.

Right now I can put them to hash on a getwork pool and they do nothing..I put them back to mine proxy on Slushes pool and they are hashing away... but are not showing up on slushes pool at all.

Resetting my proxy terminal might get slushes pool to recognize but this is the reason I left that pool to begin with.

The proxy for what ever reason will not accept my doing stratum on another pool it just ignores my "-"flags. I have no choice in the matter.

WTF do I do?



Oh and also they hashed @ 10-11/mh on getwork and now 8/mh with proxy so boooo to you getwork haters...

Hello I wanted to thank dogie and many other members on this site, dogie's Blade Setup Guide helped me out especially.

I'll show off my rig if I may.

I have three ASICminer Blades setup at the moment powered by a Thermaltake 550w PSU.

Four 120mm fans. Two on the front sucking air in and two on the back blowing air out.

Fan controller with thermistats.

I used an old PC case with conduit to mount the blades. The side panels stay on the case usually.

https://dl.dropboxusercontent.com/u/90286356/2013-12-07%2020.41.39.jpg

https://dl.dropboxusercontent.com/u/90286356/2013-12-03%2017.38.20.jpg

https://dl.dropboxusercontent.com/u/90286356/2013-11-30%2021.11.06.jpg

This photo was taken before I used the conduit mount.

https://dl.dropboxusercontent.com/u/90286356/2013-12-03%2017.36.57.jpg

I have two more 120mm fans on order which i'm going to mount on the side panels.

My Raspberry Pi arrived today, might use that for the proxy. Also thinking about buying three more blades.

Overall I've had no hardware problems at all. One blade has been running 24/7 for about five weeks now and the other two for three weeks.

Did you try hitting "Switch server"? Sometimes these guys get locked and won't connect until you tell it to look at the secondary. Happened to me several times.

Hey guys,

I have a couple of Blades running for the past few months and I've been tweaking them a bit when running into issues with the chips, i.e. when I was getting one or more X in the "Chip: ..." diagnostics line.

One single X (might be XX), or a couple of them scattered among O's:

Probably heat related. Try power down, 5 min cool down and restart.
Your Blade may require more cooling.

XXXX or XXX (might be XX), sticky after power cycle

Probably voltage related. Locate the corresponding power lane, and use a multimeter to adjust the voltage to the required level (1.06 for low clock, 1.2 for high clock)

All XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

If 5 min cool down doesn't help,

- check PSU voltage under load (should be near 12V)
- check power lanes voltage (should be 1.06 or 1.2V)
- if low clock is OK but not high, your power lanes may need 1.2 instead of 1.06 V