Wireless slow to reconnect after suspend and resume -- wl

[Craig Marshall]

Binary package hint: network-manager

I'm using Maverick Meerkat Alpha 3, as fully updated as possible (it wouldn't update libgirepository, due to some kind of duplication).

When I suspend then resume my laptop (A x86-64 Dell 1764), it refuses to connect to the wireless or even see any wireless networks for a good 30+ seconds, in Windows 7 on the same machine with the same wireless card, it will reconnect within 2-4 seconds after a resume.

Here's my Ubuntu release:

Description: Ubuntu maverick (development branch)
Release: 10.10

And here's my network-manager version:

network-manager:
  Installed: 0.8.1+git.20100810t184654.ab580f4-0ubuntu1
  Candidate: 0.8.1+git.20100810t184654.ab580f4-0ubuntu1
  Version table:
 *** 0.8.1+git.20100810t184654.ab580f4-0ubuntu1 0
        500 http://gb.archive.ubuntu.com/ubuntu/ maverick/main amd64 Packages
        100 /var/lib/dpkg/status

What I expected to happen:

Should be able to reconnect to the wireless after a suspend within about 5 seconds. Otherwise it's not worth suspending, it's just as quick to reboot (where the wireless connects much more quickly).

What happened instead:

It took around 35 seconds to reconnect, although earlier today it took over 1 minute, so it clearly varies.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: network-manager 0.8.1+git.20100810t184654.ab580f4-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-15.21-generic 2.6.35.1
Uname: Linux 2.6.35-15-generic x86_64
NonfreeKernelModules: wl
Architecture: amd64
CRDA: Error: [Errno 2] No such file or directory
Date: Thu Aug 19 09:28:59 2010
IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100803.1)
IpRoute:
 192.168.0.0/24 dev eth1 proto kernel scope link src 192.168.0.6 metric 2
 169.254.0.0/16 dev eth1 scope link metric 1000
 default via 192.168.0.1 dev eth1 proto static
Keyfiles: Error: [Errno 2] No such file or directory
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
RfKill:
 0: dell-wifi: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: network-manager

[mlaverdiere (mlaverdiere)]

Same thing hereon Maverick, using a Broadcom BCM4312 802.11b/g, card and the wl driver.

[nerdy_kid (nerdy-kid)]

I have a BCM4312 802.11b/g LP-PHY (rev 01) card that gave me similar problems with the wl driver: my wireless would take about 20 seconds to resume on wake from suspend. What I have done is manually edit /usr/lib/pm-utils/sleep.d/55NetworkManager config. Mine now looks like the attached. I have disabled the dbus calls to network manager on sleep/resume. It works nicely with my router, have left the laptop off all night and had it resume connected instantly. With my workaround network manager does not kill the connection on suspend and it does not request a new IP address on resume, so I have no idea how this will behave working with multiple networks. Hope it helps someone :)

[mlaverdiere (mlaverdiere)]

nerdy_kid: your workaround is working great while network is not changing between sleep & resume cycle. I did a test with a network change, and NM is keeping the failed connection with the down network forever... To establish a connection with the new available network, wireless network must be deactivated/reactivated using NM panel icon. I'll see if I can fine tune this... Don't hold your breath!

[mlaverdiere (mlaverdiere)]

Just want to report that while using nerdy-kid workaround and contrary to my previous report, network change/adaptation seems to work (sometimes, at least). That's what I experienced yesterday when I put my laptop to sleep at home and then resume at the university. Network-manager has graciously and pretty quickly connected to the univ. network, instead of keeping my unavailable home network registered as connected. I'll do some more tests and report if anything new.

[nerdy_kid (nerdy-kid)]

It does seem that Gmail with Chrome (7.0.517.44) does not like this workaround one bit, it will freeze (gmail that is) with a "loading" message until I request a new IP and reload gmail.com.

[nerdy_kid (nerdy-kid)]

If someone would give me a tip on how to ask NetworkManager for a new IP from dbus that would be great. Trying to improve my workaround.

[Jorge Eduardo (jorge-birck)]

Try this:

