Quote from: HellDiverUK on September 11, 2013, 08:18:07 PM

That worked. Pleased to announce BFG is happily mining away with 11 Block Erupters on a TL-WR703N with a 4GB USB stick.

RAM is a bit tight, but I think it'd run the HTTP proxy thingymabob for the Blades, too, if a nice developer could compile it in. Wink

Very cool, I've been reading your posts hoping it would work out.

Congratulations HellDiver!

Luke, I want to thank you for what you have done and have sent a small donation your way. I recently rebuilt BFGminer on my pi with 3.2.0 and now with the new getwork option I have my USB's and my blade all happy together in one interface!

My only issue at this point is for some reason 3 out of my 25 sticks show up as BES instead of ICA and are giving me sick/dead restart problems. Before I changed to this version, I have been stable since I set it up. Impressive to say the least. I definitely want my blade connected through BFGminer... So I have isolated the 3 erupters that show up differently and pulled them, now BFG is running like a champ. Not a big deal since my windows machine is always running with my node and so I can just put the 3 "BES"sticks on there. Just thought I would add that information in case someone else is having a similar issue.

FYI...

I have tried with -G switch and without.
I have tried with the icarus timings and without
I have tried -S erupter:all and --scan-serial erupter:*

-S all with the icarus timings seems to give me the best results, but after a while the 3 sticks which show up as BES go to sick and sometimes dead, also randomly causing problems with other sticks in the process of restarting themselves etc. Staged work underrun will not increase automatically pass 36 keeps coming up every 2-3 min.. So far since I have removed those 3 from the equation, no messages about staged overrun and it looks like all is well. Hardware errors are also very low... Thanks for everything you do!

Edit: Still no issues, stable like it always was but just got this message "staged work underrun; increasing queue minimum to 2" Doesn't seem to be a problem, I'm sure it has said this many times before (but it's been running so good I haven't been watching it at all) and sorry for being such a newb but google doesn't want to tell me what it means.