Finally found the root reason of the problem! :-) Both wl (broadcom proprietary driver) and brcmsmac (the open source driver) are installed, in 11.10 this wasn't a problem since the brcmsmac was not blacklisted, and even if the wl driver was loaded, it failed silently and brcmsmac was used instead.
In 12.04, the wl driver has been updated to version 5.100.82.38+bdcom- 0ubuntu6.1 which includes the following fix: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/873117/comments/36 that basically blacklists the brcmsmac module, forcing the wl proprietary driver to be in use. When the wl driver is in use, resume takes 30 seconds to associate to the network, but when the brcmsmac driver is in use, it just takes 5 seconds. I just blacklisted the 'wl' module, and happily using the brcmsmac now in 12.04, without any issues. Problem solved! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/994739 Title: wireless takes several seconds longer to connect from standby Status in Linux WPA/WPA2/IEEE 802.1X Supplicant: New Status in “network-manager” package in Ubuntu: Confirmed Bug description: My observation is that network-manager is taking longer to connect to my wireless access point than 11.10. I trust the rest of the attached info will reveal all necessary system data. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-24.38-generic-pae 3.2.16 Uname: Linux 3.2.0-24-generic-pae i686 NonfreeKernelModules: wl nvidia ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Fri May 4 12:47:28 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) IpRoute: default via 192.168.1.1 dev eth1 proto static 169.254.0.0/16 dev eth1 scope link metric 1000 192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.116 metric 2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 1 264165e3-74f6-4750-8198-6e8b6d3632cf 802-3-ethernet 1336133356 Fri 04 May 2012 07:09:16 AM CDT yes no /org/freedesktop/NetworkManager/Settings/1 2.4GHzWPA2 9afe3092-8693-4b03-92cd-fd179af0fca8 802-11-wireless 1336153624 Fri 04 May 2012 12:47:04 PM CDT yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth1 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernet unavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0 connected enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/wpasupplicant/+bug/994739/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp