Date: Mon, 21 Dec 2009 18:15:46 +0100 From: Leslie Jensen <leslie@eskk.nu> To: Rolf Nielsen <listreader@lazlarlyricon.com> Cc: freebsd-questions@freebsd.org Subject: [SOLVED]Re: Loading kernel modules for virtualbox via script Message-ID: <4B2FAD42.1060009@eskk.nu> In-Reply-To: <4B2FAA1D.9000701@lazlarlyricon.com> References: <alpine.BSF.2.00.0912202157330.32571@fledge.watson.org> <4B2F60BA.7010002@bsdforen.de> <4B2F9CEF.6050501@eskk.nu> <4B2FA3DD.5050206@lazlarlyricon.com> <4B2FA6F0.30306@eskk.nu> <4B2FAA1D.9000701@lazlarlyricon.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2009-12-21 18:02, Rolf Nielsen wrote: > Leslie Jensen wrote: >> >> On 2009-12-21 17:35, Rolf Nielsen wrote: >>> Leslie Jensen wrote: >>>> >>>> Following the suggestion here: >>>> http://forums.freebsd.org/showpost.php?p=45664&postcount=5 >>>> >>>> To load two kernel modules via a script in /etc/rc.d/ >>>> >>>> Produces the following: >>>> >>>> WARNING: Ignoring old-style startup script /etc/rc.d/ >>>> >>>> I found the answer here: >>>> >>>> http://sourceforge.net/tracker/index.php?func=detail&aid=2896643&group_id=151951&atid=782616 >>>> >>>> >>>> >>>> >>>> I would like a suggestion on how to load the modules! >>>> >>>> Thanks >>>> >>>> /Leslie >> >>>> >>>> >>> >>> Can't you load the modules from /boot/loader.conf? AFAIK VirtualBox >>> places its modules in /boot/modules, which makes them loadable by >>> load_modulename="YES" in /boot/loader.conf, where modulename should be >>> replaced by the filename of the module(s), omitting the leading path and >>> the .ko suffix, e.g. nvidia_load=YES" loads /boot/modules/nvidia.ko. >> >> Correction.................... >> >> I read in the same post that the loading order was important, and the >> way I understood it was that, if I load via loader.conf I could not be >> sure that the order is correct! >> >> >> >> >> > > If the order is important, one probably depends on the other. Try > loading only one of them and see if it automagically loads the other one. > > Or I guess you could simply load them from /etc/rc.local. Though that > is, AFAIK, no longer a recommended way to do things, it does still work. > I start a few things from there, simply because I couldn't be bothered > with writing an rc.d script. You where right! One of them loaded the other so problem solved :-) Thank you!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B2FAD42.1060009>