• Bumblebee Service cannot be started after Nvidia Update


    Hello,

    I made some updates yesterday, at first for Kernel 4.20.11 and bbswitch and Nvidia drivers, everything was fine then and worked.
    Later in the evening I got another prompt of updates, but these included just Nvidia Drivers and Libraries, but also Nvidia Settings.
    Now after the reboot, I cannot run applications with optirun and also not enable an external monitor with “intel-virtual-output”.

    optirun -status
    [  170.768295] [ERROR]The Bumblebee daemon has not been started yet or the socket path tatus was incorrect.
    [  170.768350] [ERROR]Could not connect to bumblebee daemon - is it running?
    
    sudo systemctl enable bumblebeed.service
    

    seems to run normally though, but the same problem persists even though I rebooted.

    inxi -Fx
    System:    Host: antergos Kernel: 4.20.11-arch2-1-ARCH x86_64 bits: 64 compiler: gcc v: 8.2.1 Desktop: Gnome 3.30.2 
               Distro: Antergos Linux 
    Machine:   Type: Laptop System: LENOVO product: 24476J7 v: ThinkPad W530 serial: <root required> 
               Mobo: LENOVO model: 24476J7 serial: <root required> UEFI [Legacy]: LENOVO v: G5ET98WW (2.58 ) 
               date: 04/01/2014 
    Battery:   ID-1: BAT0 charge: 44.2 Wh condition: 48.9/93.6 Wh (52%) model: LGC 45N1011 status: Discharging 
    CPU:       Topology: Quad Core model: Intel Core i7-3740QM bits: 64 type: MT MCP arch: Ivy Bridge rev: 9 
               L2 cache: 6144 KiB 
               flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 43123 
               Speed: 1197 MHz min/max: 1200/3700 MHz Core speeds (MHz): 1: 1198 2: 1198 3: 1198 4: 1199 5: 1197 6: 1197 
               7: 1197 8: 1199 
    Graphics:  Device-1: Intel 3rd Gen Core processor Graphics vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0 
               Device-2: NVIDIA GK107GLM [Quadro K2000M] driver: N/A bus ID: 01:00.0 
               Display: x11 server: X.Org 1.20.3 driver: intel resolution: 1920x1080~60Hz 
               OpenGL: renderer: Mesa DRI Intel Ivybridge Mobile v: 4.2 Mesa 18.3.3 direct render: Yes 
    Audio:     Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Lenovo driver: snd_hda_intel v: kernel 
               bus ID: 00:1b.0 
               Sound Server: ALSA v: k4.20.11-arch2-1-ARCH 
    Network:   Device-1: Intel 82579LM Gigabit Network vendor: Lenovo driver: e1000e v: 3.2.6-k port: 6080 
               bus ID: 00:19.0 
               IF: enp0s25 state: down mac: 3c:97:0e:9f:82:f3 
               Device-2: Intel Centrino Ultimate-N 6300 driver: iwlwifi v: kernel port: efa0 bus ID: 03:00.0 
               IF: wlp3s0 state: up mac: 3c:a9:f4:33:9f:98 
    Drives:    Local Storage: total: 465.76 GiB used: 277.89 GiB (59.7%) 
               ID-1: /dev/sda vendor: HGST (Hitachi) model: HTS725050A7E630 size: 465.76 GiB 
    Partition: ID-1: / size: 46.68 GiB used: 21.92 GiB (47.0%) fs: ext4 dev: /dev/sda2 
               ID-2: /boot size: 1022.2 MiB used: 61.1 MiB (6.0%) fs: ext4 dev: /dev/sda1 
               ID-3: /home size: 406.53 GiB used: 255.91 GiB (62.9%) fs: ext4 dev: /dev/sda3 
    Sensors:   System Temperatures: cpu: 43.0 C mobo: N/A 
               Fan Speeds (RPM): cpu: 0 
    Info:      Processes: 248 Uptime: 14m Memory: 7.35 GiB used: 1.24 GiB (16.9%) Init: systemd Compilers: gcc: 8.2.1 
               Shell: bash v: 5.0.0 inxi: 3.0.30
    

    I guess the problem has to do with these latest Nvidia Updates I made. Is there any way of rolling back this drivers and libraries?
    Unfortunatly wasn’t able to set up something like Timeshift yet, since it plainly doesn’t work with NAS Storage.

  • @Severus
    There’s a package called downgrade that, as expected, can be used for downgrading packages.

    But be careful when using it since it can easily make the system unbootable when downgrading essential system packages. (Well, you can go back with chrooting and reinstalling the packages.)

    And of course, downgrading is not a long term solution, but merely a short term workaround.

  • @Severus said in Bumblebee Service cannot be started after Nvidia Update:

    systemctl enable bumblebeed.service

    as it is already enabled, the command gives no output…

    you should do:

    systemctl status bumblebeed.service

  • Okay. I tried the status output you provided. And it gives me the following output:

    sudo systemctl status bumblebeed.service
    ● bumblebeed.service - Bumblebee C Daemon
       Loaded: loaded (/usr/lib/systemd/system/bumblebeed.service; enabled; vendor preset: disabled)
       Active: active (running) since Sun 2019-02-24 12:01:14 CET; 1min 22s ago
     Main PID: 776 (bumblebeed)
        Tasks: 1 (limit: 4915)
       Memory: 2.2M
       CGroup: /system.slice/bumblebeed.service
               └─776 /usr/bin/bumblebeed
    
    Feb 24 12:01:14 antergos systemd[1]: Started Bumblebee C Daemon.
    Feb 24 12:01:15 antergos bumblebeed[776]: [   15.116040] [INFO]/usr/bin/bumblebeed 3.2.1 started
    
    

    That is a bit confusing, since the optirun -status command still gives me the info that bumblebee is not running…

    Should I try downgrading the Nvidia Stuff or is there anything else I can try? If possible I don’t want to completely break my system.

  • do you make sure system is completely updated? may something went wrong on last update.

  • @Severus
    Are you sure you haven’t blocked any updates?

  • @joekamprad
    It certainly looked that way to me. At least I didn’t see any error.

    @manuel
    I am quite sure I didn’t, since I usually just update without any issues. And really I don’t even know how to block updates.

    cat /var/log/pacman.log
    
    [2019-02-23 11:02] [PACMAN] Running 'pacman -R -s --config /etc/pacman.conf -- minecraft-launcher'
    [2019-02-23 11:02] [ALPM] transaction started
    [2019-02-23 11:03] [ALPM] removed minecraft-launcher (2.1.2472-1)
    [2019-02-23 11:03] [ALPM] transaction completed
    [2019-02-23 11:03] [ALPM] running 'gtk-update-icon-cache.hook'...
    [2019-02-23 11:03] [ALPM] running 'systemd-update.hook'...
    [2019-02-23 11:03] [ALPM] running 'update-desktop-database.hook'...
    [2019-02-23 11:04] [PACMAN] Running 'pacman -Syu'
    [2019-02-23 11:04] [PACMAN] synchronizing package lists
    [2019-02-23 11:04] [PACMAN] starting full system upgrade
    [2019-02-23 11:04] [ALPM] transaction started
    [2019-02-23 11:04] [ALPM] upgraded iana-etc (20190125-1 -> 20190219-1)
    [2019-02-23 11:04] [ALPM] upgraded libgdm (3.30.2-2 -> 3.30.2+5+g57bf0dd7-1)
    [2019-02-23 11:04] [ALPM] upgraded libgweather (3.28.2-1 -> 3.28.3-1)
    [2019-02-23 11:04] [ALPM] upgraded python-beaker (1.10.0-3 -> 1.10.1-1)
    [2019-02-23 11:04] [ALPM] upgraded tracker (2.2.0-1 -> 2.2.0-2)
    [2019-02-23 11:04] [ALPM] transaction completed
    [2019-02-23 11:04] [ALPM] running 'glib-compile-schemas.hook'...
    [2019-02-23 11:04] [ALPM-SCRIPTLET] cannot provide per-desktop overrides for localised key “visible-name” in schema “org.gnome.Terminal.Legacy.Profile:/org/gnome/terminal/legacy/profiles:/:b1dcc9dd-5262-4d8d-a863-c897e6d979b9” (override file “/usr/share/glib-2.0/schemas/90_antergos_gnome.gschema.override”); ignoring override for this key.
    [2019-02-23 11:04] [ALPM] running 'systemd-update.hook'...
    [2019-02-23 11:06] [PACMAN] Running 'pacman -U --noconfirm --config /etc/pacman.conf -- /home/svenja/.cache/yay/minecraft-launcher/minecraft-launcher-2.1.2472-1-x86_64.pkg.tar'
    [2019-02-23 11:06] [ALPM] transaction started
    [2019-02-23 11:06] [ALPM] installed minecraft-launcher (2.1.2472-1)
    [2019-02-23 11:06] [ALPM] transaction completed
    [2019-02-23 11:06] [ALPM] running 'gtk-update-icon-cache.hook'...
    [2019-02-23 11:06] [ALPM] running 'systemd-update.hook'...
    [2019-02-23 11:06] [ALPM] running 'update-desktop-database.hook'...
    [2019-02-23 16:49] [PACMAN] Running 'pacman -Syu'
    [2019-02-23 16:49] [PACMAN] synchronizing package lists
    [2019-02-23 16:49] [PACMAN] starting full system upgrade
    [2019-02-23 16:50] [ALPM] running '70-dkms-remove.hook'...
    [2019-02-23 16:50] [ALPM-SCRIPTLET] ==> dkms remove nvhda/r10.3e13d2e -k 4.20.11-arch1-1-ARCH
    [2019-02-23 16:50] [ALPM-SCRIPTLET] ==> dkms remove openrazer-driver/2.4.0 -k 4.20.11-arch1-1-ARCH
    [2019-02-23 16:50] [ALPM-SCRIPTLET] ==> dkms remove tp_smapi-dkms/0.43 -k 4.20.11-arch1-1-ARCH
    [2019-02-23 16:50] [ALPM-SCRIPTLET] ==> dkms remove vboxhost/6.0.4_OSE -k 4.20.11-arch1-1-ARCH
    [2019-02-23 16:50] [ALPM] transaction started
    [2019-02-23 16:50] [ALPM] upgraded linux (4.20.11.arch1-1 -> 4.20.11.arch2-1)
    [2019-02-23 16:50] [ALPM] upgraded bbswitch (0.8-199 -> 0.8-200)
    [2019-02-23 16:50] [ALPM] upgraded libnm (1.14.5dev+17+gba83251bb-2 -> 1.14.6-1)
    [2019-02-23 16:50] [ALPM] upgraded libnm-glib (1.14.5dev+17+gba83251bb-2 -> 1.14.6-1)
    [2019-02-23 16:50] [ALPM] upgraded libxkbcommon (0.8.3-1 -> 0.8.4-1)
    [2019-02-23 16:50] [ALPM] upgraded libxkbcommon-x11 (0.8.3-1 -> 0.8.4-1)
    [2019-02-23 16:50] [ALPM] upgraded linux-headers (4.20.11.arch1-1 -> 4.20.11.arch2-1)
    [2019-02-23 16:50] [ALPM] upgraded networkmanager (1.14.5dev+17+gba83251bb-2 -> 1.14.6-1)
    [2019-02-23 16:50] [ALPM] upgraded nvidia-390xx (390.87-35 -> 390.87-36)
    [2019-02-23 16:50] [ALPM] upgraded python-anytree (2.6.0-1 -> 2.6.0-2)
    [2019-02-23 16:50] [ALPM] transaction completed
    [2019-02-23 16:50] [ALPM] running '60-linux.hook'...
    [2019-02-23 16:51] [ALPM] running '70-dkms-install.hook'...
    [2019-02-23 16:51] [ALPM-SCRIPTLET] ==> dkms install vboxhost/6.0.4_OSE -k 4.20.11-arch2-1-ARCH
    [2019-02-23 16:51] [ALPM-SCRIPTLET] ==> dkms install nvhda/r10.3e13d2e -k 4.20.11-arch2-1-ARCH
    [2019-02-23 16:51] [ALPM-SCRIPTLET] ==> dkms install tp_smapi-dkms/0.43 -k 4.20.11-arch2-1-ARCH
    [2019-02-23 16:51] [ALPM-SCRIPTLET] ==> dkms install openrazer-driver/2.4.0 -k 4.20.11-arch2-1-ARCH
    [2019-02-23 16:52] [ALPM] running '90-linux.hook'...
    [2019-02-23 16:52] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
    [2019-02-23 16:52] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
    [2019-02-23 16:52] [ALPM-SCRIPTLET] ==> Starting build: 4.20.11-arch2-1-ARCH
    [2019-02-23 16:52] [ALPM-SCRIPTLET]   -> Running build hook: [base]
    [2019-02-23 16:52] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
    [2019-02-23 16:52] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
    [2019-02-23 16:52] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
    [2019-02-23 16:52] [ALPM-SCRIPTLET]   -> Running build hook: [block]
    [2019-02-23 16:52] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
    [2019-02-23 16:52] [ALPM-SCRIPTLET]   -> Running build hook: [keymap]
    [2019-02-23 16:52] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
    [2019-02-23 16:52] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
    [2019-02-23 16:52] [ALPM-SCRIPTLET] ==> Generating module dependencies
    [2019-02-23 16:52] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
    [2019-02-23 16:52] [ALPM-SCRIPTLET] ==> Image generation successful
    [2019-02-23 16:52] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
    [2019-02-23 16:52] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
    [2019-02-23 16:52] [ALPM-SCRIPTLET] ==> Starting build: 4.20.11-arch2-1-ARCH
    [2019-02-23 16:52] [ALPM-SCRIPTLET]   -> Running build hook: [base]
    [2019-02-23 16:52] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
    [2019-02-23 16:52] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
    [2019-02-23 16:52] [ALPM-SCRIPTLET]   -> Running build hook: [block]
    [2019-02-23 16:52] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: wd719x
    [2019-02-23 16:52] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
    [2019-02-23 16:52] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
    [2019-02-23 16:52] [ALPM-SCRIPTLET]   -> Running build hook: [keymap]
    [2019-02-23 16:52] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
    [2019-02-23 16:52] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
    [2019-02-23 16:52] [ALPM-SCRIPTLET] ==> Generating module dependencies
    [2019-02-23 16:52] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
    [2019-02-23 16:52] [ALPM-SCRIPTLET] ==> Image generation successful
    [2019-02-23 16:52] [ALPM] running 'antergos-reboot.hook'...
    [2019-02-23 16:52] [ALPM] running 'systemd-daemon-reload.hook'...
    [2019-02-23 16:52] [ALPM] running 'systemd-udev-reload.hook'...
    [2019-02-23 16:52] [ALPM] running 'systemd-update.hook'...
    [2019-02-23 18:49] [PACMAN] Running 'pacman -S falkon'
    [2019-02-23 18:49] [ALPM] transaction started
    [2019-02-23 18:49] [ALPM] installed qt5-webengine (5.12.1-1)
    [2019-02-23 18:49] [ALPM] installed falkon (3.0.1-6)
    [2019-02-23 18:49] [ALPM] transaction completed
    [2019-02-23 18:49] [ALPM] running 'gtk-update-icon-cache.hook'...
    [2019-02-23 18:49] [ALPM] running 'systemd-update.hook'...
    [2019-02-23 18:49] [ALPM] running 'update-desktop-database.hook'...
    [2019-02-23 18:51] [PACMAN] Running 'pacman -S kdenlive'
    [2019-02-23 19:04] [PACMAN] Running 'pacman -S conky'
    [2019-02-23 19:05] [ALPM] transaction started
    [2019-02-23 19:05] [ALPM] reinstalled conky (1.11.2-1)
    [2019-02-23 19:05] [ALPM] transaction completed
    [2019-02-23 19:05] [ALPM] running 'systemd-update.hook'...
    [2019-02-23 21:03] [PACMAN] Running 'pacman -Syu'
    [2019-02-23 21:03] [PACMAN] synchronizing package lists
    [2019-02-23 21:03] [PACMAN] starting full system upgrade
    [2019-02-23 21:49] [PACMAN] Running 'pacman -Syu'
    [2019-02-23 21:49] [PACMAN] synchronizing package lists
    [2019-02-23 21:49] [PACMAN] starting full system upgrade
    [2019-02-23 21:50] [ALPM] transaction started
    [2019-02-23 21:50] [ALPM] upgraded nvidia-390xx-utils (390.87-1 -> 390.116-1)
    [2019-02-23 21:50] [ALPM-SCRIPTLET] If you run into trouble with CUDA not being available, run nvidia-modprobe first.
    [2019-02-23 21:50] [ALPM] upgraded lib32-nvidia-390xx-utils (390.87-2 -> 390.116-2)
    [2019-02-23 21:50] [ALPM] upgraded lib32-opencl-nvidia-390xx (390.87-2 -> 390.116-2)
    [2019-02-23 21:50] [ALPM] upgraded libxnvctrl-390xx (390.87-1 -> 390.116-1)
    [2019-02-23 21:50] [ALPM] upgraded nvidia-390xx (390.87-36 -> 390.116-1)
    [2019-02-23 21:50] [ALPM] upgraded nvidia-390xx-settings (390.87-1 -> 390.116-1)
    [2019-02-23 21:50] [ALPM] upgraded opencl-nvidia-390xx (390.87-1 -> 390.116-1)
    [2019-02-23 21:50] [ALPM] transaction completed
    [2019-02-23 21:50] [ALPM] running '60-linux.hook'...
    [2019-02-23 21:51] [ALPM] running 'antergos-reboot.hook'...
    [2019-02-23 21:52] [ALPM] running 'systemd-daemon-reload.hook'...
    [2019-02-23 21:52] [ALPM] running 'systemd-sysusers.hook'...
    [2019-02-23 21:52] [ALPM] running 'systemd-update.hook'...
    [2019-02-23 21:52] [ALPM] running 'update-desktop-database.hook'...
    

    Is what I have for yesterday. I would guess it must have been the update around 21:50 which caused the problem.

    Also pacman tells me there is nothing to do.

  • @Severus
    OK, I was just thinking if you simply forgot something as blocked, but that’s clearly not the case.

    One thing though, maybe helps nothing, but just a check: what does command

    nvidia-installer -b -t
    

    show? You may need to install package nvidia-installer.

    EDIT: By the way, you could try using the dkms versions of the related packages:

    nvidia-390xx-dkms
    bbswitch-dkms
    linux-headers
    linux-lts-headers  # optional
    
  • @manuel

    The output from Nvidia installer is this one:

    nvidia-installer -b -t
    2019-02-24 13:04:40 [INFO]: Antergos Nvidia Installer v1.17
    2019-02-24 13:04:40 [INFO]: All logs will be stored in /tmp/nvidia-installer.log
    2019-02-24 13:04:40 [INFO]: Running the installer in testing mode...
    2019-02-24 13:04:41 [INFO]: Installing bumblebee driver...
    2019-02-24 13:04:41 [INFO]: Removing conflicting packages...
    2019-02-24 13:04:41 [INFO]: pacman -Rs --noconfirm --noprogressbar --nodeps nvidia-390xx-utils
    2019-02-24 13:04:41 [INFO]: pacman -Rs --noconfirm --noprogressbar --nodeps lib32-nvidia-390xx-utils
    2019-02-24 13:04:41 [INFO]: Downloading and installing driver packages, please wait...
    2019-02-24 13:04:41 [INFO]: pacman -Sqy --noconfirm --noprogressbar bumblebee mesa xf86-video-intel nvidia virtualgl nvidia-settings bbswitch lib32-nvidia-utils lib32-virtualgl lib32-mesa
    2019-02-24 13:04:41 [INFO]: Adding user svenja to bumblebee group...
    2019-02-24 13:04:41 [INFO]: gpasswd -a svenja bumblebee
    2019-02-24 13:04:41 [INFO]: Adding user svenja to video group...
    2019-02-24 13:04:41 [INFO]: gpasswd -a svenja video
    2019-02-24 13:04:41 [INFO]: Enabling bumblebeed.service service...
    2019-02-24 13:04:41 [INFO]: systemctl enable bumblebeed.service
    2019-02-24 13:04:41 [INFO]: Patching /usr/share/applications/nvidia-settings.desktop...
    2019-02-24 13:04:41 [INFO]: sed -i s|Exec=/usr/bin/nvidia-settings|Exec=optirun -b none /usr/bin/nvidia-settings -c :8| /usr/share/applications/nvidia-settings.desktop
    2019-02-24 13:04:41 [INFO]: /etc/X11/xorg.conf.d/20-nvidia.conf not found. That's ok.
    2019-02-24 13:04:41 [INFO]: Installation finished. Nothing has been modified as testing mode was ON.
    

    My graphics card is a Nvidia Quadro K2000M though, where Nvidia Website shows it is only supported on Nvidia 390xx Legacy Driver though so I guess the Nvidia Installer didn’t check for that.

  • @Severus
    AFAIK nvidia-installer checks it. And I also checked nvidia.com to see, and the nvidia driver (version 418.43) does support your card.

    So installing that might help. It is available via pacman.

  • @manuel
    Okay Now I am really wondering, what exactly is going on. I know last Time I checked it was definitly in the Legacy Drive List. I also know I once had a problem where it was the problem that I had once the latest Driver running and I needed to install 390xx Version, since Nvidia had moved my card to 390xx and it was running fine on that till yesterday.

    But okay whatever I just try it now. Can’t break anything more I guess. Just saving the Bumblebee Config though. Will post later here. Thanks so far.

  • @Severus
    The new driver was created at nvidia couple of days ago…

  • @manuel
    Thank you so much. Don’t know why Nvidia suddenly decided to move Cards out of Legacy, but okay…

    Really haven’t thought of that… Seems kinda crazy. But external Monitor is working again. Now have to get Nvhda working again with Audio through Displayport. I’ll see how it goes. Thank you.

  • @Severus
    If you feel this is solved, would you mind marking the thread as solved? 😃

  • @manuel
    Sorry. Just forgot.

nvidia166 bumblebee49 service18 Posts 16Views 150
Log in to reply
Bloom Email Optin Plugin

Looks like your connection to Antergos Community Forum was lost, please wait while we try to reconnect.