Re: Doesn't always work after resume

[Dan Williams <dcbw redhat com>]

On Sun, 2006-08-13 at 13:18 +0200, Stian Jordet wrote:
> s�3,.08.2006 kl. 00.03 -0400, skrev Pat Suwalski:
> > 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?
> 
> Nope, doesn't help to uncheck and recheck wireless. And as I said, my
> neighbour's net is always there. 
> 
> When NetworkManager doesn't find my net, I can use "Connect to another
> wireless network" (or something, freely translated from Norwegian) and
> tell it my SSID and WEB-key, and it works. So the problem is that it
> doesn't find it by itself...
> 
> Might sound like an issue with my AP, but it's working fine with OS X
> and Windows everytime.

It may well be ipw2200; though here for me it seems to work fine after
resume.  What kernel version are you using, what version of the ipw2200
drivers, and what version of the ieee80211 kernel stack?  If you look
through the output of 'dmesg' you should be able to find the last two.

For me:
ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.1.2kmprq
ieee80211: 802.11 data/management/control stack, git-1.1.13

Linux localhost.localdomain 2.6.17-1.2532.fc6 #1 SMP Tue Aug 8 20:42:18
EDT 2006 i686 i686 i386 GNU/Linux

Bill Moss has also reported some driver-based stupidity in ipw2200 where
it automatically attempts to find and connect to access points on its
own by default.  You might try having modprobe load the ipw2200 module
with those bits set off.  For example, see #2 here:

http://mail.gnome.org/archives/networkmanager-list/2006-July/msg00159.html

Dan