Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 12 Oct 2014 16:38:40 -0600
From:      Dave Babb <dcbdbis@comcast.net>
To:        freebsd-questions@freebsd.org
Subject:   [CANCEL] Re: Misbehaving /boot/loader.conf <Updated info>
Message-ID:  <543B02F0.4010005@comcast.net>
In-Reply-To: <543AFD26.1030505@comcast.net>
References:  <5439F046.60204@comcast.net>	<543ABF08.10701@comcast.net>	<CAHu1Y7127RBEP9vGO3Paxp4k2O-04xU58nsZytNa4zmt5ooCQQ@mail.gmail.com>	<543AD258.5000307@comcast.net> <CAHu1Y73YzoMYpsrQPT+r=Mrce7DWV2Y0-oTk4Se8EBHzTbmMjQ@mail.gmail.com> <543AF9A7.9060103@comcast.net> <543AFD26.1030505@comcast.net>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
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"
>




Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?543B02F0.4010005>