Ubuntu
nvidia-graphics-drivers package

package nvidia-current 195.36.24-0ubuntu1~10.04.1 failed to install/upgrade: nvidia-current kernel module failed to build

Bug #966905 reported by Mike Torelli on 2012-03-28

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 (Ubuntu)	New	Undecided	Unassigned

Bug Description

Update failed...no further informations...

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-current 195.36.24-0ubuntu1~10.04.1
ProcVersionSignature: Ubuntu 3.0.0-17.30~lucid1-generic 3.0.22
Uname: Linux 3.0.0-17-generic i686
Architecture: i386
Date: Wed Mar 28 00:43:35 2012
ErrorMessage: nvidia-current kernel module failed to build
InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110720.1)
MachineType: SAMSUNG ELECTRONICS CO., LTD. N510
PackageVersion: 195.36.24-0ubuntu1~10.04.1
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-17-generic root=UUID=6acf518d-497f-4582-87d1-7988269044b9 ro quiet splash
SourcePackage: nvidia-graphics-drivers
Title: package nvidia-current 195.36.24-0ubuntu1~10.04.1 failed to install/upgrade: nvidia-current kernel module failed to build
dmi.bios.date: 01/25/2010
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 03MU.M009.20100125.LDG
dmi.board.name: N510
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr03MU.M009.20100125.LDG:bd01/25/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnN510:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnN510:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
dmi.product.name: N510
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
glxinfo: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
system:
distro: Ubuntu
codename: lucid
architecture: i686
kernel: 3.0.0-17-generic

Tags:

Revision history for this message

Mike Torelli (dr-devil) wrote on 2012-03-28:

BootDmesg.txt Edit (58.7 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (5.5 KiB, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (979 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (1.3 KiB, text/plain; charset="utf-8")
DkmsStatus.txt Edit (343 bytes, text/plain; charset="utf-8")
GdmLog.txt Edit (21.0 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (21.2 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (21.1 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (20.7 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (363 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (1.1 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.1 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (233 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (117.9 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (268.1 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (24.6 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (25.2 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (570 bytes, text/plain; charset="utf-8")
make.log.txt Edit (975 bytes, text/plain; charset="utf-8")
setxkbmap.txt Edit (233 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (2.5 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (57.1 KiB, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2012-03-29:

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.