Tribe 5 seems to have fixed the issue. Now, the wireless either
completely works or completely doesn't. When it does not work, it is
simply a problem with the ipw3945 daemon not being started. This only
occurs when I boot into a -386 kernel image, as I don't have a -386
ipw3945 daemon. The -gen
Fixed via network-manager.
** Changed in: linux-restricted-modules-2.6.22 (Ubuntu)
Status: New => Invalid
--
[ipw3945] wpasupplicant gusty takes a long time to associate
https://bugs.launchpad.net/bugs/123188
You received this bug notification because you are a member of Ubuntu
Bugs, whic
We worked around this by unsetting essid right before trying to connect:
network-manager (0.6.5-0ubuntu9) gutsy; urgency=low
* debian/patches/series: disable 41o_completely_deactivate_stage1.patch
for tribe-4
-- Alexander Sack <[EMAIL PROTECTED]> Tue, 7 Aug 2007 12:36:37 +0200
#
with unsetting essid before trying to connect it works pretty fast. I
guess its the driver so i reject the wpasupplicant task
** Changed in: wpasupplicant (Ubuntu)
Status: Incomplete => Invalid
--
[ipw3945] wpasupplicant gusty takes a long time to associate
https://bugs.launchpad.net/bugs
network-manager 0.6.5-0ubuntu9 should fix wpa for ipw3945 ... if it
doesn't for you please let us know.
--
[ipw3945] wpasupplicant gusty takes a long time to associate
https://bugs.launchpad.net/bugs/123188
You received this bug notification because you are a member of Ubuntu
Bugs, which is the b
Hi,
apparently we found a workaround for one variant of this bug:
"unset essid manually using iwconfig before connecting."
Can you try if this helps for you as well?
Thanks,
- Alexander
--
[ipw3945] wpasupplicant gusty takes a long time to associate
https://bugs.launchpad.net/bugs/123188
