Bugzilla – Bug 328011
networkmanager does not reconnect on suspend/resume
Last modified: 2007-09-29 20:09:10 UTC
I have a ipw3945 wireless card. When I resume from S2R, all ESSID's are gone from the ist in knetworkmanager. After I restart the networkstack (rcnetwork restart) it will autoconnect again, based on the info in kwallet (I think). This is a continuation of the bugreport summary in bug 326906.
OK, I've investigated a bit further in the refusal of networkmanager to reconnect on resume. First, could it have anything to do with bug 310509. Second, if I do a "rcnetwork restart" it reconnects. It seems the dbus call in /usr/lib/pm-utils/sleep.d/10NetworkManager doesn't seem to doing anything. I've executed the same command on the commandline. Nothing happened. Here is a excerp from /var/log/pm-suspend.log: ===== Thu Sep 20 23:18:47 CEST 2007: running hook: /usr/lib/pm-utils/sleep.d/10NetworkManager ===== ===== Thu Sep 20 23:18:47 CEST 2007: running hook: /usr/lib/pm-utils/sleep.d/06autofs ===== ===== Thu Sep 20 23:18:47 CEST 2007: running hook: /usr/lib/pm-utils/sleep.d/05led ===== ===== Thu Sep 20 23:18:47 CEST 2007: running hook: /usr/lib/pm-utils/sleep.d/01logging ===== ===== Thu Sep 20 23:18:47 CEST 2007: running hook: /usr/lib/pm-utils/sleep.d/00clear ===== Thu Sep 20 23:18:47 CEST 2007: done running resume hooks.
When I run the dbus command from 10NetworkManager from the commenct prompt nothing happens. I don't get any response from it. I also patched 10Networkmanager: I added a "rcnetwork restart" statement in the resume logic. It did not help, but doing the same from the command line does help... Is this a timing thingie?
ipw3945 bug, pretty sure this is a dupe.
Oke, i'm a but further with this. I noticed nm-tool didn't even see the wireless adapter, so it had to be a driver issue. I've added the ipw3945 module driver to /usr/lib/pm-utils/default like so: SUSPEND_MODULES="ipw3945" (I know it's the wrong place, but I thought it could hurd for a quick test :-). Things are a little easier now. The driver and it's dependency get unloaded at suspend and loaded at resume. I see a list of ESSID's again in knetworkmanager and nm-tool sees the wireless adapter again. However, it does _not_ reconnect on it's own, I have to choose my ESSID manually. So now the behaviour at startup and at resume are basically the same. Wireless up and running, kwallet has all the info, but it will _not_ autoconnect.
O, I forgot. If I quit and restart knetworkmanager after resume in the above situation it _does_ autoconnect. Is there a way to give (k)networkmanager a notice to connect to a ESSID from the CLI?
This is a dup of bug 232420. From there I saw the mention of using s2ram. suspending using s2ram is very successfull! It resume's and the connection doesn't even need to be re-established, it just works again!
*** This bug has been marked as a duplicate of bug 232420 ***