Ubuntu
bcmwl package

6.20.155.1 fails to build with 3.8 kernel in Precise

Bug #1189156 reported by OpenSource on 2013-06-09

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

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

Bug Description

i don't now

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1
ProcVersionSignature: Ubuntu 3.8.0-25.37~precise1-generic 3.8.13
Uname: Linux 3.8.0-25-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.3
Architecture: amd64
DKMSKernelVersion: 3.8.0-25-generic
Date: Sun Jun 9 14:10:46 2013
InstallationMedia: Ubuntu "Precise" - Build amd64 LIVE Binary 20120426-22:45
MarkForUpload: True
PackageVersion: 6.20.155.1+bdcom-0ubuntu0.0.1
SourcePackage: bcmwl
Title: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1: bcmwl kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

OpenSource (polferbg) wrote on 2013-06-09:

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

Apport retracing service (apport) on 2013-06-09

tags:

removed: need-duplicate-check

Adam Porter (alphapapa) on 2013-06-09

summary:	- bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1: bcmwl kernel module - failed to build + 6.20.155.1 fails to build with 3.8 kernel in Precise
Changed in bcmwl (Ubuntu):
status:	New → Confirmed

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2013-06-17:

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.