Failed to start load linux kernel module after update (MSI/AMD)

General system Kernel, boot, graphics & hardware
1

Just updated and I’m seeing the error Failed to start load linux kernel module after update in red text during startup. It also shows to check systemctl status systemd-modules-load.service for more information, which shows the following:

systemctl status systemd-modules-load.service
× systemd-modules-load.service - Load Kernel Modules
     Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static)
     Active: failed (Result: exit-code) since Mon 2024-07-22 10:02:37 CDT; 11min ago
 Invocation: 442ebe5477404df581a19bd983a37e1e
       Docs: man:systemd-modules-load.service(8)
             man:modules-load.d(5)
    Process: 1218 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=>
   Main PID: 1218 (code=exited, status=1/FAILURE)

Jul 22 10:02:37 delta1 systemd[1]: systemd-modules-load.service: Main process exited, c>
Jul 22 10:02:37 delta1 systemd[1]: systemd-modules-load.service: Failed with result 'ex>
Jul 22 10:02:37 delta1 systemd[1]: Failed to start Load Kernel Modules.
Jul 22 10:02:37 delta1 systemd[1]: Starting Load Kernel Modules...
Jul 22 10:02:37 delta1 systemd[1]: systemd-modules-load.service: Main process exited, c>
Jul 22 10:02:37 delta1 systemd[1]: systemd-modules-load.service: Failed with result 'ex>
Jul 22 10:02:37 delta1 systemd[1]: Failed to start Load Kernel Modules.

Then I checked lspci > log.txt && lsusb >> log.txt && journalctl -b -0 >> log.txt && cat log.txt | eos-sendlog and looked for the timestamp 10:02:37 and found this:

Jul 22 10:02:37 delta1 kernel: [drm] amdgpu kernel modesetting enabled.
Jul 22 10:02:37 delta1 kernel: amdgpu: vga_switcheroo: detected switching method \_SB_.PCI0.GP17.VGA_.ATPX handle
Jul 22 10:02:37 delta1 kernel: amdgpu: ATPX version 1, functions 0x00000001
Jul 22 10:02:37 delta1 kernel: amdgpu: ATPX Hybrid Graphics
Jul 22 10:02:37 delta1 kernel: msi_ec: Firmware version is not supported: '15CKEMS1.108'
Jul 22 10:02:37 delta1 kernel: iwlwifi 0000:04:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420
Jul 22 10:02:37 delta1 kernel: thermal thermal_zone1: failed to read out thermal zone (-61)
Jul 22 10:02:37 delta1 systemd[1]: Mounted /efi.
Jul 22 10:02:37 delta1 kernel: AMD Address Translation Library initialized
Jul 22 10:02:37 delta1 kernel: intel_rapl_common: Found RAPL domain package
Jul 22 10:02:37 delta1 kernel: intel_rapl_common: Found RAPL domain core
Jul 22 10:02:37 delta1 kernel: amdgpu: Virtual CRAT table created for CPU
Jul 22 10:02:37 delta1 kernel: amdgpu: Topology: Add CPU node
Jul 22 10:02:37 delta1 kernel: amdgpu 0000:03:00.0: enabling device (0000 -> 0002)

Is the line showing Jul 22 10:02:37 delta1 kernel: msi_ec: Firmware version is not supported: '15CKEMS1.108' telling me my firmware is in some way no longer supported? I checked MSI and it is the latest firmware, dated 2023-09-28.

Here is that full report: https://dpaste.com/6F5KJP858

And in case it’s needed: inxi -Faz

2

Looks like it is the correct UEFI Bios and also firmware. Not sure what it means but i assume the error is reported because it’s failing to load the modules. :thinking:

The update may have failed or was a partial update? You may have to arch-chroot and try running the update again? :thinking: I’m just not sure? Did you try restarting the systemd-modules-load.service?

3

This is not a fatal/serious error message.
For serious (non-fatal) messages, filter journal:

journalctl -b0 -p3

You haven’t explained if your system works fine, or something looks broken. Journal messages are mostly informational, unless they are not :wink: .

1 Like
4

I assumed it wasn’t working. :upside_down_face:

1 Like
5

:man_facepalming:

My apologies, I went overkill on that original journal based on other posts I was reading.
Correct, the system is working but I was trying to identify the multiple red-text errors I see while I’m booting in case I need to proactively prevent worse problems.

Filtered journal: https://dpaste.com/CC3G4XL6T

6

This is a problem with a lot of linux users. They tend to seem to want to always be looking for error messages when in fact there is no problem and a lot of error messages are purely informational. I also find they are always concerned with the amount ram being used when in fact in many cases it makes no difference as long as the computer works fine there isn’t any issue. I don’t care how much ram my system is using if it is working like it should. I never even look at that stuff. I look at error messaging if there is a hardware problem or if i think it is related to an issue. Otherwise I don’t concern myself too much with it. I look more to make sure that my UEFI Bios is completely up todate. That is more important to me and to the hardware than informational error messaging that is not affecting how the hardware works albeit sometimes it is connected.

Edit: Don’t get me wrong here. I do think it is good to take notice. Sometimes when one does have issues it can come in handy knowing what information you are seeing. :wink:

Edit: A lot of these error messages are based on hardware and poor implementation of UEFI Bios by many manufacturers. Some on the other hand show very little messaging such as my systems. The logs are almost pristine except for some Kde software error messaging.

1 Like
7

Most of them are firmware related, upstream kernel devs might be interested, if you report them.
If you have an msi related AUR package installed, you might check for re-installation/update.

The most serious looking is the cryptofile.bin, maybe confirm/check your crypto setup.

1 Like
8

@ricklinux Good message to not give too much energy to things that aren’t broken. Guess I took too much notice of the error message because it was new, despite everything functioning as expected.

@petsam I’ll check my AUR packages again, but definitely looking into the crypto setup. After an update some time ago it did stop asking for the password for both drives and only have to enter it for one.

2 Likes