sorry to revive an old bug but i have this similar functionality as
well. when suspending and moving to a new location, the network manager
tries to connect to the old AP until it asks for the password for it.
when canceled it will connect to new AP and old APs are gone from the
list. I am using
If I use the command sudo iwlist scanning, which I think uses the
driver to report networks, the network in question is _not_ reported.
--
NetworkManager attempts to connect to unavailable previously connected network
when resuming from suspend
https://bugs.launchpad.net/bugs/379201
You
In Karmic, kernel 2.6.31-17 and the wl wireless kernel module (BCM4328),
I still have this problem. I find that removing and re-inserting the
module (sudo rmmod wl; sudo modprobe wl) enables NetworkManager to work
properly, but then the system inevitably freezes within a few minutes.
--
It's not a networkmanager bug
Networkmanager gets its list of connections from the driver, and the
driver may report the old one to exist when in fact it doesn't. This is
a bug with specific drivers i think.
--
NetworkManager attempts to connect to unavailable previously connected network
awesome, marking this as fixed.
** Changed in: network-manager (Ubuntu)
Status: New = Fix Released
--
NetworkManager attempts to connect to unavailable previously connected network
when resuming from suspend
https://bugs.launchpad.net/bugs/379201
You received this bug notification
Definitely not a problem for me anymore.
--
NetworkManager attempts to connect to unavailable previously connected network
when resuming from suspend
https://bugs.launchpad.net/bugs/379201
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Seems like it's fixed on the new linux 2.6.31 in karmic. I will keep
testing going from school to home.
--
NetworkManager attempts to connect to unavailable previously connected network
when resuming from suspend
https://bugs.launchpad.net/bugs/379201
You received this bug notification because
For once today, this behavior did not occur for me. Using 2.6.30-9 with
karmic.
On Fri, Jun 12, 2009 at 3:34 PM, Michael
Marleymich...@michaelmarley.com wrote:
Yes, I thought about doing that, too. I probably will now. The problem
might be related to the Full-MAC drivers (like madwifi) vs
This happened to me on intrepid/jaunty/karmic when I switched to the
ath5k driver. I have this problem right now. I don't think it's
networkmanager's fault. It seems the previous connected network shows
up in the scanning list before real networks do, and then it doesn't go
away. I'm on a
I was using madwifi before, and i didn't have this problem. One
cumbersome workaround is to edit the pm-utils scripts to unload and
reload the ath5k module on resume. I did something similar for madwifi
for a different issue.
--
NetworkManager attempts to connect to unavailable previously
Yes, I thought about doing that, too. I probably will now. The problem
might be related to the Full-MAC drivers (like madwifi) vs the Soft-MAC
drivers (like ath5k and iwlagn).
--
NetworkManager attempts to connect to unavailable previously connected network
when resuming from suspend
11 matches
Mail list logo