dbus-send --system --type=method_call --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.DBus.Properties.Set string:org.freedesktop.NetworkManager string:WirelessEnabled variant:boolean:false

dbus-send --system --type=method_call --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.DBus.Properties.Set string:org.freedesktop.NetworkManager string:WirelessEnabled variant:boolean:true

[nerdy_kid (nerdy-kid)]

That doesn't work, it still takes it like 20 secs to recognize it.
 Currently I am messing with dhclient, and have fixed the issue with gmail
that I mentioned previously. I am now using "dhclient &" in the resume
function, and it has been working fine.

On Tue, Dec 28, 2010 at 12:14 PM, Jorge Eduardo
<email address hidden>wrote:

> Try this:
>
> dbus-send --system --type=method_call
> --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager
> org.freedesktop.DBus.Properties.Set
> string:org.freedesktop.NetworkManager string:WirelessEnabled
> variant:boolean:false
>
> dbus-send --system --type=method_call
> --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager
> org.freedesktop.DBus.Properties.Set
> string:org.freedesktop.NetworkManager string:WirelessEnabled
> variant:boolean:true
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/620318
>
> Title:
> Wireless slow to reconnect after suspend and resume
>
> Status in “network-manager” package in Ubuntu:
> New
>
> Bug description:
> Binary package hint: network-manager
>
> I'm using Maverick Meerkat Alpha 3, as fully updated as possible (it
> wouldn't update libgirepository, due to some kind of duplication).
>
> When I suspend then resume my laptop (A x86-64 Dell 1764), it refuses to
> connect to the wireless or even see any wireless networks for a good 30+
> seconds, in Windows 7 on the same machine with the same wireless card, it
> will reconnect within 2-4 seconds after a resume.
>
> Here's my Ubuntu release:
>
> Description: Ubuntu maverick (development branch)
> Release: 10.10
>
> And here's my network-manager version:
>
> network-manager:
> Installed: 0.8.1+git.20100810t184654.ab580f4-0ubuntu1
> Candidate: 0.8.1+git.20100810t184654.ab580f4-0ubuntu1
> Version table:
> *** 0.8.1+git.20100810t184654.ab580f4-0ubuntu1 0
> 500 http://gb.archive.ubuntu.com/ubuntu/ maverick/main amd64
> Packages
> 100 /var/lib/dpkg/status
>
> What I expected to happen:
>
> Should be able to reconnect to the wireless after a suspend within about 5
> seconds. Otherwise it's not worth suspending, it's just as quick to reboot
> (where the wireless connects much more quickly).
>
> What happened instead:
>
> It took around 35 seconds to reconnect, although earlier today it took over
> 1 minute, so it clearly varies.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 10.10
> Package: network-manager 0.8.1+git.20100810t184654.ab580f4-0ubuntu1
> ProcVersionSignature: Ubuntu 2.6.35-15.21-generic 2.6.35.1
> Uname: Linux 2.6.35-15-generic x86_64
> NonfreeKernelModules: wl
> Architecture: amd64
> CRDA: Error: [Errno 2] No such file or directory
> Date: Thu Aug 19 09:28:59 2010
> IfupdownConfig:
> auto lo
> iface lo inet loopback
> InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64
> (20100803.1)
> IpRoute:
> 192.168.0.0/24 dev eth1 proto kernel scope link src 192.168.0.6
> metric 2
> 169.254.0.0/16 dev eth1 scope link metric 1000
> default via 192.168.0.1 dev eth1 proto static
> Keyfiles: Error: [Errno 2] No such file or directory
> ProcEnviron:
> LANG=en_GB.UTF-8
>...

[Richard Bailey (bailey937)]

I have a Dell Inspiron Mini 10V and was having the problem with having to wait 30 seconds to get reconnected to my wifi AP after resuming.

I'm always suspending and resuming in the same place.

I'm running 10.10 now and had the problem in 10.04 LTS also.

The workaround mentioned above (commenting out the lines in /usr/lib/pm-utils/sleep.d/55NetworkManager) works for me. Thanks!

[nerdy_kid (nerdy-kid)]

