Ubuntu
fglrx-installer package

package fglrx 2:8.723.1-0ubuntu6 failed to install/upgrade: fglrx kernel module failed to build

Bug #1010664 reported by Nico van Dijkhuizen on 2012-06-08

This bug report is a duplicate of: Bug #601447: package fglrx 2:8.723.1-0ubuntu4 failed to install/upgrade: fglrx kernel module failed to build [Error: kernel includes at ... do not match current kernel. they are versioned as "" instead of "2.6.32-23-generic". you might need to adjust your symlinks: ...]. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	fglrx-installer (Ubuntu)	New	Undecided	Unassigned

Bug Description

fglrx failed to upgrade by the update manager.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: fglrx 2:8.723.1-0ubuntu6
ProcVersionSignature: Ubuntu 2.6.38-10.46~lucid1-generic 2.6.38.7
Uname: Linux 2.6.38-10-generic x86_64
Architecture: amd64
Date: Fri Jun 8 21:09:58 2012
DkmsStatus:
fglrx, 8.723.1: added
vboxhost, 4.0.4, 2.6.38-10-generic, x86_64: installed
ErrorMessage: fglrx kernel module failed to build
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: FUJITSU SIEMENS ESPRIMO Mobile V5545
PackageVersion: 2:8.723.1-0ubuntu6
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-10-generic root=UUID=9d3f05cf-79b0-4aad-bceb-473d8c03144b ro quiet splash
SourcePackage: fglrx-installer
Title: package fglrx 2:8.723.1-0ubuntu6 failed to install/upgrade: fglrx kernel module failed to build
dmi.bios.date: 01/21/2009
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: R01-A1D
dmi.board.name: ESPRIMO Mobile V5545
dmi.board.vendor: FUJITSU SIEMENS
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.chassis.version: A2040
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR01-A1D:bd01/21/2009:svnFUJITSUSIEMENS:pnESPRIMOMobileV5545:pvr20:rvnFUJITSUSIEMENS:rnESPRIMOMobileV5545:rvrNotApplicable:cvnFUJITSUSIEMENS:ct10:cvrA2040:
dmi.product.name: ESPRIMO Mobile V5545
dmi.product.version: 20
dmi.sys.vendor: FUJITSU SIEMENS
system:
distro: Ubuntu
codename: lucid
architecture: x86_64
kernel: 2.6.38-10-generic

Tags:

Revision history for this message

Nico van Dijkhuizen (nico-p0) wrote on 2012-06-08:

BootDmesg.txt Edit (52.4 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (2.9 KiB, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (463 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (4.6 KiB, text/plain; charset="utf-8")
GdmLog.txt Edit (17.7 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (16.3 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (15.2 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (27.0 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (715 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (1.7 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.8 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (233 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (128.9 KiB, text/plain; charset="utf-8")
UdevLog.gz Edit (30.9 KiB, application/x-gzip)
XorgConf.txt Edit (290 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (21.7 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (20.6 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (3.0 KiB, text/plain; charset="utf-8")
glxinfo.txt Edit (350 bytes, text/plain; charset="utf-8")
make.log.txt Edit (463 bytes, text/plain; charset="utf-8")
setxkbmap.txt Edit (233 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (4.2 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (47.3 KiB, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2012-06-10:

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