[Bug 133963] Re: Cannot re-connect using NetworkManager and ndiswrapper after resume
most drivers should be fixed by drivers in hardy. if you still cannot reconnect with ndiswrapper with network-manager 0.6.6-0ubunt5, please reopen this bug (as Incomplete) and attach your complete /var/log/syslog taken after a failed connect attempt. Thanks! ** Changed in: network-manager (Ubuntu) Status: Confirmed = Fix Released -- Cannot re-connect using NetworkManager and ndiswrapper after resume https://bugs.launchpad.net/bugs/133963 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133963] Re: Cannot re-connect using NetworkManager and ndiswrapper after resume
Same here. Kubuntu 7.10 final, Intel 3945 -- unable to reconnect after suspend/hibernate. The only case when it is able to reconnect is when the duration of the suspend is only a few seconds. -- Cannot re-connect using NetworkManager and ndiswrapper after resume https://bugs.launchpad.net/bugs/133963 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133963] Re: Cannot re-connect using NetworkManager and ndiswrapper after resume
** Changed in: network-manager (Ubuntu) Status: Incomplete = Confirmed -- Cannot re-connect using NetworkManager and ndiswrapper after resume https://bugs.launchpad.net/bugs/133963 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133963] Re: Cannot re-connect using NetworkManager and ndiswrapper after resume
OK, we did some improvements in latest network-manager/wpasupplicant. would be cool if you could test with http://cdimage.ubuntu.com/daily/current/ and attach the /var/log/syslog if it still fails. ** Changed in: network-manager (Ubuntu) Status: Confirmed = Incomplete -- Cannot re-connect using NetworkManager and ndiswrapper after resume https://bugs.launchpad.net/bugs/133963 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133963] Re: Cannot re-connect using NetworkManager and ndiswrapper after resume
Have tested with gutsy live DVD downloaded on Sept 8, and seems OK. Cannot test suspend/resume as have no room to install gutsy, and cannot suspend with live DVD. As I could not suspend gutsy, I tested by using /etc/dbus-1/event.d/25NetworkManager to stop NetworkManager (which seemed to have no effect on gutsy, but stopped NWM on feisty), and removed ndiswrapper module. I checked the module was actually removed, and then reversed the procedure, and could reconnect using knetworkmanager. This procedure could not reconnect on feisty using ndiswrapper, only worked if used bcm43xx module. It could be done repeatedly for either bcm43xx or ndiswrapper on gutsy. Looking at syslog on feisty, it seems NWM starts dhclient before wpa_supplicant has finished connecting after a resume, but not at boot. Is there some way to remove any cached information so it would think it was doing a boot rather than a resume? -- Cannot re-connect using NetworkManager and ndiswrapper after resume https://bugs.launchpad.net/bugs/133963 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133963] Re: Cannot re-connect using NetworkManager and ndiswrapper after resume
** Changed in: network-manager (Ubuntu) Status: Incomplete = Confirmed -- Cannot re-connect using NetworkManager and ndiswrapper after resume https://bugs.launchpad.net/bugs/133963 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133963] Re: Cannot re-connect using NetworkManager and ndiswrapper after resume
do you have a chance to test this on latest gutsy? ** Changed in: network-manager (Ubuntu) Status: New = Incomplete ** Changed in: network-manager (Ubuntu) Importance: Undecided = Medium -- Cannot re-connect using NetworkManager and ndiswrapper after resume https://bugs.launchpad.net/bugs/133963 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133963] Re: Cannot re-connect using NetworkManager and ndiswrapper after resume
I have unmarked this as a duplicate of 38329 as it is about ndiswrapper using the Broadcom windows driver not about using the bcm43xx driver. Additionally, I am going to assign this to the networkmanager package. ** This bug is no longer a duplicate of bug 38329 bcm43xx needs manual treatment after resume -- Cannot re-connect using NetworkManager and ndiswrapper after resume https://bugs.launchpad.net/bugs/133963 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133963] Re: Cannot re-connect using NetworkManager and ndiswrapper after resume
I have unmarked this as a duplicate of 38329 as it is about ndiswrapper using the Broadcom windows driver not about using the bcm43xx driver. Additionally, I am going to assign this to the networkmanager package. ** Changed in: network-manager (Ubuntu) Sourcepackagename: None = network-manager -- Cannot re-connect using NetworkManager and ndiswrapper after resume https://bugs.launchpad.net/bugs/133963 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133963] Re: Cannot re-connect using NetworkManager and ndiswrapper after resume
*** This bug is a duplicate of bug 38329 *** https://bugs.launchpad.net/bugs/38329 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 38329, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can add, or to see if there is a workaround for the bug. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 38329 bcm43xx needs manual treatment after resume -- Cannot re-connect using NetworkManager and ndiswrapper after resume https://bugs.launchpad.net/bugs/133963 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133963] Re: Cannot re-connect using NetworkManager and ndiswrapper after resume
*** This bug is a duplicate of bug 38329 *** https://bugs.launchpad.net/bugs/38329 This does not seem to be a duplicate of 38329 (and the other bugs also marked as duplicates of 38329), because they all report problems with the bcm43xx driver. I usually have no problems with suspend/resume etc of the bcm43xx driver (except for the limit of 11Mbps speed). This bug is a problem with using the ndiswrapper bcmwl5 driver to try and use the bcm43.. chip at full speed. Using ndiswrapper does not use the bcm43xx driver. -- Cannot re-connect using NetworkManager and ndiswrapper after resume https://bugs.launchpad.net/bugs/133963 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
