Date: Fri, 24 Aug 2018 10:04:54 +0200 From: Johannes Lundberg <johalun0@gmail.com> To: freebsd-current <freebsd-current@freebsd.org> Subject: priority of paths to kernel modules? Message-ID: <CAECmPwu5suk9xaf4zWFYgVW6kkuUiFb1DviVR6VmQttjJUd56g@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Hi Since we now stuck with drm2 in base for a few more years I have an idea would make things much smoother for many of us, hugely reduce the amount of bug reports we get and I think would be beneficial in other ways too. Current I run with something like this in /boot/loader.conf module_path="/boot/modules.drm-v4.16;/boot/modules;/boot/dtb;/boot/overlays" So I expect modules to be loaded in that order, with /boot/<mykernel> LAST. However, if you look at this sysctl kern.module_path kern.module_path: /boot/kernel;/boot/modules.drm-v4.16;/boot/modules;/boot/dtb;/boot/overlays /boot/kernel is inserted first and probably modules in /boot/kernel have the highest priority. This is also proven by everyone wanting to use drm*kmods that get drm.ko from base loaded instead of the installed in /boot/modules. Please correct me if I'm wrong but if my understanding is correct this is a flaw and /boot/<mykernel> should be inserted last so that any overlays or custom modules have higher priority than the default ones. I can imagine this is also useful when building custom modules and you don't want to overwrite or delete the default one in /boot/kernel... Cheers
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAECmPwu5suk9xaf4zWFYgVW6kkuUiFb1DviVR6VmQttjJUd56g>