OSourceDiplomat is right. However, I guess there are several problems you need to solve in a reasonable order (I don't want to sound patronising, but I'll try to cover it extensively - please bear with me).
As far as I can see, you tried most of the following steps, but something may have gone wrong somewhere. It's also possible that iwconfig
can't talk to your card - indicating that there's indeed a driver/kernel module problem. Try this procedure:
1) Be root; I don't know how your system is set up, but this means either using the su
command and entering your root password or using sudo
with or without password, depending on your system. Whichever you choose, make sure to work in a consistent way (you needn't logout and login again as root). Well, you'll know how to do that.
2) Use lspci
(OSourceDiplomat gave the path just in case) to determine the exact chipset your adaptor is using. This will help you find out if the kernel module is loaded and/or available on (or for) your system.
3.) Use lsmod
to determine if the appropriate kernel module (driver) is loaded.
3.1) If not, you can try to load it with modprobe <yourmodule>
. You can look for it in /lib/modules/<yourkernel>/net/wireless
- or any other appropriate subdirectory of /lib/modules/<yourkernel>
. If it's not present on your system, this won't work and you'll need to get the driver (an existing kernel module or a set of such modules) first via your distributions package management or downloading it, possibly compiling it for your kernel. Look here for more information: http://tools.cisco.com/support/downl...utype=wireless
3.2) You can also install ndiswrapper
. In this case you'll also have to get hold of a suitable WinDoze driver for your wireless adaptor. The rest is done according to man ndiswrapper
(it's really easy). But since there are kernel modules for Aironet cards, I'd rather recommend to stick to 3)
4) Use iwconfig wifi0
to have a look at the current setup of your wifi connection. If the driver's there, you'll see some basic configuration information, nothing spectacular (you more or less reported on that already). If you see some cryptic error codes, the driver's still missing. This means: Go back to 3)
5.1) Use iwconfig wifi0 essid <youressid>
. This is a) necessary if it's not set and b) a good test if things work correctly (you did something similar already). If things fail here, it's time to look for further advice (which you did). If in doubt, go back to 3)
5.2) Use iwconfig wifi0 mode <yourmode>
5.3) Use iwconfig wifi0 channel <yourchannel>
5.4) Use iwconfig wifi0 key <yourkeymode> <yourkey>
(You can do 5.1 to 5.4 in one sweep, but in order to determine what goes wrong where, I'd do it step by step. You may also need additional steps here, depending on your setup.)
6) Use ifconfig wifi0 up
; if this fails, you might have to use ifconfig eth0 down
first, but this shouldn't be the case (but it might if you're already connected to your LAN via ethernet). See 10) though.
7) Use dhclient wifi0
; if you get another error message, you might have to do kill <dhclient-pid>
first (it's given in the error message IIRC - one of your posts shows that). If you're not sure about the PID, use ps -ef | less
to find it. If dhclient
works correctly, you're online.