K, so perhaps you missed the announcement about the openssl bug affecting bitcoin.
https://bitcointalk.org/index.php?topic=919373.0

I can't use the ppa version, it's affected by the openssl issue and my p2pool won't function - verified with make check error. I need a statically linked version of the bitcoin core, not a dynamically linked version.

I really don't understand why a dev team would release something and not provide a simple README to describe where to put the files. Surely they must realize that non-developers and / or newbs like myself are going to be using the programs. So, instead of a 1 minute read through a README now we have a drawn-out and frustrating back & forth on forum which was preceded with a frustratingly pointless search on the net.

Thank you for your repsonse grue, your assistance is appreciated.

Hi, considering the openssl bug / vulnerability problem, my system is affected and bitcoin no longer works on my system.

I want to install the static binary version from the site, so i downloaded it but when i extracted it there's a bitcoin-0.9.3-linux then a bin and src folder in there. In the bin is a 32 and a 64 folder and in the src is a file named bitcon-0.9.3.tar.gz

so, what do i do with these files? where do they go?

I was hoping for a working version of the bug-affect bitcoin-qt but i'm lost with this download.

Any assistance from some of the experienced users?

Thank you.

Well, finally got an orphan share, after 36 hours ... so 1 orphan in 22 shares, I can live with that.

Already got a wardrobe full of 'em, but can't have too many, right. After all, once they know you're protecting yourself, they sneak into your house when you're out and bug the hats you have, have to keep getting new ones in order to stay one step ahead

No, I've been installing each new firmware as soon as they came out, assuming that each new one was simply the old one plus bug fixes or patches.
I find it interesting how all of my S3s changed hashing rates after reverting to the S320140826 firmware.
Surely it's not just my S3s that are affected, as that would be even more bizarre. [conspiracy theorists unite]

One interesting note to add:
Since installing the S320140826 firmware, now just over 48 hours, not any orphans or dead shares yet, where before I was getting an orphan every 6 - 12 hours.

Yep, same, messed up my miners totally.
I'm glad that the earlier version - https://bitmaintech.com/files/download/antMiner_S320140826.bin - was able to correct it.
Thanks for the verification.

Thanks JB, much appreciated, cheers.

Just saw this on the terminal:
Removed /home/[user]/p2pool/data/bitcoin/shares.43
I've never seen this message before.
Does anyone know what it means / indicates?
Is it something to worry about? - I love playing the conspiracy theory card  

Just something I noticed in the last couple of days.

I have been experimenting with the different firmware versions for the S3 Antminers and the versions after antMiner_S320140826.bin all produce buggy mining hashing totals after approximately 5 minutes of hashing.

Regardless of the frequency and voltage selected, using any of the firmware versions after antMiner_S320140826.bin causes all of my miners to drop to hashing rates from 50GH/s - 300GH/s.

As soon as I revert to antMiner_S320140826.bin the miners all jump back up to 440GH/s+ and remain stable at these rates.

It may be worth verifying on your own machines. If you have installed the newer firmware versions you may not be getting the hashing rates that you expect.

Hope this helps someone else.

Thanks for the reply.
I figured out that reinstalling the firmware might correct the issue, turned out to be true.
All better now, yay!! - whew!!

Perhaps one of the mods could help out with this one?

I didn't realize that there is no repository on the S3, I was going to remove and then reinstall the cgminer software, but once remove is clicked, then the software is gone.
I tried, from the gui to wget to ckolivas site, but it comes up with errors.
Wget functions from within the ssh, but the miner still doesn't work after I do so and the software isn't showing up in the gui software list.
Instructions from http://coinmyne.proboards.com/thread/257/latest-antminer-firmware-pool-info looked promising, but after following them, nothing changed.
From the ssh I copied all the cgminer files that I could find, from another S3, but no change - still not working, cgminer not showing in software list for installation option.
Any assistance would be greatly appreciated. I'm just about ready to copy each and every file, one by one, from one S3 to the non-functioning S3.

