Ubuntu
fglrx-installer package

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

Bug #903052 reported by Izhan Jafry on 2011-12-12

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

latest kernel on Lucid get problem

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: fglrx 2:8.723.1-0ubuntu5
ProcVersionSignature: Ubuntu 3.0.0-13.22~lucid1-generic 3.0.6
Uname: Linux 3.0.0-13-generic x86_64
Architecture: amd64
Date: Mon Dec 12 13:33:18 2011
DkmsStatus: fglrx, 8.723.1: added
ErrorMessage: fglrx kernel module failed to build
InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 (20110720.1)
MachineType: Hewlett-Packard Compaq 421
PackageVersion: 2:8.723.1-0ubuntu5
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-13-generic root=UUID=998b8ffe-2076-41b0-bdb9-91ff37650613 ro quiet splash nomodeset video=uvesafb:mode_option=1366x768-24,mtrr=3,scroll=ywrap
SourcePackage: fglrx-installer
Title: package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel module failed to build
dmi.bios.date: 07/21/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PVI Ver. F.04
dmi.board.name: 1476
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 71.0D
dmi.chassis.asset.tag: CNU03303X9
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68PVIVer.F.04:bd07/21/2010:svnHewlett-Packard:pnCompaq421:pvrF.04:rvnHewlett-Packard:rn1476:rvrKBCVersion71.0D:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: Compaq 421
dmi.product.version: F.04
dmi.sys.vendor: Hewlett-Packard
system:
distro: Ubuntu
codename: lucid
architecture: x86_64
kernel: 3.0.0-13-generic

Tags:

Revision history for this message

Izhan Jafry (izhanjafry) wrote on 2011-12-12:

BootDmesg.txt Edit (62.1 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (417 bytes, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (459 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (4.7 KiB, text/plain; charset="utf-8")
GdmLog.txt Edit (16.0 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (16.3 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (16.6 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (30.7 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (693 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (1.7 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.9 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.4 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (231 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (134.4 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (303.6 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (723 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (20.1 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (20.6 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (3.0 KiB, text/plain; charset="utf-8")
glxinfo.txt Edit (350 bytes, text/plain; charset="utf-8")
make.log.txt Edit (459 bytes, text/plain; charset="utf-8")
setxkbmap.txt Edit (233 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (4.2 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 2011-12-13:

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.