Some modules not loading on boot after kernel reconfigure

[equaeghe]

I have been creating a ‘clean’, well-documented kernel config for my system. When booting, it does not load some modules (such as ext4 for a partition automounted at boot). This leaves me with a crippled system if I use that kernel. (I have other kernels that do boot nicely.)
When I modprobe these modules that should have been loaded at boot, they load fine. With my existing kernels, they are loaded automatically at boot.

I am at a loss for what the reason may be: autoloading works for a decent number of modules, but not for all en apparently the ones that do not autoload can be modprobed correctly. In my logs (journalctl -b), I see some consequences of non-loaded modules, but no error or warning messages about failure to load modules. Any help diagnosing and fixing this is much appreciated.

[pietinger]

[equaeghe]

[pietinger]

If you have no errors in your dmesg, then I would be interested in your kernel version and your selectings in your kernel configuration - section: "Enable loadable module support".

[Goverp]

Apologies if this is screwy but, I thought there were approx. 4 ways to load modules:

• initramfs/initrd config or script;
• /etc/modules.d and its imitations;
• udev; and
• something explicit calling modprobe during init.

IIUC there's no kernel function that automatically loads a module just 'cos the system won't work without it
_________________
Greybeard

[equaeghe]

[equaeghe]

[pietinger]

[pietinger]