[Expired for bcmwl (Ubuntu) because there has been no activity for 60
days.]
** Changed in: bcmwl (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/956
KJ Tsanaktsidis, could you please provide the missing information
following
https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx#Broadcom_STA_Wireless_driver
?
** Changed in: bcmwl (Ubuntu)
Importance: Undecided = Low
** Changed in: bcmwl (Ubuntu)
Status: Confirmed = Incomplete
@Adam,
OK. Let's do one thing. If brcmsmac works for you, then be happy and
forget about bcmwl. Meaning don't touch any bcmwl-related bug, as, as
I've repeteadly said, forcing users to use brcmsmac will not, by
definition, solve any bug in bcmwl, just as this one.
Nobody forces you to use bcmwl.
Bernardo,
Yes, as I've said in other reports we've discussed, I verified that
brcmsmac works with the BCM4313 card.
Unless there are other problems with brcmsmac and BCM4313 cards, users
should uninstall bcmwl and use brcmsmac. If there are other problems,
we need to get those bugs filed. Our
Adam,
Pleas read the first post again. Have YOU verified that this bug is
fixed with drivers other than bcmwl?
THIS bug report is about BCM4313 *and* bwmcl ignoring ARP broadcast
packets. If you think other drivers solve this bug, then please kindly
post this as a workaround in a comment, but do
Bernardo,
You should not undo my marking of the bug without explaining your
reasoning. Your own report suggests that most likely this bug has been
fixed on Precise with current versions of the kernel package and bcmwl
package. It may also be fixed on Precise with the in-tree driver, which
may
** This bug is no longer a duplicate of bug 1097519
Wrong driver used for older Broadcom chipsets
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/956
Title:
BCM4313 ignores ARP broadcast
*** This bug is a duplicate of bug 1097519 ***
https://bugs.launchpad.net/bugs/1097519
** This bug has been marked a duplicate of bug 1097519
Wrong driver used for older Broadcom chipsets
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Hi,
It works fine with Kubuntu 13.04 using kernel 3.8.0.19 (bcmwl-kernel-
source_6.30.223.30+bdcom-0ubuntu1~ppa1_i386).
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/956
Title:
Just for extra verification: could any of the affected people test if
the new bcmwl version (6.30.*) works OK?
The version here https://launchpad.net/~albertomilone/+archive/broadcom
is now (I think) in precise-proposed. Should work with any kernel up to
3.8.x.
(I'm on precise now with mainline
I have a BCM4313 and am running Kubuntu 12.04.02.
Until today I've been using the lts-quantal kernel (3.5.0-27 and
3.5.0-28 from -proposed) with bcmwl-kernel-source_6.20.155.1+bdcom-
0ubuntu0.0.1_amd64.deb (precise-updates).
Today I've installed the kernel from linux-generic-lts-raring
It seems that this may be related to the wireless encryption. If I
connect to an open (unencrypted) network, I can receive broadcast ARPs.
On a WPA2 network, I cannot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
Just for information (no for controversy), I've encountered the same problem
under Ubuntu 12.04 with linux kernel 3.2.0-37-generic-pae.
I've just removed the broadcom-sta-common and installed the package
broadcom-sta-dkms 5.100.82.112-8.deb from the Debian Wheezy distribution and
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bcmwl (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/956
Title:
Yes, exactly the same problem here. I used wireshark to trace down the problem.
It seems that the broadcom driver simply ignores broadcasts. Everything has
been very fine for quite a long time (years ?). Now it's broken!
What should we do now? It's a proprietary driver as I understand. So will
I'm also experiencing this problem with a netbook on my LAN. I can no
longer access it through SSH, but it can access its own SSH server and
use internet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I tried to run apport-collect but the machine doesn't have a GUI, and
the OAuth process fails in links. Let me know what other information is
needed!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
17 matches
Mail list logo
