Johannes Kastl wrote: > On 3/5/09 12:16 PM Dave Plater wrote: > > >> # modprobe -rv vboxdrv >> FATAL: Module vboxdrv is in use. >> is what happens if I attempt to unload vboxdrv >> > > Try to stop VBOX before (/etc/init.d/vbox stop), then unload the module. > > And try to run "/etc/init.d/vbox setup" and see what happens. > > >> and the only unusual >> thing in /var/log/vbox-install.log is :- >> test -e include/linux/autoconf.h -a -e include/config/auto.conf || >> ( \ >> echo; \ >> echo " ERROR: Kernel configuration is invalid."; \ >> echo " include/linux/autoconf.h or >> include/config/auto.conf are missing."; \ >> echo " Run 'make oldconfig && make prepare' on kernel >> src to fix it."; \ >> echo; \ >> /bin/false) >> And this happens with or without make mrproper, make cloneconfig etc. >> > > What about "make oldconfig && make prepare", as it says in the log? > > > >> Do you have an idea what the error >> > > Unfortunately not, sorry. > > Regards, > OJ > > /etc/init.d/vboxdrv stop removes the driver from lsmod so it must be unloaded. You must mean vboxdrv stop and not vbox which doesn't exist. After vboxdrv setup there is no change. Make cloneconfig preserves my kernel configuration otherwise I may introduce other problems. It's not necessary to prepare the suse kernel for driver building, I have never had a problem in the past. I just wish somebody could shed a light on the error code, it gets very frustrating repeating the same steps over and over with no joy. Maybe if I install and run the factory virtual box os and then install the closed binary it might help. Regards Dave P
_______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
