bumblebee fails on trying to modprobe "off"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bumblebee (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Currently Ubuntu switched to systemd by default, unfortunately bumblebee is not working in this case.
I have proprietary nvidia driver and bumblebee from standard repository, kernel 3.19.0.
nazar-
[ 523.733713] [ERROR]Cannot access secondary GPU - error: Could not load GPU driver
[ 523.733754] [ERROR]Aborting because fallback start is disabled.
with Driver=
nazar-
● bumblebeed.service - Bumblebee C Daemon
Loaded: loaded (/lib/systemd/
Active: active (running) since ср 2015-03-25 03:56:04 CET; 31s ago
Main PID: 16229 (bumblebeed)
Memory: 292.0K
CGroup: /system.
└─16229 /usr/sbin/
бер 25 03:56:04 nazar-pc systemd[1]: Started Bumblebee C Daemon.
бер 25 03:56:04 nazar-pc systemd[1]: Starting Bumblebee C Daemon...
бер 25 03:56:04 nazar-pc bumblebeed[16229]: [ 495.736332] [INFO]/
бер 25 03:56:32 nazar-pc bumblebeed[16229]: modprobe: ERROR: ../libkmod/
бер 25 03:56:32 nazar-pc bumblebeed[16229]: modprobe: ERROR: could not insert 'off': Function not implemented
бер 25 03:56:32 nazar-pc bumblebeed[16229]: [ 523.733668] [ERROR]Module nouveau could not be loaded (timeout?)
бер 25 03:56:32 nazar-pc bumblebeed[16229]: [ 523.733678] [ERROR]Could not load GPU driver
with Driver=nvidia
nazar-
● bumblebeed.service - Bumblebee C Daemon
Loaded: loaded (/lib/systemd/
Active: activating (auto-restart) (Result: exit-code) since ср 2015-03-25 04:01:52 CET; 1s ago
Process: 18370 ExecStart=
Main PID: 18370 (code=exited, status=1/FAILURE)
бер 25 04:01:52 nazar-pc systemd[1]: Unit bumblebeed.service entered failed state.
бер 25 04:01:52 nazar-pc systemd[1]: bumblebeed.service failed.
When booted with upstart - works perfectly
From bumblebee developer:
> Looks like a compatibility issue with the modprobe configuration file on Ubuntu.
> When I said compatibility, I think that systemd(/kmod?) does not like the alias nvidia off line in some modprobe configuration as supplied by the nvidia package.
Initially reported on GitHub: https:/
description: | updated |
description: | updated |
description: | updated |
bumblebeed itself fails in the modprobe call, so reassigning back for now. This could also belong to kmod, but let's find out what's wrong first. What does that command say?
grep -r off /etc/mod*
My suspicion is that there is some "alias whatever off" in /etc/modprobe.d which bumblebee tries to load, and bumblebee calls "modprobe whatever" and gets this error:
modprobe: ERROR: ../libkmod/ libkmod- module. c:816 kmod_module_ insert_ module( ) could not find module by name='off'
modprobe: ERROR: could not insert 'off': Function not implemented
This is how current kmod behaves, and is independent of systemd vs. upstart. That may or may not be a kmod bug, but I don't think it is -- "off" is not a magic name in any way, it's not documented in man modprobe.d. So it seems "off" is merely a convention, but modprobing indeed will fail. I'll wait for your confirmation, then we can set this to "Triaged", and I suggest the upstream bug should be reopened.
Thanks! bumblebee. conf (which gets installed into /etc/modprobe. d/bumblebee. conf) looks fine to me.
I don't see any "off" in the bumblebee source, and debian/