Ask Your Question

Is it safe to disable dkms_autoinstaller.service?

asked 2013-02-12 06:55:44 -0500

polarfish gravatar image

updated 2014-09-28 21:17:14 -0500

mether gravatar image

I'm issuing long boot time.

[user@comp ~]$ systemd-analyze
Startup finished in 1799ms (kernel) + 3748ms (initrd) + 34879ms (userspace) = 40427ms

[user@comp ~]$ systemd-analyze blame
16589ms dkms_autoinstaller.service
8435ms iscsid.service
7444ms systemd-udev-settle.service
7009ms firewalld.service
5250ms postgresql.service

So my question: Is it safe to disable dkms_autoinstaller.service because it's in top of my "blamelist"?

1) My linux kernel version is 3.7.6-201.fc18.i686.PAE
2) I'm using VirtualBox and from time to time it refuses to start (after another kernel upgrade), so I need to run /etc/init.d/vboxdrv setup. Every time I do it by hand, so do I actually need dkms_autoinstaller.service enabled?

Thanks in advance.

I've tried it on my own risk and it's OK, system is booting as an usual. As for booting time - I've won just 5 seconds :(

Startup finished in 1793ms (kernel) + 3747ms (initrd) + 30081ms (userspace) = 35623ms

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2013-02-12 08:27:45 -0500

updated 2013-02-12 08:28:27 -0500

It's safe as long you understand that any kernel module you need must be added manually. DKMS make's it easier to have new kernel modules loaded automatically, like the one's for Virtualbox, making it easier to have programs like VirtualBox always working without any mannually tweaking.

If in your case, DKMS isn't working for VirtualBox, and you already know how to load kernel modules by your own, then yes, you can remove it.

Nevertheless doing so may break your system, if some kernel module doesn't get loaded on boot time

edit flag offensive delete link more

Question Tools


Asked: 2013-02-12 06:55:44 -0500

Seen: 2,163 times

Last updated: Feb 13 '13