Ubuntu
nvidia-graphics-drivers package

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

Bug #1060405 reported by Tritus on 2012-10-02

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

nvidia-current driver installation finishes with the message: "SystemError: installArchives() failed"

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-current 195.36.24-0ubuntu1~10.04.3
ProcVersionSignature: Ubuntu 3.0.0-26.43~lucid1-generic 3.0.43
Uname: Linux 3.0.0-26-generic x86_64
Architecture: amd64
Date: Tue Oct 2 21:38:03 2012
DkmsStatus:
nvidia-current, 195.36.24: added
nvidia-173, 173.14.22: added
ErrorMessage: nvidia-current kernel module failed to build
InstallationMedia: Ubuntu 10.04.4 LTS "Lucid Lynx" - Release amd64 (20120214)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
PackageVersion: 195.36.24-0ubuntu1~10.04.3
ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-26-generic root=UUID=bfa6e57e-820e-4a7e-8eea-8032979401fa ro quiet splash
SourcePackage: nvidia-graphics-drivers
Title: package nvidia-current 195.36.24-0ubuntu1~10.04.3 failed to install/upgrade: nvidia-current kernel module failed to build
dmi.bios.date: 06/29/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.30
dmi.board.name: Z68 Pro3-M
dmi.board.vendor: ASRock
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:bvnAmericanMegatrendsInc.:bvrP2.30:bd06/29/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ68Pro3-M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
glxinfo: Error: [Errno 2] Нет такого файла или каталога
system:
distro: Ubuntu
codename: lucid
architecture: x86_64
kernel: 3.0.0-26-generic

Tags:

Revision history for this message

Tritus (tritus) wrote on 2012-10-02:

BootDmesg.txt Edit (56.7 KiB, text/plain; charset="utf-8")
CurrentDmesg.gz Edit (5.4 KiB, application/x-gzip)
DKMSBuildLog.txt Edit (978 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (1.3 KiB, text/plain; charset="utf-8")
GdmLog.txt Edit (3.1 MiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (1.8 MiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (12.3 MiB, text/plain; charset="utf-8")
Lspci.txt Edit (15.3 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (499 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (1.9 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (3.3 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (1.7 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (235 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (128.9 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (236.8 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (3.1 MiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (1.8 MiB, text/plain; charset="utf-8")
Xrandr.txt Edit (579 bytes, text/plain; charset="utf-8")
make.log.txt Edit (974 bytes, text/plain; charset="utf-8")
setxkbmap.txt Edit (304 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (17.2 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (47.7 KiB, text/plain; charset="utf-8")

Revision history for this message

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

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.