Re: Akmods run RPM install as service?

2016-09-14 18:01 GMT+02:00 Richard Shaw <hobbes1069(a)gmail.com&gt;: > > 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.

For some known ones, the major reason why the kernel posttrans script might fails is because it's missing the matching kernel-devel for the new installed kernel. Please see: https://bugzilla.rpmfusion.org/show_bug.cgi?id=3386 (please note that while its reported against the akmods maintainer, anyone can take this and implement, not only Richard or me). In others word, you need to force to install the matching kernel- devel along with the kernel update (dnf update kernel will break).

Looking at the current akmods.service, can you please explain why: - It's using before display-manager.service (that's not the point with nvidia here, if the nvidia driver isn't here, we should better implement a fallback to anything else) - RemainAfterExit=yes, Can you point me why this was added ? akmods shouldn't remains once it has finished to build. - It has "ExecStart=-/usr/sbin/modprobe nvidia", this is not the way the nvidia driver should be loaded, it's loaded by the DDX driver (well not that true with modern nvidia driver,but at least it shoudn't be loaded that way). I think having more into systemd service might help (you can trigger a start akmods.service from posttrans), I don't think having yet another akmods script will help. Thx