After 4.0.6 and 4.0.6-r1 versions of the app-emulation/virtualbox-modules ebuild, Virtualbox cannot load because of modules version mismatch. The version of app-emulation/virtualbox-bin is the same as the modules version mentioned in the ebuild - I have 4.0.6 version installed for both modules and virtualbox-bin. With 4.0.6-r1 version the problem still persists. When loading vboxdrv kernel report 4.0.4 version of the loaded module. Reproducible: Always Steps to Reproduce: 1.Emerge the latest versions of virtualbox-bin and virtualbox-modules - 4.0.6 or 4.0.6-r1 2. modprobe vboxdrv and see dmesg for module version 3. Start virtualbox-bin Actual Results: Modules and program versions mismatch Expected Results: Emerging 4.0.6 or 4.0.6-r1 versions of virtualbox-modules to provide the correct versions of the modules
Make sure your /usr/src/linux symlkink is set correctly. Post the output of : ls -ld /usr/src/linux If it's set to a different kernel version than the one you are running, the modules will be installed in a different /lib/modules/ directory, and you'll not be able to use them with your kernel.
(In reply to comment #1) > Make sure your /usr/src/linux symlkink is set correctly. > Post the output of : > ls -ld /usr/src/linux > > If it's set to a different kernel version than the one you are running, the > modules will be installed in a different /lib/modules/ directory, and you'll > not be able to use them with your kernel. Stratos thank you for reply. It was completely my mistake and you are right - the "linux" symlink didn't point my current kernel source tree. Fixed it, reinstalled virtualbox-modules and now everything is OK. Regards, niki
I'm glad I could help. Closing this as invalid.
