bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1: bcmwl kernel module failed to build
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bcmwl (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
# sudo apt-get install --reinstall bcmwl-kernel-source
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 32 not upgraded.
Need to get 0 B/1,301 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 143173 files and directories currently installed.)
Preparing to replace bcmwl-kernel-source 6.20.155.
Removing all DKMS Modules
Done.
Unpacking replacement bcmwl-kernel-source ...
Setting up bcmwl-kernel-source (6.20.155.
Loading new bcmwl-6.
Building only for 3.8.0-29-generic
Building for architecture i686
Building initial module for 3.8.0-29-generic
Error! Bad return status for module build on kernel: 3.8.0-29-generic (i686)
Consult /var/lib/
FATAL: Module wl not found.
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: bcmwl-kernel-source 6.20.155.
ProcVersionSign
Uname: Linux 3.8.0-29-generic i686
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: i386
DKMSKernelVersion: 3.8.0-29-generic
Date: Sun Sep 15 02:25:42 2013
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 (20130820.1)
MarkForUpload: True
PackageVersion: 6.20.155.
SourcePackage: bcmwl
Title: bcmwl-kernel-source 6.20.155.
UpgradeStatus: No upgrade log present (probably fresh install)
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1224714, so 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. Please continue to report any other bugs you may find.