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
Crash while I update even if I use the proper kernel version (2.6.32.38)
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-173 173.14.22-0ubuntu11
ProcVersionSign
Uname: Linux 2.6.32-38-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Thu Jan 26 10:42:58 2012
DkmsStatus:
blcr, 0.8.2, 2.6.32-33-generic, x86_64: installed
blcr, 0.8.2, 2.6.32-38-generic, x86_64: installed
nvidia-current, 195.36.24, 2.6.32-38-generic, x86_64: installed
nvidia-current, 195.36.24, 2.6.35-31-generic, x86_64: installed
nvidia-173, 173.14.22, 2.6.32-33-generic, x86_64: installed
ErrorMessage: nvidia-173 kernel module failed to build
InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 (20110720.1)
MachineType: System manufacturer System Product Name
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: 07/28/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0209
dmi.board.
dmi.board.name: P7P55D EVO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
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
glxinfo: Error: [Errno 2] No such file or directory
system:
distro: Ubuntu
codename: lucid
architecture: x86_64
kernel: 2.6.32-38-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.