Also, instead of manual load, you may want to use enable-module. Sent from my iPhone
> On 20. Oct 2022, at 13:08, Emmanuel Vadot <m...@bidouilliste.com> wrote: > > On Thu, 20 Oct 2022 13:03:26 +0300 > Andriy Gapon <a...@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 <m...@bidouilliste.com> <m...@freebsd.org> >
