http://data.bitcoinity.org/bitcoin/block_version/30d?c=block_version&r=week&t=a

While the percentage of blocks signalling segwit support is rising, that's only because the relative proportion of blocks by the pools signalling support is getting closer to what they represent as a proportion of the network - the same 6 entities have been signalling support as soon as they could. A significant proportion of pools have not (+/-yet) started signalled support. I wouldn't take the rise in percentage of blocks signalling segwit to be indicative of support increasing for it. I'd watch the pool count supporting segwit as a better marker of whether it will get up or not - and at this stage there isn't remotely enough pools supporting it, but it's way too early to make a call about what will happen (note my pool is currently testing support for it and plans to but it's less than 0.1% of the network.)

Yes that's correct. In the file ASIC-README it lists the avalon4 specific commands, they're the ones starting with --avalon4-*

And yet you're still mining tiny blocks... 

I use Debian for servers exclusively and a mixture of Ubuntu and Arch for desktops/laptops, though lately I've used Arch very little for convenience but I still like it.

That's what documentation was invented for:
https://github.com/ckolivas/cgminer/blob/master/README

Please don't ask about windows. You'd be nuts to consider mining with windows at this point, though I will be releasing windows binary when I finally release the next version but there's no hurry to do so and it's just out of legacy that I still do so.

By the way, for those of you working on getting sdcards working and other shit to get your A7s mining, you can actually run them off the master cgminer and a regular PC in the meantime. Grab the latest master cgminer, build it with avalon7 support, and plug the avalon7 into your pc/laptop and mine in the meantime until you can get your RPis working. Not only that but you'll get newer code than is on the RPi images with my improvements and bugfixes.

This is incorrect on multiple levels. Mining has almost nothing to do with it. Transactions are mined at an almost constant rate regardless of how many miners there are (provided miners choose to mine as many transactions as possible and generally they do), and secondly the overall mining hashrate has only kept increasing in the last year.

Test pool is only on the main pool. The de pool doesn't have enough resources to run two pools fast enough for me to be happy with their performance.

You can mine to either port, but mining to 13333 is mining the test code with segwit activation flagged, and while the code has now been bugtested and appears to be working fine, I give no guarantees with it (though I'm almost certain it should be fine now.) If the lack of guarantee concerns you, or you wish to not signal support for segwit, mine on the regular port 3333, though once the test pool finds a block successfully, I will not be giving an option against segwit.

Mining pools need to update their configuration and software to work in concert with segwit, otherwise they're unable to support it. Actual miners with hardware it makes no difference to them as all the work is done at the pool level, unless you're one of the rare few who wish to mine solo for yourself, in which case the onus falls on the miner to do what the pool would otherwise do for them.

5.3TH @ 815W at the wall with gold PSUs. Not much more efficient than the default which ends up being 6.3TH @ 1040W, however it's a lot quieter and probably makes it more suitable for home mining as a result. In short setting the voltage to 4669 gave me this, but your mileage may vary as all silicon has different capabilities and tolerances.

Enough replies of the same thing again. Locked thread to prevent more repeated posts from sigspammers.

Once the test pool has proven itself working properly by finding a block, the main pool will be updated to the code of the test pool and the test pool will be shut down. It will happen very quickly after notification on this forum and is an instantaneous process. Existing miners will be redirected seamlessly without needing to do anything with effectively no down time and anyone that tries to mine on port 13333 will be mining on the updated main pool.

Segwit benefits:
https://bitcoincore.org/en/2016/01/26/segwit-benefits/

Segwit costs and risks:
https://bitcoincore.org/en/2016/10/28/segwit-costs/

Firstly, even if every GPU on earth was added to the global bitcoin mining hashrate, it wouldn't add any significant hashrate to the existing network whatsoever. Second, irrespective of the hashrate, transactions are mined as blocks are found and blocks are found at an almost constant rate of 1 every 10 minutes on average by the network adapting to the existing hashrate. So it wouldn't make a snot of difference even if you doubled the network hashrate.

I've been committing driver improvements for the A7 to master cgminer anyway and they're likely to be included in firmware updates so you probably won't have to keep track of the suggestions pasted here. I've altered the frequency adjustment to speed it up, fixed a reject issue, and converted the fan controller to a PID-like feedback loop for optimal temperature and fanspeed control.

Welcome, all cold weather heater miners, and thanks to the 200TH of miners already on the test pool!

Alas every freaking time I've been offered mining gear is just before summer and electricity here has always been really expensive so I only get to mine in the worst possible conditions for a short period with the latest gear till diff takes its next hike upwards. I'm currently dumping my one A7 onto the test pool myself and am already undervolting it to keep it quieter, cooler and more efficient. Running it at the lower voltage also makes its noise much more tolerable for indoor mining if you're looking for a new heater.

Your gratuitous use of spoilers offends me... oh wait, wrong forum. Mine on.

No as the update is (supposed to) work on both networks regardless, and there are other updates to the pool as well which were pending. When the test pool finds a block, I'll be moving back to the one pool again with the updated code, and just get all miners back on the one main pool through a series of seamless redirects the way I usually do, and simply leave that port open on the new pool as well as the existing port.

At this stage if I were to make a call, it's my guess that there will be a significant proportion of the network, maybe 15% that will persist with something like BU or just core pre-segwit, while there is a large chunk of mining entities that are currently neutral. I expect the neutral entities will simply switch with time when it's convenient to avoid fucking up the way I did with the pool. The remainder is the real issue, but with one year for segwit to activate I still expect they'll eventually come around. They've signalled support for all sorts of other things in the past and eventually abandoned them. A lot of the concerns regarding segwit, I believe, are a combination of minor valid concerns, perceived major concerns, and plain FUD, and I don't believe the minor valid concerns outweigh the benefits segwit brings to bitcoin at large.

And I'd just like to take this opportunity to bring up fucking up with the pool again. Even though it's out of character for me, I'd like to remind people of the slush incident - his pool had block withholding from a mining entity that likely lost the pool somewhere in the order of 250-500BTC depending on real luck over the course of about 3 months and that money was never reimbursed to the miners even though he allegedly found the offenders. Not sure what he ever did with the offenders but he certainly didn't treat that incident the way I did out of my own personal reserves of cash.

Thanks guys. The test pool is at a rip roaring 1.8% diff so it'll find a block in no time.