From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Stuge Date: Mon, 11 Jan 2010 17:49:03 +0100 Subject: [ath9k-devel] No probe response from AP after 500ms, disconnecting. In-Reply-To: <4B4B4F8F.5050807@openwrt.org> References: <20091216174112.GD11461@tux> <20091216222157.28840.qmail@stuge.se> <20091216234308.GA425@tux> <20091218115708.14617.qmail@stuge.se> <20091218161854.GA6231@tux> <20091218200753.30718.qmail@stuge.se> <8e92b4100912182103n5e3402echbedb85ab62f28e57@mail.gmail.com> <20091220125745.8234.qmail@stuge.se> <20100111150339.21118.qmail@stuge.se> <4B4B4F8F.5050807@openwrt.org> Message-ID: <20100111164903.9039.qmail@stuge.se> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org Hi Felix, Felix Fietkau wrote: > > Since I never saw this behavior in exactly the same kernel with > > another mac80211 driver (ipw2200) the problem must be in the ath9k > > driver or in my "AR5416 MAC/BB Rev:2 AR5133 RF Rev:81" hardware. > > ipw2200 is not a mac80211 driver. Whoops! That was me not doing thorough research! Sorry about that. :\ > It probably handles reconnects internally inside the libipw stack, > whereas mac80211 does not do this and leaves it to user space > instead. I am not 100% sure, but I believe wpa_supplicant does not actually help me. I think I still need to down/up the interface to reconnect. I will test this further to make sure. > The difference in behaviour thus does not necessarily rule out a > problem in the RF environment. I've seen the problem in every RF environment I've visited with this card. Most are in cities small and large, but one is in an office on the outskirts of a small city, where the only wifi to be seen is the two closest of the six-or-so WAP54 access points that we have set up throughout the adjacent buildings. There's very little traffic in that network and I still see disconnects. In any case I would love to debug this from the bottom and up. Any pointers on registers and settings that may be useful too look into, in particular if some features of the hardware are not yet supported by the driver, would be most welcome. //Peter