You are not logged in.
Hello community. The last full upgrade of June 4, in which the kernel was upgrade to v3.9.4 from v3.8.2, brought some complications for some kernel modules and as I'd like your keen eyes to help me shoot them all. Here they are:
- After the last kernel upgrade and bumblebee-git reinstallation, the bumblebee daemon could be systemctl-started although with the same configuration and access, it logs the following error
Could not set the GID of bumblebeeAny ideas why?
- BBswitch could not be systemctl-started anymore. Systemctl returns with the error
Unit bbswitch.service failed to load: No such file or directory.although the kernel buffer says otherwise:
[ 14.395884] bbswitch: version 0.7
[ 14.395891] bbswitch: Found integrated VGA device 0000:00:02.0: \_SB_.PCI0.GFX0
[ 14.395895] bbswitch: Found discrete VGA device 0000:01:00.0: \_SB_.PCI0.PEG0.PEGP
[ 14.396042] bbswitch: detected an Optimus _DSM function
[ 14.396078] bbswitch: disabling discrete graphics
[ 14.441452] bbswitch: [b]Succesfully loaded[/b]. Discrete card 0000:01:00.0 is off
[ 320.757595] bbswitch: enabling discrete graphics
[ 321.246286] bbswitch: disabling discrete graphicsWhere does this come from?
- Last but not least, the systemd-modules-load service could be not started.
I suspect these errors have something to do in common but miss some clues to start fixing them.
Could you give a hand? Thanks a lot.
Offline
bbswitch has no systemd unit. If bumblebeed fails to start, ensure that you have fully upgraded your system, including the filesystem package. bumblebeed should then be located at /usr/bin/bumblebeed.
What does journalctl say about bumblebeed?
Offline
Here's the output of a # journalctl -u bumblebeed -xmn 10
Jun 08 12:23:37 nu systemd[1]: Starting Bumblebee C Daemon...
-- Subject: Unit bumblebeed.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit bumblebeed.service has begun starting up.
Jun 08 12:23:37 nu systemd[1]: Started Bumblebee C Daemon.
-- Subject: Unit bumblebeed.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit bumblebeed.service has finished starting up.
--
-- The start-up result is done.
Jun 08 12:23:37 nu bumblebeed[1450]: [ 321.362249] [INFO]/usr/bin/bumblebeed 3.2.1 started
Jun 08 13:34:49 nu bumblebeed[1450]: [ 4593.804544] [WARN]Received Terminated signal.
Jun 08 13:34:49 nu systemd[1]: Stopped Bumblebee C Daemon.
-- Subject: Unit bumblebeed.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/9d1aaa27d60140bd96365438aad20286
--
-- Unit bumblebeed.service has finished shutting down.
Jun 08 17:10:49 nu bumblebeed[737]: [ 23.324420] [INFO]/usr/bin/bumblebeed 3.2.1 startedAs silly as it may sound, the bumblebee daemon logs out:
[ 1253.904780] [DEBUG]Found card: 01:00.0 (discrete)
[ 1253.904820] [DEBUG]Found card: 00:02.0 (integrated)
[ 1253.904830] [DEBUG]Reading file: /etc/bumblebee/bumblebee.conf
[ 1253.905599] [DEBUG]Process /sbin/modprobe started, PID 2612.
[ 1253.905666] [DEBUG]Hiding stderr for execution of /sbin/modprobe
[ 1253.907070] [DEBUG]SIGCHILD received, but wait failed with No child processes
[ 1253.907094] [DEBUG]Detected nvidia driver (module nvidia)
[ 1253.907204] [DEBUG]succesfully loaded bbswitch
[ 1253.907215] [INFO]Switching method 'bbswitch' is available and will be used.
[ 1253.907221] [DEBUG]Active configuration:
[ 1253.907238] [DEBUG] bumblebeed config file: /etc/bumblebee/bumblebee.conf
[ 1253.907246] [DEBUG] X display: :8
[ 1253.907253] [DEBUG] LD_LIBRARY_PATH: /usr/lib/nvidia:/usr/lib32/nvidia
[ 1253.907261] [DEBUG] Socket path: /var/run/bumblebee.socket
[ 1253.907268] [DEBUG] xorg.conf file: /etc/bumblebee/xorg.conf.nvidia
[ 1253.907275] [DEBUG] xorg.conf.d dir: /etc/bumblebee/xorg.conf.d
[ 1253.907283] [DEBUG] ModulePath: /usr/lib/nvidia/xorg/,/usr/lib/xorg/modules
[ 1253.907290] [DEBUG] GID name: bumblebee
[ 1253.907298] [DEBUG] Power method: bbswitch
[ 1253.907305] [DEBUG] Stop X on exit: 1
[ 1253.907312] [DEBUG] Driver: nvidia
[ 1253.907319] [DEBUG] Driver module: nvidia
[ 1253.907327] [DEBUG] Card shutdown state: 1
[ 1253.907444] [DEBUG]Process /sbin/modprobe started, PID 2613.
[ 1253.907524] [DEBUG]Hiding stderr for execution of /sbin/modprobe
[ 1253.908695] [DEBUG]SIGCHILD received, but wait failed with No child processes
[ 1253.908750] [DEBUG]Configuration test passed.
[ 1253.909106] [ERROR]Could not set the GID of bumblebee: Operation not permittedIs it possible that bumblebeed doesn't have access to the appropriate group causing all this?
Offline
No idea why you get EPERM. Does the bumblebee group exist? Besides that, I do not see issues, do you have any?
Offline
Me neither
The bumblebee group exists ; the excerpt of the /etc/group indicates it.
users:x:100:
dbus:x:81:
avahi:x:84:
git:x:998:io
uuidd:x:68:
plugdev:x:46:io
polkitd:x:102:
bumblebee:x:997:io
ntp:x:87:
systemd-journal:x:190:And I concur with you, besides the eperm, it seems there is no issue and bumblebeed causes no trouble -- which makes me want to pull my hair.
Could it be possible that the Intel pstate introduced in the kernel 3.9.x induces this error?
Since it's here, the cpu frequency scaling governor has been set by default to powersave instead of ondemand.
Offline
Does it work ok with the official bumblebee package? Did you reboot after switching to 3.9.4?
Offline
With either of bumblebee and bumblebee-git packages, the dameon hangs at the same step with the same error. The process was to upgrade to 3.9.4, right after the initramfs was generated, to recompile and reinstall bumblebee-git, terminated by a reboot. This was what is done at each full upgrade and insofar, no such problem. At first, the official bumblebee package was prefered over the one in aur. As it raises this error, the development version replaced it---without any luck.
Last edited by nunobaba (2013-06-10 12:09:51)
Offline