Bugzilla – Bug 256646
Network does not go up automaticly, after waking up from suspend to disk.
Last modified: 2007-09-26 09:26:44 UTC
This happens standard. Manualy it can get aktivated without any problems. AJ told me it has to come up automaticly, so it is a bug. Tell me what logs or info you need from me.
Please attach /var/log/NetworkManager, /var/log/messages and post output of 'nm-tool'. Is it a wireless or wired network?
nm-tool is unknown to bash.. Network is wired/wireless/dhcp/fixed ip-adresses. The PC where I noticed this is AMD64, wired.
Created attachment 126025 [details] networkmngr.log
Created attachment 126026 [details] messages.log
I have the same problem however some additional comments: On a Acer Travelmate 2403, with bcm43xx module, SUSPEND2DISK_RESTART_SERVICES = network, helped, and nm reconnects after resume. On a Dell Inspiron 8600c, with ipw2200, the same trick did not work, however using UNLOAD_MODULES_BEFORE_SUSPEND2DISK = ipw2200 , works. On both laptops traditional if-up method works fine, and reconnects to the same AP without any tricks. manually executing "/etc/pm/hooks/10NetworkManager resume" has no effect
I have a workaround, just create a script at /etc/pm/hooks/02network which restarts the network, something like this: cat at /etc/pm/hooks/02network #!/bin/sh . /etc/pm/functions resume_n() { /etc/init.d/network restart return $? } case "$1" in thaw|resume) resume_nm ;; *) ;; esac exit $?
If nobody makes an objection, i want to close this bug. In the RC1+ 10.3 these things work just fine.