Failed to start Load Kernel Modules after bumblebee installation

I followed suse’s tutorial on how to install bumblebee step by step on the newly installed 42.1 system.

After installation, I have got these boot errors

~ # journalctl -b -p err
-- Logs begin at Sat 2016-03-05 09:55:46 CST, end at Tue 2016-03-08 19:31:01 CST. --
Mar 08 19:30:08 LENSU kernel: Ignoring BGRT: invalid status 0 (expected 1)
Mar 08 19:30:08 LENSU systemd[1]: Failed to start Load Kernel Modules.
Mar 08 19:30:18 LENSU systemd-udevd[827]: invalid key/value pair in file /usr/lib/udev/rules.d/51-android.rules on line 115,starting at character 57 ('')
Mar 08 19:30:21 LENSU audispd[1204]: No plugins found, exiting

optirun glxspheres is OK, but

~ primusrun glxspheres
Polygons in scene: 62464 (61 spheres * 1024 polys/spheres)
Visual ID of window: 0xb3
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  154 (GLX)
  Minor opcode of failed request:  24 (X_GLXCreateNewContext)
  Value in failed request:  0x0
  Serial number of failed request:  17
  Current serial number in output stream:  18

I need to use steam, which uses primusrun instead of optirun. And what is that kernel module load error?

Assuming that you followed the tutorial to the last word, maybe your initrd was not refreshed; try to open a terminal and as superuser issue:

dracut --host-only --force

That should rebuild the initrd with the new Nvidia kernel modules and hopefully fix your problem.
Please write back if that is not the case. Good Luck!

If this is to use Steam on the NVIDIA, be prepared to get very happy :D. Bo Simonson packages “suse-prime”. It allows you to run your entire X-session on either the Intel or the NVIDIA.
Here’s the OBS page with instructions, I followed these on my Optimus based laptop and it works great.

Compared to optirun and primusrun it’s a huge improvement. IMHO.

I’ll try it when I get back to the machine.

I did some further research and think maybe I should keep using bumblebee instead of prime, which need switch between intel/nvidia with session logon/off. When you say it’s a huge improvement, do you mean the performance? Don’t they use the same NVIDIA properties’ driver?

I did a dup for plasma5 repo and after restart, the kernel module error is gone. Primusrun works too now.

Nice to know, maybe a refresh to the initrd was part of this last dup…
RE bumblebee performance, you might be interested in this thread
]( Bumblebee has a delay of maybe 4-5 ms when copying the graphics buffer from Nvidia to Intel for display that might be a concern for gamers; I didn’t try suse-prime myself (yet), so I cannot comment on the performance advantage, if any.

Many with openSUSE are recommending “suse-prime” instead of Bumblebee as it has better written scripts.