package nvidia-current (not installed) failed to install/upgrade: nvidia-current kernel module failed to build

Bug #632797 reported by Nick Brady
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Running Nvidia 9600GT on Ubuntu 10.10

ProblemType: Package
DistroRelease: Ubuntu 10.10
Package: nvidia-current (not installed)
ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4
Uname: Linux 2.6.35-20-generic x86_64
Architecture: amd64
Date: Tue Sep 7 15:30:54 2010
DkmsStatus:
 dkms.conf: Error! No 'DEST_MODULE_LOCATION' directive specified.
 dkms.conf: Error! No 'PACKAGE_NAME' directive specified.
 dkms.conf: Error! No 'PACKAGE_VERSION' directive specified.
 nvidia-current, 256.52, 2.6.32-24-generic, x86_64: installed
ErrorMessage: nvidia-current kernel module failed to build
MachineType: Gigabyte Technology Co., Ltd. EP45-UD3R
PackageVersion: 256.53-0ubuntu2
ProcCmdLine: root=UUID=f6a65c40-2eaa-46c1-8974-76625979f455 ro quiet splash
SourcePackage: nvidia-graphics-drivers
Title: package nvidia-current (not installed) failed to install/upgrade: nvidia-current kernel module failed to build
dmi.bios.date: 04/16/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F9
dmi.board.name: EP45-UD3R
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.:bvrF9:bd04/16/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3R:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: EP45-UD3R
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
system:
 distro: Ubuntu
 codename: maverick
 architecture: x86_64
 kernel: 2.6.35-20-generic

Revision history for this message
Nick Brady (nickybrady) wrote :
Revision history for this message
bugbot (bugbot) wrote :

Hey Nick,

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.

Changed in nvidia-graphics-drivers (Ubuntu):
status: New → Incomplete
Revision history for this message
Nick Brady (nickybrady) wrote :

I think this was a hardware related issue. You can close this ticket please.

Changed in nvidia-graphics-drivers (Ubuntu):
status: Incomplete → Opinion
status: Opinion → Fix Committed
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

closing, thanks.

Changed in nvidia-graphics-drivers (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.