Re: BUG: NM only connects the third time

On Sun, 2007-11-04 at 00:31 +0100, Eric Brunet lps ens fr wrote:
> > The problem here is that the card is powered down during suspend or
> > hibernate.  When the card is down, it looses the association, and you
> > have to go back through the entire connection process anyway, just get
> > association, authenticate, and get an address back.
> Ha, that's not true on my laptop [Dell D430 with an Intel Corporation
> PRO/Wireless 3945ABG Network Connection (rev 02)]. I have disabled the
> script /usr/lib/pm-utils/sleep.d/10NetworkManager, so that NM doesn't get
> the suspend/wake methods, and I enjoy instantly my wifi connexion on
> resume. [I  checked in the log that NM doesn't do anything during the
> suspend/resume].
> Maybe my card is not properly shut down and I spend more power than
> needed during sleep...

If you hibernate, sleep, or ifdown the device, then the card should
certainly be powering down, and the association should be lost.  Perhaps
the driver keeps the parameters of the last association around across
the suspend/resume, but that's quite error prone, and the driver still
needs to do a scan to find the AP again.  NM isn't going to rely on the
driver re-associating, and the re-association certainly won't work _at
all_ when using WPA or Dynamic WEP because a userspace supplicant is


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]