Solved loader module_path

[W.hâ/t]

I've got some issues booting from loader prompt where I have to set module_path to add /boot/kernel
If I boot 'normaly' module_path is set correctly. Yet I don't add it in /boot/loader.conf.

[what@home]~> grep module_path /boot/defaults/loader.conf
bitmap_type="splash_image_data" # and place it on the module_path
module_path="/boot/modules;/boot/dtb;/boot/dtb/overlays"        # Set the module search path
[what@home]~> grep module_path /boot/loader.conf        
1[what@home]~> sysctl -n kern.module_path
/boot/kernel;/boot/modules;/boot/dtb;/boot/dtb/overlays

Is this expected behavior?


On the same note, I've been unable to load cpu_microcode from the loader prompt. Not to sure what am I missing there...

set cpu_microcode_load=YES
set cpu_microcode_name=/boot/firmware/intel-ucode.bin

 

[W.hâ/t]

From loader(8)

load [-t type] file

And in deed load -t cpu_microcode /boot/firmware/intel-ucode.bin did the job.

Is this expected behavior?

The loader will add the directory of the selected kernel you choose to boot from to module_path, if selected from the menu. If you manually select the kernel from the prompt, you have to manually set the appropriate module_path. Makes sense.. to me at least. I am not sure if that;'s accurate.