On Fri, Dec 18, 2009 at 1:21 PM, Michael Meskes <[email protected]> wrote: > On Fri, Dec 18, 2009 at 11:26:07AM -0300, Matias Bellone wrote: >> This happens on i386 emulating i386 >> >> eternia:/home/toote# lsmod | grep vbox >> vboxnetflt 72328 0 >> vboxnetadp 66864 0 >> vboxdrv 102576 1 vboxnetflt > > How did you build these modules? Do they have the same version as the other > virtualbox packages?
They are the modules included in the virtualbox-ose-modules package. I didn't compile it myself. > What does dmesg tell you after insmod'ing the modules? I have the modules loaded automatically on boot by setting LOAD_VBOXDRV_MODULE to 1 on /etc/default/virtualbox-ose. This is what I guess would be the output of that (last lines of /var/log/dmesg): [ 18.333841] vboxdrv: Trying to deactivate the NMI watchdog permanently... [ 18.333848] vboxdrv: Successfully done. [ 18.333852] vboxdrv: Found 2 processor cores. [ 18.334117] vboxdrv: fAsync=0 offMin=0x834 offMax=0x10d10 [ 18.334285] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'. [ 18.334373] vboxdrv: Successfully loaded version 3.0.6_OSE (interface 0x000e0000). Then again, more investigation on this front resulted in the issue being the same as #560320 [0] I've upgraded to the unstable version and the same error occurred but now it stated that one needed to install the -dkms package, did so and it worked fine. I'm not sure if installing the -dkms package would have solved it without updating too. [0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560320 > >> eternia:/home/toote# vboxheadless > > Doesn't the line above lack some arguments? vboxheadless usually needs an > argument. Very likely, I use the qt interface. Just wanted a text-version of the error as the error was the same just in a fancy dialog. Regards, Matías -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
