1. Adding max_replies_per_connection=512 to /etc/dbus-1/system.d/NetworkManager.conf
2. Adding dbus suspend/resume scripts (with varying priorities) as per John Cooper's post
3. Disabling Wireless Networking from the nm-applet prior to suspending
Doing a suspend/resume cycle whilst running NetworkManager --no-daemon reports:
NetworkManager: <information> Activation (eth1) successful, device activated.
NetworkManager: <information> Activation (eth1) Finish handler scheduled.
NetworkManager: <information> Activation (eth1) Stage 5 of 5 (IP Configure Commit) complete.
NetworkManager: <information> wpa_supplicant(6706): cess=1
NetworkManager: <information> Going to sleep.
sendmsg(CTRL_IFACE monitor): No such file or directory
NetworkManager: <debug info> [1183921757.754011] nm_hal_device_removed (): Device removed (hal udi is '/org/freedesktop/Hal/devices/net_00_13_a9_86_51_bd').
NetworkManager: <information> Deactivating device eth2.
NetworkManager: <information> Waking up from sleep.
NetworkManager: <information> Deactivating device eth1.
NetworkManager: <WARNING> nm_device_802_11_wireless_set_essid (): error setting ESSID to '' for device eth1: Resource temporarily unavailable
NetworkManager: <WARNING> nm_device_802_11_wireless_set_wep_enc_key (): error setting key for device eth1: Resource temporarily unavailable
NetworkManager: <WARNING> nm_device_802_11_wireless_get_mode (): error getting card mode on eth1: Resource temporarily unavailable
NetworkManager: <WARNING> nm_device_802_11_wireless_set_mode (): error setting card eth1 to Infrastructure mode: Resource temporarily unavailable
** net_00_13_a9_86_51_bd is the wired interface (not in use).
Stopping and restarting NetworkManager (as daemon or not) will start the network and connect successfully if NetworkManager was running as --nodaemon during suspend.
Feisty 32-bit, 2.6.20-16-generic with ipw3945 and e100 on a Sony Vaio VGN-FE41Z.
Using just the ipw3945 wireless connection on a WPA2 network.
After resume from suspend NetworkManager reported no network devices. Restarting NetworkManager didn't seem to solve it.
The solution was to use mlaverdiere's method dated 2006-07-05 to stop NetworkManager during suspend and start it during resume:
https:/ /bugs.launchpad .net/ubuntu/ +source/ network- manager/ +bug/40125/ comments/ 43
These methods all failed to solve the issue:
1. Adding max_replies_ per_connection= 512 to /etc/dbus- 1/system. d/NetworkManage r.conf
2. Adding dbus suspend/resume scripts (with varying priorities) as per John Cooper's post
3. Disabling Wireless Networking from the nm-applet prior to suspending
Doing a suspend/resume cycle whilst running NetworkManager --no-daemon reports:
NetworkManager: <information> Activation (eth1) successful, device activated. 6706): cess=1 device_ removed (): Device removed (hal udi is '/org/freedeskt op/Hal/ devices/ net_00_ 13_a9_86_ 51_bd') . 802_11_ wireless_ set_essid (): error setting ESSID to '' for device eth1: Resource temporarily unavailable 802_11_ wireless_ set_wep_ enc_key (): error setting key for device eth1: Resource temporarily unavailable 802_11_ wireless_ get_mode (): error getting card mode on eth1: Resource temporarily unavailable 802_11_ wireless_ set_mode (): error setting card eth1 to Infrastructure mode: Resource temporarily unavailable
NetworkManager: <information> Activation (eth1) Finish handler scheduled.
NetworkManager: <information> Activation (eth1) Stage 5 of 5 (IP Configure Commit) complete.
NetworkManager: <information> wpa_supplicant(
NetworkManager: <information> Going to sleep.
sendmsg(CTRL_IFACE monitor): No such file or directory
NetworkManager: <debug info> [1183921757.754011] nm_hal_
NetworkManager: <information> Deactivating device eth2.
NetworkManager: <information> Waking up from sleep.
NetworkManager: <information> Deactivating device eth1.
NetworkManager: <WARNING> nm_device_
NetworkManager: <WARNING> nm_device_
NetworkManager: <WARNING> nm_device_
NetworkManager: <WARNING> nm_device_
** net_00_ 13_a9_86_ 51_bd is the wired interface (not in use).
Stopping and restarting NetworkManager (as daemon or not) will start the network and connect successfully if NetworkManager was running as --nodaemon during suspend.