You are not logged in.
Pages: 1
In the process of doing my daily updates this week, I noticed both a new kernel and a new version of virtualbox. I didn't give it much thought, but when I started it today it said my vb kernel modules don't match my kernel. No sweat, this happens all the time. This time however, when I re-ran `sudo /etc/rc.d/vboxdrv setup` it didn't fix the problem. Now I'm stuck.
I have:
VirtualBox 3.2.0_OSE r29652
uname -a:
Linux sheldon 2.6.33-ARCH #1 SMP PREEMPT Thu May 13 12:06:25 CEST 2010 i686 Intel(R) Core(TM)2 Duo CPU T9600 @ 2.80GHz GenuineIntel GNU/Linux
I've googled some, but don't find any posts with my problem. Any ideas?
Offline
ok, you did /etc/rc.d/vboxdrv setup but you reloaded the modules after that?
rmmod vboxdrv
modprobe vboxdrv
Give what you have. To someone, it may be better than you dare to think.
Offline
That did the trick. Since switching to using /etc/rc.d/vboxdrv I haven't had to do that though. How interesting. Thanks for the help!
Offline
That did the trick. Since switching to using /etc/rc.d/vboxdrv I haven't had to do that though. How interesting. Thanks for the help!
please edit your thread title and add Solved
Give what you have. To someone, it may be better than you dare to think.
Offline
Pages: 1