You are not logged in.
I had virtual box working (64bit) from puel/aur perfectly... then there was a kernel update and then when i went to bootup the virtual machine (the virtualbox gui worked fine), the VM screen went black and the entire computer/mouse froze solid, had to do a hard reboot..
was there or should I ask "is there" a command i should re-issue after the kernel updates? i'm thinking it has something to do with the virtualbox kernel module.. but i'm not sure..
i've read the info about virtualbox in the wiki... couldnt find much based on what i'm trying to ask in here..
any help/suggestions would be most appreciated..
thanks
Last edited by binskipy2u (2010-02-11 21:40:13)
"Sometimes you comfort the afflicted, other times you AFFLICT the COMFORTABLE"
Offline
i remember something similar when we had to rebuild all external modules against 2.6.32.3.
did you tried to rebuild yours? like a side note, virtualbox_bin links to libpng12 and you might want to install it from aur.
Give what you have. To someone, it may be better than you dare to think.
Offline
sorry, after a few searches i found what "could" be the answer.. since i redid entire 4.4kde system.. from ftp/scratch.. no problem.. ill save the commands I found to see if they work...
btw, how do you delete a post in here or are regular users allowed?
"Sometimes you comfort the afflicted, other times you AFFLICT the COMFORTABLE"
Offline
When you installed aur/virtualbox_bin, the following post-install message was displayed:
Run "vbox_build_module" as root every time your kernel is upgraded, to compile the module for the new kernel version.
You can confirm this by checking your pacman log and/or by reading /var/lib/pacman/local/virtualbox_bin-<version>/install.
Offline
yeah i found that on my 3rd forum search.. thanks
"Sometimes you comfort the afflicted, other times you AFFLICT the COMFORTABLE"
Offline