Re: Akmods run RPM install as service?
2016-09-14 20:16 GMT+02:00 Richard Shaw <hobbes1069(a)gmail.com>:
On Wed, Sep 14, 2016 at 12:12 PM, Nicolas Chauvet
<kwizart(a)gmail.com> wrote:
>
> 2016-09-14 18:01 GMT+02:00 Richard Shaw <hobbes1069(a)gmail.com>:
> > I've had a few failures but not really sure as to the cause, but I've
> > been
> > toying around with doing the final RPM install with a systemd service
> > instead of calling dnf directly with the kernel posttrans script.
> >
> > Thoughts? Pitfalls?
> I really don't understand the method here.
> Can you reproduce any issue ? or do you have received informal
> informations that the posttrans script wasn't working for a reason ?
> Because for now It's working fine with me all the time, so there is
> probably an unknown corner case here.
Reproduce, no, but I've had a couple of occasions where I was not able to
get to graphical boot. I just read about the need to run depmod on a Fedora
thread. I didn't think about that so I manually erased the RPMs and let
akmod rebuild them which fixed the problem.
depmod is run at the %post (and
%postun) step from the kmod produced by akmod:
rpm -q kmod-nvidia-$(uname -r)-367.44-1.fc24.x86_64 --scripts
I remember that when using the fedup (fedora upgrade tool), there is a
need to run depmod because of some races conditions
(fedup doesn't wait for the posttrans task to finish and might reboot
right after,but before akmod will then install the produced kmod).
The current recommandation from fedup is to disable any kmod before fedup.
It might be a might be interesting to implement some reboot locking
mechanism in this case.
Thx