fglrx 2:8.831-0ubuntu1: fglrx kernel module failed to build
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
fglrx-installer (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
sytem says it is installed but there is not the command chains or anything to show it is installed.
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: fglrx 2:8.951-0ubuntu1
ProcVersionSign
Uname: Linux 3.2.0-22-
.tmp.unity.
ApportVersion: 2.0-0ubuntu4
Architecture: i386
CompizPlugins: No value set for `/apps/
CompositorRunning: None
DKMSKernelVersion: 3.2.0-22-
Date: Sun Apr 8 21:42:26 2012
DistUpgraded: 2012-04-08 17:49:26,442 WARNING no activity on terminal for 240 seconds (Configuring rhythmbox-data)
DistroCodename: precise
DistroVariant: ubuntu
DkmsStatus: fglrx, 8.951: added
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
MachineType: MSI MS-6567
PackageVersion: 2:8.831-0ubuntu1
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: fglrx-installer
Title: fglrx 2:8.831-0ubuntu1: fglrx kernel module failed to build
UpgradeStatus: Upgraded to precise on 2012-04-08 (0 days ago)
dmi.bios.date: 02/01/02
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 07.00T
dmi.board.name: MS-6567
dmi.board.vendor: MSI
dmi.board.version: 0.0B
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Uknown Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: MS-6567
dmi.product.
dmi.sys.vendor: MSI
version.compiz: compiz 1:0.9.7.4-0ubuntu3
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.