The end-all definitive guide to getting wireless working in Ubuntu Edgy Eft
Alright, people are always asking at OSU Opensource Club, “How do I get my wireless card working?” So instead of answering this question over and over, I decided to write this guide instead.
Step 1. Do I have a wireless card?
The first thing we have to figure out is whether Ubuntu knows about the wireless card. Unfortunately, some wireless companies refuse to tell the community how their cards work and don’t see the demand to write Linux drivers. In this case, people are working to reverse-engineer these wireless cards but it’s still very sketchy right now. If you have Intel Centrino, you’re in luck because these will almost certainly work without any added nonsense.
To see if your wireless card is recognized, we will run some commands in the Terminal. Of course, you can do almost all of this without it in Ubuntu, but it’s much easier to copy and paste text then to go through lots of dialogs. To start the terminal, go to Applications->Accessories->Terminal, and type iwconfig.
After running the command, you should get something similar to this:
paul@desdemona:~$ iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
eth1 IEEE 802.11b/g ESSID:"Intarnet" Nickname:"Broadcom 4318"
Mode:Managed Frequency=2.417 GHz Access Point: 00:16:01:4A:C5:48
Bit Rate=11 Mb/s Tx-Power=18 dBm
RTS thr:off Fragment thr:off
Link Quality=56/100 Signal level=-49 dBm Noise level=-70 dBm
Rx invalid nwid:0 Rx invalid crypt:1345 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
If you see this, you should be good to go. If you only see “no wireless extensions” for every entry, your wireless card isn’t supported natively.
My wireless card isn’t here!
Fear not! Your wireless card can still work using a program called NDISWrapper. This allows you to use Windows wireless drivers in Linux. To get this to work:
- In the terminal window you opened, run lspci -nn. Then look for the numbers highlighted in red here:
05:02.0 Network controller [0280]: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller [14e4:4318] (rev 02)
- Go to the NDISWrapper Compatibility List and search the page for the ID, then download the driver. After unzipping, you should end up with (at least)two files, a .INF file and a .SYS file.
- In the terminal run sudo apt-get install ndisgtk, then go to System->Administration->Windows Wireless Drivers. Install the Windows drivers by browsing to the .INF file
- Try iwconfig again. If it doesn’t work, run sudo modprobe ndiswrapper in the terminal then try again. If it still doesn’t work, you may have to try another driver.
Install NetworkManager
Now that you have your wireless card working, let’s install a program to let us select wireless networks directly called NetworkManager. Run the command (in the terminal!) sudo apt-get install network-manager-gnome, then reboot. You’ll be greeted by a new icon:
Congratulations! Your wireless should work with standard access points.
What about OSU Wireless?
Now, for OSU Wireless, you need to do a bit extra. Make sure to register to get your username (usually your OSU username + ‘w’, mine is “betts.62w”) and get your password. When you try to connect using Network Manager, you should get a dialog similar to this one:
Only fill in the two fields colored in red, NetworkManager sets the rest of the fields correctly by default. Some people report they don’t get this dialog when they try to connect to OSU Wireless; if this happens, make sure your NetworkManager is up to date (it should be >= version 0.6.3). It could also be that your native wireless driver isn’t finished, so try the NDISWrapper driver if you aren’t already using it.
Update: I was able to get the actual OSU Wireless dialog
Entries RSS
Bill said,
March 30, 2007 @ 3:54 pm
I have the network manager installed but am unable to set the “nickname” parameter. The SSID is correct - I am able to specify it through the network manager. However, there is no obvious way to specify the nickname. I know neither what the nickname should be nor how to set it. If you can help, that would be wonderful. If you have too little time and too many emails to which you must respond, I fully understand and thank you for the tutorial you posted above.
Paul Betts said,
March 30, 2007 @ 4:00 pm
The nickname is set by the driver, it’s just a hint so that you know what eth1 is if you have eth1, eth2 and eth3 and don’t know which attaches to which adapter. You don’t need to worry about it.
Braiden said,
April 21, 2008 @ 5:03 pm
I am having trouble getting the network manager installed. I go to the NetworkManager link and click on the most recent version and save it to the computer. Then when I type into the terminal the sudo apt-get install command it says that the network manager cannot be found. Am I doing it wrong. It feels as though there should be another command somewhere.
I am using an Asus Eee Pc that uses a customized version of Xandros. Will that have any bearing over these instructions? Are there other steps that aren’t listed? I’m really frustrated and everywhere wants $60+ dollars an hour and I am not paying that. Any help would be appreciated.
Paul Betts said,
April 27, 2008 @ 12:18 am
@Braiden: Sadly, I don’t know how these apply to Xandros. However, since it’s a Debian-based distro, you should be able to run:
apt-cache search Network Manager
and it will give you the correct name to use in the apt-get install command.
Josh said,
May 1, 2008 @ 9:00 am
Paul,
I spent an hour trying to get the wireless to work using OIT’s information, but your simple tutorial worked right away; perhaps you should submit it to OIT. Thanks!
Josh