** Changed in: linux-source-2.6.15 (Ubuntu)
Status: Confirmed => Invalid
--
bcm43xx needs manual treatment after resume
https://bugs.launchpad.net/bugs/38329
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing l
** Changed in: acpi-support (Ubuntu)
Status: New => Invalid
--
bcm43xx needs manual treatment after resume
https://bugs.launchpad.net/bugs/38329
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bu
This bug may be related to bug #119563
--
bcm43xx needs manual treatment after resume
https://bugs.launchpad.net/bugs/38329
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://
I am currently using Gutsy final with the Feisty kernel, since Gutsy's
kernel broke suspend to RAM on powerpc. This works fine, so I'm closing
this bug.
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Incomplete => Fix Released
--
bcm43xx needs manual treatment after resume
https://bu
Hey Martin, can you confirm if this is still an issue in the 7.10 Gutsy
Gibbon release? Thanks!
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: New => Incomplete
--
bcm43xx needs manual treatment after resume
https://bugs.launchpad.net/bugs/38329
You received this bug notification be
** Also affects: linux-source-2.6.20 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: acpi-support (Ubuntu)
Importance: Undecided
Status: New
--
bcm43xx needs manual treatment after resume
https://bugs.launchpad.net/bugs/38329
You received this bug notification bec
** Changed in: linux-source-2.6.15 (Ubuntu)
Status: New => Confirmed
--
bcm43xx needs manual treatment after resume
https://bugs.launchpad.net/bugs/38329
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
I have a similar problem with an HP NX6125 laptop
I use NetworkManager, and sometimes I can solve it right-clicking it and
disabling and reenabling the wireless network.
Sometimes though I really have to reload the bcm43xx kernel module for it to
work again.
--
bcm43xx needs manual treatment af
this seems like it might be related to bug #54092 and I've got the same
issue as cyrilo on an hp laptop. I can connect fine, using the bcm43xx
module and wpa_supplicant. I close the laptop screen, putting the
machine to sleep. When I open it back up, network manager claims to be
connected, but
