You are not logged in.
SOLUTION @ POST #2
At some point within the past few weeks I've broken Bumblebee. I am not sure if this happened after an update, or if I did something to break it unintentionally. I will dump hardware specs, proof that daemon is running, installed packages, and errors below. Based on the output of optirun, I assume it might have something to do with a misconfigured config file, since it tries to access nouveau instead of nvidia.
Hardware Specs:
# lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
01:00.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 540M] (rev a1)
Daemon Confirmation:
# systemctl | grep bumblebee
bumblebeed.service loaded active running Bumblebee C Daemon
Installed packages:
# pacman -Q nvidia-bumblebee nvidia-utils-bumblebee lib32-nvidia-utils-bumblebee bbswitch bumblebee primus-git lib32-primus-git
nvidia-bumblebee 310.19-1
nvidia-utils-bumblebee 310.19-1
lib32-nvidia-utils-bumblebee 310.19-2
bbswitch 0.5-2
bumblebee 3.0.1-4
primus-git 20121217-1
lib32-primus-git 20121217-1
Primusrun error:
# primusrun glxgears
primus: fatal: failure contacting bumblebee daemon
Optirun error:
# optirun -vv glxgears -info
[43120.847658] [DEBUG]Reading file: /etc/bumblebee/bumblebee.conf
[43121.036876] [DEBUG]optirun version 3.0.1 starting...
[43121.036897] [DEBUG]Active configuration:
[43121.036903] [DEBUG] bumblebeed config file: /etc/bumblebee/bumblebee.conf
[43121.036907] [DEBUG] X display: :8
[43121.036911] [DEBUG] LD_LIBRARY_PATH:
[43121.036915] [DEBUG] Socket path: /var/run/bumblebee.socket
[43121.036919] [DEBUG] VGL Compression: proxy
[43121.143733] [INFO]Response: No - error: [XORG] (EE) Failed to load module "nouveau" (module does not exist, 0)
[43121.143753] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) Failed to load module "nouveau" (module does not exist, 0)
[43121.143759] [DEBUG]Socket closed.
[43121.143775] [ERROR]Aborting because fallback start is disabled.
[43121.143781] [DEBUG]Killing all remaining processes.
Last edited by qKUqm3wtY4 (2013-02-07 20:30:28)
I am a noob. Ask me nothing.
Offline
Which Driver is selected in /etc/bumblebee/bumblebee.conf? It should be
Driver=nvidia
Offline
Which Driver is selected in /etc/bumblebee/bumblebee.conf? It should be
Driver=nvidia
Strangely, the config file didn't specify a driver; it simply says, "Driver=". I added in, "nvidia", saved, and rebooted. Now I get a new error when running optirun.
# optirun -vv glxgears
[ 608.997724] [DEBUG]Reading file: /etc/bumblebee/bumblebee.conf
[ 608.997950] [INFO]Configured driver: nvidia
[ 608.997979] [ERROR]The Bumblebee daemon has not been started yet or the socket path /var/run/bumblebee.socket was incorrect.
[ 608.997985] [DEBUG]Socket closed.
[ 608.997994] [ERROR]Could not connect to bumblebee daemon - is it running?
So, I restarted the daemon and when I check it's status, it says, "loaded activating". I'm not sure what to do at this point.
# systemctl | grep bumblebee
bumblebeed.service loaded activating auto-restart Bumblebee C Daemon
Last edited by qKUqm3wtY4 (2013-02-05 05:17:50)
I am a noob. Ask me nothing.
Offline
Did you try
systemctl start bumblebeed
?
Offline
Did you try
systemctl start bumblebeed
?
Yes. It stays stuck in this, "loaded activating" state. It doesn't matter if I restart the daemon either.
# systemctl start bumblebeed
# systemctl | grep bumblebee
bumblebeed.service loaded activating auto-restart Bumblebee C Daemon
I am a noob. Ask me nothing.
Offline
What if I purge my system of all video based packages and then reinstall? What types of problems would I run into by doing this? Is it worth bothering with? Most of the required packages are from the AUR, so there will be a few more steps involved if I go this route.
I am a noob. Ask me nothing.
Offline
I am going to mark this as solved, since technically post #2 did fix the error message.
I am a noob. Ask me nothing.
Offline