Ubuntu
fglrx-installer package

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

Bug #862712 reported by MAR on 2011-09-29

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

After the update can not install the proprietary driver fglrx

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: fglrx 2:8.723.1-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.32-33.72-generic 2.6.32.41+drm33.18
Uname: Linux 2.6.32-33-generic i686
Architecture: i386
Date: Thu Sep 29 21:36:35 2011
DkmsStatus:
fglrx, 8.723.1: added
vboxhost, 4.1.2, 2.6.32-33-generic, i686: installed
ErrorMessage: fglrx kernel module failed to build
InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110720.1)
MachineType: System manufacturer System Product Name
PackageVersion: 2:8.723.1-0ubuntu5
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-33-generic root=UUID=4284390a-ebd3-4ba6-a1bb-97e5df562108 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: 10/14/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1105
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M3A76-CM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1105:bd10/14/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3A76-CM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
glxinfo: Error: [Errno 2] Nie ma takiego pliku ani katalogu
system:
distro: Ubuntu
codename: lucid
architecture: i686
kernel: 2.6.32-33-generic

Tags:

Revision history for this message

MAR (zok-vp) wrote on 2011-09-29:

BootDmesg.txt Edit (47.2 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (549 bytes, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (472 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (4.6 KiB, text/plain; charset="utf-8")
GdmLog.txt Edit (39.0 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (48.1 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (37.0 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (17.6 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (551 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (1009 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (637 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.5 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (231 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (97.0 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (212.9 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (40.2 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (51.7 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (4.6 KiB, text/plain; charset="utf-8")
make.log.txt Edit (472 bytes, text/plain; charset="utf-8")
setxkbmap.txt Edit (233 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (17.2 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (47.3 KiB, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2011-09-30:

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.