fglrx 2:8.960-0ubuntu1: fglrx kernel module failed to build
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
fglrx-installer (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
fglrx kernel module failed to build
Distro: Ubuntu 12.10 Quantal Quetzal
Package: fglrx 2:8.960-0ubuntu1
ProblemType: Package
DistroRelease: Ubuntu 12.10
Package: fglrx 2:8.960-0ubuntu1
ProcVersionSign
Uname: Linux 3.5.0-9-generic x86_64
ApportVersion: 2.5.1-0ubuntu3
Architecture: amd64
DKMSKernelVersion: 3.5.0-13-generic
Date: Wed Aug 29 19:42:23 2012
DistUpgraded: 2012-08-20 21:31:47,296 DEBUG enabling apt cron job
DistroCodename: quantal
DistroVariant: ubuntu
DkmsStatus: fglrx, 8.960, 3.2.0-26-generic, x86_64: installed
GraphicsCard:
Advanced Micro Devices [AMD] nee ATI Barts PRO [Radeon HD 6800 Series] [1002:6739] (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:03aa]
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
MachineType: Gigabyte Technology Co., Ltd. GA-870A-UD3
PackageVersion: 2:8.960-0ubuntu1
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: fglrx-installer
Title: fglrx 2:8.960-0ubuntu1: fglrx kernel module failed to build
UpgradeStatus: Upgraded to quantal on 2012-08-20 (8 days ago)
dmi.bios.date: 10/17/2011
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: FEe
dmi.board.name: GA-870A-UD3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSof
dmi.product.name: GA-870A-UD3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.8+
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.38-0ubuntu2
version.
version.
version.
version.
version.
version.
version.
version.
tags: | removed: need-duplicate-check |
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 1025488, 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.