"Failed to start Load Kernel Modules" at startup

Hey what’s up:sarcastic:
(openSUSE Leap 42.1 Gnome 3 Dell Inspiron Laptop)
After installing bumblebee (for nouveau drivers according to the official openSUSE article) which works perfectly fine, I can see a line or two in startup (before the plymouth login screen) which tells me that “Failed to start Load Kernel Modules”
I am sure this happens because of bumblebee since I have installed it after clean install and updating more than 15 times (:O)
Please can you help me figure out why that message pops up and how I can fix it (even though it looks harmless since at least bumblebee works [tested with

optirun glxspheres

])

If you require more info please tell me what to post and how to find it

Thanks!!!

It’s likely that modules weren’t built successfully the last time you re-compiled modules for your kernel.
It’s also likely that what you’re seeing are only warnings (modules aren’t often critical to core functionality) and not critical notifications.

Recommend that the next time you compile a new kernel (next system update that includes a kernel upgrade?) that you watch your stdout carefully. Kernel module build output almost always will report successful and unsuccessful module builds.

If you’re really bothered by the notifications and want to know your current situation, you should probably be able to search your system journal using keywords like FAILED.

TSU

Thanks for replying
What is that “stdout” you mentioned? A command? How do I use it?

The exact process I followed is this:
https://en.opensuse.org/SDB:NVIDIA_Bumblebee
I used the Leap repository of course. And followed every step. What may have caused the error I’m talking about?:sarcastic:
Also when I used the mkinitrd command at the end I received a few errors like this:

dracut module 'blablabla' could not be installed, because command 'blablabla2'
could not be found!

