Comment 4 for bug 60162

Thanks for the reply. It seems after the latest round of updates my
problem matches yours: wireless extensions are still there after
resume, and unloading and reloading the driver generally fixes things
and allows NM to recognize the wireless card again.

On 9/28/06, Mary Gardiner <email address hidden> wrote:
> For me, it is still listed as having a wireless extension even though NM
> lists two wired cards (this is why it can sometimes actually bring the
> so-called "wired" interface up -- the card associates even though NM
> doesn't even know it is wireless):
>
> eth1 unassociated ESSID:off/any
>
> I am not sure now if I was corrent in saying that restarting NM
> sometimes works. I usually unload and load my driver: "rmmod ipw2200;
> modprobe ipw2200"
>
> --
> Network manager sometimes gets the device type wrong
> https://launchpad.net/bugs/60162
>