Bumblebee daemon reported error - Исправление ошибок и поиск оптимальных решений проблем

new update: as I thought, changing just one line in /etc/bumblebee/bumblebee.conf actually worked out: I got everything working perfectly on updated LMDE 201403 (debian jessie based) by just adding some code to KernelDriver line. Before editing, it was like:

KernelDriver=nvidia

I just added -current to it. This is line now:

KernelDriver=nvidia-current

Now works fine with primusrun glxgears and optirun glxgears.
Haven’t checked with anything else, have no time currently. Hope this helped, cheers.

EDIT: Reason why bumblebee fails and «cannot find driver» is because of incorrect paths to nvidia driver libraries. What I do right now to make bumblebee work with any driver version I wish is changing following lines in /etc/bumblebee/bumblebee.conf file:

line 22: Driver=nvidia
line 55: KernelDriver=nvidia-_version_, i.e. nvidia-352
lines 58, 61: these lines contain paths to nvidia libraries and xorg modules. Paths probably start with /usr/lib/nvidia, /usr/lib32/nvidia, or /usr/lib/xorg. You should replace nvidia with nvidia-_version_, i.e. /usr/lib/nvidia-352. Pay attention: each line contains 2 paths, separated by colon or by comma. You should make changes to each path (DO NOT edit path that starts with /usr/lib/xorg).

Note that if you want to use default drivers, _version_ should be current, i.e. line 52: KernelDriver=nvidia-current. I think that bumblebee comes preconfigured to use nvidia-current when package bumblebee-nvidia is installed (sudo apt-get install bumblebee-nvidia).

If done correctly, bumblebee should not report error finding drivers — this worked for me with numerous driver versions.

Источник

Index
» Laptop Issues
» Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

Pages: 1

#1 2015-03-27 11:53:00

AndreasEr: Member; Registered: 2013-12-03; Posts: 17

Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

Hello. I am trying to get bumblebee up and running but there seems to be an issue. This is what i’ve done:

sudo pacman -S bumblebee mesa  xf86-video-intel nvidia lib32-nvidia-utils lib32-mesa-libgl
gpasswd -a $USER bumblebee
sudo systemctl enable bumblebeed
reboot

But when i try to test it out i get the output:

primusrun glxspheres64
primus: fatal: Bumblebee daemon reported: error: [XORG] (EE) systemd-logind: failed to get session: PID 635 does not belong to any known session

So i whent onto the wiki and found this: (and also installed bbswitch)

systemd-logind: failed to get session: PID XXX does not belong to any known session

If the console output is (PID varies):

[ERROR]Cannot access secondary GPU - error: [XORG] (EE) systemd-logind: failed to get session: PID 753 does not belong to any known session
[ERROR]Aborting because fallback start is disabled.

In /etc/mkinitcpio.conf change the MODULES var to:

MODULES="i915 bbswitch"

Or:

MODULES="i915 nouveau bbswitch"

And run:

# mkinitcpio -p linux

mkinitcpio ran fine with no errors. After i rebooted i got promoted with the same error. Can anyone give me a hint on if im missing someting?

lspci
00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b)
00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 0b)
00:04.0 Signal processing controller: Intel Corporation Device 0a03 (rev 0b)
00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04)
00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04)
00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 (rev e4)
00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev e4)
00:1c.4 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 5 (rev e4)
00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04)
00:1f.6 Signal processing controller: Intel Corporation 8 Series Thermal (rev 04)
02:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)
03:00.0 3D controller: NVIDIA Corporation GM108M [GeForce 840M] (rev a2)

pacman -Q | grep linux
archlinux-keyring 20150212-1
lib32-util-linux 2.26-1
libutil-linux 2.26.1-3
linux 3.19.2-1
linux-api-headers 3.18.5-1
linux-firmware 20150206.17657c3-1
linux-git 4.0rc4.r199.gb314aca-1
linux-git-docs 4.0rc4.r199.gb314aca-1
linux-git-headers 4.0rc4.r199.gb314aca-1
linux-headers 3.19.2-1
util-linux 2.26.1-3

#2 2015-03-27 13:04:47

karol: Archivist; Registered: 2009-05-06; Posts: 25,440

Re: Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

You have both linux 3.19 an linux 4 — does this happen when you boot both kernels & kernel images?

#3 2015-03-27 13:20:08

AndreasEr: Member; Registered: 2013-12-03; Posts: 17

Re: Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

karol wrote:

You have both linux 3.19 an linux 4 — does this happen when you boot both kernels & kernel images?

The reason why i have v4 is to get mouse scoll on my laptop to work. As i understand it’s okay to have multiple kernels? I select my kernel in the GRUB menu. Can this add any issues? Am i missing someting?

I can also add that i just tried this solution without any progress.

#4 2015-03-27 13:24:35

dice: Member; From: Germany; Registered: 2014-02-10; Posts: 413

Re: Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

So which kernel are you trying to run bumblebee on?
If you try to run it on v4 you probably need to compile the nvidia modules against this version.
What does

systemctl status bumblebeed

give you right after reboot?

I put at button on it. Yes. I wish to press it, but I’m not sure what will happen if I do. (Gune | Titan A.E.)

#5 2015-03-27 13:26:13

AndreasEr: Member; Registered: 2013-12-03; Posts: 17

Re: Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

dice wrote:

So which kernel are you trying to run bumblebee on?
If you try to run it on v4 you probably need to compile the nvidia modules against this version.
What does
systemctl status bumblebeed
give you right after reboot?

I always use v4 and have been used when i installed the drivers. Anything i need to do?

systemctl status bumblebeed
● bumblebeed.service - Bumblebee C Daemon
   Loaded: loaded (/usr/lib/systemd/system/bumblebeed.service; enabled; vendor preset: disabled)
   Active: active (running) since fre 2015-03-27 14:14:07 CET; 11min ago
 Main PID: 449 (bumblebeed)
   CGroup: /system.slice/bumblebeed.service
           └─449 /usr/bin/bumblebeed

mar 27 14:14:42 laptop bumblebeed[449]: [   64.920660] [WARN][XORG] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
mar 27 14:14:42 laptop bumblebeed[449]: [   64.920669] [ERROR][XORG] (EE) [drm] KMS not enabled
mar 27 14:14:42 laptop bumblebeed[449]: [   64.920673] [ERROR][XORG] (EE) No devices detected.
mar 27 14:14:42 laptop bumblebeed[449]: [   64.920676] [ERROR][XORG] (EE)
mar 27 14:14:42 laptop bumblebeed[449]: [   64.920679] [ERROR][XORG] (EE) no screens found(EE)
mar 27 14:14:42 laptop bumblebeed[449]: [   64.920682] [ERROR][XORG] (EE)
mar 27 14:14:42 laptop bumblebeed[449]: [   64.920686] [ERROR][XORG] (EE) Please also check the log file at "/var/log/Xorg.8.log" for additional information.
mar 27 14:14:42 laptop bumblebeed[449]: [   64.920690] [ERROR][XORG] (EE)
mar 27 14:14:42 laptop bumblebeed[449]: [   64.920693] [ERROR][XORG] (EE) Server terminated with error (1). Closing log file.
mar 27 14:14:42 laptop bumblebeed[449]: [   64.920696] [ERROR]X did not start properly

Sorry, that one was not right after reboot. This one is tho (inside i3wm):

systemctl status bumblebeed
● bumblebeed.service - Bumblebee C Daemon
   Loaded: loaded (/usr/lib/systemd/system/bumblebeed.service; enabled; vendor preset: disabled)
   Active: active (running) since fre 2015-03-27 15:57:08 CET; 1min 15s ago
 Main PID: 453 (bumblebeed)
   CGroup: /system.slice/bumblebeed.service
           └─453 /usr/bin/bumblebeed

mar 27 15:57:08 laptop systemd[1]: Started Bumblebee C Daemon.
mar 27 15:57:08 laptop systemd[1]: Starting Bumblebee C Daemon...
mar 27 15:57:08 laptop bumblebeed[453]: modprobe: FATAL: Module bbswitch not found.
mar 27 15:57:08 laptop bumblebeed[453]: [   33.470972] [ERROR]Module bbswitch could not be loaded (timeout?)
mar 27 15:57:08 laptop bumblebeed[453]: [   33.470986] [WARN]No switching method available. The dedicated card will always be on.
mar 27 15:57:08 laptop bumblebeed[453]: [   33.471866] [INFO]/usr/bin/bumblebeed 3.2.1 started

I ran

And the bbswitch error disapeard but now im back on the first log with xorg errors.
/var/log/Xorg.8.log

[    78.331]
X.Org X Server 1.17.1
Release Date: 2015-02-10
[    78.331] X Protocol Version 11, Revision 0
[    78.331] Build Operating System: Linux 3.18.6-1-ARCH x86_64
[    78.331] Current Operating System: Linux laptop 4.0.0-rc4-gb314aca #1 SMP PREEMPT Fri Mar 20 13:23:44 CET 2015 x86_64
[    78.331] Kernel command line: BOOT_IMAGE=/vmlinuz-linux-git root=/dev/mapper/store-root rw cryptdevice=/dev/sda:enc:header rcutree.rcu_idle_gp_delay=1
[    78.331] Build Date: 14 March 2015  06:45:50PM
[    78.331]
[    78.331] Current version of pixman: 0.32.6
[    78.331]    Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
[    78.331] Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    78.331] (==) Log file: "/var/log/Xorg.8.log", Time: Fri Mar 27 16:11:13 2015
[    78.332] (++) Using config file: "/etc/bumblebee/xorg.conf.nouveau"
[    78.332] (++) Using config directory: "/etc/bumblebee/xorg.conf.d"
[    78.332] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    78.334] (==) ServerLayout "Layout0"
[    78.334] (==) No screen section available. Using defaults.
[    78.334] (**) |-->Screen "Default Screen Section" (0)
[    78.334] (**) |   |-->Monitor "<default monitor>"
[    78.334] (==) No device specified for screen "Default Screen Section".
        Using the first device section listed.
[    78.334] (**) |   |-->Device "DiscreteNvidia" 
[    78.334] (==) No monitor specified for screen "Default Screen Section".
        Using a default monitor configuration.
[    78.334] (**) Option "AutoAddDevices" "false"
[    78.334] (**) Option "AutoAddGPU" "false"1
[    78.334] (**) Not automatically adding devices
[    78.334] (==) Automatically enabling devices
[    78.334] (**) Not automatically adding GPU devices
[    78.334] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/OTF/".
[    78.334]    Entry deleted from font path.
[    78.334]    (Run 'mkfontdir' on "/usr/share/fonts/OTF/").
[    78.334] (==) FontPath set to:
        /usr/share/fonts/misc/,
        /usr/share/fonts/TTF/,
        /usr/share/fonts/Type1/,
        /usr/share/fonts/100dpi/,
        /usr/share/fonts/75dpi/
[    78.334] (==) ModulePath set to "/usr/lib/xorg/modules"
[    78.334] (==) |-->Input Device "<default pointer>"
[    78.334] (==) |-->Input Device "<default keyboard>"
[    78.334] (==) The core pointer device wasn't specified explicitly in the layout.
        Using the default mouse configuration.
[    78.334] (==) The core keyboard device wasn't specified explicitly in the layout.
        Using the default keyboard configuration.
