Comment 23 for bug 1097519

Revision history for this message
Sam Coffland (sam-truckmovers) wrote : Re: [Bug 1097519] Re: Wrong driver used for older Broadcom chipsets

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 more were scattered around and not generating any discussion.

That being said I do not like the brcmsmac driver and know for fact that it
is not nearly are good as the bcmwl driver. I have over 100 laptops with
the bcm4313 and bcm4312 chips. These all come out of the box with Windows 7
preinstalled. I wipe Windows when I deploy them with Ubuntu 12.04 LTS for
our users. The fully functioning bcmwl driver can reach speeds of up 10
Mbps the Windows driver can reach speeds of up to 12Mbps. The brcmsmac in
the same environment can only reach speeds of 2-3Mbps. It also uses much
more power draining the laptop battery takes longer to connect and does not
roam from AP to AP nearly as quick or efficiently. Installing
the 5.100.82.112 bcmwl driver from the multiverse is not an option in our
company enviorment so the best solutions has simple been to get rid of the
Broadcom chips.

I hope someone from Broadcom is reading this and anyone looking to buy a
laptop takes note of this do not waste your time with Broadcom chips as
they do not support the open source community. Support Intel as they
develop their driver's in the open and consistently release support Linux.
Broadcom may work for a while but you will eventually get bit as in this
instance when they update their drivers and drop support for older chips.

To the Ubuntu team these are the type of thing that we want you focused on
fixing not developing a splashier interface. If the network does not
connect it does not matter how many online retailers are integrated in the
the Dash. Make the basics work well first. If we must use proprietary
drivers test them before pushing them out as the vendors with putting these
out frankly don't care about the open source community.

Again Thanks Adam for all of your work on this.

---
*Sam Coffland*
Systems Administrator
TruckMovers.com, Inc.
<email address hidden>
816.878.6046 [phone]
http://truckmovers.com

On Tue, Jun 11, 2013 at 9:45 AM, Adam Porter <email address hidden>wrote:

> On Mon, Jun 10, 2013 at 1:38 AM, Bernardo Reino
> <email address hidden> 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 on my system because I verified it myself. I have a
> BCM4313 and it works perfectly for me. If this is not the case for
> you, explain. I did not claim that it's the best solution for
> everyone.
>
> > I'm astonished at how easy it is for ONE person to make such a mess of a
> > linux distribution.
>
> Really? So I've made a mess of the entire Ubuntu distro? By spending
> several hours cleaning up over 100 stale and duplicate bug reports on
> the bcmwl package? I cleaned up a major mess in one area but get
> blamed for making a mess of everything, everywhere. I guess I should
> have known better. No good deed goes unpunished. You're welcome.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1112924).
> https://bugs.launchpad.net/bugs/1097519
>
> Title:
> Wrong driver used for older Broadcom chipsets
>
> Status in “bcmwl” package in Ubuntu:
> Confirmed
> Status in “ubuntu-drivers-common” package in Ubuntu:
> New
>
> Bug description:
> On upgrade to 13.04, the wl.ko, package bcmwl-kernel-source drier is
> selected.
>
> This driver does not allow the computer to boot and causes great pain in
> recovery for users, most of which will not be able to get the Ubuntu
> installation functional
> https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1097509
>
> Instead use the driver brcmsmac, that actually works with BCM4313
>
> ProblemType: Bug
> DistroRelease: Ubuntu 13.04
> Package: linux-image-3.7.0-7-generic 3.7.0-7.15
> ProcVersionSignature: Ubuntu 3.7.0-7.15-generic 3.7.0
> Uname: Linux 3.7.0-7-generic i686
> ApportVersion: 2.7-0ubuntu2
> Architecture: i386
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: foxyboy 1904 F.... pulseaudio
> Date: Tue Jan 8 15:36:51 2013
> HibernationDevice: RESUME=UUID=695c8efa-91da-424d-983e-cc08dd01eba3
> MachineType: LENOVO 20040M18
> MarkForUpload: True
> ProcEnviron:
> TERM=xterm
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-7-generic
> root=UUID=8b809c57-f15a-464f-a7a9-fafb8abaa715 ro quiet
> RelatedPackageVersions:
> linux-restricted-modules-3.7.0-7-generic N/A
> linux-backports-modules-3.7.0-7-generic N/A
> linux-firmware 1.99
> SourcePackage: linux
> UpgradeStatus: Upgraded to raring on 2013-01-08 (0 days ago)
> dmi.bios.date: 08/30/2010
> dmi.bios.vendor: LENOVO
> dmi.bios.version: 24CN62WW
> dmi.board.name: Caucasus2
> dmi.board.vendor: LENOVO
> dmi.board.version: Rev 1.0
> dmi.chassis.asset.tag: No Asset Tag
> dmi.chassis.type: 10
> dmi.chassis.vendor: Lenovo
> dmi.chassis.version: Rev 1.0
> dmi.modalias:
> dmi:bvnLENOVO:bvr24CN62WW:bd08/30/2010:svnLENOVO:pn20040M18:pvrLenovoIdeapadS10-3t:rvnLENOVO:rnCaucasus2:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0:
> dmi.product.name: 20040M18
> dmi.product.version: Lenovo Ideapad S10-3t
> dmi.sys.vendor: LENOVO
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1097519/+subscriptions
>