This is my current config, it has given me no problems so far -- been using
it for a couple months. There is about a 5 second delay while the IP
address is updated, but it should work nicer with multiple access points (I
think)

On Fri, Feb 4, 2011 at 6:46 AM, Richard Bailey <email address hidden>wrote:

> I have a Dell Inspiron Mini 10V and was having the problem with having
> to wait 30 seconds to get reconnected to my wifi AP after resuming.
>
> I'm always suspending and resuming in the same place.
>
> I'm running 10.10 now and had the problem in 10.04 LTS also.
>
> The workaround mentioned above (commenting out the lines in /usr/lib/pm-
> utils/sleep.d/55NetworkManager) works for me. Thanks!
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/620318
>
> Title:
> Wireless slow to reconnect after suspend and resume
>
> Status in “network-manager” package in Ubuntu:
> New
>
> Bug description:
> Binary package hint: network-manager
>
> I'm using Maverick Meerkat Alpha 3, as fully updated as possible (it
> wouldn't update libgirepository, due to some kind of duplication).
>
> When I suspend then resume my laptop (A x86-64 Dell 1764), it refuses
> to connect to the wireless or even see any wireless networks for a
> good 30+ seconds, in Windows 7 on the same machine with the same
> wireless card, it will reconnect within 2-4 seconds after a resume.
>
> Here's my Ubuntu release:
>
> Description: Ubuntu maverick (development branch)
> Release: 10.10
>
> And here's my network-manager version:
>
> network-manager:
> Installed: 0.8.1+git.20100810t184654.ab580f4-0ubuntu1
> Candidate: 0.8.1+git.20100810t184654.ab580f4-0ubuntu1
> Version table:
> *** 0.8.1+git.20100810t184654.ab580f4-0ubuntu1 0
> 500 http://gb.archive.ubuntu.com/ubuntu/ maverick/main amd64
> Packages
> 100 /var/lib/dpkg/status
>
> What I expected to happen:
>
> Should be able to reconnect to the wireless after a suspend within
> about 5 seconds. Otherwise it's not worth suspending, it's just as
> quick to reboot (where the wireless connects much more quickly).
>
> What happened instead:
>
> It took around 35 seconds to reconnect, although earlier today it took
> over 1 minute, so it clearly varies.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 10.10
> Package: network-manager 0.8.1+git.20100810t184654.ab580f4-0ubuntu1
> ProcVersionSignature: Ubuntu 2.6.35-15.21-generic 2.6.35.1
> Uname: Linux 2.6.35-15-generic x86_64
> NonfreeKernelModules: wl
> Architecture: amd64
> CRDA: Error: [Errno 2] No such file or directory
> Date: Thu Aug 19 09:28:59 2010
> IfupdownConfig:
> auto lo
> iface lo inet loopback
> InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64
> (20100803.1)
> IpRoute:
> 192.168.0.0/24 dev eth1 proto kernel scope link src 192.168.0.6
> metric 2
> 169.254.0.0/16 dev eth1 scope link metric 1000
> default via 192.168.0.1 dev eth1 proto static
> Keyfiles: Error: [Errno 2] No such file or directory
> ProcEnviron:
> LANG=en_GB.UTF-8
> SHELL=/bin/bash
> RfKill:
> 0: dell-wifi: Wireless LAN
> ...

[zpletan (zpletan)]

@everyone, does this have anything to do with bug #708776?

[nerdy_kid (nerdy-kid)]

zpletan, that sounds exactly like my issue.

[mu3en (mu3en)]

most solutions failed here, however:

changing the last part in /usr/lib/pm-utils/sleep.d/55NetworkManager

from
  thaw|resume)¶
     resume_nm¶

to
  thaw|resume)¶
    resume_nm¶
    sleep 2 && iwlist eth1 scanning &

forces a wifi scan and network manager connects almost immediately after resume.

[nerdy_kid (nerdy-kid)]

Upgrading to natty solved this for me.

On Sat, Apr 30, 2011 at 7:22 PM, mu3en <email address hidden> wrote:

