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!
On 10/28/2013 7:19 PM, Dan Williams wrote:
> On Mon, 2013-10-28 at 17:28 -0400, Richard Wang wrote:
>> 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."
> The proprietary ralink drivers do not appear to support the kernel's
> nl80211 API. In the first case (no such device) that's what is
> happening. IN the second case (nl80211 not found) the nl80211 module is
> either not compiled into the kernel, or is not loaded. And since the
> wifi driver doesn't use nl80211, that's probably why it's not loaded.
>
>> 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
> Correct, that proprietary driver does not use nl80211.
>
>> 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.
> Getting "iw" working would basically involve adding RT3573 support to
> rt2800usb, so you're really asking "how can we get RT3573 chips properly
> supported in Linux?". If that's done, "iw" comes for free.
>
> Dan
>
Hi Dan,
Thanks for the response and that's exactly my question stated much more
succinctly. Based on other threads, it appeared as if there might be
support for rt2800usb for rt3573 chips in experimental versions
(http://rt2x00.serialmonkey.com/pipermail/users_rt2x00.serialmonkey.com/2013-July/006283.html).
I tried to install the latest development version of backports hoping
that this patch would be part of it but it didn't seem to work. I'm
hoping to see if anyone happens to have a working patch for rt3573 chips.
RIchard
On Mon, 2013-10-28 at 17:28 -0400, Richard Wang wrote:
> 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."
The proprietary ralink drivers do not appear to support the kernel's
nl80211 API. In the first case (no such device) that's what is
happening. IN the second case (nl80211 not found) the nl80211 module is
either not compiled into the kernel, or is not loaded. And since the
wifi driver doesn't use nl80211, that's probably why it's not loaded.
> 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
Correct, that proprietary driver does not use nl80211.
> 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.
Getting "iw" working would basically involve adding RT3573 support to
rt2800usb, so you're really asking "how can we get RT3573 chips properly
supported in Linux?". If that's done, "iw" comes for free.
Dan
Richard Wang wrote:
> succinctly. Based on other threads, it appeared as if there might be
> support for rt2800usb for rt3573 chips in experimental versions
> (http://rt2x00.serialmonkey.com/pipermail/users_rt2x00.serialmonkey.com/2013-July/006283.html).
> I tried to install the latest development version of backports hoping
> that this patch would be part of it but it didn't seem to work. I'm
> hoping to see if anyone happens to have a working patch for rt3573 chips.
Support for RT3573 was added recently, you should use wireless-next:
http://git.kernel.org/cgit/linux/kernel/git/linville/wireless-next.git
or latest backports:
http://www.kernel.org/pub/linux/kernel/projects/backports/2013/10/25/backports-20131025.tar.bz2