package fglrx 2:8.801-0ubuntu2 failed to install/upgrade: fglrx kernel module failed to build
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
fglrx-installer (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Dist upgrade from Maverick to Natty.
ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: fglrx 2:8.801-0ubuntu2
ProcVersionSign
Uname: Linux 2.6.35-25-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Sat Jan 29 17:44:53 2011
DistUpgraded: Yes, recently upgraded Log time: 2011-01-29 13:53:53.109710
DistroCodename: natty
DistroVariant: ubuntu
DkmsStatus:
virtualbox-ose, 3.2.12, 2.6.35-25-generic, x86_64: installed
fglrx, 8.801, 2.6.35-25-generic, x86_64: installed
ErrorMessage: fglrx kernel module failed to build
GraphicsCard: Subsystem: ASUSTeK Computer Inc. M4A785TD Motherboard [1043:83a2]
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
MachineType: System manufacturer System Product Name
PackageVersion: 2:8.801-0ubuntu2
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: fglrx-installer
Title: package fglrx 2:8.801-0ubuntu2 failed to install/upgrade: fglrx kernel module failed to build
dmi.bios.date: 06/18/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2103
dmi.board.
dmi.board.name: M4A785TD-V EVO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: System Product Name
dmi.product.
dmi.sys.vendor: System manufacturer
version.
version.libdrm2: libdrm2 2.4.23-1ubuntu3
version.
version.
version.
version.
version.
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 #709719, 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.