Ubuntu
fglrx-installer package

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

Bug #1012889 reported by sepiroth on 2012-06-13

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

I was install ATI driver. I go to hardware controllers and install the driver and the error ocurred

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: fglrx 2:8.723.1-0ubuntu6
ProcVersionSignature: Ubuntu 3.0.0-16.29~lucid1-generic 3.0.20
Uname: Linux 3.0.0-16-generic x86_64
Architecture: amd64
Date: Wed Jun 13 17:06:35 2012
ErrorMessage: fglrx kernel module failed to build
InstallationMedia: Peru Tradeshow - Release amd64
MachineType: Hewlett-Packard HP MultiSeat 6005 SFF PC
PackageVersion: 2:8.723.1-0ubuntu6
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-16-generic root=UUID=38da8d4a-7fb2-4cdc-8f66-9e794efadb29 ro quiet splash radeon.modeset=0 nouveau.modeset=0 consoleblank=0
SourcePackage: fglrx-installer
Title: package fglrx 2:8.723.1-0ubuntu6 failed to install/upgrade: fglrx kernel module failed to build
dmi.bios.date: 08/04/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 786G6 v01.11
dmi.board.asset.tag: MXL12209TZ
dmi.board.name: 3047h
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: MXL12209TZ
dmi.chassis.type: 4
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr786G6v01.11:bd08/04/2010:svnHewlett-Packard:pnHPMultiSeat6005SFFPC:pvr:rvnHewlett-Packard:rn3047h:rvr:cvnHewlett-Packard:ct4:cvr:
dmi.product.name: HP MultiSeat 6005 SFF PC
dmi.sys.vendor: Hewlett-Packard
glxinfo: Error: [Errno 2] No existe el fichero o el directorio
system:
distro: Ubuntu
codename: lucid
architecture: x86_64
kernel: 3.0.0-16-generic

Tags:

Revision history for this message

sepiroth (ea-rc) wrote on 2012-06-13:

BootDmesg.txt Edit (50.6 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (6.9 KiB, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (459 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (4.5 KiB, text/plain; charset="utf-8")
DkmsStatus.txt Edit (289 bytes, text/plain; charset="utf-8")
GdmLog.txt Edit (72.5 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (43.3 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (15.6 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (17.4 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (723 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (986 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (3.4 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (2.0 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (4.1 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (354 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (144.6 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (299.7 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (89.4 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (58.1 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (2.3 KiB, text/plain; charset="utf-8")
make.log.txt Edit (459 bytes, text/plain; charset="utf-8")
setxkbmap.txt Edit (241 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (4.0 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (61.3 KiB, text/plain; charset="utf-8")

Revision history for this message

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

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.