From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adrian Chadd Date: Sun, 24 Mar 2013 22:38:43 -0700 Subject: [ath9k-devel] ath9k not connecting to one particular network.. In-Reply-To: References: Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org On 24 March 2013 21:06, Linus Torvalds wrote: > Ok, I'm sure this is something people have seen before, but it has me stumped. > wlan0: authenticate with 50:46:5d:02:85:08 > wlan0: send auth to 50:46:5d:02:85:08 (try 1/3) > wlan0: authenticated > wlan0: associate with 50:46:5d:02:85:08 (try 1/3) > wlan0: RX AssocResp from 50:46:5d:02:85:08 (capab=0x411 status=0 aid=10) > wlan0: associated [snip] > I'm not seeing what the difference is. Except for that "aid=1" vs > "aid=10", which I have no idea what it means. AID is the "Association ID", which is a field used by the AP to identify which particular offset inside various things (eg the TIM bitmap, which identifies which stations have traffic in each beacon frame, so stations can stay asleep until they see a beacon with their bit set in said TIM) to pay attention to. Now, the bulk of the driver/chip doesn't care about the AID. It only affects things in power save. So perhaps you can try disabling power save on your chromebook (there's an iw command to do this; please check the archives to see what it is.) If disabling station-side power save works, maybe the AID isn't being programmed or restored correctly when the hardware is being reset (which occurs during scans, for example.) Thanks, Adrian