No WIFI autoconnect - neither after resume nor dropped connection
Bug #578334 reported by
tomlaunch
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
wicd |
New
|
Undecided
|
Unassigned |
Bug Description
Running on ubuntu Lucid (10.4)
Even after editing the path in /etc/acpi/ resume.d to
/usr/share/
To post a comment you must log in.
I seem to have a similar problem.
After resume, wicd doesn't reconnect to the wifi network.
I've got Samsung N140 + Kubuntu 10.4 + wicd 1.7.0
After a bit of investigation, I've noticed that the order of resume scripts seem to be wrong. pm-utils/ sleep.d/
This is the order I have in /usr/lib/
55NetworkManager 75modules 91wicd
The "75modules" script is responsible for stopping and starting kernel modules defined in the SUSPEND_MODULES list. Including my wifi card driver.
Now, the above order is for suspending, the resume order is reverse.
So the wicd is resumed BEFORE the wifi module is even started.
As an experiment, I've reordered scripts by renaming 91wicd to 55wicd and it worked perfectly.
The strange thing is that I checked the logs and this script WAS called 55wicd some time ago but then renamed to 91wicd on 2009-07-28 by Adam Blackburn. Could not find any explanations though. Does anyone remember what was the reason?
From resume order point of view, the wicd suspend/resume script should be called XXwicd where XX < 75, so that it starts reconnecting after the modules are ready.
I'd say that 55wicd is actually the best choice because it reuses the same spot as 55NetworkManager. Even though I know that wicd is the best, there are many more people that use NM. So other projects are likely to position their suspend/resume scripts relative to 55NetworkManager. If wicd reuses the same position, those projects will automatically work with wicd as well.