package nvidia-current 256.44-0ubuntu1 failed to install/upgrade: nvidia-current kernel module failed to build
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nvidia-graphics-drivers (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
This happened while installing http://
ProblemType: Package
DistroRelease: Ubuntu 10.10
Package: nvidia-current 256.44-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.35-15-generic i686
NonfreeKernelMo
.proc.driver.
NVRM version: NVIDIA UNIX x86 Kernel Module 256.44 Thu Jul 29 01:30:36 PDT 2010
GCC version: gcc version 4.4.5 20100816 (prerelease) (Ubuntu/Linaro 4.4.4-9ubuntu1)
Architecture: i386
Date: Wed Aug 25 08:15:57 2010
DkmsStatus:
nvidia-current, 256.44, 2.6.35-14-generic, i686: installed
nvidia-current, 256.44, 2.6.35-15-generic, i686: installed
ErrorMessage: nvidia-current kernel module failed to build
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100803.1)
MachineType: Gigabyte Technology Co., Ltd. G41M-ES2L
PackageVersion: 256.44-0ubuntu1
ProcCmdLine: BOOT_IMAGE=
SourcePackage: nvidia-
Title: package nvidia-current 256.44-0ubuntu1 failed to install/upgrade: nvidia-current kernel module failed to build
dmi.bios.date: 07/22/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F4
dmi.board.name: G41M-ES2L
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:bvnAwardSof
dmi.product.name: G41M-ES2L
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
glxinfo: Error: [Errno 2] No such file or directory
nvidia-settings:
system:
distro: Ubuntu
codename: maverick
architecture: i686
kernel: 2.6.35-15-generic
Hey Charles,
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.