On 06/30/15 22:30, Richard Shaw wrote: > Sorry, I should have been more specific, the services are called "akmods" and "akmods-shutdown". Enabling either one should help... The shutdown one if dnf releases the lock before you shutdown or the bootup one in case that one fails. > > $ systemctl status akmods > ● akmods.service - Builds and install new kmods from akmod packages > Loaded: loaded (/usr/lib/systemd/system/akmods.service; enabled) > Active: active (exited) since Sun 2015-06-14 11:20:19 CDT; 2 weeks 1 days ago > Main PID: 852 (code=exited, status=0/SUCCESS) > CGroup: /system.slice/akmods.service > $ systemctl status akmods-shutdown > ● akmods-shutdown.service - Builds and install new kmods from akmod packages > Loaded: loaded (/usr/lib/systemd/system/akmods-shutdown.service; enabled) > Active: active (exited) since Sun 2015-06-14 11:20:08 CDT; 2 weeks 1 days ago > Main PID: 876 (code=exited, status=0/SUCCESS) > CGroup: /system.slice/akmods-shutdown.service I see.... Well, first I must admit that on both of my systems I notice the failure before I reboot and I correct the issue. So, I don't know if having those enabled will fix the issue. But just for completeness... [root@acer ~]# systemctl status akmods ● akmods.service - Builds and install new kmods from akmod packages Loaded: loaded (/usr/lib/systemd/system/akmods.service; enabled; vendor preset: disabled) Active: active (exited) since Tue 2015-06-30 09:08:56 CST; 13h ago Process: 754 ExecStart=/usr/sbin/akmods --from-init (code=exited, status=0/SUCCESS) Main PID: 754 (code=exited, status=0/SUCCESS) CGroup: /system.slice/akmods.service Jun 30 09:08:46 acer.greshko.com systemd[1]: Starting Builds and install new.... Jun 30 09:08:56 acer.greshko.com akmods[754]: Checking kmods exist for 4.0.6...] Jun 30 09:08:56 acer.greshko.com systemd[1]: Started Builds and install new .... [root@acer ~]# systemctl status akmods-shutdown ● akmods-shutdown.service - Builds and install new kmods from akmod packages Loaded: loaded (/usr/lib/systemd/system/akmods-shutdown.service; enabled; vendor preset: disabled) Active: active (exited) since Tue 2015-06-30 09:08:47 CST; 14h ago Process: 774 ExecStart=/bin/true (code=exited, status=0/SUCCESS) Main PID: 774 (code=exited, status=0/SUCCESS) CGroup: /system.slice/akmods-shutdown.service Jun 30 09:08:46 acer.greshko.com systemd[1]: Starting Builds and install new.... Jun 30 09:08:47 acer.greshko.com systemd[1]: Started Builds and install new .... I gather I should test at the next kernel update if this does "fix" the issue. -- Sorta what I want to say when folks habitually complain about Fedora - https://youtu.be/ZArl8fTfub4 -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
