Ubuntu
fglrx-installer-updates package

fglrx-updates-core 2:15.200-0ubuntu0.5: fglrx-updates-core kernel module failed to build

Bug #1525004 reported by benjamin button on 2015-12-10

This bug report is a duplicate of: Bug #1428404: fglrx-updates-core 2:14.501-0ubuntu1: fglrx-updates-core kernel module failed to build [Makefile: No such file or directory]. Edit Remove

This bug affects 1 person

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

Bug Description

I was trying to install kernel 4.2.6.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: fglrx-updates-core 2:15.200-0ubuntu0.5
ProcVersionSignature: Ubuntu 3.16.0-55.74~14.04.1-generic 3.16.7-ckt19
Uname: Linux 3.16.0-55-generic x86_64
NonfreeKernelModules: sep3_15 pax fglrx
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
DKMSKernelVersion: 4.2.6-040206-generic
Date: Fri Dec 11 00:25:37 2015
InstallationDate: Installed on 2015-04-29 (224 days ago)
InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
PackageVersion: 2:15.200-0ubuntu0.5
RelatedPackageVersions:
dpkg 1.17.5ubuntu5.5
apt 1.0.1ubuntu2.10
SourcePackage: fglrx-installer-updates
Title: fglrx-updates-core 2:15.200-0ubuntu0.5: fglrx-updates-core kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

benjamin button (canavaroski90) wrote on 2015-12-10:

DKMSBuildLog.txt Edit (767 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (3.7 KiB, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2015-12-11:

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