[    78.334] (II) Loader magic: 0x815d80
[    78.334] (II) Module ABI versions:
[    78.334]    X.Org ANSI C Emulation: 0.4
[    78.334]    X.Org Video Driver: 19.0
[    78.334]    X.Org XInput driver : 21.0
[    78.334]    X.Org Server Extension : 9.0
[    78.335] (EE) systemd-logind: failed to get session: PID 927 does not belong to any known session
[    78.335] (II) xfree86: Adding drm device (/dev/dri/card0)
[    78.335] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
[    78.336] (--) PCI:*(0:3:0:0) 10de:1341:1043:167d rev 162, Mem @ 0xf6000000/16777216, 0xe0000000/268435456, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[    78.336] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[    78.336] (II) LoadModule: "glx"
[    78.336] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    78.337] (II) Module glx: vendor="X.Org Foundation"
[    78.337]    compiled for 1.17.1, module version = 1.0.0
[    78.337]    ABI class: X.Org Server Extension, version 9.0
[    78.337] (==) AIGLX enabled
[    78.337] (II) LoadModule: "nouveau"
[    78.337] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
[    78.340] (II) Module nouveau: vendor="X.Org Foundation"
[    78.340]    compiled for 1.17.0, module version = 1.0.11
[    78.340]    Module class: X.Org Video Driver
[    78.340]    ABI class: X.Org Video Driver, version 19.0
[    78.340] (II) LoadModule: "mouse"
[    78.341] (II) Loading /usr/lib/xorg/modules/input/mouse_drv.so
[    78.341] (II) Module mouse: vendor="X.Org Foundation"
[    78.341]    compiled for 1.16.0, module version = 1.9.1
[    78.341]    Module class: X.Org XInput Driver
[    78.341]    ABI class: X.Org XInput driver, version 21.0
[    78.341] (II) LoadModule: "kbd"
[    78.341] (II) Loading /usr/lib/xorg/modules/input/kbd_drv.so
[    78.342] (II) Module kbd: vendor="X.Org Foundation"
[    78.342]    compiled for 1.16.0, module version = 1.8.0
[    78.342]    Module class: X.Org XInput Driver
[    78.342]    ABI class: X.Org XInput driver, version 21.0
[    78.342] (II) NOUVEAU driver
[    78.342] (II) NOUVEAU driver for NVIDIA chipset families :
[    78.342]    RIVA TNT        (NV04)
[    78.342]    RIVA TNT2       (NV05)
[    78.342]    GeForce 256     (NV10)
[    78.342]    GeForce 2       (NV11, NV15)
[    78.342]    GeForce 4MX     (NV17, NV18)
[    78.342]    GeForce 3       (NV20)
[    78.342]    GeForce 4Ti     (NV25, NV28)
[    78.342]    GeForce FX      (NV3x)
[    78.342]    GeForce 6       (NV4x)
[    78.342]    GeForce 7       (G7x)
[    78.342]    GeForce 8       (G8x)
[    78.342]    GeForce GTX 200 (NVA0)
[    78.342]    GeForce GTX 400 (NVC0)
[    78.342] (--) using VT number 1

[    78.342] (EE) [drm] KMS not enabled
[    78.342] (EE) No devices detected.
[    78.342] (EE)
Fatal server error:
[    78.342] (EE) no screens found(EE)
[    78.342] (EE)
Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.
[    78.342] (EE) Please also check the log file at "/var/log/Xorg.8.log" for additional information.
[    78.342] (EE)

Last edited by AndreasEr (2015-03-27 15:15:29)

#6 2015-03-28 05:30:18

AndreasEr: Member; Registered: 2013-12-03; Posts: 17

Re: Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

I decided to try and change to bumblebee-git. Did not work out but gave me another error:

[   99.691916] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied

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

Wiki told me this, But with no success:

This could be worked around by appending following lines in /etc/bumblebee/xorg.conf.nvidia (see here):

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

Everything worked fine on my previous optimus laptop from asus. Is it someting im missing with those «new» GPUs? It’s a Geforce 840m.

Last edited by AndreasEr (2015-03-28 05:32:16)

#7 2015-03-28 08:49:10

dice: Member; From: Germany; Registered: 2014-02-10; Posts: 413

Re: Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

dice wrote:

So which kernel are you trying to run bumblebee on?
If you try to run it on v4 you probably need to compile the nvidia modules against this version.

And also the module for bbswitch.

EDIT: from your Xorg.8.log it seems that you are using bumblebee with nouveau drivers. Therefore changes in the nvidia related configs won’t apply

Last edited by dice (2015-03-28 08:52:55)

I put at button on it. Yes. I wish to press it, but I’m not sure what will happen if I do. (Gune | Titan A.E.)

#8 2015-03-28 17:04:25

AndreasEr: Member; Registered: 2013-12-03; Posts: 17

Re: Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

dice wrote:

dice wrote:

So which kernel are you trying to run bumblebee on?
If you try to run it on v4 you probably need to compile the nvidia modules against this version.

And also the module for bbswitch.

EDIT: from your Xorg.8.log it seems that you are using bumblebee with nouveau drivers. Therefore changes in the nvidia related configs won’t apply

Hi again dice, I made a fresh install of arch and i have bumblebee up and running now. No issues. Currently im running the 3.19.2-1 kernel but i do have to install v4 to get my mousepad working on my laptop. Could you possible give me a short step by step guide of how i can make it work with the new kernel? How do i compile things against a newer kernel?

#9 2015-06-27 16:51:09

rajat: Member; Registered: 2013-10-10; Posts: 10

Re: Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

I get this error
primus: fatal: Bumblebee daemon reported: error: [XORG] (EE) systemd-logind: failed to get session: PID 6333 does not belong to any known session

However after I attempt a second time it works fine. I have been testing bumblebee across many Distributions, Ubuntu, OpenSuse 13.2/Tumbleweed, Fedora22, Elementary OS. etc.. It is a common issue. So I think it is not specific to a Kernel, it more looks like a bug of some sort, Maybe with bumblebee or not. I have tested this on my Lenovo Laptop Z70-50 . My hardware Specs are as below.

lshw -C Display
WARNING: you should run this program as super-user.
*-display
description: VGA compatible controller
product: Haswell-ULT Integrated Graphics Controller
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
version: 0b
width: 64 bits
clock: 33MHz
capabilities: vga_controller bus_master cap_list rom
configuration: driver=i915 latency=0
resources: irq:45 memory:c3000000-c33fffff memory:d0000000-dfffffff ioport:5000(size=64)
*-display
description: 3D controller
product: GF117M [GeForce 610M/710M/820M / GT 620M/625M/630M/720M]
vendor: NVIDIA Corporation
physical id: 0
bus info: pci@0000:03:00.0
version: a1
width: 64 bits
clock: 33MHz
capabilities: bus_master cap_list
configuration: driver=nvidia latency=0
resources: irq:51 memory:c2000000-c2ffffff memory:b0000000-bfffffff memory:c0000000-c1ffffff ioport:3000(size=128)

I think I should now file a bug report for this issue.

Do you also see similar behaviour ? Please let me know so that I could log a bug for this as it would then be established that it works fine after a second or 3rd attempt.?

Linux is easy.. People are Difficult

#10 2015-08-15 08:44:49

starthis: Member; Registered: 2004-12-25; Posts: 46

Re: Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

I had the same error message trying to use primusrun / optirun :

primus: fatal: Bumblebee daemon reported: error: [XORG] (EE) systemd-logind: failed to get session: PID xxxx does not belong to any known session

It used to work fine a couple of kernel versions ago, when I initially setup bumblebeed I applied most hints from the bumblebee wiki page.

I discovered for me bumblebee started working again if I reloaded the bbswitch module (rmmod bbswitch & modprobe bbswitch)
One of the hints from the wiki page was to add bbswitch module to /etc/mkinitcpio.conf for early loading, but once I REMOVED the module from etc/mkinitcpio.conf again, everything works again as expected.

I suppose loading the bbswitch module early, causes it to be loaded in a wrong (no) session context somehow.

I don’t know if this will help solve your issue, but I thought I’d leave it here for reference.

Источник

Fresh 13.10 install + default upgrade
sudo apt-get install bumblebee bumblebee-nvidia primus linux-headers-generic

Currently:

lspci -vnn | grep »'[030[02]]’

00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core Processor Integrated Graphics  
Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller])                                             1 right up                                                                                           

01:00.0 3D controller [0302]: NVIDIA Corporation GK208M [GeForce GT 740M] [10de:1292] (rev ff) (prog-if ff)

optirun -vv ff

[...]
[  753.781611] [INFO]Response: No - error: Could not load GPU driver                                    

[  753.781625] [ERROR]Cannot access secondary GPU - error: Could not load GPU driver 
[...]

I already checked that the BusID matches in /etc/bumblebee/xorg.conf.nvidia and I tried with a different set up by setting the Driver=nvidia and KernelDriver=nvidia in /etc/bumblebee/bumblebee.conf, same situation.

uname -a

Linux mene 3.11.0-14-generic #21-Ubuntu SMP Tue Nov 12 17:04:55 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

sudo dmidecode | grep «System Information» -A 3

System Information                                                                                      
        Manufacturer: LENOVO                                                                            
        Product Name: 20250                                                                             
        Version: Lenovo Z710

Источник

Reported by: Vincas Dargis <vindrg@gmail.com>

Date: Mon, 29 Jun 2020 17:03:07 UTC

Severity: important

Tags: moreinfo, unreproducible

Found in versions bumblebee/3.2.1-23, bumblebee/3.2.1-26~bpo10+1

Reply or subscribe to this bug.

Toggle useless messages

Report forwarded
to debian-bugs-dist@lists.debian.org, vindrg@gmail.com, Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth.debian.org>:
Bug#963980; Package bumblebee-nvidia.
(Mon, 29 Jun 2020 17:03:09 GMT) (full text, mbox, link).

Acknowledgement sent
to Vincas Dargis <vindrg@gmail.com>:
New Bug report received and forwarded. Copy sent to vindrg@gmail.com, Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth.debian.org>.
(Mon, 29 Jun 2020 17:03:09 GMT) (full text, mbox, link).

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

Package: bumblebee-nvidia
Version: 3.2.1-23
Severity: important

Dear Maintainer,

After some updates I cannot use primusrun/optirun/pvkrun on my Sid:

```
$ primusrun glxgears
primus: fatal: Bumblebee daemon reported: error: [XORG] (EE) Unable to
locate/open config directory: "/etc/bumblebee/xorg.conf.d"
```

```
$ optirun glxgears
[  444.023511] [ERROR]Cannot access secondary GPU - error: [XORG] (EE)
Unable to locate/open config directory: "/etc/bumblebee/xorg.conf.d"

[  444.023570] [ERROR]Aborting because fallback start is disabled.
```

```
$ pvkrun vkcube
primus: fatal: Bumblebee daemon reported: error: [XORG] (EE) Unable to
locate/open config directory: "/etc/bumblebee/xorg.conf.d"
<hangs>
```

journalctl shows this:

```
$ sudo journalctl -f -u bumblebeed -n0
-- Logs begin at Mon 2020-06-29 19:49:28 EEST. --
birž. 29 19:57:47 vinco bumblebeed[12788]: [  504.277010] [ERROR][XORG] (EE) Unable to locate/open config directory: "/etc/bumblebee/xorg.conf.d"
birž. 29 19:57:47 vinco bumblebeed[12788]: [  504.277034] [WARN][XORG] (WW) Warning, couldn't open module mouse
birž. 29 19:57:47 vinco bumblebeed[12788]: [  504.277039] [ERROR][XORG] (EE) Failed to load module "mouse" (module does not exist, 0)
birž. 29 19:57:47 vinco bumblebeed[12788]: [  504.277045] [ERROR][XORG] (EE) NOUVEAU(0): [drm] failed to set drm interface version.
birž. 29 19:57:47 vinco bumblebeed[12788]: [  504.277048] [ERROR][XORG] (EE) NOUVEAU(0): [drm] error opening the drm
birž. 29 19:57:47 vinco bumblebeed[12788]: [  504.277051] [ERROR][XORG] (EE) NOUVEAU(0): 910:
birž. 29 19:57:47 vinco bumblebeed[12788]: [  504.277054] [ERROR][XORG] (EE) Screen(s) found, but none have a usable configuration.
birž. 29 19:57:47 vinco bumblebeed[12788]: [  504.277057] [ERROR][XORG] (EE)
birž. 29 19:57:47 vinco bumblebeed[12788]: [  504.277060] [ERROR][XORG] (EE) no screens found(EE)
birž. 29 19:57:47 vinco bumblebeed[12788]: [  504.277062] [ERROR][XORG] (EE)
birž. 29 19:57:47 vinco bumblebeed[12788]: [  504.277068] [ERROR][XORG] (EE) Please also check the log file at "/var/log/Xorg.8.log" for additional information.
birž. 29 19:57:47 vinco bumblebeed[12788]: [  504.277073] [ERROR][XORG] (EE)
birž. 29 19:57:47 vinco bumblebeed[12788]: [  504.277077] [ERROR][XORG] (EE) Server terminated with error (1). Closing log file.
birž. 29 19:57:47 vinco bumblebeed[12788]: [  504.277728] [ERROR]X did not start properly
```


