From: Sujith Manoharan <sujith@msujith.org>
To: Nick Thomas <nhomas@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [ath9k] Recent driver versions break compatibility with AR9285 for me
Date: Wed, 6 Mar 2013 11:33:29 +0530 [thread overview]
Message-ID: <20790.56369.998911.884240@gargle.gargle.HOWL> (raw)
In-Reply-To: <CAEk6VBHnWn_KF0TJ_vojuOhWFhR6TncAok+B9mqgGzAdC5DzVg@mail.gmail.com>
Nick Thomas wrote:
> When I run the 3.7.10 kernel with the ath9k module loaded, the
> wireless does not work, and iwconfig wlan0 reports:
>
> wlan0: no wireless extensions.
>
> When I run the 3.2.39 kernel, the wireless works, and iwconfig wlan0 reports:
>
> wlan0 IEEE 802.11bgn ESSID:"HardFatCox"
> Mode:Managed Frequency:2.437 GHz Access Point: 00:22:75:49:42:F7
> Bit Rate=48 Mb/s Tx-Power=15 dBm
> Retry long limit:7 RTS thr:off Fragment thr:off
> Encryption key:off
> Power Management:on
> Link Quality=50/70 Signal level=-60 dBm
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:23 Invalid misc:11577 Missed beacon:0
>
> My best guess is that recent driver revisions broke compatibility with
> my wireless card.
The card is recognized properly by ath9k, since it is shown in the interface
list and it's even associated with HardFatCox :)
What doesn't work ?
Sujith
next prev parent reply other threads:[~2013-03-06 6:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 5:42 [ath9k] Recent driver versions break compatibility with AR9285 for me Nick Thomas
2013-03-06 6:03 ` Sujith Manoharan [this message]
2013-03-06 7:00 ` Nick Thomas
2013-03-06 7:30 ` Sujith Manoharan
2013-03-06 14:03 ` Kalle Valo
2013-03-06 20:32 ` Nick Thomas
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=20790.56369.998911.884240@gargle.gargle.HOWL \
--to=sujith@msujith.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nhomas@gmail.com \
/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