Am 16.07.2015 um 14:16 schrieb Roderick Johnstone:
2015/07/16 10:43:04 akmods: Checking kmods exist for
4.0.7-300.fc22.x86_64
2015/07/16 10:43:08 akmods: Ignoring nvidia-340xx-kmod as it failed earlier
2015/07/16 10:43:08 akmods: Hint: Some kmods were ignored or failed to
build or install.
2015/07/16 10:43:08 akmods: You can try to rebuild and install them by
by calling
2015/07/16 10:43:08 akmods: '/usr/sbin/akmods --force' as root.
I didn't see a fix for this in your note about the new akmods package
you have in testing or in other recent threads, but I might have
overlooked something.
there is likely a akmods folders in /var/lib/ as for any other software
with runtime data, the information about the previous fail is there
so just purge that folder - due package install on a virgin setup it's
empty by definition
A dirty workaround for me would be to make the akmods.service file
run
/usr/sbin/akmods --force as the ExecStart line, but I have seen reports
on google that you can't easily pass parameters to the ExecStart command
like that
nonsense - most services are using params and it's no problem disable a
service, clone it's unit in /etc/systemd/system/, modify it there and
enable the service again so it don't get overwritten by updates