[elrepo] after kmod-nvidia el7 update during boot still use the old kmod

[Farkas Levente]

On 10/25/2015 03:27 PM, Phil Perry wrote:
> On 25/10/15 10:38, Farkas Levente wrote:
>> hi,
>> after upgrading to kmod-nvidia-352.55-1.el7.elrepo.x86_64 after boot
>> i've only got black screen. and this happended with the previous version
>> also. the reason is that during boot the kernel's initramfs still
>> contains the old kmod. the relevant part of dmesg:
> 
> But because it's not versioned this won't tell us if the initramfs image
> gets updated on updating the driver or not.
> 
> After updating to kmod-nvidia-352.55-1.el7.elrepo we can check if dracut
> has been run on the initramfs images:
>
> So as expected we see dracut has been run twice on all kernels, once
> during %post as the new kmod package is installed and once during
> %postun as the old kmod is uninstalled.
> 
> Rebooting after the kmod update proceeds as expected.
> 
...
> Check the initramfs as I did above. Then update to
> kmod-nvidia-352.55-1.el7.elrepo, watching what dracut does, and see if
> you can replicate the issue.
> 
> If we can work out what's happening, and why, then maybe we can come up
> with a solution to make the process more robust.
> 
> Note that in the %post script, on first install only, we do:
> 
> /usr/bin/dracut --add-drivers nvidia -f /boot/initramfs-$KERNEL.img $KERNEL

so this last line solve my problem. and the reaon is this part only runs
once, BUT not in the kmod's post sript but in the nvidia-x11-drv's post
script. that's why i can't find it. why?

why not the kmod take cares about the kmod update in the initramfs?

is there any reason why this part put into the nvidia-x11-drv's post
scripts?

anyway i still don't know why this do not properly set my initramfs
during update.

but thanks you solve my problem:-)
-- 
  Levente                               "Si vis pacem para bellum!"