![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=409110
User david@picella.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=409110#c2
David Picella
Ok. Just to make sure i get it right:
- suspend to RAM kills the network. - if you manually do dbus-send --system \ --dest=org.freedesktop.NetworkManager \ /org/freedesktop/NetworkManager \ org.freedesktop.NetworkManager.wake after resume, network works again. - if you disable /usr/lib/pm-utils/sleep.d/10NetworkManager, network also does not work after resume - if you additionally unload ndiswrapper during suspend, it works again.
Is this correct?
Not exactly.
How are you invoking suspend to RAM? via gnome-power-manager, kpowersave
I can invoke s2ram from the command line or from kpowersave (usually I use kpowersave). I cannot bring the wireless network back online after resume. I can sleep and wake the network just fine from the terminal using dbus-send. I can also unload and load the network module from the command line without any issues. It is only when s2ram is performed that I can't get the wireless network back. Once I have fully resumed, I can unload and load ndiswrapper with modprobe and then things are restored, but I have to do this manually. Hope that makes sense ! ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.