Topic: BFL 5GHS and 50GHS + Bitminter <-- seems to need to be babied? (Read 813 times)
Yeah, try OSX - less likely to have malware installed than Windows
What are you mining on these "beasts" if I may ask?
Just bitcoin.
Also, looks like we stabilized by connecting the boxes to windows or OSX boxes. The linux box we were using may end up being the culprit.
So we ordered a baby jalapeno (5GHs) a while back and have been using Bitminter on a linux box. Hashing rates are fine and all that but every so often, the rate will go to 0 and it just stops working.
In these cases, stopping and restarting the hashing often doesnt work so you have to either physically unplug and replug the USB cord back in and restart the jobs or restart the client completely.
it hasn't been that bad so we've just kept at it and 'babied' it along.
Well we ordered a 50GHS (calling this one junior) and plugged it in with the baby and they both were going pretty good at their respective hash rates.
Now we've seen the junior box doing the same as the baby jalapeno sometimes where it just goes to 0....meanwhile baby is still hashing away just fine.
A new issue that's slightly different has started happening with junior that doesnt happen with baby too though...instead of stopping and going to 0H/s, the meter freezes at 50GHs or 51 or whatever it's at and it no longer moves and it no longer accepts jobs.
I'm just wondering if anyone else has had similar issues with the 5 and/or 50 GHashers with Bitminter and what kinds of things have you tried to get around that?
Meanwhile we plugged the baby into a windows box and it's been going fine. I'm trying an OSX box for the junior today to see how it goes.
In these cases, stopping and restarting the hashing often doesnt work so you have to either physically unplug and replug the USB cord back in and restart the jobs or restart the client completely.
it hasn't been that bad so we've just kept at it and 'babied' it along.
Well we ordered a 50GHS (calling this one junior) and plugged it in with the baby and they both were going pretty good at their respective hash rates.
Now we've seen the junior box doing the same as the baby jalapeno sometimes where it just goes to 0....meanwhile baby is still hashing away just fine.
A new issue that's slightly different has started happening with junior that doesnt happen with baby too though...instead of stopping and going to 0H/s, the meter freezes at 50GHs or 51 or whatever it's at and it no longer moves and it no longer accepts jobs.
I'm just wondering if anyone else has had similar issues with the 5 and/or 50 GHashers with Bitminter and what kinds of things have you tried to get around that?
Meanwhile we plugged the baby into a windows box and it's been going fine. I'm trying an OSX box for the junior today to see how it goes.
What are you mining on these "beasts" if I may ask?
So we ordered a baby jalapeno (5GHs) a while back and have been using Bitminter on a linux box. Hashing rates are fine and all that but every so often, the rate will go to 0 and it just stops working.
In these cases, stopping and restarting the hashing often doesnt work so you have to either physically unplug and replug the USB cord back in and restart the jobs or restart the client completely.
it hasn't been that bad so we've just kept at it and 'babied' it along.
Well we ordered a 50GHS (calling this one junior) and plugged it in with the baby and they both were going pretty good at their respective hash rates.
Now we've seen the junior box doing the same as the baby jalapeno sometimes where it just goes to 0....meanwhile baby is still hashing away just fine.
A new issue that's slightly different has started happening with junior that doesnt happen with baby too though...instead of stopping and going to 0H/s, the meter freezes at 50GHs or 51 or whatever it's at and it no longer moves and it no longer accepts jobs.
I'm just wondering if anyone else has had similar issues with the 5 and/or 50 GHashers with Bitminter and what kinds of things have you tried to get around that?
Meanwhile we plugged the baby into a windows box and it's been going fine. I'm trying an OSX box for the junior today to see how it goes.
In these cases, stopping and restarting the hashing often doesnt work so you have to either physically unplug and replug the USB cord back in and restart the jobs or restart the client completely.
it hasn't been that bad so we've just kept at it and 'babied' it along.
Well we ordered a 50GHS (calling this one junior) and plugged it in with the baby and they both were going pretty good at their respective hash rates.
Now we've seen the junior box doing the same as the baby jalapeno sometimes where it just goes to 0....meanwhile baby is still hashing away just fine.
A new issue that's slightly different has started happening with junior that doesnt happen with baby too though...instead of stopping and going to 0H/s, the meter freezes at 50GHs or 51 or whatever it's at and it no longer moves and it no longer accepts jobs.
I'm just wondering if anyone else has had similar issues with the 5 and/or 50 GHashers with Bitminter and what kinds of things have you tried to get around that?
Meanwhile we plugged the baby into a windows box and it's been going fine. I'm trying an OSX box for the junior today to see how it goes.
Jump to: