Ubuntu
bcmwl package

bcmwl-kernel-source 6.30.223.30+bdcom-0ubuntu3: bcmwl kernel module failed to build

Bug #1232908 reported by Gabriel Jiménez on 2013-09-29

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

El problema apareció cuando desactivé el dispositivo que usaba el paquete. A mi no me ocasiona ningún problema, resporto el error por si puedo ayudar a alguien más.

ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: bcmwl-kernel-source 6.30.223.30+bdcom-0ubuntu3
ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
Uname: Linux 3.11.0-9-generic x86_64
NonfreeKernelModules: wl nvidia
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
DKMSKernelVersion: 3.11.0-2-lowlatency
Date: Sun Sep 29 21:49:22 2013
InstallationDate: Installed on 2013-09-29 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
MarkForUpload: True
PackageVersion: 6.30.223.30+bdcom-0ubuntu3
SourcePackage: bcmwl
Title: bcmwl-kernel-source 6.30.223.30+bdcom-0ubuntu3: bcmwl kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Gabriel Jiménez (gabijp95) wrote on 2013-09-29:

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

Revision history for this message

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

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.