On Tue, 2013-07-09 at 14:22 +0100, José Miguel Gonçalves wrote: > On 09-07-2013 13:42, Arik Nemtsov wrote: > > On Tue, Jul 9, 2013 at 2:27 PM, José Miguel Gonçalves > > <jose.goncalves@xxxxxxx> wrote: > > > >> Any more ideas on how to debug this? Is there any specific debug_level mask > >> that can apply to the driver to help it? > > You can try the mask 0x63c20 (it's pretty verbose, so I would put it > > in pastebin). > > > > Perhaps this is a genuine problem with the antenna of the card? > > Nope. The AP is 1 meter away form my board (even without antenna in the > card it should associate). Too strong a signal can also cause problems, because of distortion. > > Can > > you verify the RSSI of the AP is ok using iw? > > The iw output: > > http://pastebin.com/XmEzqjHs This looks okay, but the RSSI value cannot be trusted blindly. There are other factors that can influence the signal quality, such as the SNR. > The dmesg output with debug mask set to 0x63c20: > > http://pastebin.com/zGE0Gfp8 > > Note that with debug activated I did not see the driver's "Beacon loss > detected" messages. There could be some timing issue here. Is it always like that? Do you *always* see the "Beacon loss" messages without debugging and *never* with debugging? -- Luca. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
