Old access points after suspend/resume with BCM4328, wl wireless driver; can't connect to new APs

Bug #484883 reported by Nilbus
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
wl (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: wl

The wl driver for my BCM4328 card was working perfectly for me in Jaunty.

Since my fresh Karmic install, after a resume, nm-applet always shows old access points from the location where I had suspended.
It tries to connect to the old access point, and fails. Access points in the new location are visible, but if you try to connect before the old access point times out, it will not connect to the new AP.

Sometimes, it cannot connect to new access points at all. In my limited experience, it will only connect to secure access points after a resume in a new location. It has no problems connecting to access points that it knew about before suspend, secured or not.

According to this blog
http://blogs.gnome.org/dcbw/2009/02/26/suspendresume-vs-networkmanager/
This is a problem with the wl driver, not network-manager.

I'd be glad to help debug this issue, if I could have some guidance.

ProblemType: Bug
Architecture: amd64
Date: Wed Nov 18 10:58:02 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: wl
Package: wl (not installed)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: wl
Uname: Linux 2.6.31-14-generic x86_64

Revision history for this message
Nilbus (nilbus) wrote :
Revision history for this message
Nilbus (nilbus) wrote :

Turns out this was bug #264683 showing its head again.

Revision history for this message
Tony Espy (awe) wrote :

I disagree that this is a duplicate of bug #264683, instead I'm almost certain that this is a duplicate of bug #452571 which is caused by a combination of a bug in the 'wl' driver and a bug in network-manager.

I'm going to go ahead and change it, please let me know if there's any disagreement with this decision.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.