Bumblebee not working

Cristiano Urban · 12-28-2017, 05:50 AM

Hi,
I have some issues with Bumblebee, it doesn't work anymore on my laptop, a Dell Inspiron 7537.
My machine runs Slackware stable 14.2 x86_64 at the last patch level with multilib installed.
I've already blacklisted the nouveau drivers (xf86-video-nouveau-blacklist-noarch-1.txz is already installed).
I used the so called "automated way" to install/upgrade Bumblebee.
Here below I try to provide some additional information that could be useful.

Code:

bash-4.3# lspci
00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09)                                                                       
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09)                                          
00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 09)                                                                  
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.2 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (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:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04)                                                                           
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)                                                                               
02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)
03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5287 (rev 01)
03:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 12)
04:00.0 3D controller: NVIDIA Corporation GK107M [GeForce GT 750M] (rev a1)

Code:

bash-4.3$ primusrun glxgears
primus: fatal: Bumblebee daemon reported: error: [XORG] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied

Code:

bash-4.3$ optirun glxgears
[   69.287402] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied

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

Code:

bash-4.3# dmesg | tail
[   41.717400] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0).
[   41.717405] atkbd serio0: Use 'setkeycodes e00d <keycode>' to make it known.
[   61.510764] vgaarb: this pci device is not a vga device
[   61.514788] NVRM: failed to copy vbios to system memory.
[   61.514935] NVRM: RmInitAdapter failed! (0x30:0xffff:654)
[   61.514955] NVRM: rm_init_adapter failed for device bearing minor number 0
[   69.303698] vgaarb: this pci device is not a vga device
[   69.306067] NVRM: failed to copy vbios to system memory.
[   69.306214] NVRM: RmInitAdapter failed! (0x30:0xffff:654)
[   69.306232] NVRM: rm_init_adapter failed for device bearing minor number 0

/etc/bumblebee/xorg.conf.nvidia

Code:

Section "ServerLayout"
    Identifier  "Layout0"
    Option      "AutoAddDevices" "false"
    Option      "AutoAddGPU" "false"
EndSection

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

#   If the X server does not automatically detect your VGA device,
#   you can manually set it here.
#   To get the BusID prop, run `lspci | egrep 'VGA|3D'` and input the data
#   as you see in the commented example.
#   This Setting may be needed in some platforms with more than one
#   nvidia card, which may confuse the proprietary driver (e.g.,
#   trying to take ownership of the wrong device). Also needed on Ubuntu 13.04.
#   BusID "PCI:01:00:0"

#   Setting ProbeAllGpus to false prevents the new proprietary driver
#   instance spawned to try to control the integrated graphics card,
#   which is already being managed outside bumblebee.
#   This option doesn't hurt and it is required on platforms running
#   more than one nvidia graphics card with the proprietary driver.
#   (E.g. Macbook Pro pre-2010 with nVidia 9400M + 9600M GT).
#   If this option is not set, the new Xorg may blacken the screen and
#   render it unusable (unless you have some way to run killall Xorg).
    Option "ProbeAllGpus" "false"

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

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

/etc/bumblebee/bumblebee.conf

Code:

# Configuration file for Bumblebee. Values should **not** be put between quotes

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

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

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

## Section with nvidia driver specific options, only parsed if Driver=nvidia
[driver-nvidia]
# Module name to load, defaults to Driver if empty or unset
KernelDriver=nvidia
PMMethod=auto
# colon-separated path to the nvidia libraries
LibraryPath=/usr/lib64/nvidia-bumblebee:/usr/lib/nvidia-bumblebee
# comma-separated path of the directory containing nvidia_drv.so and the
# default Xorg modules path
XorgModulePath=/usr/lib64/nvidia-bumblebee/xorg/modules,/usr/lib64/xorg/modules
XorgConfFile=/etc/bumblebee/xorg.conf.nvidia

## Section with nouveau driver specific options, only parsed if Driver=nouveau
[driver-nouveau]
KernelDriver=nouveau
PMMethod=auto
XorgConfFile=/etc/bumblebee/xorg.conf.nouveau

If I start the service manually, all seems to be ok:

Code:

bash-4.3# /etc/rc.d/rc.bumblebeed start
bash-4.3# ps -A | grep bumblebee
 2429 ?        00:00:00 bumblebeed

If I try to restart it manually, instead, I obtain the following error (some words of the output are in italian, sorry):

Code:

bash-4.3# /etc/rc.d/rc.bumblebeed restart
/etc/rc.d/rc.bumblebeed: riga 34: kill: "": non è un pid o un numero di job valido
modprobe: ERROR: could not insert 'bbswitch': No such device

I also added an attachment containing the content of /var/log/Xorg.0.log.

Is there anyone having the same problems?
Thank you in advance for your help.

Cristiano.

bassmadrigal · 12-28-2017, 10:16 PM

My guess is that your user is not a part of the video group. What is the output of the groups command? If you used adduser and used the suggested groups, it should look like the below:

Code:

jbhansen@craven-moorhead:~$ groups
users lp floppy audio video cdrom plugdev power netdev scanner

