Network Manager stops connecting after suspend

Questions about Wi-Fi and other network devices, file sharing, firewalls, connection sharing etc
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
Lunestic

Network Manager stops connecting after suspend

Post by Lunestic »

When I turn on my computer and log on, the Network Manager automatically and almost instantly connects to my WiFi. However, if I suspend Linux Mint and resume, the Network Manager is no longer connected. There is the "attempting to connect" (made-up name) spinner next to my WiFi's name, but it never ends up connecting.

I'm fairly certain the problem is with Linux Mint, not my WiFi.



My connection when it works (when laptop is turned on, no suspend suspend):

Code: Select all

$ sudo /usr/lib/linuxmint/mintWifi/mintWifi.py
-------------------------
* I. scanning WIFI PCI devices...
  -- Intel Corporation Centrino Wireless-N 2230 (rev c4)
      ==> PCI ID = 8086:0887 (rev c4)
-------------------------
* II. querying ndiswrapper...
-------------------------
* III. querying iwconfig...
eth0      no wireless extensions.

lo        no wireless extensions.

wlan0     IEEE 802.11bgn  ESSID:"BigTiger"  
          Mode:Managed  Frequency:2.427 GHz  Access Point: 20:AA:4B:71:61:EF   
          Bit Rate=90 Mb/s   Tx-Power=16 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=35/70  Signal level=-75 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:558  Invalid misc:192   Missed beacon:0

-------------------------
* IV. querying ifconfig...
eth0      Link encap:Ethernet  HWaddr a0:b3:cc:44:f1:e6  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:2175 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2175 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:236349 (236.3 KB)  TX bytes:236349 (236.3 KB)

wlan0     Link encap:Ethernet  HWaddr 68:5d:43:ab:c7:cd  
          inet addr:192.168.1.115  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::6a5d:43ff:feab:c7cd/64 Scope:Link
          inet6 addr: 2601:c:3380:843:68fb:60ab:71cd:243c/64 Scope:Global
          inet6 addr: 2601:c:3380:843:6a5d:43ff:feab:c7cd/64 Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:251258 errors:0 dropped:0 overruns:0 frame:0
          TX packets:161055 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:290624456 (290.6 MB)  TX bytes:25650938 (25.6 MB)

-------------------------
* V. querying DHCP...
-------------------------
* VI. querying nslookup google.com...
Server:		192.168.1.1
Address:	192.168.1.1#53

Non-authoritative answer:
Name:	google.com
Address: 74.125.228.40
Name:	google.com
Address: 74.125.228.38
Name:	google.com
Address: 74.125.228.32
Name:	google.com
Address: 74.125.228.46
Name:	google.com
Address: 74.125.228.34
Name:	google.com
Address: 74.125.228.35
Name:	google.com
Address: 74.125.228.41
Name:	google.com
Address: 74.125.228.33
Name:	google.com
Address: 74.125.228.37
Name:	google.com
Address: 74.125.228.39
Name:	google.com
Address: 74.125.228.36
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Top
slikriktn1
Level 1
Level 1
Posts: 1
Joined: Mon Dec 29, 2014 1:23 pm

Re: Network Manager stops connecting after suspend

Post by slikriktn1 »

I have the same problem and I have tried every method I can find and nothing resolves the issue.What I did find that is a work around without having to do a full reboot is this: type into terminal after waking computer sudo killall NetworkManager this has worked every time so far.
Top
wjvman
Level 1
Level 1
Posts: 3
Joined: Mon Dec 19, 2011 6:30 pm

Re: Network Manager stops connecting after suspend

Post by wjvman »

I have the same problem on my home-built desktop with a USB Wi-FI interface from TP-Link. After a suspend, the LED never comes back on when Linux is powered on after a Suspend. Linux Mint 16 and 17.1 both have the same problem.

I have booted Ubuntu 14 from a DVD, and it does not have a problem re-connecting after a Suspend, and neither does WinXp and Win7.

I know it is not a Wi-Fi problem, since three other OS's can Suspend/Re-Connect without disconnect and reconnect of the USB cable.

I have set up Boot Manager on my PC system with two hard drives, so I can boot in Linux Mint 17.1, WinXP or Win7.

I prefer Linux Mint over Ubuntu, but I have to unplug the USB connector to my TP-Link Wi-Fi, to force a re-connect after Suspending Linux Mint.
Top
Locked

Return to “Networking”