Ubuntu
nvidia-graphics-drivers-173 package

package nvidia-173 173.14.22-0ubuntu11 failed to install/upgrade: nvidia-173 kernel module failed to build

Bug #621465 reported by Cesar Luis Medina on 2010-08-20

This bug report is a duplicate of: Bug #576648: package nvidia-* failed to install/upgrade: nvidia-* kernel module failed to build (Unable to determine the target kernel version.). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	nvidia-graphics-drivers-173 (Ubuntu)	New	Undecided	Unassigned

Bug Description

Me sucedió instalando la actualización de Kermel.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-173 173.14.22-0ubuntu11
ProcVersionSignature: Ubuntu 2.6.32-24.41-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Fri Aug 20 20:00:53 2010
ErrorMessage: nvidia-173 kernel module failed to build
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
Lsusb:
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: MSI MS-7309
PackageVersion: 173.14.22-0ubuntu11
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-24-generic root=UUID=5d8b8fdd-a4b3-4616-8735-c805657600da ro quiet splash
SourcePackage: nvidia-graphics-drivers-173
Title: package nvidia-173 173.14.22-0ubuntu11 failed to install/upgrade: nvidia-173 kernel module failed to build
dmi.bios.date: 08/31/2007
dmi.bios.vendor: MS-7309
dmi.bios.version: V1.9
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: MS-7309
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnMS-7309:bvrV1.9:bd08/31/2007:svnMSI:pnMS-7309:pvr1.0:rvnMSI:rnMS-7309:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: MS-7309
dmi.product.version: 1.0
dmi.sys.vendor: MSI
glxinfo: Error: [Errno 2] No existe el archivo o directorio
system:
distro: Ubuntu
codename: lucid
architecture: i686
kernel: 2.6.32-24-generic

Tags:

Revision history for this message

Cesar Luis Medina (cesarlm05) wrote on 2010-08-20:

BootDmesg.txt Edit (41.6 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (3.5 KiB, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (977 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (1.3 KiB, text/plain; charset="utf-8")
DkmsStatus.txt Edit (523 bytes, text/plain; charset="utf-8")
GdmLog.txt Edit (9.9 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (10.1 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (10.2 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (21.5 KiB, text/plain; charset="utf-8")
PciDisplay.txt Edit (1.9 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.8 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (231 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (92.1 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (206.4 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (213 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (12.7 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (13.1 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (6.8 KiB, text/plain; charset="utf-8")
make.log.txt Edit (977 bytes, text/plain; charset="utf-8")
setxkbmap.txt Edit (236 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (22.0 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (47.3 KiB, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2011-05-31:

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.