Intel Pro wireless 4965 can't connect to WPA network

[Venlaar]

I did manage once more to get into kde3 and tried several times with network manager to connect to my encrypted network with no success. I tried installing kinternet with YaST and I got a Microsoft EULA pop up. I saw an update I hadn't installed yet for TrueType Fonts so I figured it was from that. I declined the EULA and another popped up and I declined it as well. After installing kinternet I tried running it from the command line and got a pop up box error message saying something about a missing server.

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.

I would tend to agree if it wasn't happening to me. However I think we may be talking about two separate login processes. When I boot up to SuSE from GRUB it doesn't take me to a login screen it just logs me in automatically. The way I was using to switch desktop managers was hitting logout button then from that login screen clicking on my login which changed the options on the bottom to allow different desktops. Then I click the drop down button and select my desktop manager, type in my password (I even checked the selection again at this point). Now I hit enter or click the arrow button next to the password field and then watch it boot into some window manager I did not select (mostly). If I can figure out how to change the way it logs in I will make it not auto login so that I can select the desktop manager to see if that makes a difference.

[Venlaar]

At least now when I boot up I am getting into kde3 so I will stick with that for the time being so that we can stay on topic about getting connected to my encrypted network. Here is a tail from wpa_supplicant.log. It doesn't look to me like it sheds any light on why this is not working though.

WPA: Group rekeying completed with 00:13:10:ed:62:0a [GTK=TKIP]
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Associated with 00:13:10:ed:62:0a
CTRL-EVENT-SCAN-RESULTS
WPA: Key negotiation completed with 00:13:10:ed:62:0a [PTK=TKIP GTK=TKIP]
CTRL-EVENT-CONNECTED - Connection to 00:13:10:ed:62:0a completed (reauth) [id=0 id_str=]
WPA: Group rekeying completed with 00:13:10:ed:62:0a [GTK=TKIP]
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-SCAN-RESULTS
CTRL-EVENT-SCAN-RESULTS

Oh and kinternet doesn't look like it does anything when I'm already connected to the unencrypted network. At the command line it looks like it's running but nothing happens. I don't get the error popup.

Ok so after trying to connect to my network again and it disconnecting I tried kinternet to get the error message. Here it is:

Connection to local and remote server
refused. Maybe smpppd is not running
or you are not member of the group "dialout".
Also check the server settings in
the dialog "Various Settings".

But if this is just a configuration problem then I don't want to have to rely on a particular window manager or kinternet to connect. I really want to find then underlying configuration error so that I can connect using any desktop manager.

[Venlaar]

Oh just checked and I am in the dialout group. Under various settings it is set to automatic for smpppd. A ps | grep smpppd looks like it isn't running so I guess that's the problem there.

[Venlaar]

So I got kinternet working but it couldn't see any of the 11-14 networks that I normally see under gnome. It only would see the unencrypted linksys that I was connected to before I started it up. I tried every search option in the tool and since you can't type in a specific ESSID I couldn't do that. I turned off IPv6 in the network configuration also which said I needed to reboot. I tried just logging out and back in but instead of taking me back into kde3 it took me to gnome which now for some reason isn't running it's network manager. I rebooted completely and now am back in kde3 using network manager and still unable to connect to my encrypted network.

[Venlaar]

I thought I would include the NetworkManager log in case this might shed some light on it.

Mar  7 09:28:04 linux-xzov NetworkManager: <info>  Activation (wlan0) successful
, device activated.
Mar  7 09:28:04 linux-xzov NetworkManager: <info>  Activation (wlan0) Stage 5 of
 5 (IP Configure Commit) complete.
Mar  7 09:57:14 linux-xzov NetworkManager: <info>  DHCP: device wlan0 state chan
ged bound -> renew
Mar  7 09:57:14 linux-xzov NetworkManager: <info>    address 192.168.1.107
Mar  7 09:57:14 linux-xzov NetworkManager: <info>    prefix 24 (255.255.255.0)
Mar  7 09:57:14 linux-xzov NetworkManager: <info>    gateway 192.168.1.1
Mar  7 09:57:14 linux-xzov NetworkManager: <info>    nameserver '68.87.85.98'
Mar  7 09:57:14 linux-xzov NetworkManager: <info>    nameserver '68.87.69.146'
Mar  7 09:57:14 linux-xzov NetworkManager: <info>    nameserver '68.87.78.130'
Mar  7 09:57:14 linux-xzov NetworkManager: <info>    domain name 'hsd1.co.comcas
t.net.'
Mar  7 10:52:03 linux-xzov NetworkManager: <info>  (wlan0): device state change:
 8 -> 3
