I am trying to understand/fix several (~30) modprobe failure messages during boot. The syslog messages are all similar to the following.
Code:
# journalctl |grep modprobe
Oct 23 14:26:14 15301634 systemd-udevd[117]: Process '/sbin/modprobe platform:Fixed MDIO bus' failed with exit code 1.
Oct 23 14:26:14 15301634 systemd-udevd[115]: Process '/sbin/modprobe platform:cpufreq-dt' failed with exit code 1.
Oct 23 14:26:14 15301634 systemd-udevd[116]: Process '/sbin/modprobe of:NocpT<NULL>Csimple-bus' failed with exit code 1.
Oct 23 14:26:14 15301634 systemd-udevd[119]: Process '/sbin/modprobe platform:alarmtimer' failed with exit code 1.
Oct 23 14:26:14 15301634 systemd-udevd[116]: Process '/sbin/modprobe of:NgpioT<NULL>Cti,omap4-gpio'
[...]
Taking the second error message for example. If I check the dependencies of "cpufreq-dt" using `modprobe -D`, it returns "builtin cpufreq-dt". This is correct because the .config file specifies "CONFIG_CPUFREQ_DT=y". So why is the kernel calling modprobe to load the module? How can I prevent this from happening?