> most solutions failed here, however:
>
> changing the last part in /usr/lib/pm-utils/sleep.d/55NetworkManager
>
> from
> thaw|resume)¶
> resume_nm¶
>
> to
> thaw|resume)¶
> resume_nm¶
> sleep 2 && iwlist eth1 scanning &
>
> forces a wifi scan and network manager connects almost immediately after
> resume.
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/620318
>
> Title:
> Wireless slow to reconnect after suspend and resume
>
> Status in “network-manager” package in Ubuntu:
> New
>
> Bug description:
> Binary package hint: network-manager
>
> I'm using Maverick Meerkat Alpha 3, as fully updated as possible (it
> wouldn't update libgirepository, due to some kind of duplication).
>
> When I suspend then resume my laptop (A x86-64 Dell 1764), it refuses
> to connect to the wireless or even see any wireless networks for a
> good 30+ seconds, in Windows 7 on the same machine with the same
> wireless card, it will reconnect within 2-4 seconds after a resume.
>
> Here's my Ubuntu release:
>
> Description: Ubuntu maverick (development branch)
> Release: 10.10
>
> And here's my network-manager version:
>
> network-manager:
> Installed: 0.8.1+git.20100810t184654.ab580f4-0ubuntu1
> Candidate: 0.8.1+git.20100810t184654.ab580f4-0ubuntu1
> Version table:
> *** 0.8.1+git.20100810t184654.ab580f4-0ubuntu1 0
> 500 http://gb.archive.ubuntu.com/ubuntu/ maverick/main amd64
> Packages
> 100 /var/lib/dpkg/status
>
> What I expected to happen:
>
> Should be able to reconnect to the wireless after a suspend within
> about 5 seconds. Otherwise it's not worth suspending, it's just as
> quick to reboot (where the wireless connects much more quickly).
>
> What happened instead:
>
> It took around 35 seconds to reconnect, although earlier today it took
> over 1 minute, so it clearly varies.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 10.10
> Package: network-manager 0.8.1+git.20100810t184654.ab580f4-0ubuntu1
> ProcVersionSignature: Ubuntu 2.6.35-15.21-generic 2.6.35.1
> Uname: Linux 2.6.35-15-generic x86_64
> NonfreeKernelModules: wl
> Architecture: amd64
> CRDA: Error: [Errno 2] No such file or directory
> Date: Thu Aug 19 09:28:59 2010
> IfupdownConfig:
> auto lo
> iface lo inet loopback
> InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64
> (20100803.1)
> IpRoute:
> 192.168.0.0/24 dev eth1 proto kernel scope link src 192.168.0.6
> metric 2
> 169.254.0.0/16 dev eth1 scope link metric 1000
> default via 192.168.0.1 dev eth1 proto static
> Keyfiles: Error: [Errno 2] No such file or directory
> ProcEnviron:
> LANG=en_GB.UTF-8
> SHELL=/bin/bash
> RfKill:
> 0: dell-wifi: Wireless LAN
> Soft blocked: no
> Hard blocked: no
> SourcePackage: network-manager
>
> To unsubscribe from this bug, go to:
>
> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/620318/+subscribe
>

[mu3en (mu3en)]

modification as posted above was necessary on fresh natty install here. otherwise still took 20~30s or manual 'iwlist scanning' to make connection, down to 5~10s using above.

[josh duran (rubbersoul-josh)]

i'm on a 2010 MBA and was having the same problems. it's nearly instant when running windows or osx, but took many seconds for ubuntu.

i've tried the mu3en workaround above, and this has cleared it up for me. wireless scans immediately after resume and connects seconds later.

[oliver (oliver-schinagl)]

Not sure if this affects me, but since upgrading from 10.10 to 12.04 (fresh install though) I find wifi to be quite slow in reconnecting.

I think it is due to the new, more secre, password entry dialog box when waking maybe? I know there was some talk about being able to bypass the screenlock. I notice there is a new screenlock now and after entering my password, it takes about 1-2 seconds to start connecting.

Before, on 10.10, this probably happend the moment it returned from resume, so the moment I was done entering my password everything was nearly or allready up and running.

Would that be a new bug report? Or is that similar to this one.

[Thomas Hood (jdthood)]

NonfreeKernelModules: wl