A general advice, regarding akmod automatic building: module building for the kernel just installed is started in background after kernel update has been completed. This means that, if you restart the system right after the upgrade process, you might be very well aborting the module building, thus leading to the frequent problems posted in this list. Use top, htop or similar after the update to check if the akmod building has effectively terninated before restarting the system.

On Tue, Jul 14, 2015 at 5:09 AM, Reindl Harald <h.reindl(a)thelounge.net why was that behavior changed? in the past the akmod builds happended *while reboot* some years ago as i had crap hardware needing that... The akmods package includes both a service that will run on startup and on shutdown but they are not enabled by default

Hello , On Ter, 2015-07-14 at 21:41 -0500, Richard Shaw wrote: > Ok, I wasn't sure if installing in a chroot was a sufficient test case > so I tried installing akmods in a F22 virtual machine and can confirm > that although the services are explicitly enabled in %post that they > are not enabled after install. Somehow systemd (or something else) is > refusing to allow the enable commands to work in %post and is using > the preset file instead. Not in my test case : mock -r fedora-22-i386-rpmfusion_free --install akmods mock -r fedora-22-i386-rpmfusion_free --shell <mock-chroot>sh-4.3# systemctl is-enabled akmods enabled > Thanks, > Richard -- Sérgio M. B.

On Wed, Jul 15, 2015 at 1:37 AM, Dave Pawson <dave.pawson(a)gmail.com&gt; wrote: > > Fedora21 installed on clean disk. > F22 update from F21. > I've not touched any of the permissions. > > $ systemctl is-enabled akmods > enabled Was this a fresh install of akmods? I wouldn't expect upgrading to turn the services off. Thanks, Richard

On Wed, Jul 15, 2015 at 10:07 AM, Dave Pawson <dave.pawson(a)gmail.com&gt; wrote: > > Unsure Richard. If I installed it, I installed it with F20, I > certainly haven't changed hardware or software re graphics for years. > Assumption: displaying 'enabled' means that akmods *is* enabled? I'm not exactly sure when the systemd preset starting being enforced on Fedora, so if you had the services previously enabled, they wouldn't be turned "off". What I'm trying to figure out is why when they are explicitly enabled in %post but seemed to get ignored, at least in my testing both in a chroot and in a f22 virtual machine. Thanks, Richard

On Tue, Jul 14, 2015 at 11:32 PM, Sérgio Basto <sergio(a)serjux.com&gt; wrote: Hello , On Ter, 2015-07-14 at 21:41 -0500, Richard Shaw wrote: > Ok, I wasn't sure if installing in a chroot was a sufficient test case > so I tried installing akmods in a F22 virtual machine and can confirm > that although the services are explicitly enabled in %post that they > are not enabled after install. Somehow systemd (or something else) is > refusing to allow the enable commands to work in %post and is using > the preset file instead. Not in my test case : mock -r fedora-22-i386-rpmfusion_free --install akmods mock -r fedora-22-i386-rpmfusion_free --shell <mock-chroot>sh-4.3# systemctl is-enabled akmods enabled How did you get that to work? When I tried running systemctl it said something to the effect of "chroot detected, aborting."

Thanks, Richard