Network Resume Dance

I learned this little dance while Network Manager was having a problem with sleep and resume. Bringing my laptop out of sleep always had problems getting networking again. Network Manager would die upon resume so this is how I would get my wireless card (iwl3945) to return after resuming from sleep. I’m looking forward to not running this all the time…

[clarkbw@localhost ~]$ sudo /etc/init.d/NetworkManager restart

Stopping NetworkManager daemon:                            [FAILED]

Setting network parameters...

Starting NetworkManager daemon:                            [  OK  ]

[clarkbw@localhost ~]$ sudo /etc/init.d/NetworkManager stop

Stopping NetworkManager daemon:                            [  OK  ]

Now wait about 10 seconds…

[clarkbw@localhost ~]$ sudo /etc/init.d/NetworkManager start

Setting network parameters...

Starting NetworkManager daemon:                            [  OK  ]

[clarkbw@localhost ~]$

About this entry

You’re currently reading “Network Resume Dance,” an entry on Bryan Clark

Published:: 11.01.07 / 9am

Category:: NetworkManager

5 Comments

Jump to comment form | comments rss [?] | trackback uri [?]

Chris Lord November 1, 2007

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 :))
Jeremy Katz November 1, 2007

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.
dgoodwin November 4, 2007

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.
Jay November 5, 2007

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
Suspend/Resume with linux laptops « Keystone IT Tech March 2, 2008

[...] 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 [...]

Comment Guidelines

Hyperlinks are automatically generated.
<em>italic</em>
<strong>bold</strong>

Monthly Archives

About

My name is Bryan Clark, I’m a User Experience Designer working with Mozilla Messaging on Thunderbird; currently living in the Boston area. I have interests in design, economics, architecture, and beer. Previous to my work with Mozilla I was one of a select few Interaction Designers at Red Hat, working on their Desktop Team, OLPC, GNOME, Online Desktop and many other projects.

This blog focuses mainly on my work driving design in an open source context.

Bryan Clark

Network Resume Dance

About this entry

5 Comments

Post a Comment »

Comment Guidelines

Categories

Monthly Archives

Recent Comments

About

Recently