Slush's reward payout is not working again... have been over my threshold for a few hours, but nada....  |
|
|
|
|
Reward payment eventually happened, abt 2 hours later...
|
|
|
|
Reward payout not happening again on time.... crossed the threshold twice already but the pool holds on to the BTC.... |
|
|
|
 ))))) so good to be back )))) |
|
|
|
|
Does the lower hash rate and higher HW error apply to all BE's or only to some?
I had a case where 3 of my BE's developed a much higher HW error rate and had lower hash rate than others. I disabled them, removed them, allowed them to cool down then inserted them into free ports on another hub, and this 'cured' them.
To disable specific BE: with Bfgminer in focus, type 'm', then select the one that you want to disable with the arrow keys, then type 'd', wait until its LED lights up constantly, then you can remove it.
(by the way, if you used "-S erupters:all" in your command line/short cut, instead of "-'S all", you would get the option 'I' to identify the units, but some people claim that this reduces the hash rate).
Good luck
|
|
|
|
|
has anything else change? ambient temp? are the Eruptors running hotter than before?
(your bfgminer settings seem to be normal)
|
|
|
|
I had BTC as a backup, obviously not the perfect one... |
|
|
|
|
BTC guild reports
"UPDATE: As of approximately 1:00 PM (Pacific Time), the attacks resumed.
UPDATE: As of approximately 10:15 AM (Pacific Time), the attacks seemed to have stopped."
Looks like a DDOS attack on a few pools
|
|
|
|
|
My miners switched to a backup pool, now Slush's rate is getting back, at 59 TH now...
|
|
|
|
|
Suggest that you try bfgminer 3.2.1, I had significantly lower HW errors after moving from 3.1.4 to 3.2.0 then 3.2.1. It may not fully solve your problem, but will help. Also check if any of your power adapters is running either very hot or cooler than normal (if one died, the others will try to compensate, but will be overloaded). If one of them is 'cool' (I would suspect the 2A ebay ones), then measure its output voltage (disconnect the power plug, use a voltage meter to measure between the inner contact and the outer sleeve), if you don't read 5V, then it is 'dead'. You can replace this with a suitable power adapter from your local electronics store or on-line. You may find that you can run more Eruptors with a higher capacity power adapter.
Good luck
|
|
|
|
|
BTC guild also had a very sharp drop...(440 -> 286 TH) ?!
|
|
|
|
|
using both stick-on small heatsinks on the component side to cool the Asic and a couple of USB fans helps keep my USB BE's much cooler to the touch than running them uncooled.
|
|
|
|
|
Julz,
I'm interested in one, please check your email
Cheers
|
|
|
|
|
Julz,
Thanks for the quick BE transaction on Sunday, it was a pleasure to met you in person
Do you still offer a discount to prior customers?
Cheers
|
|
|
|
|
if you use BFGMiner, use the latest version (3.2.0) instead of 3.1.4 listed in the BTC Guild. Ver 3.2.0 has a significantly lower HW error rate than 3.1.4 (I had HW of about 1.2% with 3.1.4 which dropped to about 0.75% with 3.2.0, note that you need to wait for things to settle down and average, don't panic if one BE has a higher error in the first few minutes).
Enjoy your mining
|
|
|
|
|
I replaced the original plug pack that came with the cheap 10 port USB 2.0 hub with another unit (same plug into the hub, same polarity, but a much higher current specification, 4A instead of 2A in this case).
If you try bfgminer, use the latest version (3.2.0) which has a lower HW error rate than earlier versions. You'll need to install the serial comms ports (see the BTC Guild guide).
Cheers
|
|
|
|
|
Instead of getting another hub, you could simply get a power supply with the same plug (and polarity) but with a higher current capacity. I got some cheap 10 port USB2.0 hubs, replaced the original (2A) power supply with a 4A units (this should be capable of supporting 8 BE's per hub, but currently only have 6 on a hub). Note that if you run a USB powered fan(s), that uses power too that needs to be accommodated by the hub's power capacity. The hubs USB data connection are daisy-chained (one hub feeds into another, which then connects to a single port on the PC), this works fine with BFGMiner. The latest BFGMiner version (3.2.0) has a significantly lower HW error rate than earlier versions.
Cheers
|
|
|
|
|
Thanks for the super quick delivery!
Cheers
|
|
|
|
|
looks like your motherboard's USB ports did not cope with the power demand of your BE. Most people use the BE's on a powered USB hub, rather than plugging them directly into a PC USB port. You may be lucky if your MB has self-resetting fuses on the USB power (otherwise you may have killed those ports)....
You may find that your BE is alive and well when plugged into a powered USB hub with sufficient current capacity (about 500mA per BE).
Good luck
|
|
|
|
|
Show Posts
