AyeTea

** This thread discusses the content article: Updating the RT8260 802.11N Wireless Network Driver from Source **

Compiling stuff on your own system has advantages too - you can distribute code to platforms you don't even know, and the person wanting to run your code on this platform just needs to compile it with an appropriate compiler and presto a working version specific to his platform. Without any need to worry about compatibility issues and stuff.

Also, for compatibility reasons, the "stock" binary is optimized for the i586 (Pentium I) architecture, or sometimes even the i386 architecture. By compiling and having it optimize for the i686 (Pentium Pro or later) architecture, as well as enabling things like SSE and 3DNow, you get a binary which might not work on someone else's computer, but it will run a lot faster.

That's the theory, anyway. In practice, the performance boost is relatively minor, and it's only worth the trouble when the code has to be very, very fast (i.e. games and the kernel itself.)

I just wanted to thank you for the post! I've been struggling with this issue and patiently waiting for a resolution since I first purchased my Asus Eee PC 1000 several months ago.

I converted to Eeebuntu NBR 2.0 and WICD and have never had a problem using WPA2-PSK on my home net. However I've never been able to get a 802.11n connection either. I really felt, based on everything I'd read, that the issue was driver related and that I just needed to wait for a good solution to surface. It did.

After backing everything up I followed the instructions on your link this morning and I had a fast and rock solid 802.11n connection with WPA2-PSK.

It looks as though Ralink has, with v2.1.2.0, corrected the 802.11n issue and if the proper WPA_SUPPLICANT mods are made to the config.mk file then both the issues are resolved.

Cheers! And many thanks!