Kmod-Nvidia Broken after a kernel update

[newmanium2001]

So, I guess I was foolish enough to update Fedora last night, and wouldn't you know it, I broke the **** out of it.

It seems the nvidia driver is not working because I get a really ugly screen of bars and colors. I've tried doing a "yum update" and another "yum install kmod-nvidia", but they keep saying that my nvidia driver is up to date. My kernel is 2.6.26 and the nvidia driver is 173.14.12-3.lvn9

After 2 hours of searching (which involves going into Windows, searching, then writing things down, then going back into Fedora), I'm about ready to give up. My patience is wearing extremely thin with this OS.

[Hlingler]

The kmod-nvidia package version has to match the kernel version - i.e., each kmod works for one and only one kernel version. Did you update the kmod-nvidia package along with the kernel? If not, simply re-boot, but at the GRUB screen, select the previous (older) kernel instead of the new one, until an updated kmod is available.

V

[newmanium2001]

I guess what I'm asking is, "is there an updated kmod-nvidia for the 2.6.26 kernel?" I've done a yum update, but it says there are no updates available. Does that definitively mean that there is no kmod-nvidia package for this kernel, or is there some other command I can run to check for an update?

[Hlingler]

Looks to me very much like Livna have not yet updated their kmod-nvidia to match newest kernel.

Alternative: install akmod-nvidia to build the kmod dynamically for you. Also requires kernel-devel to match kernel, plus latest kernel-headers packages (WARNING: they're large and take up much HDD space), so you don't have to wait. See "NVidia" link in my signature for more details.

V

[bob]

The kmod-nvidias are 3rd. party (livna) packages and are handled by individuals who may have some problem/emergency that holds up a release. I've got a separate thread going about the 96xx Fedora 8 kmod that's also not available and how I did a temporary fix.

Hlingler's got one solution for you, plus you can simply wait for the right kmod-nvidia to be released which should come in a day or two. And you can also exclude the kernels from the updates. Nothing says you have to give up on a great kernel just because a new one's out there. The new kmod would call up the new kernel once it's available, I believe.

[zargorn]

This happens quite often after a kernel update. The solution is to choose the old kernel during boot up (it is still installed by default) until the new kmod is available. The kmod will then be installed automatically (or by doing 'yum update' depending on your configuration).

My question is: Is there a way to tell yum to wait with the kernel update until all kernel modules are available (it used to do that)?

An advanced feature could be to notify the user ONLY if this blocks the kernel update for a longer time because a kmod does not get updated. Or yum could install the new kernel, but not make it the default kernel in grub until all kmods have been installed.

There seem to be a lot of people that have problems with yums default behaviour right now.

[bob]

I'm certainly not 'in the know' about how it works, but prior kernels have failed to install for me due to the lack of the kmod-nvidia. This time, it installed and simply deleted the existing mods, which was a pain. Something was left out of the normal formula, I'd guess.

[beer_hunter]

I'd suggest to remove the livna nvidia driver, install kernel-devel and then install freshrpms nvidia driver. it builds its kmod at installation time, so you can use this driver anytime new kernel comes up.

[jdeslip]

It has now been over a day since fedora pushed 2.6.26.3-29 kernel into the update repos, but there is still no kmod-nvidia from livna, which is unusual. Is the packager sick? Or is there a bigger problem with 2.6.26 kernel?

[beer_hunter]

As i wrote in some other thread, remove the livna nvidia driver and install the freshrpms one. It doesnt need to install kmod nvidia as it builds it during install process. (Make sure you have all needed packages for building ex. gcc and kernel-devel)

[jdeslip]

ya, the livna akmod does the same thing. But all these packages add a lot of bulk to my drive.

[beer_hunter]

So it seems packager is sick or he enjoy the weekend

[icydog]

Don't the livna kmods now use akmod, which builds the kmod without needing an update for each kernel? I have kmod-nvidia-2.6.26.3-29.fc9.x86_64-173.14.12-2.fc9.x86_64 installed, and it was built on my machine automatically apparently.

[Hlingler]

Regardless of whether you install Livna's akmod-nvidia or FreshRPMs nvidia-x11-drv, both will need the kernel-devel and kernel-headers packages (which are the big HDD space hogs) in order to build the kmod(s) for you on-the-spot. FreshRPMs system also requires the dkms package to build kmods. Six of one, a half-dozen of the other....

Personally, I prefer FreshRPMs nvidia-x11-drv and dkms.

Otherwise, there's simply no choice but to wait until someone builds and packages the updated kmod.

V

P.S. No problem here with nvidia-x11-drv-173.14.12 and kernel-2.6.26.3-14.fc8.

[pete_1967]

yum install akmod-nvidia

This automatically builds your nVidia kernel module for Livna's driver.