Ubuntu
bcmwl package

package bcmwl-kernel-source 5.100.82.38+bdcom-0ubuntu3.2 failed to install/upgrade: bcmwl kernel module failed to build

Bug #1165610 reported by Amit Supugade on 2013-04-07

This bug report is a duplicate of: Bug #912155: package bcmwl-kernel-source 5.100.82.38+bdcom-0ubuntu3.2 failed to install/upgrade: bcmwl kernel module failed to build (error: unknown field ‘ndo_set_multicast_list’ specified in initializer). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	bcmwl (Ubuntu)	New	Undecided	Unassigned

Bug Description

while i am tryng to install wireless drivers for lenovo G550 laptop, command sudo dpkg -i bcmwl*.deb is fail saying some system error.

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: bcmwl-kernel-source 5.100.82.38+bdcom-0ubuntu3.2
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
Uname: Linux 3.2.0-23-generic-pae i686
ApportVersion: 2.0.1-0ubuntu5
Architecture: i386
Date: Sat Apr 6 21:50:16 2013
ErrorMessage: bcmwl kernel module failed to build
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
PackageVersion: 5.100.82.38+bdcom-0ubuntu3.2
SourcePackage: bcmwl
Title: package bcmwl-kernel-source 5.100.82.38+bdcom-0ubuntu3.2 failed to install/upgrade: bcmwl kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Amit Supugade (amit-lovely) wrote on 2013-04-07:

DKMSBuildLog.txt Edit (1.1 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (987 bytes, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2013-04-09:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 912155, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.