Comments on: Network Resume Dance

By: Suspend/Resume with linux laptops « Keystone IT Tech

Suspend/Resume with linux laptops « Keystone IT Tech — Sun, 02 Mar 2008 18:34:07 +0000

[...] latest Nvidia driver. The wifi (Intel 3945) driver needs to be reset after resuming. I adapted a script I found and connected it to a launcher on the panel. echo “Resetting Network” sudo [...]

By: Jay

Jay — Mon, 05 Nov 2007 20:44:11 +0000

Bryan,
I’ve been there too. I have a script in ~/bin/re_wifi (contents below… and yes it doesn’t work w/o the sleeps). I don’t need it as much as I used to but when I go from work (LEAP) to Home (WPA) it’s a requirement. I found I had to go back all the way to “network” so it would unload the wireless driver, but I did notice recently that the Dispatcher seems to do something similar.
FWIW, this is on a RHEL5. system. I’m going to F8 as soon as I get a chance.

sudo /etc/init.d/NetworkManagerDispatcher stop
sleep 5
sudo /etc/init.d/NetworkManager stop
sleep 5
sudo /etc/init.d/network stop
sleep 5
sudo /etc/init.d/ipw3945d stop
sleep 45
sudo /etc/init.d/ipw3945d start
sleep 5
sudo /etc/init.d/network start
sleep 5
sudo /etc/init.d/NetworkManager start
sleep 5
sudo /etc/init.d/NetworkManagerDispatcher start

By: dgoodwin

dgoodwin — Sun, 04 Nov 2007 22:24:06 +0000

Thanks for this, I was having the same problem with iwl3945 and thought I was running into a brick wall with restarting services, nothing seemed to get that wifi back up. Waiting 10 seconds was the key.

By: Jeremy Katz

Jeremy Katz — Thu, 01 Nov 2007 17:09:54 +0000

You really shouldn’t need to be unloading the module or restarting NetworkManager. The only little quirk I’ve got right now with iwl3945 on resume is that (sometimes) wpa_supplicant is keeping its cached scan results around. But after 30 seconds or so, it realizes that I’ve gone home and finds the other network.

And now that the brunt of F8 is out of the way, I might actually get around to prodding at wpa_supplicant to make it forget things too.

By: Chris Lord

Chris Lord — Thu, 01 Nov 2007 15:29:53 +0000

I also have an Intel wireless chipset and I found that whitelisting the module (in Ubuntu, see /etc/default/acpi-support) works well and NetworkManager only needs to be restarted when you resume as it doesn’t refresh the networks quick enough (none of this stop start stop wait start nonsense :))