Date: Thu, 20 Oct 2022 12:08:09 +0200 From: Emmanuel Vadot <manu@bidouilliste.com> To: Andriy Gapon <avg@FreeBSD.org> Cc: FreeBSD Current <current@FreeBSD.org> Subject: Re: loader.efi module path vs kernel directory Message-ID: <20221020120809.f3a21c9a5c33a2ba440ddc01@bidouilliste.com> In-Reply-To: <2292945b-c6ba-69c4-e1fd-2726528993cd@FreeBSD.org> References: <2292945b-c6ba-69c4-e1fd-2726528993cd@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 20 Oct 2022 13:03:26 +0300 Andriy Gapon <avg@FreeBSD.org> wrote: > > I recently needed to recover a system by manually preloading a driver. > To a bit of surprise, simple 'load $modname' did not work, I had to use 'load > /boot/kernel/$modname.ko'. I didn't have to do this in a long time, but I > recall that the short command used to work. Additionally, required modules also > failed to get loaded automatically because loader couldn't find them. > > I am not sure what the issue is. Is it that /boot/kernel is not in module path > (as per /boot/defaults/loader.conf) ? Or is it that /boot/kernel does not get > added to the *effective* module path? > > Thanks! > -- > Andriy Gapon > if you escape to prompt directly loader didn't loaded all it's config so there is no modulepath defined, you need to 'boot-conf' to load the configuration files. Cheers, -- Emmanuel Vadot <manu@bidouilliste.com> <manu@FreeBSD.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20221020120809.f3a21c9a5c33a2ba440ddc01>