Ubuntu
bcmwl package

bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1: bcmwl kernel module failed to build

Bug #1237486 reported by rathboma on 2013-10-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 1 person

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

Bug Description

I had to uninstall this package as it was causing the computer to freeze up. When depmod runs on install this happens and causes the freezup / installation issue.

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: bcmwl-kernel-source (not installed)
ProcVersionSignature: Ubuntu 3.8.0-31.46~precise1-generic 3.8.13.8
Uname: Linux 3.8.0-31-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu17.5
Architecture: amd64
DKMSKernelVersion: 3.8.0-31-generic
Date: Mon Oct 7 19:56:32 2013
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1)
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

rathboma (beekeeper-studio) wrote on 2013-10-09:

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

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

tags:

removed: need-duplicate-check

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2013-10-10:

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.