From: Richard Wang <rpw@andrew.cmu.edu>
To: linux-wireless@vger.kernel.org
Subject: Linksys AE3000 iw tool issues
Date: Mon, 28 Oct 2013 17:28:35 -0400 [thread overview]
Message-ID: <526ED703.6020901@andrew.cmu.edu> (raw)
Hi,
I currently have a Linksys AE3000 Wifi USB dongle, which has the
RalinkRT3573 chipset.
I am able currently able to connect to surrounding APs by installing
Ralink proprietary drivers as outlined here
(http://geekniggle.blogspot.com/2012/07/cisco-linksys-ae3000-wifi-usb-dongle.html).
Ifconfig and iwconfig both recognize the device using the interface ra0.
Unfortunately, the "iw" tool is having some issues. One machine running
Lucid Ubuntu 10.04 with the following command "iw dev ra0 info" returns
"command failed: No such device (-19)". Another machine machine with
xubuntu on command "iw list" returns "nl80211 not found."
From what I have read so far, it appears that the current driver may
not support iw operations. As a result, I looked into installing
rt2800usb driver that a few other threads appear to have working
successfully. As stated on wikidevi
(http://wikidevi.com/wiki/Linksys_AE3000), one of the more recent
patches appears to support the RT3573 chipset. I tried to install the
latest developmental release. After rebooting and loading the rt2800usb
driver, "modprobe rt2800usb", I get dmesg errors like "rt2x00lib:
disagrees about version of... ieee80211....".
Any suggestions to get the "iw" tool working would be much appreciated.
Thanks!
next reply other threads:[~2013-10-28 21:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-28 21:28 Richard Wang [this message]
2013-10-28 23:19 ` Linksys AE3000 iw tool issues Dan Williams
2013-10-28 23:48 ` Richard Wang
-- strict thread matches above, loose matches on Subject: below --
2013-10-29 9:35 Xose Vazquez Perez
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=526ED703.6020901@andrew.cmu.edu \
--to=rpw@andrew.cmu.edu \
--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).