Axel Thimm wrote at about 23:04:05 +0300 on Wednesday, June 11, 2008:
> On Wed, Jun 11, 2008 at 01:21:23PM -0400, Jeffrey J. Kosowsky wrote:
> > O.K. I think I see the problem with nvidia. I always keep one older
> > kernel version just in case. Well, this older version has an nvidia
> > kmdl that is tied to 96.43.01. So, I guess that as long as the old
> > nvidia kmdl is still there, yum won't upgrade the nvidia-graphics
> > package from 96.43.01 to 96.43.05 so it then won't pull in the
> > corresponding kmdl for the new kernel.
>
> It would if you had nvidia-graphics-legacy-96xx installed. This
> automatically upgrades drivers within the 96* versioning scheme.
I just tried installing the rpm but it wants to remove for
dependencies one of my 2 older kernels (and associated kmdl's) and
upgrade my kernel to 2.6.25.
Interestingly, it wants to remove kernel-2.6.24.7-92.fc8 but NOT the
OLDER kernel-2.6.24.4-64.fc8 (which is actually the kernel that I am
running now).
Note that it doesn't try to remove the OLD module versions:
nvidia-graphics96.43.01-96.43.01-92.fc8
nvidia-graphics96.43.01-libs-96.43.01-92.fc8
So, two questions:
- Why doesn't this allow me to keep the older kernels without
upgrading the kernel?
(I'm not sure I followed your explanation below about the module
versioning working for the nvidia kmdl but only for 2.6.25)
- Why does it allow me to keep one kernel but not the other?
>
> > If that is indeed the case, is there any way to work around this so
> > that one can keep several versions of the kernel (and associated
> > kmdls) working. If not, this situation in a way defeats a lot of the
> > benefits of the kmdl system that separates out the kernel dependent
> > modules from the non-kernel dependent portions.
>
> The separations is there to allow several kernels to work with the
> same module version. E.g. one userspace of version X and many kmdls of
> version X but for kernel a, b, c etc.
>
> But you don't only shift the kernel version space (a,b,c, ...), but
> also the modules' (96.43.01 vs 96.43.05). Although even this is in
> principle supported solely for the nvidia drivers (and no other kmdl),
> there are only patches for 96.43.05 out there to make it work on
> 2.6.25.
>
> These patches may or may not also work with other 96* variants, but I
> didn't try to rebuild any. Until now no one ever complained about the
> legacy drivers, it's the top notch drivers that sometimes have a
> regression.
>
> Having said that if you find 96.43.05 to be broken in any way and
> 96.43.01 doing the job, I wouldn't mind to ship a patched 96.43.01.
> --
> Axel.Thimm at ATrpms.net
>
> [GNUPG:] ERRSIG 401552D4639A99F1 17 2 01 1213214644 9
> [GNUPG:] NO_PUBKEY 401552D4639A99F1
_______________________________________________
atrpms-users mailing list
[email protected]
http://lists.atrpms.net/mailman/listinfo/atrpms-users
