[SOLVED] Since networkmanager upgrade wifi dowsn't connect anymore

Pitou · 2012-02-25 02:03:21

Hello,

Since the networkmanager's upgrade I did today, my wifi connection doesn't establish anymore. It tries then disconnect after a few sec.

Any idea?

Thank you.

Pitou!

Last edited by Pitou (2012-03-09 15:09:37)

vwyodajl · 2012-02-25 06:33:37

Might want to start off by giving some info (wifi chip and other relevant info) and post actual error's you're seeing.

Pitou · 2012-02-25 12:36:36

I'm not sure where to look to be honest.

Here is a log from dmesg:

[38517.207363] wlan0: authenticate with 74:ea:3a:a1:6a:28 (try 1)
[38517.209706] wlan0: authenticated
[38517.249837] wlan0: associate with 74:ea:3a:a1:6a:28 (try 1)
[38517.253906] wlan0: RX AssocResp from 74:ea:3a:a1:6a:28 (capab=0x411 status=0 aid=1)
[38517.253909] wlan0: associated
[38517.261959] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[38517.375157] Intel AES-NI instructions are not detected.
[38525.141841] wlan0: deauthenticating from 74:ea:3a:a1:6a:28 by local choice (reason=3)
[38525.300135] cfg80211: Calling CRDA for country: CO
[38528.820101] wlan0: authenticate with 74:ea:3a:a1:6a:28 (try 1)
[38528.822343] wlan0: authenticated
[38528.842420] wlan0: associate with 74:ea:3a:a1:6a:28 (try 1)
[38528.846268] wlan0: RX ReassocResp from 74:ea:3a:a1:6a:28 (capab=0x411 status=0 aid=1)
[38528.846271] wlan0: associated
[38537.414008] wlan0: deauthenticating from 74:ea:3a:a1:6a:28 by local choice (reason=3)
[38537.560136] cfg80211: Calling CRDA for country: CA
[38540.820076] wlan0: authenticate with 74:ea:3a:a1:6a:28 (try 1)
[38540.822343] wlan0: authenticated
[38540.842608] wlan0: associate with 74:ea:3a:a1:6a:28 (try 1)
[38540.846691] wlan0: RX ReassocResp from 74:ea:3a:a1:6a:28 (capab=0x411 status=0 aid=1)
[38540.846694] wlan0: associated

Here is my wireless card according to lspci:

05:02.0 Network controller: Atheros Communications Inc. AR922X Wireless Network Adapter (rev 01)

iwconfig:

wlan0 IEEE 802.11bgn ESSID:"Univers"
Mode:Managed Frequency:2.452 GHz Access Point: 74:EA:3A:A1:6A:28
Bit Rate=1 Mb/s Tx-Power=18 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=70/70 Signal level=-35 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:14 Missed beacon:0

I'm running gnome3/gnomeshell and I see the little icon trying to connect (the 3 little dots) and then fail and try again.

Any suggestions?

Pitou!

vwyodajl · 2012-02-25 20:54:55

You could see if you have more than one instance of wpa-supplicant running. If so kill them all restart wpa-supplicant and then see if it works. I see on google there are a bunch of posting relating to NM and Reason=3, most seem to have multiple instance of wpa-* running.

Another post just says even if only one is running kill it do not start again and just try to authenticate with the AP. This might be of use to you https://azitech.wordpress.com/2010/02/2 … g-reason3/

I gave up on NM awhile ago for other reasons, it did not like my wifi card either after a certain update, wicd just always works for me.
HTH

Pitou · 2012-02-26 02:13:47

Tried to kill wpa_supplicant, but it does restart by itself everytime the applet tries to connect.

Tried Wicd but cannot connect either the wired or wireless interface. it seems to connect but at the very end it says "not connected" at the bottom of the window.

helloworld1 · 2012-02-26 02:18:52

I have the same issue after today's update! I am using Intel 5300 agbn wireless card.

[ 6.012350] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 13.660387] wlan0: authenticate with 20:76:00:02:69:ec (try 1)
[ 13.666334] wlan0: authenticated
[ 13.666704] wlan0: associate with 20:76:00:02:69:ec (try 1)
[ 13.669415] wlan0: RX AssocResp from 20:76:00:02:69:ec (capab=0x411 status=0 aid=3)
[ 13.669420] wlan0: associated
[ 13.674723] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 25.255067] wlan0: deauthenticating from 20:76:00:02:69:ec by local choice (reason=3)
[ 30.609587] wlan0: authenticate with 20:76:00:02:69:ec (try 1)
[ 30.612352] wlan0: authenticated
[ 30.616049] wlan0: associate with 20:76:00:02:69:ec (try 1)
[ 30.618718] wlan0: RX ReassocResp from 20:76:00:02:69:ec (capab=0x411 status=0 aid=3)
[ 30.618724] wlan0: associated
[ 40.745188] wlan0: deauthenticating from 20:76:00:02:69:ec by local choice (reason=3)
[ 47.335124] wlan0: authenticate with 20:76:00:02:69:ec (try 1)
[ 47.338019] wlan0: authenticated
[ 47.340489] wlan0: associate with

