env: kernel 2.6.31/ gcc 4.3.4/ make 3.81/ debian unstable
I double check the related setting again. It looks correct to me, but I think there should have something missing and I am not aware of it. They are follow:
Firmware located at /lib/firmware contains
The result of lsmod | grep iwlagn
iwlagn 73340 0
iwlcore 95716 1 iwlagn
mac80211 124608 2 iwlagn, iwlcore
cfg80211 76636 3 iwlagn, iwlcore, mac80211
led_class 3868 3 iwlcore, hp_accel, sdhci
I can not find any kernel module with `lsmod | grep 4965`, which is the module detected in the past. I also read on the internet saying that iwl4965 is iwlagn in fact, as follow:
The syslog shows
iwlagn: Intel(R) Wireless Wifi Link AGN driver for Linux, 1.3.27ks
iwlagn: Copyright(c) 2003-2009 Intel Corporation
iwlagn: 0000:10:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
iwlagn: 0000:10:00.0: setting latency timer to 64
iwlagn: 0000:10:00.0: Detected Intel Wireless WiFi Link 4965AGN REV=0x4
iwlagn 0000:10:00.0: firmware: requesting iwlwifi-4965-2.ucode
iwlagn 0000:10:00.0: loaded firmware version 22.214.171.124
Registered led device: iwl-phy0::radio
Registered led device: iwl-phy0::assoc
Registered led device: iwl-phy0::RX
Registered led device: iwl-phy0::TX
ADDRCONF(NETDEV_UP): wlan0: link is not ready
It looks like the firmware is loaded, but I do not know why the link is not ready.
The iwconfig reault
wlan0 IEEEE 802.11abgn ESSID:"TEST"
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Retry long limit: 7 RTS thr:off Fragment thr:off
Power Management: off
Link Quality:0 Signal level: 0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx execessive retries:0 Invalid misc: 0 Missed beacon:0
The interfaces configuration
iface wlan0 inet dhcp
Does these look correct?
Thanks for the help.
I appreciate it.
Originally Posted by evo2
That is extremly strange. I should output much more than that, even if it does fail.
It depends if the typos above are only in your post and not in your interfaces file. If what is really in your interfaces file is as below, then it should work for wep.
iface wlan0 inet dhcp
I'm pretty sure that what I posted is correct. There must be some other problem.
From your original post it seems that you are able to use some gui tool to get your wireless working. If so can you please post the output of the following for two cases
1. When the wireless is working: after bring it up with the gui
2. When it is not working: just after failing to bring it up on the command line.