package nvidia-173 173.14.27-0ubuntu1 failed to install/upgrade: nvidia-173 kernel module failed to build

[Aislan Jefferson de Souza Brito]

Failed to install driver on linux-rt kernel

ProblemType: Package
DistroRelease: Ubuntu 10.10
Package: nvidia-173 173.14.27-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.31-11.154-rt
Uname: Linux 2.6.31-11-rt i686
Architecture: i386
Date: Sun Aug 29 12:52:52 2010
DkmsStatus: nvidia-173, 173.14.27: added
ErrorMessage: nvidia-173 kernel module failed to build
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
PackageVersion: 173.14.27-0ubuntu1
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-11-rt root=UUID=edea54d5-4c06-4711-8ac8-76ab472cc3a5 ro splash quiet vga=786 quiet splash acpi=ht
SourcePackage: nvidia-graphics-drivers-173
Title: package nvidia-173 173.14.27-0ubuntu1 failed to install/upgrade: nvidia-173 kernel module failed to build
dmi.bios.date: 06/15/2006
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1006.002
dmi.board.name: P4S800D-X
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1006.002:bd06/15/2006:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASUSTeKComputerINC.:rnP4S800D-X:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
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.
system:
 distro: Ubuntu
 codename: maverick
 architecture: i686
 kernel: 2.6.31-11-rt

[bugbot (bugbot)]

Hey Aislan,

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.

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.