On Mon, 2006-06-12 at 20:24 +1000, Danny Yee wrote: > Thorsten Leemhuis wrote: > > Anyway: The plugin doesn't remove the currently running kernel, which > > means in this case: there was no nvidia-kernel-module for the current > > kernel installed. > > You're right! I was running an older version of the kernel. It looks > like the nvidia-kernel-module for my running kernel got removed at > some point... presumably everything will work fine until I try to > reboot (unless I reboot with the newer kernel that has the module). > It got removed _when yum did the update_. Your lines that said it erased the modules show when it was removed. > I fixed the problem by manually installing the new kernel, then > yum updating. I always do a manual yum update, then when I know the kernel has been updated I also do a manual install of the newer kmod-nvidia package to match (when it is available). This prevents the erasing of the older module which an update would do (as you saw) and leaves me able to boot to either kernel with X functional. > > Updating kernel modules using yum seems to work better with livna's new > kmod- naming approach, but it would be nice if yum could be configured > not to switch to newer kernels until all modules were updated as well. > Yum does *not* switch to the newer kernel. It installs it when available but does not switch to it. Your reboot activates the new kernel. > Danny. > --------------------------------------------------------- > http://dannyreviews.com/ - over nine hundred book reviews > http://danny.oz.au/ - civil liberties, travel tales, blog > --------------------------------------------------------- > -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
