From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 27 21:08:02 2005 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6AD0216A4CE for ; Wed, 27 Apr 2005 21:08:02 +0000 (GMT) Received: from dbmail-mx2.orcon.net.nz (loadbalancer1.orcon.net.nz [219.88.242.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8045143D3F for ; Wed, 27 Apr 2005 21:08:01 +0000 (GMT) (envelope-from thompsa@fud.org.nz) Received: from heff.fud.org.nz (60-234-149-201.bitstream.orcon.net.nz [60.234.149.201] (may be forged))j3RLBgC2031307 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 28 Apr 2005 09:11:44 +1200 Received: from thompsa by heff.fud.org.nz with local (Exim 4.50 (FreeBSD)) id 1DQtlF-0000yh-OW; Thu, 28 Apr 2005 09:07:57 +1200 Date: Thu, 28 Apr 2005 09:07:57 +1200 From: Andrew Thompson To: Steven Hartland Message-ID: <20050427210757.GA3625@heff.fud.org.nz> References: <004501c54b6c$6e41bbc0$b3db87d4@multiplay.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <004501c54b6c$6e41bbc0$b3db87d4@multiplay.co.uk> User-Agent: Mutt/1.4.2.1i Sender: Andrew Thompson X-Virus-Scanned: ClamAV version 0.83, clamav-milter version 0.83 on dbmail-mx2.orcon.net.nz X-Virus-Status: Clean cc: freebsd-hackers@freebsd.org Subject: Re: kern.module_path missing kernel boot dir X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2005 21:08:02 -0000 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