Ubuntu
fglrx-installer package

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

Bug #852687 reported by csakalinuxjo on 2011-09-17

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

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

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: fglrx 2:8.723.1-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.32-34.77-generic 2.6.32.44+drm33.19
Uname: Linux 2.6.32-34-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Sat Sep 17 18:57:44 2011
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=/boot/vmlinuz-2.6.32-34-generic root=UUID=75c09a12-0692-45c9-ac67-c4c526acd21e 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: 05/21/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.80
dmi.board.name: K10N78D
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.80:bd05/21/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnK10N78D: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] Nincs ilyen fájl vagy könyvtár
system:
distro: Ubuntu
codename: lucid
architecture: x86_64
kernel: 2.6.32-34-generic

Tags:

Revision history for this message

csakalinuxjo (csakalinuxjo) wrote on 2011-09-17:

BootDmesg.txt Edit (55.1 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (4.1 KiB, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (479 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (4.6 KiB, text/plain; charset="utf-8")
DkmsStatus.txt Edit (9.3 KiB, text/plain; charset="utf-8")
GdmLog.txt Edit (10.9 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (10.4 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (10.7 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (27.3 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (545 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (1.9 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (4.4 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (231 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (165.5 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (306.3 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (1.6 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (14.2 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (13.6 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (573 bytes, text/plain; charset="utf-8")
make.log.txt Edit (479 bytes, text/plain; charset="utf-8")
setxkbmap.txt Edit (233 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (22.0 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (57.1 KiB, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2011-09-18:

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.