Difference between revisions of "Rt2x00 beta driver"

From ArchWiki
Jump to: navigation, search
(Installing the driver: link to pkgbuild in aur)
m (Installing the driver)
(19 intermediate revisions by 9 users not shown)
Line 1: Line 1:
[[Category:Communication and network (English)]]
+
[[Category:Wireless Networking]]
[[Category:HOWTOs (English)]]
+
This page describes how you can make the new '''rt2x00''' drivers work. This page '''does not''' describe the legacy '''rt2500''', '''rt2400''', '''rt2570''', '''rt61''' and '''rt73''' drivers derived from the original Ralink drivers. The '''rt2x00''' driver has a few advantages over the legacy drivers: It works with all the standard tools, it is in active development as part of the kernel, and it is SMP-safe.
This page describes how you can make the new '''rt2x00''' Beta drivers work. This page '''does not''' describe the legacy '''rt2500''', '''rt2400''' and '''rt2570''' drivers derived from the original Ralink drivers.
+
  
At the time of this writing, only the '''rt2560''' PCI and PcCard chipsets ('''rt2500pci''' driver) are known to work in Open, WEP or WPA (PSK and EAP) mode. So far, there are no success stories with '''rt2400pci''', '''rt2500usb''' and '''rt61pci''' drivers. If you succeed in using these drivers, please add a comment here.
+
A lot has changed since these drivers were out-of-tree, so it's worth trying the modules (now in the main kernel package) even if the drivers have not worked for you in the past.
  
