Date: Thu, 28 Apr 2005 09:07:57 +1200 From: Andrew Thompson <andy@fud.org.nz> To: Steven Hartland <killing@multiplay.co.uk> Cc: freebsd-hackers@freebsd.org Subject: Re: kern.module_path missing kernel boot dir Message-ID: <20050427210757.GA3625@heff.fud.org.nz> In-Reply-To: <004501c54b6c$6e41bbc0$b3db87d4@multiplay.co.uk> References: <004501c54b6c$6e41bbc0$b3db87d4@multiplay.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Apr 27, 2005 at 10:02:28PM +0100, Steven Hartland wrote:
> I have a 5.3-RELEASE machine here which refuses to load things like
> nfsd erroring about kernel module doesnt exist. I've been tracking it
> down and it looks like: kern.module_path is at fault on the broken
> machine its:
> sysctl -a |grep modules
> kern.module_path: /boot/modules
>
> where as on a working machine its:
> sysctl -a |grep modules
> kern.module_path: /boot/kernel;/boot/modules
>
> Anyone got any ideas where I can look next to see why module_path
> is not been set correctly?
>
You may want to check this out from UPDATING
20040806:
Module loading has been fixed. Some older installations will
drop proper module_path initialization and modules will fail to
load properly. If you have a line in /boot/loader.rc that says:
"initialize drop", do (i386 only):
cp /usr/src/sys/boot/i386/loader/loader.rc /boot/loader.rc
chown root:wheel /boot/loader.rc
chmod 444 /boot/loader.rc
Andrew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050427210757.GA3625>