Rt2x00 README
From Rt2x00Wiki
Installation and configuration instructions for the rt2x00 Modules
This information is now obsolete
- Kernel
- Most (if not all) major distributions have now the rt2x00 in-kernel driver available by default in their build.
- This availability means essentially that all the previous efforts to maintain a driver off kernel are no longer needed.
Bug reporting:
When reporting a bug or problem with the rt2x00 module, make sure you report the following information:
- How to reproduce
- RT2x00 debug output, usually found in /var/log/messages.
- Module version.
- Wireless card chipset, model and manufacturer.
- Kernel version (i.e. 2.6.13)
- Hardware architecture (i.e. x86, AMD64, Sparc)
- Anything else you may think will help us resolve the issue.
Bug reports:
http://rt2x00.serialmonkey.com/wiki/index.php/Rt2x00Wiki:Bug_reports
Contact us:
- Website
- http://rt2x00.serialmonkey.com/
- wireless information http://linuxwireless.org
- Forums:
- Mailing list:
rt2x00 FAQ:
This guide was put together to help people who are testing the rt2x00 suite of drives during the development phase. Please note that at this moment in time, the drivers are still in development and does not conform to the normal Linux wireless configuration process (you have to do special steps to get them going) nor are the drivers particularly stable. DO NOT USE THESE DRIVERS IN A PRODUCTION ENVIRONMENT (refer to the stable branch for the rt2500 and rt2400 drivers)
I cannot see any debug information
Have you compiled the drivers with “make debug” and have you modprobed the driver (rt{4|5}00{pci|usb} with debug=1? e.g. “modprobe rt2500pci debug=1”
The steps in the readme doesn't work
Have you following the steps verbatim (obviously substituting your network vars such as AP bessid and channel for your values)? This is a requirement at the moment since some of the functions in the card need to be initialised using the steps described in the README. Note that the driver does not comform to the normal wireless configuration process in that you will not be associated with an access point unless you follow the steps in the README.
(check http://rt2x00.serialmonkey.com/wiki/index.php/Rt2x00Wiki:Bug_reports#Bug_No:_003)
I have a wep encrypted network
If you need to add WEP encryption add the following step after setting the essid (where AABBCCDDEE is your 48 bit encryption key in HEX) $iwconfig wlan0 key AABBCCDDEE
How do I know things worked?
You should see something like the following in dmesg: [4439180.426000] wlan0: associate with AP 00:50:18:36:b8:36 [4439180.428000] wlan0: RX ReassocResp from 00:50:18:36:b8:36 (capab=0x431 status=0 aid=2) [4439180.428000] wlan0: associated
dmesg shows an authentication message time out
If you get something like below, makes sure that you have following the README verbatim and specifically that you set the channel and iwlist wlan0 scan. These steps are required to initialize the card properly.
[4438543.721000] wlan0: Initial auth_alg=0 [4438543.721000] wlan0: authenticate with AP 00:50:18:36:b8:36 [4438543.921000] wlan0: authenticate with AP 00:50:18:36:b8:36 [4438544.121000] wlan0: authenticate with AP 00:50:18:36:b8:36 [4438544.321000] wlan0: authentication with AP 00:50:18:36:b8:36 timed out
I have done everything but still cannot associate with the ap?
Try lowering your channel on your access point as this might be a regional problem.
(check http://rt2x00.serialmonkey.com/wiki/index.php/Rt2x00Wiki:Bug_reports#Bug_No:_004)
I loose association
Sometimes you see this in dmesg [4439570.806000] wlan0: RX deauthentication from 00:50:18:36:b8:36 (reason=6) [4439570.806000] wlan0: deauthenticated
I don't know what reason 6 means yet.
I cannot associate and get timed out messages in dmesg
[4321475.171000] wlan0: Initial auth_alg=0 [4321475.171000] wlan0: authenticate with AP 00:50:18:36:b8:36 [4321475.371000] wlan0: authenticate with AP 00:50:18:36:b8:36 [4321475.571000] wlan0: authenticate with AP 00:50:18:36:b8:36 [4321475.771000] wlan0: authentication with AP 00:50:18:36:b8:36 timed out
You are either out of range of the AP or you have the same problem as me at the moment (will update this guide as soon as I figure out what it is)
I have a debian based system. What about moving the modules?
The issue here is that once you compile your new modules, they are installed in the root of your module tree (normally /lib/modules/2.6.xx-xx/rt2x00/). However, your old modules are still around in the tree and you have one of two options:
- Move the old modules out of the tree and leave your newly compiled modules where they are.
- Copy your new modules over your old ones.
BEWARE if you delete or overwrite the old modules and your new driver doesn't work the way you thought it would, then you will have to reinstall the kernel package (or boot up on an old kernel with the modules still intact) to get your old modules back. If you require a network connection in order to do this, then you might have a problem, so best strategy is to copy these items away.
make in the folder root fails
Makefile:52: /lib/modules/2.6.15-23-686/build/.config: No such file or directory
make: *** No rule to make target `/lib/modules/2.6.15-23-686/build/.config'. Stop.
The message is not always exactly the same since it is dependent on your kernel version. You need to install the development headers that will supply the file in question (/lib/modules/2.6.xxxxxx/build/.config).
If you have a debian based system, install the linux-headers-2.6.xxxxx package that conforms to your installed kernel
To find out your kernel version
$ uname -r
to install the headers
$ sudo apt-get install linux-headers-`uname -r`
Statistics don't work
Statistics have not received a high priority yet and many tools don't work correctly. We are looking for debugging information to help us identify the problem. See the debug howto on how to produce this information.
There is also currently a bug in the dscape stack and the wireless interface is not reported correctly in proc with the result that many tools does not detect the interface correctly.
This has consequences for report generation and configuration by many existing tools.
(check http://rt2x00.serialmonkey.com/wiki/index.php/Rt2x00Wiki:Bug_reports#Bug_No:001)