Mar  7 10:52:03 linux-xzov NetworkManager: <info>  (wlan0): deactivating device
(reason: 0).
Mar  7 10:52:03 linux-xzov NetworkManager: <info>  wlan0: canceled DHCP transact
ion, dhcp client pid 7180
Mar  7 10:52:03 linux-xzov NetworkManager: <debug> [1236448323.202775] run_netco
nfig(): Spawning '/sbin/netconfig modify --service NetworkManager'
Mar  7 10:52:03 linux-xzov NetworkManager: <debug> [1236448323.205663] write_to_
netconfig(): Writing to netconfig: INTERFACE='wlan0'
Mar  7 10:52:03 linux-xzov NetworkManager: <info>  Clearing nscd hosts cache.
Mar  7 10:52:03 linux-xzov NetworkManager: <WARN>  check_one_route(): (wlan0) er
ror -34 returned from rtnl_route_del(): Sucess
Mar  7 10:52:03 linux-xzov NetworkManager: <info>  Activation (wlan0) starting c
onnection 'WildTundra'
Mar  7 10:52:03 linux-xzov NetworkManager: <info>  (wlan0): device state change:
 3 -> 4
Mar  7 10:52:03 linux-xzov NetworkManager: <info>  Activation (wlan0) Stage 1 of
 5 (Device Prepare) scheduled...
Mar  7 10:52:03 linux-xzov NetworkManager: <info>  Activation (wlan0) Stage 1 of
 5 (Device Prepare) started...
Mar  7 10:52:03 linux-xzov NetworkManager: <info>  Activation (wlan0) Stage 2 of
 5 (Device Configure) scheduled...
Mar  7 10:52:03 linux-xzov NetworkManager: <info>  Activation (wlan0) Stage 1 of
 5 (Device Prepare) complete.
Mar  7 10:52:03 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  completed -> disconnected
Mar  7 10:52:03 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  disconnected -> associated
Mar  7 10:52:03 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  associated -> disconnected
Mar  7 10:52:03 linux-xzov NetworkManager: <info>  Activation (wlan0) Stage 2 of
 5 (Device Configure) starting...
Mar  7 10:52:03 linux-xzov NetworkManager: <info>  (wlan0): device state change:
 4 -> 5
Mar  7 10:52:03 linux-xzov NetworkManager: <info>  Activation (wlan0/wireless):
access point 'WildTundra' has security, but secrets are required.
Mar  7 10:52:03 linux-xzov NetworkManager: <info>  (wlan0): device state change:
 5 -> 6
Mar  7 10:52:03 linux-xzov NetworkManager: <info>  Activation (wlan0) Stage 2 of
 5 (Device Configure) complete.
Mar  7 10:52:03 linux-xzov NetworkManager: <info>  Activation (wlan0) Stage 1 of
 5 (Device Prepare) scheduled...
Mar  7 10:52:03 linux-xzov NetworkManager: <info>  Activation (wlan0) Stage 1 of
 5 (Device Prepare) started...
Mar  7 10:52:03 linux-xzov NetworkManager: <info>  (wlan0): device state change:
 6 -> 4
Mar  7 10:52:03 linux-xzov NetworkManager: <info>  Activation (wlan0) Stage 2 of
 5 (Device Configure) scheduled...
Mar  7 10:52:03 linux-xzov NetworkManager: <info>  Activation (wlan0) Stage 1 of
 5 (Device Prepare) complete.
Mar  7 10:52:03 linux-xzov NetworkManager: <info>  Activation (wlan0) Stage 2 of
 5 (Device Configure) starting...
Mar  7 10:52:03 linux-xzov NetworkManager: <info>  (wlan0): device state change:
 4 -> 5
Mar  7 10:52:03 linux-xzov NetworkManager: <info>  Activation (wlan0/wireless):
connection 'WildTundra' has security, and secrets exist.  No new secrets needed.
Mar  7 10:52:03 linux-xzov NetworkManager: <info>  Config: added 'ssid' value 'W
ildTundra'
Mar  7 10:52:03 linux-xzov NetworkManager: <info>  Config: added 'scan_ssid' val
ue '1'
Mar  7 10:52:03 linux-xzov NetworkManager: <info>  Config: added 'key_mgmt' valu
e 'WPA-PSK'
Mar  7 10:52:03 linux-xzov NetworkManager: <info>  Config: added 'psk' value '<o
mitted>'
Mar  7 10:52:03 linux-xzov NetworkManager: <info>  Config: added 'pairwise' valu
e 'TKIP CCMP'
Mar  7 10:52:03 linux-xzov NetworkManager: <info>  Config: added 'group' value '
TKIP CCMP'
Mar  7 10:52:03 linux-xzov NetworkManager: <info>  Activation (wlan0) Stage 2 of
 5 (Device Configure) complete.
