I solved it. I have an ASUS P5E3 premium with onboard (usb) wireless n but it should work for anybody else having trouble using the same chipset. If you have a problem where it keeps asking for the WPA key over and over again even after solving the driver conflict you need to build your own rt2870sta module.
Resolving the Driver conflict
First check if there is a driver conflict by doing this
if you see all of these:
Code:
rt2x00usb
rt2x00lib
rt2800usb
rt2870sta
in the output, you have a conflict and you need to blacklist some modules
do
Code:
gksudo gedit /etc/modprobe.d/blacklist.conf
and add this:
Code:
# Wifi Drivers conflict with rt2870sta
blacklist rt2x00usb
blacklist rt2x00lib
blacklist rt2800usb
to the bottom of the file that opens, then save and close gedit.
Build your own (newer) rt2870sta
Make sure you have build-essentials
either with an alternative internet connection with:
Code:
sudo apt-get install build-essential
OR from the UBUNTU cd
Code:
apt-cdrom add-d / cdrom
apt-get update.
apt-get install build-essential.
download the latest rt2870USB(RT2870/RT2770) file from their website
http://www.ralinktech.com/support.php?s=2
extract the files somewhere
in a terminal go to the directory which you just extracted
e.g.
Code:
cd /home/user/Downloads/RT2870_LinuxSTA_V2.3.0.0
do
and make sure these are set
Code:
RT28xx_MODE = STA
TARGET = LINUX
if so, close gedit making sure to save if you had to change them.
check config.mk
Code:
gedit ./os/linux/config.mk
make sure these are set correctly
Code:
HAS_WPA_SUPPLICANT = y
HAS_NATIVE_WPA_SUPPLICANT_SUPPORT = y
if so, back at the terminal do:
Code:
sudo ifconfig wlan0 down
where you replace "wlan0" with the name of your wireless interface
unload the module
Code:
sudo modprobe -rf rt2870sta
do:
Code:
make
sudo make install
now overwrite the rt2870sta module
Code:
sudo cp ./os/linux/rt2870sta.ko /lib/modules/ <your kernel> (e.g. 2.6.32-21-generic)/kernel/drivers/staging/rt2870/rt2870sta.ko
restart the computer and your wireless n should now work.
Hope this helps
PS:Can somebody advise me on a better way of loading the alternative module at startup instead of replacing the default kernel one? since a kernel update will overwrite it with the default again.
Bookmarks