<html><head></head><body><div>On Qua, 2016-09-14 at 13:16 -0500, Richard Shaw wrote:</div><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, Sep 14, 2016 at 12:12 PM, Nicolas Chauvet <span dir="ltr"><<a href="mailto:kwizart@gmail.com" target="_blank">kwizart@gmail.com</a>></span> wrote:<br><blockquote type="cite"><span class="">2016-09-14 18:01 GMT+02:00 Richard Shaw <<a href="mailto:hobbes1069@gmail.com">hobbes1069@gmail.com</a>>:<br>
> I've had a few failures but not really sure as to the cause, but I've been<br>
> toying around with doing the final RPM install with a systemd service<br>
> instead of calling dnf directly with the kernel posttrans script.<br>
><br>
> Thoughts? Pitfalls?<br>
</span>I really don't understand the method here.<br>
Can you reproduce any issue ? or do you have received informal<br>
informations that the posttrans script wasn't working for a reason ?<br>
Because for now It's working fine with me all the time, so there is<br>
probably an unknown corner case here.<br></blockquote><div><br></div><div>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. </div></div></div></div></blockquote><div><br></div><div>yes , after install kmod you should load the kmods modules , it may work without it , because X load it but we should ensure modprobe nvidia.ko (not depmod .. ) </div><div><br></div><div>for example VirtualBox instructions:</div><div><br></div><div> dnf install VirtualBox kernel-devel-$(uname -r) akmod-VirtualBox</div><div> akmods</div><div> systemctl restart systemd-modules-load.service</div><div><br></div><div><br></div><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div> </div><blockquote type="cite">
For some known ones, the major reason why the kernel posttrans script<br>
might fails is because it's missing the matching kernel-devel for the<br>
new installed kernel. Please see:<br>
<a href="https://bugzilla.rpmfusion.org/show_bug.cgi?id=3386" rel="noreferrer" target="_blank">https://bugzilla.rpmfusion.<wbr>org/show_bug.cgi?id=3386</a> (please note that<br>
while its reported against the akmods maintainer, anyone can take this<br>
and implement, not only Richard or me).<br>
In others word, you need to force to install the matching kernel-devel<br>
along with the kernel update (dnf update kernel will break).<br></blockquote><div><br></div><div>I'm certainly not missing kernel-devel but I have had intermittent issues. </div><div><br></div><div><br></div><blockquote type="cite">Looking at the current akmods.service, can you please explain why:<br>
- It's using before display-manager.service (that's not the point with<br>
nvidia here, if the nvidia driver isn't here, we should better<br>
implement a fallback to anything else)<br></blockquote><div><br></div><div>Are you saying it should be dependent on an earlier target? I chose display-manager since nvidia is my primary use.</div><div><br></div><div> </div><blockquote type="cite">
- RemainAfterExit=yes, Can you point me why this was added ? akmods<br>
shouldn't remains once it has finished to build.<br></blockquote><div><br></div><div>Since it runs and exits (not a daemon) this option keeps systemd from thinking it failed.</div><div><br></div><div> </div><blockquote type="cite">
- It has "ExecStart=-/usr/sbin/modprobe nvidia", this is not the way<br>
the nvidia driver should be loaded, it's loaded by the DDX driver<br>
(well not that true with modern nvidia driver,but at least it shoudn't<br>
be loaded that way).<br></blockquote><div><br></div><div>I can't remember why I added that but if must have fixed a problem I was having at the time. </div><div><br></div><div><br></div><blockquote type="cite">I think having more into systemd service might help (you can trigger a<br>
start akmods.service from posttrans), I don't think having yet another<br>
akmods script will help.<br></blockquote><div><br></div><div>No new script, just alter the akmodsposttrans to call "systemctl start akmods-install" or whatever it will be called instead of calling akmods directly. </div><div><br></div><div>Thanks,</div><div>Richard</div></div></div></div>
</blockquote><div><span><pre>--
Sérgio M. B.
</pre></span></div></body></html>