Mar  7 10:52:03 linux-xzov NetworkManager: <info>  Config: set interface ap_scan
 to 1
Mar  7 10:52:03 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  disconnected -> scanning
Mar  7 10:52:11 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  scanning -> associating
Mar  7 10:52:11 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  associating -> disconnected
Mar  7 10:52:11 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  disconnected -> associated
Mar  7 10:52:15 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  associated -> 4-way handshake
Mar  7 10:52:15 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  4-way handshake -> group handshake
Mar  7 10:52:15 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  group handshake -> completed
Mar  7 10:52:15 linux-xzov NetworkManager: <info>  Activation (wlan0/wireless) S
tage 2 of 5 (Device Configure) successful.  Connected to wireless network 'WildT
undra'.
Mar  7 10:52:15 linux-xzov NetworkManager: <info>  Activation (wlan0) Stage 3 of
 5 (IP Configure Start) scheduled.
Mar  7 10:52:15 linux-xzov NetworkManager: <info>  Activation (wlan0) Stage 3 of
 5 (IP Configure Start) started...
Mar  7 10:52:15 linux-xzov NetworkManager: <info>  (wlan0): device state change:
 5 -> 7
Mar  7 10:52:15 linux-xzov NetworkManager: <info>  Activation (wlan0) Beginning
DHCP transaction.
Mar  7 10:52:15 linux-xzov NetworkManager: <info>  dhclient started with pid 832
4
Mar  7 10:52:15 linux-xzov NetworkManager: <info>  Activation (wlan0) Stage 3 of
 5 (IP Configure Start) complete.
Mar  7 10:52:15 linux-xzov NetworkManager: <info>  DHCP: device wlan0 state chan
ged normal exit -> preinit
Mar  7 10:52:18 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  completed -> group handshake
Mar  7 10:52:18 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  group handshake -> completed
Mar  7 10:52:21 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  completed -> disconnected
Mar  7 10:52:22 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  disconnected -> scanning
Mar  7 10:52:22 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  scanning -> 4-way handshake
Mar  7 10:52:22 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  4-way handshake -> associated
Mar  7 10:52:25 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  associated -> 4-way handshake
Mar  7 10:52:25 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  4-way handshake -> group handshake
Mar  7 10:52:25 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  group handshake -> completed
Mar  7 10:52:28 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  completed -> group handshake
Mar  7 10:52:28 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  group handshake -> completed
Mar  7 10:52:32 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  completed -> disconnected
Mar  7 10:52:32 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  disconnected -> scanning
Mar  7 10:52:33 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  scanning -> 4-way handshake
Mar  7 10:52:33 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  4-way handshake -> associated
Mar  7 10:52:35 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  associated -> 4-way handshake
Mar  7 10:52:35 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  4-way handshake -> group handshake
Mar  7 10:52:35 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  group handshake -> completed
Mar  7 10:52:38 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  completed -> group handshake
Mar  7 10:52:38 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  group handshake -> completed
Mar  7 10:52:42 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  completed -> disconnected
Mar  7 10:52:42 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  disconnected -> scanning
Mar  7 10:52:43 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  scanning -> 4-way handshake
Mar  7 10:52:43 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  4-way handshake -> associated
Mar  7 10:52:45 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  associated -> 4-way handshake
Mar  7 10:52:45 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  4-way handshake -> group handshake
Mar  7 10:52:45 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  group handshake -> completed
Mar  7 10:52:48 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  completed -> group handshake
Mar  7 10:52:48 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  group handshake -> completed
Mar  7 10:52:52 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  completed -> disconnected
Mar  7 10:52:52 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  disconnected -> scanning
Mar  7 10:52:53 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  scanning -> 4-way handshake
Mar  7 10:52:53 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  4-way handshake -> associated
Mar  7 10:52:55 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  associated -> 4-way handshake
Mar  7 10:52:55 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  4-way handshake -> group handshake
Mar  7 10:52:55 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  group handshake -> completed
Mar  7 10:52:59 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio
n state:  completed -> group handshake
Mar  7 10:52:59 linux-xzov NetworkManager: <info>  (wlan0): supplicant connectio                                                           n state:  group handshake -> completed
Mar  7 10:53:00 linux-xzov NetworkManager: <info>  Device 'wlan0' DHCP transacti                                                           on took too long (>45s), stopping it.
Mar  7 10:53:00 linux-xzov NetworkManager: <info>  wlan0: canceled DHCP transact                                                           ion, dhcp client pid 8324
Mar  7 10:53:00 linux-xzov NetworkManager: <info>  Activation (wlan0) Stage 4 of                                                            5 (IP Configure Timeout) scheduled...
Mar  7 10:53:00 linux-xzov NetworkManager: <info>  Activation (wlan0) Stage 4 of                                                            5 (IP Configure Timeout) started...
Mar  7 10:53:00 linux-xzov NetworkManager: <info>  (wlan0): device state change:                                                            7 -> 9
Mar  7 10:53:00 linux-xzov NetworkManager: <info>  Activation (wlan0) failed for                                                            access point (WildTundra)
Mar  7 10:53:00 linux-xzov NetworkManager: <info>  Marking connection 'WildTundr                                                           a' invalid.
Mar  7 10:53:00 linux-xzov NetworkManager: <info>  Activation (wlan0) failed.
Mar  7 10:53:00 linux-xzov NetworkManager: <info>  Activation (wlan0) Stage 4 of                                                            5 (IP Configure Timeout) complete.
Mar  7 10:53:00 linux-xzov NetworkManager: <info>  (wlan0): device state change:                                                            9 -> 3
Mar  7 10:53:00 linux-xzov NetworkManager: <info>  (wlan0): deactivating device                                                            (reason: 0).

