[Fwd: Re: Trouble Associating with ath5k on AR5212]

[Will Keaney <keaneyw@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1479 bytes --]

Forwarding back to the list, as I was silly and sent as HTML originally...

-------- Original Message --------
Bob Copeland wrote:
> On Thu, Apr 02, 2009 at 09:20:05PM -0400, Will Keaney wrote:
>   
>> For what it's worth, I have also tried using iwconfig to associate to
>> the neighbor's network under ath5k without success.  So I don't think
>> it's related to wpa_supplicant's scanning algorithm.
>>     
>
> Well it's a long shot but I thought I'd mention it because I had
> very similar results due to long scans, where wpa_supplicant would
> time out and fail associations.  
>
> Try 'dmesg -n 7', then capture the output of dmesg while trying to
> associate, that should show the reason (CONFIG_PRINTK_TIME=y is helpful
> too). 
>   
dmesg shows this:
[38645.639170] ath5k 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> 
IRQ 17
[38645.639199] ath5k 0000:03:00.0: setting latency timer to 64
[38645.639342] ath5k 0000:03:00.0: registered as 'phy5'
[38645.872038] phy5: Selected rate control algorithm 'minstrel'
[38645.882037] Registered led device: ath5k-phy5::rx
[38645.882090] Registered led device: ath5k-phy5::tx
[38645.882097] ath5k phy5: Atheros AR5414 chip found (MAC: 0xa3, PHY: 0x61)
[38646.133614] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[38667.211026] ath5k phy5: noise floor calibration timeout (5785MHz)

I think the key there is the last line.  There is no further output in 
dmesg, regardless of what I do in wpa_supplicant.

Thanks,

Will Keaney

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 271 bytes --]