But then the process succeeds. I think…
I am sorry but I do not remember the exact outputs. :’(

If this is not enough, ask me whatever info you wish me to provide

(when I use cnf blablabla2 I can find the package that contains the missing command and install it, but I don’t know if this is necessary since it doesn’t change anything from what I saw)

stdout is standard out channel ie what you see normally in a terminal

You need to post your mkinitrd output to a pastebin, then provide a link to your pastebin in your Forum post.
Otherwise, no one can evaluate your “blablabla2” errors…
:slight_smile:

TSU

:wink: Okay I a going to post the output of mkinitrd but I’m sorry, what is “pastebin”?

And yes I would like to resolve any issue , I don’t like having errors of any kind

Here :wink:

linux-xken:~ # mkinitrd
Creating initrd: /boot/initrd-4.4.0-3-default
dracut: Executing: /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --force /boot/initrd-4.4.0-3-default 4.4.0-3-default
dracut: dracut module 'multipath' will not be installed, because command 'multipath' could not be found!
dracut: dracut module 'fcoe-uefi' will not be installed, because command 'dcbtool' could not be found!
dracut: dracut module 'fcoe-uefi' will not be installed, because command 'fipvlan' could not be found!
dracut: dracut module 'fcoe-uefi' will not be installed, because command 'lldpad' could not be found!
dracut: dracut module 'multipath' will not be installed, because command 'multipath' could not be found!
dracut: dracut module 'fcoe-uefi' will not be installed, because command 'dcbtool' could not be found!
dracut: dracut module 'fcoe-uefi' will not be installed, because command 'fipvlan' could not be found!
dracut: dracut module 'fcoe-uefi' will not be installed, because command 'lldpad' could not be found!
dracut: *** Including module: bash ***
dracut: *** Including module: systemd ***
dracut: *** Including module: warpclock ***
dracut: *** Including module: systemd-initrd ***
dracut: *** Including module: i18n ***
dracut: *** Including module: drm ***
dracut: *** Including module: plymouth ***
dracut: *** Including module: btrfs ***
dracut: *** Including module: kernel-modules ***
dracut: *** Including module: resume ***
dracut: *** Including module: rootfs-block ***
dracut: *** Including module: terminfo ***
dracut: *** Including module: udev-rules ***
dracut: Skipping udev rule: 40-redhat.rules
dracut: Skipping udev rule: 50-firmware.rules
dracut: Skipping udev rule: 50-udev.rules
dracut: Skipping udev rule: 91-permissions.rules
dracut: Skipping udev rule: 80-drivers-modprobe.rules
dracut: *** Including module: biosdevname ***
dracut: *** Including module: dracut-systemd ***
dracut: *** Including module: haveged ***
dracut: *** Including module: usrmount ***
dracut: *** Including module: base ***
dracut: *** Including module: fs-lib ***
dracut: *** Including module: shutdown ***
dracut: *** Including module: suse ***
dracut: *** Including modules done ***
dracut: *** Installing kernel module dependencies and firmware ***
dracut: *** Installing kernel module dependencies and firmware done ***
dracut: *** Resolving executable dependencies ***
dracut: *** Resolving executable dependencies done***
dracut: *** Hardlinking files ***
dracut: *** Hardlinking files done ***
dracut: *** Stripping files ***
dracut: *** Stripping files done ***
dracut: *** Generating early-microcode cpio image ***
dracut: *** Constructing GenuineIntel.bin ****
dracut: *** Store current command line parameters ***
dracut: Stored kernel commandline:
dracut:  resume=UUID=986e3569-77e7-4cb7-b95e-a600dadfead0
dracut:  root=UUID=264a4d84-6589-4f7b-87e9-0661ff8430a6 rootfstype=btrfs rootflags=rw,relatime,space_cache,subvolid=258,subvol=/.snapshots/1/snapshot,subvol=.snapshots/1/snapshot
dracut: *** Creating image file '/boot/initrd-4.4.0-3-default' ***
dracut: *** Creating initramfs image file '/boot/initrd-4.4.0-3-default' done ***
linux-xken:~ # 

dracut: dracut module 'multipath' will not be installed, because command 'multipath' could not be found!
dracut: dracut module 'fcoe-uefi' will not be installed, because command 'dcbtool' could not be found!
dracut: dracut module 'fcoe-uefi' will not be installed, because command 'fipvlan' could not be found!
dracut: dracut module 'fcoe-uefi' will not be installed, because command 'lldpad' could not be found!
dracut: dracut module 'multipath' will not be installed, because command 'multipath' could not be found!
dracut: dracut module 'fcoe-uefi' will not be installed, because command 'dcbtool' could not be found!
dracut: dracut module 'fcoe-uefi' will not be installed, because command 'fipvlan' could not be found!
dracut: dracut module 'fcoe-uefi' will not be installed, because command 'lldpad' could not be found!

The above “informationals” are not unusual, I see similar with every kernel compile. openSUSE maintainers make their decision what to include or exclude from upstream kernel source and pass that down to you.
The important issue is to take that information to the next level, are any of those modules required for anything you do? If so, <then> you should ask how those modules can be built by the maintainers (recommend submit a bug at https://bugzilla.opensuse.org) or by yourself.

Pastebins are websites that will post anything from anyone. You can post anonymously (a popular way to dump stolen secrets publicly) or as a logged in User. If you login, you can manage and modify your posting after your initial post. Pastebins are used by Forums and other support channels (like IRC) which may have real or practical restrictions on how much info you can post at a time. What you posted here is OK, but if for instance you posted a day of logfile activity it would be too large to post here, so you can post on a pastebin and then include the URL to your pastebin in your Forum post.

openSUSE has its own pastebin
http://paste.opensuse.org

There is also the original(?) pastebin that’ll accept posts about anything

TSU

You sure know what you are talking about :wink: thanks

Btw I used the cnf command (for example: cnf multipath) and found the missing packages and installed them, and then the mkinitrd command had no such errors. However I didn’t exactly know what I am doing, I just waned to fix the error I see during booting, and installing these packages made no change to that :X But I am happy to know that this this “dracut moduled could not be installed” is not a problem, according to what you posted.
So in conclusion, maybe bumblebee is not very compatible with openSUSE’s Leap kernel? Or is it something else?

Bumblebee has special requirements.
An SDB has been created for Bumblebee
https://en.opensuse.org/SDB:NVIDIA_Bumblebee

TSU

Yes I followed the directions in the link :slight_smile:

By the way, no 2016 snapshot of Tumbleweed has shown me this message after installing bumblebee in my Dell