-- Package-specific info:
OpenGL and NVIDIA library files installed:
lrwxrwxrwx 1 root root 25 Jun 29 19:44 /etc/alternatives/glx -> /usr/lib/nvidia/bumblebee
lrwxrwxrwx 1 root root 49 Jan 29 18:26 /etc/alternatives/glx--libEGL.so-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libEGL.so
lrwxrwxrwx 1 root root 51 Jun 29 19:44 /etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libEGL.so.1
lrwxrwxrwx 1 root root 48 Jan 29 18:26 /etc/alternatives/glx--libGL.so-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so
lrwxrwxrwx 1 root root 48 Jun 29 19:44 /etc/alternatives/glx--libGL.so.1-i386-linux-gnu -> /usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root 50 Jun 29 19:44 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root 55 Jan 29 18:26 /etc/alternatives/glx--libGLESv1_CM.so-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so
lrwxrwxrwx 1 root root 55 Jun 29 19:44 /etc/alternatives/glx--libGLESv1_CM.so.1-i386-linux-gnu -> /usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1
lrwxrwxrwx 1 root root 57 Jun 29 19:44 /etc/alternatives/glx--libGLESv1_CM.so.1-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so.1
lrwxrwxrwx 1 root root 52 Jan 29 18:26 /etc/alternatives/glx--libGLESv2.so-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so
lrwxrwxrwx 1 root root 52 Jun 29 19:44 /etc/alternatives/glx--libGLESv2.so.2-i386-linux-gnu -> /usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2
lrwxrwxrwx 1 root root 54 Jun 29 19:44 /etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2
lrwxrwxrwx 1 root root 40 Jun 29 19:44 /etc/alternatives/glx--libGLX_indirect.so.0-i386-linux-gnu -> /usr/lib/i386-linux-gnu/libGLX_mesa.so.0
lrwxrwxrwx 1 root root 42 Jun 29 19:44 /etc/alternatives/glx--libGLX_indirect.so.0-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
lrwxrwxrwx 1 root root 25 Jun 29 19:44 /etc/alternatives/nvidia -> /usr/lib/nvidia/tesla-418
lrwxrwxrwx 1 root root 53 Jun 29 19:44 /etc/alternatives/nvidia--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/tesla-418/libGL.so.1

/etc/modprobe.d:
total 52
drwxr-xr-x   2 root root  4096 Jun 29 19:54 .
drwxr-xr-x 169 root root 12288 Jun 29 19:54 ..
-rw-r--r--   1 root root   113 Feb 23 12:19 alsa-base.conf
-rw-r--r--   1 root root   154 Dec 15  2018 amd64-microcode-blacklist.conf
-rw-r--r--   1 root root    31 Dec 18  2017 ath9k_htc.conf
-rw-r--r--   1 root root   543 Jun 29 19:54 bumblebee.conf
-rw-r--r--   1 root root    88 Oct 22  2017 custom-blacklist.conf
-rw-r--r--   1 root root   127 Oct 25  2016 dkms.conf
-rw-r--r--   1 root root   154 Jul  9  2017 intel-microcode-blacklist.conf
-rw-r--r--   1 root root   260 Jan 27  2019 nvidia-kernel-common.conf
-rw-r--r--   1 root root    20 Oct  7  2017 qemu-blacklist.conf

