Ubuntu
bcmwl package

bcmwl-kernel-source 5.100.82.38+bdcom-0ubuntu6.1: bcmwl kernel module failed to build

Bug #1026097 reported by Amit Kucheria on 2012-07-18

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

Filed a separate bug since I'm trying this with the ubuntu-x-swat ppa enabled so that I can test the quantal kernel on precise. I'm currently rebooted back into the offical precise kernel to file the bug since the 3.5 quantal kernel won't give me working wireless.

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: bcmwl-kernel-source 5.100.82.38+bdcom-0ubuntu6.1
ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
Uname: Linux 3.2.0-26-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.0.1-0ubuntu11
Architecture: amd64
DKMSKernelVersion: 3.5.0-5-generic
Date: Wed Jul 18 12:08:08 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64+mac (20120425.1)
PackageVersion: 5.100.82.38+bdcom-0ubuntu6.1
SourcePackage: bcmwl
Title: bcmwl-kernel-source 5.100.82.38+bdcom-0ubuntu6.1: bcmwl kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

See original description

Tags:

Revision history for this message

Amit Kucheria (amitk) wrote on 2012-07-18:

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

description:

updated

Apport retracing service (apport) on 2012-07-18

tags:

removed: need-duplicate-check

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2012-07-19:

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.