From: Bob Copeland <me@bobcopeland.com>
To: Will Keaney <keaneyw@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Trouble Associating with ath5k on AR5212
Date: Fri, 3 Apr 2009 08:23:32 -0400 [thread overview]
Message-ID: <20090403122332.GA14853@hash.localnet> (raw)
In-Reply-To: <49D571BB.7060406@gmail.com>
On Thu, Apr 02, 2009 at 10:17:31PM -0400, Will Keaney wrote:
> 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.
Probably a red herring, actually -- but yeah, you should be seeing more
output as the association process continues. That is a pretty frequent
and harmless error message, here you are scanning and just changed to
a 5.7 ghz channel for a passive scan.
Are you getting any results at all from scans? Is ath5k using 100% of
any cpu?
--
Bob Copeland %% www.bobcopeland.com
next prev parent reply other threads:[~2009-04-03 12:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 14:12 Trouble Associating with ath5k on AR5212 Will Keaney
2009-04-02 15:05 ` Bob Copeland
[not found] ` <49D56445.20502@gmail.com>
2009-04-03 2:03 ` Bob Copeland
[not found] ` <49D571BB.7060406@gmail.com>
2009-04-03 12:23 ` Bob Copeland [this message]
2009-04-03 13:39 ` Will Keaney
2009-04-07 2:02 ` Will Keaney
2009-04-08 12:10 ` Bob Copeland
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090403122332.GA14853@hash.localnet \
--to=me@bobcopeland.com \
--cc=keaneyw@gmail.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).