> True, there is a lot that Nvidia screws up that I don't even realize. After > several years of using the proprietary Nvidia file, it's almost second > nature to reboot in init 3, run the script, and reboot to init 5 with thing > working again. As cool as KDE 4.2 is, and as much as I appreciate being > able to use it, mucking with the Nvidia script is a price I'm willing to > pay, even given that it is not the best option. > > Cheers, > Gar What sort of problems did you encounter with the kmod-route? I use rpms from the Livna repo for years without any problems. Sometimes it take a while before the latest drivers are released. This was e.g. the case with the transition from the 177.x.x series to the 180.x series. Maybe their 'merge' had something to do with it, but I was impatient :-) Version 180.22 was known to have solved the 'Openoffice.org' 'flickering problem' under KDE 4. So I decided to use the latest Nvidia drivers. I set up a local build environment - installed rpmdevtools and the rpm-fusion build packages -, picked the source rpm from Livna/rpmfusion.org, and edited the spec file to get the latest Nvidia source build. I installed the libs, kernel module and the akmod package, so the 'new kernel' problem wouldn't exist. Very nice is that no system files are getting overwritten - the problem Kevin Kofler mentioned - and when the rpm-fusion guys come up with their builds they will overwrite mine, so that I have always the latest version :-) Hope this can help you. Martin Kho _______________________________________________ The problem I was having was that when I used kmod-nvida from rpm-fusion and enabled desktop effects, my session immediately crashed as soon as I applied the change. When I switched to the nvida script, desktop effects works without either an immediate or delayed crash. Since it works, and I really enjoy KDE4.2, I switched to what allows me to work. Cheers, Gar