[Venlaar]

Well this is confusing. I tested this with wpa on a friends network using a dlink wbr2310 router and connected just fine with wpa using kde3. At home the router I was attempting to connect to was a linksys wrt54g (I think thats it anyway it's the router that comes with the wkpc54g package). I know I had to downgrade the firmware on the router because of a problem that linksys refused to fix after the newer version became a problem for people. When I get home again I'll have to verify the model number and see if i can install dd-wrt on it. I seem to remember some reason I couldn't install it before.

[Venlaar]

Ok so I have a little update. I tried connecting to my friends WPA network on his dlink router using kde3, kde4 and gnome and all 3 were successful. So I guess this means something is wrong with the implementation of the linksys router I am using.

On a side note I'm still having trouble logging out and logging back into a desktop manager. But I think that if I log out select a desktop manager and instead of logging in again if I select reboot it seems to boot to the correct desktop manager. I'll keep you posted as to anything I find out about the linksys. Hopefully it will help someone out.

[lwfinger]

Venlaar wrote:
> Well this is confusing. I tested this with wpa on a friends network
> using a dlink wbr2310 router and connected just fine with wpa using
> kde3. At home the router I was attempting to connect to was a linksys
> wrt54g (I think thats it anyway it's the router that comes with the
> wkpc54g package). I know I had to downgrade the firmware on the router
> because of a problem that linksys refused to fix after the newer version
> became a problem for people. When I get home again I'll have to verify
> the model number and see if i can install dd-wrt on it. I seem to
> remember some reason I couldn't install it before.

Which version of WRT54G?

Larry

[Venlaar]

Which version of WRT54G?

Larry

Actually once I got home I looked at it again and the router is a WRK54G ver 1.1 that comes with the WKPC54G package that also includes the WPC54G PCMCIA card. So I was having trouble remembering what had been wrong before cause I remembered downgrading the firmware but had forgotten why. Then I found some posts with a google search that cleared it up for me and sparked my memory. There was a problem with the WRK54G locking up to the point you would have to reset it and it was happening daily. That was using the latest linksys firmware 1.58.03. The only solution was to downgrade the firmware since neither dd-wrt nor openwrt doesn't support the WRK54G. I had previously downgraded to the 1.58.00 firmware and it seemed to work well enough. No more drops or lockups. But now with this issue I know it won't work with it looks like any flavor of linux or at least not with the Intel 4965 card. I also tried last night several times to upgrade the firmware back to the 1.58.03 (which might have caused more problems then it would have solved) but was unable to as I received an error during the update and the firmware never changed. So it looks like my solution is going to be to go to Best Buy and throw down some cash to get a new router. I still don't understand why Vista is able to connect using the same card though.

[sunscape]

Actually, you found a nasty bug that has plagued many people for a long time...

Since kernel 2.6.27.x iwlagn (4965) has had serious problems connecting to some routers and disconnects and kernel panics are common. I have been waiting for someone to fix this bug for a very long time, and the suse team thought they had a fix that was pushed out in the recent kernel update. Their fix prevents crashing but does not solve the horrible connection issues.

Twiddling my thumbs while Bug 1918 – iwl4965 - Microcode SW error detected - Kernel 2.6.28 gets fixed.

This is just one problem of many with intel wireless. There is one bug report related to your issue; i think number 3 of 8.