Heh, I was mining on BAN up until the middle of September.
I have 8 S3 Ants and when I pulled out of BAN I was down to around $12 / day and at the time the price for BTC was much higher than it is now.
After setting up a server, experimenting, testing and now running my own p2pool node for the last two months - with only the same 8 x S3 Ants - it's near the end of November and most days I'm making $25 - $30, some days nothing, some days $10, some days $40 and some days $50 or more - of course it depends on the frequency of finding blocks just the same as other pools.
P2pool kicks ass in comparison to the payouts from other pools, I'll never go back to mining in someone else's pool - whether BAN or any other.
Setting up one's own p2pool node is a great learning experience and provides a measure of control - even if it is only psychological.
It's unfortunate if others cannot / will not believe that it's a better payout, but that's their loss I guess - hopefully more will come over.

Thanks for the suggestion, I'll take a look. Though, my goal is to become proficient with the command line, like the matrix - think in code 

You're welcome, I enjoyed it. It gives me a topic for learning something new.

Sounds insulting, but not intended so, try a different ethernet cable. I get this sort of issue regularly with all the cat 5 / cat 6 ethernet cables I have ... I swap out a cable and it's all better. I even have brand new, never used, cables that don't work at all or work on one computer but not another - true story. Now, I only buy high-quality cat7 cables - no more junk.

Have you made sure that both the router and your network connection are set to the same thing? ... for example, both set for dhcp or both for static ip assignment. A router set up for static IPs and a computer connection set to dhcp won't get much traffic moving.

If no change, and just for fun, you could try this:
Delete existing connection (from within the Edit Connections applet) ... DON'T create a new one,
disable networking (option from network applet at top of ubuntu desktop),
count to 10,
enable networking (option from same applet),
select autoethernet to connect to (that's the auto generated name my ubuntu comes up with),
additionally:
sudo service network-manager stop && sudo rm /var/lib/NetworkManager/NetworkManager.state && sudo service network-manager start ... then reboot
Cheers.

Ok, just spent the day installing ubuntu server over and over to see what happens with this and that.

I tried a few options for correcting the problem:
1) Edit connections >>> delete whatever connection is listed, create / add new connection ... I tried that, but it had no effect at all, rebooted, still no effect.
2) In terminal >>> sudo service network-manager stop && sudo rm /var/lib/NetworkManager/NetworkManager.state && sudo service network-manager start >>> reboot ... no effect
3) Uninstall libglib2.0-0 >>> reinstall libglib2.0-0 >>> it broke my server >>> reinstalled
4) Uninstalling and then re-installing the network-manager - no effect.

I then recalled that during the setup and install of ubuntu server, it asks which ethernet port (I have two onboard gblans) is primary, I chose eth0, but, it appears I was plugged into eth1 with the ethernet cable >>> I changed the cable to the other port et voila!! - all better instantly, connection manager recognized that I was plugged in and showed all appropriate info in the Connection Information window.

So, no guarantee, but perhaps you have a similar situation with which port you're connecting the ethernet cable to when there's only one cable connected - worth checking out.

Cheers.

For connecting to a p2pool node, use your bitcoin public payout address as your username and use anything as your password, it's irrelevant ... most people have 123 as the password.
Cheers.

Find the IP address and port for the p2pool node that you want to connect to and put that address into your miner. You want to find a node that is near your location - for example 207.81.46.117:9332 if you're near western Canada - as that will help to provide a lower latency (delay) for the information that is sent between the p2pool node and your miner(s).

Here's a list of public p2pool nodes. (sort the list by country or other criteria by clicking on the values (country / latency / etc) at the top of the columns)
http://p2pool-nodes.info/

There are other lists available. There are p2pool node scanners available as well. To get started, unless you have your own p2pool node, use this list to find a node which is near you.

You can use the ping command in a terminal / command prompt, or from within some miners' diagnostic page, to check the latency between your location and another location (ip address) ... for example, in a Windows command prompt you could type (without the quotes) "ping 207.81.46.117" (leave the port :9332 off of the ping command). The lower the ping value, the faster / better the connection between your miner and the node. Experiment, have fun.

Here's a setup manual for the dragon:
https://www.dropbox.com/s/89n6g9155b11an5/Setting%20up%20your%20MintForge%201TH%20Bitcoin%20Miner%20v5.pdf

Here's a manual for an older version (no LCD):
https://www.dropbox.com/s/xrtn916zzgfksmu/Setting%20up%20your%20Coincraft%201TH%20Bitcoin%20Miner%20v4.pdf

Cheers.

I wonder if there's some sort of power management / sleep setting interfering with the connection(s). Perhaps a BIOS setting controlling a timer or something within Ubuntu that's putting the NIC to sleep.

Anyone else have a theory?