bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu6: bcmwl kernel module failed to build

[Robert Los]

did a dist-upgrade from 12.04 to 12.10 and than from 12.10 to 13.04
Kernel did not upgrade because of an inconsistency in kernel modules and memtest86+
tried to download the latest kernel modules from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8.10-raring/
copied header modules and kernel modules and generic headers.
did dpkg -i which resulted in compiled modules. Grub failed however with:

 /boot/vmlinuz-3.8.10-030810-generic
Generating grub.cfg ...
run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-3.8.10-030810-generic.postinst line 1010.
dpkg: error processing linux-image-3.8.10-030810-generic (--install):
 subprocess installed post-installation script returned error exit status 2
Errors were encountered while processing:
 linux-image-3.8.10-030810-generic

leaving me with a 3.2 kernel.

ProblemType: Package
DistroRelease: Ubuntu 13.04
Package: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu6
ProcVersionSignature: Ubuntu 3.2.0-52.78-generic 3.2.48
Uname: Linux 3.2.0-52-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
DKMSKernelVersion: 3.9.11-030911-generic
Date: Tue Jul 30 23:07:49 2013
InstallationDate: Installed on 2012-10-11 (292 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
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-07-30 (0 days ago)

[Daniel van Vugt (vanvugt)]

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