Difference between revisions of "Rt2x00 beta driver"

From ArchWiki
Jump to: navigation, search
m (Moved to category "wireless networking")
m (Bot: Removing from Category:HOWTOs (English))
Line 1: Line 1:
{{i18n|Rt2x00 beta driver}}
{{i18n|Rt2x00 beta driver}}
[[Category:HOWTOs (English)]]
[[Category:Wireless Networking (English)]]
[[Category:Wireless Networking (English)]]

Revision as of 18:14, 10 June 2011

This template has only maintenance purposes. For linking to local translations please use interlanguage links, see Help:i18n#Interlanguage links.

Local languages: Català – Dansk – English – Español – Esperanto – Hrvatski – Indonesia – Italiano – Lietuviškai – Magyar – Nederlands – Norsk Bokmål – Polski – Português – Slovenský – Česky – Ελληνικά – Български – Русский – Српски – Українська – עברית – العربية – ไทย – 日本語 – 正體中文 – 简体中文 – 한국어

External languages (all articles in these languages should be moved to the external wiki): Deutsch – Français – Română – Suomi – Svenska – Tiếng Việt – Türkçe – فارسی

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

Using the driver

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

In the case of these drivers, the order in which you configure them is important. This is the preferred, and most likely to work order of configuring the device.

ifconfig wlan0 up
iwlist wlan0 scan
iwconfig wlan0 essid myessid
iwconfig wlan0 ap mybssid 

To obtain an ip address after setup use ifconfig or dhcpcd and wep or wpa if needed.

dhcpcd wlan0

Extra utils for wep/wpa


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 works with the wireless extensions used by iwconfig. See Wireless Setup#Wireless Quickstart.

Configuring the driver for automatic startup on booting

RT2400 (rt2400pci)

The following is known to work for the cvs snapshot available 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

wlan0="wlan0 netmask broadcast"
INTERFACES=(lo !eth0 wlan0)

And the following in /etc/rc.local

iwconfig wlan0 channel 10
iwconfig wlan0 essid linksys
iwconfig wlan0 ap 00:0c:41:a8:87:8e <-- Put your access point's bssid here