Ubuntu
broadcom-sta package

broadcom-sta-dkms 5.100.82.112-7: broadcom-sta kernel module failed to build

Bug #1073244 reported by John Doe on 2012-10-30

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 5 people

Affects		Status	Importance	Assigned to	Milestone
	broadcom-sta (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Trying to install broadcom driver in ubuntu 12.10 macbook 5.1, failed

ProblemType: Package
DistroRelease: Ubuntu 12.10
Package: broadcom-sta-dkms 5.100.82.112-7
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.6.1-0ubuntu3
Architecture: amd64
DKMSKernelVersion: 3.5.0-17-generic
Date: Tue Oct 30 12:43:11 2012
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
PackageArchitecture: all
PackageVersion: 5.100.82.112-7
SourcePackage: broadcom-sta
Title: broadcom-sta-dkms 5.100.82.112-7: broadcom-sta kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

John Doe (aaron0browne-deactivatedaccount) wrote on 2012-10-30:

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

Apport retracing service (apport) on 2012-10-30

tags:

removed: need-duplicate-check

Revision history for this message

Launchpad Janitor (janitor) wrote on 2012-11-03:

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in broadcom-sta (Ubuntu):
status:	New → Confirmed

Revision history for this message

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

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.