Agreed Petr. I did a little more digging earlier today and managed to get scan results immediately after resuming from suspend. When I can get physical access to my AP to reset the WPA2 key, which I've forgotten as I let the Gnome keyring remember it for me, I'll verify whether or not I'm able to actually get wireless connectivity without NM -- I think that is what you're suggesting is possible. If that is indeed the case, I wonder if some event isn't getting through to notify NM of the b43 interface availability after resume.
Running NM and NMDispatcher in no-daemon mode, then modprobe -r b43 followed by modprobe b43, I see no output from NMD, but NM gives: NetworkManager: <debug> [1207433187.131214] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/net_00_0e_9b_d3_ce_d0'). NetworkManager: <debug> [1207433187.156125] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/ssb__null_'). NetworkManager: <debug> [1207433202.221719] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/ssb__null_'). NetworkManager: <debug> [1207433202.252308] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/net_00_0e_9b_d3_ce_d0'). I'm not sure which way it's supposed to work, but it looks to me like NMD is responsible for calling /etc/network/if-up.d via /etc/NetworkManager/dispatcher.d/01ifupdown in response to NM interface events. I'm guessing somehow NMD isn't getting the interface events through. -- NetworkManager stops working for wireless after going to sleep (both ram and disk) [newest Hardy; b43] https://bugs.launchpad.net/bugs/209970 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
