I don't understand why yum doesn't want to install updates when a new kernel is available:
sudo yum update ... ---> Package kernel.x86_64 0:3.16.7-200.fc20 will be installed ... [nothing about kmod-nvidia-blah]
** yum wants to update kernel **
rpm -qa kmod-nvidia* kmod-nvidia-304xx-3.16.6-203.fc20.x86_64-304.123-1.fc20.16.x86_64
** kmod-nvidia 3.16.6-203 is already installed **
yum info kmod-nvidia* ... Name : kmod-nvidia-304xx-3.16.7-200.fc20.x86_64 Arch : x86_64 Version : 304.123 Release : 1.fc20.17
** OK, there it is! The kmod I need for the new kernel. So why doesn't yum want to install it?
On Sat, 2014-11-08 at 19:01 -0500, Neal Becker wrote:
I don't understand why yum doesn't want to install updates when a new kernel is available:
sudo yum update ... ---> Package kernel.x86_64 0:3.16.7-200.fc20 will be installed ... [nothing about kmod-nvidia-blah]
** yum wants to update kernel **
rpm -qa kmod-nvidia* kmod-nvidia-304xx-3.16.6-203.fc20.x86_64-304.123-1.fc20.16.x86_64
** kmod-nvidia 3.16.6-203 is already installed **
yum info kmod-nvidia* ... Name : kmod-nvidia-304xx-3.16.7-200.fc20.x86_64 Arch : x86_64 Version : 304.123 Release : 1.fc20.17
** OK, there it is! The kmod I need for the new kernel. So why doesn't yum want to install it?
-- -- Those who don't understand recursion are doomed to repeat it
Try to install the new kernel first, then after, see if the new kmod will update.
Or just use akmod-nvidia and when you install an updated kernel and reboot, akmod will auto build the new kmod for you (you need to install kernel-devel along with kmod initially).
On Sun, 2014-11-09 at 03:40 -0600, Mike Chambers wrote:
On Sat, 2014-11-08 at 19:01 -0500, Neal Becker wrote:
I don't understand why yum doesn't want to install updates when a new kernel is available:
sudo yum update ... ---> Package kernel.x86_64 0:3.16.7-200.fc20 will be installed ... [nothing about kmod-nvidia-blah]
** yum wants to update kernel **
rpm -qa kmod-nvidia* kmod-nvidia-304xx-3.16.6-203.fc20.x86_64-304.123-1.fc20.16.x86_64
** kmod-nvidia 3.16.6-203 is already installed **
yum info kmod-nvidia* ... Name : kmod-nvidia-304xx-3.16.7-200.fc20.x86_64 Arch : x86_64 Version : 304.123 Release : 1.fc20.17
** OK, there it is! The kmod I need for the new kernel. So why doesn't yum want to install it?
-- -- Those who don't understand recursion are doomed to repeat it
Try to install the new kernel first, then after, see if the new kmod will update.
Or just use akmod-nvidia and when you install an updated kernel and reboot, akmod will auto build the new kmod for you (you need to install kernel-devel along with kmod initially).
(install kernel-devel along with akmod initially, I mean, not kmod haha)
Joe Zeff wrote:
On 11/09/2014 01:40 AM, Mike Chambers wrote:
Try to install the new kernel first, then after, see if the new kmod will update.
Speaking from experience, when you update the kernel, the new kmod (if available) is normally drawn in as a dependency.
Except when, as I just showed, it isn't.
On 11/11/2014 01:53 AM, Neal Becker wrote:
Joe Zeff wrote:
On 11/09/2014 01:40 AM, Mike Chambers wrote:
Try to install the new kernel first, then after, see if the new kmod will update.
Speaking from experience, when you update the kernel, the new kmod (if available) is normally drawn in as a dependency.
Except when, as I just showed, it isn't.
Just my 2 cents worth, as I understand things the kernel does not have kmod-nvidia as a dependency, its the other way around, kmod-nvidia has a dependency on the kernel version it has been compiled for. For example, when I did a full system update yesterday the kernel was upgraded to the latest version available in the mirrors dnf is using and kmod-nvidia was upgraded to 3.16.6 at the same time, and then this morning rpm fusion notified of an upgrade to kmod-nvidia to 3.16.7. I have just done a normal 'dnf upgrade' which upgraded, in my case, kmod-nvidia and kmod-virtualbox both to 3.16.7. Just further to this I have also been in the situation where a kernel has been updated and kmod-nvidia has not and at boot time the nvidia driver would not start because the installed one was not compatible with the new kernel. My system was still usable because I could reboot into the older kernel that was compatible with the installed kmod-nvidia driver, but in addition, xorg also falls back to the nouveau driver if the nvidia driver doesn't work, and, if the nouveau driver is not available it falls back to the vga driver before it gives up. Having said this, compatibility between kmod-nvidia and the kernel is not that big a deal for me as I also have akmod-nvidia installed so the driver will be compiled and installed at boot time if necessary anyway.
regards, Steve
On 11/10/2014 06:53 AM, Neal Becker wrote:
Joe Zeff wrote:
On 11/09/2014 01:40 AM, Mike Chambers wrote:
Try to install the new kernel first, then after, see if the new kmod will update.
Speaking from experience, when you update the kernel, the new kmod (if available) is normally drawn in as a dependency.
Except when, as I just showed, it isn't.
Yes. Exactly, which is why I was very careful to qualify that by saying "normally."
Stephen Morris wrote:
On 11/11/2014 01:53 AM, Neal Becker wrote:
Joe Zeff wrote:
On 11/09/2014 01:40 AM, Mike Chambers wrote:
Try to install the new kernel first, then after, see if the new kmod will update.
Speaking from experience, when you update the kernel, the new kmod (if available) is normally drawn in as a dependency.
Except when, as I just showed, it isn't.
Just my 2 cents worth, as I understand things the kernel does not have kmod-nvidia as a dependency, its the other way around, kmod-nvidia has a dependency on the kernel version it has been compiled for. For example, when I did a full system update yesterday the kernel was upgraded to the latest version available in the mirrors dnf is using and kmod-nvidia was upgraded to 3.16.6 at the same time, and then this morning rpm fusion notified of an upgrade to kmod-nvidia to 3.16.7. I have just done a normal 'dnf upgrade' which upgraded, in my case, kmod-nvidia and kmod-virtualbox both to 3.16.7. Just further to this I have also been in the situation where a kernel has been updated and kmod-nvidia has not and at boot time the nvidia driver would not start because the installed one was not compatible with the new kernel. My system was still usable because I could reboot into the older kernel that was compatible with the installed kmod-nvidia driver, but in addition, xorg also falls back to the nouveau driver if the nvidia driver doesn't work, and, if the nouveau driver is not available it falls back to the vga driver before it gives up. Having said this, compatibility between kmod-nvidia and the kernel is not that big a deal for me as I also have akmod-nvidia installed so the driver will be compiled and installed at boot time if necessary anyway.
regards, Steve
I don't think I've ever seen this fallback to nouveau behavior. I believe the nouveau kernel parts are excluded at boot, so I don't know how that could work.
On 11/11/2014 10:55 PM, Neal Becker wrote:
Stephen Morris wrote:
On 11/11/2014 01:53 AM, Neal Becker wrote:
Joe Zeff wrote:
On 11/09/2014 01:40 AM, Mike Chambers wrote:
Try to install the new kernel first, then after, see if the new kmod will update.
Speaking from experience, when you update the kernel, the new kmod (if available) is normally drawn in as a dependency.
Except when, as I just showed, it isn't.
Just my 2 cents worth, as I understand things the kernel does not have kmod-nvidia as a dependency, its the other way around, kmod-nvidia has a dependency on the kernel version it has been compiled for. For example, when I did a full system update yesterday the kernel was upgraded to the latest version available in the mirrors dnf is using and kmod-nvidia was upgraded to 3.16.6 at the same time, and then this morning rpm fusion notified of an upgrade to kmod-nvidia to 3.16.7. I have just done a normal 'dnf upgrade' which upgraded, in my case, kmod-nvidia and kmod-virtualbox both to 3.16.7. Just further to this I have also been in the situation where a kernel has been updated and kmod-nvidia has not and at boot time the nvidia driver would not start because the installed one was not compatible with the new kernel. My system was still usable because I could reboot into the older kernel that was compatible with the installed kmod-nvidia driver, but in addition, xorg also falls back to the nouveau driver if the nvidia driver doesn't work, and, if the nouveau driver is not available it falls back to the vga driver before it gives up. Having said this, compatibility between kmod-nvidia and the kernel is not that big a deal for me as I also have akmod-nvidia installed so the driver will be compiled and installed at boot time if necessary anyway.
regards, Steve
I don't think I've ever seen this fallback to nouveau behavior. I believe the nouveau kernel parts are excluded at boot, so I don't know how that could work.
I'm basing xorg's functionality on messages I've seen in xorg.0.log where there are statements that it is checking for the nvidia driver, nouveau driver and vga driver in that order. I'm assuming from this that the kmod-nvidia package supplies the xorg driver as, unlike other distros, in Fedora I haven't seen any upgrades to what are obvious xorg driver packages when kmod-nvidia is upgraded. As I understand it, the nouveau driver is built into the initramfs file, and unless this file is rebuilt at boot time when using akmod-nvidia instead of kmod-nvidia which is not obviously done, then akmod-nvidia users have nouveau in initramfs at boot time.
regards, Steve
-
Joe Zeff -
Mike Chambers -
Neal Becker -
Stephen Morris