Bringing Linux to the Masses
I have a Dell sitting in my living room with a Linksys WMP54G PCI wireless adapter installed. The adapter worked just fine under Feisty (well TBH I never got the triangular bars icon of wireless connections but the two terminals of wired connections, but do I care??). Anyways I did upgraded to Gutsy on the 17th, just 1 day shy of its official release, by invoking a ‘gksu ‘update-manager -c’, and to my horror the adapter stopped working!! No Internet connection for me!
I am not sure if this card is not supported under Gutsy, or just something went awry during the upgrade process (will try a Gutsy live CD later), but i tried using the “Windows Wireless Driver” function but to no avail.
Anyways, this is how I managed to get my WMP54G to work under Gutsy:
1-First of all grab the driver from here (XP not Vista)
2-Extract the .exe file using any archive manager and place on your desktop (or where ever you wish)
3-Go to the ndiswrapper homepage, and download the latest release (1.48 to date).
4-Next we will have to install ndiswrapper, so fire up a terminal and navigate to the folder where you downloaded ndiswrapper.
tar zxvf ndiswrapper-version.tar.gz
sudo make uninstall
sudo make
sudo make install
5- If everything went as planned, you should have ndiswrapper installed now, next we will need to install the driver. Assuming that the downloaded driver from step 1 is on your desktop:
ndiswrapper -i ~/Desktop/WMP54Gversion/Drivers/WMP54G/Rt2500.INF
6-Finally you will have to load the ndiswrapper module.
sudo modprobe ndiswrapper
6-In my case this didn’t really work, which probably explains why using the “Windows Wireless Driver” function didn’t work in the first place. So here is the tricky part, apparently Gutsy already loaded my card’s module and is conflicting with the new installed driver. So we will have to remove the modules using rmmod.
sudo rmmod rt2500pci rt2x00pci rt2x00lib
Thats it! Perhaps you would have to unload ndiswrapper using rmmod and reload it again though.
8-Finally, you will probably need to cement this in order not to do this everytime you restart, so you will have blacklist the three modules we removed.
sudo nano /etc/modprobe.d/blacklist
And add these lines:
blacklist rt2500pci
blacklist rt2x00pci
blacklist rt2x00lib
Also add the ndiswrapper in /etc/modules to automatically load it when booting
sudo nano /etc/modules
And add:
ndiswrapper
Happy tweaking!!
Edit: If you know of anyway to improve this guide, or have suggestions, or other workarounds. Please comment or E-mail me.
Royal HeHe2-ness is a world where free software is valued, nay sought for!! While proprietary software is banished, degraded and ridiculed till the end of times.
gluonman
January 7th, 2008 at 2:10 pm
You know, the link to the driver (step 1) leads to an error. Any other way of finding that driver?
atropos
January 7th, 2008 at 4:43 pm
@gluonman: Apparently Linksys just changed the location of the file. Here is the card’s page.
Use the menu on the left
mazingerZ
January 25th, 2008 at 3:32 am
I’m just wondering if this will work for v4.1 cards, which use different drivers.. I’m guessing the principle is the same but you just blacklist the different drivers?
atropos
January 25th, 2008 at 3:50 am
hmm, you will have to try it out, but I believe so. Try it out and if you have any troubles let me know.
PS: anime?
jglee
May 15th, 2008 at 6:01 pm
after a long struggle, this worked for my 4.1 card. thanks for taking the time to write up the process.