Не могу настроить bumblebee

 , ,



Debian 7.8. Две видеокарты intel hd graphics и Nvidia 610M. Установил bumblebee. Но он не работает. Ошибка:

[  743.013948] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) No devices detected.

[  743.013984] [ERROR]Aborting because fallback start is disabled.
Конфиг вроде настроен правельно. /etc/bumblebee/xorg.conf.nvidia:
Section "ServerLayout"
    Identifier  "Layout0"
    Option      "AutoAddDevices" "false"
    Option      "AutoAddGPU" "false"

Section "Device"
    Identifier  "DiscreteNvidia"
    Driver      "nvidia"
    VendorName  "NVIDIA Corporation"

#   If the X server does not automatically detect your VGA device,
#   you can manually set it here.
#   To get the BusID prop, run `lspci | egrep 'VGA|3D'` and input the data
#   as you see in the commented example.
#   This Setting may be needed in some platforms with more than one
#   nvidia card, which may confuse the proprietary driver (e.g.,
#   trying to take ownership of the wrong device). Also needed on Ubuntu 13.04.
BusID "PCI:01:00.0"
#   Setting ProbeAllGpus to false prevents the new proprietary driver
#   instance spawned to try to control the integrated graphics card,
#   which is already being managed outside bumblebee.
#   This option doesn't hurt and it is required on platforms running
#   more than one nvidia graphics card with the proprietary driver.
#   (E.g. Macbook Pro pre-2010 with nVidia 9400M + 9600M GT).
#   If this option is not set, the new Xorg may blacken the screen and
#   render it unusable (unless you have some way to run killall Xorg).
    Option "ProbeAllGpus" "false"

    Option "NoLogo" "true"
    Option "UseEDID" "false"
    Option "UseDisplayDevice" "none"

Section "Screen"
    Identifier "Default Screen"
    Device "DiscreteNvidia"

Ответ на: комментарий от amorpher

Теперь такое пише:

[ 1589.431551] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA GPU at PCI:1:0:0.  Please

[ 1589.431587] [ERROR]Aborting because fallback start is disabled.

maxzhykov ()
Ответ на: комментарий от amorpher
# Configuration file for Bumblebee. Values should **not** be put between quotes

## Server options. Any change made in this section will need a server restart
# to take effect.
# The secondary Xorg server DISPLAY number
# Should the unused Xorg server be kept running? Set this to true if waiting
# for X to be ready is too long and don't need power management at all.
# The name of the Bumbleblee server group name (GID name)
# Card power state at exit. Set to false if the card shoud be ON when Bumblebee
# server exits.
# The default behavior of '-f' option on optirun. If set to "true", '-f' will
# be ignored.
# The Driver used by Bumblebee server. If this value is not set (or empty),
# auto-detection is performed. The available drivers are nvidia and nouveau
# (See also the driver-specific sections below)
# Directory with a dummy config file to pass as a -configdir to secondary X

## Client options. Will take effect on the next optirun executed.
# Acceleration/ rendering bridge, possible values are auto, virtualgl and
# primus.
# The method used for VirtualGL to transport frames between X servers.
# Possible values are proxy, jpeg, rgb, xv and yuv.
# List of paths which are searched for the primus when using
# the primus bridge
# Should the program run under optirun even if Bumblebee server or nvidia card
# is not available?

# Driver-specific settings are grouped under [driver-NAME]. The sections are
# parsed if the Driver setting in [bumblebeed] is set to NAME (or if auto-
# detection resolves to NAME).
# PMMethod: method to use for saving power by disabling the nvidia card, valid
# values are: auto - automatically detect which PM method to use
#         bbswitch - new in BB 3, recommended if available
#       switcheroo - vga_switcheroo method, use at your own risk
#             none - disable PM completely

## Section with nvidia driver specific options, only parsed if Driver=nvidia
# Module name to load, defaults to Driver if empty or unset
# colon-separated path to the nvidia libraries
# comma-separated path of the directory containing and the
# default Xorg modules path
## Section with nouveau driver specific options, only parsed if Driver=nouveau

maxzhykov ()
Ответ на: комментарий от maxzhykov

а у тебя есть /usr/lib/nvidia-current?

я только менял у себя это:


заголовки ядра стоят?

# apt-get install linux-headers-generic
# dkms autoinstall -k `uname -r`
# start bumblebeed

amorpher ★★★★★ ()
Ответ на: комментарий от amorpher

насчёт /usr/lib/nvidia-current не знаю. apt-get install linux-headers-generic

Пакет linux-headers-generic недоступен, но упоминается в перечне зависимостей другого пакета.
Это может означать, что пакет отсутствует, устарел, или доступен из источников, не упомянутых в sources.list

maxzhykov ()
Ответ на: комментарий от maxzhykov

вообщем хз, я вот себе давно уже записал и всегда везде работает:


sudo apt-get install nvidia-346 bumblebee bumblebee-nvidia primus mesa-utils

Отредактировать файл настроек bumblebee:
sudo mcedit /etc/bumblebee/bumblebee.conf

В нём изменить:

Перенастроить bbswitch-dkms:
sudo dpkg-reconfigure bbswitch-dkms && sudo dpkg-reconfigure bumblebee
#sudo apt-get install --reinstall bbswitch-dkms && sudo /etc/init.d/bumblebeed restart

Перезагрузиться и проверить:

optirun glxgears

amorpher ★★★★★ ()
Ответ на: комментарий от amorpher

получаем что-то вроде

[ 55.675807] [ERROR]The Bumblebee daemon has not been started yet or the socket path /var/run/bumblebee.socket was incorrect.
[ 55.675837] [ERROR]Could not connect to bumblebee daemon - is it running?

Это все не сложно исправить.

Сначала попробуем переставить переустановить установленую версию

sudo apt-get purge bbswitch-dkms bumblebee-nvidia
sudo apt-get install bbswitch-dkms bumblebee-nvidia

и проводим еще несколько манипуляций

sudo apt-get install linux-headers-generic
sudo dkms autoinstall -k `uname -r`
sudo start bumblebeed

amorpher ★★★★★ ()
Вы не можете добавлять комментарии в эту тему. Тема перемещена в архив.