"[FAILED] Failed to start systemd-modules-load.service - Load Kernel Modules."

Ask Fedora
, , ,
1

At boot the error message “[FAILED] Failed to start systemd-modules-load.service - Load Kernel Modules.” appears for a split second before the LUKS password prompt is displayed. After that, my laptop seems to work normally. What’s this error? I didn’t see it before in F41 or even when I first did an in place upgrade to F42. Seems to be new but I’m not 100% sure. I had to video the boot process to catch the frame that it is displayed. I really couldn’t read it because it disappears so quickly. I’m using a Lenovo Yoga (Intel, with no separate graphics.)

EDIT: Here is the dmesg output with the relevant part:>

[ 1.517076] systemd[1]: Starting dracut-cmdline.service - dracut cmdline hook...

[ 1.525797] mc: Linux media interface: v0.10

[ 1.549897] videodev: Linux video capture interface: v2.00

[ 1.558061] Loading of module with unavailable key is rejected

[ 1.560815] Loading of module with unavailable key is rejected

[ 1.561222] systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE

[ 1.561293] systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.

[ 1.561412] systemd[1]: Failed to start systemd-modules-load.service - Load Kernel Modules.

[ 1.561441] fbcon: Taking over console

[ 1.562103] systemd[1]: Starting systemd-sysctl.service - Apply Kernel Variables...

[ 1.563616] Console: switching to colour frame buffer device 240x75

[ 1.587978] systemd[1]: Finished dracut-cmdline.service - dracut cmdline hook.

Specs below:

System Details Report

Report details

  • Date generated: 2025-04-21 11:42:58

Hardware Information:

  • Hardware Model: Lenovo Yoga 7 14IRL8
  • Memory: 16.0 GiB
  • Processor: 13th Gen Intel® Core™ i7-1360P × 16
  • Graphics: Intel® Iris® Xe Graphics (RPL-P)
  • Disk Capacity: 512.1 GB

Software Information:

  • Firmware Version: LHCN27WW
  • OS Name: Fedora Linux 42 (Workstation Edition)
  • OS Build: (null)
  • OS Type: 64-bit
  • GNOME Version: 48
  • Windowing System: Wayland
  • Kernel Version: Linux 6.14.2-300.fc42.x86_64
2

Seems you are configured to load modules that do not have the correct signing key. Did you add 3rd party modules?

3

I have same problem with same kernel .Solved like that Disable secure boot

4

I take it that you also had 3rd party code that was not getting signed as required then?

5

yes same unsigned key nothing that is 3rd party modules that I’m aware It’s intel cpu with integrated intel gpu

6

This service only runs if there is something configured.
You can see all the folders that are checked by looking at this output
and the ConditionDirectoryNotEmpty= lines.

systemctl cat systemd-modules-load.service

I think this will list all the modules that will be loaded:

ls -l /lib/modules-load.d \
/usr/lib/modules-load.d \
/usr/local/lib/modules-load.d \
/etc/modules-load.d \
/run/modules-load.d \
;

To see the errors I assume that you must have a module configured that was not provided by Fedora RPMs.

All I see is these logs on two Fedora systems I checked:

systemctl status systemd-modules-load.service | cat
...
Apr 19 10:47:29 fender.internal systemd-modules-load[4557]: Module 'msr' is built in
Apr 19 10:47:29 fender.internal systemd[1]: Finished systemd-modules-load.service - Load Kernel Modules.
7

I suspected the module v4l2loopback was the culprit. I removed it, made a dracut regenerate and the problem went away. I don’t know why it was there. Maybe Waydroid which was already uninstalled, or anydesk & teamviewer which uninstalling them didn’t solve.