trying to install the proprietary nvidia driver via jockey fails shortly before finishing
ProblemType: Package
DistroRelease: Ubuntu 10.10
Package: nvidia-current 256.53-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic i686
Architecture: i386
DRM.card0.DVI.D.1:
status: disconnected
enabled: disabled
dpms: Off
modes:
edid-base64:
DRM.card0.LVDS.1:
status: connected
enabled: enabled
dpms: On
modes: 1920x1200 1920x1200 1920x1080 1600x1200 1680x1050 1400x1050 1280x1024 1280x960 1152x864 1024x768 800x600 640x480 720x400 640x400 640x350
edid-base64: AP///////wBMo1UyAAAAAAASAQOAIRV4Cof1lFdPjCcnUFQAAAABAQEBAQEBAQEBAQEBAQEBjEGAWHGwI0BkICYAS88QAAAZAAAADwAAAAAAAAAAAEbSAmQAAAAA/gBZMjg0RwAxNTRVMgogAAAA/gAXJy8/X5ev/wIBCiAgADk=
DRM.card0.VGA.1:
status: disconnected
enabled: disabled
dpms: Off
modes:
edid-base64:
Date: Tue Sep 7 14:29:17 2010
ErrorMessage: nvidia-current kernel module failed to build
MachineType: Dell Inc. Precision M4300
PackageVersion: 256.53-0ubuntu2
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-19-generic root=UUID=f957135d-b762-45ac-9e0d-6979595882aa ro quiet splash
SourcePackage: nvidia-graphics-drivers
Title: package nvidia-current 256.53-0ubuntu2 failed to install/upgrade: nvidia-current kernel module failed to build
dmi.bios.date: 05/23/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0UY141
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA11:bd05/23/2008:svnDellInc.:pnPrecisionM4300:pvr:rvnDellInc.:rn0UY141:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Precision M4300
dmi.sys.vendor: Dell Inc.
system:
distro: Ubuntu
codename: maverick
architecture: i686
kernel: 2.6.35-19-generic
Hey Daniel,
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.