On Tue, 2008-03-25 at 11:25 +1100, Peter McNeil wrote:
> For some reason the update to a new kernel seems to randomly point to a
> kernel to boot by default which would be OK but the livna nvidia setup
> breaks the older kernels nvidia module, so you need to make sure you
> boot on the latest kernel by default (by editing /etc/grub.conf to point
> to the latest kernel).
Generally, it doesn't. There's a glitch when installing a new kernel
results in installing a new version of the nVidia driver.
>
> The "solution" is to install the nvidia module manually from the nvidia
> site download, which is not really a simple option.
...which has its own problems.
Search the archives of this list for how to rebuild new Livna nvidia
packages for the old kernel.
>
>
>
> David Kramer wrote:
> > I simply don't understand why this is the case, but every time I
> > upgrade the . After some updates, the symlinks point to the wrong
> > version, etc. But I will only address my current situation. This is
> > on a Dell D820.
> >
> > Currently running the newly-installed 2.6.24.3-34 kernel.
> >
> > [...]
> >
> > Thanks for any advice you can offer.
> >
>
>
--
Matthew Saltzman
Clemson University Math Sciences
mjs AT clemson DOT edu
http://www.math.clemson.edu/~mjs
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
