# Kernel module error at boot with LTS kernel

**URL:** <https://forum.endeavouros.com/t/kernel-module-error-at-boot-with-lts-kernel/1216>\
**Category:** General system\
**Created:** [August 25, 2019, 2:11am UTC](https://forum.endeavouros.com/t/kernel-module-error-at-boot-with-lts-kernel/1216 "2019-08-25T02:11:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![roadhazard](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/r/96bed5/32.png) [@roadhazard](https://forum.endeavouros.com/u/roadhazard)\
**Post date:** [August 25, 2019, 2:11am UTC](https://forum.endeavouros.com/t/kernel-module-error-at-boot-with-lts-kernel/1216/1 "2019-08-25T02:11:28Z")

</div>

When I boot the latest kernel, I don’t get any boot error. However, when I boot the LTS kernel, I get an error about ‘failed to start kernel modules’ (or something along those lines). It gives me a command to type to troubleshoot and this is the resulting data:

```auto
[roadhazard@server-pc ~]$ sudo systemctl status systemd-modules-load.service 
[sudo] password for roadhazard: 
● systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static>
   Active: failed (Result: exit-code) since Sat 2019-08-24 21:49:12 EDT; 21s ago
     Docs: man:systemd-modules-load.service(8)
           man:modules-load.d(5)
  Process: 361 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, st>
 Main PID: 361 (code=exited, status=1/FAILURE)

Warning: Journal has been rotated since unit was started. Log output is incompl>
lines 1-9/9 (END)...skipping...
● systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Sat 2019-08-24 21:49:12 EDT; 21s ago
     Docs: man:systemd-modules-load.service(8)
           man:modules-load.d(5)
  Process: 361 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
 Main PID: 361 (code=exited, status=1/FAILURE)

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
~

```

I saw a similar post: [Failed to start kernel (lts) modules - #53 by makeixo](https://forum.endeavouros.com/t/failed-to-start-kernel-lts-modules/538/53) but I’m affraid to carry out those steps in case my configuration is different. I’m running my Plex/media/backup server on EOS and can’t risk screwing it up. 🙂

---

<div class="post-metadata">

**Author:** ![ringo](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/ringo/32/66182_2.png) [@ringo](https://forum.endeavouros.com/u/ringo)\
**Post date:** [August 25, 2019, 7:13am UTC](https://forum.endeavouros.com/t/kernel-module-error-at-boot-with-lts-kernel/1216/2 "2019-08-25T07:13:46Z")

</div>

Hi, normal it should tell which module does not load wel.

This kinda log is incomplete. Check your installed modules. So like do you got dkms modules or  
only Arch modules like virtualbox-modules-host-arch.  
If you got only modules for the ‘linux’ kernel with there headers but got not a specifik modules for lts, mostly dkms, then is possible you get error at boot.

---

<div class="post-metadata">

**Author:** ![roadhazard](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/r/96bed5/32.png) [@roadhazard](https://forum.endeavouros.com/u/roadhazard)\
**Post date:** [August 25, 2019, 12:53pm UTC](https://forum.endeavouros.com/t/kernel-module-error-at-boot-with-lts-kernel/1216/3 "2019-08-25T12:53:20Z")

</div>

@ringo Thanks for the helping hand but I figured it out! I took your advice and started taking a closer look at installed modules (journalctl -b) and found this lurking in the logs:

```auto
Aug 25 08:32:44 server-pc systemd-modules-load[361]: Failed to find module 'pkcs8_key_parser'

```

Googling that up, I stumbled upon this Arch forum post: [https://bbs.archlinux.org/viewtopic.php?id=245535](https://bbs.archlinux.org/viewtopic.php?id=245535)

And did as they instructed:

```auto
pacman -Rs iwd

```

…and no more boot errors using the LTS kernel! 🙂