Ubuntu
fglrx-installer package

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

Bug #822450 reported by gerry_the_hat on 2011-08-07

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

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: fglrx 2:8.723.1-0ubuntu5
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: Mon Aug 8 00:03:19 2011
DkmsStatus:
vboxhost, 4.1.0, 2.6.32-33-generic, x86_64: installed
vboxhost, 4.1.0, 2.6.38-10-generic, x86_64: installed
fglrx, 8.723.1: added
ErrorMessage: fglrx kernel module failed to build
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: LENOVO 20559BG
PackageVersion: 2:8.723.1-0ubuntu5
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-10-generic root=UUID=53b7a2ed-3299-45d3-9551-70612da9d2f1 ro quiet splash
SourcePackage: fglrx-installer
Title: package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel module failed to build
dmi.bios.date: 03/10/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 7VET90WW (3.20 )
dmi.board.name: 20559BG
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr7VET90WW(3.20):bd03/10/2011:svnLENOVO:pn20559BG:pvrThinkPadT500:rvnLENOVO:rn20559BG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20559BG
dmi.product.version: ThinkPad T500
dmi.sys.vendor: LENOVO
system:
distro: Ubuntu
codename: lucid
architecture: x86_64
kernel: 2.6.38-10-generic

Tags:

Revision history for this message

gerry_the_hat (gerry-the-hat) wrote on 2011-08-07:

BootDmesg.txt Edit (75.8 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (43.4 KiB, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (464 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (4.5 KiB, text/plain; charset="utf-8")
GdmLog.txt Edit (16.4 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (18.9 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (19.2 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (33.6 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (624 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.9 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.1 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (231 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (130.3 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (290.6 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (245 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (20.4 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (24.1 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (5.0 KiB, text/plain; charset="utf-8")
glxinfo.txt Edit (350 bytes, text/plain; charset="utf-8")
make.log.txt Edit (464 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.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2011-08-08:

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.