Ubuntu
bcmwl package

bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu6: bcmwl kernel module failed to build - now no wifi! any workaround?

Bug #1184974 reported by Tom Hastings on 2013-05-28

This bug report is a duplicate of: Bug #1156138: bcmwl-kernel-source fails to build on lowlatency kernel [FATAL: modpost: GPL-incompatible module wl.ko uses GPL-only symbol '__rcu_read_unlock']. Edit Remove

This bug affects 1 person

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

Bug Description

wifi not working now as this package contains the driver for broadcom wireless. Any workaround?

ProblemType: Package
DistroRelease: Ubuntu 13.04
Package: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu6
ProcVersionSignature: Ubuntu 3.8.0-22.15-lowlatency 3.8.11
Uname: Linux 3.8.0-22-lowlatency i686
ApportVersion: 2.9.2-0ubuntu8
Architecture: i386
DKMSKernelVersion: 3.8.0-22-lowlatency
Date: Tue May 28 13:15:11 2013
InstallationDate: Installed on 2012-05-24 (369 days ago)
InstallationMedia: Ubuntu-Studio 12.04 "Precise Pangolin" - Release i386 (20120423)
MarkForUpload: True
PackageVersion: 6.20.155.1+bdcom-0ubuntu6
SourcePackage: bcmwl
Title: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu6: bcmwl kernel module failed to build
UpgradeStatus: Upgraded to raring on 2013-05-03 (25 days ago)

Tags:

Revision history for this message

Tom Hastings (tomjuggler) wrote on 2013-05-28:

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

Apport retracing service (apport) on 2013-05-28

tags:

removed: need-duplicate-check

Revision history for this message

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

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