At current difficulty, each Block Erupter takes about 4.3 years to make BTC1 - thats ignoring power use.

Have you paid the import tax?  It'll sit forever until you do.

I rolled back to 3.4.0 on OpenWRT and it's all working again, exact same command used between the two.  

3.5.0's Erupter support is confirmed broken.

I usually recommend BFGMiner.  Just avoid the newest 3.5.0 for now - it seems to be having USB driver issues.  3.4.0 is fine, though.

All your grounds in your house should be tied together.  If you're getting ground loops, then you need an electrician.

Probably will be OK, depends on what part of the chip is fried.  I had an old 5870 that wouldn't even display a picture, it just displayed random gibberish.  It mined fine.

No, it isn't.  p2pool only needs a few tens of kilobytes per second.  You could do that on 512k DSL no problems.  It's getblocktemplate latency that's the issue, which is purely bitcoind hogging CPU. 

But, hey, don't let facts get in the way of a good argument.

Ah, another armchair miner.    

So it's all slush's stratum proxy's fault?  So explain, Brianiac, how p2pool STILL doesn't work when you run the ASICMiner Blade on p2pool's getwork interface.  Or how it still doesn't work when using BFGMiner's getwork proxy?   Or how the Blades work on every other pool without issue?   No?  No answer?  Thought not.

This a hundred times.  Thread over.

They aren't making anything by mining - it's advertising speak.

My 2 ASICMiner Blades are making 1BTC every 40 days, rough estimate, at 511Mil difficulty.  That's at ~12GH each.  That means the 10x Block Erupters are making 1BTC every 160 days.  Each single one takes 1600 days, which is 4.38 years, assuming difficulty stays at 511M.  Which it won't.

Totally pointless.

The ONLY way to make money from Block Erupters is by selling them on eBay or Amazon to suckers.  Period.

Hopefully a lot of folks will just give up, which will keep diff steady, or lower it.

I'm back to 1BTC a month again, as I was with my GPUs about 6 months ago.   

Can't say I've seen that myself.


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.


Seems I did.   

If your machine is reasonably fast, it can run P2Pool, your miners, the lot.  Anything with an i3 or better is fine.

Well, no.  He's right, p2pool doesn't work on ASICMiner Blades, on the KnC machines...

p2pool also doesn't work for shit unless you're running it on a beast of a machine.  I'm talking fast i3 at the bare minimum.  I ran a p2pool node for a long time, and I just couldn't be bothered with it.  I had to run a dedicated machine using ~80W to host the node.  I was only putting 30GH though it, if I were running decent hashrates I don't know what sort of machine I'd have to run.  I tried it on lower powered machines, and the latencies were totally off the charts.  The 3.3GHz i3 with SSD drive was the only machine that would run it properly.

I loved the idea of p2pool, it's just a shame it hasn't kept up with the hardware people are using.  That's why p2pool is only running around 30-40TH.  If it worked better, more people would use it.  Out of all the people mining, how come there's only about 40 nodes that have any decent hashrate going though them?  Heck, the top hashing node is only 4TH...that's low.

You're high if you think p2pool is a good for option for those mining with ASICs. 

Block Erupters aren't working on 3.5.0 on OpenWRT either.  Tried all the various options, but they're not being picked up.  Same command as always used (screen -dmS bfg bfgminer -S all --http-port 8330).  Tried the --scan-serial options as well.

Unfortunately I'm on an SSH session via LogMeIn to my home PC from work, so I can't see what's physically happening, nor can I cold reboot.   

Seeing the same as someone above.  Until the 4th Nov my hashrate graph was smooth, between 25GH and 30GH.  Never above, never below.  The past few days it's fluctuating between 20GH and 40GH.  Same hashrate (28GH) at this end.

Less variance. 

Thread over.

It's f**king depressing. 

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.

What difficulty is your pool set to?

You want to be as close to 1 as possible for a small number of BEs.  Bigger difficulty shares will take forever on a few BEs, and probably lead to stales.