Ubuntu
fglrx-installer package

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

Bug #778834 reported by jonatime on 2011-05-07

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

i could not get my ubuntu accuont , a debug always is there

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: fglrx 2:8.723.1-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.32-31.61-generic 2.6.32.32+drm33.14
Uname: Linux 2.6.32-31-generic i686
Architecture: i386
Date: Fri May 6 19:34:29 2011
ErrorMessage: fglrx kernel module failed to build
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: Hewlett-Packard HP G72 Notebook PC
PackageVersion: 2:8.723.1-0ubuntu5
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-31-generic root=UUID=f5aa0d7c-ca29-4499-bfa8-ed4f8e45f750 ro vga=758 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: 07/06/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.17
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1484
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 77.19
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.17:bd07/06/2010:svnHewlett-Packard:pnHPG72NotebookPC:pvr0493110003202710000620000:rvnHewlett-Packard:rn1484:rvr77.19:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: HP G72 Notebook PC
dmi.product.version: 0493110003202710000620000
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-31-generic

Tags:

Revision history for this message

jonatime (topoapocaliptico) wrote on 2011-05-07:

BootDmesg.txt Edit (46.6 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (122.5 KiB, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (472 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (4.5 KiB, text/plain; charset="utf-8")
DkmsStatus.txt Edit (1.1 KiB, text/plain; charset="utf-8")
GdmLog.txt Edit (23.7 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (24.3 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (25.6 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (20.4 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (657 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.0 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (231 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (113.9 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (249.6 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (26.9 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (27.9 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (3.2 KiB, text/plain; charset="utf-8")
make.log.txt Edit (10.8 KiB, text/plain; charset="utf-8")
setxkbmap.txt Edit (367 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (2.7 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (61.6 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.