From owner-freebsd-questions@FreeBSD.ORG Sun Oct 12 22:14:00 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 50F0CEEC for ; Sun, 12 Oct 2014 22:14:00 +0000 (UTC) Received: from resqmta-ch2-05v.sys.comcast.net (resqmta-ch2-05v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:37]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "Bizanga Labs SMTP Client Certificate", Issuer "Bizanga Labs CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 06BE9F7C for ; Sun, 12 Oct 2014 22:13:59 +0000 (UTC) Received: from resomta-ch2-19v.sys.comcast.net ([69.252.207.115]) by resqmta-ch2-05v.sys.comcast.net with comcast id 2NDz1p0022VvR6D01NDz4A; Sun, 12 Oct 2014 22:13:59 +0000 Received: from CurlySr.dbis.net ([50.183.226.175]) by resomta-ch2-19v.sys.comcast.net with comcast id 2NDy1p00D3nhSLa01NDyHX; Sun, 12 Oct 2014 22:13:58 +0000 Message-ID: <543AFD26.1030505@comcast.net> Date: Sun, 12 Oct 2014 16:13:58 -0600 From: Dave Babb User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: Misbehaving /boot/loader.conf References: <5439F046.60204@comcast.net> <543ABF08.10701@comcast.net> <543AD258.5000307@comcast.net> <543AF9A7.9060103@comcast.net> In-Reply-To: <543AF9A7.9060103@comcast.net> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1413152039; bh=cfXKP6tE0kd9zRB1lqRIO9d1ak2+l3yYrEUWJuGXySA=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=Ad9pGNHUirkuZlZQReeGQHWwBbHKQVruiljnswnnylxea/LRQKBFAeXUFQS7TNsxh dBaYrt/ostXK3RvybRzP7W0rW+VG3S3y21Wpuzu6c6qiZ7fL5JelyZCGG949qX703V wUS7ynip9l6UDZfx6g8HPszUQE0vM3K4kC2etq/sqnFfBlRU4t+WTrwbHDuFVW+Z6m S0hZENd3Pflg/nmYUOkPC9qITCozPtuISQw0X2+XI3DDup4j2aiBTLX5Z92JgNbKMk CwVmTQ14mQXyYwDztgf6xQTDuR5A3Bqly/mL15Hl3sr9P+8eqx8o/Ah+k63aalCD8J Vwr3uRfSw3Bjw== Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Oct 2014 22:14:00 -0000 I have done some experimentation on my system. It appears that the loader is dying on the "/boot/defaults/loader.conf" file....becasue that is the last file listed when the loader dies. Also, I added the "module_path" entries as suggested below into /boot/loader.conf...with no changes in the result. It appears that the culprit is "/boot/defaults/loader.conf"...but in reviewing it...I cannot see any spelling errors at all. And it clearly sets the module_load path to both /boot/kernel and /boot/modules..... But for whatever reason....loader is ignoring the path to the /boot/modules....and is only looking at /boot/kernel path...even though it is configured otherwise. Ideas? Suggestions? Sincerely and respectfully, Dave On 10/12/14 15:59, Dave Babb wrote: > Good Afternoon All, > > > When I list : > > "nvidia_load="YES"" in my /boot/loader.conf....the loader dies after > doing a register dump on the screen. > > I have validated that the kernel module is indeed in > "/boot/modules"....I can kldload it and have it operate just fine if I > boot without the loader line enabled. > > If I copy the modult into the /boot/kernel/ dir....then the > "nvidia_load="YES" line operates properly. > > I have validated that "/boot/defaults/loader.conf" does indeed have a > line that is unremmed that points correctly to both the kernel and > module paths as search paths for modules. > > Following another responders reply...I have performed a "sysctl > kern.module_path" and it returns what I expected "kern.module_path: > /boot/kernel;/boot/modules" > > I also performed a "kldconfig -r" and received the response of > "/boot/kernel;/boot/modules" > > > It is clear that I am configured properly......But it is also clear that > something else is wrong. This behavior now spans three new system > installs..... > > > Assistance in resolving would be sincerely appreciated. > > > Sincerely and respectfully, > > > Dave > > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" >