LinuxQuestions.org - kernel/modprobe trying to load built-in drivers during boot

- Linux - Kernel (https://www.linuxquestions.org/questions/linux-kernel-70/)

- - kernel/modprobe trying to load built-in drivers during boot (https://www.linuxquestions.org/questions/linux-kernel-70/kernel-modprobe-trying-to-load-built-in-drivers-during-boot-4175730191/)

kernel/modprobe trying to load built-in drivers during boot

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?

Hello, CaptGG & welcome to LQ.

The kernel gives a debug level of output while booting. So everything that counts as an error is mentioned, but they don't all need to be fixed. I would ignore those messages.

As for fixing them, I don't know because I have no clue about your system. You told us nothing at all about your system, initrd, kernel, or OS. You can rebuild your kernel or initrd to 'fix' them, but I fancy your distro made the error. They probably saw them and ignored them.