Ubuntu
nvidia-graphics-drivers package

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

Bug #732122 reported by Skiter on 2011-03-09

This bug report is a duplicate of: Bug #581045: package nvidia-* failed to install/upgrade: nvidia-* kernel module failed to build (FATAL: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol 'xen_features') [Lucid on kernel 2.6.32-22]. Edit Remove

This bug affects 1 person

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

Bug Description

Problem by upgrading the sistem

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-current 195.36.24-0ubuntu1~10.04
ProcVersionSignature: Ubuntu 2.6.32-29.58-generic-pae 2.6.32.28+drm33.13
Uname: Linux 2.6.32-29-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Wed Mar 9 16:50:23 2011
ErrorMessage: nvidia-current kernel module failed to build
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: Gigabyte Technology Co., Ltd. EP41-UD3L
PackageVersion: 195.36.24-0ubuntu1~10.04
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-29-generic-pae root=UUID=d2f09a37-fa96-4d82-b8ee-4f428c383262 ro quiet splash
SourcePackage: nvidia-graphics-drivers
Title: package nvidia-current 195.36.24-0ubuntu1~10.04 failed to install/upgrade: nvidia-current kernel module failed to build
dmi.bios.date: 11/06/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F5
dmi.board.name: EP41-UD3L
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd11/06/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP41-UD3L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP41-UD3L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: EP41-UD3L
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
glxinfo: Error: [Errno 2] No existe el fichero o el directorio
system:
distro: Ubuntu
codename: lucid
architecture: i686
kernel: 2.6.32-29-generic-pae

Tags:

Revision history for this message

Skiter (skiter-skitergia) wrote on 2011-03-09:

BootDmesg.txt Edit (42.2 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (7.8 KiB, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (97.2 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.3 KiB, text/plain; charset="utf-8")
DkmsStatus.txt Edit (2.6 KiB, text/plain; charset="utf-8")
GdmLog.txt Edit (9.9 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (10.2 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (10.2 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (20.0 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (512 bytes, 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.5 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.5 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (231 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (107.5 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (223.7 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (1.7 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (12.9 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (13.3 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (8.1 KiB, text/plain; charset="utf-8")
make.log.txt Edit (97.2 KiB, text/plain; charset="utf-8")
setxkbmap.txt Edit (233 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (22.0 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (57.0 KiB, text/plain; charset="utf-8")

Revision history for this message

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

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 #581045, 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.