Ubuntu
bcmwl package

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

Bug #1216837 reported by 8lackie on 2013-08-26

This bug report is a duplicate of: Bug #994255: bcmwl-kernel-source / broadcom-sta failed to build [fatal error: asm/system.h: No such file or directory]. Edit Remove

This bug affects 1 person

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

Bug Description

It could be one of the bugs I was presented with. However I don't know my way around well enough to know. Apologies

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: bcmwl-kernel-source 5.100.82.38+bdcom-0ubuntu5
ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2
Uname: Linux 3.5.0-23-generic i686
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: i386
DKMSKernelVersion: 3.5.0-23-generic
Date: Mon Aug 26 11:38:29 2013
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 (20130213)
MarkForUpload: True
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

8lackie (slickjesus) wrote on 2013-08-26:

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

Apport retracing service (apport) on 2013-08-26

tags:

removed: need-duplicate-check

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2013-08-27:

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 994255, 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.