package nvidia-173 173.14.22-0ubuntu11 failed to install/upgrade: nvidia-173 kernel module failed to build
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nvidia-graphics-drivers-173 (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
After upgrading the kernel, the package failed to update.
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-173 173.14.22-0ubuntu11
ProcVersionSign
Uname: Linux 2.6.32-32-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Mon Jun 6 10:16:33 2011
DkmsStatus:
vboxhost, 4.0.8, 2.6.32-32-generic, x86_64: installed
vboxhost, 4.0.8, 2.6.38-10-generic, x86_64: installed
nvidia-current, 195.36.24, 2.6.32-32-generic, x86_64: installed
nvidia-173, 173.14.22, 2.6.32-32-generic, x86_64: installed
ErrorMessage: nvidia-173 kernel module failed to build
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
PackageVersion: 173.14.22-0ubuntu11
ProcCmdLine: BOOT_IMAGE=
SourcePackage: nvidia-
Title: package nvidia-173 173.14.22-0ubuntu11 failed to install/upgrade: nvidia-173 kernel module failed to build
dmi.bios.date: 01/05/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080015
dmi.board.
dmi.board.name: MI-A78S-8209
dmi.board.vendor: XFX
dmi.board.version: Ver1.1
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: To Be Filled By O.E.M.
dmi.product.
dmi.sys.vendor: To Be Filled By O.E.M.
system:
distro: Ubuntu
codename: lucid
architecture: x86_64
kernel: 2.6.32-32-generic
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 #576648, 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.