From: Luis R. Rodriguez <lrodriguez@atheros.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ar9271.fw not found
Date: Tue, 22 Jun 2010 10:25:12 -0700 [thread overview]
Message-ID: <20100622172512.GA12659@tux> (raw)
In-Reply-To: <53748.60.50.114.221.1277199950.squirrel@compu-zone.com>
On Tue, Jun 22, 2010 at 02:45:50AM -0700, peter at compu-zone.com wrote:
> Hi to all,
>
> I Previously brought a TP-Link wn422g-v2 atheros chipset
> Bus 001 Device 003: ID 0cf3:1006 Atheros Communications, Inc.
>
> I use the ndiswrapper but not working, i use the compat-wireless still not
> working
> this is the output that i get:-
>
> root at bt:~# dmesg | grep -e ath -e wlan
> md: multipath personality registered for level -4
> ath9k 0000:04:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
> ath9k 0000:04:00.0: setting latency timer to 64
> ath: EEPROM regdomain: 0x65
> ath: EEPROM indicates we should expect a direct regpair map
> ath: Country alpha2 being used: 00
> ath: Regpair used: 0x65
> phy0: Selected rate control algorithm 'ath9k_rate_control'
> Registered led device: ath9k-phy0::radio
> Registered led device: ath9k-phy0::assoc
> Registered led device: ath9k-phy0::tx
> Registered led device: ath9k-phy0::rx
> usb 1-1.2: ath9k_htc: Firmware - ar9271.fw not found <<<<<<<<<<<<<<<<<<<<
> ath9k_hif_usb: probe of 1-1.2:1.0 failed with error -22
> <<<<<<<<<<<<<<<<<<<<<<<
git clone git://git.kernel.org/pub/scm/linux/kernel/git/dwmw2/linux-firmware.git
sudo cp linux-firmware/ar9271.fw /lib/firmware/
Luis
next prev parent reply other threads:[~2010-06-22 17:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 9:45 [ath9k-devel] ar9271.fw not found peter at compu-zone.com
2010-06-22 17:25 ` Luis R. Rodriguez [this message]
2010-06-24 7:22 ` DaFy
-- strict thread matches above, loose matches on Subject: below --
2010-06-25 10:34 peter at compu-zone.com
2010-06-25 10:38 ` Peter Stuge
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=20100622172512.GA12659@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.