Search content
Sort by

Showing 7 of 7 results by Jorsher
Post
Topic
Board Pools
Re: mining.BitcoinAffiliatenetwork.com - we're giving away 1 Antminer S3 every day!
by
Jorsher
on 01/09/2014, 19:59:41 UTC
I'm not knowledgeable enough on the whole process to point fingers or suggest problems with either pool...

But what I can say is that I've split my miners between two pools for months without issue, and my balances on the two pools stays more or less the same -- as it should from what I understand.  The time MP was going through this pool, my balance there fell behind enough that I was curious what happened.
Post
Topic
Board Mining support
Re: BITMAIN Antminer S3 support and OverClocking thread
by
Jorsher
on 06/08/2014, 08:48:33 UTC
the think is the AC is cooling air from the room (recycling it ) and not taking it from outside, which is why you are getting that vacuum effect, you are better off just not exhausting your miners to outside if they put out less heat than your temperature outside the barn.

ding ding ding!

AC doesn't/shouldn't draw air from outside the room it's trying to cool.  Just think about it.  Bringing in hot air from outside and trying to cool it is far less efficient than just trying to cool the air that's already inside, along with the fact that it would be creating positive pressure which would force cooled air outside.  Instead, it recycles the air inside.

By having your miners blowing air outside of the room, it's creating negative pressure inside the building.  Less air crossing the heatsinks, less air to absorb heat, they'll hang out and get toasty.

At least, that's how I understand it...
Post
Topic
Board Mining support
Re: BITMAIN Antminer S3 support and OverClocking thread
by
Jorsher
on 04/08/2014, 04:02:07 UTC
My B1s seem to get the best hashrate at 218mhz...  Sigh.

One did alright at 250mhz for a while getting 500GHS but it was highly erratic with lots of rejects and hw errors.

Oh well.
Post
Topic
Board Mining support
Re: BITMAIN Antminer S3 support and OverClocking thread
by
Jorsher
on 03/08/2014, 07:51:09 UTC
Is an "x" for one of the ASICs always something to worry about?

I have both S3s at 250mhz.  Both initially had an "x," however one cleared up on its own (?) and the other still has one.  Strangely, the one with the "x" has a higher hashrate so far.
Post
Topic
Board Mining support
Re: BITMAIN Antminer S3 support and OverClocking thread
by
Jorsher
on 01/08/2014, 18:56:04 UTC
My two B1 arrived in the middle east today. Had to go to USA then be reshipped...

Anyway.  One of them had the old firmware and was set to 350mhz from the factory in the cleanly formatted asic-freq.  Obviously didn't run worth a crap and every chip x'ed out. WTF?  The other had the new firmware and was set at 218.75mhz in a sloppy as hell asic-freq.

I updated the other to the latest firmware, added the 218.75 settings, and it ran fine.

At them both to 250mhz.  Both have one chip x'ed.  One has averaged 482ghs and the other 379ghs.  Going to try 237mhz and see how they go, and order some thermal paste which won't arrive for two weeks to clean their mess...

350mhz from the factory? WTF bitmaintech?
Post
Topic
Board Mining support
Re: Can someone explain these stats?
by
Jorsher
on 07/07/2014, 03:32:19 UTC
Hey all,

Thanks for the responses and sorry for the late reply.

In the last day, one got 99 HW errors and the other 133.  Close enough I'm not going to worry too much.  They are both overclocked.  One was reporting a fault with one of the chips for almost a week straight but now shows clear.

Difficulty is different between the two because it's set by the pool.

48-50C for both.

I'm using multipool right now.
Post
Topic
Board Mining support
Topic OP
Can someone explain these stats?
by
Jorsher
on 01/07/2014, 06:52:25 UTC
I don't really understand the stats, and when I search around I find multiple explanations so I'm not sure what's true...

http://i.imgur.com/nqOLkgo.png

These are Antminer S1s.  Initially, one of them was showing an "x" for the status of one of the chips, all the time, and soon after every reboot.  That seems to have fixed itself...

What I'm concerned about is the number of discarded shares.  When I've seen other people post their discarded shares, it's nowhere near as high of a ratio as mine.

Another question: if they're both on the same pool, why does one use a 2048 Diff while the other uses 512?

Last, why does one get so many more discarded and so many more HW errors?

Anything to worry about or is there anything I can do to improve it?  Calculating the HW error percentage, one is 0.01% while the other is 0.23%.