Ubuntu
fglrx-installer package

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

Bug #1007905 reported by kevin brian giacobbe on 2012-06-02

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

i don't know. in layman terms, it appears to have been looking for something (package, program, driver). when it did not find what it needed it threw it's logical hands in the air and quit. i hope all the messages that were shown to me at end time are somehow included in bug report. background: trying to get ati-6770 to display properly (without horizontal stretch, vertical compress). i was hoping that "fglrx" would be key to rebecca showing inner working of settings in video card. oh well..... i will also look at x. maybe a tweak in right place will do the trick. i know that google is my friend.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: fglrx 2:8.723.1-0ubuntu6
ProcVersionSignature: Ubuntu 2.6.32-41.90-generic-pae 2.6.32.59+drm33.24
Uname: Linux 2.6.32-41-generic-pae i686
Architecture: i386
Date: Fri Jun 1 21:20:29 2012
DkmsStatus: fglrx, 8.723.1: added
ErrorMessage: fglrx kernel module failed to build
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: Hewlett-Packard PPPPPPP-CCC#MMMMMMMM
PackageVersion: 2:8.723.1-0ubuntu6
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-41-generic-pae root=UUID=225784eb-d459-4f54-8191-047b7a5a09de ro splash vga=799 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: 11/27/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 5.07
dmi.board.name: Aspen
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.07:bd11/27/2008:svnHewlett-Packard:pnPPPPPPP-CCC#MMMMMMMM:pvr:rvnMSI:rnAspen:rvr1.0:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: PPPPPPP-CCC#MMMMMMMM
dmi.sys.vendor: Hewlett-Packard
glxinfo: Error: command ['glxinfo'] failed with exit code -11:
system:
distro: Ubuntu
codename: lucid
architecture: i686
kernel: 2.6.32-41-generic-pae

Tags:

Revision history for this message

kevin brian giacobbe (kevin-giacobbe) wrote on 2012-06-02:

BootDmesg.txt Edit (50.0 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (1.2 KiB, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (2.3 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (4.6 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (31.2 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (661 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (1.7 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (3.3 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (2.1 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.3 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (233 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (118.3 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (261.0 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (16.4 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (232.6 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (1.7 KiB, text/plain; charset="utf-8")
make.log.txt Edit (2.3 KiB, 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 (44.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2012-06-03:

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.