From owner-freebsd-questions@FreeBSD.ORG Sun Oct 12 22:38:44 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 ECD2D6B5 for ; Sun, 12 Oct 2014 22:38:43 +0000 (UTC) Received: from resqmta-po-01v.sys.comcast.net (resqmta-po-01v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:160]) (using TLSv1.2 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 BAA7925F for ; Sun, 12 Oct 2014 22:38:43 +0000 (UTC) Received: from resomta-po-20v.sys.comcast.net ([96.114.154.244]) by resqmta-po-01v.sys.comcast.net with comcast id 2Neh1p0055Geu2801NeiHz; Sun, 12 Oct 2014 22:38:42 +0000 Received: from CurlySr.dbis.net ([50.183.226.175]) by resomta-po-20v.sys.comcast.net with comcast id 2Neg1p00G3nhSLa01Neih2; Sun, 12 Oct 2014 22:38:42 +0000 Message-ID: <543B02F0.4010005@comcast.net> Date: Sun, 12 Oct 2014 16:38:40 -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: [CANCEL] Re: Misbehaving /boot/loader.conf References: <5439F046.60204@comcast.net> <543ABF08.10701@comcast.net> <543AD258.5000307@comcast.net> <543AF9A7.9060103@comcast.net> <543AFD26.1030505@comcast.net> In-Reply-To: <543AFD26.1030505@comcast.net> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1413153522; bh=oCZGWrQH0pCE/26ZJxj9QSIqOlpNY3Dq6/Ask1xLwrk=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=wr87rRrZsmgoY4d66L2FxeQ/D/Gi/cA4gmDhS/nuQlXMIDjExUchsVlr7on7/h0To WEHCN91wOH+VVMbkaubXL+s5zOYMQee4gHepr4Flj6iyE4RbL+ehAK1XmJhFAeTGUG 1hCzMcMPbpEih2GBugdTLeHTd/9/xhOdDXxvx3o8O7XA/oH9uR+Arw4w676GZLWXSG JQ328pp+PadeuuG+uwYmIIyG9WAM57u8cL4iEviecKz+vmqpAbpGrugnRDkYhX9VoD 0y82AtX5aOe/1pUEuegITEixPbKOPrpzomhYbBg0l2T8yH1/5fEHMKuw/ZcIT0nMQG AtVH9JCvEoU9w== 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:38:44 -0000 Someone has reported this bug to the maintainers. I couldn't find reported bugs when I searched for "nvidia" but found them when I searched for "loader.conf". It is indeed a bug...and it may be related to changes to the loader to accomodate UEFI equipped machines. There are two solves... #1: Put the module into /boot/kernel as I have done. #2: Or manually load the module from rc.conf with kld_load="modulename" So the issue is not specific to me nor my systems. FYI folks. Sincerely and respectfully, Dave On 10/12/14 16:13, Dave Babb wrote: > 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" >> > _______________________________________________ > 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" >