Ubuntu
fglrx-installer-experimental-9 package

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

Bug #1251465 reported by Daniel Ivanov on 2013-11-14

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

Was trying to install AMD driver on clean new Ubuntu 12.04.3 LTS.

Attached jockey.log

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: fglrx-experimental-9 2:9.010-0ubuntu0.3
ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5
Uname: Linux 3.8.0-29-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
DKMSKernelVersion: 3.8.0-29-generic
Date: Fri Nov 15 00:35:44 2013
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

Daniel Ivanov (sekanato) wrote on 2013-11-14:

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

Apport retracing service (apport) on 2013-11-14

tags:

removed: need-duplicate-check

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2013-11-15:

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