On 12/16/2009 06:49 PM, Eli Wapniarski wrote: > The problem with the rpmfusion installation is that they are usually a bit behind the kernel updates. So, if you've updated your kernel and then rebooted before your computer has been updated to the matching rpmfusion builds, its very likely that your xorg.conf is loading the vesa driver. > That is what akmod-nvidia is for. Builds the module for the current kernel if it is not there on boot. [boutilpj at hplaptop TV]$ yum info akmods akmod-nvidia Loaded plugins: refresh-packagekit Available Packages Name : akmod-nvidia Arch : x86_64 Version : 190.42 Release : 1.fc12.4 Size : 5.7 M Repo : rpmfusion-nonfree-updates Summary : Akmod package for nvidia kernel module(s) URL : http://www.nvidia.com/ License : Redistributable, no modification permitted Description: This package provides the akmod package for the nvidia kernel modules. Name : akmods Arch : noarch Version : 0.3.6 Release : 3.fc12 Size : 16 k Repo : rpmfusion-free Summary : Automatic kmods build and install tool URL : http://rpmfusion.org/Packaging/KernelModules/Akmods License : MIT Description: Akmods startup script will rebuild akmod packages during system : boot while its background daemon will build them for kernels right : after they were installed. > Eli > > On Thursday 17 December 2009 00:43:20 Colin J Thomson - G6AVK wrote: >> Hi, >> >> Out of curiosity, >> I am using rpmfusions Nvidia drivers but I can't get any of KDE's desktop >> effects to work, everything else seems fine. Is this a known problem? >> >> All was fine in F11, I've tried to search for some info but no luck so >> far. >> >> Clean install - F12/KDE-4.3.4 >> >> Cheers >> >> Colin >> >
