He needs to set up the environment before trying to compile bfgminer.


I'd suggest you read the README file and sequentially and carefully follow the instructions section of setting up the developement environment before you try to compile.
I have not done it on rPi, but used BFGMiner instructions for setting up MinGW on windows and it works a treat. All the errors that you are encountering indicate that your environment is not set up correctly, and posting each error as you encounter it may simply bamboozle whoever is trying to help.
I know for sure you'll encounter compilation errors that need Luke-Jr to address, but if you keep crying wolf when there is none, then when that wolf does turn up you may not get the help you require!

Updated OP with 2 days screenshot running freq 262.5 @ 0.75v

From my calculations (excluding power consumption of other bits, e.g fans and dc/dc converters), I have:

For freq 250 32 chips @ 0.75v 12.24A = 293.76 Watts
So, by your linear model: 262.5 / 250 = 1.05 (factored to the amperage) =>12.852
For freq 262.5 32chips @ 0.75v 12.852A = 308.448 Watts

Making a grand difference of 14.68 Watts. Tell me if I am splitting hairs here ... I mean to say, even 20 watts is not exactly pushing the envelope!


My thoughts exactly .... though I blew up my 550W rated PSU running my rig @ 0.85v !

I am guessing you are in the Americas, if that, what is the shipping to UK and how much do you want for each?

Hindsight is always a wonderful thing ... and with that in mind, it looks like the first port of call for dropping hash-rates would be the freq settings, but yeah, I don't blame you for sticking with your reset firmware seeing the only officially documented change is the reset button functionality.

Anyone still running the new November firmware, would you please find out what version of cgminer ships with it?

So it seems like you need to manually set the voltage and frequency setting(s) after flashing the new firmware ..... that would perfectly explain the dropping hash-rates then ...

Yep, and going by the bits they seem to have broken, now that they fixed the reset button, I think it is time to test that feature for those who took the plunge.

The well established paradigm of "if it ain't broken, do not fix it" then ....Actually, I think bitmain were fixing something with the reset thingybob, now look.

I'd have liked to try that but the datasheet does not provide a voltage setting for that frequency, it literally only provides the four in the first table of the opening post! Also, the largest PSU I have available to run the S3 rigs is a measly 670W.

If you insist on splitting hairs, then it'd be best to be exact on how much more (specific) wattage draw there is between freqs 250 and 262.5 at the suggested 0.75V

I have just updated the 262.5 overclock over a full day web UI to compare equally with the August 2014 overclock (last image in OP). The HW error rate remains at 0.0004 over the day, a total of ONLY 46 HW errors! Now, there is something to shout home about.

Your guess is as good as mine .... best to drop them a line but I'd defer on the description (encompassing the prior updates). Also, you can try posting on the cgminer thread, I know ckolivas and kano do release binaries compiled for antminer rigs independent of bitmain.

I've just updated the thread with a 24hr comparison of my previous OC @ 262.5 and the HW rate has drastically reduced.
I can pretty much guarrantee that this will work for all BM1382 boards, it just depends on whether you want to do it. First, run it at a frequency within the bitmain spec (the black numbers in the last table) with the voltage set. The rate will take a while to settle and will at the very least match the spec rate (expected hash in the last table), but more likely beat it (as I have demonstrated). More important though, is the lower HW rate (and again, do not jump at conclusions after the first half hour, let it run for a few hours).
If you feel the HW rate is low enough (even not and just feel like it!), turn up the freq within that voltage range (this is mine through my tests not bitmain's) and you should be OK.

For the 262.5 freq test, the voltage setting is 0750, which is the datasheet voltage for freq 250. Start with 250 and I bet you'll get very few HW errors and a good hash speed, then if you feel like it, turn up the freq and watch your hash-speed increase, with still few HW errors.

That is not an immature rant, it is just a rant. Grow up and snap out of your self importance!

I can not see how that answers the question, so I'll add to it thus: If you have nothing to say, do not say it!

No need to have a dig at me ... believe me. But that you did, and your suggestion of the dc/dc regulators, I suppose those should work well at lower freqs then .... and not cause the rig to drop off in speed .... or is that just an answer to provide room for name calling (or to make you look clever when you clearly are not)?

You've got both. Open them up and see the difference (the chips have numbers on them!) rather than waste every-body else's time with your circular question!

If you know what you are asking for, why ask in the first place?

1. How were we supposed to know all that extra detail when you first asked the question? Last I checked, there are no mind readers on this forum (let alone thread!).
2. Do not feel obliged to ask your question clearly on the back of my thinking you are dissing my "work". Ask your question clearly if you want an answer to your question, else, you'll get what whoever reads it thinks you are asking.
3. Since it seems you believe you have exhausted all avenues, here's one; Swap boards with one of your "working" S3's
I'm done here.

What is stopping you from classifying it as an S3+ then? Can it not run at higher freqs without a load of HW errors? I have just pointed you to a good solution to efficiently running (even overclocking) with the voltage, but you dissed that with contempt. I only made that post yesterday, but have been toying with it for over a week, so I know what I am talking about there (wouldn't have posted if I was not sure).

The ONLY documented reason, in these hallowed pages no less, has been lack of adequate heat dissipation which leads to HW errors when you try to OC. Combine the two, i.e proper voltage setting at the running freq + good heat dissipation and you have, no doubt, an S3+ !

But hey, you asked the question and got an answer, it is (again!) the proverbial taking a horse to the water hole but cannot force the damn thing to drink!

Heat dissipation. Re-apply the heat paste (possibly use a better type), swap the paste with heatpads on the chips / front heatsink, tighten both heatsinks properly and update to latest firmware. Voilla, you have an S3+ !

EDIT: by the way, you can also use the voltage setting in the new firmware to help with efficiency / overclocking, see my sig!