If you are only a member of users, run the following command, replacing $USER with your username for the computer:

Code:

usermod -a -G lp floppy audio video cdrom plugdev power netdev scanner $USER

You'll need to log out and log back in for it to take effect (or simply reboot the computer).

Cristiano Urban · 12-29-2017, 03:07 AM

Hi bassmadrigal,
thank you for your answer.

The output of the groups command is the following one:

Code:

bash-4.3$ groups
users lp floppy audio video cdrom plugdev power netdev scanner vitamtp vboxusers bumblebee

I don't know what could be wrong.

bassmadrigal · 12-29-2017, 12:53 PM

What resource did you use to install bumblebee? Unfortunately, I have no experience with it, so I'm not sure how much help I'll be...

TheEzekielProject · 12-29-2017, 01:47 PM

So you had this working properly before?

Does it work again if you use the old kernel?

Cristiano Urban · 12-29-2017, 02:34 PM

Quote:

Originally Posted by bassmadrigal

What resource did you use to install bumblebee?

I installed Bumblebee with the "automated way", as described here. I used the first command, the one without the STABLE parameter.

Quote:

Originally Posted by TheEzekielProject

So you had this working properly before?

Yes, but unfortunately I have noticed that it doesn't work only a few days ago. I didn't check it for a long time, so I'm not able to say when exactly it stopped working.

Quote:

Originally Posted by TheEzekielProject

Does it work again if you use the old kernel?

I don't know. I think I will try it (should be the 4.4.75) in these days and I will report here what happens.

TommyC7 · 12-29-2017, 03:11 PM

The nvidia driver installs itself into the kernel directories (bbswitch as well) so if you upgraded your kernel recently chances are the packages weren't rebuilt for the new kernel.

Just rebuild and then reinstall the nivida-kernel package and the bbswitch package as described in the FAQ at the end of the wiki article.

Cristiano Urban · 12-29-2017, 03:59 PM

TommyC7,
I upgraded the kernel to the version 4.4.88 a short time after its appearance on the changelog.
Anyway, some days ago I have launched the script to rebuild and reinstall all the Bumblebee related stuff, but the errors are still present.

bassmadrigal · 12-29-2017, 06:48 PM

Quote:

Originally Posted by Cristiano Urban

TommyC7,
I upgraded the kernel to the version 4.4.88 a short time after its appearance on the changelog.
Anyway, some days ago I have launched the script to rebuild and reinstall all the Bumblebee related stuff, but the errors are still present.

You would also need to rebuild the kernel modules for the nvidia driver, which I don't know if the bumblebee script does that for you.

@TheEzekielProject and TommyC7, good catch on the kernel upgrade!

Cristiano Urban · 12-30-2017, 03:44 PM

I have just made a very simple test.

I've re-added the entry for the kernel 4.4.75 in /etc/lilo.conf, then I rebooted the machine with that kernel.
Launching optirun glxgears or primusrun glxgears has given me the same errors I reported on the first post (as expected).
Then I have launched the script (after removing the old folder present in /root) in order to rebuild and reinstall all the needed.
After that, I have rebooted my laptop, I have tried again with the same commands and all has worked fine.

Then I've rebooted in order to retry with the last kernel, the 4.4.88.
I've repeated the same procedure, but I've re-obtained the usual errors...

Now the question I have in mind is: may be something related to the kernel 4.4.88?

BradReed · 12-30-2017, 04:45 PM

So when you ran the script when booted into kernel 4.4.75, presumably it successfully created:
/tmp/libbsd-0.8.3-x86_64-1_bbsb.txz
/tmp/bumblebee-3.2.1-x86_64-1_bbsb.txz
/tmp/bbswitch-0.8_4.4.75-x86_64-1_bbsb.txz
/tmp/primus-0.1.7-x86_64-1_bbsb.txz
/tmp/nvidia-kernel-XXX.XX_4.4.75-x86_64-1_bbsb.txz
/tmp/nvidia-bumblebee-XXX.XX-x86_64-1_bbsb.txz

(replacing XXX.XX with whatever version of nvidia driver the standard bumblebee is using these days.)

When you ran the script in kernel 4.4.88, did it rebuild all of these six packages correctly?
/tmp/libbsd-0.8.3-x86_64-1_bbsb.txz
/tmp/bumblebee-3.2.1-x86_64-1_bbsb.txz
/tmp/bbswitch-0.8_4.4.88-x86_64-1_bbsb.txz
/tmp/primus-0.1.7-x86_64-1_bbsb.txz
/tmp/nvidia-kernel-XXX.XX_4.4.88-x86_64-1_bbsb.txz
/tmp/nvidia-bumblebee-XXX.XX-x86_64-1_bbsb.txz

Which failed to build? if they all rebuilt, did you install all of them?

Cristiano Urban · 12-31-2017, 05:24 AM

Quote:

Originally Posted by BradReed

When you ran the script in kernel 4.4.88, did it rebuild all of these six packages correctly?

Yes.

Quote:

