Ubuntu
fglrx-installer package

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

Bug #899590 reported by Josef Göttle on 2011-12-03

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

$ ubuntu-bug fglrx-installer failed

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: fglrx 2:8.723.1-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.32-35.78-generic 2.6.32.46+drm33.20
Uname: Linux 2.6.32-35-generic i686
NonfreeKernelModules: fglrx
Architecture: i386
Date: Sat Dec 3 14:18:04 2011
DkmsStatus: fglrx, 8.723.1, 2.6.32-35-generic, i686: installed
ErrorMessage: fglrx kernel module failed to build
InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110720.1)
MachineType: Acer TravelMate 5520
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.32-35-generic root=UUID=d5a2073e-4528-4249-8aee-d49828fc103f ro noplymouth pcie_aspm=force
SourcePackage: fglrx-installer
Title: package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel module failed to build
dmi.bios.date: 08/17/2007
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.14
dmi.board.name: TravelMate 5520
dmi.board.vendor: Acer
dmi.board.version: Rev
dmi.chassis.asset.tag: None
dmi.chassis.type: 1
dmi.chassis.vendor: Acer
dmi.chassis.version: None
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.14:bd08/17/2007:svnAcer:pnTravelMate5520:pvr0100:rvnAcer:rnTravelMate5520:rvrRev:cvnAcer:ct1:cvrNone:
dmi.product.name: TravelMate 5520
dmi.product.version: 0100
dmi.sys.vendor: Acer
glxinfo: Error: command ['glxinfo'] failed with exit code -11:
system:
distro: Ubuntu
codename: lucid
architecture: i686
kernel: 2.6.32-35-generic

Tags:

Revision history for this message

Josef Göttle (j-goettle) wrote on 2011-12-03:

BootDmesg.txt Edit (48.0 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (972 bytes, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (472 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (4.6 KiB, text/plain; charset="utf-8")
GdmLog.txt Edit (40.3 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (28.1 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (26.7 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (27.1 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (445 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (1.8 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.6 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (231 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (103.6 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (233.4 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (46.2 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (32.2 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (2.9 KiB, text/plain; charset="utf-8")
make.log.txt Edit (472 bytes, text/plain; charset="utf-8")
setxkbmap.txt Edit (233 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (2.7 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-12-04:

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.