/etc/modprobe.d/bumblebee.conf:# do not automatically load nouveau as it may prevent nvidia from loading
/etc/modprobe.d/bumblebee.conf:# do not automatically load nvidia as it's unloaded anyway when bumblebeed
/etc/modprobe.d/bumblebee.conf:blacklist nvidia
/etc/modprobe.d/bumblebee.conf:blacklist nvidia-current
/etc/modprobe.d/bumblebee.conf:blacklist nvidia-tesla-440
/etc/modprobe.d/bumblebee.conf:blacklist nvidia-tesla-418
/etc/modprobe.d/bumblebee.conf:blacklist nvidia-legacy-390xx
/etc/modprobe.d/bumblebee.conf:blacklist nvidia-legacy-340xx
/etc/modprobe.d/nvidia-kernel-common.conf:alias char-major-195* nvidia
/etc/modprobe.d/nvidia-kernel-common.conf:#options nvidia NVreg_DeviceFileUID=0 NVreg_DeviceFileGID=44 NVreg_DeviceFileMode=0660
/etc/modprobe.d/nvidia-kernel-common.conf:# options nvidia NVreg_EnableAGPSBA=1
/etc/modprobe.d/nvidia-kernel-common.conf:# options nvidia NVreg_EnableAGPFW=1
/etc/modprobe.d/bumblebee.conf:# do not automatically load nouveau as it may prevent nvidia from loading
/etc/modprobe.d/bumblebee.conf:blacklist nouveau


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.7.0-1-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=lt_LT.UTF-8, LC_CTYPE=lt_LT.UTF-8 (charmap=UTF-8), LANGUAGE=lt (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages bumblebee-nvidia depends on:
ii  bumblebee                                       3.2.1-23
ii  glx-alternative-nvidia                          1.1.0
ii  nvidia-legacy-390xx-driver [nvidia-driver-any]  390.138-1
ii  nvidia-legacy-390xx-kernel-dkms                 390.138-1

Versions of packages bumblebee-nvidia recommends:
ii  nvidia-primus-vk-wrapper  1.5-1

bumblebee-nvidia suggests no packages.

Versions of packages bumblebee-nvidia is related to:
ii  nvidia-legacy-390xx-driver [nvidia-driver-any]                390.138-1
ii  nvidia-legacy-390xx-driver-libs-nonglvnd [nvidia-driver-libs  390.138-1
ii  primus-libs                                                   0~20150328-11
ii  xserver-xorg-video-nvidia-legacy-390xx [xserver-xorg-video-n  390.138-1

-- no debconf information

Information forwarded
to debian-bugs-dist@lists.debian.org, Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth.debian.org>:
Bug#963980; Package bumblebee-nvidia.
(Mon, 29 Jun 2020 17:21:04 GMT) (full text, mbox, link).

Acknowledgement sent
to Vincas Dargis <vindrg@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth.debian.org>.
(Mon, 29 Jun 2020 17:21:04 GMT) (full text, mbox, link).

Message #10 received at 963980@bugs.debian.org (full text, mbox, reply):

/etc/bumblebee/xorg.conf.d directory is empty :/

Message #15 received at 963980@bugs.debian.org (full text, mbox, reply):

In bumblebee changelog I see:

  * Simplify rules and use bumblebee.install etc. for installation.
  * Remove obsolete conffile /etc/bumblebee/xorg.conf.d/10-dummy.conf.

Could these introduce some sort of regression in my case?

Information forwarded
to debian-bugs-dist@lists.debian.org, Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth.debian.org>:
Bug#963980; Package bumblebee-nvidia.
(Tue, 30 Jun 2020 16:27:04 GMT) (full text, mbox, link).

Acknowledgement sent
to Vincas Dargis <vindrg@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth.debian.org>.
(Tue, 30 Jun 2020 16:27:04 GMT) (full text, mbox, link).

Message #20 received at 963980@bugs.debian.org (full text, mbox, reply):

$ sudo strace -efile -f -p $(pgrep bumblebeed) 2>&1 | fgrep /etc/bumblebee
[pid  7068] execve("/usr/lib/xorg/Xorg", ["/usr/lib/xorg/Xorg", ":8", "-config", 
"/etc/bumblebee/xorg.conf.nouveau", "-configdir", "/etc/bumblebee/xorg.conf.d", "-sharevts", 
"-nolisten", "tcp", "-noreset", "-verbose", "3", "-isolateDevice", "PCI:01:00:0"], 0x7fff6ca8f198 /* 
4 vars */ <unfinished ...>
[pid  7068] openat(AT_FDCWD, "/etc/bumblebee/xorg.conf.d", 
O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = 16
[pid  7068] openat(AT_FDCWD, "/etc/bumblebee/xorg.conf.nouveau", O_RDONLY) = 16

Information forwarded
to debian-bugs-dist@lists.debian.org, Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth.debian.org>:
Bug#963980; Package bumblebee-nvidia.
(Wed, 01 Jul 2020 18:18:02 GMT) (full text, mbox, link).

Acknowledgement sent
to Vincas Dargis <vindrg@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth.debian.org>.
(Wed, 01 Jul 2020 18:18:02 GMT) (full text, mbox, link).

Message #25 received at 963980@bugs.debian.org (full text, mbox, reply):

I just this:

sudo apt purge --autoremove nvidia*
sudo apt install nvidia-driver bumblebee-nvidia primus-nvidia primus-vk-nvidia

And after reinstalling driver and all other bumbleblee-related packages, it started to work again.

Information forwarded
to debian-bugs-dist@lists.debian.org, Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth.debian.org>:
Bug#963980; Package bumblebee-nvidia.
(Wed, 01 Jul 2020 19:36:06 GMT) (full text, mbox, link).

Acknowledgement sent
to Andreas Beckmann <anbe@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth.debian.org>.
(Wed, 01 Jul 2020 19:36:06 GMT) (full text, mbox, link).

Message #30 received at 963980@bugs.debian.org (full text, mbox, reply):

Control: tag -1 moreinfo unreproducible

On 7/1/20 8:15 PM, Vincas Dargis wrote:
> And after reinstalling driver and all other bumbleblee-related packages, 
> it started to work again.

Thanks for this "solution". You probably can't tell what changed (likely 
in /etc) after purge+reinstall?
Anyway, I'll keep this bug open as unreproducible in case someone else 
stumbles upon it ...

Andreas

Added tag(s) moreinfo and unreproducible.
Request was from Andreas Beckmann <anbe@debian.org>
to 963980-submit@bugs.debian.org.
(Wed, 01 Jul 2020 19:36:06 GMT) (full text, mbox, link).

Information forwarded
to debian-bugs-dist@lists.debian.org, Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth.debian.org>:
Bug#963980; Package bumblebee-nvidia.
(Thu, 02 Jul 2020 16:06:02 GMT) (full text, mbox, link).

Acknowledgement sent
to Vincas Dargis <vindrg@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth.debian.org>.
(Thu, 02 Jul 2020 16:06:02 GMT) (full text, mbox, link).

Message #37 received at 963980@bugs.debian.org (full text, mbox, reply):

> Thanks for this "solution". You probably can't tell what changed (likely 
> in /etc) after purge+reinstall?

Sadly, no. I could have taken copy if /etc, just haven't thought of it, sorry.

All I see is that `/etc/bumblebee/xorg.conf.d/` is still empty as it where, can't comment any more.

Information forwarded
to debian-bugs-dist@lists.debian.org, Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth.debian.org>:
Bug#963980; Package bumblebee-nvidia.
(Wed, 02 Sep 2020 17:03:02 GMT) (full text, mbox, link).

Acknowledgement sent
to Vincas Dargis <vindrg@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth.debian.org>.
(Wed, 02 Sep 2020 17:03:02 GMT) (full text, mbox, link).

Message #42 received at 963980@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

OK so it looks like after 2020-09-01 updates that had lot's of NVIDIA stuff, same error reproduces again:

```
$ pvkrun vkcube
primus: fatal: Bumblebee daemon reported: error: [XORG] (EE) Unable to locate/open config directory: 
"/etc/bumblebee/xorg.conf.d"
```

```
$ optirun glxgears
[ 5856.436157] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) Unable to locate/open config directory: 
"/etc/bumblebee/xorg.conf.d"

[ 5856.436198] [ERROR]Aborting because fallback start is disabled.
```


```
$ primusrun glxgears
primus: fatal: Bumblebee daemon reported: error: [XORG] (EE) Unable to locate/open config directory: 
"/etc/bumblebee/xorg.conf.d
```

optirun/primusrun/pvkrun does not work. glxgears does run with integrated graphics, but not with NVIDIA.

Attached /etc/bumblebee directory contents.

Here's what /var/log/apt/history.log tells:

Start-Date: 2020-09-01  18:26:20
Commandline: apt full-upgrade
Requested-By: vincas (1000)
Upgrade: libmpc3:amd64 (1.2.0~rc1-1, 1.2.0-1), libnvidia-glvkspirv:amd64 (450.57-3, 450.66-1), libnvidia-glvkspirv:i386 
(450.57-3, 450.66-1), libstdc++-10-dev:amd64 (10.2.0-5, 10.2.0-6), liblouisutdml-data:amd64 (2.8.0-4, 2.9.0-1), 
libwayland-egl1:amd64 (1.18.0-2~exp1, 1.18.0-2~exp1.1), libwayland-egl1:i386 (1.18.0-2~exp1, 1.18.0-2~exp1.1), 
mesa-opencl-icd:amd64 (20.1.5-1, 20.1.6-1), libgles-nvidia1:amd64 (450.57-3, 450.66-1), libgles-nvidia1:i386 (450.57-3, 
450.66-1), libgles-nvidia2:amd64 (450.57-3, 450.66-1), libgles-nvidia2:i386 (450.57-3, 450.66-1), xserver-common:amd64 
(2:1.20.8-2, 2:1.20.9-1), g++-10:amd64 (10.2.0-5, 10.2.0-6), libnvidia-ml1:amd64 (450.57-3, 450.66-1), 
nvidia-vulkan-icd:amd64 (450.57-3, 450.66-1), nvidia-vulkan-icd:i386 (450.57-3, 450.66-1), xserver-xorg-core:amd64 
(2:1.20.8-2, 2:1.20.9-1), nvidia-egl-icd:amd64 (450.57-3, 450.66-1), nvidia-egl-icd:i386 (450.57-3, 450.66-1), 
libegl-mesa0:amd64 (20.1.5-1, 20.1.6-1), libegl-mesa0:i386 (20.1.5-1, 20.1.6-1), lib32stdc++6:amd64 (10.2.0-5, 
10.2.0-6), libaprutil1:amd64 (1.6.1-4+b1, 1.6.1-5), gcc-10-base:amd64 (10.2.0-5, 10.2.0-6), gcc-10-base:i386 (10.2.0-5, 
10.2.0-6), electrum:amd64 (4.0.2-1, 4.0.2-2), libobjc4:amd64 (10.2.0-5, 10.2.0-6), nvidia-driver:amd64 (450.57-3, 
450.66-1), libglapi-mesa:amd64 (20.1.5-1, 20.1.6-1), libglapi-mesa:i386 (20.1.5-1, 20.1.6-1), mesa-common-dev:amd64 
(20.1.5-1, 20.1.6-1), lib32gcc-s1:amd64 (10.2.0-5, 10.2.0-6), mesa-vulkan-drivers-dbgsym:amd64 (20.1.5-1, 20.1.6-1), 
liblouis20:amd64 (3.14.0-1, 3.15.0-1), libitm1:amd64 (10.2.0-5, 10.2.0-6), nvidia-vulkan-common:amd64 (450.57-3, 
450.66-1), xserver-xorg-legacy:amd64 (2:1.20.8-2, 2:1.20.9-1), libxatracker2:amd64 (20.1.5-1, 20.1.6-1), 
python3-louis:amd64 (3.14.0-1, 3.15.0-1), nvidia-vdpau-driver:amd64 (450.57-3, 450.66-1), libgl1-nvidia-glvnd-glx:amd64 
(450.57-3, 450.66-1), libgl1-nvidia-glvnd-glx:i386 (450.57-3, 450.66-1), libegl1-mesa:amd64 (20.1.5-1, 20.1.6-1), 
cmake-data:amd64 (3.16.3-3, 3.18.2-1), libasan6:amd64 (10.2.0-5, 10.2.0-6), libglx-nvidia0:amd64 (450.57-3, 450.66-1), 
libglx-nvidia0:i386 (450.57-3, 450.66-1), libquadmath0:amd64 (10.2.0-5, 10.2.0-6), orca:amd64 (3.36.5-1, 3.36.6-1), 
rsyslog:amd64 (8.2006.0-2, 8.2008.0-1), nvidia-kernel-dkms:amd64 (450.57-3, 450.66-1), libgbm1:amd64 (20.1.5-1, 
20.1.6-1), libgbm1:i386 (20.1.5-1, 20.1.6-1), libegl-nvidia0:amd64 (450.57-3, 450.66-1), libegl-nvidia0:i386 (450.57-3, 
450.66-1), libwayland-client0:amd64 (1.18.0-2~exp1, 1.18.0-2~exp1.1), libwayland-client0:i386 (1.18.0-2~exp1, 
1.18.0-2~exp1.1), nvidia-egl-common:amd64 (450.57-3, 450.66-1), libapr1:amd64 (1.7.0-1, 1.7.0-3), libgcc-10-dev:amd64 
(10.2.0-5, 10.2.0-6), libllvm10:amd64 (1:10.0.1-4, 1:10.0.1-5), libllvm10:i386 (1:10.0.1-4, 1:10.0.1-5), 
libnvidia-cfg1:amd64 (450.57-3, 450.66-1), libtsan0:amd64 (10.2.0-5, 10.2.0-6), nvidia-legacy-check:amd64 (450.57-3, 
450.66-1), libubsan1:amd64 (10.2.0-5, 10.2.0-6), aspell-de-1901:amd64 (1:2-35, 1:2-36), liblouisutdml9:amd64 (2.8.0-4, 
2.9.0-1), libgfortran5:amd64 (10.2.0-5, 10.2.0-6), kinfocenter:amd64 (4:5.17.5-2, 4:5.17.5-3), 
nvidia-kernel-support:amd64 (450.57-3, 450.66-1), liblsan0:amd64 (10.2.0-5, 10.2.0-6), libgomp1:amd64 (10.2.0-5, 
10.2.0-6), libgomp1:i386 (10.2.0-5, 10.2.0-6), nvidia-driver-libs:amd64 (450.57-3, 450.66-1), nvidia-driver-libs:i386 
(450.57-3, 450.66-1), nvidia-driver-bin:amd64 (450.57-3, 450.66-1), libgl1-mesa-dev:amd64 (20.1.5-1, 20.1.6-1), 
libgl1-mesa-dri:amd64 (20.1.5-1, 20.1.6-1), libgl1-mesa-dri:i386 (20.1.5-1, 20.1.6-1), liblouisutdml-bin:amd64 (2.8.0-4, 
2.9.0-1), libosmesa6:amd64 (20.1.5-1, 20.1.6-1), libosmesa6:i386 (20.1.5-1, 20.1.6-1), libtss2-esys0:amd64 (2.4.1-1+b1, 
3.0.0-1), libgcc-s1:amd64 (10.2.0-5, 10.2.0-6), libgcc-s1:i386 (10.2.0-5, 10.2.0-6), libgl1-mesa-glx:amd64 (20.1.5-1, 
20.1.6-1), libgl1-mesa-glx:i386 (20.1.5-1, 20.1.6-1), xserver-xorg-video-nvidia:amd64 (450.57-3, 450.66-1), cmake:amd64 
(3.16.3-3, 3.18.2-1), libclang-common-10-dev:amd64 (1:10.0.1-4, 1:10.0.1-5), liblouis-data:amd64 (3.14.0-1, 3.15.0-1), 
python3-electrum:amd64 (4.0.2-1, 4.0.2-2), libnvidia-rtcore:amd64 (450.57-3, 450.66-1), cpp-10:amd64 (10.2.0-5, 
10.2.0-6), mesa-vdpau-drivers:amd64 (20.1.5-1, 20.1.6-1), mesa-vdpau-drivers:i386 (20.1.5-1, 20.1.6-1), 
mesa-vulkan-drivers:amd64 (20.1.5-1, 20.1.6-1), mesa-vulkan-drivers:i386 (20.1.5-1, 20.1.6-1), libatomic1:amd64 
(10.2.0-5, 10.2.0-6), libatomic1:i386 (10.2.0-5, 10.2.0-6), libcc1-0:amd64 (10.2.0-5, 10.2.0-6), libstdc++6:amd64 
(10.2.0-5, 10.2.0-6), libstdc++6:i386 (10.2.0-5, 10.2.0-6), libnvidia-cbl:amd64 (450.57-3, 450.66-1), 
libhtml-parser-perl:amd64 (3.73-1, 3.75-1), libnvidia-glcore:amd64 (450.57-3, 450.66-1), libnvidia-glcore:i386 
(450.57-3, 450.66-1), libwayland-server0:amd64 (1.18.0-2~exp1, 1.18.0-2~exp1.1), libwayland-server0:i386 (1.18.0-2~exp1, 
1.18.0-2~exp1.1), gcc-10:amd64 (10.2.0-5, 10.2.0-6), libnvidia-eglcore:amd64 (450.57-3, 450.66-1), 
libnvidia-eglcore:i386 (450.57-3, 450.66-1), mesa-va-drivers:amd64 (20.1.5-1, 20.1.6-1), mesa-va-drivers:i386 (20.1.5-1, 
20.1.6-1), libglx-mesa0:amd64 (20.1.5-1, 20.1.6-1), libglx-mesa0:i386 (20.1.5-1, 20.1.6-1), nvidia-alternative:amd64 
(450.57-3, 450.66-1), libwayland-cursor0:amd64 (1.18.0-2~exp1, 1.18.0-2~exp1.1), libwayland-cursor0:i386 (1.18.0-2~exp1, 
1.18.0-2~exp1.1)
End-Date: 2020-09-01  18:28:17

[etc.bumblebee.tar.gz (application/gzip, attachment)]

Information forwarded
to debian-bugs-dist@lists.debian.org, Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth.debian.org>:
Bug#963980; Package bumblebee-nvidia.
(Wed, 02 Sep 2020 17:30:03 GMT) (full text, mbox, link).

Acknowledgement sent
to Vincas Dargis <vindrg@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth.debian.org>.
(Wed, 02 Sep 2020 17:30:03 GMT) (full text, mbox, link).

Message #47 received at 963980@bugs.debian.org (full text, mbox, reply):

Sadly, purge & reinstall did not help this time...

Information forwarded
to debian-bugs-dist@lists.debian.org, Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth.debian.org>:
Bug#963980; Package bumblebee-nvidia.
(Fri, 04 Sep 2020 16:15:05 GMT) (full text, mbox, link).

Acknowledgement sent
to Vincas Dargis <vindrg@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth.debian.org>.
(Fri, 04 Sep 2020 16:15:05 GMT) (full text, mbox, link).

Message #52 received at 963980@bugs.debian.org (full text, mbox, reply):

from `/var/log/Xorg.8.log`

[  2486.434] (II) NVIDIA dlloader X Driver  450.66  Wed Aug 12 19:44:12 UTC 2020
[  2486.434] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[  2486.435] (EE) No devices detected.
[  2486.435] (EE)
Fatal server error:
[  2486.435] (EE) no screens found(EE)
[  2486.435] (EE)

So maybe this latest 450.66 simply does not support my `GM107M [GeForce GTX 860M]`, or just because of some bug?

Information forwarded
to debian-bugs-dist@lists.debian.org, Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth.debian.org>:
Bug#963980; Package bumblebee-nvidia.
(Fri, 04 Sep 2020 16:33:02 GMT) (full text, mbox, link).

Acknowledgement sent
to Vincas Dargis <vindrg@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth.debian.org>.
(Fri, 04 Sep 2020 16:33:02 GMT) (full text, mbox, link).

Message #57 received at 963980@bugs.debian.org (full text, mbox, reply):

In https://wiki.debian.org/Bumblebee#Debian_10_and_older I've found this hint:

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

You may have to set the BusID manually, in /etc/bumblebee/xorg.conf.nvidia. To get the BusID, run lspci | egrep 'VGA|3D' 
in a terminal. Refer to the comments in that file for further instructions.
```

So I've edited `/etc/bumblebee/xorg.conf.nvidia` and uncommented one line so it's now:

```
BusID "PCI:01:00:0"
```

And it works!

`lspci | egrep 'VGA|3D'` on my machine returns:

```
00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06)
01:00.0 3D controller: NVIDIA Corporation GM107M [GeForce GTX 860M] (rev ff)
```

So some part fails to detect that only NVIDIA card..? :)

Information forwarded
to debian-bugs-dist@lists.debian.org, Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth.debian.org>:
Bug#963980; Package bumblebee-nvidia.
(Sat, 05 Sep 2020 10:15:02 GMT) (full text, mbox, link).

Acknowledgement sent
to Felix Dörre <debian@felixdoerre.de>:
Extra info received and forwarded to list. Copy sent to Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth.debian.org>.
(Sat, 05 Sep 2020 10:15:02 GMT) (full text, mbox, link).

Message #62 received at 963980@bugs.debian.org (full text, mbox, reply):

I've just upgraded from nvidia 450.57-2 to 450.66-1 and observe exactly 
the same problem. In parallel, I also upgraded bumblebee from 3.2.1-25 
to 3.2.1-26. And x-server from 2:1.20.8-2 to 2:1.20.9-1. Also my nvidia 
card (NVIDIA Corporation GM206GLM [Quadro M2200 Mobile]) is now not 
detected automatically anymore. Adding it manually in the config also 
solves this problem for me.

I've experimented a bit with the involved packages and observed this:
- downgrade the nvidia-driver: still no auto-detect
- downgrade bumblebee: still no auto-detect
- downgrade the xserver: auto-detect works again
- upgrade nvidia-driver and bumblebee: auto-detect still works!
- upgrade xserver: auto-detect broken again

So I believe one can workaround this problem as well by doing:
apt install --only-upgrade xserver-common=2:1.20.8-2 
xserver-xorg-legacy=2:1.20.8-2 xserver-xorg-core=2:1.20.8-2 
xserver-xephyr=2:1.20.8-2 xwayland=2:1.20.8-2

Maybe this information helps someone to figure out what is wrong.

-- 
Kind regards,
Felix Dörre

Information forwarded
to debian-bugs-dist@lists.debian.org, Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth.debian.org>:
Bug#963980; Package bumblebee-nvidia.
(Thu, 24 Sep 2020 21:54:03 GMT) (full text, mbox, link).

Acknowledgement sent
to Andreas Beckmann <anbe@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth.debian.org>.
(Thu, 24 Sep 2020 21:54:03 GMT) (full text, mbox, link).

Message #67 received at 963980@bugs.debian.org (full text, mbox, reply):

On 9/5/20 11:43 AM, Felix Dörre wrote:
> I've just upgraded from nvidia 450.57-2 to 450.66-1 and observe exactly
> the same problem. In parallel, I also upgraded bumblebee from 3.2.1-25
> to 3.2.1-26. And x-server from 2:1.20.8-2 to 2:1.20.9-1. Also my nvidia
...
> - upgrade xserver: auto-detect broken again
...
> Maybe this information helps someone to figure out what is wrong.

please try xserver-xorg-core 2:1.20.9-2 first and file a bug against it
if the issue persists.

Andreas

Information forwarded
to debian-bugs-dist@lists.debian.org, Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth.debian.org>:
Bug#963980; Package bumblebee-nvidia.
(Fri, 25 Sep 2020 06:39:04 GMT) (full text, mbox, link).

Acknowledgement sent
to Felix Dörre <debian@felixdoerre.de>:
Extra info received and forwarded to list. Copy sent to Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth.debian.org>.
(Fri, 25 Sep 2020 06:39:04 GMT) (full text, mbox, link).

Message #72 received at 963980@bugs.debian.org (full text, mbox, reply):

On 2020-09-24 23:44, Andreas Beckmann wrote:
> please try xserver-xorg-core 2:1.20.9-2 first and file a bug against it
> if the issue persists.

I've just upgraded to 2:1.20.9-2 and this seems to solve the problem for 
me. So it seems one of these: 
https://salsa.debian.org/xorg-team/xserver/xorg-server/-/commit/9c140c1c65aa05bd2e1b50cc8d6c8c4b9a1c1d9e 
has solved this bug for me (which does not seem that unplausible).

-- 
Kind regards,
Felix Dörre

Information forwarded
to debian-bugs-dist@lists.debian.org, debian@seb.lautre.net, Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth.debian.org>:
Bug#963980; Package bumblebee-nvidia.
(Mon, 07 Dec 2020 22:00:03 GMT) (full text, mbox, link).

Acknowledgement sent
to Sébastien MARQUE <debian@seb.lautre.net>:
Extra info received and forwarded to list. Copy sent to debian@seb.lautre.net, Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth.debian.org>.
(Mon, 07 Dec 2020 22:00:03 GMT) (full text, mbox, link).

Message #77 received at 963980@bugs.debian.org (full text, mbox, reply):

Package: bumblebee
Version: 3.2.1-26~bpo10+1
Followup-For: Bug #963980

Dear Maintainer,


        everything was working as a charm, until few days ago. I can't find
        what has changed but only the following packages has been updated
        between the last time primusrun worked out of the box and the
        failure encountered:
        - libproxy1v5:amd64 (0.4.15-5, 0.4.15-5+deb10u1)
        - libbrotli1:amd64 (1.0.7-2, 1.0.7-2+deb10u1)
        - libproxy1-plugin-gsettings:amd64 (0.4.15-5, 0.4.15-5+deb10u1)
        - libproxy-tools:amd64 (0.4.15-5, 0.4.15-5+deb10u1)
        - libproxy1-plugin-webkit:amd64 (0.4.15-5, 0.4.15-5+deb10u1)
        - libproxy1-plugin-networkmanager:amd64 (0.4.15-5, 0.4.15-5+deb10u1)

        After many tries, following many attempts to workaround
        including the upgrade from stable to backports for bumblebee and
        nvidia propietary drivers I found a post, a bit isolated:
        https://github.com/Bumblebee-Project/Bumblebee/issues/652#issuecomment-123401024

        It talks about switching off the network as a workaround to get
        the secondary GPU driver loaded and used, no-one replied.

        It worked for me and I added the following piece of ugly code in script
        in order to use nvidia driver:

        (
            # TODO: manage restart of blutooth if needed
            nmcli radio all off
            while test $(lsmod | grep -c nvidia) -eq 0; do
                sleep 1
            done
            nmcli radio wifi on
        )&
        primusrun what_I_have_to_launch

        It is ugly, but it works (for now), and may be a clue for the
        resolution of the issue.

        I haven't tried from a dummy new user if the issue is still
        there, I haven't tried to upgrade to newer kernel. I've tried
        with nouveau and the issue is the same, but haven't tried yet
        with the network-off workaround.

        I don't have a github account so I can't post this upstream on
        bumblebee project.

        Thanks a lot for your concern, and best regards

        Sebastien MARQUE

-- Package-specific info:
OpenGL and NVIDIA library files installed:
lrwxrwxrwx 1 root root 25 Dec  4 19:19 /etc/alternatives/glx -> /usr/lib/nvidia/bumblebee
lrwxrwxrwx 1 root root 49 Dec  4 19:19 /etc/alternatives/glx--libEGL.so-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libEGL.so
lrwxrwxrwx 1 root root 51 Dec  4 19:19 /etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libEGL.so.1
lrwxrwxrwx 1 root root 48 Dec  4 19:19 /etc/alternatives/glx--libGL.so-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so
lrwxrwxrwx 1 root root 50 Dec  4 19:19 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root 55 Dec  4 19:19 /etc/alternatives/glx--libGLESv1_CM.so-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so
lrwxrwxrwx 1 root root 57 Dec  4 19:19 /etc/alternatives/glx--libGLESv1_CM.so.1-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so.1
lrwxrwxrwx 1 root root 52 Dec  4 19:19 /etc/alternatives/glx--libGLESv2.so-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so
lrwxrwxrwx 1 root root 54 Dec  4 19:19 /etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2
lrwxrwxrwx 1 root root 42 Dec  4 19:19 /etc/alternatives/glx--libGLX_indirect.so.0-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
lrwxrwxrwx 1 root root 51 Dec  4 19:19 /etc/alternatives/glx--libnvidia-cfg.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libnvidia-cfg.so.1
lrwxrwxrwx 1 root root 42 Dec  4 19:19 /etc/alternatives/glx--nvidia-blacklists-nouveau.conf -> /etc/nvidia/nvidia-blacklists-nouveau.conf
lrwxrwxrwx 1 root root 36 Dec  4 19:19 /etc/alternatives/glx--nvidia-bug-report.sh -> /usr/lib/nvidia/nvidia-bug-report.sh
lrwxrwxrwx 1 root root 32 Dec  4 19:19 /etc/alternatives/glx--nvidia-modprobe.conf -> /etc/nvidia/nvidia-modprobe.conf
lrwxrwxrwx 1 root root 23 Dec  4 19:19 /etc/alternatives/nvidia -> /usr/lib/nvidia/current
lrwxrwxrwx 1 root root 59 Dec  4 19:19 /etc/alternatives/nvidia--libEGL_nvidia.so.0-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/current/libEGL_nvidia.so.0
lrwxrwxrwx 1 root root 65 Dec  4 19:19 /etc/alternatives/nvidia--libGLESv1_CM_nvidia.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/current/libGLESv1_CM_nvidia.so.1
lrwxrwxrwx 1 root root 62 Dec  4 19:19 /etc/alternatives/nvidia--libGLESv2_nvidia.so.2-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/current/libGLESv2_nvidia.so.2
lrwxrwxrwx 1 root root 59 Dec  4 19:19 /etc/alternatives/nvidia--libGLX_nvidia.so.0-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/current/libGLX_nvidia.so.0
lrwxrwxrwx 1 root root 46 Dec  4 19:19 /etc/alternatives/nvidia--libglxserver_nvidia.so -> /usr/lib/nvidia/current/libglxserver_nvidia.so
lrwxrwxrwx 1 root root 59 Dec  4 19:19 /etc/alternatives/nvidia--libnvidia-cfg.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/current/libnvidia-cfg.so.1
lrwxrwxrwx 1 root root 58 Dec  4 19:19 /etc/alternatives/nvidia--libnvidia-ml.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/current/libnvidia-ml.so.1
lrwxrwxrwx 1 root root 61 Dec  4 19:19 /etc/alternatives/nvidia--libvdpau_nvidia.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/current/libvdpau_nvidia.so.1
lrwxrwxrwx 1 root root 38 Dec  4 19:19 /etc/alternatives/nvidia--nv-control-dpy -> /usr/lib/nvidia/current/nv-control-dpy
lrwxrwxrwx 1 root root 73 Dec  4 19:19 /etc/alternatives/nvidia--nvidia-application-profiles-key-documentation -> /usr/share/nvidia/nvidia-application-profiles-450.80.02-key-documentation
lrwxrwxrwx 1 root root 50 Dec  4 19:19 /etc/alternatives/nvidia--nvidia-blacklists-nouveau.conf -> /etc/nvidia/current/nvidia-blacklists-nouveau.conf
lrwxrwxrwx 1 root root 44 Dec  4 19:19 /etc/alternatives/nvidia--nvidia-bug-report.sh -> /usr/lib/nvidia/current/nvidia-bug-report.sh
lrwxrwxrwx 1 root root 40 Dec  4 19:19 /etc/alternatives/nvidia--nvidia-debugdump -> /usr/lib/nvidia/current/nvidia-debugdump
lrwxrwxrwx 1 root root 47 Dec  4 19:19 /etc/alternatives/nvidia--nvidia-drm-outputclass.conf -> /etc/nvidia/current/nvidia-drm-outputclass.conf
lrwxrwxrwx 1 root root 36 Dec  4 19:19 /etc/alternatives/nvidia--nvidia-load.conf -> /etc/nvidia/current/nvidia-load.conf
lrwxrwxrwx 1 root root 40 Dec  4 19:19 /etc/alternatives/nvidia--nvidia-modprobe.conf -> /etc/nvidia/current/nvidia-modprobe.conf
lrwxrwxrwx 1 root root 39 Dec  4 19:19 /etc/alternatives/nvidia--nvidia-settings -> /usr/lib/nvidia/current/nvidia-settings
lrwxrwxrwx 1 root root 44 Dec  4 19:19 /etc/alternatives/nvidia--nvidia-settings.1.gz -> /usr/lib/nvidia/current/nvidia-settings.1.gz
lrwxrwxrwx 1 root root 47 Dec  4 19:19 /etc/alternatives/nvidia--nvidia-settings.desktop -> /usr/lib/nvidia/current/nvidia-settings.desktop
lrwxrwxrwx 1 root root 37 Dec  4 19:19 /etc/alternatives/nvidia--nvidia_drv.so -> /usr/lib/nvidia/current/nvidia_drv.so

/etc/modprobe.d:
total 32
drwxr-xr-x   2 root root  4096 Dec  4 19:19 .
drwxr-xr-x 141 root root 12288 Dec  7 22:46 ..
-rw-r--r--   1 root root   473 Feb 20  2020 blacklist-vboxpci.conf
-rw-r--r--   1 root root   570 Dec  4 19:18 bumblebee.conf
-rw-r--r--   1 root root   127 Jan  2  2019 dkms.conf
lrwxrwxrwx   1 root root    53 Dec  4 19:19 nvidia-blacklists-nouveau.conf -> /etc/alternatives/glx--nvidia-blacklists-nouveau.conf
-rw-r--r--   1 root root   260 Jul 13 23:03 nvidia-kernel-common.conf
lrwxrwxrwx   1 root root    43 Dec  4 19:19 nvidia.conf -> /etc/alternatives/glx--nvidia-modprobe.conf

/etc/modprobe.d/nvidia-kernel-common.conf:alias char-major-195* nvidia
/etc/modprobe.d/nvidia-kernel-common.conf:#options nvidia NVreg_DeviceFileUID=0 NVreg_DeviceFileGID=44 NVreg_DeviceFileMode=0660
/etc/modprobe.d/nvidia-kernel-common.conf:# options nvidia NVreg_EnableAGPSBA=1
/etc/modprobe.d/nvidia-kernel-common.conf:# options nvidia NVreg_EnableAGPFW=1
/etc/modprobe.d/bumblebee.conf:# do not automatically load nouveau as it may prevent nvidia from loading
/etc/modprobe.d/bumblebee.conf:# do not automatically load nvidia as it's unloaded anyway when bumblebeed
/etc/modprobe.d/bumblebee.conf:blacklist nvidia
/etc/modprobe.d/bumblebee.conf:blacklist nvidia-current
/etc/modprobe.d/bumblebee.conf:blacklist nvidia-tesla-450
/etc/modprobe.d/bumblebee.conf:blacklist nvidia-tesla-440
/etc/modprobe.d/bumblebee.conf:blacklist nvidia-tesla-418
/etc/modprobe.d/bumblebee.conf:blacklist nvidia-legacy-390xx
/etc/modprobe.d/bumblebee.conf:blacklist nvidia-legacy-340xx
/etc/modprobe.d/bumblebee.conf:# do not automatically load nouveau as it may prevent nvidia from loading
/etc/modprobe.d/bumblebee.conf:blacklist nouveau


-- System Information:
Debian Release: 10.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-12-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages bumblebee depends on:
ii  init-system-helpers  1.56+nmu1
ii  libbsd0              0.9.1-2
ii  libc6                2.28-10
ii  libglib2.0-0         2.58.3-2+deb10u2
ii  libkmod2             26-1
ii  libx11-6             2:1.6.7-1+deb10u1
ii  lsb-base             10.2019051400
ii  xserver-xorg-core    2:1.20.4-1+deb10u2

Versions of packages bumblebee recommends:
ii  bbswitch-dkms  0.8-8
ii  primus-libs    0~20150328-12~bpo10+1

Versions of packages bumblebee suggests:
ii  bumblebee-nvidia  3.2.1-26~bpo10+1

Versions of packages bumblebee is related to:
ii  nvidia-driver [nvidia-driver-any]                     450.80.02-1~bpo10+1
ii  nvidia-driver-libs [nvidia-driver-libs-any]           450.80.02-1~bpo10+1
ii  primus-libs                                           0~20150328-12~bpo10+1
ii  xserver-xorg-video-nvidia [xserver-xorg-video-nvidia  450.80.02-1~bpo10+1

-- no debconf information

Information forwarded
to debian-bugs-dist@lists.debian.org, Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth.debian.org>:
Bug#963980; Package bumblebee-nvidia.
(Wed, 27 Jan 2021 17:27:02 GMT) (full text, mbox, link).

Acknowledgement sent
to Dan Robinson <dlrobin874@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth.debian.org>.
(Wed, 27 Jan 2021 17:27:03 GMT) (full text, mbox, link).

Message #82 received at 963980@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

I also had this issue on a fresh bullseye install.

I was able to get a different error message by commenting out the reference
to /etc/bumblebee/xorg.conf.d in /etc/bumblebee.conf, but then I get a
different error about a missing module 'mouse'.

Unfortunately I didn't have any time to troubleshoot any further and I
think there are other issues at play outside the scope of this bug (like
the fact that with the legacy Nvidia drivers there is no 'nvidia' module so
it's trying to use nouveau) so I'll probably have to try to solve all of
that before I can offer any more useful feedback on this bug.

[Message part 2 (text/html, inline)]

Information forwarded
to debian-bugs-dist@lists.debian.org, Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth.debian.org>:
Bug#963980; Package bumblebee-nvidia.
(Tue, 29 Jun 2021 11:54:03 GMT) (full text, mbox, link).

Acknowledgement sent
to Marcus Hardt <marcus@hardt-it.de>:
Extra info received and forwarded to list. Copy sent to Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth.debian.org>.

Your message did not contain a Subject field. They are recommended and
useful because the title of a Bug is determined using this field.
Please remember to include a Subject field in your messages in future.

(Tue, 29 Jun 2021 11:54:03 GMT) (full text, mbox, link).

Message #87 received at 963980@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

I have the same issue with these versions:


bumblebee:  3.2.1-27
init-system-helpers:  1.60
libbsd0:  0.11.3-1
libc6:  2.31-12
libglib2: 
libkmod2:  28-1
libx11-6:  2:1.7.1-1
lsb-base:  11.1.0
xserver-xorg-core:  2:1.20.11-1
bbswitch-dkms:  0.8-10
primus-libs:  0~20150328-13
bumblebee-nvidia:  3.2.1-27
nvidia-driver:  460.73.01-1
nvidia-driver-libs:  460.73.01-1
primus-libs:  0~20150328-13
xserver-xorg-video-nvidia:  460.73.01-1



-- 
Marcus.

[signature.asc (application/pgp-signature, inline)]

Information forwarded
to debian-bugs-dist@lists.debian.org, Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth.debian.org>:
Bug#963980; Package bumblebee-nvidia.
(Sat, 04 Dec 2021 23:09:02 GMT) (full text, mbox, link).

Acknowledgement sent
to Luc <bug963980-throwawayemailaddress@lgms.nl>:
Extra info received and forwarded to list. Copy sent to Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth.debian.org>.

(Sat, 04 Dec 2021 23:09:03 GMT) (full text, mbox, link).

Message #92 received at 963980@bugs.debian.org (full text, mbox, reply):

Many thanks to Sébastien MARQUE for the suggestion `nmcli radio all
off`. This resolves the problem. For me, I don't need to wait for nvidia
to no longer be in lsmod before I can start it again.

This is with a Qualcomm Atheros QCA9377 802.11ac Wireless Network
Adapter (rev 31), Intel Corporation UHD Graphics 620 (rev 07), and
NVIDIA Corporation GP108M [GeForce MX150] (rev a1), on an up-to-date
Debian 10 using nouveau drivers if I'm not mistaken (I tried every
possible setup until something worked to run Parkitect a few weeks ago,
not sure what the current setup is, just that the nvidia-detect command
doesn't exist and I have to prefix primusrun and add -force-opengl).

If I can help by providing details about my setup or by trying
something, please let me know what commands to run -- via lgms.nl/email
since I expect I'll be receiving spam on the sending address before too
long which means I'll have to block it.

Best,
Luc

Information forwarded
to debian-bugs-dist@lists.debian.org, Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth.debian.org>:
Bug#963980; Package bumblebee-nvidia.
(Sat, 08 Jan 2022 18:00:03 GMT) (full text, mbox, link).

Acknowledgement sent
to "Sébastien Marque" <debian@seb.lautre.net>:
Extra info received and forwarded to list. Copy sent to Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth.debian.org>.
(Sat, 08 Jan 2022 18:00:03 GMT) (full text, mbox, link).

Message #97 received at 963980@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

Hello,

Nice to see the hack could help someone.

BTW I "improved" the ugly hack this way:

 (
 path=/proc/driver/nvidia
 if ! test -e $path; then
 IFS=':' read -a radio <<< $(LANG=C nmcli -t radio)
 nmcli radio wifi off
 while ! test -e $path; do
 continue
 done
 test ${radio[1]} = 'enabled' && nmcli radio wifi on
 fi
)&

And it resides now on /usr/local/bin/primusrun (https://seb.lautre.net/git/seb/scripts/blob/master/primusrun (https://seb.lautre.net/git/seb/scripts/blob/master/primusrun))

Best regards,

Seb

[Message part 2 (text/html, inline)]

Information forwarded
to debian-bugs-dist@lists.debian.org, Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth.debian.org>:
Bug#963980; Package bumblebee-nvidia.
(Wed, 02 Feb 2022 21:57:03 GMT) (full text, mbox, link).

Acknowledgement sent
to Jérémy Viès <jeremy.vies@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth.debian.org>.
(Wed, 02 Feb 2022 21:57:03 GMT) (full text, mbox, link).

Message #102 received at 963980@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

I can confirm I have the same issue using a brandly new installed machine
with the nvidia driver.


primus: fatal: Bumblebee daemon reported: error: [XORG] (EE) Unable to
locate/open config directory: "/etc/bumblebee/xorg.conf.d"

[Message part 2 (text/html, inline)]

Send a report that this bug log contains spam.

Debian bug tracking system administrator <owner@bugs.debian.org>.
Last modified:
Thu Feb 9 07:59:38 2023;
Machine Name:
bembo

Debian Bug tracking system

Debbugs is free software and licensed under the terms of the GNU
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.

Copyright © 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson,
2005-2017 Don Armstrong, and many other contributors.

Источник

Печать

Страницы: [1] Вниз

Тема: Проблема с запуском optirun bumblebee на 15.04 (Прочитано 3376 раз)

0 Пользователей и 1 Гость просматривают эту тему.

c00lrad

Я обновил Ubuntu до последней версии.
Так вот, в прошлой версии запуск оптируна работал корректно.
А вот в новой, выводят вот такие ошибки —

allein@NoOneCares:~$ optirun steam steam://rungameid/570 [ 4389.816525] [ERROR]Cannot access secondary GPU - error: Could not load GPU driver


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

Это попытка запуска игры дота2. Работала корректно уже год.
И, конечно же, через любую другую программу с оптируном или примусом, например, glxgears возвращает те же ошибки.
Так вот, прошу разгадать эту задачку.

P.S. Добавить в строку «Driver=» nvidia и «KernelDriver» nvidia-current или nvidia-331? Это бесполезно!
Конечно же, перезагрузить не забываю.

symon2014

c00lrad

Ну, это и было моей первой статьей и по ней пытался решить проблему, до создания этой темы.
Все бесполезно. После махинаций я получаю только это, но уже с другой ошибкой.

allein@NoOneCares:~$ optirun glxgears [ 629.560057] [ERROR]The Bumblebee daemon has not been started yet or the socket path /var/run/bumblebee.socket was incorrect. [ 629.560126] [ERROR]Could not connect to bumblebee daemon - is it running? allein@NoOneCares:~$ sudo start bumblebeed start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refusedЧтобы вернуться к первой ошибки, я удаляю бумблееды и нвидиа, переустанавливаю вновь.

Так, как же запустить сервис бумблебее?
Если так писать

systemctl enable bumblebeed systemctl start bumblebeedТо выводятся какие-то ошибки, такое ощущение что эти команды не подходят линуксу в новой версии.

« Последнее редактирование: 27 Апреля 2015, 20:19:04 от c00lrad »

GNU/Linux forever.

symon2014

c00lrad

Нет, только что пришел с него, спасибо за хорошую ссылку.
Но там решение проблемы такое — переустановить заново Ubuntu. Неужели нет более лаконичного решения проблемы?

symon2014

Есть — через год выйдет Ubuntu 16.04 LTS, а 15.04 для тренировки.

c00lrad

Довольно логично.
А как можно откатать?) Через груб не поможет, хотя там были аж 3 ядра на выбор, ибо та же самая ошибка. Понимаю, что это уже другая тема, но тем не менее, это может послужить решением созданной проблемы)

symon2014

Я обновил Ubuntu до последней версии.

Надо понимать что установил а не обновил. Боюсь что вернуться можно таким же способом.

c00lrad

Итак, я решил проблему благодаря symon2014。
Он　мне　скинул　ссылку　в　личное　сообщение　https://forum.ubuntu.ru/index.php?topic=190100.0
Так　вот, начиная с последней страницы(как-никак 15.04 новая версия) я прочитал снизу вверх и пришло озарение)
Решение — установить nvidia-prime (https://help.ubuntu.ru/wiki/nvidia-prime)
Никаких вводов с консоли, кроме предварительной настройки, если потребуется, не нужно!
Кликаешь на стим, на доту и играешь. Как на винде.
Да и на других программах тоже. Принцип работы с праймом и оптируном схож.

Печать

Страницы: [1] Вверх

Источник

7 комментариев

avatar

pushsla
↓
27 октября 2019, 23:08

Не запускаютя игры с bumblebeed.

А что вы запускаете? А как вы запускаете? А что говорит, когда не запускается?

В норме

optirun steam чего-то там...

работает, как надо… не?

avatar

автор baz
↑
↓
3 ноября 2019, 21:18

[76937.270331] [ERROR]The Bumblebee daemon has not been started yet or the socket path /var/run/bumblebee.socket was incorrect.

avatar

PavelMilko
↓
28 октября 2019, 01:52

primusrun glxinfo | grep -i opnegl
glxinfo | grep -i opnegl

Сравни выхлоп. В первом варианте должно быть что-то про nvidia.
В стим зоходеш, жамкоеш на игру. И устанавливаешь параматры запуска

primusrun %command%

Да, прям так и пишешь.

avatar

автор baz
↑
↓
3 ноября 2019, 21:29

primusrun glxinfo | grep -i opnegl
primus: fatal: failed to connect to Bumblebee daemon: No such file or directory

Только зарегистрированные и авторизованные пользователи могут оставлять комментарии.

Источник

Arch Linux

You are not logged in.

#1 2015-03-27 11:53:00

Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

Hello. I am trying to get bumblebee up and running but there seems to be an issue. This is what i’ve done:

But when i try to test it out i get the output:

So i whent onto the wiki and found this: (and also installed bbswitch)

mkinitcpio ran fine with no errors. After i rebooted i got promoted with the same error. Can anyone give me a hint on if im missing someting?

#2 2015-03-27 13:04:47

Re: Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

You have both linux 3.19 an linux 4 — does this happen when you boot both kernels & kernel images?

#3 2015-03-27 13:20:08

Re: Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

You have both linux 3.19 an linux 4 — does this happen when you boot both kernels & kernel images?

I can also add that i just tried this solution without any progress.

#4 2015-03-27 13:24:35

Re: Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

So which kernel are you trying to run bumblebee on?
If you try to run it on v4 you probably need to compile the nvidia modules against this version.
What does

give you right after reboot?

I put at button on it. Yes. I wish to press it, but I’m not sure what will happen if I do. (Gune | Titan A.E.)

#5 2015-03-27 13:26:13

Re: Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

So which kernel are you trying to run bumblebee on?
If you try to run it on v4 you probably need to compile the nvidia modules against this version.
What does

give you right after reboot?

I always use v4 and have been used when i installed the drivers. Anything i need to do?

Sorry, that one was not right after reboot. This one is tho (inside i3wm):

And the bbswitch error disapeard but now im back on the first log with xorg errors.
/var/log/Xorg.8.log

Last edited by AndreasEr (2015-03-27 15:15:29)

#6 2015-03-28 05:30:18

Re: Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

I decided to try and change to bumblebee-git. Did not work out but gave me another error:

Wiki told me this, But with no success:

Everything worked fine on my previous optimus laptop from asus. Is it someting im missing with those «new» GPUs? It’s a Geforce 840m.

Last edited by AndreasEr (2015-03-28 05:32:16)

#7 2015-03-28 08:49:10

Re: Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

So which kernel are you trying to run bumblebee on?
If you try to run it on v4 you probably need to compile the nvidia modules against this version.

And also the module for bbswitch.

EDIT: from your Xorg.8.log it seems that you are using bumblebee with nouveau drivers. Therefore changes in the nvidia related configs won’t apply

Last edited by dice (2015-03-28 08:52:55)

I put at button on it. Yes. I wish to press it, but I’m not sure what will happen if I do. (Gune | Titan A.E.)

#8 2015-03-28 17:04:25

Re: Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

So which kernel are you trying to run bumblebee on?
If you try to run it on v4 you probably need to compile the nvidia modules against this version.

And also the module for bbswitch.

EDIT: from your Xorg.8.log it seems that you are using bumblebee with nouveau drivers. Therefore changes in the nvidia related configs won’t apply

#9 2015-06-27 16:51:09

Re: Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

I get this error
primus: fatal: Bumblebee daemon reported: error: [XORG] (EE) systemd-logind: failed to get session: PID 6333 does not belong to any known session

I think I should now file a bug report for this issue.

Do you also see similar behaviour ? Please let me know so that I could log a bug for this as it would then be established that it works fine after a second or 3rd attempt.?

Linux is easy.. People are Difficult

#10 2015-08-15 08:44:49

Re: Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

I had the same error message trying to use primusrun / optirun :

primus: fatal: Bumblebee daemon reported: error: [XORG] (EE) systemd-logind: failed to get session: PID xxxx does not belong to any known session

It used to work fine a couple of kernel versions ago, when I initially setup bumblebeed I applied most hints from the bumblebee wiki page.

I suppose loading the bbswitch module early, causes it to be loaded in a wrong (no) session context somehow.

I don’t know if this will help solve your issue, but I thought I’d leave it here for reference.

Источник

Arch Linux

You are not logged in.

#1 2013-04-26 10:38:18

primus: fatal: failure contacting bumblebee daemon [SOLVED]

I just did a pacman -Syu which broke my system as usual. This time I get the above error message when trying to use primusrun:

Trying to run glxshperes gives a slightly different message:

and via optirun, just for the heck of it:

I noticed:
1) primus in official repos (I was using git so far) causes a timeout from about 40 mirrors until it finds one where the download works. I hope that’s no bad sign of some sort?
2) bumblebeed update created new bumblebee.conf.pacnew and xorg.conf.nvidia.pacnew
3) off-topic: When I clicked ‘logout’ in XFCE’s applications menu, usually I get a box where I can pick whether I wanna logout/restart/shutdown etc, but this time it just straightly logged me out (makes sense I guess).
4) after rebooting my system I saw I think two systemd error messages pop up for a split second, that usually did not occur.
5) Xorg.8.log had the line «[633217.731] (WW) NVIDIA: This server has an unsupported input driver ABI version (have 19.1, need but both exit with the error message.
I tried the new conf files (copied the pacnew files to the normal filenames) but they don’t work either.

I checked:
Bumbleed is running, systemctl shows

and lspci | grep VGA shows the usual

(After I try to start something with primusrun, the indicator light switches on and remains on, I can turn it off again with the usual

.)
dmesg has these:

echoing ‘OFF’ to bbswitch seems fine though (it worked, as I mentioned)

Here is /var/log/Xorg.8.log (trimmed):

PS: In this light I was wondering whether the https://wiki.archlinux.org/index.php/Bumblebee article is still up to date or might need reworking of some sort (I don’t have any actual ideas to base this on though, was just a thought)

Last edited by Jindur (2013-04-27 18:10:21)

Источник

primus: fatal: Bumblebee daemon reported: error: Could not load GPU driver

I recently installed Ubuntu 14.04 and then installed bumblebee following the instructions on Ubuntu Bumblebee wiki(where they said that primusrun is better than optirun for version=> 13.10) But when I rebooted and tried to run primusrun with any applications (except google-chrome and firefox) the following error came(and comes):

And surprisingly when I check the status of my nvidia driver, it gets on after running for example

gives the following

Then, in order to avoid powerloss, I have to switch it off by bbswitch

NOTE: I was able to turn it off using bbswitch only after I set Driver=nouveau in the /etc/bumblebee/bumblebee.conf file and rebooted it.

2 Answers 2

I had the same problem.

I solved changing some lines in file /etc/bumblebee/bumblebee.conf : (In my case I’m using the version 352 of nvidia driver, change this value by your driver version)

KernelDriver=nvidia-current to KernelDriver=nvidia-352

LibraryPath=/usr/lib/nvidia-current:/usr/lib32/nvidia-current to LibraryPath=/usr/lib/nvidia-352:/usr/lib32/nvidia-352

XorgModulePath=/usr/lib/nvidia-current/xorg,/usr/lib/xorg/modules to XorgModulePath=/usr/lib/nvidia-352/xorg,/usr/lib/xorg/modules

After that restart the system or restart the bumblebee service with:

sudo systemctl restart bumblebeed.service

To check the service status:

sudo systemctl status bumblebeed.service

and you can check the log in /var/log/syslog file for any error.

new update: as I thought, changing just one line in /etc/bumblebee/bumblebee.conf actually worked out: I got everything working perfectly on updated LMDE 201403 (debian jessie based) by just adding some code to KernelDriver line. Before editing, it was like:

I just added -current to it. This is line now:

Now works fine with primusrun glxgears and optirun glxgears . Haven’t checked with anything else, have no time currently. Hope this helped, cheers. 😀

line 22: Driver=nvidia
line 55: KernelDriver=nvidia-_version_ , i.e. nvidia-352
lines 58, 61: these lines contain paths to nvidia libraries and xorg modules. Paths probably start with /usr/lib/nvidia , /usr/lib32/nvidia , or /usr/lib/xorg . You should replace nvidia with nvidia-_version_ , i.e. /usr/lib/nvidia-352 . Pay attention: each line contains 2 paths, separated by colon or by comma. You should make changes to each path (DO NOT edit path that starts with /usr/lib/xorg ).

Note that if you want to use default drivers, _version_ should be current , i.e. line 52: KernelDriver=nvidia-current . I think that bumblebee comes preconfigured to use nvidia-current when package bumblebee-nvidia is installed ( sudo apt-get install bumblebee-nvidia ).

If done correctly, bumblebee should not report error finding drivers — this worked for me with numerous driver versions.

Источник

primus: fatal: Bumblebee daemon reported: error: [XORG] (EE) Failed to load module «nvidia» (module does not exist, 0)

Какой-то косяк произошел. Кто-нибудь сталкивался? Как решать?
Рабочий модуль ядра есть. Вроде все ставил правильно.
Спрашивайте еще данные, отвечу.

Я вроде все про это написал

Bumblebee его должен сам подгружать, но даже если руками это сделать, то результат не поменяется.

перезагрузись што ли

мануал по которому ставил в студию! Bbswitch стоит?

Что /etc/bumblebee/ Driver=nvidia стоит?

Кажется нашел в чем проблема, что-то блочит флаг X у nvidia-drivers.

у тебя тоже x11-misc/primus-9999 или нашел нормальный ебилд?

Тоже, а что с ним не так?

у тебя тоже x11-misc/primus-9999 или нашел нормальный ебилд?

Тоже, а что с ним не так?

Тоже с недели две назад с primus была ошибка какая-то, но с optirun работало нормально. Сам primus обновил из Bumblebee-Project и он тоже заработал.

просто я не люблю live-ebuild’ы, думал, мож где есть обычный. убунтоиды же не из гита примус собирают, у них полюбому в каком то ppa есть пакеты нормальные.

Источник

# 10 лет, 6 месяцев назад
Темы: 6 Сообщения: 32 Участник с: 14 марта 2012	Приветствую! Пытаюсь запустить bumblebee командой rc.d start bumblebee выходит такая ошибка: /etc/rc.d/functions: line 212: /run/daemons/bumblebeed: Отказано в доступе есть идеи? П.С. вот команда на на строчке 212 >\| /run/daemons/“$1”

#
10 лет, 6 месяцев назад

Темы:

Сообщения:

Участник с: 14 марта 2012

Приветствую! Пытаюсь запустить bumblebee командой rc.d start bumblebee выходит такая ошибка:
/etc/rc.d/functions: line 212: /run/daemons/bumblebeed: Отказано в доступе

есть идеи?

П.С. вот команда на на строчке 212 >| /run/daemons/“$1”

derfenix	# 10 лет, 6 месяцев назад
Темы: 4 Сообщения: 232 Участник с: 10 февраля 2012	от рута, надеюсь, запускаешь? %) дай вывод ls -l /run/daemons

derfenix

#
10 лет, 6 месяцев назад

Темы:

Сообщения:

232

Участник с: 10 февраля 2012

от рута, надеюсь, запускаешь? %)
дай вывод

ls -l /run/daemons

djemna	# 10 лет, 6 месяцев назад
Темы: 6 Сообщения: 32 Участник с: 14 марта 2012	Все проблема решена, но теперь не могу протестировать. Выходит ошибка [27541.303608] [ERROR]The Bumblebee daemon has not been started yet or the socket path /var/run/bumblebee.socket was incorrect. [27541.303718] [ERROR]Could not connect to bumblebee daemon - is it running? в демоны я добавил. -rw-r--r-- 1 root root 0 июля 27 21:50 alsa -rw-r--r-- 1 root root 0 июля 31 13:19 bumblebeed -rw-r--r-- 1 root root 0 июля 27 21:50 crond -rw-r--r-- 1 root root 0 июля 27 21:50 dbus -rw-r--r-- 1 root root 0 июля 27 21:50 gdm -rw-r--r-- 1 root root 0 июля 27 21:50 networkmanager -rw-r--r-- 1 root root 0 июля 27 21:50 syslog-ng

djemna

#
10 лет, 6 месяцев назад

Темы:

Сообщения:

Участник с: 14 марта 2012

Все проблема решена, но теперь не могу протестировать. Выходит ошибка

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

в демоны я добавил.

-rw-r--r-- 1 root root 0 июля  27 21:50 alsa
-rw-r--r-- 1 root root 0 июля  31 13:19 bumblebeed
-rw-r--r-- 1 root root 0 июля  27 21:50 crond
-rw-r--r-- 1 root root 0 июля  27 21:50 dbus
-rw-r--r-- 1 root root 0 июля  27 21:50 gdm
-rw-r--r-- 1 root root 0 июля  27 21:50 networkmanager
-rw-r--r-- 1 root root 0 июля  27 21:50 syslog-ng

derfenix	# 10 лет, 6 месяцев назад
Темы: 4 Сообщения: 232 Участник с: 10 февраля 2012	Когда выходит эта ошибка? демон добавил, а запустил? что выдаёт bumblebeed -vv (запускать от рута)

derfenix

#
10 лет, 6 месяцев назад

Темы:

Сообщения:

232

Участник с: 10 февраля 2012

Когда выходит эта ошибка?
демон добавил, а запустил? что выдаёт

bumblebeed -vv

(запускать от рута)

djemna	# 10 лет, 6 месяцев назад
Темы: 6 Сообщения: 32 Участник с: 14 марта 2012	[31675.495746] [ERROR]The Bumblebee daemon has not been started yet or the socket path /var/run/bumblebee.socket was incorrect. [31675.495857] [ERROR]Could not connect to bumblebee daemon - is it running? [[email protected] ~]# bumblebeed -vv [31686.420157] [DEBUG]Reading file: /etc/bumblebee/bumblebee.conf [31686.421007] [DEBUG]Detected nouveau driver [31686.421518] [INFO]Loading driver bbswitch (module bbswitch) [31686.421828] [DEBUG]Process modprobe started, PID 26595. [31686.423805] [DEBUG]Process with PID 26595 returned code 1 [31686.424173] [ERROR]Module bbswitch could not be loaded (timeout?) [31686.424192] [DEBUG]bbswitch is not available, perhaps you need to insmod it? [31686.424205] [INFO]Skipping switcheroo PM method because it is not explicitly selected in the configuration. [31686.424217] [WARN]No switching method available. The dedicated card will always be on. [31686.424228] [DEBUG]Active configuration: [31686.424239] [DEBUG] bumblebeed config file: /etc/bumblebee/bumblebee.conf [31686.424257] [DEBUG] X display: :8 [31686.424274] [DEBUG] LD_LIBRARY_PATH: [31686.424288] [DEBUG] Socket path: /var/run/bumblebee.socket [31686.424303] [DEBUG] pidfile: /var/run/bumblebeed.pid [31686.424317] [DEBUG] xorg.conf file: /etc/bumblebee/xorg.conf.nouveau [31686.424333] [DEBUG] ModulePath: [31686.424349] [DEBUG] GID name: bumblebee [31686.424366] [DEBUG] Power method: auto [31686.424383] [DEBUG] Stop X on exit: 1 [31686.424401] [DEBUG] Driver: nouveau [31686.424418] [DEBUG] Driver module: nouveau [31686.424438] [DEBUG] Card shutdown state: 1 [31686.424762] [DEBUG]Process modinfo started, PID 26596. [31686.424859] [DEBUG]Hiding stderr for execution of modinfo [31686.426552] [DEBUG]SIGCHILD received, but wait failed with No child processes [31686.426583] [ERROR]Module 'nouveau' is not found. На первый взгляд много ошибок.

djemna

#
10 лет, 6 месяцев назад

Темы:

Сообщения:

Участник с: 14 марта 2012

[31675.495746] [ERROR]The Bumblebee daemon has not been started yet or the socket path /var/run/bumblebee.socket was incorrect.
[31675.495857] [ERROR]Could not connect to bumblebee daemon - is it running?
[[email protected] ~]# bumblebeed -vv
[31686.420157] [DEBUG]Reading file: /etc/bumblebee/bumblebee.conf
[31686.421007] [DEBUG]Detected nouveau driver
[31686.421518] [INFO]Loading driver bbswitch (module bbswitch)
[31686.421828] [DEBUG]Process modprobe started, PID 26595.
[31686.423805] [DEBUG]Process with PID 26595 returned code 1
[31686.424173] [ERROR]Module bbswitch could not be loaded (timeout?)
[31686.424192] [DEBUG]bbswitch is not available, perhaps you need to insmod it?
[31686.424205] [INFO]Skipping switcheroo PM method because it is not explicitly selected in the configuration.
[31686.424217] [WARN]No switching method available. The dedicated card will always be on.
[31686.424228] [DEBUG]Active configuration:
[31686.424239] [DEBUG] bumblebeed config file: /etc/bumblebee/bumblebee.conf
[31686.424257] [DEBUG] X display: :8
[31686.424274] [DEBUG] LD_LIBRARY_PATH: 
[31686.424288] [DEBUG] Socket path: /var/run/bumblebee.socket
[31686.424303] [DEBUG] pidfile: /var/run/bumblebeed.pid
[31686.424317] [DEBUG] xorg.conf file: /etc/bumblebee/xorg.conf.nouveau
[31686.424333] [DEBUG] ModulePath: 
[31686.424349] [DEBUG] GID name: bumblebee
[31686.424366] [DEBUG] Power method: auto
[31686.424383] [DEBUG] Stop X on exit: 1
[31686.424401] [DEBUG] Driver: nouveau
[31686.424418] [DEBUG] Driver module: nouveau
[31686.424438] [DEBUG] Card shutdown state: 1
[31686.424762] [DEBUG]Process modinfo started, PID 26596.
[31686.424859] [DEBUG]Hiding stderr for execution of modinfo
[31686.426552] [DEBUG]SIGCHILD received, but wait failed with No child processes
[31686.426583] [ERROR]Module 'nouveau' is not found.

На первый взгляд много ошибок.

derfenix	# 10 лет, 6 месяцев назад
Темы: 4 Сообщения: 232 Участник с: 10 февраля 2012	Самое главное в конце: Module ‘nouveau’ is not found. догадываешься о чём речь? но я советую не ставить nouveau, а поставить проприетарные дрова. Ставь nvidia-bumblebee, перезапускай bumblebeed и будет счастье. Только если ядро 3.5 (подключены testing репозитории) — надо будет отредактировать PKGBUILD и install скрипт — заменить там везде 3.4 на 3.5 и в PKGBUILD’е убрать linux<3.5 в зависимостях и конфликтах.

derfenix

#
10 лет, 6 месяцев назад

Темы:

Сообщения:

232

Участник с: 10 февраля 2012

Самое главное в конце: Module ‘nouveau’ is not found.
догадываешься о чём речь? но я советую не ставить nouveau, а поставить проприетарные дрова. Ставь nvidia-bumblebee, перезапускай bumblebeed и будет счастье.

Только если ядро 3.5 (подключены testing репозитории) — надо будет отредактировать PKGBUILD и install скрипт — заменить там везде 3.4 на 3.5 и в PKGBUILD’е убрать linux<3.5 в зависимостях и конфликтах.

djemna	# 10 лет, 6 месяцев назад
Темы: 6 Сообщения: 32 Участник с: 14 марта 2012	Установил. Все равно ошибка. что модуль nouveau отсутствует. Уже перезапустил комп. ошибка та же. [ 753.512152] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) Failed to load module "nouveau" (module does not exist, 0) [ 753.512263] [ERROR]Aborting because fallback start is disabled.

djemna

#
10 лет, 6 месяцев назад

Темы:

Сообщения:

Участник с: 14 марта 2012

Установил. Все равно ошибка. что модуль nouveau отсутствует. Уже перезапустил комп. ошибка та же.

[  753.512152] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) Failed to load module "nouveau" (module does not exist, 0)
[  753.512263] [ERROR]Aborting because fallback start is disabled.

djemna	# 10 лет, 6 месяцев назад
Темы: 6 Сообщения: 32 Участник с: 14 марта 2012	Все, запустилось все! Спасибо! Пока тему не закрывайте, у меня возможно еще будут вопросы! Спасибо!

djemna

#
10 лет, 6 месяцев назад

Темы:

Сообщения:

Участник с: 14 марта 2012

Все, запустилось все! Спасибо! Пока тему не закрывайте, у меня возможно еще будут вопросы! Спасибо!

djemna	# 10 лет, 6 месяцев назад
Темы: 6 Сообщения: 32 Участник с: 14 марта 2012	Такой еще вопрос.. если у меня glxgears запустился и все без проблем, то получается теперь наконец nvidia подключена?

djemna

#
10 лет, 6 месяцев назад

Темы:

Сообщения:

Участник с: 14 марта 2012

Такой еще вопрос.. если у меня glxgears запустился и все без проблем, то получается теперь наконец nvidia подключена?

gudvin-t	# 10 лет, 6 месяцев назад
Темы: 38 Сообщения: 244 Участник с: 09 ноября 2010	если вы уверены, что он запустился с ускорителем nvidia, то да FPS у меня порядка 600-900 (на intel с SNA и отключенным vsync порядка 4000 FPS) это можно проверить, установив опцию AllowFallbackToIGC=false в /etc/bumblebee/bumblebee.conf и попробовать еще раз запустить glxgers и, если вы до сих пор этого не сделали, советую настроить энергосбережение (выключение с помощью bbswitch, выключение иксов после завершения приложения и т.д.)

gudvin-t

#
10 лет, 6 месяцев назад

Темы:

Сообщения:

244

Участник с: 09 ноября 2010

если вы уверены, что он запустился с ускорителем nvidia, то да

FPS у меня порядка 600-900 (на intel с SNA и отключенным vsync порядка 4000 FPS)
это можно проверить, установив опцию
AllowFallbackToIGC=false

в /etc/bumblebee/bumblebee.conf и попробовать еще раз запустить glxgers
и, если вы до сих пор этого не сделали, советую настроить энергосбережение (выключение с помощью bbswitch, выключение иксов после завершения приложения и т.д.)

Источник

#1 2015-03-27 11:53:00

Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

#2 2015-03-27 13:04:47

Re: Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

#3 2015-03-27 13:20:08

Re: Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

#4 2015-03-27 13:24:35

Re: Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

#5 2015-03-27 13:26:13

Re: Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

#6 2015-03-28 05:30:18

Re: Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

#7 2015-03-28 08:49:10

Re: Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

#8 2015-03-28 17:04:25

Re: Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

#9 2015-06-27 16:51:09

Re: Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

#10 2015-08-15 08:44:49

Re: Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> c00lrad

symon2014

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> c00lrad

symon2014

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> c00lrad

symon2014

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> c00lrad

symon2014

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> c00lrad

Arch Linux

#1 2015-03-27 11:53:00

Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

#2 2015-03-27 13:04:47

Re: Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

#3 2015-03-27 13:20:08

Re: Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

#4 2015-03-27 13:24:35

Re: Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

#5 2015-03-27 13:26:13

Re: Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

#6 2015-03-28 05:30:18

Re: Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

#7 2015-03-28 08:49:10

Re: Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

#8 2015-03-28 17:04:25

Re: Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

#9 2015-06-27 16:51:09

Re: Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

#10 2015-08-15 08:44:49

Re: Bumblebee daemon reported: error — ASUS UX303LN,bumblebee,geforce 840m

Arch Linux

#1 2013-04-26 10:38:18

primus: fatal: failure contacting bumblebee daemon [SOLVED]

primus: fatal: Bumblebee daemon reported: error: Could not load GPU driver

2 Answers 2

primus: fatal: Bumblebee daemon reported: error: [XORG] (EE) Failed to load module «nvidia» (module does not exist, 0)

Читайте также:

c00lrad

c00lrad

c00lrad

c00lrad

c00lrad