Ubuntu
bcmwl package

bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.1: bcmwl kernel module failed to build

Bug #1465057 reported by Jim Butcher on 2015-06-14

This bug report is a duplicate of: Bug #1310118: bcmwl-kernel-source 6.30.223.141+bdcom-0ubuntu2: bcmwl kernel module failed to build [ld: Relocatable linking with relocations from format elf64-x86-64 (.../wlc_hybrid.o_shipped_x86_64) to format elf32-i386 (/.../wl.o) is not supported]. Edit Remove

This bug affects 1 person

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

Bug Description

Don't know anything about it. I was using the Synaptic Package manager to install andoid development packages when 'it' happened. The synaptic package manager installed everything correctly. Only other window open at the time was a xterm window that was idle.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.1
ProcVersionSignature: Ubuntu 3.16.0-40.54~14.04.1-generic 3.16.7-ckt11
Uname: Linux 3.16.0-40-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
DKMSKernelVersion: 3.4.0-3-goldfish
Date: Sun Jun 14 13:28:58 2015
InstallationDate: Installed on 2015-06-02 (11 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
PackageVersion: 6.30.223.248+bdcom-0ubuntu0.1
SourcePackage: bcmwl
Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.1: bcmwl kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Jim Butcher (soyoboi) wrote on 2015-06-14:

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

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2015-06-15:

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