Ubuntu
bcmwl package

bcmwl-kernel-source 5.100.82.38+bdcom-0ubuntu5: bcmwl kernel module failed to build

Bug #919144 reported by Syukri_Lajin on 2012-01-20

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

trying to upgrade to kernel 3.3rc1 using dpkg. debs files downloaded from ubuntu kernel mainline's archive.

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: bcmwl-kernel-source 5.100.82.38+bdcom-0ubuntu5
ProcVersionSignature: Ubuntu 3.2.0-9.16-generic 3.2.1
Uname: Linux 3.2.0-9-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
DKMSKernelVersion: 3.3.0-030300rc1-generic
Date: Fri Jan 20 19:06:07 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120119)
PackageVersion: 5.100.82.38+bdcom-0ubuntu5
SourcePackage: bcmwl
Title: bcmwl-kernel-source 5.100.82.38+bdcom-0ubuntu5: bcmwl kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Syukri_Lajin (ginger-boy92) wrote on 2012-01-20:

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

Apport retracing service (apport) on 2012-01-20

tags:

removed: need-duplicate-check

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2012-01-21:

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.