Can we get a title that describes better this bug?
If you are logged in, you can edit the title yourself. Just click the little
circle icon of a pencil to the right of the title.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Can we get a title that describes better this bug? Like bcmwl 6.20
update breaks for BCM4313? It isn't the wrong driver and should work
for this card.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sam Coffland's proposal from comment #29 seems to be the most sensible
IMHO. I also have a BCM4313 on my Acer Aspire One, which has been broken
with this upgraded wl.ko driver. brcmsmac is not an option for me since
it doesn't support ad-hoc mode, which I require.
--
You received this bug
So, after a bit of hacking around, I was able to get my BCM4313 working
with the latest bcmwl-6.30.223.30 and the latest kernel 3.10.0.
I think the main problem that I originally had, and that others
(
https://mail.gnome.org/archives/networkmanager-list/2013-February/msg00125.html
)
started
Lubuntu 12.04 kernel 3.2.0-48-generic.
I was getting the sys.log spammed by ERROR @wl_cfg80211.
I was using Broadcom Corporation BCM4321 for wireless and the driver
was wl: bcmwl-kernel-source.
I uninstalled everything that was installed and at
http://wireless.kernel.org/en/users/Drivers/b43
** Changed in: bcmwl (Ubuntu)
Assignee: (unassigned) = Alberto Milone (albertomilone)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097519
Title:
Wrong driver used for older Broadcom chipsets
The merger of Bug #1174145 into this group is inappropriate. This bug
appears to be related to getting brcmsmac selected by default, whereas
Bug #1174145 is related to a WLAN interference issue that popped up
between bcmwl-kernel-source versions 5.100.82.112+bdcom-0ubuntu3 shipped
with 12.10 and
OK. Perhaps it would be interesting to actually define what this
(1097519) bug is about. According to the first message, it's about using
the brcmsmac driver for the BCM4313 chip. No more, no less.
Now lots of other, unrelated, bugs (mostly bugs about the bcmwl driver)
have been merged into this
I had many problems with this wireless chip, because neither of
packages/modules from ubuntu repository didn't work well in my 3.8
kernel ubuntu 13.04. What I (finally) found useful was the compiling the
triver on my own, taken from broadcom's website. With the patches
described in the post
I agree with Bernado in comment #26. If this bug is campaign to get
brcmsmac installed by default, then
a) Bug #1160471 should not have been marked as a duplicate. Bug #1160471
is about v6.20.155.1 of the bcmwl drivers that was automatically
installed with Raring not working (causing kernel panic
I think the best solutions would be to pull the 6.20 BCMWL driver and
downgrade the official repos to the 5.100 BCMWL driver.
In the future do not roll out new Broadcom drivers until they have been
thoroughly tested by the community.
I do believe most if not all of these bug reports would
Besides the potential forever b43 debate.
Maybe we should make wl driver versioned as NVIDIA drivers now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097519
Title:
Wrong driver used for older
I have the 4312-LPHY chipset and the only way for me to get wifi to work
correctly and consistently is to install the bcmwl-kernel-source
package.
With kernel 3.7 and up all versions except bcmwl-kernel-
source_6.30.223.30+bdcom-0ubuntu1_amd64.deb gives me a kernel panic.
This made 13.04
On Mon, Jun 10, 2013 at 1:38 AM, Bernardo Reino
1097...@bugs.launchpad.net wrote:
@Adam Porter,
Please relax. You're making a whole mess of the entire bcmwl situation
because *you* think that the in-tree driver works OK for BCM4313, which
is (unfortunately) simply not true.
I know it works
Let me throw my Two cents in here. Adam I do appreciate your work on this
and so should everyone else. Reino please remember this is open source and
without people like Adam cleaning up these bugs and bring them into one
place we would not even be having this conversation as my bug report and
many
Sam, thanks for your encouraging words. I'm simply a user who ran
into a bug and had some free time to mess with the bug reports I
found. I expected a little random pushback, but I get too defensive
sometimes. Sometimes people (including myself) forget that we're all
working toward the same
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Adam Porter,
Please relax. You're making a whole mess of the entire bcmwl situation
because *you* think that the in-tree driver works OK for BCM4313, which
is (unfortunately) simply not true.
I'm astonished at how easy it is for ONE person to make such a mess of a
linux distribution.
--
You
And the regression was caused here: bug 923809
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097519
Title:
Wrong driver used for older Broadcom chipsets
To manage notifications about this bug go
P.S. This comment indicates a newer release may work with these older
chipsets, but it would probably be best to stick with the known-good
5.100.82.112 driver.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1110139/comments/45
--
You received this bug notification because you are a
I'm astonished at how many duplicates I'm finding of this bug. At its
core it goes back about three years, because Ubuntu's not automatically
switched to the broadcom-sta-* package for these chipsets, but remained
with bcmwl-kernel-source. Eventually bcmwl-kernel-source got bumped to
an upstream
Further reading of old bug reports suggests that for many the proper
solution is to simply uninstall all bcmwl-kernel-source and broadcom-
sta-* packages so that the in-tree driver will be used. e.g.
http://catlingmindswipe.blogspot.com.br/2012/07/broadcom-wireless-fix-
for-ubuntu-1210.html
--
Finally, bug 1134477 seems relevant. If that had been fixed, this might
have been too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097519
Title:
Wrong driver used for older Broadcom chipsets
And to confirm: removing bcmwl-kernel-source and broadcom-sta-source and
using the in-tree brcmsmac driver is working on my Acer Aspire One AO722
with BCM4313 chipset on Raring with the 3.8.0-23 kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Yes this is a work around but the brcmsmac is not as efficient, uses more
power and overall does not have nearly the throughput of the bcmwl. My work
around for 100+ Dell
Inspiron and Latitude laptops has been to ditch the Broadcom chip and
replace it with an Intel chip. The Centrino 6250 has
As I said many times, we need b43 (in tree driver) as an option for
u-d-c or jockey.
pitti, stop FUD about b43 and adopt it.
** Also affects: ubuntu-drivers-common (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
For the record, if you just unselect the bcmwl driver, ubuntu will use
b43. It's exactly similar to unselecting nvidia (then it will use
nouveau) or unselecting fglrx (then it will use ati).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
27 matches
Mail list logo
