Ubuntu
fglrx-installer-experimental-9 package

fglrx-experimental-9 2:9.010-0ubuntu0.3: fglrx-experimental-9 kernel module failed to build

Bug #1231959 reported by Jaime Cruz on 2013-09-27

This bug report is a duplicate of: Bug #1176429: fglrx-updates 2:9.000-0ubuntu0.3: fglrx-updates kernel module failed to build [kcl_acpi.c:779:58: error: ‘struct dev_archdata’ has no member named ‘acpi_handle’]. Edit Remove

This bug affects 1 person

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

Bug Description

Problem occurred when applying latest updates this morning.

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: fglrx-experimental-9 2:9.010-0ubuntu0.3
ProcVersionSignature: Ubuntu 3.5.0-40.62~precise1-generic 3.5.7.20
Uname: Linux 3.5.0-40-generic x86_64
NonfreeKernelModules: wl fglrx
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: amd64
DKMSKernelVersion: 3.8.0-31-generic
Date: Fri Sep 27 08:15:25 2013
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213)
MarkForUpload: True
PackageVersion: 2:9.010-0ubuntu0.3
SourcePackage: fglrx-installer-experimental-9
Title: fglrx-experimental-9 2:9.010-0ubuntu0.3: fglrx-experimental-9 kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Jaime Cruz (jaime-cruz) wrote on 2013-09-27:

DKMSBuildLog.txt Edit (1.2 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.9 KiB, text/plain; charset="utf-8")
DuplicateSignature.txt Edit (1.2 KiB, text/plain; charset="utf-8")

Apport retracing service (apport) on 2013-09-27

tags:

removed: need-duplicate-check

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2013-09-30:

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