Ubuntu
fglrx-installer package

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

Bug #1101078 reported by Daniel on 2013-01-18

This bug report is a duplicate of: Bug #559729: package fglrx 2:8.721-0ubuntu8 failed to install/upgrade: fglrx kernel module failed to build: ld: internal error in output_symtab_index, at ../../gold/object.h:1086. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	fglrx-installer (Ubuntu)	New	Undecided	Unassigned

Bug Description

for some reason this bug continiously keep showing after i try to install ati drivers

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: fglrx 2:8.723.1-0ubuntu6
ProcVersionSignature: Ubuntu 2.6.32-42.96-generic 2.6.32.59+drm33.24
Uname: Linux 2.6.32-42-generic x86_64
Architecture: amd64
Date: Fri Jan 18 00:13:00 2013
DkmsStatus:
fglrx, 8.723.1: added
vboxhost, 3.2.16, 2.6.32-45-generic, x86_64: built
vboxhost, 3.2.16, 2.6.32-41-generic, x86_64: built
ErrorMessage: fglrx kernel module failed to build
InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 (20110720.1)
MachineType: System manufacturer System Product Name
PackageVersion: 2:8.723.1-0ubuntu6
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-42-generic root=UUID=dcce52fc-259d-402d-b2ca-48f5043cf398 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: 09/06/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0901
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M4A88TD-M/USB3
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.:bvr0901:bd09/06/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A88TD-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
glxinfo: Error: command ['glxinfo'] failed with exit code -11:
system:
distro: Ubuntu
codename: lucid
architecture: x86_64
kernel: 2.6.32-42-generic

Tags:

Revision history for this message

Daniel (itahncristosdaniel) wrote on 2013-01-18:

BootDmesg.txt Edit (52.9 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (2.3 KiB, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (2.1 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (4.6 KiB, text/plain; charset="utf-8")
GdmLog.txt Edit (38.7 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (35.6 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (57.4 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (28.4 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (652 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (998 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (3.3 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (2.2 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.0 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (235 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (113.4 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (237.1 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (41.0 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (39.6 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (3.8 KiB, text/plain; charset="utf-8")
make.log.txt Edit (2.1 KiB, text/plain; charset="utf-8")
setxkbmap.txt Edit (272 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (17.3 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (47.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2013-01-18:

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 559729, 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.