From: Luis R. Rodriguez <lrodriguez@atheros.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] openwrt - ath9k does not load: probe of ath9k failed with error -22
Date: Mon, 9 Nov 2009 08:38:25 -0800 [thread overview]
Message-ID: <20091109163825.GA8719@tux> (raw)
In-Reply-To: <20091108122923.GA7743@asa.multi24.com>
On Sun, Nov 08, 2009 at 04:29:23AM -0800, Florian Reitmeir wrote:
> Hi,
>
> i do own 2 linksys wrt160nl, which use ath9k.
>
> i flashed both in the last weeks several times, and ath9k was loading
> nice. since yesterday, one of them can't load ath9k anymore. reflashing
> with the original firmware of linksys didn't help.
>
> here the kernel dmesg:
>
> ath9k ath9k: failed to initialize device
> ath9k: probe of ath9k failed with error -22
On what kernel? We've seen one case now where on a specific x86 platform
some new changes instroduced on 2.6.32 rounded up the PCI memory area
incorrectly and had an impact on devices like sky and ath9k. For more
information please see:
http://bugzilla.kernel.org/show_bug.cgi?id=14402
There is a fix for this now available and in Linus' tree.
But -- wrt160nl doesn't run x86 :) I take it, so... lets see.
> i use openwrt trunk, with compat wireless from 3.11.2009. is the device
> broken? if not how to tell, how do debug?
You want to enable debugging as I explained to the user on the bug
report above. In the bug report you can find the same exact situation
and how I explain to get more information to further debug this issue.
Please post your dmesg logs once you get debugging enabled, and enable
it completely and load.
Compat-wireless could use a fix for ./scripts/driver-select ath9k to
enable ath9k debugging, but I haven't gotten around to it yet so for
now please just compile all the drivers.
Luis
prev parent reply other threads:[~2009-11-09 16:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-08 12:29 [ath9k-devel] openwrt - ath9k does not load: probe of ath9k failed with error -22 Florian Reitmeir
2009-11-09 16:38 ` Luis R. Rodriguez [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=20091109163825.GA8719@tux \
--to=lrodriguez@atheros.com \
--cc=ath9k-devel@lists.ath9k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.