|
Beastlymac,
Thanks for the quick response. I solved the H error rate by going to the original modified bfgminer 3.2.0. The hash rate is still 2.26 GH/sec. I posted this in the support thread.
|
|
|
|
|
After trying to run the Blue Fury miner with bfgminer3.4.0 with -S bigpic:all, it was detected and hashed, but had a very high H error rate (about 61%) after about 40 minutes. The hash rate was about 2.26 GH/Sec.
Trying the original modified bfgminer 3.2.0 resolves the H error rate, but the hash rate is still about 2.26 GH/sec.
Is there any way to change the configuration or firmware to get closer to the specifiec 2.6 GH/sec?
|
|
|
|
Julz, thanks for the direct delivery. I managed to get it going, but the results are strange. Not sure if it is a faulty device or something else. Running the latest BFGMiner (3.4.0). The rest of the installation is per Beastlymac in https://bitcointalk.org/index.php?topic=299295.0. To avoid interactions with other things it is running entirely alone, on a separate Win7 64 PC as a single device on a powered hub. I am getting a very high H error rate (about 61% after about 40 minutes) and the hash rate is about 2.26GH/sec (on Slush's pool). I tried resetting the device, the miner software etc, but there is no improvement. I wonder if it is a faulty device or a configuration problem. More exploration: Using the older bfgminer 3.2.0 with the original batch file seems to solve the high H rate. The hash rate remains however close to 2.26 GH/sec. Cheers |
|
|
|
|
Just got my BF and it's running on Win7 with BFGminer 3.4.0, but the results are strange. The hash rate is about 2.26GH/S and the HW error rate is HUGE ~ 61% after more than 40 minutes. Tried resetting BFG, reinserting the device but there is no change. Is it faulty?
More exploration: using the older bfgminer 3.2.0 with the original batch file seems to solve the high H rate. The hash rate remains however close to 2.26 GH/sec.
|
|
|
|
I have a tracking number... hoping it's for the entire batch.
Hi Julz Any news on these? |
|
|
|
I still got no reward for the block 20598 with 38472 shares! I'm qqqq85 on the pool.
You can raise it with Live Support (see link on left side of the Slush web site), 'they' probably will not look here. I had this one confirmed at 'normal' reward rate. Did you mine steadily through the whole block? |
|
|
|
I apparently tried to run too many block erupters off of one hub; the hub got very hot and seems to have burned something out inside (apparently the part of the hub that supplies the power to the individual ports), and now 3 of the 4 block erupters no longer seem to be working, even when I try to use them with another hub (when I plug in the block erupter the computer doesn't even seem to recognize that anything has been plugged into it). I don't think there is any damage to the computer or its USB ports itself though, because it still recognizes and uses USB flash drives and external hard drives without a problem.
I was hoping that maybe it was just some sort of a software/registry etc. issue, but I restored my entire OS partition from an Acronis True Image image I made a week ago when the block erupters were still working fine, and the computer still does not recognize these 3 block erupters. So the problem seems to be the block erupters.
Two of the block erupters I don't see any signs of life at all in; the third sometimes when I try plugging it in, the little tiny square LED light will come on and stay on continuously, but the computer still doesn't recognize the block erupter.
Is there any kind of repair service that may be able to fix these 3 block erupters? If so, what is the cost and how do I get in touch with them?
If not, does anyone have any suggestions for environmentally friendly uses for dead block erupters? So far I have thought of 'paperweight', but I'm sure there are more uses I haven't considered.
Thanks!
Check that the USB ports on your PC are working - for example by plugging a USB Flash drive and checking that it is recognized. Had a case of USB port damage (seems only the 5V rail) due to a powered hub 'injecting' too much into the PC. Check the suspected BE's with another hub or by plugging them 1 at a time into the PC USB port. There was a guide somewhere on the forum on clearing the USB port settings (but you probably took care of that by restoring the partition) |
|
|
|
It seems I got shortchanged again in the last block:
20608 2013-10-26 02:16:27 1:27:23 291941058 97919 0.00061354
Anybody else? I hope it gets corrected but I doubt it; I've had a couple that never did so.
Block 20608 fixed itself, Slush must have a script running a couple of hours after a block was found that recounts the shares. if you want to calculate your correct payout use the following: 25 divided by the total round shares then multiply with your number of submitted shares (25/total shares) * your shares Unfortunately the reward calculation is not that simple, as Slush uses a system described in https://bitcointalk.org/index.php?topic=1976.msg50002#msg50002score = score + exp(round_time/C), to avoid 'pool hopping', essentially this means that if you left the pool some short time before a block was solved, your reward will be much lower than the simple proportion of your submitted shares... correct, but it comes pretty darn close, specially for shorter rounds ( if mined steady for at least 1 million shares ) You are correct for steady hash rates...  |
|
|
|
It seems I got shortchanged again in the last block:
20608 2013-10-26 02:16:27 1:27:23 291941058 97919 0.00061354
Anybody else? I hope it gets corrected but I doubt it; I've had a couple that never did so.
Block 20608 fixed itself, Slush must have a script running a couple of hours after a block was found that recounts the shares. if you want to calculate your correct payout use the following: 25 divided by the total round shares then multiply with your number of submitted shares (25/total shares) * your shares Unfortunately the reward calculation is not that simple, as Slush uses a system described in https://bitcointalk.org/index.php?topic=1976.msg50002#msg50002score = score + exp(round_time/C), to avoid 'pool hopping', essentially this means that if you left the pool some short time before a block was solved, your reward will be much lower than the simple proportion of your submitted shares... |
|
|
|
|
mining.bitcoin.cz responds with
503 Service Unavailable
No server is available to handle this request.
now back 'on the air'....
|
|
|
|
Not sure what happen? Miners were not down.
# Block found at Duration Total shares Your shares Your BTC reward Block # Block value Validity
20474 2013-10-19 19:49:11 0:58:18 183619562 14319 0.00278337 264716 25.05891520 98 confirmations left
20473 2013-10-19 18:50:53 4:18:43 806905065 47775 0.00000000 264706 25.02120000 88 confirmations left
20472 2013-10-19 14:32:10 0:33:05 101910920 9975 0.00273336 264672 25.12480605 54 confirmations left
20471 2013-10-19 13:59:05 1:34:50 290381577 31050 0.00262393 264664 25.03999643 46 confirmations left
20470 2013-10-19 12:24:15 0:36:09 109556297 12050 0.00281957 264650 25.06568921 32 confirmations left
Comparing your fraction of shares to Total shares to mine, there is clearly a lower value for this block, perhaps your rig or internet connection had some issue towards the end of the block Block # Share ratio Aurel57/Kabopar 20474 1.649844452 20473 1.22581721120472 1.936893204 20471 2.221506761 20470 2.186536019 |
|
|
|
All my Block Eruptor stopped working 15 miutes ago for no obvious reasons ... using BFGMiner. Network on my RPi seems ok. Anyone else has issues with the pool ?
my rig is working ok, but I noticed a large drop in the pool's hash rate (from about 220TH to 198TH/s) now at 176TH, looks like another DDOS attack or some server fault at our pool?! |
|
|
|
All my Block Eruptor stopped working 15 miutes ago for no obvious reasons ... using BFGMiner. Network on my RPi seems ok. Anyone else has issues with the pool ?
my rig is working ok, but I noticed a large drop in the pool's hash rate (from about 220TH to 198TH/s) |
|
|
|
Is anyone else experiencing that reward payout is not happening? Had my confirmed reward above the threshold for at least 2 hours and no payout... Wake up slush server, put some more coals into that engine....
Yeah me too Now 3 hours over due....  And now 4 hours... Slush, PLEASE!!!! |
|
|
|
Is anyone else experiencing that reward payout is not happening? Had my confirmed reward above the threshold for at least 2 hours and no payout... Wake up slush server, put some more coals into that engine....
Yeah me too Now 3 hours over due.... |
|
|
|
|
Is anyone else experiencing that reward payout is not happening? Had my confirmed reward above the threshold for at least 2 hours and no payout... Wake up slush server, put some more coals into that engine....
|
|
|
|
|
visdude@
I don't think it would get fixed once it is confirmed, would it?
the confirmation is an external issue, while the reward is internal to the pool. I think that in the past there were similar cases that got fixed eventually
|
|
|
|
|
visdude@
I had this one ok
20352 2013-10-11 17:14:40 0:46:18 85167670 5746 0.00157400 262973 25.39866404 confirmed
It may 'fix itself' later.
On another matter - my reward payout finally happened, just about 3 hours late...
|
|
|
|
my bitcoin address is fine.... it's Slush holding on to those rewards.... used to pay like clockwork 1 minute past the whole hour when the confirmed reward was above the threshold, but recently it's quite random... i'm sure that it will eventually get sorted, just frustrating....  |
|
|
|
|
And just crossed another round hour, still above the threshold and no payout.... wake up Slush.... send some coins.... please....
|
|
|
|
|
Show Posts
