Ubuntu
broadcom-sta package

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

Bug #1219096 reported by Amitai Bar on 2013-08-30

This bug report is a duplicate of: Bug #1095751: bcmwl fails to build with 3.8 kernels [error: 'struct cfg80211_ibss_params' has no member named 'channel']. Edit Remove

This bug affects 1 person

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

Bug Description

All i did was running apt-get update and it updated the kernek but the dkms failed.
Thanks
Amitai

ProblemType: Package
DistroRelease: Ubuntu 13.04
Package: broadcom-sta-dkms 5.100.82.112-9
ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
Uname: Linux 3.8.0-27-generic i686
NonfreeKernelModules: wl fglrx
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: i386
DKMSKernelVersion: 3.8.0-27-generic
Date: Sat Aug 31 00:33:47 2013
InstallationDate: Installed on 2012-07-28 (398 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
MarkForUpload: True
PackageArchitecture: all
PackageVersion: 5.100.82.112-9
SourcePackage: broadcom-sta
Title: broadcom-sta-dkms 5.100.82.112-9: broadcom-sta kernel module failed to build
UpgradeStatus: Upgraded to raring on 2013-04-04 (148 days ago)

Tags:

Revision history for this message

Amitai Bar (amitaibar) wrote on 2013-08-30:

DKMSBuildLog.txt Edit (2.6 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.5 KiB, text/plain; charset="utf-8")
DuplicateSignature.txt Edit (2.5 KiB, text/plain; charset="utf-8")

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

tags:

removed: need-duplicate-check

Revision history for this message

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

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