Ubuntu
fglrx-installer package

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

Bug #1006285 reported by praween kumar on 2012-05-30

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

not able to install this package.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: fglrx 2:8.723.1-0ubuntu6
ProcVersionSignature: Ubuntu 2.6.32-38.83-generic 2.6.32.52+drm33.21
Uname: Linux 2.6.32-38-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Wed May 30 17:02:32 2012
DkmsStatus: fglrx, 8.723.1, 2.6.32-38-generic, x86_64: installed
ErrorMessage: fglrx kernel module failed to build
InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 (20110720.1)
MachineType: LENOVO GC60MTM
PackageVersion: 2:8.723.1-0ubuntu6
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-38-generic root=UUID=dca6d20b-7b77-4597-9116-21e330630a90 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: 04/28/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 80ET31WW (1.08 )
dmi.board.name: GC60MTM
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr80ET31WW(1.08):bd04/28/2010:svnLENOVO:pnGC60MTM:pvrThinkPadEdge:rvnLENOVO:rnGC60MTM:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: GC60MTM
dmi.product.version: ThinkPad Edge
dmi.sys.vendor: LENOVO
glxinfo: Error: [Errno 2] No such file or directory
system:
distro: Ubuntu
codename: lucid
architecture: x86_64
kernel: 2.6.32-38-generic

Tags:

Revision history for this message

praween kumar (praween-erk) wrote on 2012-05-30:

BootDmesg.txt Edit (56.2 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (9.1 KiB, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (419 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (4.6 KiB, text/plain; charset="utf-8")
GdmLog.txt Edit (22.5 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (27.8 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (24.1 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (32.7 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (677 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (1.8 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (3.3 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.9 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.6 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (233 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (130.4 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (265.6 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (188 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (27.6 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (33.6 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (3.0 KiB, text/plain; charset="utf-8")
make.log.txt Edit (419 bytes, text/plain; charset="utf-8")
setxkbmap.txt Edit (233 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (21.4 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-05-31:

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.