Comment 4 for bug 274405

OK, thanks for this info.

Anybody else using iwl3945 that experience (or not) this problem?

Jeffrey Baker <email address hidden> wrote:

> On Fri, Sep 26, 2008 at 5:02 AM, Marc Jauvin <email address hidden> wrote:
>
>> According to 'modinfo iwl3945', the default is scanning enabled, and I
>> don't see anywhere that overrides this, so I would think this is not
>> the case. Do you have an easy way to check this?
>>
>
> You would know if it was disabled, because you have to do it manually.
>
> I asked because I had long n-m wait to associate in Hardy, but it's instant
> in Intrepid i.e. basically the opposite of your problem. I suspect this bug
> is in iwl3945, not in n-m.
>
> --
> network manager slow to reconnect after suspend/resume
> https://bugs.launchpad.net/bugs/274405
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “network-manager-applet” source package in Ubuntu: New
>
> Bug description:
> Binary package hint: network-manager-gnome
>
> On my Thinkpad T61 with Intel 3945abg (iwl3945 driver), Network
> Manager usually takes around 1 minute before trying to reconnect to
> my WiFi router. I noticed that if I run the following command:
>
> # iwlist eth1 scan
>
> Network Manager seems to "wake-up" right after the scan is complete
> and connects right away.
>
> Would there be a way to send a signal upon resume that would trigger
> the same "wake-up" call?
>
> *** I'm running Intrepid Ibex updated multiple time a day.
>

--
Marc Jauvin
514-905-6500
http://register4less.com