Hi again, LD> Thanks a lot for the detailed info. LD> Indeed my system had a wrong symlink, from /lib/modules/`uname -r`/build LD> to /usr/src/kernels/2.6.19-1.2895.fc6-i586 instead of LD> /usr/src/kernels/2.6.19-1.2895.fc6-i686 LD> Who knows!
LD> Anyway, now the installer does the job, but I have another LD> problem. The installer said: LD> Verifying archive integrity... All good. LD> Uncompressing VirtualBox for Linux installation..... LD> VirtualBox Version 1.3.2 (Sun Jan 14 15:25:08 CET 2007) installation LD> Installing VirtualBox to /opt/VirtualBox-1.3.2 LD> FATAL: Error inserting vboxdrv LD> (/lib/modules/2.6.19-1.2895.fc6/misc/vboxdrv.ko): Invalid module LD> format LD> VirtualBox has been installed successfully. LD> What is this invalid module format? My guess, you are in fact running 2.6.19-1.2895.fc6-i586 kernel, but have sources for i686 (what's that? 8-) ). This cause your module to have wrong vermagic. LD> The same message appear when I try and start the service vboxdrv. Does depmod -a (as root) help? LD> And, if I try and run VirtualBox, it says: LD> error while loading shared libraries: libstdc++.so.5: cannot open LD> shared object file: No such file or directory LD> I _do_ have exported LD_LIBRARYPATH to the installation dir LD> which in my case is /opt/VirtualBox-1.3.2 LD> Suggestions? Don't set LD_LIBRARYPATH to VirtualBox install dir - there are (almost) no libraries there in VirtualBox doesn't need this to function properly. Just install it and type 'VirtualBox' from the console or use your desktop menu. Before VirtualBox work, you need to solve a problem with the module and add your user to vboxusers group (then restart). Regards, Valentine _______________________________________________ vbox-dev mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-dev
