Re: still problems with updating kernels + nvidia drivers

2012/11/11 Neal Becker <ndbecker2(a)gmail.com&gt;: Actually the kmod was pushed "before" the new kernel by misstake. So this should have been the opposite. There are several problems that might be fixed: - The rpmfusion mirror your've used might not be updated in time - Mirrormanager doesn't remove outdated mirrors from the list. - Your rpmfusion yum metadata cache doesn't get renewed at the same time as the fedora one. Anyway we cannot be sure to have the kernel and kmod push at the exact same time, we can only try to reduce the time, when both appears. Then this could be fixed at the rpm/yum level, by a specialized yum plugins. One way I was thinking was to fetch the matching kmod from rpmfusion-*-updates-testing instead. Others suggested to disable the new kernel update to stay on the previous kernel. But this problem is discussed from time to time, then nothing stays. So someone really need to sort out some specification about describing the problem and how to solve it. This could start from the rpmfusion wiki. Users could be advertised to use akmod- instead. But this is unlikely to solve thing in a secure boot environnement if we manage to sign the kernel modules. The shortest plan for nvidia, could be to make a validation test, and to be abble to disable nvidia when the module isn't present. Nicolas (kwizart)