14.04 same thing WIFI won't come back after suspend... Editing /etc/pm/config.d/config with the "SUSPEND_MODULES="your_driver_here"" in my case rtl8192ce.... used to work now its not working at all. After every suspend it seems to be unable to disconnect. The last time WIFI worked at this point was 11.04.... Is anyone reading these??? Why does the below Authenticate and then fail ???? HELP PLEASE I DON't WANT TO RESTART my computer every time I use it....
[ 2014.937326] rtl8192ce: Using firmware rtlwifi/rtl8192cfw.bin [ 2015.173101] cfg80211: Ignoring regulatory request Set by core since the driver uses its own custom regulatory domain [ 2015.173438] ieee80211 phy0: Selected rate control algorithm 'rtl_rc' [ 2015.174204] rtlwifi: wireless switch is on [ 2016.710890] r8169 0000:09:00.0: eth0: link down [ 2016.711525] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 2017.076669] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 2017.080772] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 2028.174542] wlan0: authenticate with 14:d6:4d:23:76:ee [ 2028.515770] wlan0: send auth to 14:d6:4d:23:76:ee (try 1/3) [ 2028.520460] wlan0: authenticated [ 2043.997218] wlan0: authenticate with 14:d6:4d:23:76:ee [ 2044.339577] wlan0: send auth to 14:d6:4d:23:76:ee (try 1/3) [ 2044.540065] wlan0: send auth to 14:d6:4d:23:76:ee (try 2/3) [ 2044.556494] wlan0: authenticated ** Attachment added: "DMESG from WIFI problems in terminal" https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+attachment/4087330/+files/WIFI_problem -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in NetworkManager: New Status in wicd: New Status in “systemd-shim” package in Ubuntu: Confirmed Status in “systemd-shim” source package in Saucy: Confirmed Status in “systemd-shim” source package in Trusty: Confirmed Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1252121/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