// Currently the rt2500/2570usb adapter component is still in development. It should work and associate with an AP, then gain an IP from DHCP but the connection works intermittantly. NDiswrapper is recommended until fixed.
+
For help with these drivers see the [http://rt2x00.serialmonkey.com/phpBB/viewforum.php?f=5 rt2x00 Driver Support] section of the rt2x00 forums.
  
// 03/09/2007 - rt2x00-cvs version 20070826-1 works pretty well with my rt61 PCMCIA card. Successfully used with WPA2 through wpa_supplicant, and speed is fine for using 2 Mbit DSL. Networkmanager sometimes causes problems with it though, so perhaps it's best to use the Arch networking scripts for now.
+
== Installing the driver ==
  
The '''rt2x00''' drivers are supposed to work with SMP kernels, but I did not test this myself. Please add comments here if you were able to use the driver with an SMP kernel.
+
The rt2x00 drivers are now part of the mainline kernel. One need only load the relevant module:
 +
# modprobe rt2400pci
  
There are still many issues with this driver. Many people experienced crappy speed. To help solve these issues, everyone who is willing to test the new driver should look at the [http://rt2x00.serialmonkey.com/phpBB2/viewforum.php?f=5 rt2x00 BETA Testing] section of the rt2x00 forums.
+
# modprobe rt2500pci
  
 +
# modprobe rt2500usb
  
= Installing the driver =
+
# modprobe rt61pci
  
The '''rt2x00 Beta 3''' (as posted in the AUR) and older version are known to '''NOT WORK'''. In order to have a working driver, you '''MUST''' use the new rewrite based on the DeviceScape stack. This new driver is (at the time of this writing) only available as a [http://rt2x00.serialmonkey.com/rt2x00-cvs-daily.tar.gz CVS snapshot]. To install the driver, unpack the driver, change to the '''rt2x00-cvs-2006XXXXXX''' directory and type
+
# modprobe rt73usb
  
make
+
The last two require a firmware file, provided by the Linux firmwares package:
make install
+
pacman -S linux-firmware
 
+
There is a pkgbuild in AUR which builds the latest hourly snapshot from serialmonkey: http://aur.archlinux.org/packages.php?do_Details=1&ID=12714
+
 
+
If it is the '''rt61''' driver you need, you'll also have to manually install the '''firmware''' [http://www.ralinktech.com.tw/data/RT61_Firmware_V1.2.zip from RaLink]. To proceed, create a /lib/firmware directory -if you don't have one already- and place the *.bin files inside. (NB: this firmware is likely to be soon included into rt2x00.serialmonkey tree)
+
 
+
= Using the driver =
+
  
 
== Setting the interface up ==
 
== Setting the interface up ==
Line 41: Line 36:
 
== Using the driver ==
 
== Using the driver ==
  
In the case of these drivers, the order in which you configure them is important.
+
See [[Wireless Setup#Part II: Wireless management]]
 
+
ifconfig wlan0 up
+
iwlist wlan0 scan
+
iwconfig wlan0 essid myessid
+
iwconfig wlan0 ap mybssid
+
 
+
Is the preferred, and most likely to work order of configuring the device. From there you can use '''ifconfig''' or '''dhcpcd''' to get an IP, and wep or wpa if needed.
+
 
+
= Extra utils for wep/wpa =
+
 
+
== wpa_supplicant ==
+
 
+
rt2x00 should work fine with the wpa_supplicant '''wext''' driver. It is not necessary to patch it any more.
+
 
+
== Using wpa_supplicant ==
+
 
+
For example, to use wpa_supplicant, try
+
 
+
/usr/sbin/wpa_supplicant -wB -Dwext -iwlan0 -c/etc/wpa_supplicant.conf
+
 
+
Note that wpa_supplicant didn't work with hidden essid in my tests.
+
 
+
// TODO: someone please confirm that wpa_supplicant also successfully associates to open or wep-encrypted networks, I only tried WPA-PSK and read success reports about WPA-EAP
+
 
+
== Using WEP ==
+
 
+
WEP should work with the Wireless Extensions used by iwconfig.
+
 
+
// TODO: Some please confirm that this works
+
 
+
= Configuring the driver for automatic startup on booting =
+
 
+
== RT2400 (rt2400pci) ==
+
The following is known to work for the cvs snapshot available [http://rt2x00.serialmonkey.com/wiki/index.php?title=Downloads here] with the date 23-Dec-2006.
+
  
To set the driver up for automatically connecting while the computer is booting, type the following in /etc/rc.conf
+
=== wpa_supplicant ===
  
wlan0="wlan0 192.168.1.102 netmast 255.255.255.0 broadcast 192.168.1.255"
+
rt2x00 should work fine with the wpa_supplicant '''wext''' driver. It is not necessary to patch it any more. See [[WPA supplicant]]
INTERFACES=(lo !eth0 wlan0)
+
  
And the following in /etc/rc.local
+
=== Using WEP ===
  
iwconfig wlan0 channel 10
+
WEP works with the wireless extensions used by iwconfig. See [[Wireless Setup#Wireless Quickstart]].
iwconfig wlan0 essid linksys
+
iwconfig wlan0 ap 00:0c:41:a8:87:8e <-- Put your access point's bssid here
+

Revision as of 04:01, 6 March 2013

This page describes how you can make the new rt2x00 drivers work. This page does not describe the legacy rt2500, rt2400, rt2570, rt61 and rt73 drivers derived from the original Ralink drivers. The rt2x00 driver has a few advantages over the legacy drivers: It works with all the standard tools, it is in active development as part of the kernel, and it is SMP-safe.

A lot has changed since these drivers were out-of-tree, so it's worth trying the modules (now in the main kernel package) even if the drivers have not worked for you in the past.

For help with these drivers see the rt2x00 Driver Support section of the rt2x00 forums.

Installing the driver

The rt2x00 drivers are now part of the mainline kernel. One need only load the relevant module:

# modprobe rt2400pci
# modprobe rt2500pci
# modprobe rt2500usb
# modprobe rt61pci
# modprobe rt73usb

The last two require a firmware file, provided by the Linux firmwares package:

pacman -S linux-firmware

Setting the interface up

If you have module autoloading enabled, the drivers should be loaded automatically when you boot your machine or insert the device. If this doesn't work or autoloading is disabled, load the modules manually:

modprobe 80211
modprobe rc80211_simple
modprobe $driver

where $driver is one of the following: rt2500pci, rt2400pci, rt2500usb or rt61pci.

When the driver is loaded, you will have two interfaces, wmaster0 and wlan0.

Using the driver

See Wireless Setup#Part II: Wireless management

wpa_supplicant

rt2x00 should work fine with the wpa_supplicant wext driver. It is not necessary to patch it any more. See WPA supplicant

Using WEP

WEP works with the wireless extensions used by iwconfig. See Wireless Setup#Wireless Quickstart.