You are not logged in.
After updating NetworkManager to 1.0.0-1, my wifi constantly disconnects and reconnects after waking from suspend (or from a fresh reboot). My dmesg looks like this:
[ 1694.315432] cfg80211: Calling CRDA to update world regulatory domain
[ 1694.689630] wlp1s0: authenticate with 9c:d3:6d:99:2d:6b
[ 1694.691673] wlp1s0: send auth to 9c:d3:6d:99:2d:6b (try 1/3)
[ 1694.693807] wlp1s0: authenticated
[ 1694.695560] wlp1s0: associate with 9c:d3:6d:99:2d:6b (try 1/3)
[ 1694.704455] wlp1s0: RX AssocResp from 9c:d3:6d:99:2d:6b (capab=0x411 status=0 aid=12)
[ 1694.706197] wlp1s0: associated
[ 1697.461998] wlp1s0: deauthenticating from 9c:d3:6d:99:2d:6b by local choice (Reason: 3=DEAUTH_LEAVING)
[ 1697.496482] cfg80211: Calling CRDA to update world regulatory domain
[ 1698.182307] cfg80211: Calling CRDA to update world regulatory domain
[ 1698.392173] cfg80211: Calling CRDA to update world regulatory domain
[ 1698.508530] cfg80211: Calling CRDA to update world regulatory domain
[ 1700.673705] cfg80211: Calling CRDA to update world regulatory domain
[ 1700.975692] cfg80211: Calling CRDA to update world regulatory domain
[ 1701.276617] wlp1s0: authenticate with 9c:d3:6d:99:2d:6b
[ 1701.278491] wlp1s0: send auth to 9c:d3:6d:99:2d:6b (try 1/3)
[ 1701.283057] wlp1s0: authenticated
[ 1701.286369] wlp1s0: associate with 9c:d3:6d:99:2d:6b (try 1/3)
[ 1701.290597] wlp1s0: RX AssocResp from 9c:d3:6d:99:2d:6b (capab=0x411 status=0 aid=12)
[ 1701.291695] wlp1s0: associated
but repeated a lot. This will sometimes happen once or twice and sometimes goes on for minutes before it finally connects.
Googling leads to a thread that suggests disabling the dhcpcd service, which didn't help, and reloading modules with an explicit regulatory domain, which also didn't help. Any suggestions?
Last edited by astex (2015-02-07 15:32:02)
Offline
To me this sounds like a power management issue. Try disabling power management and see if the problem persists.https://wiki.archlinux.org/index.php/Wi … onnections
Offline
Actually, the problem seems to be that netctl enabled itself at boot after a recent update, so a simple `systemctl disable netctl` seems to have solved it. I'll report back if the problem persists.
Last edited by astex (2015-02-02 18:12:59)
Offline
I was wrong. This problem persists with netctl disabled. There just weren't any connection problems for a few tries. The power management status of the card has no effect. Netctl works fine, so this seems to be a problem with NetworkManager specifically.
Offline