Comment 107 for bug 414560

That was explained in one of the previous discussions. The ath9k is an a/b/g/n interface and has a lot more channels to scan, and it's the extra time required to scan these additional channels that causes the association to time out. Or that's the theory anyway; the ath9k driver seems to still have plenty of problems of its own without NM adding to them.