package blcr-dkms 0.8.2-10 failed to install/upgrade: blcr kernel module failed to build - configure: error: Failed to locate kernel symbol table.

Bug #572012 reported by pedro@gruposinapsys.com
32
This bug affects 7 people
Affects Status Importance Assigned to Milestone
blcr (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Esto falló cuando estaba actualizando Ubuntu en un servidor de Core 2 Quad, en genera todo está funcionando bien hasta ahora.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: blcr-dkms 0.8.2-10
ProcVersionSignature: Ubuntu 2.6.32-21.32-server 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-server x86_64
Architecture: amd64
Date: Thu Apr 29 21:58:24 2010
ErrorMessage: blcr kernel module failed to build
PackageArchitecture: all
PackageVersion: 0.8.2-10
SourcePackage: blcr
Title: package blcr-dkms 0.8.2-10 failed to install/upgrade: blcr kernel module failed to build

Revision history for this message
pedro@gruposinapsys.com (pedrodago) wrote :
Revision history for this message
Alan (awoodland) wrote :

From the log it looks like you're trying to build for a kernel which doesn't have the System.map installed - BLCR needs this in order to be able to build.

Alan

Revision history for this message
Ondrej Sipr (sipr) wrote :

You may be right; the description of the package linux-image-2.6.32.22-generic (x86_64) which I have installed states that this package "also includes the corresponding System.map file", yet there is not such file on my computer (and the above described bug also affects me).
So the issue might in fact be with the linux-image-2.6.32-22-generic package (2.6.32-22.35, x86/x86_64).
BTW: This bug seems to be duplicated - there is a whole family of bugs 534175, 502261, 586875 , 572012, 583755, 590092 concerning probably the same issue.

summary: package blcr-dkms 0.8.2-10 failed to install/upgrade: blcr kernel module
- failed to build
+ failed to build - configure: error: Failed to locate kernel symbol
+ table.
Changed in blcr (Ubuntu):
status: New → Confirmed
Revision history for this message
Kirils Solovjovs (linux-kirils) wrote :

This happens when I upgrade from 9.10 to 10.04

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.