You are not logged in.
I recently purchase a Belkin N750 DB wireless usb adapter and had a HELL of a time trying to get it to work.
lsusb showed
050d:1103 Belkin Components F9L1103 N750 DB 802.11abgn 2x3:3 [Ralink RT3573]
So after hours of research and trying different ideas and failing each time, I found a solution that WORKS GREAT! Thanks to an ubuntu forum, someone mentioned that the device id was missing from a .c file; so even though the adapter was recognized, the driver was installed AND modprobe'd... it still wouldnt work.
If you purchased this adapter and are having difficulty, here is my gift to you: the instructions on how I fixed it in 6 easy steps.
Step 1: Download the current driver from http://www.ralinktech.com/en/04_support … hp?sn=5034 and extract to home directory (or a directory of choice that you will remember and have easy access to).
Step 2: Open the directory you extracted everything to and open the 'common' directory.
Step3: Edit the 'rtusb_dev_id.c ' and scroll to the section containing:
#ifdef RT3573
{USB_DEVICE(0x148F,0x3573)}, /* Ralink 3573 */
{USB_DEVICE(0x7392,0x7733)}, /* Edimax */
{USB_DEVICE(0x0846,0x9012)}, /* Netgear WNDA4100 N900*/
#endif /* RT3573 */
Step 4: Add a line for your device id (found with lsusb), it should look as follows (notice the added line for the Belkin device):
#ifdef RT3573
{USB_DEVICE(0x148F,0x3573)}, /* Ralink 3573 */
{USB_DEVICE(0x7392,0x7733)}, /* Edimax */
{USB_DEVICE(0x0846,0x9012)}, /* Netgear WNDA4100 N900*/
{USB_DEVICE(0x050D,0x1103)}, /* Belkin F9L1103 */
#endif /* RT3573 */
Then save the file (of course).
*Step 5: If you plan on using NetworkManager or wpa_supplicant wext functions, ensure the following is set properly in the os/linux/config.mk file.
HAS_WPA_SUPPLICANT=y
and
HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y'
Then again, save the file.
Step 6: In a terminal, cd back to the directory you extracted the driver's .zip file to and run
sudo su
make clean
make
make install
modprobe rt3573sta
Now enjoy your new (should be) WORKING wireless adapter!
Of course, if you want it to start automatically at boot, add rt3573sta to the modules loaded at boot (either using the modprobe.conf or modules-load.d methods).
If you run into any issues, then feel free to ask for help!! (But I would make sure to read the README_STA_usb file first (as it contains important info)
Offline
Hi villian999,
Thanks for the info. I think this can be updated in Wiki ( I dont know exactly, just see, whether you can update the info.) Then it would prove useful to many I guess
With regards,
Ajay Kumar G
With regards,
Ajay Kumar G
Nanos Gigantum Humeris Insidentis
Offline
Hey all,
I followed villian999's instructions and everything seemed to be going fine. wpa_supplicant even booted up to the menu. However, when it tried to connect to my wireless terminal said that it couldn't initialize nl80211 driver and it couldn't locate rfkill. Many forums said to ignore this error so I did, I pinged from the terminal fine but everytime I use wireless with a browser, everything (the whole computer, not just the browser) freezes and crashes. I've tried with multiple browsers and still the same result.
any ideas?
let me know if you need any more info or terminal output
Last edited by derekArch (2013-02-02 18:56:04)
Offline
I have followed these instructions but I get a kernel panic whenever I open up firefox and navigate anywhere or use pacman to update. This happens on arch x86_64 only for me.
I have since changed to i686 arch system and have no problems.
Has anyone else experienced problems with their rt3573 under x86_64?
Offline
OK, if anyone wants to use this driver under x86_64, here is a where you can get a patched version that doesn't kernel panic:
https://github.com/ashaffer/rt3573sta
Here's a link to the Zip file for the driver:
https://github.com/ashaffer/rt3573sta/a … master.zip
EDIT - I forgot to mention that Step 5 is already done in this source code.
Last edited by Zenther (2013-04-16 04:13:01)
Offline
I have followed these instructions but I get a kernel panic whenever I open up firefox and navigate anywhere or use pacman to update. This happens on arch x86_64 only for me.
I have since changed to i686 arch system and have no problems.
Has anyone else experienced problems with their rt3573 under x86_64?
I am also running x86_64 Arch and getting kernel panics, though I am using the Cisco Linksys AE3000 usb adapter.
I tried your solution from Github, but unfortunately it does not fix the issue for me. It seems that the source of the issue is the same, though: skbuff.
What did you do to fix yours? (I looked at the git diffs, but I'm no kernel dev, so I have no idea what's going on!) Maybe just a high level reasoning or links to appropriate documentation could help me to solve this issue (for me and many others!)
Offline
I didn't have to do anything other than extract the zip file...
cd rt3573sta-master
sudo make clean
sudo make
sudo make install
sudo modprobe rt3573sta
I don't know what to say for you. I fought this for a long time giving up and just using 32bit Arch. I ran across this on a monthly google search and gave it another try and it worked for me. That was a couple two or three kernel updates ago and they all compiled and worked without panicing for me.
Offline
Villain999 and Zenther: Holy mother of god, thankyou
Links in #5 worked perfectly for me (with steps in #7), on kernel 3.7.0 x64. So far the connection is working well.. I was about to embark on ndiswrapper, after mucking about with the ralink driver all night.
Offline
Hello, I just bought the Asus USB-N66 which has the exact same chipset as the belkin n750. The driver from ralink is RT3573STA, I have modified it according to the recommendations i've found in this thread and on the internet.
Since I have a x86_54 system, i followed the link provided on post #5 and downloaded the said driver. I modified the lines under common/rtusb_dev_id.c so that my usb device appears under that list found thanks to
$ lsusb
Bus 001 Device 002: ID 1532:010d Razer USA, Ltd
Bus 003 Device 002: ID 2109:0811
Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 005 Device 002: ID 0bc2:3312 Seagate RSS LLC
Bus 006 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 003: ID 1532:0024 Razer USA, Ltd Razer Mamba
Bus 003 Device 004: ID 059b:0577 Iomega Corp.
Bus 003 Device 005: ID 0b05:17ad ASUSTek Computer, Inc.
So that it reads as follows:
#ifdef RT3573
{USB_DEVICE(0x148F,0x3573)}, /* Ralink 3573 */
{USB_DEVICE(0x7392,0x7733)}, /* Edimax */
{USB_DEVICE(0x0846,0x9012)}, /* Netgear WNDA4100 N900*/
{USB_DEVICE(0x050D,0x1103)}, /* Belkin F9L1103 */
{USB_DEVICE(0x0B05,0x17AD)}, /* Asus USB-N66 */
{USB_DEVICE(0x0b05,0x1784)}, /* Asus USB-N13 */
#endif /* RT3573 */
After compiling and installing, I am able to add the module with
$ modprobe -v rt3573sta
insmod /lib/modules/3.9.6-1-ARCH/kernel/drivers/net/wireless/rt3573sta.ko
However even if the module seems loaded
$ lsmod | grep rt3573
rt3573sta 691169 1
usbcore 177091 6 usb_storage,ehci_hcd,ehci_pci,rt3573sta,usbhid,xhci_hcd
And the interface seems to be up
$ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
3: wlp7s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT qlen 1000
link/ether 00:18:e7:db:23:85 brd ff:ff:ff:ff:ff:ff
6: ra0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT qlen 1000
link/ether 30:85:a9:37:19:5f brd ff:ff:ff:ff:ff:ff
$iwconfig
[root@arch-fenix rt3573sta-master]# iwconfig
ra0 Ralink STA
wlp7s0 IEEE 802.11bgn ESSID:"netgear"
Mode:Managed Frequency:2.452 GHz Access Point: C0:C1:C0:4E:9C:6D
Bit Rate=104 Mb/s Tx-Power=18 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=33/70 Signal level=-77 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:11 Invalid misc:14 Missed beacon:0
lo no wireless extensions.
Nothing seems to work to connect to a network.
iwlist ra0 scanning gives no results, wicd fails, wifi-menu fails as well. They do not seem to be able to find a single network. I do not know what the problem is.... Need some help...
Offline
I have this same chipset in an ASUS USB-N66 wireless adapter. I am interested to know if there is any way to use these instructions on a fresh install of Arch? I have modified the appropriate file, but cannot seem to run "make" during the install. Does anyone have any insight into this?
Offline
So I downloaded the .zip file and went in to compile, and I've run into this lovely error:
make[1]: Entering directory `/usr/lib/modules/3.10.7-1-ARCH/build'
make[1]: *** No rule to make target `modules'. Stop.
make[1]: Leaving directory `/usr/lib/modules/3.10.7-1-ARCH/build'
Tried compile on both of my machines, what is up here?
Offline
So I downloaded the .zip file and went in to compile, and I've run into this lovely error:
make[1]: Entering directory `/usr/lib/modules/3.10.7-1-ARCH/build' make[1]: *** No rule to make target `modules'. Stop. make[1]: Leaving directory `/usr/lib/modules/3.10.7-1-ARCH/build'
Tried compile on both of my machines, what is up here?
Bump for info, I'm stuck at this point... Please someone help!
Last edited by Takeshi_Kovacs (2013-09-14 21:29:53)
“Solitude is impractical and yet society is fatal.” (Emerson, R. W.)
Offline