|{urse
November 27th, 2008, 05:55 PM
Hi there. I'm having this really odd problem with NetworkManager under Gutsy (no, i don't want to to upgrade to hardy or intrepid) Anyways, NetworkManager will use a ridiculous amount of cpu. top usually reports it using anywhere from 50 - 100 percent at times. It seems this only happens when i lose signal. For some reason when NetworkManager gets this out of hand i can only kill it like this:
#!/bin/bash
gksudo killall NetworkManager
gksudo killall nm-applet
gksudo NetworkManager
nm-applet
xmessage -center "Hi, `whoami`. Click the button." -buttons "Restart NM":0]
gksudo iwconfig ath0 essid "linksys" || gksudo iwconfig ath0 essid "Jayhawk"
exit
by the way.. linksys is never weak enough that the script has to resort to the Jayhawk essid. However, when i start this box the normal way with the default gutsy session my connection to linksys is tenuous at best.
I'm not usually one to write scripts for such simple things but for some odd reason this is the only way i can get the wireless working again once it has "died". It may also help to note that restarting the networkmanager via dbus (sudo /etc/dbus-1/event.d/25NetworkManager restart) does not help. the situation at all.
There are only 2 reasonably strong signals nearby but i know they arent weak enough to cause NetworkManager to have to reconnect constantly. Any help would be much appreciated and thanks in advance ^^
#!/bin/bash
gksudo killall NetworkManager
gksudo killall nm-applet
gksudo NetworkManager
nm-applet
xmessage -center "Hi, `whoami`. Click the button." -buttons "Restart NM":0]
gksudo iwconfig ath0 essid "linksys" || gksudo iwconfig ath0 essid "Jayhawk"
exit
by the way.. linksys is never weak enough that the script has to resort to the Jayhawk essid. However, when i start this box the normal way with the default gutsy session my connection to linksys is tenuous at best.
I'm not usually one to write scripts for such simple things but for some odd reason this is the only way i can get the wireless working again once it has "died". It may also help to note that restarting the networkmanager via dbus (sudo /etc/dbus-1/event.d/25NetworkManager restart) does not help. the situation at all.
There are only 2 reasonably strong signals nearby but i know they arent weak enough to cause NetworkManager to have to reconnect constantly. Any help would be much appreciated and thanks in advance ^^