To summarize and perhaps end this thread about VirtualBox as supplied by SUSE: 1) SUSE's VirtualBox kernel module is not installed in such a way that it is loaded automatically. This is nothing to do with kernel updates. The module is not set up to be loaded automatically. 2) You have two options to remedy this: a) run "/etc/init.d/vboxdrv start" by hand at each system reboot. b) run "insserv vboxdrv" once and be done with it. (Why the RPM does not do this is anybody's guess.) 3) Forget you ever heard of "/etc/init.d/vboxdrv setup". It had no effect on for the SUSE RPM. Be aware that SUSE's "setup" does not do the same as the original VirtualBox "setup". 4) SUSE will (is this not the case?) provide a new VirtualBox driver to match new kernels that they release. Updating one should cause an update of the other automatically.
Tom in NM
Where in NM? I lived a few years in Las Cruces. I loved the place. Even though I left it for Sweden. Go figure. And just try to get a late summer green chili enchilada here... -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Office: Int +46 8-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org