nvidia drivers 185.xx compile into kernel 2.6.28 instead of 2.6.31 on update from jaunty to karmic
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Release Notes for Ubuntu |
Invalid
|
Undecided
|
Unassigned | ||
dkms (Ubuntu) |
Fix Released
|
Critical
|
Alberto Milone | ||
Lucid |
Fix Released
|
Critical
|
Alberto Milone | ||
nvidia-graphics-drivers-173 (Ubuntu) |
Fix Released
|
Critical
|
Alberto Milone | ||
Lucid |
Fix Released
|
Critical
|
Alberto Milone | ||
nvidia-graphics-drivers-180 (Ubuntu) |
Fix Released
|
Critical
|
Alberto Milone | ||
Lucid |
Fix Released
|
Critical
|
Alberto Milone | ||
nvidia-graphics-drivers-96 (Ubuntu) |
Fix Released
|
Critical
|
Alberto Milone | ||
Lucid |
Fix Released
|
Critical
|
Alberto Milone |
Bug Description
I did not find an existing bug report on this issue even though certain other reports exist regarding the nvidia-185 package that affect me, so I am filing a new one. While upgrading from jaunty to the karmic RC (on the 28th of October, a day before the final release), during the installation of nvidia-185 (upgrading from nvidia-180.xx, the latest on jaunty), I got a warning message to the effect "this driver has no modules in kernel 2.6.31, installing in 2.6.28", and installation continued in the existing 2.6.28 kernel I had; this sound like a potential problem to me, since I (and I am sure many others) do not like to keep older kernels on the system. I am therefore inclined to believe this is a packaging bug in the existing nvidia drivers (185.xx) available in the karmic upgrade. I did not save the log, since I had never filed a bug report and I was all too excited to check out what karmic was like (the upgrade did complete with a few hiccups), but I believe that the problem is completely reproducible from a system with the latest nvidia drivers (180.xx) in jaunty and running kernel 2.6.28, upon an upgrade. I am not aware if this issue has been fixed in the current version of karmic.
After the upgrade I was plagued by the "powermizer" problem in:
https:/
which is a different story altogether, and probably unrelated to the issue at hand. I am inclined to think that the nvidia driver v185.xx is itself the cause of this and until replaced by the newer 190.xx it will continue to be so.
(While filing this report, for some reason I was unable to select nvidia-
affects: | ubuntu → nvidia-graphics-drivers-180 (Ubuntu) |
Changed in nvidia-graphics-drivers-180 (Ubuntu): | |
status: | Incomplete → Triaged |
importance: | Undecided → Critical |
Changed in nvidia-graphics-drivers-173 (Ubuntu): | |
status: | In Progress → Confirmed |
status: | Confirmed → Fix Committed |
status: | Fix Committed → In Progress |
assignee: | Alberto Milone (albertomilone) → piero (petercrue) |
Changed in nvidia-graphics-drivers-173 (Ubuntu): | |
assignee: | piero (petercrue) → Alberto Milone (albertomilone) |
tags: | added: karmic |
tags: | added: jaunty |
Changed in ubuntu-release-notes: | |
status: | New → Invalid |
tags: | added: patch-accepted-upstream |
tags: | added: jaunty2karmic |
Okay, you've mentioned a few different problems, it is generally best to focus just one issue per bug report. The powermizer bug obviously already has a bug report. The 180/185 confusion is just that - we left the package in launchpad named 180 even though the driver itself is 185 (we didn't care to have to move all the bug reports from package to package); we'll fix the naming to not show numbers in lucid.
Anyway, so let's focus this just to the unique issue mentioned in the title. My guess is that the driver failed to *build* against the 2.6.31 kernel, rather than that it is failing during install. Could you please find and attach your build log for nvidia? The file will be found someplace like:
/var/lib/ dkms/nvidia/ 185.18. 36/build/ make.log
The numbered directory may be different depending on what version you have installed, but if you poke around it should be somewhere like that.