fglrx 2:8.930-0ubuntu1: fglrx kernel module failed to build
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
fglrx-installer (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I have tried the catalyst 12.03 from AMD site but got exactly the same error.
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: fglrx 2:8.930-0ubuntu1
ProcVersionSign
Uname: Linux 3.2.0-23-
.tmp.unity.
.tmp.unity.
ApportVersion: 2.0.1-0ubuntu5
Architecture: i386
CompizPlugins: No value set for `/apps/
CompositorRunning: compiz
DKMSKernelVersion: 3.2.0-23-
Date: Thu Apr 19 10:59:29 2012
DistUpgraded: 2012-04-12 13:59:23,328 DEBUG enabling apt cron job
DistroCodename: precise
DistroVariant: ubuntu
DkmsStatus: fglrx, 8.930: added
GraphicsCard:
Advanced Micro Devices [AMD] nee ATI RV710 [Radeon HD 4350] [1002:954f] (prog-if 00 [VGA controller])
Subsystem: Device [1642:3879]
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
MachineType: LENOVO QiTianM7100
PackageVersion: 2:8.930-0ubuntu1
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: fglrx-installer
Title: fglrx 2:8.930-0ubuntu1: fglrx kernel module failed to build
UpgradeStatus: Upgraded to precise on 2012-04-12 (6 days ago)
dmi.bios.date: 12/25/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 90KT11CUS
dmi.board.
dmi.board.name: To be filled by O.E.M.
dmi.board.vendor: LENOVO
dmi.board.version: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: QiTianM7100
dmi.product.
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.7.6-0ubuntu1
version.libdrm2: libdrm2 2.4.32-1ubuntu1
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 947871, 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.