From: Pavel Roskin <proski@gnu.org>
To: Andy Pyles <andy.pyles@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: ath9k - D-link DWA-552
Date: Sat, 24 Jul 2010 02:28:12 -0400 [thread overview]
Message-ID: <1279952892.31905.3.camel@mj> (raw)
In-Reply-To: <AANLkTimnFGidxLvnR+=WXykQyf4NNAJBkxuqZ3HWRdeh@mail.gmail.com>
On Fri, 2010-07-23 at 22:30 -0400, Andy Pyles wrote:
> Hi Pavel,
>
> Incidentally this is the output after adding that id to pci.c:
>
> [ 1211.423855] Backport based on linux-next.git next-20100720
> [ 1211.437076] cfg80211: World regulatory domain updated:
> [ 1211.437080] (start_freq - end_freq @ bandwidth),
> (max_antenna_gain, max_eirp)
> [ 1211.437084] (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
> [ 1211.437087] (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
> [ 1211.437089] (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
> [ 1211.437092] (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
> [ 1211.437095] (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
> [ 1211.447705] ath9k 0000:05:02.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
> [ 1211.447794] ath9k 0000:05:02.0: Failed to initialize device
> [ 1211.447830] ath9k 0000:05:02.0: PCI INT A disabled
> [ 1211.447859] ath9k: probe of 0000:05:02.0 failed with error -95
You may want to post it to ath9k-devel@lists.ath9k.org
It looks like a hardware problem. Either the device is broken, or it's
an experimental chip that is not supported by ath9k. There have been
patches removing support for cards that have never been sold (or were
not supposed to be sold). Maybe your card ended up with an experimental
chip by mistake.
--
Regards,
Pavel Roskin
prev parent reply other threads:[~2010-07-24 6:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 18:58 ath9k - D-link DWA-552 Andy Pyles
2010-07-24 2:02 ` Pavel Roskin
2010-07-24 2:30 ` Andy Pyles
2010-07-24 6:28 ` Pavel Roskin [this message]
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=1279952892.31905.3.camel@mj \
--to=proski@gnu.org \
--cc=andy.pyles@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).