Sunday, August 19, 2012

How To Use A Belkin N450/N600 DB USB Wi-Fi, F9L1101 (v1) On Ubuntu!

I just got a new computer the other day, actually a Pentium 4 server made in Canada. I installed Ubuntu 10.04 on the HDD, and loaded everything up. It was perfect until I realized that my Belkin F9L1101 USB Wi-Fi Adapter wasn't receiving a signal, let alone giving me a light to acknowledge it's plugged-in state. After a bunch of testing, I realized that the way to fix it was to upgrade to Ubuntu 10.10 (or 11.04 which I upgraded to after I realized that it was working already on 10.10. Basically, you have to open the Ubuntu Terminal, and type in (without the quotes) "apt-get install ndiswrapper-gtk". Or you could just go to the Ubuntu Software Center and search ndiswrapper. Ndiswrapper is a program that allows you to run Windows-based drivers on Ubuntu. After you download it, put the CD that came with the Belkin USB into the CD Drive of your computer. Don't run the CD, but right-click the icon of it, and select "explore". You will find a couple files in there, but the one you're looking for is in one of the folders. Look inside the folders until you find one called "drivers". Go in, and click on the "xp" folder, and drag it onto your desktop, or other desired location, then look inside for a couple of .sys, .cat, and .inf files. You should see one called "bcmwlhigh5.sys" and another called "bcmwlhigh564.sys". If you have an x86/32-bit architecture, then delete the "bcmwlhigh564.sys" file, and the opposite if you have a 64-bit architecture. If you aren't sure what kind of architecture you have, open the Terminal, and type in (once again, without quotes) "lscpu" and it should tell you. At this point, go into the top left corner of your screen, and click on the drop-down menu for "System", and navigate to "Administration", and then look for "Windows Wireless Drivers". Click on it to open the program, and click "Add Drivers". Go to wherever you have the .inf file and select it, making sure your Belkin USB is plugged in. Now, just reboot, and it should be working.

No comments:

Post a Comment