Main Page | Recent changes | Edit this page | Page history

Printable version | Disclaimers | Privacy policy

Not logged in
Log in | Help

Rt2x00 alpha

From Rt2x00Wiki

rt2x00_alpha status page

This page's purpose is to provide details on the status of the rt2x00_alpha module. The alpha module is the first stage in the complete rewrite of the driver code. Alpha will not form a complete driver but instead will be used to test out much of the hardware IO and basic principles.

Current status of alpha

Alpha basically works but there are still a few little bugs in there that we really could do with finding. It is possible to use the module in RFMON mode with kismet/ethereal etc and it is possible to collect scan results with "iwlist scanning".

Alpha compiles OK on IA32 systems with newish 2.4 and 2.6 Kernels. Tests on other systems would be welcome.

How to build

To compile simply type "make debug" to build the debug version of the module.

To load the module use

insmod ./rt2x00.ko enable_debug=1

insmod ./rt2x00_pci.ko

the interface is called eth0

Most serious BUGS

reports of a problem on SMP systems and cannot bring the interface up

Other bugs

On SuSE 9.3 the following message appear when unloading the module after monitor mode: dev_mc_discard: multicast leakage! dmi_users=1 I don't know if this is just a serious warning or not. (RobinC: This is caused by setting the multicast flags on the net device. Its not IMHO serious but we need to clean up in the shutdown functions somewehre to undo any multicast settings to prevent this warning.)

I can't test repeater mode as i don't have enough kit. With what i have got repeater mode effectively did a DOS on the wireless network.

The RX, TX, ATIM and PRIO register are incorrectly written to. The base address of each ring is written according the the host byte order,
instead it should be converted to a little endian value.

I am not seeing any beacon packets from ad-hoc mdoe etc being transmitted.

When calling iwconfig commit the connection will automaticly go up without having to do ifconfig up.
The problem lies in the commit call itself because it will always call rt2x00_radio_off() followed by rt2x00_radio_on() to trigger the config update to occur.

Create beacon is currently NOT passing the extension data (after the 802.11 header, through a cpu_to_device function. The header is going through a conversion.

Tidy ups

Pretty much cleaned up now, can results are good and in correct place. Channel scan timer needs setting to a sensible vale. Can still get into problems where it won't rescan.

Any help with the above bugs would be great!


--Robinc 10:15, 11 May 2005 (PDT)

Retrieved from ""

This page has been accessed 22,150 times. This page was last modified 21:27, 30 May 2005 by Robin Cornelius. Based on work by Ivo van Doorn and Mark Wallis. Content is available under GNU Free Documentation License 1.2.

[Main Page]
Main Page
Community portal
Current events
Recent changes
Random page

Edit this page
Discuss this page
Page history
What links here
Related changes

Special pages
Bug reports