Am 17.11.2013 19:00, schrieb Sjoerd Mullender:
On 2013-11-17 17:19, Steven Stern wrote:
Booting after today's kernel update, I noticed that there was a dkms
failure:
Nov 17 10:08:10 sds-desk-2 vboxdrv[556]: Starting VirtualBox kernel
modules [FA
ILED]
Nov 17 10:08:10 sds-desk-2 vboxdrv[556]: (modprobe vboxdrv failed.
Please use '
dmesg' to find out why)
Nov 17 10:08:10 sds-desk-2 dkms_autoinstaller[558]: Starting dkms:
Error! Could not locate dkms.conf file.
Nov 17 10:08:10 sds-desk-2 dkms_autoinstaller[558]: File: does not exist.
# locate dkms.conf
/usr/share/virtualbox/src/vboxhost/dkms.conf
/var/lib/dkms/vboxhost/4.2.10/build/dkms.conf
/var/lib/dkms/vboxhost/4.2.18/build/dkms.conf
Does anyone else using the Oracle distribution of VirtualBox see any
errors after a kernel update?
No problems with VirtualBox 4.3.2.
# rpm -q VirtualBox-4.3
VirtualBox-4.3-4.3.2_90405_fedora18-1.x86_64
# uname -r
3.11.8-200.fc19.x86_64
Using VirtualBox-4.2 (VirtualBox-4.3-4.3.2_90405_fedora18-1.x86_64)
without any problems after upgrade to kernel 3.11.8-200.fc19.x86_6.
--
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
