I installed updates last night, and although my 280.13 drivers work fine, I now do not have a working kernel module for VirtualBox. So I booted into my old kernel, and now the nvidia drivers tell me that they do not match the nvidia kernel module.
However, the old version of my nvidia drivers (275.09) was erased by last night's update and I had not turned on rpm caching for yum prior to downloading the 275.09 drivers in early July.
Please, how can I get access to the 275.09 drivers? I am missing work because of this.
---------- Post added at 03:20 PM ---------- Previous post was at 03:09 PM ----------
There seems to be a problem getting the VirtualBox kernel module working with the 2.6.40 kernel, as documented in these other threads: 1500929 1500568
so my only choice is to revert back to the 2.6.38 kernel, but now my nvidia drivers don't work with my old kernel. I guess since I had both the 2.6.38 nvidia kernel module installed AND the 2.6.40 kernel module installed, yum/rpm felt it was OK to upgrade the drivers to the 280.13 version, which do not work with my old 2.6.38 kernel/nvidia module.
---------- Post added at 04:05 PM ---------- Previous post was at 03:20 PM ----------
Sigh. I guess I will download the 275.09 drivers from nvidia and just install them over my rpms.
---------- Post added at 05:07 PM ---------- Previous post was at 04:05 PM ----------
So I got it working by downloading the drivers from nvidia and manually copying the .so files over my current .so files so that at least I could remove them and replace them using yum when the problem with VirtualBox gets fixed.
My day would have been so much easier if yum were configured by default to cache RPMs, OR if new rpms from rpmfusion could exist along side the old versions for a while, so that it would be possible to roll back.
Linear Mode