Originally Posted by BradReed

[...], if they all rebuilt, did you install all of them?

Yes, all seems to be installed correctly.

Code:

bash-4.3$ ls /var/log/packages/ | grep libbsd
libbsd-0.8.3-x86_64-1_bbsb

Code:

bash-4.3$ ls /var/log/packages/ | grep bumblebee
bumblebee-3.2.1-x86_64-1_bbsb
nvidia-bumblebee-375.39-x86_64-1_bbsb

Code:

bash-4.3$ ls /var/log/packages/ | grep bbswitch
bbswitch-0.8_4.4.88-x86_64-1_bbsb

Code:

bash-4.3$ ls /var/log/packages/ | grep primus
primus-0.1.7-x86_64-1_bbsb

Code:

bash-4.3$ ls /var/log/packages/ | grep nvidia-kernel
nvidia-kernel-375.39_4.4.88-x86_64-1_bbsb

BradReed · 12-31-2017, 01:24 PM

Since xorg seems to have issues with /dev/dri/card0, what are the permissions on /dev/dri/card0?
Here, mine are:

14:15 # ll /dev/dri/card0
crw-rw---- 1 root video 226, 0 2017-12-28 19:53:00 /dev/dri/card0

Also, have you tried changing:
# BusID "PCI:01:00:0"

to
BusID "PCI:04:00:0"

in /etc/bumblebee/xorg.conf.nvidia?

I also note that my XorgModulePath slightly differs from yours in /etc/bumblebee/bumblebee.conf:
XorgModulePath=/usr/lib64/nvidia-bumblebee/xorg/modules,/usr/lib64/xorg/modules,/usr/lib64/xorg/modules/drivers

Cristiano Urban · 01-01-2018, 08:34 AM

First of all, happy new year to everyone!

Quote:

Originally Posted by BradReed

Since xorg seems to have issues with /dev/dri/card0, what are the permissions on /dev/dri/card0?

These are the permissions for /dev/dri/card0:

Code:

bash-4.3# ls -l /dev/dri/card0
crw-rw----+ 1 root video 226, 0 gen  1 14:51 /dev/dri/card0

I've tried to made some changes to the BusID in /etc/bumblebee/xorg.nvidia.conf and to the paths in /etc/bumblebee/bumblebee.conf also bearing in mind of these considerations, but nothing seems to change.

The point is that, with the 4.4.75, all worked fine with this configuration and I can't figure out if this is something related to a mistake I made or if, instead, this is due to something that doesn't depend on me.

Inspecting the output of dmesg and lsmod I've found something else:

Code:

bash-4.3# dmesg | grep nvidia
[    5.769452] nvidia: module license 'NVIDIA' taints kernel.
[    5.778638] nvidia 0000:04:00.0: enabling device (0006 -> 0007)
[    5.778919] nvidia-nvlink: Nvlink Core is being initialized, major device number 245
[    5.794660] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  375.39  Tue Jan 31 19:41:48 PST 2017
[    6.844080] [drm] [nvidia-drm] [GPU ID 0x00000400] Loading driver

Code:

bash-4.3# lsmod | grep nvidia
nvidia_drm             44041  0
nvidia_modeset        783360  1 nvidia_drm
nvidia              12124768  1 nvidia_modeset
drm_kms_helper        119004  2 i915,nvidia_drm
drm                   323286  6 i915,drm_kms_helper,nvidia_drm
i2c_core               47925  14 drm,i915,i2c_i801,elan_i2c,i2c_dev,i2c_hid,i2c_designware_core,i2c_designware_platform,drm_kms_helper,i2c_algo_bit,eeprom,nvidia,v4l2_common,videodev

Code:

bash-4.3# dmesg | grep bbswitch
[   11.991415] bbswitch: version 0.8
[   11.991421] bbswitch: Found integrated VGA device 0000:00:02.0: \_SB_.PCI0.GFX0
[   11.991428] bbswitch: Found discrete VGA device 0000:04:00.0: \_SB_.PCI0.RP05.PXSX
[   11.991440] bbswitch: failed to evaluate \_SB_.PCI0.RP05.PXSX._DSM {0xF8,0xD8,0x86,0xA4,0xDA,0x0B,0x1B,0x47,0xA7,0x2B,0x60,0x42,0xA6,0xB5,0xBE,0xE0} 0x100 0x0 {0x00,0x00,0x00,0x00}: AE_NOT_FOUND
[   11.991448] bbswitch: failed to evaluate \_SB_.PCI0.RP05.PXSX._DSM {0xA0,0xA0,0x95,0x9D,0x60,0x00,0x48,0x4D,0xB3,0x4D,0x7E,0x5F,0xEA,0x12,0x9F,0xD4} 0x102 0x0 {0x00,0x00,0x00,0x00}: AE_NOT_FOUND
[   11.991511] bbswitch: No suitable _DSM call found.

The nvidia driver seems to be loaded, bbswitch, instead, is complaining.

Cristiano Urban · 01-01-2018, 09:02 AM

For completeness, I also attach the full content of dmesg here below.