Last edited by helloworld1 (2012-02-26 02:20:06)

benob · 2012-02-26 10:05:56

I am having the same problem with same hardware. Downgrading to networkmanager 0.9.2.0-1 and libnl 1.1-3 fixes it.

--- edit ---
Related post: https://bbs.archlinux.org/viewtopic.php?id=136406

Last edited by benob (2012-02-26 10:08:34)

Pitou · 2012-02-26 12:27:02

@benob: Could you tell how to downgrade networkmanager and libnl.

Thx!

Strike0 · 2012-02-26 12:57:47

Have a look here, Pitou.

Pitou · 2012-02-27 17:52:27

I did downgrade networkmanager along with libnl, but now it doesn't see any wifi AP. It says "not available"

iwlist scan works and find my AP.

Any idea?

benob · 2012-02-27 18:00:27

Same here. The downgrade worked until I rebooted. Now, whatever config I have, it doesn't work. In the mean time, I have been using https://wiki.archlinux.org/index.php/Wpa_supplicant and dhcpcd to connect.

Pitou · 2012-02-27 18:23:53

@benob: Thanks for the link, but I would prefer making networkmanager work....

Strike0 · 2012-02-27 19:06:12

Things to try, if you have not already:
1. disabling hardware encryption (https://bbs.archlinux.org/viewtopic.php … 65#p919065)
2. disabling wifi-N mode of the card
3. Install the LTS kernel

ewaller · 2012-02-27 20:56:03

I think I am fighting this same issue.

On my system, nm-applet does not see my network, but displays other networks from around my area. It does not try to associate with anything as the shown networks are all secure.

iwlist scan with user permissions reports that wlan0 has no scan results.,
sudo iwlist scan reports all of the APs in my area, including my router. Once this command is issued, the nm-applet immediately indicates that it has associated with my router and is obtaining an address. A few seconds later, I get full bars.

Anyone else see this? I am not in front of my machine right now, but I will try a different kernel this evening. I have been running 3.2.7.1, but I also have an older kernel with all of the modules built in to run without an initrd all go back and try. Maybe we can figure out if it is the kernel, network manager, or wireless tools.

Avant-texte · 2012-02-27 21:11:09

Pitou, is that all that was upgraded? NetworkManager isn't the only thing that can break WiFI.

AR922X, that uses ath9k doesn't it? That driver still has a few bugs. A lot of people with ath9k have had problems since recent updates. You may want to search some of those solved threads.

hokasch · 2012-02-27 21:11:17

man iwlist wrote:

Triggering scanning is a privileged operation (root only) and normal users can only read left-over scan results.

That would suggest that networkmanager is not initiating a scan of available networks - missing permissions or is it just lazy?

No idea what triggers a scan, apparently mine is not doing one when it comes out of suspend and stubbornly tries to connect to a now out-of-reach network (but thats for another thread).

Avant-texte · 2012-02-27 21:19:30

hokasch wrote:

man iwlist wrote:
Triggering scanning is a privileged operation (root only) and normal users can only read left-over scan results.
That would suggest that networkmanager is not initiating a scan of available networks - missing permissions or is it just lazy?
No idea what triggers a scan, apparently mine is not doing one when it comes out of suspend and stubbornly tries to connect to a now out-of-reach network (but thats for another thread).

Your DE/WM gets the privileges to controle networking via consolekit/polkit.

Last edited by Avant-texte (2012-02-27 21:23:40)

Pitou · 2012-02-27 21:34:13

@Avant-Texte: it could be the kernel upgrade as well. I remember when I did pacman -Syu, there was the libnl, networkmanager, nm-applet, but the kernel was there as well.

I'll look around.

ewaller · 2012-02-27 22:00:52

hokasch wrote:

man iwlist wrote:
Triggering scanning is a privileged operation (root only) and normal users can only read left-over scan results.
That would suggest that networkmanager is not initiating a scan of available networks - missing permissions or is it just lazy?
No idea what triggers a scan, apparently mine is not doing one when it comes out of suspend and stubbornly tries to connect to a now out-of-reach network (but thats for another thread).

That was what I was dancing around, but failed to articulate.

Avant-texte has a good point that I had not considered. I'll spend some time on this tonight. In the mean time, I might suggest to those fighting this try forcing a scan with iwlist and see what happens.

Strike0 · 2012-02-27 22:52:44

@ewaller: What is your chipset?

I think it may be a mixing of issues here, since Pitou/OP is using ath9k and the original dmesg shows a connect (via nm), but frequent disconnects upon a full update. Further the iwconfig shows connect rate of 1MB/s, i.e. connection is breaking down most likely right at that moment.

The problems with NM not scanning only happened to OP after that downgrade of NM.

I would point to the driver as well in OP's case same as avant-texte, thats why the suggestion to try dis-configuring hardware crypto or try the LTS kernel.
Pity really those ath9k issues since the chipset is great capability-wise.

ewaller · 2012-02-27 23:18:40

Strike0 wrote:

@ewaller: What is your chipset?
I think it may be a mixing of issues here, since Pitou/OP is using ath9k and the original dmesg shows a connect (via nm), but frequent disconnects upon a full update.

It is Broadcom. You may be right that we are mixing issues, and I most definitely don't want to hijack a thread (lest I anger the moderators ) On the other hand, it is not inconceivable that different chip sets, and their drivers, react differently to a common root cause. As I said, I'll play with it tonight and see what I find. I'll report back with results, will qualify them as being associated with a different chip set, and see if they help here. If I don't get any satisfaction in my experiments, I'll start a new thread and link back here.

Pitou · 2012-02-28 00:34:56

Just tried with no encryption and it's the same.....

helloworld1 · 2012-02-28 07:00:08

Intel wireless card has the same issue. I am using netcfg to connect to Internet now. So it must be networkmanager's issuem not kernel's.

cedricmc · 2012-02-28 09:56:09

Quoting myself from Network Manager Applet broken after upgrade

cedricmc wrote:

As told, few days ago, after a system upgrade, the gnome network applet stop to work properly and I had to downgrade networkmanager and libnl form 0.9.2.0-2 and 3.2.7-1 to 0.9.2.0-1 and 1.1-3, respectively. This solved my ethernet connection but not the wireless one.
Yesterday, I fully updated the system again, and everything seems to work properly. I think I will never know what was the exact problem. I will have to sleep with that

BTW, my wireless adapter is a RaLink 2860 (on an Asus Eee PC 901).

Avant-texte · 2012-02-28 12:30:57

Pitou wrote:

Just tried with no encryption and it's the same.....

How about with IPv6 dissabled?

Arch Linux

#1 2012-02-25 02:03:21

[SOLVED] Since networkmanager upgrade wifi dowsn't connect anymore

#2 2012-02-25 06:33:37

Re: [SOLVED] Since networkmanager upgrade wifi dowsn't connect anymore

#3 2012-02-25 12:36:36

Re: [SOLVED] Since networkmanager upgrade wifi dowsn't connect anymore

#4 2012-02-25 20:54:55

Re: [SOLVED] Since networkmanager upgrade wifi dowsn't connect anymore

#5 2012-02-26 02:13:47

Re: [SOLVED] Since networkmanager upgrade wifi dowsn't connect anymore

#6 2012-02-26 02:18:52

Re: [SOLVED] Since networkmanager upgrade wifi dowsn't connect anymore

#7 2012-02-26 10:05:56

Re: [SOLVED] Since networkmanager upgrade wifi dowsn't connect anymore

#8 2012-02-26 12:27:02

Re: [SOLVED] Since networkmanager upgrade wifi dowsn't connect anymore

#9 2012-02-26 12:57:47

Re: [SOLVED] Since networkmanager upgrade wifi dowsn't connect anymore

#10 2012-02-27 17:52:27

Re: [SOLVED] Since networkmanager upgrade wifi dowsn't connect anymore

#11 2012-02-27 18:00:27

Re: [SOLVED] Since networkmanager upgrade wifi dowsn't connect anymore

#12 2012-02-27 18:23:53

Re: [SOLVED] Since networkmanager upgrade wifi dowsn't connect anymore

#13 2012-02-27 19:06:12

Re: [SOLVED] Since networkmanager upgrade wifi dowsn't connect anymore

#14 2012-02-27 20:56:03

Re: [SOLVED] Since networkmanager upgrade wifi dowsn't connect anymore

#15 2012-02-27 21:11:09

Re: [SOLVED] Since networkmanager upgrade wifi dowsn't connect anymore

#16 2012-02-27 21:11:17

Re: [SOLVED] Since networkmanager upgrade wifi dowsn't connect anymore

#17 2012-02-27 21:19:30

Re: [SOLVED] Since networkmanager upgrade wifi dowsn't connect anymore

#18 2012-02-27 21:34:13

Re: [SOLVED] Since networkmanager upgrade wifi dowsn't connect anymore

#19 2012-02-27 22:00:52

Re: [SOLVED] Since networkmanager upgrade wifi dowsn't connect anymore

#20 2012-02-27 22:52:44

Re: [SOLVED] Since networkmanager upgrade wifi dowsn't connect anymore

#21 2012-02-27 23:18:40

Re: [SOLVED] Since networkmanager upgrade wifi dowsn't connect anymore

#22 2012-02-28 00:34:56

Re: [SOLVED] Since networkmanager upgrade wifi dowsn't connect anymore

#23 2012-02-28 07:00:08

Re: [SOLVED] Since networkmanager upgrade wifi dowsn't connect anymore

#24 2012-02-28 09:56:09

Re: [SOLVED] Since networkmanager upgrade wifi dowsn't connect anymore

#25 2012-02-28 12:30:57

Re: [SOLVED] Since networkmanager upgrade wifi dowsn't connect anymore

Board footer