You are not logged in.
Two days ago after updating the kernel, systemd (245.2-1) and nvidia driver bumblebee has some problems.
And nothing has changed since today's update (bbswitch-0.8-298, linux-5.5.10.arch1-1, systemd-245.2-2 ).
Before reporting a bug, am I the only one with this problem?
[ksolsim@arch ~]optirun --status
[ 1123.918390] [ERROR]The Bumblebee daemon has not been started yet or the socket path /var/run/bumblebee.socket was incorrect.
[ 1123.918458] [ERROR]Could not connect to bumblebee daemon - is it running?Could not connect to bumblebee daemon - is it running?
if I restart bumblebee and check bumblebeed I got:
[root@arch ksolsim]$ systemctl restart bumblebeed
[root@arch ksolsim]$ systemctl status bumblebeed
● bumblebeed.service - Bumblebee C Daemon
Loaded: loaded (/usr/lib/systemd/system/bumblebeed.service; enabled; vendor preset: disabled)
Active: activating (auto-restart) (Result: exit-code) since Fri 2020-03-20 18:30:34 CET; 14s ago
Process: 3517 ExecStart=/usr/bin/bumblebeed (code=exited, status=1/FAILURE)
Main PID: 3517 (code=exited, status=1/FAILURE)
[ksolsim@arch ~]$ cat /proc/acpi/bbswitch
0000:01:00.0 ON
until this morning i got this:
[root@arch ksolsim]$ systemctl restart bumblebeed
[root@arch ksolsim]$ systemctl status bumblebeed
systemctl status bumblebeed.service
● bumblebeed.service - Bumblebee C Daemon
Loaded: loaded (/usr/lib/systemd/system/bumblebeed.service; enabled; vendo>
Active: activating (auto-restart) (Result: exit-code) since Wed 2020-03-18>
Process: 2481 ExecStart=/usr/bin/bumblebeed (code=exited, status=1/FAILURE)
Main PID: 2481 (code=exited, status=1/FAILURE)
[root@arch cylon-gnome]# dmesg |tail -1
[ 1247.954307] audit: type=1131 audit(1584521714.264:166): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bumblebeed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
and the only way to turn off the nvidia v card is:
[root@arch ksolsim]# tee /proc/acpi/bbswitch <<<OFF
OFF
[ksolsim@arch ~]$ cat /proc/acpi/bbswitch0000:01:00.0 OFF
Last edited by ksolsim (2020-03-26 21:49:32)
Offline
I think I've figured out what the mistake was. Nvidia-390xx drivers have been moved without any warnings or news from extra to AUR.
edit: after ugrading from aur nvidia-390xx-utils and vidia-390xx driver everything works.
Last edited by ksolsim (2020-03-26 23:19:44)
Offline
It was mentioned in the arch-dev-public mailing list
https://lists.archlinux.org/pipermail/a … 29884.html
https://lists.archlinux.org/pipermail/a … 29894.html
https://lists.archlinux.org/pipermail/a … 29895.html
Offline
sorry, I don't have time to read arch-dev-public mailing list ( I have never read it in 12 years of using arch)
Offline