Ubuntu
fglrx-installer package

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

Bug #793483 reported by summerb0y on 2011-06-06

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

Description: Ubuntu 10.04.2 LTS
Release: 10.04

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: fglrx 2:8.723.1-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.32-32.62-generic 2.6.32.38+drm33.16
Uname: Linux 2.6.32-32-generic i686
NonfreeKernelModules: fglrx
Architecture: i386
Date: Sat Jun 4 13:14:31 2011
ErrorMessage: fglrx kernel module failed to build
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate i386 (20100419.1)
MachineType: ASUSTeK Computer Inc. F7Se
PackageVersion: 2:8.723.1-0ubuntu5
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-32-generic root=UUID=fc716185-af7d-4cda-8784-254fb34e5b1c ro quiet splash
SourcePackage: fglrx-installer
Title: package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel module failed to build
dmi.bios.date: 12/01/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 308
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: F7Se
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr308:bd12/01/2008:svnASUSTeKComputerInc.:pnF7Se:pvr1.0:rvnASUSTeKComputerInc.:rnF7Se:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: F7Se
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
glxinfo: Error: [Errno 2] No such file or directory
system:
distro: Ubuntu
codename: lucid
architecture: i686
kernel: 2.6.32-32-generic

Tags:

Revision history for this message

summerb0y (matic-lesjak) wrote on 2011-06-06:

BootDmesg.txt Edit (55.5 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (8.1 KiB, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (462 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (3.1 KiB, text/plain; charset="utf-8")
DkmsStatus.txt Edit (694 bytes, text/plain; charset="utf-8")
GdmLog.txt Edit (19.1 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (19.5 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (22.4 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (34.9 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (912 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.8 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (5.3 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (231 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (136.2 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (284.7 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (245 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (24.1 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (24.8 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (4.9 KiB, text/plain; charset="utf-8")
make.log.txt Edit (462 bytes, text/plain; charset="utf-8")
setxkbmap.txt Edit (295 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (21.4 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (51.8 KiB, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2011-07-22:

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.