systemd error on start

English Install/Boot/Login
#1

“Failed to start Load Kernel Modules.” is the first line I see before plymouth takes over.

roger@VAIO:~> 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: active (exited) since Tue 2014-10-14 21:20:28 PDT; 9min ago
     Docs: man:systemd-modules-load.service(8)
           man:modules-load.d(5)
  Process: 410 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=0/SUCCESS)
 Main PID: 410 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/systemd-modules-load.service
#2

There is no useful info about your error in that status.

#3

Did the system start anyway?

If the system otherwise started normally, then this might not be an actual problem. It might be a limitation due to running off the “initrd” before the root directory is mounted.

#4

I didn’t think it was terribly useful either.

It does boot up, as far as I can tell it does so completely right. I figured it’d be good to know what that error is since I am having a driver issue pertaining to Bumblebee and NVidia proprietary driver. That and I don’t think it should go unaddressed.

#5

Do you have aqny idea about which version of openSUSE you are using? And do you mind sharing basic information that with your potential helpers?

#6

Running Factory x64. Don’t know what other information would be considered relevant.

#7

Try to run “systemctl status” as root, it should show more information then, i.e. an extract of the journal that should say why it failed to start.

sudo systemctl status systemd-modules-load.service

Although your systemctl output actually says it did not fail… :\

#8

The Factory lovers are in the Pre-release/Beta forum, not in the standard release versions section.

#9

It’s a bunch.

http://susepaste.org/80926240

#10

On 2014-10-15 20:56, Shadowolf7 wrote:
>
> hcvv;2669547 Wrote:
>> Do you have aqny idea about which version of openSUSE you are using? And
>> do you mind sharing basic information that with your potential helpers?
>
> Running Factory x64. Don’t know what other information would be
> considered relevant.

That’s a crucial bit of information, as Factory (13.2) boots differently
than the rest of the releases, and it has its own specific forum because
it has different problems. Thus, please request a moderator to move your
post to the beta, aka factory, subforum. Just click on the report
triangle button below.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

#11

The part for “Load System Modules” would have sufficed.
I.e. the output of:

sudo systemctl status systemd-modules-load.service

as I wrote.

Anyway, that doesn’t tell more unfortunately.

No idea then, other than that it’s probably an initrd problem as nrickert mentioned. I do not see this here on my Factory installation.
Try to re-create the initrd maybe?

sudo mkinitrd
#12

On 2014-10-15 23:16, wolfi323 wrote:

> No idea then, other than that it’s probably an initrd problem as
> nrickert mentioned. I do not see this here on my Factory installation.
> Try to re-create the initrd maybe?

But factory now uses dracut.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

#13

“mkinitrd” runs “dracut” with standardized arguments (on factory).

#14

On 2014-10-15 23:56, nrickert wrote:
>
> robin_listas;2669675 Wrote:
>> But factory now uses dracut.
>
> “mkinitrd” runs “dracut” with standardized arguments (on factory).

The OP is using factory, so the thread is on the wrong forum.
Yes, the call to “mkinitrd” is kept for compatibility, but it is dracut,
with different problems than any other release.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

#15

Will be moved to Pre-release/Beta and is CLOSED for the moment.

#16

Moved from Install/Boot/Login and open again.

#17

Is this thread still alive? I have the exact issue on 13.2 GM

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 Sun 2014-11-02 06:35:54 IST; 3min 25s ago
     Docs: man:systemd-modules-load.service(8)
           man:modules-load.d(5)
  Process: 457 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
 Main PID: 457 (code=exited, status=1/FAILURE)

Nov 02 06:35:54 Anon systemd[1]: Failed to start Load Kernel Modules.

-Hrudai.

#18

How many kernels have you installed?

I was getting something like that when a kernel update broke V-box kernel module or something like that
I uninstalled whatever it was; rebooted and reinstalled it; no more "Failed to start Load Kernel Modules"here

#19

I have 3 kernels installed.

  1. 3.17.2
  2. 3.17.1
  3. 3.16.1

It’s the same on all three. Uninstall–>reboot–>reinstall didn’t fix it either.

P.S: ran sudo mkinitrd after login and tried to start the service, still no change.

Thanks,
Hrudai.

#20

I was getting something similar after kernel upgrade; had multiple kernels and a Packman “Broadcom WL” driver that I rebuilt the rpm from a SRC.rpm.

With 13.2 GM, the kernel is linux-3.16.6-2-desktop #1; I deleted all the other kernels and deleted all instances of Broadcom WL,rpm (kernel module one also) that I had built in YAST, ran bootloader; rebooted.

Rebuild the Broadcom WL,rpm; install; reboot; no more “Failed to start Load Kernel Modules”

Search YAST for “kernel” and see if there are any module rpms orphaned.

What errors/warnings are in “DMESG”; search it for “module”

Good luck!

PS: When 13.2 GA is released, I’ll do a clean install for reasons like this