The Debian control file's "modaliases" is too generic

Bug #1490713 reported by Adam Smith on 2015-08-31
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bcmwl (Ubuntu)

Bug Description

Software-properties-gtk offers wl as the driver for all Broadcom wifi cards, regardless of whether they are supported or not. This is due to the modaliases field used by the bcmwl-kernel-source package.

Although in reality I know very little about such things, I'll attach a proposed debian/bcmwl-kernel-source.modaliases file based on the info here:

Users are going through needless painful procedures to get the correct working driver.

Adam Smith (adamsmith) wrote :
Adam Smith (adamsmith) on 2015-08-31
description: updated
Adam Smith (adamsmith) wrote :

This is one of several bugs I'm reporting about Broadcom at the moment. See here

Adam Smith (adamsmith) wrote :

Attached is the file as a patch. Note I've relaced a * with four 0's.

Martin Pitt (pitti) wrote :

Thank you! Makes sense. I removed the duplicate product ID at the end of the patch. I'll upload this together with bug 1491070.

Changed in bcmwl (Ubuntu):
status: New → Fix Committed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package bcmwl -

bcmwl ( wily; urgency=medium

  * debian/bcmwl-kernel-source.modaliases: Fine-tune product list as per Thanks
    Adam Smith! (LP: #1490713)
  * debian/bcmwl-kernel-source.postrm: Warn that a reboot is needed after
    removing. Thanks Adam Smith! (LP: #1491070)

 -- Martin Pitt <email address hidden> Fri, 18 Sep 2015 10:12:45 +0200

Changed in bcmwl (Ubuntu):
status: Fix Committed → Fix Released

Hello Adam, or anyone else affected,

Accepted bcmwl into trusty-proposed. The package will build now and be available at in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at . Thank you in advance!

Changed in bcmwl (Ubuntu Trusty):
status: New → Fix Committed
tags: added: verification-needed
Mathew Hodson (mhodson) on 2016-12-11
Changed in bcmwl (Ubuntu):
importance: Undecided → Medium
Changed in bcmwl (Ubuntu Trusty):
importance: Undecided → Medium

The fix for this bug has been awaiting testing feedback in the -proposed repository for trusty for more than 90 days. Please test this fix and update the bug appropriately with the results. In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository.

tags: added: removal-candidate

As part of a recent change in the Stable Release Update verification policy we would like to inform that for a bug to be considered verified for a given release a verification-done-$RELEASE tag needs to be added to the bug where $RELEASE is the name of the series the package that was tested (e.g. verification-done-xenial). Please note that the global 'verification-done' tag can no longer be used for this purpose.

Thank you!

Mathew Hodson (mhodson) on 2019-04-13
tags: added: verification-needed-trusty
Bryan Quigley (bryanquigley) wrote :

Trusty release has gone end of support for this package, so marking this as such.

Newer releases will have this fix though.

Changed in bcmwl (Ubuntu Trusty):
status: Fix Committed → Won't Fix
Mathew Hodson (mhodson) on 2019-11-02
tags: removed: verification-needed verification-needed-trusty
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers