Intel Pro wireless 4965 can't connect to WPA network

Venlaar · #1 (**permalink**) 05-Mar-2009, 23:51

I am having a problem getting my Intel ProWireless 4965AGN wireless card to work under SuSE 11.1. I can connect to the WPA encrypted network with no problem under Vista on the same laptop. I have tried it also under Ubuntu 8.10 and it isn't working under it either. I am however able to connect to a non-encrypted neighbor's network with no problem under both SuSE 11.1 and Ubuntu 8.10. I am hoping someone has a solution for this issue as I don't really feel good about hijacking my neighbor's wireless. Here is some info on the card:

Code:

lspci
06:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)
lspci -n
06:00.0 0280: 8086:4229 (rev 61)

Code:

dmesg
iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27ks
iwlagn: Copyright(c) 2003-2008 Intel Corporation
...
iwlagn 0000:06:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
iwlagn 0000:06:00.0: setting latency timer to 64
iwlagn: Detected Intel Wireless WiFi Link 4965AGN REV=0x4
iwlagn: Tunable channels: 11 802.11bg, 13 802.11a channels
vendor=8086 device=2843
iwlagn 0000:06:00.0: PCI INT A disabled
phy0: Selected rate control algorithm 'iwl-agn-rs'
...
iwlagn 0000:06:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
iwlagn 0000:06:00.0: restoring config space at offset 0x1 (was 0x40100102, writi
ng 0x40100106)
...
firmware: requesting iwlwifi-4965-2.ucode
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
...
wlan0: authenticate with AP 00:16:b6:08:28:c7
wlan0: authenticated
wlan0: associate with AP 00:16:b6:08:28:c7
wlan0: RX AssocResp from 00:16:b6:08:28:c7 (capab=0x401 status=0 aid=1)
wlan0: associated
wlan0: disassociating by local choice (reason=3)

Code:

iwconfig 
lo        no wireless extensions.

eth0      no wireless extensions.

wmaster0  no wireless extensions.

wlan0     IEEE 802.11abgn  ESSID:"linksys"  
          Mode:Managed  Frequency:2.437 GHz  Access Point: 00:16:B6:08:28:C7   
          Bit Rate=36 Mb/s   Tx-Power=14 dBm   
          Retry min limit:7   RTS thr:off   Fragment thr=2352 B   
          Power Management:off
          Link Quality=35/100  Signal level:-80 dBm  Noise level=-94 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

pan0      no wireless extensions.

Code:

iwlist scan

wlan0     Scan completed :

   Cell 02 - Address: 00:13:10:ED:62:0A
                    ESSID:"WildTundra"
                    Mode:Master
                    Channel:6
                    Frequency:2.437 GHz (Channel 6)
                    Quality=46/100  Signal level:-81 dBm  Noise level=-127 dBm
                    Encryption key:on
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (1) : TKIP
                        Authentication Suites (1) : PSK
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
                              9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
                              48 Mb/s; 54 Mb/s
                    Extra:tsf=000000a3e0c56360
                    Extra: Last beacon: 2812ms ago

caf4926 · #2 (**permalink**) 06-Mar-2009, 00:05

Make sure you have this installed

iwl4965-ucode

Are you managing connections with networkmanager?

I'm am and have the following device

Quote:

Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection
Kernel driver in use: iwl3945
Kernel modules: iwl3945

No problems for me. I know it's not quite the same. But believe it or not, it works better than in Vista.

Venlaar · #3 (**permalink**) 06-Mar-2009, 08:44

Thanks for the quick reply. I checked in YaST and iwl4965-ucode is installed. It looks like the kernel driver is iwlagn. It looks like the kernel module is also iwlagn. I wonder if this is the problem. I'm not quite sure if there is a iwl4965 driver or module or how I would install it. I'm a relative newbie to linux. If you have any ideas it would be greatly appriciated.

lwfinger · #4 (**permalink**) 06-Mar-2009, 09:32

Venlaar wrote:
> Thanks for the quick reply. I checked in YaST and iwl4965-ucode is
> installed. It looks like the kernel driver is iwlagn. It looks like the
> kernel module is also iwlagn. I wonder if this is the problem. I'm not
> quite sure if there is a iwl4965 driver or module or how I would install
> it. I'm a relative newbie to linux. If you have any ideas it would be
> greatly appriciated.

The "driver" and the kernel module are the same thing. The kernel bases its
module decision based on PCI ID's. As you can connect with an unencrypted
network, your hardware is working just fine. It is your configuration that is wrong.

Do you have the wpa_supplicant package installed? You also didn't answer the
question concerning use of NetworkManager.

Venlaar · #5 (**permalink**) 06-Mar-2009, 17:35

I am using NetworkManager Applet to connect. I checked and wpa_supplicant is installed. Any suggestions on how it should be configured to work with WPA?

brucecadieux · #6 (**permalink**) 06-Mar-2009, 18:02

If you are using the KDE4 networkmanager it will not connect to a secured network, this is a known issue.

The kde3 knetworkmanager will connect to a secured network.

If you can connect to an unsecured network then your driver is fine.

If kde3networkmanager won't work for you, then you can use kinternet and it should do the job.

Venlaar · #7 (**permalink**) 06-Mar-2009, 19:37

Quote:

If you are using the KDE4 networkmanager it will not connect to a secured network, this is a known issue.

The kde3 knetworkmanager will connect to a secured network.

If you can connect to an unsecured network then your driver is fine.

If kde3networkmanager won't work for you, then you can use kinternet and it should do the job.

I am actually using Gnome but I have kde 3 and 4 installed also. I tried kde3 and knetworkmanager and it didn't work. I had a strange occurance also when I tried to log out and log back in using kde 4 it just went into gnome. I tried rebooting and now I believe I am in kde 3 and I am connected to my network.

Venlaar · #8 (**permalink**) 06-Mar-2009, 19:48

I just tried logging out and back into kde 3 and now it isn't connecting to my network. I logged out and successfully this time into gnome and I still can't connect to my encrypted network. I don't know what made the difference the one time.

Venlaar · #9 (**permalink**) 06-Mar-2009, 20:15

Now I have a separate problem. When I'm trying to log in selecting a desktop manager it seems to be a **** shoot as to which one I get. I have tried several times to boot back into kde3 with no success. I either end up in kde4 or gnome. I also tried icewm and xfce and once again i ended up in either kde4 or gnome. I have SuSE 11.0 installed on a desktop and haven't had these problems starting up a different desktop manager. If I can get into kde3 I will try kinternet.

caf4926 · #10 (**permalink**) 06-Mar-2009, 21:42

It cannot be such 'Pot Luck' as you describe Login.

You select kde3 OR kde4.... from the Login Options in the lower left of your login screen - That's it. You can't have selected one and get the other.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode