Quoting Dan Williams <[EMAIL PROTECTED]>:
> NM is likely to be very unhappy if you just suspend it, and wireless
> drivers in general have issues with suspend. There really is no method
> for NM to know when you've put the computer to sleep since nothing sends
> global events out (PowerManager+HAL will eventually do this the Right
> Way using dbus).
I already fixed the device issue in my acpi scripts.. I ifdown the interface
manually and then rmmod all the device modules (I have no idea why "modprobe
-r" doesn't DWIW). This seems to work fine as far as the module itself is
concerned.
> NM does have a "sleep" dbus method that will make NM stop and down all
> devices, and a "wake" method to wake it up. Those should be able to be
> done in the ACPI scripts fairly simply:
Ooh, this is useful to know. Is this documented somewhere? I'll try this and
see if it works. Thanks!
> /usr/bin/dbus-send --system --dest=org.freedesktop.NetworkManager
> --type=method-call /org/freedesktop/NetworkManager
> org.freedesktop.NetworkManager.sleep
> sleep 5;
>
> and:
>
> /usr/bin/dbus-send --system --dest=org.freedesktop.NetworkManager
> --type=method-call /org/freedesktop/NetworkManager
> org.freedesktop.NetworkManager.wake
>
> Dan
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
[EMAIL PROTECTED] PGP key available
_______________________________________________
NetworkManager-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/networkmanager-list
