Ubuntu
fglrx-installer package

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

Bug #920179 reported by Benjamin on 2012-01-22

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

cannot active the fglrx driver for Kernel 3.0.0-14-generic

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: fglrx 2:8.723.1-0ubuntu5
ProcVersionSignature: Ubuntu 3.0.0-14.23~lucid1-generic 3.0.9
Uname: Linux 3.0.0-14-generic x86_64
Architecture: amd64
Date: Sun Jan 22 22:45:45 2012
ErrorMessage: fglrx kernel module failed to build
InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 (20110720.1)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
PackageVersion: 2:8.723.1-0ubuntu5
ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-14-generic root=UUID=6fbd2265-6f6d-485c-9c46-96e033c6363a ro noplymouth
SourcePackage: fglrx-installer
Title: package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel module failed to build
dmi.bios.date: 10/05/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.60
dmi.board.name: 880GMH/U3S3
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd10/05/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn880GMH/U3S3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
glxinfo: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
system:
distro: Ubuntu
codename: lucid
architecture: x86_64
kernel: 3.0.0-14-generic

Tags:

Revision history for this message

Benjamin (nailartcenter) wrote on 2012-01-22:

BootDmesg.txt Edit (55.6 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (680 bytes, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (459 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (3.2 KiB, text/plain; charset="utf-8")
DkmsStatus.txt Edit (291 bytes, text/plain; charset="utf-8")
GdmLog.txt Edit (13.6 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (19.4 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (6.2 MiB, text/plain; charset="utf-8")
Lspci.txt Edit (28.0 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (699 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (967 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.7 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.8 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.1 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (217 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (116.1 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (254.9 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (58.4 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (22.3 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (1.3 KiB, text/plain; charset="utf-8")
make.log.txt Edit (459 bytes, text/plain; charset="utf-8")
setxkbmap.txt Edit (295 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (2.5 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (52.0 KiB, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2012-01-23:

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.