Code: Select all
SUBSYSTEM=="firmware", ACTION=="add", RUN+="firmware --firmware=$env{FIRMWARE} --devpath=$env{DEVPATH}"
Even this is no longer necessary from kernel 3.7 onwards, which has its own firmware loader, but I keep it there for compatibility reasons.
Module loading similarly is handled directly with this:
Code: Select all
ENV{MODALIAS}=="?*", RUN+="/sbin/modprobe -bv $env{MODALIAS}"
Module blacklisting, preference etc is done using modprobe's standard blacklist. Fatdog doesn't have a nice gui for this, but I'm sure if/when it's needed one can be written easily. So far I haven't seen many cases (the most common one is to blacklist nouveau, radeon) so there isn't need for GUI yet.
Also, don't depmod when the system boots up, it's slow. Do the depmod when the distro is built, and when one installs a new pet package containing new modules. This is one the reason why Fatdog keeps the modules outside the main sfs - so that we can easily upgrade kernel & its modules without having to mess with the rest of the base system (just replace vmlinuz & its kernel-modules.sfs).