Ubuntu
fglrx-installer package

package fglrx (installed) failed to run: fglrx kernel module failed to build

Bug #1008145 reported by cesare46 on 2012-06-03

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

Causes: problema with dependencies (not specified)
results: black screen at the boot of Ubuntu (10.04), post menu F8. Resolved after boot in poor grafical mode and de-intallation of fglrx package.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: fglrx (not installed)
Uname: Linux 2.6.33-02063305-generic i686
Architecture: i386
Date: Tue May 29 20:26:27 2012
ErrorMessage: fglrx kernel module failed to build
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
PackageVersion: 2:8.723.1-0ubuntu6
SourcePackage: fglrx-installer
Title: package fglrx (not installed) failed to install/upgrade: fglrx kernel module failed to build
system:
distro: Ubuntu
codename: lucid
architecture: i686
kernel: 2.6.33-02063305-generic

Tags:

Revision history for this message

cesare46 (cavenati) wrote on 2012-06-03:

DKMSBuildLog.txt Edit (493 bytes, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (233 bytes, text/plain; charset="utf-8")

Revision history for this message

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

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.