Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed with some of the updates. It would help us a lot if
you could test it on a currently supported Ubuntu version. When you test
it and it is still an issue, kindly upload the updated logs by running
apport-collect 359827 and any other logs that are relevant for this
particular issue.
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/359827
Title:
network manager unreliable with broadcom 4315 wireless
Status in “network-manager” package in Ubuntu:
Incomplete
Bug description:
Binary package hint: network-manager
tittle@anathema:~$ lsb_release -rd
Description: Ubuntu jaunty (development branch)
Release: 9.04
tittle@anathema:~$ apt-cache policy network-manager
network-manager:
Installed: 0.7.1~rc4.1.cf199a964-0ubuntu1
Candidate: 0.7.1~rc4.1.cf199a964-0ubuntu1
Version table:
*** 0.7.1~rc4.1.cf199a964-0ubuntu1 0
500 http://us.archive.ubuntu.com jaunty/main Packages
100 /var/lib/dpkg/status
tittle@anathema:~$ lspci | grep Broadcom
04:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g (rev 01)
tittle@anathema:~$ lspci -n | grep '14e4:43'
04:00.0 0280: 14e4:4315 (rev 01)
Here is what happened:
1) I installed 9.04 rc1 and the wireless worked out of the box, until
it dropped connection and reconnected. At that point, it continually
asked for a WEP key and after that no matter how many times I verified
it, it came back and asked for WEP until eventually gave up. After
that, no matter how i rebooted, etc, it would not recognize any
available wireless.
2) So I installed 8.10. This never was able to use the wireless at
all. NM acted like there were never any wireless to detect, even tho
the various listings lspci, dmesg, etc all looked normal (and the
proprietary broadcom driver was available & activated). In short,
same as above after a reboot. So.
3) In desperation, I reinstalled 9.04...Same deal. It worked for a
couple of hours, but then dropped & reconnected and went into WEP
PLZKTHX mode. So I uninstalled NM and put in wicd. Played with that,
but wasn't perfectly happy with it, and so reinstalled Network
manager, but this time went straight into NM and TURNED OFF THE
AUTOCONNECT. Since then, for several days, it has worked perfectly.
I just need to take the additional step of telling it to, yes, connect
to this wireless router instead of letting the puppy think on its own.
WILD SPECULATION ON MY PART: NM is fucking up one or more of its
configuration files, that are correct at the time of installing the
operating system, in some fashion when it is in autoconnect mode. I
have tarballed my current configuration files in case it goes belly up
again and will compare, if this happens.
ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
IfupdownConfig:
auto lo
iface lo inet loopback
Package: network-manager 0.7.1~rc4.1.cf199a964-0ubuntu1
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: network-manager
Uname: Linux 2.6.28-11-generic i686
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/359827/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
