package nvidia-current 256.53-0ubuntu1 failed to install/upgrade: nvidia-current kernel module failed to build
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nvidia-graphics-drivers (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
I ran the command:
sudo apt-get update; sudo apt-get upgrade
And received this error.
Maverick 10.10
Linux duanedesign-laptop 2.6.35-19-generic #28-Ubuntu SMP Sun Aug 29 06:34:38 UTC 2010 x86_64 GNU/Linux
nvidia-current:
Installed: 256.53-0ubuntu1
Candidate: 256.53-0ubuntu1
Version table:
*** 256.53-0ubuntu1 0
500 http://
100 /var/lib/
I ran apt-get install -f to try and fix the partial install.
-------- Uninstall Beginning --------
Module: nvidia-current
Version: 256.53
Kernel: 2.6.35-19-generic (x86_64)
-------
Status: Before uninstall, this module version was ACTIVE on this kernel.
nvidia-current.ko:
- Uninstallation
- Deleting from: /lib/modules/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
depmod....
DKMS: uninstall Completed.
-------
Deleting module version: 256.53
completely from the DKMS tree.
-------
Done.
Loading new nvidia-
Building for 2.6.35-19-generic and 2.6.36-
Building for architecture x86_64
Building initial module for 2.6.35-19-generic
Done.
nvidia-current.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/
depmod....
DKMS: install Completed.
Building initial module for 2.6.36-
patch: **** malformed patch at line 5: static struct file_operations nv_fops = {
Error! Application of patch nvidia-
Check /var/lib/
dpkg: error processing nvidia-current (--configure):
subprocess installed post-installation script returned error exit status 6
ProblemType: Package
DistroRelease: Ubuntu 10.10
Package: nvidia-current 256.53-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.35-19-generic x86_64
NonfreeKernelMo
.proc.driver.
NVRM version: NVIDIA UNIX x86_64 Kernel Module 256.44 Thu Jul 29 01:22:44 PDT 2010
GCC version: gcc version 4.4.5 20100824 (prerelease) (Ubuntu/Linaro 4.4.4-9ubuntu2)
Architecture: amd64
Date: Fri Sep 3 21:48:56 2010
DkmsStatus: nvidia-current, 256.53, 2.6.35-19-generic, x86_64: installed
ErrorMessage: nvidia-current kernel module failed to build
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
MachineType: Hewlett-Packard HP G60 Notebook PC
PackageVersion: 256.53-0ubuntu1
ProcCmdLine: BOOT_IMAGE=
SourcePackage: nvidia-
Title: package nvidia-current 256.53-0ubuntu1 failed to install/upgrade: nvidia-current kernel module failed to build
dmi.bios.date: 08/18/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.54
dmi.board.name: 303C
dmi.board.vendor: Wistron
dmi.board.version: 08.60
dmi.chassis.type: 10
dmi.chassis.vendor: Wistron
dmi.chassis.
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP G60 Notebook PC
dmi.product.
dmi.sys.vendor: Hewlett-Packard
system:
distro: Ubuntu
codename: maverick
architecture: x86_64
kernel: 2.6.35-19-generic
Hey duanedesign,
Thanks for testing maverick during its development period. Unfortunately it looks like this bug report didn't get attention during the maverick development period. But I see there's not been more comments on the bug since the release, which makes me wonder if this is still an issue for you?
If you've not seen this issue since maverick's release yourself, it may have been solved by kernel or X or other updates that occurred late in the release; if so, would you mind please closing the bug for us? Go to the URL mentioned in this bug report, click the yellow icon(s) in the status column and set to 'Fix Released'.
If you no longer have the hardware needed to reproduce the problem, or otherwise feel the bug no longer needs tracked in Launchpad, you can set the status to 'Invalid'.
If you are the original reporter and still have this issue, just reply to this email saying so. (Or set the bug status to Confirmed.) If you are able to re-test this against 11.04 Natty Narwhal (our current development focus) and find the issue still affects Natty, please also run 'apport-collect <bug-number>' while running natty, which will add fresh logs and debug data, and flag it for the Ubuntu-X development team to look at.