package bcmwl-kernel-source 5.60.48.36+bdcom-0ubuntu3 failed to install/upgrade: bcmwl kernel module failed to build [error: linux/autoconf.h: No existe el fichero o el directorio]

Bug #991956 reported by RAFAEL ANDRÉS LÓPEZ ARÉVALO
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
bcmwl (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

this problem is caused when i install the kernel 2.6.39-020639 in the version 10.04-4 of ubuntu, and i think that is a comun problem in this actualization of kernel.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: bcmwl-kernel-source 5.60.48.36+bdcom-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-34.77-generic 2.6.32.44+drm33.19
Uname: Linux 2.6.32-34-generic x86_64
NonfreeKernelModules: wl nvidia
Architecture: amd64
Date: Mon Apr 30 08:18:27 2012
ErrorMessage: bcmwl kernel module failed to build
InstallationMedia: RATAEL - Release amd64
PackageVersion: 5.60.48.36+bdcom-0ubuntu3
SourcePackage: bcmwl
Title: package bcmwl-kernel-source 5.60.48.36+bdcom-0ubuntu3 failed to install/upgrade: bcmwl kernel module failed to build

Revision history for this message
RAFAEL ANDRÉS LÓPEZ ARÉVALO (rataeltriforce) wrote :
summary: package bcmwl-kernel-source 5.60.48.36+bdcom-0ubuntu3 failed to
- install/upgrade: bcmwl kernel module failed to build
+ install/upgrade: bcmwl kernel module failed to build [error:
+ linux/autoconf.h: No existe el fichero o el directorio]
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in bcmwl (Ubuntu):
status: New → Confirmed
Revision history for this message
rubencarbonero (rubencarbonero) wrote :

See duplicate bug https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/994347 for a possible workaround. (At least, it worked for me, nothing assured).

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

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

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.