Re: Doesn't always work after resume

["Robert G. Brown" <rgb phy duke edu>]

On Sun, 13 Aug 2006, Pat Suwalski wrote:

> Stian Jordet wrote:
> > I have a problem that NetworkManager often (but not always) don't find
> > my wireless network after a resume. It always works after a fresh boot,
> > it sometimes work after resume. It always finds my neighbours
> > unencrypted network everytime, but I don't know if my WEP-encryption
> > really has anything to do about it.
>
> I have a similar issue with madwifi. To work around it, I right-click on
> the applet and uncheck "Wireless" then recheck it. It seems to work
> afterwards.
>
> I wonder if that is the case on ipw as well?

Absolutely.  In fact, I've encountered a variety of "interesting" hangs
and errors when I suspend/resume a lot, including a message that I've
"exceeded the allowed number" of some resource and refusing to work at
all.  Other times it finds the network but ignores the key in the
keyring manager and prompts me for the key all over again.  When this
happens maybe half the time it ends up looping on this and never
getting a connection, sometimes it hooks right up after I enter a
password I shouldn't have had to enter.

I have a variety of ad hoc workarounds for the stuff I encounter along
these lines.  Disabling/reenabling wireless sometimes works.  Restarting
NetworkManager sometimes works.  Removing the ipw2200 kernel module and
re-inserting it (sandwiched by NetworkManager stop/start) sometimes
works.  Sometimes nothing works and I reboot (logging out and logging in
again usually don't seem to work).

I think that what I'm seeing is a variety of bugs at different levels --
in the ipw2200 driver (as sometimes re-initializing it altogether is
essential to success or there are messages in the log that lead me to
believe that it is having problems), in NM's interface, in the gnome
keyring (where you have to sometimes delete altogether a key that worked
fine for a week, re-insert it, and go into the manager interface and
re-enable it to work without a password).  Maybe in wpa_supplicant and
NM's back end stuff.  This is all pretty complex stuff.

It does seem to gradually be improving though.  I have periods of weeks
in a row where it just works, exactly the way it is supposed to, across
suspend/resume and all else.  I just dislike the non-deterministic/state
dependent nature of the crashes/failures, as they are really hard to
debug, and causes appear to be spread out over several layers of
responsibility at the software layer.

  rgb

> --Pat
> _______________________________________________
> NetworkManager-list mailing list
> NetworkManager-list gnome org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list

--
Robert G. Brown	                       http://www.phy.duke.edu/~rgb/
Duke University Dept. of Physics, Box 90305
Durham, N.C. 27708-0305
Phone: 1-919-660-2567  Fax: 919-660-2525     email:rgb phy duke edu