Ubuntu
fglrx-installer package

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

Bug #1007994 reported by Randy Morton on 2012-06-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

fglrx will not install

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: fglrx 2:8.723.1-0ubuntu6
ProcVersionSignature: Ubuntu 2.6.32-41.89-generic 2.6.32.59+drm33.24
Uname: Linux 2.6.32-41-generic x86_64
Architecture: amd64
Date: Sat Jun 2 21:51:04 2012
DkmsStatus:
rtl8192ce, 2.6.0003.0628.2010ubuntu1, 2.6.32-41-generic, x86_64: installed
fglrx, 8.723.1: added
ErrorMessage: fglrx kernel module failed to build
InstallationMedia: Ubuntu 10.04.4 LTS "Lucid Lynx" - Release amd64 (20120214.2)
MachineType: Hewlett-Packard HP Pavilion g7 Notebook PC
PackageVersion: 2:8.723.1-0ubuntu6
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-41-generic root=UUID=5fe47743-98ab-4873-a709-66f197448b1d 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: 10/17/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.35
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 3568
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 21.27
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.35:bd10/17/2011:svnHewlett-Packard:pnHPPaviliong7NotebookPC:pvr0690120000204620000620100:rvnHewlett-Packard:rn3568:rvr21.27:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion g7 Notebook PC
dmi.product.version: 0690120000204620000620100
dmi.sys.vendor: Hewlett-Packard
glxinfo: Error: [Errno 2] No such file or directory
system:
distro: Ubuntu
codename: lucid
architecture: x86_64
kernel: 2.6.32-41-generic

Tags:

Revision history for this message

Randy Morton (ke5eot) wrote on 2012-06-03:

BootDmesg.txt Edit (43.9 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (1.1 KiB, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (367 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (5.3 KiB, text/plain; charset="utf-8")
GdmLog.txt Edit (25.1 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (25.7 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (25.6 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (25.1 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (536 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.7 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.6 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (233 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (110.2 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (234.8 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (77.2 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (77.9 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (577 bytes, text/plain; charset="utf-8")
make.log.txt Edit (367 bytes, text/plain; charset="utf-8")
setxkbmap.txt Edit (233 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (2.5 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (44.4 KiB, text/plain; charset="utf-8")

Revision history for this message

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

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.