Made a slight mistake mines the LW153 and apparently should run on RT3070.sta
I added the device to rtusb_dev_id.c
and now got
ra0 Ralink STA
Am i on-track? how come it's not wlan0?
I tried to set ESSID and got
iwconfig ra0 essid wireless
Error for wireless request "Set ESSID" (8B1A) :
iwlist ra0 scan
ra0 Interface doesn't support scanning : Network is down
lsmod | grep rt3070sta
rt3070sta 631728 0
usbcore 128828 5 rt3070sta,ohci_hcd,ehci_hcd,usb_storage
two entries for rt3070sta?
Did you follow the complete instructions? There is a text file in the driver source that explains how to set it to use NetworkManager. Also, reread my first post. It explains about copying and renaming the rt2870sta.dat file.
Yes I did the copying of the files here's my start to finish
cp RT2870STACard.dat RT3070STACard.dat
cp RT2870STA.dat RT3070STA.dat
# Added device
Bus 001 Device 003: ID 177f:0153 Sweex
even though I put Sweex LW153 in rtusb_dev_id.c is this right?
But did you follow the instructions in the README_STA_usb file, that came with the driver?
1> $tar -xvzf DPB_RT2870_Linux_STA_x.x.x.x.tgz
go to "./DPB_RT2870_Linux_STA_x.x.x.x" directory.
2> In Makefile
set the "MODE = STA" in Makefile and chose the TARGET to Linux by set "TARGET = LINUX"
define the linux kernel source include file path LINUX_SRC
modify to meet your need.
3> In os/linux/config.mk
define the GCC and LD of the target machine
define the compiler flags CFLAGS
modify to meet your need.
** Build for being controlled by NetworkManager or wpa_supplicant wext functions
Please set 'HAS_WPA_SUPPLICANT=y' and 'HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y'.
I have just experimented with the latest versions of the RT3070sta and RT2870sta driver and I can definitely confirm the following findings:
- Adding MODULE_LICENSE("GPL"); to /<driver name>/is/linux/usb_main_dev.c is no longer needed. Ralink has already added the information there. This applies to both the RT2870 and RT3070sta drivers
- For the RT2870sta driver, 'HAS_WPA_SUPPLICANT=y' and 'HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y' must be set in os/linux/config.mk. The default has those settings to 'N' for both.
- Installation of RT2870sta is STILL REQUIRED to get RT3070sta working due to the driver making calls to rt2870sta.dat.
I have tried this out on both a Fedora 10 and OpenSUSE 11.1 machine and my Aztech WL-552 wireless-N USB adaptor worked perfectly.
And it is good to see that Ralink had fixed the Module License bug.
Thanks for the info.
You shouldn't have to install the rt2870 driver. the RT2870STA.dat file is included in driver version 22.214.171.124. If I recall, you needed to rename that file to RT3070STA.dat, but I may be wrong.
Unfortunately, it did not work on mine.
Originally Posted by waterhead
I followed your instructions to 'cp RT2870STA.dat RT3070STA.dat' but when i ran
dmeg still complains about not being able to find rt2870sta.dat and the interface refuses to be brought up. But the moment i installed Rt2870STA, every proceeded without a hitch.
Then try not renaming the file. Maybe that bug has been fixed too.
I followed every instruction found in this thread... but after initialization of rt3070sta with modprobe, I got the following error found in dmesg:
iwconfig doesn't offer a new device to me.. any suggestions? :)
[ 641.949920] usbcore: deregistering interface driver rt2870
[ 641.952270] <--- rtusb exit
[ 646.990661] rtusb init rt2870 --->
[ 646.990753] rt2870 1-1.2.1:1.0: usb_probe_interface
[ 646.990783] rt2870 1-1.2.1:1.0: usb_probe_interface - got id
[ 646.991546] === pAd = b47bf000, size = 521344 ===
[ 646.992340] <-- ERROR in Alloc Bulk buffer for HTTxContext!
[ 646.992340] ---> RTMPFreeTxRxRingMemory
[ 646.992370] <--- RTMPFreeTxRxRingMemory
[ 646.992370] ERROR!!! Failed to allocate memory - TxRxRing
[ 646.992584] <-- RTMPAllocAdapterBlock, Status=3
[ 646.992614] rt2870: probe of 1-1.2.1:1.0 failed with error -1
[ 646.994842] usbcore: registered new interface driver rt2870
The errors are about the rt2870 driver. This thread is about the rt3070 driver.
I haven't been following this much anymore, as this is an old thread. I don't believe that you need to do all of those things anymore.
If you want help, you need to provide more info, such as distro version, kernel version, driver version, wireless chip, etc. See the wireless sticky in this section for the type of info you should be providing.