DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
after updating kernel to 3.9.1 (from 3.2), virtualbox doesn't work. the usual '/etc/init.d/vboxdrv setup' doesn't help because /etc/init.d/vboxdrv is missing.
'sudo /etc/init.d/virtualbox start'
fails with error:
'Starting VirtualBox kernel modulesNo suitable module for running kernel found ... failed!
failed!'
using non-OSE vbox, on Debian_testing_amd64.
how to fix?
thanks.
I'm no expert in virtualbox but isn't it kernel-dependent. Don't you have to rebuild your virtualbox drivers every time you update your kernel?
And what makes you say vboxdrv is missing? That's not what the error message says. This is how the system responds when it's missing:
Code:
bash: /etc/init.d/virtualbox: No such file or directory
I remember having to manually run '/etc/init.d/vboxdrv setup' after every kernel update long ago like you say. but then I installed some (perhaps virtual) packages and, iirc, it had updated drivers automatically, until now.
so its 'virtualbox' instead of 'vboxdrv' ? but 'vritualbox' doesnt have 'setup' option, only:
You fail to understand my message. Whether it's vboxdrv or virtualbox is irrelevant. I was merely illustrating the error message given when a file (any file) is missing. You claimed "/etc/init.d/vboxdrv is missing" in your first post. But the error message does not say that.
jdk
I have a version of virtualbox on my backup laptop and it does not have vboxdrv in that folder. It has virtualbox. As I said before you probably need to recompile your module based on the current kernel or else restore the old kernel.
jdk
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.